Robotics Systems Types

I was able to install and use rst by following the steps given in documentation .. there is a further link ´installing RST´ (http://docs.cor-lab.de//rst-manual/trunk/html/install.html#build-instructions) in documentation which gives detailed installation steps.
I verified installation by running mvn install command from directory rst/rst-proto/build/java using pom-stable.xml.
- Is the the right way for verification ?
If it is then I think steps already mentioned should be enough for user to install and use RST
- do you think we need to add something to the documentation ?

Suchit Sharma wrote:

I was able to install and use rst by following the steps given in documentation .. there is a further link ´installing RST´ (http://docs.cor-lab.de//rst-manual/trunk/html/install.html#build-instructions) in documentation which gives detailed installation steps.
I verified installation by running mvn install command from directory rst/rst-proto/build/java using pom-stable.xml.
- Is the the right way for verification ?

I think the idea was to explain how the Robotics Systems Types artifact in the CITEC maven repository can be used in a maven-based project (i.e. without building Robotics Systems Types yourself).

It is still good that you verified the installation instructions, though.

As Johannes remarked in #1732, you probably have to describe how to add the CITEC maven repository configuation, i.e. something like

<repositories>
  <repository>
    <id>citec</id>
    <name>CITEC Maven Repository Server</name>
    <url>http://repo.cit-ec.uni-bielefeld.de/</url>
    <layout>default</layout>
    <releases>
      <enabled>true</enabled>
    </releases>
    <snapshots>
      <enabled>true</enabled>
    </snapshots>
  </repository>
</repositories>

Did you already push the changes?

Yes, I have pushed the changes.I thought I had to push the changes .. Was I supposed to do that?

Of course, we want to push the changes eventually.

However, the point of storing your patches into text files and uploading those to the Redmine issue is to give us an opportunity to review the changes and maybe suggest improvements before you actually push.

Don't worry. We don't do this for every little change. But in this case the topic is rather complicated, as Maven is concerned, so we wanted discuss and maybe improve your changes before adding them to the documentation.

But as I said, don't worry, it's not a big deal.

I have clean up the changes a bit in the repo and force pushed a new commit. In case you want to use your existing clone of the rst-manual repository for further things you need to do the following now:

git reset --hard HEAD~2
git pull --ff-only