[jira] Closed: (MPLUGIN-156) Stabilize ordering of configuration and requirements in generated plugin descriptor
[ http://jira.codehaus.org/browse/MPLUGIN-156?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MPLUGIN-156. - Assignee: Benjamin Bentmann Resolution: Fixed Fix Version/s: 2.5.1 Done in [r800623|http://svn.apache.org/viewvc?view=rev&revision=800623]. > Stabilize ordering of configuration and requirements in generated plugin > descriptor > --- > > Key: MPLUGIN-156 > URL: http://jira.codehaus.org/browse/MPLUGIN-156 > Project: Maven 2.x Plugin Tools > Issue Type: Task > Components: API, Plugin Plugin >Affects Versions: 2.5 >Reporter: Benjamin Bentmann >Assignee: Benjamin Bentmann >Priority: Minor > Fix For: 2.5.1 > > > Just came across an issue (MJAVADOC-251) where the order in which plugin > configuration was injected into a mojo was crucial. While plugins should not > rely on any particular ordering, the plugin descriptor should at least > provide a stable ordering so that any order related effects can be observed > independently of the JVM. -- 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] Created: (MPLUGIN-156) Stabilize ordering of configuration and requirements in generated plugin descriptor
Stabilize ordering of configuration and requirements in generated plugin descriptor --- Key: MPLUGIN-156 URL: http://jira.codehaus.org/browse/MPLUGIN-156 Project: Maven 2.x Plugin Tools Issue Type: Task Components: API, Plugin Plugin Affects Versions: 2.5 Reporter: Benjamin Bentmann Priority: Minor Just came across an issue (MJAVADOC-251) where the order in which plugin configuration was injected into a mojo was crucial. While plugins should not rely on any particular ordering, the plugin descriptor should at least provide a stable ordering so that any order related effects can be observed independently of the JVM. -- 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: (MJAVADOC-251) Configuration of javadoc:javadoc fails with NPE upon disadvantageous order of config injection
[
http://jira.codehaus.org/browse/MJAVADOC-251?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Benjamin Bentmann closed MJAVADOC-251.
--
Assignee: Benjamin Bentmann
Resolution: Fixed
Fix Version/s: 2.6.1
Fixed in [r800618|http://svn.apache.org/viewvc?view=rev&revision=800618].
> Configuration of javadoc:javadoc fails with NPE upon disadvantageous order of
> config injection
> --
>
> Key: MJAVADOC-251
> URL: http://jira.codehaus.org/browse/MJAVADOC-251
> Project: Maven 2.x Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.6
>Reporter: Benjamin Bentmann
>Assignee: Benjamin Bentmann
>Priority: Critical
> Fix For: 2.6.1
>
>
> Compare these two logs from Maven 3.x
> {noformat}
> [DEBUG] Configuring mojo
> 'org.apache.maven.plugins:maven-javadoc-plugin:2.5:javadoc' with basic
> configurator -->
> [DEBUG] (f) nosince = false
> [DEBUG] (f) use = true
> [DEBUG] (f) bootclasspathArtifacts = []
> [DEBUG] (f) links = []
> [DEBUG] (f) encoding = UTF-8
> [DEBUG] (f) aggregate = false
> [DEBUG] (f) tags = []
> [DEBUG] (f) isOffline = false
> [DEBUG] (f) useStandardDocletOptions = true
> [DEBUG] (f) taglets = []
> [DEBUG] (f) doctitle = Maven Ant Plugin 2.3-SNAPSHOT API
> [DEBUG] (f) resourcesArtifacts = []
> [DEBUG] (s) reportOutputDirectory =
> M:\maven\plugins\maven-ant-plugin\target\site\apidocs
> Unable to parse the created DOM for plugin configuration
> org.apache.maven.plugin.PluginConfigurationException: Unable to parse the
> created DOM for plugin configuration
> at
> org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(DefaultPluginManager.java:611)
> at
> org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:564)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:336)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:281)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:208)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:181)
> at
> org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:467)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:163)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:56)
> 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:597)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351)
> Caused by:
> org.codehaus.plexus.component.configurator.ComponentConfigurationException:
> Setter
> org.apache.maven.plugin.javadoc.JavadocReport.setReportOutputDirectory(
> java.lang.Class )
> threw exception when called with parameter
> 'M:\maven\plugins\maven-ant-plugin\target\site\apidocs': null
> at
> org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.setValueUsingSetter(ComponentValueSetter.java:204)
> at
> org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.configure(ComponentValueSetter.java:225)
> at
> org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:140)
> at
> org.codehaus.plexus.component.configurator.BasicComponentConfigurator.configureComponent(BasicComponentConfigurator.java:58)
> at
> org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(DefaultPluginManager.java:605)
> ... 16 more
> Caused by: java.lang.reflect.InvocationTargetException
> 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:597)
> at
> org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.setValueUsingSetter(ComponentValueSetter.java:191)
> ... 20 more
> Caused by: java.lang.NullPointerException
> at java.lang
[jira] Created: (MJAVADOC-251) Configuration of javadoc:javadoc fails with NPE upon disadvantageous order of config injection
Configuration of javadoc:javadoc fails with NPE upon disadvantageous order of
config injection
--
Key: MJAVADOC-251
URL: http://jira.codehaus.org/browse/MJAVADOC-251
Project: Maven 2.x Javadoc Plugin
Issue Type: Bug
Affects Versions: 2.6
Reporter: Benjamin Bentmann
Priority: Critical
Compare these two logs from Maven 3.x
{noformat}
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-javadoc-plugin:2.5:javadoc' with basic
configurator -->
[DEBUG] (f) nosince = false
[DEBUG] (f) use = true
[DEBUG] (f) bootclasspathArtifacts = []
[DEBUG] (f) links = []
[DEBUG] (f) encoding = UTF-8
[DEBUG] (f) aggregate = false
[DEBUG] (f) tags = []
[DEBUG] (f) isOffline = false
[DEBUG] (f) useStandardDocletOptions = true
[DEBUG] (f) taglets = []
[DEBUG] (f) doctitle = Maven Ant Plugin 2.3-SNAPSHOT API
[DEBUG] (f) resourcesArtifacts = []
[DEBUG] (s) reportOutputDirectory =
M:\maven\plugins\maven-ant-plugin\target\site\apidocs
Unable to parse the created DOM for plugin configuration
org.apache.maven.plugin.PluginConfigurationException: Unable to parse the
created DOM for plugin configuration
at
org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(DefaultPluginManager.java:611)
at
org.apache.maven.plugin.DefaultPluginManager.getConfiguredMojo(DefaultPluginManager.java:564)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:336)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:281)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:208)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:181)
at
org.apache.maven.embedder.MavenEmbedder.execute(MavenEmbedder.java:467)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:163)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:56)
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:597)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:408)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:351)
Caused by:
org.codehaus.plexus.component.configurator.ComponentConfigurationException:
Setter
org.apache.maven.plugin.javadoc.JavadocReport.setReportOutputDirectory(
java.lang.Class )
threw exception when called with parameter
'M:\maven\plugins\maven-ant-plugin\target\site\apidocs': null
at
org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.setValueUsingSetter(ComponentValueSetter.java:204)
at
org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.configure(ComponentValueSetter.java:225)
at
org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsConverter.java:140)
at
org.codehaus.plexus.component.configurator.BasicComponentConfigurator.configureComponent(BasicComponentConfigurator.java:58)
at
org.apache.maven.plugin.DefaultPluginManager.populatePluginFields(DefaultPluginManager.java:605)
... 16 more
Caused by: java.lang.reflect.InvocationTargetException
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:597)
at
org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.setValueUsingSetter(ComponentValueSetter.java:191)
... 20 more
Caused by: java.lang.NullPointerException
at java.lang.String.endsWith(String.java:1466)
at
org.apache.maven.plugin.javadoc.JavadocReport.setReportOutputDirectory(JavadocReport.java:184)
... 25 more
{noformat}
and from Maven 2.2.x
{noformat}
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-javadoc-plugin:2.5:javadoc' -->
[DEBUG] (f) aggregate = false
[DEBUG] (f) author = true
[DEBUG] (f) bootclasspathArtifacts = []
[DEBUG] (f) bottom = Copyright © {inceptionYear}-{currentYear}
{organizationName}. All Rights Reserved.
[DEBUG] (f) breakiterator = false
[DEBUG] (f) debug = false
[DEBUG] (f) destDir = apidocs
[DEBUG] (f)
[jira] Closed: (MNG-4279) wagon provider selection should fail gracefully and use protocol for roleHint if protocol-provider roleHint isn't available.
[
http://jira.codehaus.org/browse/MNG-4279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey closed MNG-4279.
---
Resolution: Fixed
added code to check that the protocol-provider hint exists before blindly
passing it back. If it doesn't exist, simply fall back to the protocol as the
hint.
> wagon provider selection should fail gracefully and use protocol for roleHint
> if protocol-provider roleHint isn't available.
>
>
> Key: MNG-4279
> URL: http://jira.codehaus.org/browse/MNG-4279
> Project: Maven 2
> Issue Type: Improvement
> Components: Artifacts and Repositories
>Affects Versions: 2.2.1
>Reporter: John Casey
>Assignee: John Casey
> Fix For: 2.2.1
>
>
> Currently, if the server section of the settings.xml uses wagonProvider to
> set a provider suffix, that provider may apply to multiple different
> repository definitions.
> If the user specifies a repository with protocol == http and provider ==
> httpclient for artifact resolution using a server id of 'foo', then configure
> a distribution repository with protocol == scp, the provider == httpclient
> will be applied to this distribution repo, and result in an error like this:
> {noformat}
> Component descriptor cannot be found in the component repository:
> org.apache.maven.wagon.Wagonscp-httpclient.
> {noformat}
> Obviously, this will never work. In these cases, ideally different server IDs
> should be used. However, if not then Maven should fallback gracefully to a
> roleHint of 'scp'.
--
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: (MNG-4162) Removal of all reporting logic from the core of Maven
[
http://jira.codehaus.org/browse/MNG-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185792#action_185792
]
Olivier Lamy commented on MNG-4162:
---
The approach used creating for each report plugin : creating a new ClassRealm
with parent maven-site-plugin-realm with parent core realm.
Following imported from maven-site-plugin realm :
- org.apache.maven.reporting.MavenReport
- org.codehaus.doxia.sink.Sink
- org.apache.maven.doxia.sink.Sink
- org.apache.maven.doxia.sink.SinkEventAttributes
Note need to add org.apache.maven.artifact.manager.WagonConfigurationException
in compat.
So I now have the famous issue with :
{code}
... 15 more
Caused by: java.lang.NoSuchMethodError:
org.codehaus.plexus.PlexusContainer.getLoggerManager()Lorg/codehaus/plexus/logging/LoggerManager;
at
org.apache.maven.report.projectinfo.DependenciesReport.executeReport(DependenciesReport.java:222)
at
org.apache.maven.reporting.AbstractMavenReport.generate(AbstractMavenReport.java:90)
at
org.apache.maven.plugins.site.ReportDocumentRenderer.renderDocument(ReportDocumentRenderer.java:145)
... 19 more
{code}
> Removal of all reporting logic from the core of Maven
> -
>
> Key: MNG-4162
> URL: http://jira.codehaus.org/browse/MNG-4162
> Project: Maven 2
> Issue Type: Improvement
>Reporter: Jason van Zyl
> Fix For: 3.0
>
>
> Any reporting implementation will be implemented as a plugin. Maven will
> provide any information, APIs, and extension points to make this possible.
> But the conflation of building with reporting in the core makes it almost
> impossible for anyone two understand the distinction, makes it impossible to
> have alternate implementations and couple many tools like Doxia directly to
> the core which is unacceptable for Maven 3.x.
--
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: (SUREFIRE-118) Cannot override read-only parameter: classpathElements
[ http://jira.codehaus.org/browse/SUREFIRE-118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185789#action_185789 ] David Hoffer commented on SUREFIRE-118: --- Is it possible to specify the classpath load order of existing dependencies? I have a case where maven installs & deploys work find but site-deploy does not. The reason is the the order of the class path entries in the surefirebooter jar is different. I need to make sure that an artifact with overrides is loaded first. I don't need to add additional cp elements just specify order. Can this be done somehow? -Dave > Cannot override read-only parameter: classpathElements > -- > > Key: SUREFIRE-118 > URL: http://jira.codehaus.org/browse/SUREFIRE-118 > Project: Maven Surefire > Issue Type: Bug >Affects Versions: 1.5.2 (2.1.2 plugin), 2.0 (2.2 plugin) >Reporter: Jesper Zedlitz >Priority: Minor > Fix For: 2.4 > > Attachments: additionalClasspaths.patch > > > When calling "mvn site" on a multi-module project the goal "surefire:test" > fails for the second project: > Error configuring: org.apache.maven.plugins:maven-surefire-plugin. Reason: > ERROR: Cannot override read-only parameter: classpathElements in goal: > surefire:test > "mvn test" works and runs the tests on all modules. -- 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: (MNG-4162) Removal of all reporting logic from the core of Maven
[ http://jira.codehaus.org/browse/MNG-4162?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185780#action_185780 ] Olivier Lamy commented on MNG-4162: --- I have commit stuff in core branch. No big chance only new methods and some move from private to public. No objections to merge to trunk ? > Removal of all reporting logic from the core of Maven > - > > Key: MNG-4162 > URL: http://jira.codehaus.org/browse/MNG-4162 > Project: Maven 2 > Issue Type: Improvement >Reporter: Jason van Zyl > Fix For: 3.0 > > > Any reporting implementation will be implemented as a plugin. Maven will > provide any information, APIs, and extension points to make this possible. > But the conflation of building with reporting in the core makes it almost > impossible for anyone two understand the distinction, makes it impossible to > have alternate implementations and couple many tools like Doxia directly to > the core which is unacceptable for Maven 3.x. -- 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: (MNG-4279) wagon provider selection should fail gracefully and use protocol for roleHint if protocol-provider roleHint isn't available.
[
http://jira.codehaus.org/browse/MNG-4279?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
John Casey updated MNG-4279:
Assignee: John Casey
Description:
Currently, if the server section of the settings.xml uses wagonProvider to set
a provider suffix, that provider may apply to multiple different repository
definitions.
If the user specifies a repository with protocol == http and provider ==
httpclient for artifact resolution using a server id of 'foo', then configure a
distribution repository with protocol == scp, the provider == httpclient will
be applied to this distribution repo, and result in an error like this:
{noformat}
Component descriptor cannot be found in the component repository:
org.apache.maven.wagon.Wagonscp-httpclient.
{noformat}
Obviously, this will never work. In these cases, ideally different server IDs
should be used. However, if not then Maven should fallback gracefully to a
roleHint of 'scp'.
Fix Version/s: 2.2.1
> wagon provider selection should fail gracefully and use protocol for roleHint
> if protocol-provider roleHint isn't available.
>
>
> Key: MNG-4279
> URL: http://jira.codehaus.org/browse/MNG-4279
> Project: Maven 2
> Issue Type: Improvement
> Components: Artifacts and Repositories
>Affects Versions: 2.2.1
>Reporter: John Casey
>Assignee: John Casey
> Fix For: 2.2.1
>
>
> Currently, if the server section of the settings.xml uses wagonProvider to
> set a provider suffix, that provider may apply to multiple different
> repository definitions.
> If the user specifies a repository with protocol == http and provider ==
> httpclient for artifact resolution using a server id of 'foo', then configure
> a distribution repository with protocol == scp, the provider == httpclient
> will be applied to this distribution repo, and result in an error like this:
> {noformat}
> Component descriptor cannot be found in the component repository:
> org.apache.maven.wagon.Wagonscp-httpclient.
> {noformat}
> Obviously, this will never work. In these cases, ideally different server IDs
> should be used. However, if not then Maven should fallback gracefully to a
> roleHint of 'scp'.
--
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: (MSITE-210) DoxiaFilter does not set output encoding
[
http://jira.codehaus.org/browse/MSITE-210?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185776#action_185776
]
Darius commented on MSITE-210:
--
I see good output with version 2.1-SNAPSHOT, thanks.
> DoxiaFilter does not set output encoding
>
>
> Key: MSITE-210
> URL: http://jira.codehaus.org/browse/MSITE-210
> Project: Maven 2.x Site Plugin
> Issue Type: Bug
> Components: encoding, site:run
>Affects Versions: 2.0-beta-5, 2.0-beta-6
>Reporter: Darius
>Assignee: Lukas Theussl
> Fix For: 2.1
>
> Attachments: MSITE-DoxiaFilter-patch.txt
>
>
> As mentioned in MSITE-19 DoxiaFilter does not set any output encoding. In my
> situation this makes {{site:run}} goal pretty much useless.
> Attaching a patch for trunk.
--
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] Created: (MNG-4279) wagon provider selection should fail gracefully and use protocol for roleHint if protocol-provider roleHint isn't available.
wagon provider selection should fail gracefully and use protocol for roleHint if protocol-provider roleHint isn't available. Key: MNG-4279 URL: http://jira.codehaus.org/browse/MNG-4279 Project: Maven 2 Issue Type: Improvement Components: Artifacts and Repositories Affects Versions: 2.2.1 Reporter: John Casey -- 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: (MSTAGE-7) Unable to use archiva as http source with maven-stage-plugin
[ http://jira.codehaus.org/browse/MSTAGE-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185770#action_185770 ] Jacob Robertson commented on MSTAGE-7: -- I'm pretty sure this issue applies to the latest version of Nexus as well. We upgraded our version of nexus, and the stage plugin stopped working. The behavior was a never ending console logging of "../ found". I applied this patch locally to the stage plugin, and the problem went away. > Unable to use archiva as http source with maven-stage-plugin > > > Key: MSTAGE-7 > URL: http://jira.codehaus.org/browse/MSTAGE-7 > Project: Maven 2.x Stage Plugin > Issue Type: Bug >Affects Versions: 1.0-alpha-1 >Reporter: Dan Tran > Attachments: MSTAGE-7.patch > > > http-wagon-beta-2 currently not able to parse the archiva page ( > http://jira.codehaus.org/browse/MRM-891 ). > however with the fix from http://jira.codehaus.org/browse/MRM-893 and upgrade > to wagon-beta-3 will solve the problem > without change in stage plugin source code. -- 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: (MJAVADOC-246) ExceptionInInitializerError
[ http://jira.codehaus.org/browse/MJAVADOC-246?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185759#action_185759 ] Malachi de AElfweald commented on MJAVADOC-246: --- 2.6-SNAPSHOT does appear to have fixed that issue; leaving behind a weird side effect: [INFO] Generating "JavaDocs" report. Aug 3, 2009 10:15:45 AM org.apache.commons.httpclient.HttpMethodBase processCookieHeaders WARNING: Cookie rejected: "$Version=0; JSESSIONID=50AF6CD52E5016EFA7D533AF6DD95394; $Path=/servlets". Illegal path attribute "/servlets". Path of origin: "/nonav/maven/apidocs/package-list" [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:2.6-SNAPSHOT:javadoc' has not be previously called for the project: 'org.eoti.maven.skins:ljod:jar:2.3-SNAPSHOT'. Trying to invoke it... [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:2.6-SNAPSHOT:javadoc' has not be previously called for the project: 'org.eoti:seshat:jar:2.3-SNAPSHOT'. Trying to invoke it... [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:2.6-SNAPSHOT:javadoc' has not be previously called for the project: 'org.eoti:clotho:jar:2.3-SNAPSHOT'. Trying to invoke it... [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:2.6-SNAPSHOT:javadoc' has not be previously called for the project: 'org.eoti:lachesis:jar:2.3-SNAPSHOT'. Trying to invoke it... [INFO] The goal 'org.apache.maven.plugins:maven-javadoc-plugin:2.6-SNAPSHOT:javadoc' has not be previously called for the project: 'org.eoti:atropos:jar:2.3-SNAPSHOT'. Trying to invoke it... Loading source files for package org.eoti.rei.cmp... > ExceptionInInitializerError > --- > > Key: MJAVADOC-246 > URL: http://jira.codehaus.org/browse/MJAVADOC-246 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.6 > Environment: Hudson or command-line > Maven 2.1.0 or 2.2.0 > JDK 1.6 or JDK 1.7 > OpenSolaris >Reporter: Malachi de AElfweald >Priority: Blocker > Fix For: 2.6.1 > > > This bug only happens if I have maven-javadoc-plugin enabled. If I comment it > out site generation works. The POM is not specifying a particular version so > I am not sure which one it is using. > These bugs seem to report the same problem against other plugins: > http://jira.codehaus.org/browse/MOJO-1118 > http://jira.codehaus.org/browse/MOJO-1101 > Based on the error message, I checked the repository after successfully > building without JavaDoc and it shows these versions of commons-logging were > used: > 1.0 > 1.0.3 > 1.0.4 > 1.1 > The only SNAPSHOT dependency is 2.1-SNAPSHOT of the maven-site-plugin (to get > around site generation bugs). I am using the -U during building. > [INFO] Generating "JavaDocs" report. > [FATAL ERROR] org.apache.maven.plugins.site.SiteMojo#execute() caused a > linkage error (java.lang.ExceptionInInitializerError) and may be out-of-date. > Check the realms: > [FATAL ERROR] Plugin realm = > app0.child-container[org.apache.maven.plugins:maven-site-plugin:2.1-SNAPSHOT] > urls[0] = > file:/home/hudson/.m2/repository/org/apache/maven/plugins/maven-site-plugin/2.1-SNAPSHOT/maven-site-plugin-2.1-SNAPSHOT.jar > urls[1] = > file:/home/hudson/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.1/plexus-utils-1.5.1.jar > urls[2] = > file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.1.2-SNAPSHOT/doxia-module-xhtml-1.1.2-SNAPSHOT.jar > urls[3] = > file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-core/1.1.2-SNAPSHOT/doxia-core-1.1.2-SNAPSHOT.jar > urls[4] = > file:/home/hudson/.m2/repository/xerces/xercesImpl/2.8.1/xercesImpl-2.8.1.jar > urls[5] = > file:/home/hudson/.m2/repository/xml-apis/xml-apis/1.3.03/xml-apis-1.3.03.jar > urls[6] = > file:/home/hudson/.m2/repository/commons-lang/commons-lang/2.4/commons-lang-2.4.jar > urls[7] = > file:/home/hudson/.m2/repository/commons-httpclient/commons-httpclient/3.1/commons-httpclient-3.1.jar > urls[8] = > file:/home/hudson/.m2/repository/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar > urls[9] = > file:/home/hudson/.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar > urls[10] = > file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-module-apt/1.1.2-SNAPSHOT/doxia-module-apt-1.1.2-SNAPSHOT.jar > urls[11] = > file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-module-xdoc/1.1.2-SNAPSHOT/doxia-module-xdoc-1.1.2-SNAPSHOT.jar > urls[12] = > file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-module-fml/1.1.2-SNAPSHOT/doxia-module-fml-1.1.2-SNAPSHOT.jar > urls[13] = > file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.1.2-SNAPSHOT/doxia-decoration-model-1.1.2-SNAPSHOT.jar > urls[14] = > file:/home/hudson/.m2/repository/org/apac
[jira] Updated: (MENFORCER-81) Create a banned plugins rule
[ http://jira.codehaus.org/browse/MENFORCER-81?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Marvin Froeder updated MENFORCER-81: Attachment: banned-plugin.patch Add missing file > Create a banned plugins rule > > > Key: MENFORCER-81 > URL: http://jira.codehaus.org/browse/MENFORCER-81 > Project: Maven 2.x Enforcer Plugin > Issue Type: New Feature > Components: Standard Rules >Affects Versions: 1.0-beta-1 >Reporter: Marvin Froeder > Attachments: banned-plugin.patch, banned-plugin.patch > > > I created a new rule for banned plugins -- 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] Created: (MENFORCER-81) Create a banned plugins rule
Create a banned plugins rule Key: MENFORCER-81 URL: http://jira.codehaus.org/browse/MENFORCER-81 Project: Maven 2.x Enforcer Plugin Issue Type: New Feature Components: Standard Rules Affects Versions: 1.0-beta-1 Reporter: Marvin Froeder Attachments: banned-plugin.patch I created a new rule for banned plugins -- 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: (MSITE-420) Parent project site descriptor menu options always a link back to parent site
[ http://jira.codehaus.org/browse/MSITE-420?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185742#action_185742 ] EJ Ciramella commented on MSITE-420: Hmm - that seems to work if it's a parent/child like this (where one contains the other). Our parent->child relationship is more like corp pom->other module (where they aren't nested). How do I get this working? > Parent project site descriptor menu options always a link back to parent site > - > > Key: MSITE-420 > URL: http://jira.codehaus.org/browse/MSITE-420 > Project: Maven 2.x Site Plugin > Issue Type: Bug > Components: doxia integration, inheritance >Affects Versions: 2.0-beta-5, 2.0-beta-6, 2.0-beta-7, 2.0, 2.0.1 > Environment: Using maven 2.0.9 - and all versions of the site plugin > all the way back to 2.0-beta-5. >Reporter: EJ Ciramella > Attachments: MSITE-420.zip > > > I'd like to have a parent project define what items are in a given menu for > all child projects and let the child projects define the contents of those > links (this doesn't work). > In the documentation for the site plugin here: > http://maven.apache.org/plugins/maven-site-plugin/examples/sitedescriptor.html > There is a bit in there about how to get a parent project site descriptor to > be inherited by a child project by using the following: > > This is great if you want the child project to always link back to the parent > project's links/pages for each menu option. > Doxia however shows this is configurable: > http://maven.apache.org/doxia/doxia-sitetools-1.0.x/doxia-decoration-model/decoration.html#class_menu > inheritAsRef - If this is a reference, setting true means that it will be > populated in the project, whereas if it is false, it is populated in the > parent and then inherited. The default value is false. > This property currently doesn't work. -- 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: (MJAVADOC-249) javadoc:fix should wrap existing comments in
[
http://jira.codehaus.org/browse/MJAVADOC-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185729#action_185729
]
Vincent Siveton commented on MJAVADOC-249:
--
I guess we could add them (patch welcome!) but I can't see any plus value to
have them unless this is generated!
> javadoc:fix should wrap existing comments in
>
>
> Key: MJAVADOC-249
> URL: http://jira.codehaus.org/browse/MJAVADOC-249
> Project: Maven 2.x Javadoc Plugin
> Issue Type: New Feature
>Affects Versions: 2.6
>Reporter: jieryn
>Priority: Minor
>
> When I run the javadoc:fix mojo, freshly generated comments are wrapped
> inside tags. However, comments which existed prior to the run are
> not wrapped in such tags, even when they do not exist. This mojo does more
> than just add missing javadoc comments, but also tries to fix them up (for
> example, /**\n* {...@inheritdoc}\n*/ gets transformed to /** {...@inheritdoc}
> */ ... which sets the precedent that the mojo is at least open to the idea of
> fixing existing comments.
> Thanks!
--
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: (MJAVADOC-247) location of doc-files is wrong on page http://maven.apache.org/plugins/maven-javadoc-plugin/examples/test-javadocs.html
[ http://jira.codehaus.org/browse/MJAVADOC-247?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185731#action_185731 ] Vincent Siveton commented on MJAVADOC-247: -- Could you provide a patch or reformat your issue? > location of doc-files is wrong on page > http://maven.apache.org/plugins/maven-javadoc-plugin/examples/test-javadocs.html > --- > > Key: MJAVADOC-247 > URL: http://jira.codehaus.org/browse/MJAVADOC-247 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug > Environment: Published web page >Reporter: bruce weertman >Priority: Minor > > On the web-page > > http://maven.apache.org/plugins/maven-javadoc-plugin/examples/test-javadocs.html > > there is a tree-view of a directory layout (see below) > It shows the hypothetical path: >src/main/javadoc/org/apache/myapp/doc-files/app.png > This is a bad example as it will not work w/o fiddling around with pom > configuration. > It should say: > src/main/javadoc/doc-files/app.png > If you were to use the layout given, you would discover that app.png is never > copied into the > target directory. > yourproject > |-- src > |-- main > | |-- java > | | |-- org > | | |-- apache > | ||-- myapp > | | `-- App.java > | |-- javadoc > | `-- overview.html > | |-- org > ||-- apache > | |-- myapp > |`-- package.html > | |-- doc-files > | `-- app.png > |-- test > |-- java > | |-- org > | |-- apache > ||-- myapp > | `-- AppTest.java > |-- javadoc > `-- overview.html >|-- org > |-- apache > |-- myapp > `-- package.html > |-- doc-files > `-- app.png -- 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: (MJAVADOC-250) javadoc:fix mojo should fully qualify {...@link} class names
[
http://jira.codehaus.org/browse/MJAVADOC-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185728#action_185728
]
Vincent Siveton commented on MJAVADOC-250:
--
Yes we could have the import list but in my sample, it does not guarantee the
"exact" class to be throw.
If you have any ideas, please provide a patch.
> javadoc:fix mojo should fully qualify {...@link} class names
> -
>
> Key: MJAVADOC-250
> URL: http://jira.codehaus.org/browse/MJAVADOC-250
> Project: Maven 2.x Javadoc Plugin
> Issue Type: New Feature
>Affects Versions: 2.6
>Reporter: jieryn
>Priority: Minor
>
> When the javadoc:fix goal is executed, it rightly adds fully qualified class
> names for each {...@link} tag. It would be great if the mojo would fix
> existing {...@link} tags to be fully qualified, also. Thanks!
--
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: (MJAVADOC-244) Javadoc plugin: java files under src/main/javadoc and doc-files directory are being compiled
[ http://jira.codehaus.org/browse/MJAVADOC-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated MJAVADOC-244: - Priority: Minor (was: Major) > Javadoc plugin: java files under src/main/javadoc and doc-files directory are > being compiled > > > Key: MJAVADOC-244 > URL: http://jira.codehaus.org/browse/MJAVADOC-244 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.6 >Reporter: Chris Wilkes >Priority: Minor > Attachments: javadoc-problem.zip > > > Maven was trying to compile src/main/javadoc/my/company/doc-files/Foo.java > even though I set the docfilessubdirs configuration option to true. Renaming > it to .txt works, however maven should probably not compile anything under > src/main/javadoc/ -- 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: (MJAVADOC-244) Javadoc plugin: java files under src/main/javadoc and doc-files directory are being compiled
[ http://jira.codehaus.org/browse/MJAVADOC-244?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185727#action_185727 ] Vincent Siveton commented on MJAVADOC-244: -- Confirmed. I guess we could add a filter for java files, but the doc for docfilessubdirs [1] doesnt speak about java files. So we need to understand your use case to add java files in javadoc dir. You could also provide a patch (always better). [1] http://java.sun.com/j2se/1.4.2/docs/tooldocs/windows/javadoc.html#docfilessubdirs > Javadoc plugin: java files under src/main/javadoc and doc-files directory are > being compiled > > > Key: MJAVADOC-244 > URL: http://jira.codehaus.org/browse/MJAVADOC-244 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.6 >Reporter: Chris Wilkes > Attachments: javadoc-problem.zip > > > Maven was trying to compile src/main/javadoc/my/company/doc-files/Foo.java > even though I set the docfilessubdirs configuration option to true. Renaming > it to .txt works, however maven should probably not compile anything under > src/main/javadoc/ -- 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: (MJAVADOC-244) Javadoc plugin: java files under src/main/javadoc and doc-files directory are being compiled
[ http://jira.codehaus.org/browse/MJAVADOC-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated MJAVADOC-244: - Affects Version/s: 2.6 > Javadoc plugin: java files under src/main/javadoc and doc-files directory are > being compiled > > > Key: MJAVADOC-244 > URL: http://jira.codehaus.org/browse/MJAVADOC-244 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.6 >Reporter: Chris Wilkes > Attachments: javadoc-problem.zip > > > Maven was trying to compile src/main/javadoc/my/company/doc-files/Foo.java > even though I set the docfilessubdirs configuration option to true. Renaming > it to .txt works, however maven should probably not compile anything under > src/main/javadoc/ -- 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: (MJAVADOC-245) Aggregate does not work
[ http://jira.codehaus.org/browse/MJAVADOC-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated MJAVADOC-245: - Attachment: MJAVADOC-245.zip Are you sure? running mvn site works on mvn 2.0.x and 2.1 and files are aggregated. If you run javadoc:javadoc, it doesn't work because it is a reporting plugin configuration. You need to configure the project.build.plugins part. > Aggregate does not work > --- > > Key: MJAVADOC-245 > URL: http://jira.codehaus.org/browse/MJAVADOC-245 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.5, 2.6 >Reporter: Jörg Hohwiller > Attachments: MJAVADOC-245.zip > > > I want to have an aggregated javadoc for the entire project as well as per > module. > Therefore I followed instructions at: > http://maven.apache.org/plugins/maven-javadoc-plugin/examples/aggregate.html > When I do mvn site:stage I get no aggregated javadoc but just per module. > This does not even change if I only do > > > > aggregate > > > > So to me this looks as if is magically ignored here. > I have tested 2.5 as well as 2.6 from > https://repository.apache.org/content/repositories/maven-staging-027/org/apache/maven/plugins/maven-javadoc-plugin/2.6/ -- 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: (MJAVADOC-246) ExceptionInInitializerError
[ http://jira.codehaus.org/browse/MJAVADOC-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated MJAVADOC-246: - Affects Version/s: 2.6 > ExceptionInInitializerError > --- > > Key: MJAVADOC-246 > URL: http://jira.codehaus.org/browse/MJAVADOC-246 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.6 > Environment: Hudson or command-line > Maven 2.1.0 or 2.2.0 > JDK 1.6 or JDK 1.7 > OpenSolaris >Reporter: Malachi de AElfweald >Priority: Blocker > Fix For: 2.6.1 > > > This bug only happens if I have maven-javadoc-plugin enabled. If I comment it > out site generation works. The POM is not specifying a particular version so > I am not sure which one it is using. > These bugs seem to report the same problem against other plugins: > http://jira.codehaus.org/browse/MOJO-1118 > http://jira.codehaus.org/browse/MOJO-1101 > Based on the error message, I checked the repository after successfully > building without JavaDoc and it shows these versions of commons-logging were > used: > 1.0 > 1.0.3 > 1.0.4 > 1.1 > The only SNAPSHOT dependency is 2.1-SNAPSHOT of the maven-site-plugin (to get > around site generation bugs). I am using the -U during building. > [INFO] Generating "JavaDocs" report. > [FATAL ERROR] org.apache.maven.plugins.site.SiteMojo#execute() caused a > linkage error (java.lang.ExceptionInInitializerError) and may be out-of-date. > Check the realms: > [FATAL ERROR] Plugin realm = > app0.child-container[org.apache.maven.plugins:maven-site-plugin:2.1-SNAPSHOT] > urls[0] = > file:/home/hudson/.m2/repository/org/apache/maven/plugins/maven-site-plugin/2.1-SNAPSHOT/maven-site-plugin-2.1-SNAPSHOT.jar > urls[1] = > file:/home/hudson/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.1/plexus-utils-1.5.1.jar > urls[2] = > file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.1.2-SNAPSHOT/doxia-module-xhtml-1.1.2-SNAPSHOT.jar > urls[3] = > file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-core/1.1.2-SNAPSHOT/doxia-core-1.1.2-SNAPSHOT.jar > urls[4] = > file:/home/hudson/.m2/repository/xerces/xercesImpl/2.8.1/xercesImpl-2.8.1.jar > urls[5] = > file:/home/hudson/.m2/repository/xml-apis/xml-apis/1.3.03/xml-apis-1.3.03.jar > urls[6] = > file:/home/hudson/.m2/repository/commons-lang/commons-lang/2.4/commons-lang-2.4.jar > urls[7] = > file:/home/hudson/.m2/repository/commons-httpclient/commons-httpclient/3.1/commons-httpclient-3.1.jar > urls[8] = > file:/home/hudson/.m2/repository/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar > urls[9] = > file:/home/hudson/.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar > urls[10] = > file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-module-apt/1.1.2-SNAPSHOT/doxia-module-apt-1.1.2-SNAPSHOT.jar > urls[11] = > file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-module-xdoc/1.1.2-SNAPSHOT/doxia-module-xdoc-1.1.2-SNAPSHOT.jar > urls[12] = > file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-module-fml/1.1.2-SNAPSHOT/doxia-module-fml-1.1.2-SNAPSHOT.jar > urls[13] = > file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.1.2-SNAPSHOT/doxia-decoration-model-1.1.2-SNAPSHOT.jar > urls[14] = > file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.1.2-SNAPSHOT/doxia-site-renderer-1.1.2-SNAPSHOT.jar > urls[15] = > file:/home/hudson/.m2/repository/org/codehaus/plexus/plexus-i18n/1.0-beta-7/plexus-i18n-1.0-beta-7.jar > urls[16] = > file:/home/hudson/.m2/repository/org/codehaus/plexus/plexus-velocity/1.1.7/plexus-velocity-1.1.7.jar > urls[17] = > file:/home/hudson/.m2/repository/org/apache/velocity/velocity/1.5/velocity-1.5.jar > urls[18] = > file:/home/hudson/.m2/repository/commons-collections/commons-collections/3.2/commons-collections-3.2.jar > urls[19] = file:/home/hudson/.m2/repository/oro/oro/2.0.8/oro-2.0.8.jar > urls[20] = > file:/home/hudson/.m2/repository/org/apache/maven/shared/maven-doxia-tools/1.1-SNAPSHOT/maven-doxia-tools-1.1-SNAPSHOT.jar > urls[21] = > file:/home/hudson/.m2/repository/commons-io/commons-io/1.4/commons-io-1.4.jar > urls[22] = > file:/home/hudson/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-7/plexus-archiver-1.0-alpha-7.jar > urls[23] = > file:/home/hudson/.m2/repository/org/mortbay/jetty/jetty/6.1.5/jetty-6.1.5.jar > urls[24] = > file:/home/hudson/.m2/repository/org/mortbay/jetty/jetty-util/6.1.5/jetty-util-6.1.5.jar > urls[25] = > file:/home/hudson/.m2/repository/org/mortbay/jetty/servlet-api-2.5/6.1.5/servlet-api-2.5-6.1.5.jar > [FATAL ERROR] Container realm = plexus.core > urls[0] = file:/opt/apache-maven-2.1.0/lib/maven-2.1.0-uber.jar > [INFO] >
[jira] Updated: (MJAVADOC-246) ExceptionInInitializerError
[ http://jira.codehaus.org/browse/MJAVADOC-246?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton updated MJAVADOC-246: - Priority: Blocker (was: Major) Fix Version/s: 2.6.1 confirmed > ExceptionInInitializerError > --- > > Key: MJAVADOC-246 > URL: http://jira.codehaus.org/browse/MJAVADOC-246 > Project: Maven 2.x Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.6 > Environment: Hudson or command-line > Maven 2.1.0 or 2.2.0 > JDK 1.6 or JDK 1.7 > OpenSolaris >Reporter: Malachi de AElfweald >Priority: Blocker > Fix For: 2.6.1 > > > This bug only happens if I have maven-javadoc-plugin enabled. If I comment it > out site generation works. The POM is not specifying a particular version so > I am not sure which one it is using. > These bugs seem to report the same problem against other plugins: > http://jira.codehaus.org/browse/MOJO-1118 > http://jira.codehaus.org/browse/MOJO-1101 > Based on the error message, I checked the repository after successfully > building without JavaDoc and it shows these versions of commons-logging were > used: > 1.0 > 1.0.3 > 1.0.4 > 1.1 > The only SNAPSHOT dependency is 2.1-SNAPSHOT of the maven-site-plugin (to get > around site generation bugs). I am using the -U during building. > [INFO] Generating "JavaDocs" report. > [FATAL ERROR] org.apache.maven.plugins.site.SiteMojo#execute() caused a > linkage error (java.lang.ExceptionInInitializerError) and may be out-of-date. > Check the realms: > [FATAL ERROR] Plugin realm = > app0.child-container[org.apache.maven.plugins:maven-site-plugin:2.1-SNAPSHOT] > urls[0] = > file:/home/hudson/.m2/repository/org/apache/maven/plugins/maven-site-plugin/2.1-SNAPSHOT/maven-site-plugin-2.1-SNAPSHOT.jar > urls[1] = > file:/home/hudson/.m2/repository/org/codehaus/plexus/plexus-utils/1.5.1/plexus-utils-1.5.1.jar > urls[2] = > file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.1.2-SNAPSHOT/doxia-module-xhtml-1.1.2-SNAPSHOT.jar > urls[3] = > file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-core/1.1.2-SNAPSHOT/doxia-core-1.1.2-SNAPSHOT.jar > urls[4] = > file:/home/hudson/.m2/repository/xerces/xercesImpl/2.8.1/xercesImpl-2.8.1.jar > urls[5] = > file:/home/hudson/.m2/repository/xml-apis/xml-apis/1.3.03/xml-apis-1.3.03.jar > urls[6] = > file:/home/hudson/.m2/repository/commons-lang/commons-lang/2.4/commons-lang-2.4.jar > urls[7] = > file:/home/hudson/.m2/repository/commons-httpclient/commons-httpclient/3.1/commons-httpclient-3.1.jar > urls[8] = > file:/home/hudson/.m2/repository/commons-logging/commons-logging/1.0.4/commons-logging-1.0.4.jar > urls[9] = > file:/home/hudson/.m2/repository/commons-codec/commons-codec/1.2/commons-codec-1.2.jar > urls[10] = > file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-module-apt/1.1.2-SNAPSHOT/doxia-module-apt-1.1.2-SNAPSHOT.jar > urls[11] = > file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-module-xdoc/1.1.2-SNAPSHOT/doxia-module-xdoc-1.1.2-SNAPSHOT.jar > urls[12] = > file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-module-fml/1.1.2-SNAPSHOT/doxia-module-fml-1.1.2-SNAPSHOT.jar > urls[13] = > file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.1.2-SNAPSHOT/doxia-decoration-model-1.1.2-SNAPSHOT.jar > urls[14] = > file:/home/hudson/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.1.2-SNAPSHOT/doxia-site-renderer-1.1.2-SNAPSHOT.jar > urls[15] = > file:/home/hudson/.m2/repository/org/codehaus/plexus/plexus-i18n/1.0-beta-7/plexus-i18n-1.0-beta-7.jar > urls[16] = > file:/home/hudson/.m2/repository/org/codehaus/plexus/plexus-velocity/1.1.7/plexus-velocity-1.1.7.jar > urls[17] = > file:/home/hudson/.m2/repository/org/apache/velocity/velocity/1.5/velocity-1.5.jar > urls[18] = > file:/home/hudson/.m2/repository/commons-collections/commons-collections/3.2/commons-collections-3.2.jar > urls[19] = file:/home/hudson/.m2/repository/oro/oro/2.0.8/oro-2.0.8.jar > urls[20] = > file:/home/hudson/.m2/repository/org/apache/maven/shared/maven-doxia-tools/1.1-SNAPSHOT/maven-doxia-tools-1.1-SNAPSHOT.jar > urls[21] = > file:/home/hudson/.m2/repository/commons-io/commons-io/1.4/commons-io-1.4.jar > urls[22] = > file:/home/hudson/.m2/repository/org/codehaus/plexus/plexus-archiver/1.0-alpha-7/plexus-archiver-1.0-alpha-7.jar > urls[23] = > file:/home/hudson/.m2/repository/org/mortbay/jetty/jetty/6.1.5/jetty-6.1.5.jar > urls[24] = > file:/home/hudson/.m2/repository/org/mortbay/jetty/jetty-util/6.1.5/jetty-util-6.1.5.jar > urls[25] = > file:/home/hudson/.m2/repository/org/mortbay/jetty/servlet-api-2.5/6.1.5/servlet-api-2.5-6.1.5.jar > [FATAL ERROR] Container realm = plexus.core > urls[0] = file:/opt/apache-maven-2.1.0/lib/maven-2.1.0-uber.jar > [INFO] > --
[jira] Commented: (MJAVADOC-249) javadoc:fix should wrap existing comments in
[
http://jira.codehaus.org/browse/MJAVADOC-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185719#action_185719
]
jieryn commented on MJAVADOC-249:
-
Yep, I like that it collapses the {...@inheritdoc} down to one line. :-) I
wanted to have tags added to existing documentation simply for consistency.
> javadoc:fix should wrap existing comments in
>
>
> Key: MJAVADOC-249
> URL: http://jira.codehaus.org/browse/MJAVADOC-249
> Project: Maven 2.x Javadoc Plugin
> Issue Type: New Feature
>Affects Versions: 2.6
>Reporter: jieryn
>Priority: Minor
>
> When I run the javadoc:fix mojo, freshly generated comments are wrapped
> inside tags. However, comments which existed prior to the run are
> not wrapped in such tags, even when they do not exist. This mojo does more
> than just add missing javadoc comments, but also tries to fix them up (for
> example, /**\n* {...@inheritdoc}\n*/ gets transformed to /** {...@inheritdoc}
> */ ... which sets the precedent that the mojo is at least open to the idea of
> fixing existing comments.
> Thanks!
--
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: (MJAVADOC-248) Site 'Usage' page references 2.5 version of m-javadoc-p
[ http://jira.codehaus.org/browse/MJAVADOC-248?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Vincent Siveton closed MJAVADOC-248. Assignee: Vincent Siveton Resolution: Fixed Fix Version/s: 2.6.1 fixed in [r800341|http://svn.apache.org/viewvc?rev=800341&view=rev] > Site 'Usage' page references 2.5 version of m-javadoc-p > --- > > Key: MJAVADOC-248 > URL: http://jira.codehaus.org/browse/MJAVADOC-248 > Project: Maven 2.x Javadoc Plugin > Issue Type: Task >Affects Versions: 2.6 >Reporter: jieryn >Assignee: Vincent Siveton >Priority: Trivial > Fix For: 2.6.1 > > > http://maven.apache.org/plugins/maven-javadoc-plugin/usage.html -- 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: (MJAVADOC-249) javadoc:fix should wrap existing comments in
[
http://jira.codehaus.org/browse/MJAVADOC-249?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Vincent Siveton updated MJAVADOC-249:
-
Priority: Minor (was: Major)
> javadoc:fix should wrap existing comments in
>
>
> Key: MJAVADOC-249
> URL: http://jira.codehaus.org/browse/MJAVADOC-249
> Project: Maven 2.x Javadoc Plugin
> Issue Type: New Feature
>Affects Versions: 2.6
>Reporter: jieryn
>Priority: Minor
>
> When I run the javadoc:fix mojo, freshly generated comments are wrapped
> inside tags. However, comments which existed prior to the run are
> not wrapped in such tags, even when they do not exist. This mojo does more
> than just add missing javadoc comments, but also tries to fix them up (for
> example, /**\n* {...@inheritdoc}\n*/ gets transformed to /** {...@inheritdoc}
> */ ... which sets the precedent that the mojo is at least open to the idea of
> fixing existing comments.
> Thanks!
--
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: (MJAVADOC-249) javadoc:fix should wrap existing comments in
[
http://jira.codehaus.org/browse/MJAVADOC-249?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185717#action_185717
]
Vincent Siveton commented on MJAVADOC-249:
--
Why do you want to add them by default in your existing Javadoc? Formatting
reasons? Unify goal behaviours?
Using or not has the same behaviour... and I don't think fix goal needs to
modify the original javadoc.
Having /* @inheritDoc */ in one line is the formatting exception in the mojo.
It is common in modern projects and reduces code size.
> javadoc:fix should wrap existing comments in
>
>
> Key: MJAVADOC-249
> URL: http://jira.codehaus.org/browse/MJAVADOC-249
> Project: Maven 2.x Javadoc Plugin
> Issue Type: New Feature
>Affects Versions: 2.6
>Reporter: jieryn
>
> When I run the javadoc:fix mojo, freshly generated comments are wrapped
> inside tags. However, comments which existed prior to the run are
> not wrapped in such tags, even when they do not exist. This mojo does more
> than just add missing javadoc comments, but also tries to fix them up (for
> example, /**\n* {...@inheritdoc}\n*/ gets transformed to /** {...@inheritdoc}
> */ ... which sets the precedent that the mojo is at least open to the idea of
> fixing existing comments.
> Thanks!
--
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: (MJAVADOC-250) javadoc:fix mojo should fully qualify {...@link} class names
[
http://jira.codehaus.org/browse/MJAVADOC-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185718#action_185718
]
jieryn commented on MJAVADOC-250:
-
Does the m-javadoc-p have any class-level sense? By this I mean, if there were
is an import statement for that class name, use it, otherwise, use $package.
> javadoc:fix mojo should fully qualify {...@link} class names
> -
>
> Key: MJAVADOC-250
> URL: http://jira.codehaus.org/browse/MJAVADOC-250
> Project: Maven 2.x Javadoc Plugin
> Issue Type: New Feature
>Affects Versions: 2.6
>Reporter: jieryn
>Priority: Minor
>
> When the javadoc:fix goal is executed, it rightly adds fully qualified class
> names for each {...@link} tag. It would be great if the mojo would fix
> existing {...@link} tags to be fully qualified, also. Thanks!
--
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: (MRELEASE-468) Branch mojo page lists branchName parameter as optional itparameter although it is required
[ http://jira.codehaus.org/browse/MRELEASE-468?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stevo Slavic closed MRELEASE-468. - Resolution: Duplicate Duplicate of MRELEASE-327 > Branch mojo page lists branchName parameter as optional itparameter although > it is required > --- > > Key: MRELEASE-468 > URL: http://jira.codehaus.org/browse/MRELEASE-468 > Project: Maven 2.x Release Plugin > Issue Type: Bug > Components: documentation >Affects Versions: 2.0-beta-9 >Reporter: Stevo Slavic > > Branch mojo page > (http://maven.apache.org/plugins/maven-release-plugin/branch-mojo.html) lists > branchName parameter as optional, although it is required. -- 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: (MJAVADOC-250) javadoc:fix mojo should fully qualify {...@link} class names
[
http://jira.codehaus.org/browse/MJAVADOC-250?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185711#action_185711
]
Vincent Siveton commented on MJAVADOC-250:
--
I already thought about this feature but it seems difficult to find the right
class in the classloader.
{noformat}
/**
* @throws ConnectException
* @see {...@link ConnectException}
*/
public void dummy()
throws ConnectException {}
public static class ConnectException extends Exception{}
{noformat}
Which ConnectException? net, rmi or inner?
> javadoc:fix mojo should fully qualify {...@link} class names
> -
>
> Key: MJAVADOC-250
> URL: http://jira.codehaus.org/browse/MJAVADOC-250
> Project: Maven 2.x Javadoc Plugin
> Issue Type: New Feature
>Affects Versions: 2.6
>Reporter: jieryn
>Priority: Minor
>
> When the javadoc:fix goal is executed, it rightly adds fully qualified class
> names for each {...@link} tag. It would be great if the mojo would fix
> existing {...@link} tags to be fully qualified, also. Thanks!
--
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] Created: (SCM-488) Git provider fails to support 'release:perform' if not releasing from remote HEAD
Git provider fails to support 'release:perform' if not releasing from remote HEAD - Key: SCM-488 URL: http://jira.codehaus.org/browse/SCM-488 Project: Maven SCM Issue Type: Bug Components: maven-scm-provider-git Reporter: Petter Måhlén During the 'release:perform' phase using Git provider the following commands are issued: [INFO] Checking out the project to perform the release ... [INFO] Executing: /bin/sh -c cd /Users/pettermahlen/git/sas-client/target && git clone git://git.shopzilla.com/site/client/sas-client /Users/pettermahlen/git/sas-client/target/checkout [INFO] Working directory: /Users/pettermahlen/git/sas-client/target [INFO] Executing: /bin/sh -c cd /Users/pettermahlen/git/sas-client/target/checkout && git pull git://git.shopzilla.com/site/client/sas-client tag root-5.18-uk [INFO] Working directory: /Users/pettermahlen/git/sas-client/target/checkout If the branch that is being released has conflicts (that cannot be automatically resolved) with the current HEAD at the remote server, the 'pull' with fail due to merge conflicts. A manual execution can look like: [pettermah...@petters-macbook-pro target (uk-release)]$ git clone git://git.shopzilla.com/site/client/sas-client /Users/pettermahlen/git/sas-client/target/checkout Initialized empty Git repository in /Users/pettermahlen/git/sas-client/target/checkout/.git/ remote: Counting objects: 72993, done. remote: Compressing objects: 100% (18392/18392), done. remote: Total 72993 (delta 40752), reused 71454 (delta 39845) Receiving objects: 100% (72993/72993), 38.22 MiB | 2724 KiB/s, done. Resolving deltas: 100% (40752/40752), done. [pettermah...@petters-macbook-pro target (uk-release)]$ cd checkout/ [pettermah...@petters-macbook-pro checkout (master)]$ git pull git://git.shopzilla.com/site/client/sas-client tag root-5.18-uk Auto-merging client/pom.xml CONFLICT (content): Merge conflict in client/pom.xml Auto-merging core/pom.xml CONFLICT (content): Merge conflict in core/pom.xml Auto-merging model/pom.xml Pull does a fetch and a merge with what is currently checked out. A potential fix would be to rather than the 'git pull' command issue the following: git checkout That's what I did to get past this situation, and I believe that should work as a general solution. -- 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] Created: (MRELEASE-468) Branch mojo page lists branchName parameter as optional itparameter although it is required
Branch mojo page lists branchName parameter as optional itparameter although it is required --- Key: MRELEASE-468 URL: http://jira.codehaus.org/browse/MRELEASE-468 Project: Maven 2.x Release Plugin Issue Type: Bug Components: documentation Affects Versions: 2.0-beta-9 Reporter: Stevo Slavic Branch mojo page (http://maven.apache.org/plugins/maven-release-plugin/branch-mojo.html) lists branchName parameter as optional, although it is required. -- 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: (MNG-3043) Allow 'mvn test' to work with test-jar dependencies in a reactor
[ http://jira.codehaus.org/browse/MNG-3043?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Benjamin Bentmann closed MNG-3043. -- Resolution: Fixed Revised in [r800294|http://svn.apache.org/viewvc?view=rev&revision=800294]. > Allow 'mvn test' to work with test-jar dependencies in a reactor > > > Key: MNG-3043 > URL: http://jira.codehaus.org/browse/MNG-3043 > Project: Maven 2 > Issue Type: Bug > Components: Dependencies, Reactor and workspace >Affects Versions: 2.0.6, 2.0.7 >Reporter: Kenney Westerhof >Assignee: Benjamin Bentmann > Fix For: 3.0-alpha-3 > > Attachments: mng-3043.zip > > > Basically the issue is demonstrated by MNG-2045, but instead of running 'mvn > install', you run 'mvn test'. > Test classes of dependencies should be resolved from the reactor, just as > main classes, if there's no archive available. > I'm not sure how to go about this. Specifying a dependency on something with > test-jar, > and having that dependency declare the maven-jar-plugin with the 'test-jar' > goal is insufficient. > Perhaps we can just add a standard classifier that maven is aware of, in this > case 'tests'. The jar packaging > would export this as a known classifier, and tells maven how it contributes > to what classpath. > Since test sources are a first class citizen, just as main sources are (they > have the same phases, same > elements in the pom (but differently named)). > It seems logical to me that somehow the test classes should be made available > to dependencies, > if they declare a dependency with classifier 'tests'. -- 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] Created: (MNG-4278) Allow wildcard in server id in settings.xml
Allow wildcard in server id in settings.xml
---
Key: MNG-4278
URL: http://jira.codehaus.org/browse/MNG-4278
Project: Maven 2
Issue Type: New Feature
Components: Settings
Affects Versions: 2.2.0
Reporter: Julien HENRY
In my company each project has a separate repository for deploying their
artifacts (we are using Archiva).
One developer may work on several projects, and also the integration platform
(Continuum) must be able to deploy on all repositories.
Currently I have to add in settings.xml
{code}
mycompany.project1Id.release
userId
xxx
mycompany.project2Id.release
userId
xxx
mycompany.project1Id.snapshots
userId
xxx
mycompany.project2Id.snapshots
userId
xxx
... (repeat for every projects)
{code}
Where userId and password are always the same.
It would be great to allow:
{code}
mycompany.*.*
userId
xxx
{code}
in settings.xml.
In case there are several matches for a repositoryId, I think it is better to
raise an error.
--
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] Issue Comment Edited: (MRELEASE-400) Failed to validate POM for project ... at ...\release-pom.xml
[
http://jira.codehaus.org/browse/MRELEASE-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185677#action_185677
]
Hafga edited comment on MRELEASE-400 at 8/3/09 3:17 AM:
I got exact the same error. Using maven 2.0.8. The POM has an parent-pom and
using struts:
org.apache.struts
struts2-core
2.0.11
Struts is the only one, that define a dependency on tools:
default-tools.jar
java.vendor
Sun Microsystems Inc.
com.sun
tools
1.5.0
system
${java.home}/../lib/tools.jar
Using " -DgenerateReleasePoms=false" seams to prevent the error
was (Author: hafga):
I got exact the same error. Using maven 2.0.8. The POM has an parent-pom
and using struts:
org.apache.struts
struts2-core
2.0.11
Struts is the only one, that define a dependency on tools:
default-tools.jar
java.vendor
Sun Microsystems Inc.
com.sun
tools
1.5.0
system
${java.home}/../lib/tools.jar
> Failed to validate POM for project ... at ...\release-pom.xml
> -
>
> Key: MRELEASE-400
> URL: http://jira.codehaus.org/browse/MRELEASE-400
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Reporter: Borut Bolcina
>
> When releasing the multimodule project and one of the transitive dependencies
> is tools.jar a fatal error occurs.
> mvn release:prepare -DgenerateReleasePoms=true
> ...
> [INFO] Executing: mvn clean verify --no-plugin-updates -P proxy
> [INFO] Scanning for projects...
> [INFO] NOTE: Using release-pom:
> C:\eclipse\workspace\trident-project\release-pom.xml in reactor build.
> [INFO] NOTE: Using release-pom:
> C:\eclipse\workspace\trident-project\trident-admin\release-pom.xml in reactor
> build.
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] Error building POM (may not be this project's POM).
> Project ID: com.interseek:trident-admin
> POM Location:
> C:\eclipse\workspace\trident-project\trident-admin\release-pom.xml
> Validation Messages:
> [0] For dependency Dependency {groupId=com.sun, artifactId=tools,
> version=1.5.0, type=jar}: system-scoped dependency must specify systemPath.
> Reason: Failed to validate POM for project
> com.interseek:trident-admin at
> C:\eclipse\workspace\trident-project\trident-admin\release-pom.xml
> [INFO]
>
> [INFO] Trace
> org.apache.maven.reactor.MavenExecutionException: Failed to validate
> POM for project com.interseek:trident-admin at
> C:\eclipse\workspace\trident-project\trident-admin\release-pom.xml
> at
> org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378)
> at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292)
> at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> 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.project.InvalidProjectModelException:
> Failed to validate POM for project com.interseek:trident-admin at
> C:\eclipse\workspace\trident-project\trident-admin\release-pom.xml
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:1108)
>
[jira] Commented: (MRELEASE-400) Failed to validate POM for project ... at ...\release-pom.xml
[
http://jira.codehaus.org/browse/MRELEASE-400?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=185677#action_185677
]
Hafga commented on MRELEASE-400:
I got exact the same error. Using maven 2.0.8. The POM has an parent-pom and
using struts:
org.apache.struts
struts2-core
2.0.11
Struts is the only one, that define a dependency on tools:
default-tools.jar
java.vendor
Sun Microsystems Inc.
com.sun
tools
1.5.0
system
${java.home}/../lib/tools.jar
> Failed to validate POM for project ... at ...\release-pom.xml
> -
>
> Key: MRELEASE-400
> URL: http://jira.codehaus.org/browse/MRELEASE-400
> Project: Maven 2.x Release Plugin
> Issue Type: Bug
> Components: prepare
>Reporter: Borut Bolcina
>
> When releasing the multimodule project and one of the transitive dependencies
> is tools.jar a fatal error occurs.
> mvn release:prepare -DgenerateReleasePoms=true
> ...
> [INFO] Executing: mvn clean verify --no-plugin-updates -P proxy
> [INFO] Scanning for projects...
> [INFO] NOTE: Using release-pom:
> C:\eclipse\workspace\trident-project\release-pom.xml in reactor build.
> [INFO] NOTE: Using release-pom:
> C:\eclipse\workspace\trident-project\trident-admin\release-pom.xml in reactor
> build.
> [INFO]
>
> [ERROR] FATAL ERROR
> [INFO]
>
> [INFO] Error building POM (may not be this project's POM).
> Project ID: com.interseek:trident-admin
> POM Location:
> C:\eclipse\workspace\trident-project\trident-admin\release-pom.xml
> Validation Messages:
> [0] For dependency Dependency {groupId=com.sun, artifactId=tools,
> version=1.5.0, type=jar}: system-scoped dependency must specify systemPath.
> Reason: Failed to validate POM for project
> com.interseek:trident-admin at
> C:\eclipse\workspace\trident-project\trident-admin\release-pom.xml
> [INFO]
>
> [INFO] Trace
> org.apache.maven.reactor.MavenExecutionException: Failed to validate
> POM for project com.interseek:trident-admin at
> C:\eclipse\workspace\trident-project\trident-admin\release-pom.xml
> at
> org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:378)
> at
> org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:292)
> at
> org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:287)
> 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.project.InvalidProjectModelException:
> Failed to validate POM for project com.interseek:trident-admin at
> C:\eclipse\workspace\trident-project\trident-admin\release-pom.xml
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLogic(DefaultMavenProjectBuilder.java:1108)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(DefaultMavenProjectBuilder.java:878)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.buildFromSourceFileInternal(DefaultMavenProjectBuilder.java:506)
> at
> org.apache.maven.project.DefaultMavenProjectBuilder.build(DefaultMavenProjectBuilder.java:198)
> at
> org.apache.maven.DefaultMaven.getProject(DefaultMaven.java:583)
> at
> org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:461)
> at
> org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:534)
> at
> org.apache.maven.DefaultMaven.getProjects(DefaultMaven.java:365)
> ...
