[jira] (MSHARED-329) dependency tree should be the same when using verbose or not
Cintia DR created MSHARED-329:
-
Summary: dependency tree should be the same when using verbose or
not
Key: MSHARED-329
URL: https://jira.codehaus.org/browse/MSHARED-329
Project: Maven Shared Components
Issue Type: Improvement
Components: maven-dependency-tree
Reporter: Cintia DR
Priority: Minor
When running dependency tree (version 2.8) using maven 3, the generated tree is
consistent with what maven is using.
If you enable -Dverbose, I have a [maven 2 dependency
tree|https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Compatibility+Notes#Maven3.xCompatibilityNotes-AutomaticPluginVersionResolution]:
{code}
if ( verbose )
{
// verbose mode force Maven 2 dependency tree component use
dependencyTreeString =
serializeVerboseDependencyTree(
dependencyTreeBuilder.buildDependencyTree( project,
localRepository,
artifactFilter ) );
}
else
{
// non-verbose mode use dependency graph component, which gives
consistent results with Maven version
// running
rootNode = dependencyGraphBuilder.buildDependencyGraph(
project, artifactFilter );
dependencyTreeString = serializeDependencyTree( rootNode );
}
{code}
It's very misleading. Even the
[documentation|http://maven.apache.org/plugins/maven-dependency-plugin/tree-mojo.html#verbose]
doesn't mention it.
Probably there's a good reason to not use Aether for the verbose mode, but I
guess at least it should print a warning at the end of the process and
explicitly say it in the documentation.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (SUREFIRE-910) Surefire 2.12.1 fails with The forked VM terminated without saying properly goodbye
[
https://jira.codehaus.org/browse/SUREFIRE-910?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=345088#comment-345088
]
Gerold Broser commented on SUREFIRE-910:
Occurred with v2.16 today, from one day to the other without a code change in
this particular project since 9 days:
{{\[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.16:test (default-test) on
project com.smartstream.exception.server: Execution default-test of goal
org.apache.maven.plugins:maven-surefire-plugin:2.16:test failed: The forked VM
terminated without saying properly goodbye. VM crash or System.exit called ?}}}
{{\[ERROR] Command was/bin/sh -c cd
/var/lib/jenkins/jobs/MOR-main-2.0.9-freestyle/workspace/platform/ems/srv/com.smartstream.exception.server
/opt/jdk1.7.0_21/jre/bin/java -jar
/var/lib/jenkins/jobs/MOR-main-2.0.9-freestyle/workspace/platform/ems/srv/com.smartstream.exception.server/target/surefire/surefirebooter6827028791989735645.jar
/var/lib/jenkins/jobs/MOR-main-2.0.9-freestyle/workspace/platform/ems/srv/com.smartstream.exception.server/target/surefire/surefire6848724445266495070tmp
/var/lib/jenkins/jobs/MOR-main-2.0.9-freestyle/workspace/platform/ems/srv/com.smartstream.exception.server/target/surefire/surefire_434760846349196313015tmp}}
Surefire 2.12.1 fails with The forked VM terminated without saying properly
goodbye
-
Key: SUREFIRE-910
URL: https://jira.codehaus.org/browse/SUREFIRE-910
Project: Maven Surefire
Issue Type: Bug
Components: Maven Surefire Plugin
Reporter: Ilya Katsov
Assignee: Kristian Rosenvold
Fix For: 2.13
Build fails with The forked VM terminated without saying properly goodbye
message with no information about the source of the problem:
{code}
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.125 sec
Running org.apache.hadoop.fs.viewfs.TestViewFsHdfs
Tests run: 42, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 14.149 sec
Running org.apache.hadoop.fs.TestFcHdfsSymlink
Tests run: 67, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 20.792 sec
Results :
Tests run: 1033, Failures: 0, Errors: 0, Skipped: 1
[INFO]
[INFO]
[INFO] Skipping Apache Hadoop HDFS Project
[INFO] This project has been banned from the build due to previous failures.
[INFO]
[INFO]
[INFO]
[INFO] Skipping Apache Hadoop HDFS
[INFO] This project has been banned from the build due to previous failures.
[INFO]
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Hadoop HDFS FAILURE
[1:06:10.415s]
[INFO] Apache Hadoop HttpFS .. SKIPPED
[INFO] Apache Hadoop HDFS Project SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 1:06:11.188s
[INFO] Finished at: Wed Sep 05 12:01:46 MSK 2012
[INFO] Final Memory: 24M/394M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.12.1:test (default-test) on
project hadoop-hdfs: ExecutionException; nested exception is
java.util.concurrent.ExecutionException: java.lang.RuntimeException: The
forked VM terminated without saying properly goodbye. VM crash or System.exit
called ? - [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-surefire-plugin:2.12.1:test
(default-test) on project hadoop-hdfs: ExecutionException; nested exception
is java.util.concurrent.ExecutionException: java.lang.RuntimeException: The
forked VM terminated without saying properly goodbye. VM crash or System.exit
called ?
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
[jira] (SUREFIRE-910) Surefire 2.12.1 fails with The forked VM terminated without saying properly goodbye
[
https://jira.codehaus.org/browse/SUREFIRE-910?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gerold Broser updated SUREFIRE-910:
---
Comment: was deleted
(was: Occurred with v2.16 today, from one day to the other without a code
change in this particular project since 9 days:
{{\[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.16:test (default-test) on
project com.smartstream.exception.server: Execution default-test of goal
org.apache.maven.plugins:maven-surefire-plugin:2.16:test failed: The forked VM
terminated without saying properly goodbye. VM crash or System.exit called ?}}}
{{\[ERROR] Command was/bin/sh -c cd
/var/lib/jenkins/jobs/MOR-main-2.0.9-freestyle/workspace/platform/ems/srv/com.smartstream.exception.server
/opt/jdk1.7.0_21/jre/bin/java -jar
/var/lib/jenkins/jobs/MOR-main-2.0.9-freestyle/workspace/platform/ems/srv/com.smartstream.exception.server/target/surefire/surefirebooter6827028791989735645.jar
/var/lib/jenkins/jobs/MOR-main-2.0.9-freestyle/workspace/platform/ems/srv/com.smartstream.exception.server/target/surefire/surefire6848724445266495070tmp
/var/lib/jenkins/jobs/MOR-main-2.0.9-freestyle/workspace/platform/ems/srv/com.smartstream.exception.server/target/surefire/surefire_434760846349196313015tmp}}
)
Surefire 2.12.1 fails with The forked VM terminated without saying properly
goodbye
-
Key: SUREFIRE-910
URL: https://jira.codehaus.org/browse/SUREFIRE-910
Project: Maven Surefire
Issue Type: Bug
Components: Maven Surefire Plugin
Reporter: Ilya Katsov
Assignee: Kristian Rosenvold
Fix For: 2.13
Build fails with The forked VM terminated without saying properly goodbye
message with no information about the source of the problem:
{code}
Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 3.125 sec
Running org.apache.hadoop.fs.viewfs.TestViewFsHdfs
Tests run: 42, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 14.149 sec
Running org.apache.hadoop.fs.TestFcHdfsSymlink
Tests run: 67, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 20.792 sec
Results :
Tests run: 1033, Failures: 0, Errors: 0, Skipped: 1
[INFO]
[INFO]
[INFO] Skipping Apache Hadoop HDFS Project
[INFO] This project has been banned from the build due to previous failures.
[INFO]
[INFO]
[INFO]
[INFO] Skipping Apache Hadoop HDFS
[INFO] This project has been banned from the build due to previous failures.
[INFO]
[INFO]
[INFO] Reactor Summary:
[INFO]
[INFO] Apache Hadoop HDFS FAILURE
[1:06:10.415s]
[INFO] Apache Hadoop HttpFS .. SKIPPED
[INFO] Apache Hadoop HDFS Project SKIPPED
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 1:06:11.188s
[INFO] Finished at: Wed Sep 05 12:01:46 MSK 2012
[INFO] Final Memory: 24M/394M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-surefire-plugin:2.12.1:test (default-test) on
project hadoop-hdfs: ExecutionException; nested exception is
java.util.concurrent.ExecutionException: java.lang.RuntimeException: The
forked VM terminated without saying properly goodbye. VM crash or System.exit
called ? - [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
goal org.apache.maven.plugins:maven-surefire-plugin:2.12.1:test
(default-test) on project hadoop-hdfs: ExecutionException; nested exception
is java.util.concurrent.ExecutionException: java.lang.RuntimeException: The
forked VM terminated without saying properly goodbye. VM crash or System.exit
called ?
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:84)
at
[jira] (MCOMPILER-224) Maven compiler plugin does not properly consume plexus compiler output
[ https://jira.codehaus.org/browse/MCOMPILER-224?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=345094#comment-345094 ] David M. Lloyd commented on MCOMPILER-224: -- Looking for any update here. Maven compiler plugin does not properly consume plexus compiler output -- Key: MCOMPILER-224 URL: https://jira.codehaus.org/browse/MCOMPILER-224 Project: Maven Compiler Plugin Issue Type: Bug Affects Versions: 3.0, 3.1 Reporter: David M. Lloyd Attachments: MCOMPILER-224.patch Maven compiler plugin does not properly read the output from the plexus compiler. All CompilerMessages are logged at warning or error level, even if they are not warnings or errors. -- This message was sent by Atlassian JIRA (v6.1.6#6162)
[jira] (MJAVADOC-393) -link option values have their trailing slash removed; breaks javadoc 8
Laird Nelson created MJAVADOC-393:
-
Summary: -link option values have their trailing slash removed;
breaks javadoc 8
Key: MJAVADOC-393
URL: https://jira.codehaus.org/browse/MJAVADOC-393
Project: Maven Javadoc Plugin
Issue Type: Bug
Affects Versions: 2.9.1
Reporter: Laird Nelson
The version of {{javadoc}} that ships with Java 8 has changed such that any
value supplied to the {{-link}} option must have a trailing slash (at least on
my Mac).
Line 2932 of {{AbstractJavadocMojo.java}} programmatically strips the trailing
slashes from the {{links}} property elements, ensuring that {{javadoc}} version
8 cannot process its {{-link}} options properly.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MJAVADOC-393) -link option values have their trailing slash removed; breaks javadoc 8
[
https://jira.codehaus.org/browse/MJAVADOC-393?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=345095#comment-345095
]
Laird Nelson commented on MJAVADOC-393:
---
Line 3932, sorry.
-link option values have their trailing slash removed; breaks javadoc 8
---
Key: MJAVADOC-393
URL: https://jira.codehaus.org/browse/MJAVADOC-393
Project: Maven Javadoc Plugin
Issue Type: Bug
Affects Versions: 2.9.1
Reporter: Laird Nelson
The version of {{javadoc}} that ships with Java 8 has changed such that any
value supplied to the {{-link}} option must have a trailing slash (at least
on my Mac).
Line 2932 of {{AbstractJavadocMojo.java}} programmatically strips the
trailing slashes from the {{links}} property elements, ensuring that
{{javadoc}} version 8 cannot process its {{-link}} options properly.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPLUGIN-191) plugin-info.html is not created
[
https://jira.codehaus.org/browse/MPLUGIN-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MPLUGIN-191.
--
Resolution: Duplicate
closing as duplicate of MPLUGIN-187
plugin-info.html is not created
---
Key: MPLUGIN-191
URL: https://jira.codehaus.org/browse/MPLUGIN-191
Project: Maven Plugin Tools
Issue Type: Bug
Components: Plugin Plugin
Affects Versions: 2.9
Environment: Maven 3.x
Reporter: Balazs Zsoldos
Assignee: Robert Scholte
Priority: Critical
During running maven-plugin-plugin:report the following exception occurs:
{noformat}Caused by: java.lang.NoClassDefFoundError:
org/apache/maven/doxia/module/xhtml/decoration/render/RenderingContext
at
org.apache.maven.reporting.sink.SinkFactory.createSink(SinkFactory.java:59)
at
org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:85)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
... 20 more
Caused by: java.lang.ClassNotFoundException:
org.apache.maven.doxia.module.xhtml.decoration.render.RenderingContext
at
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:244)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:230)
... 23 more{noformat}
After some debugging it seams to me that the cause is the version of
maven-reporting-impl dependency which is now 2.0.5. I made it work with the
following snippet in my pom.xml:
{code:xml}plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-plugin-plugin/artifactId
version2.9/version
executions
execution
idreport/id
phasepre-site/phase
goals
goalreport/goal
/goals
/execution
/executions
dependencies
dependency
groupIdorg.apache.maven.reporting/groupId
artifactIdmaven-reporting-impl/artifactId
version2.2/version
/dependency
/dependencies
/plugin{code}
After this setting the plugin-info.html file is generated at
target/generated-site/xdoc directory. However nothing is copied to
target/site as the output file should be moved to target/generated-site/xhtml
and it should have the extension .xhtml.vm.
I made the workaround that I copy and rename the html file to
src/site/xhtml/plugin-info.xhtml.vm.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MPLUGIN-191) plugin-info.html is not created
[
https://jira.codehaus.org/browse/MPLUGIN-191?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte reopened MPLUGIN-191:
I just notices that the original issue was solved, but there's a related issue.
Reopening...
plugin-info.html is not created
---
Key: MPLUGIN-191
URL: https://jira.codehaus.org/browse/MPLUGIN-191
Project: Maven Plugin Tools
Issue Type: Bug
Components: Plugin Plugin
Affects Versions: 2.9
Environment: Maven 3.x
Reporter: Balazs Zsoldos
Assignee: Robert Scholte
Priority: Critical
During running maven-plugin-plugin:report the following exception occurs:
{noformat}Caused by: java.lang.NoClassDefFoundError:
org/apache/maven/doxia/module/xhtml/decoration/render/RenderingContext
at
org.apache.maven.reporting.sink.SinkFactory.createSink(SinkFactory.java:59)
at
org.apache.maven.reporting.AbstractMavenReport.execute(AbstractMavenReport.java:85)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:101)
... 20 more
Caused by: java.lang.ClassNotFoundException:
org.apache.maven.doxia.module.xhtml.decoration.render.RenderingContext
at
org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy.loadClass(SelfFirstStrategy.java:50)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:244)
at
org.codehaus.plexus.classworlds.realm.ClassRealm.loadClass(ClassRealm.java:230)
... 23 more{noformat}
After some debugging it seams to me that the cause is the version of
maven-reporting-impl dependency which is now 2.0.5. I made it work with the
following snippet in my pom.xml:
{code:xml}plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-plugin-plugin/artifactId
version2.9/version
executions
execution
idreport/id
phasepre-site/phase
goals
goalreport/goal
/goals
/execution
/executions
dependencies
dependency
groupIdorg.apache.maven.reporting/groupId
artifactIdmaven-reporting-impl/artifactId
version2.2/version
/dependency
/dependencies
/plugin{code}
After this setting the plugin-info.html file is generated at
target/generated-site/xdoc directory. However nothing is copied to
target/site as the output file should be moved to target/generated-site/xhtml
and it should have the extension .xhtml.vm.
I made the workaround that I copy and rename the html file to
src/site/xhtml/plugin-info.xhtml.vm.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MJAVADOC-368) Can not use a comma (,) in option additionalparam
[
https://jira.codehaus.org/browse/MJAVADOC-368?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=345103#comment-345103
]
Martin Desruisseaux commented on MJAVADOC-368:
--
This is also a problem for the new JDK8 {{-Xdoclint}} option. For example:
{noformat}
additionalparam-Xdoclint:syntax,missing,accessibility/additionalparam
{noformat}
produces the given lines in the {{options}} file generated by Maven:
{noformat}
-Xdoclint:syntax
missing
accessibility
{noformat}
It seems that Maven replaced the coma by line separator. Adding quote does not
prevent that. This behavior is not documented in the [plugin
goal|http://maven.apache.org/plugins/maven-javadoc-plugin/aggregate-mojo.html#additionalparam].
Can not use a comma (,) in option additionalparam
-
Key: MJAVADOC-368
URL: https://jira.codehaus.org/browse/MJAVADOC-368
Project: Maven Javadoc Plugin
Issue Type: Bug
Affects Versions: 2.9
Reporter: Andy Schönemann
I would like to set an additional parameter for javadoc like
{{additionalparam-header apos;A,Bapos;/additionalparam}}
But this is not possible! Every comma here separates the string into
different parameters. So I'm not able to set parameters including commas.
Furthermore, the options name is {{additionalparam}} and NOT
{{additionalparamS}}. So it should not be possible to set multiple parameters
here.
I also tried
{{additionalparam-header apos;A#44;Bapos;/additionalparam}}
but this doesn't work either.
[Plugin
documentation|http://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html#additionalparam]
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
[jira] (MJAVADOC-387) Handle JDK8 -Xdoclint
[
https://jira.codehaus.org/browse/MJAVADOC-387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanelfocusedCommentId=345104#comment-345104
]
Martin Desruisseaux commented on MJAVADOC-387:
--
A support for {{-Xdoclint}} would be appreciated. However I disagree that Maven
should take {{-Xdoclint:none}} as the default. I realize that the JDK 8
behavior (all checks enabled by default) will break lot of Javadoc generation.
But I think that it is preferable to force developers to explicitly disable the
checks if they need too, otherwise many developers will probably not even
realize that their Javadoc has problems. Especially since when using
{{-Xdoclint:none}}, the errors are not replaced by warnings - they just
disappear.
Handle JDK8 -Xdoclint
-
Key: MJAVADOC-387
URL: https://jira.codehaus.org/browse/MJAVADOC-387
Project: Maven Javadoc Plugin
Issue Type: Improvement
Reporter: Stephen Colebourne
The Oracle team have added the doclint tool to JDK 8. The tool validates
Javadoc as part of a standard Javadoc run. Unfortunately, with the default
settings, it rejects many HTML elements that are perfectly acceptable to
browsers, and all invalid Javadoc references (@links). This is likely to
prove very unpopular with developers.
Action needed:
1) Provide a maven-javadoc-plugin configuration item and property that can
control the doclint tool (currently this requires using additionalparam
AFAICT).
2) Apply the {{-Xdoclint:none}} option by default, so that doclint is opt-in,
not opt-out (ie. fix Oracle's messed up default). This will also make it much
easier for developers to handle migration to JDK 8.
--
This message was sent by Atlassian JIRA
(v6.1.6#6162)
