Grails Maven Plugin

maven release:prepare fails because of version not changed in application.properties

Details

  • Type: Sub-task Sub-task
  • Status: Closed Closed
  • Priority: Major Major
  • Resolution: Duplicate
  • Affects Version/s: None
  • Fix Version/s: None
  • Component/s: None
  • Labels:
    None

Description

When running mvn release:prepare, maven changes the version from 1.0-SNAPSHOT to 1.0, but the app.version in application.properties is not changed accordingly. The grails-maven plugin complains about this, causing the release to fail.

Issue Links

Activity

Hide
Reiner Saddey added a comment -

I devised a work-around that's both quite ugly and far from perfect: Teaching Mavenized Grails to Survive mvn release:prepare release:perform with Hudson

Show
Reiner Saddey added a comment - I devised a work-around that's both quite ugly and far from perfect: Teaching Mavenized Grails to Survive mvn release:prepare release:perform with Hudson
Hide
Reiner Saddey added a comment -

Peter said at Maven Users It probably makes sense for the validate goal to automatically update application.properties. I'm not sure checking whether the two versions match has any benefits.

I suspect it should be fairly easy to have the validate update application.properties as there's already a grails set-version cli.

Show
Reiner Saddey added a comment - Peter said at Maven Users It probably makes sense for the validate goal to automatically update application.properties. I'm not sure checking whether the two versions match has any benefits. I suspect it should be fairly easy to have the validate update application.properties as there's already a grails set-version cli.
Hide
Thomas Einwaller added a comment -

I think having the maven validate goal updating the version number would be a good solution!

Show
Thomas Einwaller added a comment - I think having the maven validate goal updating the version number would be a good solution!

People

Vote (1)
Watch (1)

Dates

  • Created:
    Updated:
    Resolved: