[jira] (MPIR-292) On the Modules report, the links to sub-sub-modules are not correctly generated
Anghel Botos created MPIR-292: - Summary: On the Modules report, the links to sub-sub-modules are not correctly generated Key: MPIR-292 URL: https://jira.codehaus.org/browse/MPIR-292 Project: Maven Project Info Reports Plugin Issue Type: Bug Affects Versions: 2.7 Reporter: Anghel Botos Priority: Minor Attachments: FixSubSubModulesLinks.patch, MyProjectSite.zip, MyProject.zip On the Modules report (About project page), the links to sub-sub-modules are not correctly generated. In the attached MyProject.zip file I have the following project structure: project **subProject subSubProject I've ran site and site:deploy, the resulting site is located in MyProjectSite.zip. If you open the index.html you will see that on the About project page, in the table, both the "subProject" and the "subSubProject" are listed as modules, but only the link to the direct child ("subProject") is correct, while the link to the "subSubProject" is incorrect. I've also added a patch that fixes this problem. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] (MDEPLOY-92) When a snapshot is deployed with uniqueVersion=false, its SNAPSHOT dependencies must be forced to timestamp
[ https://jira.codehaus.org/browse/MDEPLOY-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Herve Boutemy updated MDEPLOY-92: - Summary: When a snapshot is deployed with uniqueVersion=false, its SNAPSHOT dependencies must be forced to timestamp (was: When a snapshot is deployed with uniqueVersion=false, it's SNAPSHOT dependencies must be forced to timestamp) > When a snapshot is deployed with uniqueVersion=false, its SNAPSHOT > dependencies must be forced to timestamp > --- > > Key: MDEPLOY-92 > URL: https://jira.codehaus.org/browse/MDEPLOY-92 > Project: Maven Deploy Plugin > Issue Type: Bug >Reporter: nicolas de loof > Labels: scrub-review-started > > use case : > using the release plugin as a SNAPSHOT timestamped version to ensure > reproductibility. > When an incompatible SNAPSHOT of the release-manager is deployed, the plugin > doesn't work anymore : it updated it's SNAPSHOT dependencies. > -> uniqueVersion=false was useless to ensure reproductibility. > The isse is that the plugin POM has a SNAPSHOT dependency. As part of the > deploy process, the SNAPSHOT version SHOULD be forced to current timestamped > version to follow the uniqueVersion expectation. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators For more information on JIRA, see: http://www.atlassian.com/software/jira