Spring Roo
  1. Spring Roo
  2. ROO-264

Automatically detect old Roo annotation JAR versions and upgrade them

    Details

    • Type: Improvement Improvement
    • Status: Closed
    • Priority: Major Major
    • Resolution: Complete
    • Affects Version/s: None
    • Fix Version/s: 1.1.0.M3
    • Component/s: BUILD
    • Labels:
      None

      Description

      Improve automated upgrades of old version of Roo to newer versions of Roo by upgrading the Roo annotation JAR. This issue is motivated due to the ROO-261.

        Issue Links

          Activity

          Hide
          Andrew Swan added a comment -

          As a related concept, Roo should check whether its version number is equal to or later than the project's existing Roo version (as indicated by the version of the Roo annotations JAR in the POM). If the version of Roo being run (version X) is older than the version in the POM (version Y), it should:

          • throw an error message to the effect that this project requires Roo version Y or later, and
          • not make any changes to the project (as these would be retrograde changes)

          See this forum thread for details:

          http://forum.springsource.org/showthread.php?t=84562

          Show
          Andrew Swan added a comment - As a related concept, Roo should check whether its version number is equal to or later than the project's existing Roo version (as indicated by the version of the Roo annotations JAR in the POM). If the version of Roo being run (version X) is older than the version in the POM (version Y), it should: throw an error message to the effect that this project requires Roo version Y or later, and not make any changes to the project (as these would be retrograde changes) See this forum thread for details: http://forum.springsource.org/showthread.php?t=84562

          It's a good idea, as first approach, I don't know related problems.

          A more scalable but complicated approach is allow addons to decide when own downgrade is available. Could be a future enhancement.

          Show
          Mario Martínez Sánchez - gvNIX - DiSiD Technologies S.L. added a comment - It's a good idea, as first approach, I don't know related problems. A more scalable but complicated approach is allow addons to decide when own downgrade is available. Could be a future enhancement.
          Hide
          Ben Alex added a comment -

          The variation to use OSGi and enable third-party add-ons to provide their own @Roo* annotations via a separate client-side build mechanism will supersede this issue. I'll leave it open until we have that capability, though.

          Show
          Ben Alex added a comment - The variation to use OSGi and enable third-party add-ons to provide their own @Roo* annotations via a separate client-side build mechanism will supersede this issue. I'll leave it open until we have that capability, though.
          Hide
          Ben Alex added a comment -

          Added with Git ID b611dbb32725cd054595326d3255cdc697cba064.

          When you load Roo, it will now automatically update

          {roo.property}

          to the same version as the hosting Roo instance. This will not happen if the existing roo.property is for a later or equal version, or the property cannot be located or parsed. The DocBook upgrade instructions have also been updated accordingly.

          Also enhanced the messages rendered when adding a property via MavenProjectMetadataProvider.

          Show
          Ben Alex added a comment - Added with Git ID b611dbb32725cd054595326d3255cdc697cba064. When you load Roo, it will now automatically update {roo.property} to the same version as the hosting Roo instance. This will not happen if the existing roo.property is for a later or equal version, or the property cannot be located or parsed. The DocBook upgrade instructions have also been updated accordingly. Also enhanced the messages rendered when adding a property via MavenProjectMetadataProvider.

            People

            • Assignee:
              Ben Alex
              Reporter:
              Ben Alex
            • Votes:
              1 Vote for this issue
              Watchers:
              0 Start watching this issue

              Dates

              • Created:
                Updated:
                Resolved: