Announcement Announcement Module
Collapse
No announcement yet.
¿ Source code downgrade between roo versions desired ? Page Title Module
Move Remove Collapse
X
Conversation Detail Module
Collapse
  • Filter
  • Time
  • Show
Clear All
new posts

  • ¿ Source code downgrade between roo versions desired ?

    A roo project source code is updated when is managed by the a newer console version.

    By example, a 1.0.0.RELEASE project managed by a 1.0.1.RELEASE console make some updates on jspx pages, data on demand aspect, etc.

    But when a 1.0.1.RELEASE project is managed by a 1.0.0.RELEASE console make some updates too (¿ downgrade ?).

    ¿ Is this downgrade behaviour desired ?

  • #2
    We had the same problem in my workplace, where a colleague hadn't upgraded his Roo from 1.0.0 to 1.0.1.

    Maybe Roo could store its version number somewhere in the project, to prevent this type of problem? Maybe a "roo.version" file in the project's root folder, or a property in the POM, like this:

    Code:
    <?xml version="1.0" encoding="UTF-8" standalone="no"?>
    <project xmlns="http://maven.apache.org/POM/4.0.0" ...>
      ...
      <properties>
        <roo.version>1.0.1</roo.version>
      </properties>
    </project>

    Comment


    • #3
      Hi,

      I am not sure if this is really needed since you could simply run 1.0.1 on your project after you accidently 'downgraded' it and Roo will upgrade it to the new version agian.

      -Stefan

      Comment


      • #4
        The problem is that if a given developer runs Roo and it makes some changes, he doesn't know whether those changes happened because:
        • he's using an older version of Roo
        • he's using a newer version of Roo
        • Roo is re-writing the correct output for the current version of Roo (e.g. someone added/removed a toString() method)
        Only the first of these cases is a problem, and it would be good if there was some way to identify this situation before it's too late (e.g. before the developer commits those changes to version control, causing all sorts of confusion).

        Comment


        • #5
          It's not too hard for us to detect the version, as it's already in the POM due to the Roo annotations JAR. A related task is http://jira.springframework.org/browse/ROO-264 if you wanted to comment on this requirement there.

          Comment


          • #6
            Done

            Originally posted by Ben Alex View Post
            It's not too hard for us to detect the version, as it's already in the POM due to the Roo annotations JAR. A related task is http://jira.springframework.org/browse/ROO-264 if you wanted to comment on this requirement there.
            I've added a comment to that effect.

            Comment

            Working...
            X