You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Kalle Korhonen (JIRA)" <ji...@codehaus.org> on 2008/03/13 07:19:28 UTC

[jira] Created: (MRELEASE-333) allowTimestampedSnapshots is not applied to report plugins

allowTimestampedSnapshots is not applied to report plugins
----------------------------------------------------------

                 Key: MRELEASE-333
                 URL: http://jira.codehaus.org/browse/MRELEASE-333
             Project: Maven 2.x Release Plugin
          Issue Type: Bug
    Affects Versions: 2.0-beta-7
         Environment: Any
            Reporter: Kalle Korhonen


Related to already resolved MRELEASE-124. allowTimestampedSnapshots make it possible to force a release with uniquely versioned snapshots as dependencies, but the parameter has no effect on report snapshots dependencies. Looking at the code in the patch it seems the parameter is only applied to straight-up project dependencies. If you are forced to use reports that are only available as snapshots (currently e.g. the dashboard plugin), you are out of luck unless you deploy custom versions of the plugin in your internal repository or disable the reports for the release.

-- 
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-333) allowTimestampedSnapshots is not applied to report plugins

Posted by "Arnaud Heritier (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRELEASE-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Arnaud Heritier updated MRELEASE-333:
-------------------------------------

    Component/s: prepare

> allowTimestampedSnapshots is not applied to report plugins
> ----------------------------------------------------------
>
>                 Key: MRELEASE-333
>                 URL: http://jira.codehaus.org/browse/MRELEASE-333
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.0-beta-7
>         Environment: Any
>            Reporter: Kalle Korhonen
>         Attachments: pom.xml
>
>
> Related to already resolved MRELEASE-124. allowTimestampedSnapshots make it possible to force a release with uniquely versioned snapshots as dependencies, but the parameter has no effect on report snapshots dependencies. Looking at the code in the patch it seems the parameter is only applied to straight-up project dependencies. If you are forced to use reports that are only available as snapshots (currently e.g. the dashboard plugin), you are out of luck unless you deploy custom versions of the plugin in your internal repository or disable the reports for the release.

-- 
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] (MRELEASE-333) allowTimestampedSnapshots is not applied to report plugins

Posted by "Robert Scholte (JIRA)" <ji...@codehaus.org>.
     [ https://jira.codehaus.org/browse/MRELEASE-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Robert Scholte closed MRELEASE-333.
-----------------------------------

    Resolution: Incomplete

No feedback from user, closing it as {{incomplete}}.
                
> allowTimestampedSnapshots is not applied to report plugins
> ----------------------------------------------------------
>
>                 Key: MRELEASE-333
>                 URL: https://jira.codehaus.org/browse/MRELEASE-333
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>          Components: prepare
>    Affects Versions: 2.0-beta-7
>         Environment: Any
>            Reporter: Kalle Korhonen
>         Attachments: pom.xml
>
>
> Related to already resolved MRELEASE-124. allowTimestampedSnapshots make it possible to force a release with uniquely versioned snapshots as dependencies, but the parameter has no effect on report snapshots dependencies. Looking at the code in the patch it seems the parameter is only applied to straight-up project dependencies. If you are forced to use reports that are only available as snapshots (currently e.g. the dashboard plugin), you are out of luck unless you deploy custom versions of the plugin in your internal repository or disable the reports for the release.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira

        

[jira] Updated: (MRELEASE-333) allowTimestampedSnapshots is not applied to report plugins

Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRELEASE-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Bentmann updated MRELEASE-333:
---------------------------------------

    Attachment: pom.xml

I tried to reproduce your issue but failed. The attached POM defines a timestamped version of the Dashboard Plugin and running "mvn release:prepare -DdryRun" is working for me.

Can you provide some more details or a concrete POM that does not work?

> allowTimestampedSnapshots is not applied to report plugins
> ----------------------------------------------------------
>
>                 Key: MRELEASE-333
>                 URL: http://jira.codehaus.org/browse/MRELEASE-333
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0-beta-7
>         Environment: Any
>            Reporter: Kalle Korhonen
>         Attachments: pom.xml
>
>
> Related to already resolved MRELEASE-124. allowTimestampedSnapshots make it possible to force a release with uniquely versioned snapshots as dependencies, but the parameter has no effect on report snapshots dependencies. Looking at the code in the patch it seems the parameter is only applied to straight-up project dependencies. If you are forced to use reports that are only available as snapshots (currently e.g. the dashboard plugin), you are out of luck unless you deploy custom versions of the plugin in your internal repository or disable the reports for the release.

-- 
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-333) allowTimestampedSnapshots is not applied to report plugins

Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRELEASE-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Bentmann updated MRELEASE-333:
---------------------------------------

    Attachment: pom.xml

> allowTimestampedSnapshots is not applied to report plugins
> ----------------------------------------------------------
>
>                 Key: MRELEASE-333
>                 URL: http://jira.codehaus.org/browse/MRELEASE-333
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0-beta-7
>         Environment: Any
>            Reporter: Kalle Korhonen
>         Attachments: pom.xml
>
>
> Related to already resolved MRELEASE-124. allowTimestampedSnapshots make it possible to force a release with uniquely versioned snapshots as dependencies, but the parameter has no effect on report snapshots dependencies. Looking at the code in the patch it seems the parameter is only applied to straight-up project dependencies. If you are forced to use reports that are only available as snapshots (currently e.g. the dashboard plugin), you are out of luck unless you deploy custom versions of the plugin in your internal repository or disable the reports for the release.

-- 
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-333) allowTimestampedSnapshots is not applied to report plugins

Posted by "Benjamin Bentmann (JIRA)" <ji...@codehaus.org>.
     [ http://jira.codehaus.org/browse/MRELEASE-333?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Benjamin Bentmann updated MRELEASE-333:
---------------------------------------

    Attachment:     (was: pom.xml)

> allowTimestampedSnapshots is not applied to report plugins
> ----------------------------------------------------------
>
>                 Key: MRELEASE-333
>                 URL: http://jira.codehaus.org/browse/MRELEASE-333
>             Project: Maven 2.x Release Plugin
>          Issue Type: Bug
>    Affects Versions: 2.0-beta-7
>         Environment: Any
>            Reporter: Kalle Korhonen
>         Attachments: pom.xml
>
>
> Related to already resolved MRELEASE-124. allowTimestampedSnapshots make it possible to force a release with uniquely versioned snapshots as dependencies, but the parameter has no effect on report snapshots dependencies. Looking at the code in the patch it seems the parameter is only applied to straight-up project dependencies. If you are forced to use reports that are only available as snapshots (currently e.g. the dashboard plugin), you are out of luck unless you deploy custom versions of the plugin in your internal repository or disable the reports for the release.

-- 
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