Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

add enforcer plugin to ensure we have only released dependencies on release #2970

Closed
mkristian opened this issue May 21, 2015 · 2 comments
Closed

add enforcer plugin to ensure we have only released dependencies on release #2970

mkristian opened this issue May 21, 2015 · 2 comments
Assignees
@mkristian
Milestone
JRuby 9.0.0.0.rc2

Comments

@mkristian
Copy link
Member

since their are problems with 9k.pre2 release which seems to be OK on maven-central but the tagged version on git has pom.xml with SNAPSHOT dependencies which makes it very difficult to build the release from this tag.

the maven-enforcer-plugin can be configured to fail so ensure the moment you switch to a release version of jruby then ALL the dependencies need to be released versions as well.
@mkristian mkristian added this to the JRuby 9.0.0.0.rc1 milestone May 21, 2015
@mkristian mkristian self-assigned this May 21, 2015
@eregon
Copy link
Member

eregon commented May 22, 2015

Would it be possible to load this plugin only when releasing?
My concern is just that Eclipse keeps reporting warning because it does not know how to deal with this plugin.

@mkristian
Copy link
Member Author

@eregon should be possible to restrict the use to pom.xml with release versions in it

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@mkristian mkristian

Labels
None yet
Projects
None yet
Milestone
JRuby 9.0.0.0.rc2
Development

No branches or pull requests
3 participants
@enebo @mkristian @eregon