[jira] [Commented] (MNG-6254) Clarificatin on sorting in Repository Metadata
[ https://issues.apache.org/jira/browse/MNG-6254?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16081735#comment-16081735 ] Manfred Moser commented on MNG-6254: Afaik it is sorted by time of deployment... each deployment (independent of version) appends as new entry. So its sorted .. just not the way you might want it. > Clarificatin on sorting in Repository Metadata > - > > Key: MNG-6254 > URL: https://issues.apache.org/jira/browse/MNG-6254 > Project: Maven > Issue Type: Improvement > Components: Artifacts and Repositories >Affects Versions: 3.5.0 >Reporter: Markus Karg > > The document > http://maven.apache.org/ref/3.3.9/maven-repository-metadata/repository-metadata.html > explains that does contain a _List_, hence is _sorted_. > When pulling _real _metadata from Maven Central, e. g. > http://repo.maven.apache.org/maven2/javax/ws/rs/jsr311-api/maven-metadata.xml, > it is apparent that the content of is _not_ sorted (in this > example, 1.1-ea is listed _after_ 1.1, which is a violation of the sorting, > because -ea must be listed _before_ 1.1). So effectively Maven Central > devliers _unsorted_ versions. > Also, the effectively listed XSD > http://maven.apache.org/xsd/metadata-1.1.0.xsd is nonexistent, so cannot be > looked but whether Maven Central is wrong, or whether actually the > specification should say it must be Set instead of List. > To sum up, there should be a clarification whether must be sorted > according to the Maven Version Numbering Schema, whether it must be Set vs > List, and whether the missing XSD should be uploaded. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (MNG-6254) Clarificatin on sorting in Repository Metadata
Markus Karg created MNG-6254: Summary: Clarificatin on sorting in Repository Metadata Key: MNG-6254 URL: https://issues.apache.org/jira/browse/MNG-6254 Project: Maven Issue Type: Improvement Components: Artifacts and Repositories Affects Versions: 3.5.0 Reporter: Markus Karg The document http://maven.apache.org/ref/3.3.9/maven-repository-metadata/repository-metadata.html explains that does contain a _List_, hence is _sorted_. When pulling _real _metadata from Maven Central, e. g. http://repo.maven.apache.org/maven2/javax/ws/rs/jsr311-api/maven-metadata.xml, it is apparent that the content of is _not_ sorted (in this example, 1.1-ea is listed _after_ 1.1, which is a violation of the sorting, because -ea must be listed _before_ 1.1). So effectively Maven Central devliers _unsorted_ versions. Also, the effectively listed XSD http://maven.apache.org/xsd/metadata-1.1.0.xsd is nonexistent, so cannot be looked but whether Maven Central is wrong, or whether actually the specification should say it must be Set instead of List. To sum up, there should be a clarification whether must be sorted according to the Maven Version Numbering Schema, whether it must be Set vs List, and whether the missing XSD should be uploaded. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (SUREFIRE-1340) add a kind of progress status to surefire output
[
https://issues.apache.org/jira/browse/SUREFIRE-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16081084#comment-16081084
]
Tibor Digana commented on SUREFIRE-1340:
[~romain.manni-bucau]
You have two logins in Jira :)
I fully agree with you.
Additionally I am missing uptime of the plugin in test summary.
But I have to fix an issue I committed in HEAD commit, then all fixes of bugs
appeared in {{2.20}} fixed in to new version {{2.20.1}}.
We can count classes and compute %age. Methods can be accessed in plugin's
ClassLoader but this leads to loaded class in plugin and second time in the
forked jvm. People sometimes claim that static code was initialized twice.
I do not think we can have the same feature in TestNG provider. You know, we
try to offer features in both.
What about to have %age always at the end of console for this plugin (maybe
except for mvn -T xxx parallel exec)?
This would be cool effect but this is not issue of Surefire nothing but Maven
because Surefire uses generic console API from Maven project to print on
console including colors.
So please open a discussion at Maven Dev if you want this effect.
> add a kind of progress status to surefire output
>
>
> Key: SUREFIRE-1340
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1340
> Project: Maven Surefire
> Issue Type: New Feature
>Reporter: Romain Manni-Bucau
>
> ATM surefire executes tests but for big suites no way to know where we are in
> the execution exactly. What about adding a kind of line prefix showing it:
> {code}
> [124/1254] normal output
> [124/1254] another normal output
> [126/1254] another normal output after 2 tests finished
> ...
> {code}
> This would at least allow to know where we are. Idea would be to have a
> counter in the "executor" and just show it when there is something on
> stdout/stderr.
> Of course it will require a new configuration flag to activate it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (MNG-6253) Replace CI friendly variables in pom.xml when installing/deploying
[
https://issues.apache.org/jira/browse/MNG-6253?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MNG-6253:
-
Issue Type: Improvement (was: Bug)
> Replace CI friendly variables in pom.xml when installing/deploying
> --
>
> Key: MNG-6253
> URL: https://issues.apache.org/jira/browse/MNG-6253
> Project: Maven
> Issue Type: Improvement
>Affects Versions: 3.5.0
>Reporter: Christoph Amshoff
>
> When using variables in pom.xml to get CI friendly version
> (https://maven.apache.org/maven-ci-friendly.html), these will not be replaced
> in installed or deployed pom files, which makes them unusable for other
> builds.
> Karl Heinz Marbaise suggested to use the flatten-maven-plugin to do the
> property replacement
> (http://blog.soebes.de/blog/2017/04/02/maven-pom-files-without-a-version-in-it/),
> and this was also suggested as a workaround in other tickets (MDEPLOY-223
> got closed with "Not A Problem" solution).
> That indeed works, but flatten-maven-plugin has to be manually configured in
> the base POM, and additionally it changes the pom files in many other areas
> which you would not want.
> I honestly think that property replacement for the three allowed properties
> ({{$\{revision\}}}, {{$\{sha1\}}}, {{$\{changelist\}}}) should be done by
> Maven internally without having the user configure other plugins. The feature
> is just not correctly working without, so closing such issues with "Not A
> Problem" is too little.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MNG-6253) Replace CI friendly variables in pom.xml when installing/deploying
[
https://issues.apache.org/jira/browse/MNG-6253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16080856#comment-16080856
]
Karl Heinz Marbaise commented on MNG-6253:
--
The [referenced documentation already contains the
necessary|https://maven.apache.org/maven-ci-friendly.html#Install__Deploy]
information how to do it correctly.
> Replace CI friendly variables in pom.xml when installing/deploying
> --
>
> Key: MNG-6253
> URL: https://issues.apache.org/jira/browse/MNG-6253
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Christoph Amshoff
>
> When using variables in pom.xml to get CI friendly version
> (https://maven.apache.org/maven-ci-friendly.html), these will not be replaced
> in installed or deployed pom files, which makes them unusable for other
> builds.
> Karl Heinz Marbaise suggested to use the flatten-maven-plugin to do the
> property replacement
> (http://blog.soebes.de/blog/2017/04/02/maven-pom-files-without-a-version-in-it/),
> and this was also suggested as a workaround in other tickets (MDEPLOY-223
> got closed with "Not A Problem" solution).
> That indeed works, but flatten-maven-plugin has to be manually configured in
> the base POM, and additionally it changes the pom files in many other areas
> which you would not want.
> I honestly think that property replacement for the three allowed properties
> ({{$\{revision\}}}, {{$\{sha1\}}}, {{$\{changelist\}}}) should be done by
> Maven internally without having the user configure other plugins. The feature
> is just not correctly working without, so closing such issues with "Not A
> Problem" is too little.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Closed] (MCHECKSTYLE-340) Migrate plugin to Maven 3.0
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-340?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Matt Nelson closed MCHECKSTYLE-340. --- Resolution: Fixed Was trying to clone issue to address the same error with pmd. Will log a new issue instead of cloning > Migrate plugin to Maven 3.0 > --- > > Key: MCHECKSTYLE-340 > URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-340 > Project: Maven Checkstyle Plugin > Issue Type: Improvement >Affects Versions: 2.17 >Reporter: Matt Nelson >Assignee: Guillaume Boué > Fix For: 3.0.0 > > > Migrate the plugin to Maven 3.0 as described in > https://cwiki.apache.org/confluence/display/MAVEN/Plugin+migration+to+Maven3+dependencies. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (MCHECKSTYLE-340) Migrate plugin to Maven 3.0
Matt Nelson created MCHECKSTYLE-340: --- Summary: Migrate plugin to Maven 3.0 Key: MCHECKSTYLE-340 URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-340 Project: Maven Checkstyle Plugin Issue Type: Improvement Affects Versions: 2.17 Reporter: Matt Nelson Assignee: Guillaume Boué Fix For: 3.0.0 Migrate the plugin to Maven 3.0 as described in https://cwiki.apache.org/confluence/display/MAVEN/Plugin+migration+to+Maven3+dependencies. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Comment Edited] (SUREFIRE-1340) add a kind of progress status to surefire output
[
https://issues.apache.org/jira/browse/SUREFIRE-1340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15961780#comment-15961780
]
Romain Manni-Bucau edited comment on SUREFIRE-1340 at 7/10/17 3:52 PM:
---
Was not about suite where this is easy to do but actual surefire tests. Goal is
exactly the one you mention: get progress when there are forks and parallel
tests. Surefire owns that orchestration so is the one able to log that progress
from maven vm.
was (Author: romain.manni-bucau):
Was not about duite where this is easy to do but actual surefire tests. Goal is
axactly the one you mention: get progress when there are forks and parallel
tests. Surefire owns that orchestration so is the one able to log that progress
from maven vm.
> add a kind of progress status to surefire output
>
>
> Key: SUREFIRE-1340
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1340
> Project: Maven Surefire
> Issue Type: New Feature
>Reporter: Romain Manni-Bucau
>
> ATM surefire executes tests but for big suites no way to know where we are in
> the execution exactly. What about adding a kind of line prefix showing it:
> {code}
> [124/1254] normal output
> [124/1254] another normal output
> [126/1254] another normal output after 2 tests finished
> ...
> {code}
> This would at least allow to know where we are. Idea would be to have a
> counter in the "executor" and just show it when there is something on
> stdout/stderr.
> Of course it will require a new configuration flag to activate it.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MPMD-240) Migrate plugin to Maven 3.0
[
https://issues.apache.org/jira/browse/MPMD-240?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16080528#comment-16080528
]
Matt Nelson commented on MPMD-240:
--
I haven't been able to reproduce with 3.5 which I think it because of the
maven-core extension reservations on org.slf4j.*
http://maven.apache.org/ref/3.5.0/maven-core/core-extensions.html
{noformat}
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-pmd-plugin:3.8:pmd (pmd) on project my-project:
Execution pmd of goal org.apache.maven.plugins:maven-pmd-plugin:3.8:pmd failed:
An API incompatibility was encountered while executing
org.apache.maven.plugins:maven-pmd-plugin:3.8:pmd:
java.lang.IncompatibleClassChangeError: org.slf4j.MDC and
org.slf4j.MDC$MDCCloseable disagree on InnerClasses attribute
[ERROR] -
[ERROR] realm =plugin>org.apache.maven.plugins:maven-pmd-plugin:3.8
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] =
file:/Users/myuser/.m2/repository/org/apache/maven/plugins/maven-pmd-plugin/3.8/maven-pmd-plugin-3.8.jar
[ERROR] urls[1] =
file:/Users/myuser/.m2/repository/net/sourceforge/pmd/pmd-core/5.8.1/pmd-core-5.8.1.jar
[ERROR] urls[2] =
file:/Users/myuser/.m2/repository/com/beust/jcommander/1.48/jcommander-1.48.jar
[ERROR] urls[3] =
file:/Users/myuser/.m2/repository/jaxen/jaxen/1.1.6/jaxen-1.1.6.jar
[ERROR] urls[4] =
file:/Users/myuser/.m2/repository/net/java/dev/javacc/javacc/5.0/javacc-5.0.jar
[ERROR] urls[5] =
file:/Users/myuser/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8.jar
[ERROR] urls[6] =
file:/Users/myuser/.m2/repository/org/apache/commons/commons-lang3/3.4/commons-lang3-3.4.jar
[ERROR] urls[7] =
file:/Users/myuser/.m2/repository/org/ow2/asm/asm/5.0.4/asm-5.0.4.jar
[ERROR] urls[8] =
file:/Users/myuser/.m2/repository/com/google/code/gson/gson/2.5/gson-2.5.jar
[ERROR] urls[9] =
file:/Users/myuser/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8-dom.jar
[ERROR] urls[10] =
file:/Users/myuser/.m2/repository/net/sourceforge/pmd/pmd-java/5.8.1/pmd-java-5.8.1.jar
[ERROR] urls[11] =
file:/Users/myuser/.m2/repository/net/sourceforge/pmd/pmd-javascript/5.8.1/pmd-javascript-5.8.1.jar
[ERROR] urls[12] =
file:/Users/myuser/.m2/repository/org/mozilla/rhino/1.7.7/rhino-1.7.7.jar
[ERROR] urls[13] =
file:/Users/myuser/.m2/repository/net/sourceforge/pmd/pmd-jsp/5.8.1/pmd-jsp-5.8.1.jar
[ERROR] urls[14] =
file:/Users/myuser/.m2/repository/org/slf4j/jcl-over-slf4j/1.7.5/jcl-over-slf4j-1.7.5.jar
[ERROR] urls[15] =
file:/Users/myuser/.m2/repository/org/slf4j/slf4j-jdk14/1.7.5/slf4j-jdk14-1.7.5.jar
[ERROR] urls[16] =
file:/Users/myuser/.m2/repository/org/slf4j/slf4j-nop/1.7.5/slf4j-nop-1.7.5.jar
[ERROR] urls[17] =
file:/Users/myuser/.m2/repository/backport-util-concurrent/backport-util-concurrent/3.1/backport-util-concurrent-3.1.jar
[ERROR] urls[18] =
file:/Users/myuser/.m2/repository/org/codehaus/plexus/plexus-interpolation/1.11/plexus-interpolation-1.11.jar
[ERROR] urls[19] =
file:/Users/myuser/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar
[ERROR] urls[20] =
file:/Users/myuser/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.4/doxia-sink-api-1.4.jar
[ERROR] urls[21] =
file:/Users/myuser/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.4/doxia-logging-api-1.4.jar
[ERROR] urls[22] =
file:/Users/myuser/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.4/doxia-decoration-model-1.4.jar
[ERROR] urls[23] =
file:/Users/myuser/.m2/repository/org/codehaus/plexus/plexus-component-annotations/1.6/plexus-component-annotations-1.6.jar
[ERROR] urls[24] =
file:/Users/myuser/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.4/doxia-site-renderer-1.4.jar
[ERROR] urls[25] =
file:/Users/myuser/.m2/repository/org/apache/maven/doxia/doxia-core/1.4/doxia-core-1.4.jar
[ERROR] urls[26] =
file:/Users/myuser/.m2/repository/xerces/xercesImpl/2.9.1/xercesImpl-2.9.1.jar
[ERROR] urls[27] =
file:/Users/myuser/.m2/repository/xml-apis/xml-apis/1.3.04/xml-apis-1.3.04.jar
[ERROR] urls[28] =
file:/Users/myuser/.m2/repository/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
[ERROR] urls[29] =
file:/Users/myuser/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.4/doxia-module-xhtml-1.4.jar
[ERROR] urls[30] =
file:/Users/myuser/.m2/repository/org/apache/maven/doxia/doxia-module-fml/1.4/doxia-module-fml-1.4.jar
[ERROR] urls[31] =
file:/Users/myuser/.m2/repository/org/codehaus/plexus/plexus-i18n/1.0-beta-7/plexus-i18n-1.0-beta-7.jar
[ERROR] urls[32] =
file:/Users/myuser/.m2/repository/org/codehaus/plexus/plexus-velocity/1.1.7/plexus-velocity-1.1.7.jar
[ERROR] urls[33] =
file:/Users/myuser/.m2/repository/org/apache/velocity/velocity/1.5/velocity-1.5.jar
[ERROR] urls[34] = file:/Users/myuser/.m2
[jira] [Created] (MPMD-240) Migrate plugin to Maven 3.0
Matt Nelson created MPMD-240: Summary: Migrate plugin to Maven 3.0 Key: MPMD-240 URL: https://issues.apache.org/jira/browse/MPMD-240 Project: Maven PMD Plugin Issue Type: Bug Components: PMD Affects Versions: 3.8 Reporter: Matt Nelson Cloning from MCHECKSTYLE-335 to address the same slf4j issues based on the old maven-core-2.2.1 dependencies. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (MNG-6253) Replace CI friendly variables in pom.xml when installing/deploying
Christoph Amshoff created MNG-6253:
--
Summary: Replace CI friendly variables in pom.xml when
installing/deploying
Key: MNG-6253
URL: https://issues.apache.org/jira/browse/MNG-6253
Project: Maven
Issue Type: Bug
Affects Versions: 3.5.0
Reporter: Christoph Amshoff
When using variables in pom.xml to get CI friendly version
(https://maven.apache.org/maven-ci-friendly.html), these will not be replaced
in installed or deployed pom files, which makes them unusable for other builds.
Karl Heinz Marbaise suggested to use the flatten-maven-plugin to do the
property replacement
(http://blog.soebes.de/blog/2017/04/02/maven-pom-files-without-a-version-in-it/),
and this was also suggested as a workaround in other tickets (MDEPLOY-223 got
closed with "Not A Problem" solution).
That indeed works, but flatten-maven-plugin has to be manually configured in
the base POM, and additionally it changes the pom files in many other areas
which you would not want.
I honestly think that property replacement for the three allowed properties
({{$\{revision\}}}, {{$\{sha1\}}}, {{$\{changelist\}}}) should be done by Maven
internally without having the user configure other plugins. The feature is just
not correctly working without, so closing such issues with "Not A Problem" is
too little.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MNG-6253) Replace CI friendly variables in pom.xml when installing/deploying
[
https://issues.apache.org/jira/browse/MNG-6253?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16080384#comment-16080384
]
Christoph Amshoff commented on MNG-6253:
I just discovered there is a related issue for flatten-maven-plugin
(https://github.com/mojohaus/flatten-maven-plugin/issues/51), which is answered
by
{quote}
I think if maven started follow this way (support dynamic properties in
version) they have to complete their solution within deploy properly pom.xml
(with version replacement) to repository.
{quote}
> Replace CI friendly variables in pom.xml when installing/deploying
> --
>
> Key: MNG-6253
> URL: https://issues.apache.org/jira/browse/MNG-6253
> Project: Maven
> Issue Type: Bug
>Affects Versions: 3.5.0
>Reporter: Christoph Amshoff
>
> When using variables in pom.xml to get CI friendly version
> (https://maven.apache.org/maven-ci-friendly.html), these will not be replaced
> in installed or deployed pom files, which makes them unusable for other
> builds.
> Karl Heinz Marbaise suggested to use the flatten-maven-plugin to do the
> property replacement
> (http://blog.soebes.de/blog/2017/04/02/maven-pom-files-without-a-version-in-it/),
> and this was also suggested as a workaround in other tickets (MDEPLOY-223
> got closed with "Not A Problem" solution).
> That indeed works, but flatten-maven-plugin has to be manually configured in
> the base POM, and additionally it changes the pom files in many other areas
> which you would not want.
> I honestly think that property replacement for the three allowed properties
> ({{$\{revision\}}}, {{$\{sha1\}}}, {{$\{changelist\}}}) should be done by
> Maven internally without having the user configure other plugins. The feature
> is just not correctly working without, so closing such issues with "Not A
> Problem" is too little.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (MDEP-575) Inconsistent behaviour in dependency:sources between maven-dependency-plugin:2.10 and maven-dependency-plugin:3.0.z
Michal Jurc created MDEP-575:
Summary: Inconsistent behaviour in dependency:sources between
maven-dependency-plugin:2.10 and maven-dependency-plugin:3.0.z
Key: MDEP-575
URL: https://issues.apache.org/jira/browse/MDEP-575
Project: Maven Dependency Plugin
Issue Type: Bug
Components: sources
Affects Versions: 3.0.1, 3.0.0
Reporter: Michal Jurc
The {{dependency:sources}} goal behaves inconsistently between 2.10 and later
versions of the dependency plugin with dependencies provided by BOMs:
{code:title=mvn org.apache.maven.plugins:maven-dependency-plugin:2.10:sources}
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building WildFly Quickstart: helloworld 11.0.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-dependency-plugin:2.10:sources (default-cli) @ helloworld ---
[INFO]
[INFO] The following files have been resolved:
[INFO]
org.jboss.spec.javax.annotation:jboss-annotations-api_1.2_spec:jar:sources:1.0.0.Final:provided
[INFO]javax.enterprise:cdi-api:jar:sources:1.2:provided
[INFO]
org.jboss.spec.javax.servlet:jboss-servlet-api_3.1_spec:jar:sources:1.0.0.Final:provided
[INFO]javax.inject:javax.inject:jar:sources:1:provided
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 0.870 s
[INFO] Finished at: 2017-07-10T14:32:55+02:00
[INFO] Final Memory: 14M/298M
[INFO]
{code}
{code:title=mvn org.apache.maven.plugins:maven-dependency-plugin:3.0.z:sources}
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building WildFly Quickstart: helloworld 11.0.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-dependency-plugin:3.0.1:sources (default-cli) @ helloworld ---
[INFO]
[INFO] The following files have been resolved:
[INFO]javax.enterprise:cdi-api:jar:sources:1.2
[INFO]javax.inject:javax.inject:jar:sources:1
[INFO]
org.jboss.spec.javax.annotation:jboss-annotations-api_1.2_spec:jar:sources:1.0.0.Final
[INFO]
org.jboss.spec.javax.servlet:jboss-servlet-api_3.1_spec:jar:sources:1.0.0.Final
[INFO]
[INFO] The following files have NOT been resolved:
[INFO]javax.enterprise:cdi-api:jar:1.2:provided
[INFO]javax.inject:javax.inject:jar:1:provided
[INFO]
org.jboss.spec.javax.annotation:jboss-annotations-api_1.2_spec:jar:1.0.0.Final:provided
[INFO]
org.jboss.spec.javax.servlet:jboss-servlet-api_3.1_spec:jar:1.0.0.Final:provided
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 0.815 s
[INFO] Finished at: 2017-07-10T14:33:07+02:00
[INFO] Final Memory: 13M/298M
[INFO]
{code}
The used project can be found
[here|https://github.com/wildfly/quickstart/tree/11.x/helloworld].
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Updated] (MDEP-575) Inconsistent behaviour in dependency:sources between maven-dependency-plugin:2.10 and maven-dependency-plugin:3.0.z
[
https://issues.apache.org/jira/browse/MDEP-575?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michal Jurc updated MDEP-575:
-
Description:
The {{dependency:sources}} goal behaves inconsistently between 2.10 and later
versions of the dependency plugin with dependencies provided by BOMs:
{code:title=mvn org.apache.maven.plugins:maven-dependency-plugin:2.10:sources}
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building WildFly Quickstart: helloworld 11.0.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-dependency-plugin:2.10:sources (default-cli) @ helloworld ---
[INFO]
[INFO] The following files have been resolved:
[INFO]
org.jboss.spec.javax.annotation:jboss-annotations-api_1.2_spec:jar:sources:1.0.0.Final:provided
[INFO]javax.enterprise:cdi-api:jar:sources:1.2:provided
[INFO]
org.jboss.spec.javax.servlet:jboss-servlet-api_3.1_spec:jar:sources:1.0.0.Final:provided
[INFO]javax.inject:javax.inject:jar:sources:1:provided
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 0.870 s
[INFO] Finished at: 2017-07-10T14:32:55+02:00
[INFO] Final Memory: 14M/298M
[INFO]
{code}
{code:title=mvn org.apache.maven.plugins:maven-dependency-plugin:3.0.z:sources}
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building WildFly Quickstart: helloworld 11.0.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-dependency-plugin:3.0.1:sources (default-cli) @ helloworld ---
[INFO]
[INFO] The following files have been resolved:
[INFO]javax.enterprise:cdi-api:jar:sources:1.2
[INFO]javax.inject:javax.inject:jar:sources:1
[INFO]
org.jboss.spec.javax.annotation:jboss-annotations-api_1.2_spec:jar:sources:1.0.0.Final
[INFO]
org.jboss.spec.javax.servlet:jboss-servlet-api_3.1_spec:jar:sources:1.0.0.Final
[INFO]
[INFO] The following files have NOT been resolved:
[INFO]javax.enterprise:cdi-api:jar:1.2:provided
[INFO]javax.inject:javax.inject:jar:1:provided
[INFO]
org.jboss.spec.javax.annotation:jboss-annotations-api_1.2_spec:jar:1.0.0.Final:provided
[INFO]
org.jboss.spec.javax.servlet:jboss-servlet-api_3.1_spec:jar:1.0.0.Final:provided
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 0.815 s
[INFO] Finished at: 2017-07-10T14:33:07+02:00
[INFO] Final Memory: 13M/298M
[INFO]
{code}
The project used can be found
[here|https://github.com/wildfly/quickstart/tree/11.x/helloworld].
was:
The {{dependency:sources}} goal behaves inconsistently between 2.10 and later
versions of the dependency plugin with dependencies provided by BOMs:
{code:title=mvn org.apache.maven.plugins:maven-dependency-plugin:2.10:sources}
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building WildFly Quickstart: helloworld 11.0.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-dependency-plugin:2.10:sources (default-cli) @ helloworld ---
[INFO]
[INFO] The following files have been resolved:
[INFO]
org.jboss.spec.javax.annotation:jboss-annotations-api_1.2_spec:jar:sources:1.0.0.Final:provided
[INFO]javax.enterprise:cdi-api:jar:sources:1.2:provided
[INFO]
org.jboss.spec.javax.servlet:jboss-servlet-api_3.1_spec:jar:sources:1.0.0.Final:provided
[INFO]javax.inject:javax.inject:jar:sources:1:provided
[INFO]
[INFO]
[INFO] BUILD SUCCESS
[INFO]
[INFO] Total time: 0.870 s
[INFO] Finished at: 2017-07-10T14:32:55+02:00
[INFO] Final Memory: 14M/298M
[INFO]
{code}
{code:title=mvn org.apache.maven.plugins:maven-dependency-plugin:3.0.z:sources}
[INFO] Scanning for projects...
[INFO]
[INFO]
[INFO] Building WildFly Quickstart: helloworld 11.0.0-SNAPSHOT
[INFO]
[INFO]
[INFO] --- maven-dependency-plugin:3.0.1:sources (default-cli) @ helloworld ---
[INFO]
[INFO] The following files have been resolved:
[INFO]javax.en
[jira] [Issue Comment Deleted] (ARCHETYPE-488) Goal integration-test of maven-archetype-plugin fails with 'Cannot run additions goals." in version 3.3.1
[
https://issues.apache.org/jira/browse/ARCHETYPE-488?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukasz Lech updated ARCHETYPE-488:
--
Comment: was deleted
(was: Is there any solution that does not 'work for me' but simply works?
With 3.3.9 I got the error even with 'pom hack' from Alexis Resendiz Andrade
and building with -U flag.
{{[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare (default-cli) on
project parent: Failed to invoke Maven build. Error configuring command-line.
Reason: Maven executable not found at: D:\apache\apache-maven-3.3.9\bin\mvn.bat
-> [Help 1]}}
If you feel that having mvn.bat is a solution, than add it to the distribution.)
> Goal integration-test of maven-archetype-plugin fails with 'Cannot run
> additions goals." in version 3.3.1
> -
>
> Key: ARCHETYPE-488
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-488
> Project: Maven Archetype
> Issue Type: Bug
> Components: Plugin
>Affects Versions: 2.4
> Environment: maven-archetype-plugin 2.3
>Reporter: Andreas Horst
>Assignee: Robert Scholte
> Labels: archetype, integration-test
> Fix For: 3.0.0
>
>
> Running the goal 'integration-test' of the 'maven-archetype-plugin' fails
> with the following output:
> {noformat}
> [INFO] Invoking post-archetype-generation goals: verify
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 2.048 s
> [INFO] Finished at: 2015-04-23T18:17:07+02:00
> [INFO] Final Memory: 18M/309M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-archetype-plugin:2.3:integration-test
> (default-integration-test) on project simple-archetype:
> [ERROR] Archetype IT 'it' failed: Cannot run additions goals.
> [ERROR] -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-archetype-plugin:2.3:integration-test
> (default-integration-test) on project simple-archetype:
> Archetype IT 'it' failed: Cannot run additions goals.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> 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:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:862)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:197)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> 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:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.MojoExecutionException:
> Archetype IT 'it' failed: Cannot run additions goals.
> at
> org.apache.maven.archetype.mojos.IntegrationTestMojo.execute(IntegrationTestMojo.java:258)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 20 more
> [ERROR]
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> re
[jira] [Commented] (MNG-6204) Exception when parsing
[
https://issues.apache.org/jira/browse/MNG-6204?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16080028#comment-16080028
]
Michal Domagala commented on MNG-6204:
--
Fixed in plexus, see https://github.com/codehaus-plexus/plexus-utils/issues/22
> Exception when parsing
>
> Key: MNG-6204
> URL: https://issues.apache.org/jira/browse/MNG-6204
> Project: Maven
> Issue Type: Bug
> Components: Bootstrap & Build
>Affects Versions: 3.3.9, 3.5.0-alpha-1, 3.5.0-beta-1
> Environment: Windows 7
>Reporter: Robert Kleinschmager
> Attachments: debug.log, pom.xml
>
>
> Parsing large pom.xml (>8kb), which contains * Steps
> ** use given !pom.xml!
> ** execute {{mvn validate}}
> * Expected
> ** pass
> * Actual
> ** {code}
> Caused by: java.lang.ArrayIndexOutOfBoundsException: 10106
> at
> org.codehaus.plexus.util.xml.pull.MXParser.parsePI(MXParser.java:2502)
> {code}
> ** see !debug.log!
> * this is caused by [plexus-utils issue no
> 22|https://github.com/codehaus-plexus/plexus-utils/issues/22]
> ** PR must be merged
> [PR#23|https://github.com/codehaus-plexus/plexus-utils/pull/23]
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (ARCHETYPE-488) Goal integration-test of maven-archetype-plugin fails with 'Cannot run additions goals." in version 3.3.1
[
https://issues.apache.org/jira/browse/ARCHETYPE-488?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16080031#comment-16080031
]
Lukasz Lech commented on ARCHETYPE-488:
---
Is there any solution that does not 'work for me' but simply works?
With 3.3.9 I got the error even with 'pom hack' from Alexis Resendiz Andrade
and building with -U flag.
{{[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-release-plugin:2.3.2:prepare (default-cli) on
project parent: Failed to invoke Maven build. Error configuring command-line.
Reason: Maven executable not found at: D:\apache\apache-maven-3.3.9\bin\mvn.bat
-> [Help 1]}}
If you feel that having mvn.bat is a solution, than add it to the distribution.
> Goal integration-test of maven-archetype-plugin fails with 'Cannot run
> additions goals." in version 3.3.1
> -
>
> Key: ARCHETYPE-488
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-488
> Project: Maven Archetype
> Issue Type: Bug
> Components: Plugin
>Affects Versions: 2.4
> Environment: maven-archetype-plugin 2.3
>Reporter: Andreas Horst
>Assignee: Robert Scholte
> Labels: archetype, integration-test
> Fix For: 3.0.0
>
>
> Running the goal 'integration-test' of the 'maven-archetype-plugin' fails
> with the following output:
> {noformat}
> [INFO] Invoking post-archetype-generation goals: verify
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 2.048 s
> [INFO] Finished at: 2015-04-23T18:17:07+02:00
> [INFO] Final Memory: 18M/309M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-archetype-plugin:2.3:integration-test
> (default-integration-test) on project simple-archetype:
> [ERROR] Archetype IT 'it' failed: Cannot run additions goals.
> [ERROR] -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-archetype-plugin:2.3:integration-test
> (default-integration-test) on project simple-archetype:
> Archetype IT 'it' failed: Cannot run additions goals.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:216)
> 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:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:862)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:286)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:197)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> 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:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: org.apache.maven.plugin.MojoExecutionException:
> Archetype IT 'it' failed: Cannot run additions goals.
> at
> org.apache.maven.archetype.mojos.IntegrationTestMojo.execute(IntegrationTestMojo.java:258)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 20 more
> [ERROR]
> [ERROR]
> [ERROR] For more information about the errors and possibl
