You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Alexandre Poitras (JIRA)" <ji...@codehaus.org> on 2006/05/18 13:13:41 UTC
[jira] Created: (MRELEASE-111) Add a filtering configuration
element
Add a filtering configuration element
-------------------------------------
Key: MRELEASE-111
URL: http://jira.codehaus.org/browse/MRELEASE-111
Project: Maven 2.x Release Plugin
Type: New Feature
Versions: 2.0-beta-4
Reporter: Alexandre Poitras
Sometimes you don't have a choice but to depends upon a snapshot artifact (critical bug). Right now the release plugin doesn't allow it and I think it's alright but a filtering configuration element would be a nice addition to tell the release plugin when you are ok to go in production with a snapshot dependency that you have throughoutly tested.
--
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: (MRELEASE-111) Add a filtering configuration
element
Posted by "Jerome Lacoste (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-111?page=comments#action_67457 ]
Jerome Lacoste commented on MRELEASE-111:
-----------------------------------------
It appears that his can cause issue. Confer deployed mojo root pom v8 depending on webdav wagon SNAPSHOT... So maybe this shouldn't be allowed and the focus should be on removing the situations that end you up depending on a SNAPSHOT artifacts.
> Add a filtering configuration element
> -------------------------------------
>
> Key: MRELEASE-111
> URL: http://jira.codehaus.org/browse/MRELEASE-111
> Project: Maven 2.x Release Plugin
> Type: New Feature
> Versions: 2.0-beta-4
> Reporter: Alexandre Poitras
>
>
> Sometimes you don't have a choice but to depends upon a snapshot artifact (critical bug). Right now the release plugin doesn't allow it and I think it's alright but a filtering configuration element would be a nice addition to tell the release plugin when you are ok to go in production with a snapshot dependency that you have throughoutly tested.
--
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] Updated: (MRELEASE-111) Add a filtering configuration
element
Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-111?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Arnaud Heritier updated MRELEASE-111:
-------------------------------------
Component/s: prepare
> Add a filtering configuration element
> -------------------------------------
>
> Key: MRELEASE-111
> URL: http://jira.codehaus.org/browse/MRELEASE-111
> Project: Maven 2.x Release Plugin
> Issue Type: New Feature
> Components: prepare
> Affects Versions: 2.0-beta-4
> Reporter: Alexandre Poitras
>
> Sometimes you don't have a choice but to depends upon a snapshot artifact (critical bug). Right now the release plugin doesn't allow it and I think it's alright but a filtering configuration element would be a nice addition to tell the release plugin when you are ok to go in production with a snapshot dependency that you have throughoutly tested.
--
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: (MRELEASE-111) Add a filtering configuration
element
Posted by "Jerome Lacoste (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/MRELEASE-111?page=comments#action_67358 ]
Jerome Lacoste commented on MRELEASE-111:
-----------------------------------------
I like that. The user should perhaps need to specify a particular version of the snapshot artifact, -SNAPSHOT not being accepted. Comments?
> Add a filtering configuration element
> -------------------------------------
>
> Key: MRELEASE-111
> URL: http://jira.codehaus.org/browse/MRELEASE-111
> Project: Maven 2.x Release Plugin
> Type: New Feature
> Versions: 2.0-beta-4
> Reporter: Alexandre Poitras
>
>
> Sometimes you don't have a choice but to depends upon a snapshot artifact (critical bug). Right now the release plugin doesn't allow it and I think it's alright but a filtering configuration element would be a nice addition to tell the release plugin when you are ok to go in production with a snapshot dependency that you have throughoutly tested.
--
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