You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Brian Fox (JIRA)" <ji...@codehaus.org> on 2007/11/14 11:10:25 UTC
[jira] Created: (MENFORCER-22) create a rule to check the current
project is not a snapshot
create a rule to check the current project is not a snapshot
------------------------------------------------------------
Key: MENFORCER-22
URL: http://jira.codehaus.org/browse/MENFORCER-22
Project: Maven 2.x Enforcer Plugin
Issue Type: New Feature
Components: Standard Rules
Affects Versions: 1.0-alpha-3
Reporter: Brian Fox
Assignee: Brian Fox
There is already a rule to check that dependencies cannot be a snapshot, create a rule to ensure the current project is not a snapshot.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (MENFORCER-22) create a rule to check the current
project is not a snapshot
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MENFORCER-22?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Brian Fox closed MENFORCER-22.
------------------------------
Resolution: Fixed
Fix Version/s: 1.0
> create a rule to check the current project is not a snapshot
> ------------------------------------------------------------
>
> Key: MENFORCER-22
> URL: http://jira.codehaus.org/browse/MENFORCER-22
> Project: Maven 2.x Enforcer Plugin
> Issue Type: New Feature
> Components: Standard Rules
> Affects Versions: 1.0-alpha-3
> Reporter: Brian Fox
> Assignee: Brian Fox
> Fix For: 1.0
>
>
> There is already a rule to check that dependencies cannot be a snapshot, create a rule to ensure the current project is not a snapshot.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MENFORCER-22) create a rule to check the current
project is not a snapshot
Posted by "Brian Fox (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MENFORCER-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_123276 ]
Brian Fox commented on MENFORCER-22:
------------------------------------
You would normally do this as part of your profile to cut a release since once the project becomes non-snapshot you shouldn't be rebuilding it multiple times.
> create a rule to check the current project is not a snapshot
> ------------------------------------------------------------
>
> Key: MENFORCER-22
> URL: http://jira.codehaus.org/browse/MENFORCER-22
> Project: Maven 2.x Enforcer Plugin
> Issue Type: New Feature
> Components: Standard Rules
> Affects Versions: 1.0-alpha-3
> Reporter: Brian Fox
> Assignee: Brian Fox
> Fix For: 1.0
>
>
> There is already a rule to check that dependencies cannot be a snapshot, create a rule to ensure the current project is not a snapshot.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MENFORCER-22) create a rule to check the current
project is not a snapshot
Posted by "Ben Lidgey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MENFORCER-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_123278 ]
Ben Lidgey commented on MENFORCER-22:
-------------------------------------
Is it possible to activate a profile if the project version is a SNAPSHOT (or not)? I couldn't see anything in the profile docs?
We have a CruiseControl server built that checks out the latest version of a project from the head and builds it, so we would need to activate the profile to check for snapshots if the project version is not a SNAPSHOT.
> create a rule to check the current project is not a snapshot
> ------------------------------------------------------------
>
> Key: MENFORCER-22
> URL: http://jira.codehaus.org/browse/MENFORCER-22
> Project: Maven 2.x Enforcer Plugin
> Issue Type: New Feature
> Components: Standard Rules
> Affects Versions: 1.0-alpha-3
> Reporter: Brian Fox
> Assignee: Brian Fox
> Fix For: 1.0
>
>
> There is already a rule to check that dependencies cannot be a snapshot, create a rule to ensure the current project is not a snapshot.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MENFORCER-22) create a rule to check the current
project is not a snapshot
Posted by "Ben Lidgey (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MENFORCER-22?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_123269 ]
Ben Lidgey commented on MENFORCER-22:
-------------------------------------
We have the scenario where developers use a SNAPSHOT version for the project during development, and depend on other SNAPSHOT artifacts which is fine. We want this setup to pass the build in the CI server.
BUT, when the project version becomes a non-SNAPSHOT version then we want the check to ensure that no dependencies are SNAPSHOTs.
Something like:
|| || Dependency versions || ||
|| || SNAPSHOT || non-SNAPSHOT ||
|| Project version || | |
|| SNAPSHOT | pass | pass |
|| non-SNAPSHOT | fail | pass |
> create a rule to check the current project is not a snapshot
> ------------------------------------------------------------
>
> Key: MENFORCER-22
> URL: http://jira.codehaus.org/browse/MENFORCER-22
> Project: Maven 2.x Enforcer Plugin
> Issue Type: New Feature
> Components: Standard Rules
> Affects Versions: 1.0-alpha-3
> Reporter: Brian Fox
> Assignee: Brian Fox
> Fix For: 1.0
>
>
> There is already a rule to check that dependencies cannot be a snapshot, create a rule to ensure the current project is not a snapshot.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira