[jira] (MNG-3472) configuration possibilities to limit size of local repository
[ https://jira.codehaus.org/browse/MNG-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=313164#comment-313164 ] Eric Dalquist commented on MNG-3472: Here is what we are doing on our build server: find /path/to/.m2 -wholename '*SNAPSHOT/*.*' -type f -mtime +1 -print0 | xargs -r -0 rm -v find /path/to/.m2 -type d -empty -print0 | xargs -r -0 rmdir -v That deletes any files in a SNAPSHOT directory older than 1 day and then deletes all empty directories. configuration possibilities to limit size of local repository - Key: MNG-3472 URL: https://jira.codehaus.org/browse/MNG-3472 Project: Maven 2 3 Issue Type: Improvement Components: Settings Affects Versions: 2.0.8 Reporter: manuel aldana it would be great to make repository-size configurable, for instance by setting the maximum number of downloads of a snapshot-version to be kept. thus the explosion of local repository size can be reduced. especially when you are working with many in-house multi-module projects which are marked as snapshots before released , can increase repository size significantly. see mailing-list discussion: http://www.nabble.com/limit-size-of-local-repository%2C-limit-number-of-snapshots-td16147475s177.html -- 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] (MNG-3472) configuration possibilities to limit size of local repository
[
https://jira.codehaus.org/browse/MNG-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=313164#comment-313164
]
Eric Dalquist edited comment on MNG-3472 at 11/8/12 9:55 AM:
-
Here is what we are doing on our build server:
{code}
find /path/to/.m2 -wholename '*SNAPSHOT/*.*' -type f -mtime +1 -print0 | xargs
-r -0 rm -v
find /path/to/.m2 -type d -empty -print0 | xargs -r -0 rmdir -v
{code}
That deletes any files in a SNAPSHOT directory older than 1 day and then
deletes all empty directories.
was (Author: edalquist):
Here is what we are doing on our build server:
find /path/to/.m2 -wholename '*SNAPSHOT/*.*' -type f -mtime +1 -print0 | xargs
-r -0 rm -v
find /path/to/.m2 -type d -empty -print0 | xargs -r -0 rmdir -v
That deletes any files in a SNAPSHOT directory older than 1 day and then
deletes all empty directories.
configuration possibilities to limit size of local repository
-
Key: MNG-3472
URL: https://jira.codehaus.org/browse/MNG-3472
Project: Maven 2 3
Issue Type: Improvement
Components: Settings
Affects Versions: 2.0.8
Reporter: manuel aldana
it would be great to make repository-size configurable, for instance by
setting the maximum number of downloads of a snapshot-version to be kept.
thus the explosion of local repository size can be reduced.
especially when you are working with many in-house multi-module projects
which are marked as snapshots before released , can increase repository size
significantly.
see mailing-list discussion:
http://www.nabble.com/limit-size-of-local-repository%2C-limit-number-of-snapshots-td16147475s177.html
--
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] (MNG-3472) configuration possibilities to limit size of local repository
[ https://jira.codehaus.org/browse/MNG-3472?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=306674#comment-306674 ] Eric Dalquist commented on MNG-3472: It is unfortunate that this issue is marked as won't-fix. We run into this problem all the time and are starting to feel lots of pain around managing local repositories. Having some way to: * Purge all but the X newest snapshots of a version * Purge snapshots where a release exists in the local repo Is really critical, for now we'll be doing this via scripts which I'll try to post back here but of course the danger is the local repository meta data may be left in an invalid state since we'll just be deleting files. configuration possibilities to limit size of local repository - Key: MNG-3472 URL: https://jira.codehaus.org/browse/MNG-3472 Project: Maven 2 3 Issue Type: Improvement Components: Settings Affects Versions: 2.0.8 Reporter: manuel aldana it would be great to make repository-size configurable, for instance by setting the maximum number of downloads of a snapshot-version to be kept. thus the explosion of local repository size can be reduced. especially when you are working with many in-house multi-module projects which are marked as snapshots before released , can increase repository size significantly. see mailing-list discussion: http://www.nabble.com/limit-size-of-local-repository%2C-limit-number-of-snapshots-td16147475s177.html -- 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] (MWAR-274) Add support for mavenFilteringHints
Eric Dalquist created MWAR-274: -- Summary: Add support for mavenFilteringHints Key: MWAR-274 URL: https://jira.codehaus.org/browse/MWAR-274 Project: Maven 2.x WAR Plugin Issue Type: Improvement Components: filtering Affects Versions: 2.1.1 Reporter: Eric Dalquist It would be really handy if the war plugin supported the execution of additional MavenResourcesFiltering instances via the mavenFilteringHints API I'm looking through the maven-war-plugin source right now to see if an approach for this is obvious and I'll supply a patch if I figured something out. -- 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: (MSITE-484) Support adding and overriding report plugins in new maven-site-plugin 3.x reportPlugins configuration format
[
https://jira.codehaus.org/browse/MSITE-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Dalquist updated MSITE-484:
Attachment: MSITE-484.patch
Updated patch, replaces mergePolicy. prefix with merge: xml namespace. In my
testing you can specify whatever you want for the namespace URI since I don't
actually have an XSD to go with it, I used
xmlns:merge=http://maven.apache.org/plugin-merge; in my test pom.
This patch should be complete, all integration tests pass and the copyright
headers are correct. I do have an Apache ICLA on file and am an active
committer in the portals project: http://people.apache.org/committer-index.html
I would love this to become a core feature of Maven itself for merging plugin
configurations. I'm not sure where to go with getting that requested as a
feature. I'm hoping that this this seems to affect the site plugin more than
others it would be faster to get the fix in here so it could be used as soon as
possible.
Support adding and overriding report plugins in new maven-site-plugin 3.x
reportPlugins configuration format
Key: MSITE-484
URL: https://jira.codehaus.org/browse/MSITE-484
Project: Maven 2.x and 3.x Site Plugin
Issue Type: Bug
Components: inheritance, Maven 3
Affects Versions: 3.0-beta-1, 3.0-beta-2, 3.0-beta-3
Environment: 3.0-beta-1-SNAPSHOT
Reporter: Michael Pilquist
Assignee: Olivier Lamy
Fix For: 3.1
Attachments: MSITE-484.patch, MSITE-484.patch,
site-cfg-inheritance.zip
When using the new configuration format for reportPlugins, it appears that
there's no way to:
- Add a report plugin to a submodule
- Override the configuration of a report plugin in a submodule
Using the old reporting section, both of these use cases were supported.
For large, multi-module builds, it is problematic having to respecify all
reporting plugins in any submodule pom that needs to either add an additional
reporting plugin or change the configuration of a reporting plugin.
Attached is a sample project that has a parent POM configured with
project-info-reports and javadoc plugin and a submodule configured with jxr
plugin and javadoc plugin. The relevant output is here:
{code}
[INFO]
[INFO] Building parent 1.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.3:clean (default-clean) @ parent ---
[INFO] Deleting file set: /Users/mpilquist/Downloads/site-parent-issue/target
(included: [**], excluded: [])
[INFO]
[INFO] --- maven-site-plugin:3.0-beta-1-SNAPSHOT:site (default-site) @ parent
---
[INFO] configuring reportPlugin
org.apache.maven.plugins:maven-project-info-reports-plugin:2.2
[INFO] configuring reportPlugin
org.apache.maven.plugins:maven-javadoc-plugin:2.6.1
...
[INFO]
[INFO] Building parent-usage-test 1.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.3:clean (default-clean) @ parent-usage-test
---
[INFO]
[INFO] --- maven-site-plugin:3.0-beta-1-SNAPSHOT:site (default-site) @
parent-usage-test ---
[INFO] configuring reportPlugin org.apache.maven.plugins:maven-jxr-plugin:2.1
[INFO] configuring reportPlugin
org.apache.maven.plugins:maven-javadoc-plugin:2.6.1
{code}
Looking at the maven-site-plugin code, it appears the the reportPlugins
parameter is just a regular array parameter. AFAIK, there's no way to merge
list configuration items. Other plugins have worked around this by defining
additional mojo parameters (e.g., maven-eclipse-plugin and buildCommands /
additionalBuildCommands --
http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html).
This isn't the most flexible option though as it only solves 1 level
inheritance.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (MSITE-484) Support adding and overriding report plugins in new maven-site-plugin 3.x reportPlugins configuration format
[
https://jira.codehaus.org/browse/MSITE-484?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Dalquist updated MSITE-484:
Attachment: MSITE-484.patch
This patch provides robust support for merging PlexusConfiguration objects.
I've included a unit test which demonstrates the functionality and have tested
it locally with various plugin overlays with great success.
For example if the parent pom's maven-site-plugin is:
{code:xml}
plugin
artifactIdmaven-site-plugin/artifactId
configuration
reportPlugins
plugin
artifactIdmaven-javadoc-plugin/artifactId
version2.8/version
configuration
links
linkhttp://java.sun.com/javase/6/docs/api//link
linkhttp://java.sun.com/javaee/5/docs/api//link
/links
source1.6/source
/configuration
/plugin
/reportPlugins
/configuration
/plugin
{code}
And the child project pom's maven-site-plugin is:
{code:xml}
plugin
artifactIdmaven-site-plugin/artifactId
configuration
defaultMergePolicyMERGE/defaultMergePolicy
reportPlugins combine.children=append
plugin
artifactIdmaven-javadoc-plugin/artifactId
configuration
links mergePolicy.children=BOTH
mergePolicy.removeDuplicates=true
linkhttp://static.springsource.org/spring/docs/3.0.x/api//link
linkhttp://ehcache.org/apidocs//link
linkhttp://aopalliance.sourceforge.net/doc//link
linkhttp://java.sun.com/javase/6/docs/api//link
/links
maxmemory768m/maxmemory
/configuration
/plugin
/reportPlugins
/configuration
/plugin
{code:xml}
The runtime effective result is:
{code:xml}
plugin
artifactIdmaven-site-plugin/artifactId
configuration
defaultMergePolicyMERGE/defaultMergePolicy
reportPlugins combine.children=append
plugin
artifactIdmaven-javadoc-plugin/artifactId
configuration
links mergePolicy.children=BOTH
mergePolicy.removeDuplicates=true
linkhttp://static.springsource.org/spring/docs/3.0.x/api//link
linkhttp://ehcache.org/apidocs//link
linkhttp://aopalliance.sourceforge.net/doc//link
linkhttp://java.sun.com/javase/6/docs/api//link
linkhttp://java.sun.com/javaee/5/docs/api//link
/links
source1.6/source
maxmemory768m/maxmemory
/configuration
/plugin
/reportPlugins
/configuration
/plugin
{code}
Support adding and overriding report plugins in new maven-site-plugin 3.x
reportPlugins configuration format
Key: MSITE-484
URL: https://jira.codehaus.org/browse/MSITE-484
Project: Maven 2.x and 3.x Site Plugin
Issue Type: Bug
Components: inheritance, Maven 3
Affects Versions: 3.0-beta-1, 3.0-beta-2, 3.0-beta-3
Environment: 3.0-beta-1-SNAPSHOT
Reporter: Michael Pilquist
Assignee: Olivier Lamy
Fix For: 3.1
Attachments: MSITE-484.patch, site-cfg-inheritance.zip
When using the new configuration format for reportPlugins, it appears that
there's no way to:
- Add a report plugin to a submodule
- Override the configuration of a report plugin in a submodule
Using the old reporting section, both of these use cases were supported.
For large, multi-module builds, it is problematic having to respecify all
reporting plugins in any submodule pom that needs to either add an additional
reporting plugin or change the configuration of a reporting plugin.
Attached is a sample project that has a parent POM configured with
project-info-reports and javadoc plugin and a submodule configured with jxr
plugin and javadoc plugin. The relevant output is here:
{code}
[INFO]
[INFO] Building parent 1.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.3:clean (default-clean) @ parent ---
[INFO] Deleting file set: /Users/mpilquist/Downloads/site-parent-issue/target
(included: [**], excluded: [])
[INFO]
[INFO] --- maven-site-plugin:3.0-beta-1-SNAPSHOT:site (default-site) @ parent
---
[INFO] configuring reportPlugin
org.apache.maven.plugins:maven-project-info-reports-plugin:2.2
[INFO] configuring reportPlugin
org.apache.maven.plugins:maven-javadoc-plugin:2.6.1
...
[INFO]
[INFO] Building parent-usage-test 1.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.3:clean (default-clean) @ parent-usage-test
---
[INFO]
[INFO] ---
[jira] Issue Comment Edited: (MSITE-484) Support adding and overriding report plugins in new maven-site-plugin 3.x reportPlugins configuration format
[
https://jira.codehaus.org/browse/MSITE-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=279696#comment-279696
]
Eric Dalquist edited comment on MSITE-484 at 9/22/11 3:25 PM:
--
This patch provides robust support for merging PlexusConfiguration objects.
I've included a unit test which demonstrates the functionality and have tested
it locally with various plugin overlays with great success.
For example if the parent pom's maven-site-plugin is:
{code:xml}
plugin
artifactIdmaven-site-plugin/artifactId
configuration
reportPlugins
plugin
artifactIdmaven-javadoc-plugin/artifactId
version2.8/version
configuration
links
linkhttp://java.sun.com/javase/6/docs/api//link
linkhttp://java.sun.com/javaee/5/docs/api//link
/links
source1.6/source
/configuration
/plugin
/reportPlugins
/configuration
/plugin
{code}
And the child project pom's maven-site-plugin is:
{code:xml}
plugin
artifactIdmaven-site-plugin/artifactId
configuration
defaultMergePolicyMERGE/defaultMergePolicy
reportPlugins combine.children=append
plugin
artifactIdmaven-javadoc-plugin/artifactId
configuration
links mergePolicy.children=BOTH
mergePolicy.removeDuplicates=true
linkhttp://static.springsource.org/spring/docs/3.0.x/api//link
linkhttp://ehcache.org/apidocs//link
linkhttp://aopalliance.sourceforge.net/doc//link
linkhttp://java.sun.com/javase/6/docs/api//link
/links
maxmemory768m/maxmemory
/configuration
/plugin
/reportPlugins
/configuration
/plugin
{code}
The runtime effective result is:
{code:xml}
plugin
artifactIdmaven-site-plugin/artifactId
configuration
defaultMergePolicyMERGE/defaultMergePolicy
reportPlugins combine.children=append
plugin
artifactIdmaven-javadoc-plugin/artifactId
configuration
links mergePolicy.children=BOTH
mergePolicy.removeDuplicates=true
linkhttp://static.springsource.org/spring/docs/3.0.x/api//link
linkhttp://ehcache.org/apidocs//link
linkhttp://aopalliance.sourceforge.net/doc//link
linkhttp://java.sun.com/javase/6/docs/api//link
linkhttp://java.sun.com/javaee/5/docs/api//link
/links
source1.6/source
maxmemory768m/maxmemory
/configuration
/plugin
/reportPlugins
/configuration
/plugin
{code}
was (Author: edalquist):
This patch provides robust support for merging PlexusConfiguration objects.
I've included a unit test which demonstrates the functionality and have tested
it locally with various plugin overlays with great success.
For example if the parent pom's maven-site-plugin is:
{code:xml}
plugin
artifactIdmaven-site-plugin/artifactId
configuration
reportPlugins
plugin
artifactIdmaven-javadoc-plugin/artifactId
version2.8/version
configuration
links
linkhttp://java.sun.com/javase/6/docs/api//link
linkhttp://java.sun.com/javaee/5/docs/api//link
/links
source1.6/source
/configuration
/plugin
/reportPlugins
/configuration
/plugin
{code}
And the child project pom's maven-site-plugin is:
{code:xml}
plugin
artifactIdmaven-site-plugin/artifactId
configuration
defaultMergePolicyMERGE/defaultMergePolicy
reportPlugins combine.children=append
plugin
artifactIdmaven-javadoc-plugin/artifactId
configuration
links mergePolicy.children=BOTH
mergePolicy.removeDuplicates=true
linkhttp://static.springsource.org/spring/docs/3.0.x/api//link
linkhttp://ehcache.org/apidocs//link
linkhttp://aopalliance.sourceforge.net/doc//link
linkhttp://java.sun.com/javase/6/docs/api//link
/links
maxmemory768m/maxmemory
/configuration
/plugin
/reportPlugins
/configuration
/plugin
{code:xml}
The runtime effective result is:
{code:xml}
plugin
artifactIdmaven-site-plugin/artifactId
configuration
defaultMergePolicyMERGE/defaultMergePolicy
reportPlugins combine.children=append
plugin
artifactIdmaven-javadoc-plugin/artifactId
configuration
links mergePolicy.children=BOTH
mergePolicy.removeDuplicates=true
linkhttp://static.springsource.org/spring/docs/3.0.x/api//link
linkhttp://ehcache.org/apidocs//link
linkhttp://aopalliance.sourceforge.net/doc//link
linkhttp://java.sun.com/javase/6/docs/api//link
linkhttp://java.sun.com/javaee/5/docs/api//link
/links
source1.6/source
maxmemory768m/maxmemory
/configuration
/plugin
/reportPlugins
/configuration
/plugin
[jira] Issue Comment Edited: (MSITE-484) Support adding and overriding report plugins in new maven-site-plugin 3.x reportPlugins configuration format
[
https://jira.codehaus.org/browse/MSITE-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=279696#comment-279696
]
Eric Dalquist edited comment on MSITE-484 at 9/22/11 3:26 PM:
--
This patch (against r1170684) provides robust support for merging
PlexusConfiguration objects. I've included a unit test which demonstrates the
functionality and have tested it locally with various plugin overlays with
great success.
For example if the parent pom's maven-site-plugin is:
{code:xml}
plugin
artifactIdmaven-site-plugin/artifactId
configuration
reportPlugins
plugin
artifactIdmaven-javadoc-plugin/artifactId
version2.8/version
configuration
links
linkhttp://java.sun.com/javase/6/docs/api//link
linkhttp://java.sun.com/javaee/5/docs/api//link
/links
source1.6/source
/configuration
/plugin
/reportPlugins
/configuration
/plugin
{code}
And the child project pom's maven-site-plugin is:
{code:xml}
plugin
artifactIdmaven-site-plugin/artifactId
configuration
defaultMergePolicyMERGE/defaultMergePolicy
reportPlugins combine.children=append
plugin
artifactIdmaven-javadoc-plugin/artifactId
configuration
links mergePolicy.children=BOTH
mergePolicy.removeDuplicates=true
linkhttp://static.springsource.org/spring/docs/3.0.x/api//link
linkhttp://ehcache.org/apidocs//link
linkhttp://aopalliance.sourceforge.net/doc//link
linkhttp://java.sun.com/javase/6/docs/api//link
/links
maxmemory768m/maxmemory
/configuration
/plugin
/reportPlugins
/configuration
/plugin
{code}
The runtime effective result is:
{code:xml}
plugin
artifactIdmaven-site-plugin/artifactId
configuration
defaultMergePolicyMERGE/defaultMergePolicy
reportPlugins combine.children=append
plugin
artifactIdmaven-javadoc-plugin/artifactId
configuration
links mergePolicy.children=BOTH
mergePolicy.removeDuplicates=true
linkhttp://static.springsource.org/spring/docs/3.0.x/api//link
linkhttp://ehcache.org/apidocs//link
linkhttp://aopalliance.sourceforge.net/doc//link
linkhttp://java.sun.com/javase/6/docs/api//link
linkhttp://java.sun.com/javaee/5/docs/api//link
/links
source1.6/source
maxmemory768m/maxmemory
/configuration
/plugin
/reportPlugins
/configuration
/plugin
{code}
was (Author: edalquist):
This patch provides robust support for merging PlexusConfiguration objects.
I've included a unit test which demonstrates the functionality and have tested
it locally with various plugin overlays with great success.
For example if the parent pom's maven-site-plugin is:
{code:xml}
plugin
artifactIdmaven-site-plugin/artifactId
configuration
reportPlugins
plugin
artifactIdmaven-javadoc-plugin/artifactId
version2.8/version
configuration
links
linkhttp://java.sun.com/javase/6/docs/api//link
linkhttp://java.sun.com/javaee/5/docs/api//link
/links
source1.6/source
/configuration
/plugin
/reportPlugins
/configuration
/plugin
{code}
And the child project pom's maven-site-plugin is:
{code:xml}
plugin
artifactIdmaven-site-plugin/artifactId
configuration
defaultMergePolicyMERGE/defaultMergePolicy
reportPlugins combine.children=append
plugin
artifactIdmaven-javadoc-plugin/artifactId
configuration
links mergePolicy.children=BOTH
mergePolicy.removeDuplicates=true
linkhttp://static.springsource.org/spring/docs/3.0.x/api//link
linkhttp://ehcache.org/apidocs//link
linkhttp://aopalliance.sourceforge.net/doc//link
linkhttp://java.sun.com/javase/6/docs/api//link
/links
maxmemory768m/maxmemory
/configuration
/plugin
/reportPlugins
/configuration
/plugin
{code}
The runtime effective result is:
{code:xml}
plugin
artifactIdmaven-site-plugin/artifactId
configuration
defaultMergePolicyMERGE/defaultMergePolicy
reportPlugins combine.children=append
plugin
artifactIdmaven-javadoc-plugin/artifactId
configuration
links mergePolicy.children=BOTH
mergePolicy.removeDuplicates=true
linkhttp://static.springsource.org/spring/docs/3.0.x/api//link
linkhttp://ehcache.org/apidocs//link
linkhttp://aopalliance.sourceforge.net/doc//link
linkhttp://java.sun.com/javase/6/docs/api//link
linkhttp://java.sun.com/javaee/5/docs/api//link
/links
source1.6/source
maxmemory768m/maxmemory
/configuration
/plugin
/reportPlugins
[jira] Commented: (MSITE-484) Support adding and overriding report plugins in new maven-site-plugin 3.x reportPlugins configuration format
[
https://jira.codehaus.org/browse/MSITE-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=279697#comment-279697
]
Eric Dalquist commented on MSITE-484:
-
Note that I tried to implement this feature in a way such that it could be used
by any plugin. It operates on the PlexusConfiguration interface and the merging
logic has no direct ties to the maven-site-plugin
Support adding and overriding report plugins in new maven-site-plugin 3.x
reportPlugins configuration format
Key: MSITE-484
URL: https://jira.codehaus.org/browse/MSITE-484
Project: Maven 2.x and 3.x Site Plugin
Issue Type: Bug
Components: inheritance, Maven 3
Affects Versions: 3.0-beta-1, 3.0-beta-2, 3.0-beta-3
Environment: 3.0-beta-1-SNAPSHOT
Reporter: Michael Pilquist
Assignee: Olivier Lamy
Fix For: 3.1
Attachments: MSITE-484.patch, site-cfg-inheritance.zip
When using the new configuration format for reportPlugins, it appears that
there's no way to:
- Add a report plugin to a submodule
- Override the configuration of a report plugin in a submodule
Using the old reporting section, both of these use cases were supported.
For large, multi-module builds, it is problematic having to respecify all
reporting plugins in any submodule pom that needs to either add an additional
reporting plugin or change the configuration of a reporting plugin.
Attached is a sample project that has a parent POM configured with
project-info-reports and javadoc plugin and a submodule configured with jxr
plugin and javadoc plugin. The relevant output is here:
{code}
[INFO]
[INFO] Building parent 1.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.3:clean (default-clean) @ parent ---
[INFO] Deleting file set: /Users/mpilquist/Downloads/site-parent-issue/target
(included: [**], excluded: [])
[INFO]
[INFO] --- maven-site-plugin:3.0-beta-1-SNAPSHOT:site (default-site) @ parent
---
[INFO] configuring reportPlugin
org.apache.maven.plugins:maven-project-info-reports-plugin:2.2
[INFO] configuring reportPlugin
org.apache.maven.plugins:maven-javadoc-plugin:2.6.1
...
[INFO]
[INFO] Building parent-usage-test 1.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.3:clean (default-clean) @ parent-usage-test
---
[INFO]
[INFO] --- maven-site-plugin:3.0-beta-1-SNAPSHOT:site (default-site) @
parent-usage-test ---
[INFO] configuring reportPlugin org.apache.maven.plugins:maven-jxr-plugin:2.1
[INFO] configuring reportPlugin
org.apache.maven.plugins:maven-javadoc-plugin:2.6.1
{code}
Looking at the maven-site-plugin code, it appears the the reportPlugins
parameter is just a regular array parameter. AFAIK, there's no way to merge
list configuration items. Other plugins have worked around this by defining
additional mojo parameters (e.g., maven-eclipse-plugin and buildCommands /
additionalBuildCommands --
http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html).
This isn't the most flexible option though as it only solves 1 level
inheritance.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-484) Support adding and overriding report plugins in new maven-site-plugin 3.x reportPlugins configuration format
[
https://jira.codehaus.org/browse/MSITE-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=279703#comment-279703
]
Eric Dalquist commented on MSITE-484:
-
I just realized the patch is incomplete, I'll get the final version posted
tomorrow.
Support adding and overriding report plugins in new maven-site-plugin 3.x
reportPlugins configuration format
Key: MSITE-484
URL: https://jira.codehaus.org/browse/MSITE-484
Project: Maven 2.x and 3.x Site Plugin
Issue Type: Bug
Components: inheritance, Maven 3
Affects Versions: 3.0-beta-1, 3.0-beta-2, 3.0-beta-3
Environment: 3.0-beta-1-SNAPSHOT
Reporter: Michael Pilquist
Assignee: Olivier Lamy
Fix For: 3.1
Attachments: MSITE-484.patch, site-cfg-inheritance.zip
When using the new configuration format for reportPlugins, it appears that
there's no way to:
- Add a report plugin to a submodule
- Override the configuration of a report plugin in a submodule
Using the old reporting section, both of these use cases were supported.
For large, multi-module builds, it is problematic having to respecify all
reporting plugins in any submodule pom that needs to either add an additional
reporting plugin or change the configuration of a reporting plugin.
Attached is a sample project that has a parent POM configured with
project-info-reports and javadoc plugin and a submodule configured with jxr
plugin and javadoc plugin. The relevant output is here:
{code}
[INFO]
[INFO] Building parent 1.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.3:clean (default-clean) @ parent ---
[INFO] Deleting file set: /Users/mpilquist/Downloads/site-parent-issue/target
(included: [**], excluded: [])
[INFO]
[INFO] --- maven-site-plugin:3.0-beta-1-SNAPSHOT:site (default-site) @ parent
---
[INFO] configuring reportPlugin
org.apache.maven.plugins:maven-project-info-reports-plugin:2.2
[INFO] configuring reportPlugin
org.apache.maven.plugins:maven-javadoc-plugin:2.6.1
...
[INFO]
[INFO] Building parent-usage-test 1.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.3:clean (default-clean) @ parent-usage-test
---
[INFO]
[INFO] --- maven-site-plugin:3.0-beta-1-SNAPSHOT:site (default-site) @
parent-usage-test ---
[INFO] configuring reportPlugin org.apache.maven.plugins:maven-jxr-plugin:2.1
[INFO] configuring reportPlugin
org.apache.maven.plugins:maven-javadoc-plugin:2.6.1
{code}
Looking at the maven-site-plugin code, it appears the the reportPlugins
parameter is just a regular array parameter. AFAIK, there's no way to merge
list configuration items. Other plugins have worked around this by defining
additional mojo parameters (e.g., maven-eclipse-plugin and buildCommands /
additionalBuildCommands --
http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html).
This isn't the most flexible option though as it only solves 1 level
inheritance.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-484) Support adding and overriding report plugins in new maven-site-plugin 3.x reportPlugins configuration format
[
https://jira.codehaus.org/browse/MSITE-484?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=279426#comment-279426
]
Eric Dalquist commented on MSITE-484:
-
Just a note that this affects the 3.0 release of the plugin as well. Perhaps
until the Maven core modifications are done the logic in the maven-site-plugin
that handles the reportPlugins could be made configurable in the situation
where the same reportPlugin groupId artifactId exist.
Perhaps something like:
{code:xml}
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-site-plugin/artifactId
versionversion/version
configuration
duplicatePluginPolicyUSE_LAST/duplicatePluginPolicy
reportPlugins combine.children=append
{code}
The duplicatePluginPolicy option could be an enum with USE_FIRST, USE_LAST,
USE_BOTH options, allowing the site plugin to know what to do if there are
multiple plugins with the same groupId:artifactId in the list. This would at
least allow for overrides of a single plugin without having to list every
plugin the parent defines.
Support adding and overriding report plugins in new maven-site-plugin 3.x
reportPlugins configuration format
Key: MSITE-484
URL: https://jira.codehaus.org/browse/MSITE-484
Project: Maven 2.x and 3.x Site Plugin
Issue Type: Bug
Components: inheritance, Maven 3
Affects Versions: 3.0-beta-1, 3.0-beta-2, 3.0-beta-3
Environment: 3.0-beta-1-SNAPSHOT
Reporter: Michael Pilquist
Assignee: Olivier Lamy
Fix For: 3.1
Attachments: site-cfg-inheritance.zip
When using the new configuration format for reportPlugins, it appears that
there's no way to:
- Add a report plugin to a submodule
- Override the configuration of a report plugin in a submodule
Using the old reporting section, both of these use cases were supported.
For large, multi-module builds, it is problematic having to respecify all
reporting plugins in any submodule pom that needs to either add an additional
reporting plugin or change the configuration of a reporting plugin.
Attached is a sample project that has a parent POM configured with
project-info-reports and javadoc plugin and a submodule configured with jxr
plugin and javadoc plugin. The relevant output is here:
{code}
[INFO]
[INFO] Building parent 1.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.3:clean (default-clean) @ parent ---
[INFO] Deleting file set: /Users/mpilquist/Downloads/site-parent-issue/target
(included: [**], excluded: [])
[INFO]
[INFO] --- maven-site-plugin:3.0-beta-1-SNAPSHOT:site (default-site) @ parent
---
[INFO] configuring reportPlugin
org.apache.maven.plugins:maven-project-info-reports-plugin:2.2
[INFO] configuring reportPlugin
org.apache.maven.plugins:maven-javadoc-plugin:2.6.1
...
[INFO]
[INFO] Building parent-usage-test 1.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-clean-plugin:2.3:clean (default-clean) @ parent-usage-test
---
[INFO]
[INFO] --- maven-site-plugin:3.0-beta-1-SNAPSHOT:site (default-site) @
parent-usage-test ---
[INFO] configuring reportPlugin org.apache.maven.plugins:maven-jxr-plugin:2.1
[INFO] configuring reportPlugin
org.apache.maven.plugins:maven-javadoc-plugin:2.6.1
{code}
Looking at the maven-site-plugin code, it appears the the reportPlugins
parameter is just a regular array parameter. AFAIK, there's no way to merge
list configuration items. Other plugins have worked around this by defining
additional mojo parameters (e.g., maven-eclipse-plugin and buildCommands /
additionalBuildCommands --
http://maven.apache.org/plugins/maven-eclipse-plugin/eclipse-mojo.html).
This isn't the most flexible option though as it only solves 1 level
inheritance.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (MSITE-276) Links on Modules are completely broken on site:stage
[ http://jira.codehaus.org/browse/MSITE-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_119608 ] Eric Dalquist commented on MSITE-276: - I see this problem as well. Module links generated by site:stage and site-deploy are broken. Reverting to 2.0-beta-5 solves the issue: Add the following plugin to the build in your root POM plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-site-plugin/artifactId version2.0-beta-5/version /plugin Links on Modules are completely broken on site:stage Key: MSITE-276 URL: http://jira.codehaus.org/browse/MSITE-276 Project: Maven 2.x Site Plugin Issue Type: Bug Affects Versions: 2.0-beta-6 Reporter: Jörg Hohwiller The latest maven-site-plugin 2.0-beta-6 seems to to introduce a new bug that was NOT present in 2.0-beta-5: Now all my modules point to the same url which is ../../opt/project/build/development/projects/../dummyhost.de Something goes very wrong here: 1. The link should not contain pathnames specific for the environment where it was build (/opt/project/build/development/projects) nor the hostname and path of the distributionManagement. 2. The modulename itself is totally lost and all module-links in the menu have the same href Whatever has happend here, made it a lot worse. The site is now totally unuseable. It seems that only mvn site was tested before the 2.0-beta-6 was released. Multimodule-Builds need to be tested with site:stage or site:deploy. -- 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: (MCLOVER-71) Cannot resolve license file
[ http://jira.codehaus.org/browse/MCLOVER-71?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Eric Dalquist updated MCLOVER-71: - Attachment: MavenLoader_24.diff This is a slightly modified version of the already attached patch that is against the 2.4 tagged code. I have tested this patch and it works great. Is there any chance of getting a 2.4.1 cut that includes this patch so that we can include the license file in a parent project? Cannot resolve license file --- Key: MCLOVER-71 URL: http://jira.codehaus.org/browse/MCLOVER-71 Project: Maven 2.x Clover Plugin Issue Type: Bug Affects Versions: 2.4 Reporter: Bryan Madsen Attachments: MavenLoader_24.diff, MCLOVER-71.diff, MCLOVER-71.diff The license file cannot be found when the license location is a URL. This works with version 2.3. [INFO] [clover:instrumentInternal] [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Failed to load license file [http://scm.apparch.cerner.corp/svn/apparch/licenses/clover.license] Embedded error: Could not find resource 'http://scm.apparch.cerner.corp/svn/apparch/licenses/clover.license'. [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Failed to load license file [http://scm.apparch.cerner.corp/svn/apparch/licenses/clover.license] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:564) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:480) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkProjectLifecycle(DefaultLifecycleExecutor.java:896) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.forkLifecycle(DefaultLifecycleExecutor.java:739) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:510) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoal(DefaultLifecycleExecutor.java:493) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:463) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:311) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:278) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:143) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:330) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:123) at org.apache.maven.cli.MavenCli.main(MavenCli.java:272) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Failed to load license file [http://scm.apparch.cerner.corp/svn/apparch/licenses/clover.license] at org.apache.maven.plugin.clover.internal.AbstractCloverMojo.registerLicenseFile(AbstractCloverMojo.java:164) at org.apache.maven.plugin.clover.internal.AbstractCloverMojo.registerLicenseFile(AbstractCloverMojo.java:134) at org.apache.maven.plugin.clover.internal.AbstractCloverMojo.execute(AbstractCloverMojo.java:119) at org.apache.maven.plugin.clover.CloverInstrumentInternalMojo.execute(CloverInstrumentInternalMojo.java:132) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:420) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:539) ... 20 more Caused by: org.codehaus.plexus.resource.loader.ResourceNotFoundException: Could not find resource 'http://scm.apparch.cerner.corp/svn/apparch/licenses/clover.license'. at org.codehaus.plexus.resource.DefaultResourceManager.getResourceAsInputStream(DefaultResourceManager.java:91) at org.codehaus.plexus.resource.DefaultResourceManager.getResourceAsFile(DefaultResourceManager.java:117) at
