[jboss-jira] [JBoss JIRA] (DROOLS-297) The release procedure should validate there are no snapshot dependencies with the enforcer plugin

[Michael Biarnes Kiefer (JIRA)]

    [ https://issues.jboss.org/browse/DROOLS-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12992912#comment-12992912 ] 

Michael Biarnes Kiefer commented on DROOLS-297:
-----------------------------------------------

I added a profile "nonsnapshot" (locally) on kie-parent. When I do a mvn clean install -Dfull -DskipTest -Dnonsnapshot in any project, when there is a SNAPSHOT, the build fails. OK.
I don't see a time-saving here, since during a release, after the project version update I do a find in path for -SNAPSHOT, to find -SNAPSHOTS (if there are any).
If we then execute after version update -Dnonsnapshot, this will be like a second check if there is still a SNAPSHOT.
I don't know if it is worth to add this profile to kie-parent pom?



> The release procedure should validate there are no snapshot dependencies with the enforcer plugin
> -------------------------------------------------------------------------------------------------
>
>                 Key: DROOLS-297
>                 URL: https://issues.jboss.org/browse/DROOLS-297
>             Project: Drools
>          Issue Type: Task
>      Security Level: Public(Everyone can see) 
>            Reporter: Geoffrey De Smet
>            Assignee: Michael Biarnes Kiefer
>
> Apparently, we've been releasing jars which have snapshot dependencies (non-timestamped). For example drools-wb-jcr2vfs-migration-core 6.0.0.CR4 depends on 5.5.1-SNAPSHOT. Why Nexus's validation no longer prevents this is beyond me.
> Anyway, we need to prevent this. Luckily the enforcer plugin has a rule to validate this:
> http://maven.apache.org/enforcer/enforcer-rules/requireReleaseVersion.html
> During normal development this rule shouldn't be active, as jbpm depends on a drools snapshot etc.
> But during a release procedure, it must be executed once. For example, after changing the version and before deploying them. Or as part of the actual deploy build - whatever works best.
> One way would be to put it in the release profile "jboss-release", similar to what the jboss-parent pom does (which we extend):
>   https://github.com/jboss/jboss-parent-pom/blob/master/pom.xml#L700
> But I strongly dislike the use of profiles... 



--
This message was sent by Atlassian JIRA
(v6.2.6#6264)