[jira] [Created] (MEAR-247) resource-ref in generated application.xml
Yannick Majoros created MEAR-247: Summary: resource-ref in generated application.xml Key: MEAR-247 URL: https://issues.apache.org/jira/browse/MEAR-247 Project: Maven Ear Plugin Issue Type: New Feature Reporter: Yannick Majoros It seems more people would like to have that. I have 5 applications sharing the same persistence module and needing some resource-ref to have different db connections (dba requirement :-( ). Seems more people would want it: http://stackoverflow.com/questions/26113079/resource-ref-in-maven-generated-application-descriptor http://stackoverflow.com/questions/33520956/generate-resource-env-ref-entries-in-maven-ear-plugin-generated-application-xml -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Comment Edited] (SUREFIRE-1343) Failsafe ignores classesDirectory
[
https://issues.apache.org/jira/browse/SUREFIRE-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927208#comment-15927208
]
Jakob Oswald edited comment on SUREFIRE-1343 at 3/16/17 8:44 AM:
-
I understand the preference of loading classes from the packaged artifact.
However I would like to use instrumented classes to record coverage for
integration tests. I would expect failsafe to respect my choice if I explicitly
set the classesDirectory parameter and not just ignoring it. What else would be
the recommended scenario here? Would I have to package an additional jar with
the instrumented classes and move the jars around?
EDIT: Is there any good argument to not implement it like [~pwebb] suggested in
SUREFIRE-1198?
This would:
* Allow users to explicitly chooser their artifact or classes directory (which
in my opinion exist valid reasons to do so)
* Keep backwards compatibility to {{2.18.x}}
* Still load the packaged artifact by default
was (Author: jakob_oswald):
I understand the preference of loading classes from the packaged artifact.
However I would like to use instrumented classes to record coverage for
integration tests. I would expect failsafe to respect my choice if I explicitly
set the classesDirectory parameter and not just ignoring it. What else would be
the recommended scenario here? Would I have to package an additional jar with
the instrumented classes and move the jars around?
> Failsafe ignores classesDirectory
> -
>
> Key: SUREFIRE-1343
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1343
> Project: Maven Surefire
> Issue Type: Bug
> Components: classloading
>Affects Versions: 2.19.1
>Reporter: Jakob Oswald
>
> The maven failsafe pluging ignores the property in
> versions 2.19.x version 2.18.1 works as expected / documented.
> Config:
> {code:xml}
> ...
>
> ${project.build.directory}/classes
>
> ...
> {code}
> Cmd:
> mvn -X clean verify
> Output:
> 2.18.1
> [DEBUG] boot classpath:
> /home/jakob/.m2/repository/org/apache/maven/surefire/surefire-booter/2.18.1/surefire-booter-2.18.1.jar
> /home/jakob/.m2/repository/org/apache/maven/surefire/surefire-api/2.18.1/surefire-api-2.18.1.jar
> /home/jakob/source/java/qualinsight-mojo-cobertura-test/target/test-classes
> /home/jakob/source/java/qualinsight-mojo-cobertura-test/target/classes
> ...
> 2.19.1
> [DEBUG] boot classpath:
> /home/jakob/.m2/repository/org/apache/maven/surefire/surefire-booter/2.19.1/surefire-booter-2.19.1.jar
> /home/jakob/.m2/repository/org/apache/maven/surefire/surefire-api/2.19.1/surefire-api-2.19.1.jar
> /home/jakob/source/java/qualinsight-mojo-cobertura-test/target/test-classes
> /home/jakob/source/java/qualinsight-mojo-cobertura-test/target/qualinsight-mojo-cobertura-test-0.0.1-SNAPSHOT.jar
> ...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (SUREFIRE-1343) Failsafe ignores classesDirectory
[
https://issues.apache.org/jira/browse/SUREFIRE-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927208#comment-15927208
]
Jakob Oswald edited comment on SUREFIRE-1343 at 3/16/17 8:48 AM:
-
I understand the preference of loading classes from the packaged artifact.
However I would like to use instrumented classes to record coverage for
integration tests. I would expect failsafe to respect my choice if I explicitly
set the classesDirectory parameter and not just ignoring it. What else would be
the recommended scenario here? Would I have to package an additional jar with
the instrumented classes and move the jars around?
EDIT: Is there any good argument to not implement it like [~pwebb] suggested in
SUREFIRE-1198?
This would:
* Allow users to explicitly choose their artifact or classes directory (which
in my opinion exist valid reasons to do so)
* Keep backwards compatibility to {{2.18.x}}
* Still load the packaged artifact by default
was (Author: jakob_oswald):
I understand the preference of loading classes from the packaged artifact.
However I would like to use instrumented classes to record coverage for
integration tests. I would expect failsafe to respect my choice if I explicitly
set the classesDirectory parameter and not just ignoring it. What else would be
the recommended scenario here? Would I have to package an additional jar with
the instrumented classes and move the jars around?
EDIT: Is there any good argument to not implement it like [~pwebb] suggested in
SUREFIRE-1198?
This would:
* Allow users to explicitly chooser their artifact or classes directory (which
in my opinion exist valid reasons to do so)
* Keep backwards compatibility to {{2.18.x}}
* Still load the packaged artifact by default
> Failsafe ignores classesDirectory
> -
>
> Key: SUREFIRE-1343
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1343
> Project: Maven Surefire
> Issue Type: Bug
> Components: classloading
>Affects Versions: 2.19.1
>Reporter: Jakob Oswald
>
> The maven failsafe pluging ignores the property in
> versions 2.19.x version 2.18.1 works as expected / documented.
> Config:
> {code:xml}
> ...
>
> ${project.build.directory}/classes
>
> ...
> {code}
> Cmd:
> mvn -X clean verify
> Output:
> 2.18.1
> [DEBUG] boot classpath:
> /home/jakob/.m2/repository/org/apache/maven/surefire/surefire-booter/2.18.1/surefire-booter-2.18.1.jar
> /home/jakob/.m2/repository/org/apache/maven/surefire/surefire-api/2.18.1/surefire-api-2.18.1.jar
> /home/jakob/source/java/qualinsight-mojo-cobertura-test/target/test-classes
> /home/jakob/source/java/qualinsight-mojo-cobertura-test/target/classes
> ...
> 2.19.1
> [DEBUG] boot classpath:
> /home/jakob/.m2/repository/org/apache/maven/surefire/surefire-booter/2.19.1/surefire-booter-2.19.1.jar
> /home/jakob/.m2/repository/org/apache/maven/surefire/surefire-api/2.19.1/surefire-api-2.19.1.jar
> /home/jakob/source/java/qualinsight-mojo-cobertura-test/target/test-classes
> /home/jakob/source/java/qualinsight-mojo-cobertura-test/target/qualinsight-mojo-cobertura-test-0.0.1-SNAPSHOT.jar
> ...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (SUREFIRE-1343) Failsafe ignores classesDirectory
[
https://issues.apache.org/jira/browse/SUREFIRE-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15927208#comment-15927208
]
Jakob Oswald edited comment on SUREFIRE-1343 at 3/16/17 8:48 AM:
-
I understand the preference of loading classes from the packaged artifact.
However I would like to use instrumented classes to record coverage for
integration tests. I would expect failsafe to respect my choice if I explicitly
set the {{classesDirectory}} parameter and not just ignoring it. What else
would be the recommended scenario here? Would I have to package an additional
jar with the instrumented classes and move the jars around?
EDIT: Is there any good argument to not implement it like [~pwebb] suggested in
SUREFIRE-1198?
This would:
* Allow users to explicitly choose their artifact or classes directory (which
in my opinion exist valid reasons to do so)
* Keep backwards compatibility to {{2.18.x}}
* Still load the packaged artifact by default
was (Author: jakob_oswald):
I understand the preference of loading classes from the packaged artifact.
However I would like to use instrumented classes to record coverage for
integration tests. I would expect failsafe to respect my choice if I explicitly
set the classesDirectory parameter and not just ignoring it. What else would be
the recommended scenario here? Would I have to package an additional jar with
the instrumented classes and move the jars around?
EDIT: Is there any good argument to not implement it like [~pwebb] suggested in
SUREFIRE-1198?
This would:
* Allow users to explicitly choose their artifact or classes directory (which
in my opinion exist valid reasons to do so)
* Keep backwards compatibility to {{2.18.x}}
* Still load the packaged artifact by default
> Failsafe ignores classesDirectory
> -
>
> Key: SUREFIRE-1343
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1343
> Project: Maven Surefire
> Issue Type: Bug
> Components: classloading
>Affects Versions: 2.19.1
>Reporter: Jakob Oswald
>
> The maven failsafe pluging ignores the property in
> versions 2.19.x version 2.18.1 works as expected / documented.
> Config:
> {code:xml}
> ...
>
> ${project.build.directory}/classes
>
> ...
> {code}
> Cmd:
> mvn -X clean verify
> Output:
> 2.18.1
> [DEBUG] boot classpath:
> /home/jakob/.m2/repository/org/apache/maven/surefire/surefire-booter/2.18.1/surefire-booter-2.18.1.jar
> /home/jakob/.m2/repository/org/apache/maven/surefire/surefire-api/2.18.1/surefire-api-2.18.1.jar
> /home/jakob/source/java/qualinsight-mojo-cobertura-test/target/test-classes
> /home/jakob/source/java/qualinsight-mojo-cobertura-test/target/classes
> ...
> 2.19.1
> [DEBUG] boot classpath:
> /home/jakob/.m2/repository/org/apache/maven/surefire/surefire-booter/2.19.1/surefire-booter-2.19.1.jar
> /home/jakob/.m2/repository/org/apache/maven/surefire/surefire-api/2.19.1/surefire-api-2.19.1.jar
> /home/jakob/source/java/qualinsight-mojo-cobertura-test/target/test-classes
> /home/jakob/source/java/qualinsight-mojo-cobertura-test/target/qualinsight-mojo-cobertura-test-0.0.1-SNAPSHOT.jar
> ...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MDEP-558) Dependency version from test scope leaks into compile scope
[
https://issues.apache.org/jira/browse/MDEP-558?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Andrei Tomashpolskiy updated MDEP-558:
--
Component/s: (was: analyze)
tree
> Dependency version from test scope leaks into compile scope
> ---
>
> Key: MDEP-558
> URL: https://issues.apache.org/jira/browse/MDEP-558
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: tree
>Affects Versions: 2.8, 2.10, 3.0.0
>Reporter: Andrei Tomashpolskiy
>
> Despite test scope being non-transitive [1] it's still used to resolve
> versions of compile dependencies. This might be causing issues in IDEs that
> rely on the Dependency plugin to assemble the application's classpath.
> E.g. for the following project configuration *javax.servlet-api* version is
> resolved to *3.0.1* (using nearest-first strategy to resolve conflicts):
> {noformat}
> project1
> |-- project2:compile
> |..|-- jetty-server:compile
> ||-- javax.servlet-api:3.1.0:compile
> |-- jersey-test-framework-core:test
> |..|-- javax.servlet-api:3.0.1:compile
> {noformat}
> My understanding is that it should rather be resolved to 3.1.0, because
> version 3.0.1 stems from the test scope and should be ignored (AFAIK Maven
> Shade plugin works in that way).
> Please see a runnable code example in
> https://github.com/atomashpolskiy/maven-transitive-test-dependencies
> Thank you!
> [1]
> http://maven.apache.org/guides/introduction/introduction-to-dependency-mechanism.html
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (MINDEXER-97) Add OSGi 5.0 MANIFEST headers to OsgiArtifactIndexCreator
[ https://issues.apache.org/jira/browse/MINDEXER-97?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928062#comment-15928062 ] Simon Spero commented on MINDEXER-97: - An important addition to the manifest headers is the artifact SHA-256, which is required for content. Since full SHA-1 has now fallen, this wouldn't be of value only to OSGI. Furthermore, the deprecated Export-Service header is indexed (though Import-Service isn't). Both these headers were never used by any resolvers, which is why they could be deprecated. I can make these changes and submit a pull request from github. I'm not sure if I can make it track this issue. When is the next release scheduled, and would a changed version be likely to be used on maven central relatively soon thereafter? > Add OSGi 5.0 MANIFEST headers to OsgiArtifactIndexCreator > - > > Key: MINDEXER-97 > URL: https://issues.apache.org/jira/browse/MINDEXER-97 > Project: Maven Indexer > Issue Type: Improvement >Reporter: Balazs Zsoldos > > It would be extremely useful if the following MANIFEST headers were added to > the index: > - Require-Capability > - Provide-Capability > - DynamicImport-Package > Especially the first two would be necessary to be able to build up a database > that helps finding dependencies for unsatisfied bundles. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (SUREFIRE-1343) Failsafe ignores classesDirectory
[
https://issues.apache.org/jira/browse/SUREFIRE-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928807#comment-15928807
]
Tibor Digana commented on SUREFIRE-1343:
[~jakob_oswald]
I fixed this problem and classes directory is used if you specify configuration
parameter {{classesDirectory}}.
We will rename Version 2.19.2 to 2.20 and start a new release vote.
> Failsafe ignores classesDirectory
> -
>
> Key: SUREFIRE-1343
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1343
> Project: Maven Surefire
> Issue Type: Bug
> Components: classloading
>Affects Versions: 2.19.1
>Reporter: Jakob Oswald
>
> The maven failsafe pluging ignores the property in
> versions 2.19.x version 2.18.1 works as expected / documented.
> Config:
> {code:xml}
> ...
>
> ${project.build.directory}/classes
>
> ...
> {code}
> Cmd:
> mvn -X clean verify
> Output:
> 2.18.1
> [DEBUG] boot classpath:
> /home/jakob/.m2/repository/org/apache/maven/surefire/surefire-booter/2.18.1/surefire-booter-2.18.1.jar
> /home/jakob/.m2/repository/org/apache/maven/surefire/surefire-api/2.18.1/surefire-api-2.18.1.jar
> /home/jakob/source/java/qualinsight-mojo-cobertura-test/target/test-classes
> /home/jakob/source/java/qualinsight-mojo-cobertura-test/target/classes
> ...
> 2.19.1
> [DEBUG] boot classpath:
> /home/jakob/.m2/repository/org/apache/maven/surefire/surefire-booter/2.19.1/surefire-booter-2.19.1.jar
> /home/jakob/.m2/repository/org/apache/maven/surefire/surefire-api/2.19.1/surefire-api-2.19.1.jar
> /home/jakob/source/java/qualinsight-mojo-cobertura-test/target/test-classes
> /home/jakob/source/java/qualinsight-mojo-cobertura-test/target/qualinsight-mojo-cobertura-test-0.0.1-SNAPSHOT.jar
> ...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (SUREFIRE-1343) Failsafe ignores classesDirectory
[
https://issues.apache.org/jira/browse/SUREFIRE-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928863#comment-15928863
]
Jakob Oswald commented on SUREFIRE-1343:
That's great news. Thank you very much and feel free to close this issue then.
> Failsafe ignores classesDirectory
> -
>
> Key: SUREFIRE-1343
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1343
> Project: Maven Surefire
> Issue Type: Bug
> Components: classloading
>Affects Versions: 2.19.1
>Reporter: Jakob Oswald
>
> The maven failsafe pluging ignores the property in
> versions 2.19.x version 2.18.1 works as expected / documented.
> Config:
> {code:xml}
> ...
>
> ${project.build.directory}/classes
>
> ...
> {code}
> Cmd:
> mvn -X clean verify
> Output:
> 2.18.1
> [DEBUG] boot classpath:
> /home/jakob/.m2/repository/org/apache/maven/surefire/surefire-booter/2.18.1/surefire-booter-2.18.1.jar
> /home/jakob/.m2/repository/org/apache/maven/surefire/surefire-api/2.18.1/surefire-api-2.18.1.jar
> /home/jakob/source/java/qualinsight-mojo-cobertura-test/target/test-classes
> /home/jakob/source/java/qualinsight-mojo-cobertura-test/target/classes
> ...
> 2.19.1
> [DEBUG] boot classpath:
> /home/jakob/.m2/repository/org/apache/maven/surefire/surefire-booter/2.19.1/surefire-booter-2.19.1.jar
> /home/jakob/.m2/repository/org/apache/maven/surefire/surefire-api/2.19.1/surefire-api-2.19.1.jar
> /home/jakob/source/java/qualinsight-mojo-cobertura-test/target/test-classes
> /home/jakob/source/java/qualinsight-mojo-cobertura-test/target/qualinsight-mojo-cobertura-test-0.0.1-SNAPSHOT.jar
> ...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Assigned] (SUREFIRE-1343) Failsafe ignores classesDirectory
[
https://issues.apache.org/jira/browse/SUREFIRE-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana reassigned SUREFIRE-1343:
--
Assignee: Tibor Digana
> Failsafe ignores classesDirectory
> -
>
> Key: SUREFIRE-1343
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1343
> Project: Maven Surefire
> Issue Type: Bug
> Components: classloading
>Affects Versions: 2.19.1
>Reporter: Jakob Oswald
>Assignee: Tibor Digana
>
> The maven failsafe pluging ignores the property in
> versions 2.19.x version 2.18.1 works as expected / documented.
> Config:
> {code:xml}
> ...
>
> ${project.build.directory}/classes
>
> ...
> {code}
> Cmd:
> mvn -X clean verify
> Output:
> 2.18.1
> [DEBUG] boot classpath:
> /home/jakob/.m2/repository/org/apache/maven/surefire/surefire-booter/2.18.1/surefire-booter-2.18.1.jar
> /home/jakob/.m2/repository/org/apache/maven/surefire/surefire-api/2.18.1/surefire-api-2.18.1.jar
> /home/jakob/source/java/qualinsight-mojo-cobertura-test/target/test-classes
> /home/jakob/source/java/qualinsight-mojo-cobertura-test/target/classes
> ...
> 2.19.1
> [DEBUG] boot classpath:
> /home/jakob/.m2/repository/org/apache/maven/surefire/surefire-booter/2.19.1/surefire-booter-2.19.1.jar
> /home/jakob/.m2/repository/org/apache/maven/surefire/surefire-api/2.19.1/surefire-api-2.19.1.jar
> /home/jakob/source/java/qualinsight-mojo-cobertura-test/target/test-classes
> /home/jakob/source/java/qualinsight-mojo-cobertura-test/target/qualinsight-mojo-cobertura-test-0.0.1-SNAPSHOT.jar
> ...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (SUREFIRE-1343) Failsafe ignores classesDirectory
[
https://issues.apache.org/jira/browse/SUREFIRE-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15928907#comment-15928907
]
Tibor Digana commented on SUREFIRE-1343:
[~jakob_oswald]
Feel free to reopen the issue if you need our support.
> Failsafe ignores classesDirectory
> -
>
> Key: SUREFIRE-1343
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1343
> Project: Maven Surefire
> Issue Type: Bug
> Components: classloading
>Affects Versions: 2.19.1
>Reporter: Jakob Oswald
>
> The maven failsafe pluging ignores the property in
> versions 2.19.x version 2.18.1 works as expected / documented.
> Config:
> {code:xml}
> ...
>
> ${project.build.directory}/classes
>
> ...
> {code}
> Cmd:
> mvn -X clean verify
> Output:
> 2.18.1
> [DEBUG] boot classpath:
> /home/jakob/.m2/repository/org/apache/maven/surefire/surefire-booter/2.18.1/surefire-booter-2.18.1.jar
> /home/jakob/.m2/repository/org/apache/maven/surefire/surefire-api/2.18.1/surefire-api-2.18.1.jar
> /home/jakob/source/java/qualinsight-mojo-cobertura-test/target/test-classes
> /home/jakob/source/java/qualinsight-mojo-cobertura-test/target/classes
> ...
> 2.19.1
> [DEBUG] boot classpath:
> /home/jakob/.m2/repository/org/apache/maven/surefire/surefire-booter/2.19.1/surefire-booter-2.19.1.jar
> /home/jakob/.m2/repository/org/apache/maven/surefire/surefire-api/2.19.1/surefire-api-2.19.1.jar
> /home/jakob/source/java/qualinsight-mojo-cobertura-test/target/test-classes
> /home/jakob/source/java/qualinsight-mojo-cobertura-test/target/qualinsight-mojo-cobertura-test-0.0.1-SNAPSHOT.jar
> ...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Closed] (SUREFIRE-1343) Failsafe ignores classesDirectory
[
https://issues.apache.org/jira/browse/SUREFIRE-1343?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana closed SUREFIRE-1343.
--
Resolution: Duplicate
> Failsafe ignores classesDirectory
> -
>
> Key: SUREFIRE-1343
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1343
> Project: Maven Surefire
> Issue Type: Bug
> Components: classloading
>Affects Versions: 2.19.1
>Reporter: Jakob Oswald
>Assignee: Tibor Digana
>
> The maven failsafe pluging ignores the property in
> versions 2.19.x version 2.18.1 works as expected / documented.
> Config:
> {code:xml}
> ...
>
> ${project.build.directory}/classes
>
> ...
> {code}
> Cmd:
> mvn -X clean verify
> Output:
> 2.18.1
> [DEBUG] boot classpath:
> /home/jakob/.m2/repository/org/apache/maven/surefire/surefire-booter/2.18.1/surefire-booter-2.18.1.jar
> /home/jakob/.m2/repository/org/apache/maven/surefire/surefire-api/2.18.1/surefire-api-2.18.1.jar
> /home/jakob/source/java/qualinsight-mojo-cobertura-test/target/test-classes
> /home/jakob/source/java/qualinsight-mojo-cobertura-test/target/classes
> ...
> 2.19.1
> [DEBUG] boot classpath:
> /home/jakob/.m2/repository/org/apache/maven/surefire/surefire-booter/2.19.1/surefire-booter-2.19.1.jar
> /home/jakob/.m2/repository/org/apache/maven/surefire/surefire-api/2.19.1/surefire-api-2.19.1.jar
> /home/jakob/source/java/qualinsight-mojo-cobertura-test/target/test-classes
> /home/jakob/source/java/qualinsight-mojo-cobertura-test/target/qualinsight-mojo-cobertura-test-0.0.1-SNAPSHOT.jar
> ...
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (DOXIATOOLS-56) doxia-book-renderer has unit test errors
Archimedes Trajano created DOXIATOOLS-56: Summary: doxia-book-renderer has unit test errors Key: DOXIATOOLS-56 URL: https://issues.apache.org/jira/browse/DOXIATOOLS-56 Project: Maven Doxia Tools Issue Type: Bug Components: Doxia Book Renderer Affects Versions: doxia-book-renderer-1.2 Reporter: Archimedes Trajano When building the there is an error in one of the unit tests yielding junit.framework.ComparisonFailure: Wrong figure! expected:<...ileref="figure.jpg" format="JPG...> but was:<...ormat="JPG" fileref="figure.jpg...> Seen here https://travis-ci.org/trajano/maven-doxia-tools/builds/211909987#L1513 The error appears to be that the order of attributes is different, but since it is XML it really should not matter and the unit test framework should allow that. However, the code is not compatible with the current version of Doxia and stops working past version 1.4. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MRESOLVER-11) Project dependency collection result should contain repositories.
[ https://issues.apache.org/jira/browse/MRESOLVER-11?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15929068#comment-15929068 ] Hudson commented on MRESOLVER-11: - SUCCESS: Integrated in Jenkins build maven-resolver #45 (See [https://builds.apache.org/job/maven-resolver/45/]) [MRESOLVER-11] Project dependency collection result should contain (schulte: [http://git-wip-us.apache.org/repos/asf/?p=maven-resolver.git&a=commit&h=101f5342269fa28d1cb41313d6fd7282ba87019c]) * (edit) maven-resolver-impl/src/main/java/org/eclipse/aether/internal/impl/DefaultDependencyCollector.java > Project dependency collection result should contain repositories. > - > > Key: MRESOLVER-11 > URL: https://issues.apache.org/jira/browse/MRESOLVER-11 > Project: Maven Resolver > Issue Type: Bug >Reporter: Christian Schulte >Assignee: Christian Schulte > Fix For: Maven Artifact Resolver 1.2.0 pre-reset > > > The resolution result provided when performing project dependency collection > is lacking the repositories from the collection request. Components the > project root node is passed to (transformers, for example), expect this > information to be provided. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MRESOLVER-14) Statistics should be calculated using System.nanoTime instead of System.currentTimeMillis.
[ https://issues.apache.org/jira/browse/MRESOLVER-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15929069#comment-15929069 ] Hudson commented on MRESOLVER-14: - SUCCESS: Integrated in Jenkins build maven-resolver #45 (See [https://builds.apache.org/job/maven-resolver/45/]) [MRESOLVER-14] Statistics should be calculated using System.nanoTime (schulte: [http://git-wip-us.apache.org/repos/asf/?p=maven-resolver.git&a=commit&h=9bf6abff705f84327de94bf5c85ee0a98c814c2e]) * (edit) maven-resolver-util/src/main/java/org/eclipse/aether/util/graph/transformer/ConflictMarker.java * (edit) maven-resolver-impl/src/main/java/org/eclipse/aether/internal/impl/DefaultDependencyCollector.java * (edit) maven-resolver-util/src/main/java/org/eclipse/aether/util/graph/transformer/ConflictIdSorter.java * (edit) maven-resolver-util/src/main/java/org/eclipse/aether/util/graph/transformer/ConflictResolver.java > Statistics should be calculated using System.nanoTime instead of > System.currentTimeMillis. > -- > > Key: MRESOLVER-14 > URL: https://issues.apache.org/jira/browse/MRESOLVER-14 > Project: Maven Resolver > Issue Type: Bug >Reporter: Christian Schulte >Assignee: Christian Schulte > Fix For: Maven Artifact Resolver 1.2.0 pre-reset > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MRESOLVER-13) Exceptions are suppressed incorrectly when closing resources fails.
[ https://issues.apache.org/jira/browse/MRESOLVER-13?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15929139#comment-15929139 ] Hudson commented on MRESOLVER-13: - SUCCESS: Integrated in Jenkins build maven-resolver #46 (See [https://builds.apache.org/job/maven-resolver/46/]) [MRESOLVER-13] Exceptions are suppressed incorrectly when closing (schulte: [http://git-wip-us.apache.org/repos/asf/?p=maven-resolver.git&a=commit&h=ad50215d27feede0ad0e5eb83ae96c6d6fdcc639]) * (edit) maven-resolver-connector-basic/src/main/java/org/eclipse/aether/connector/basic/ChecksumCalculator.java * (edit) maven-resolver-spi/src/main/java/org/eclipse/aether/spi/connector/transport/AbstractTransporter.java * (edit) maven-resolver-test-util/src/main/java/org/eclipse/aether/internal/test/util/TestFileProcessor.java * (edit) maven-resolver-util/src/main/java/org/eclipse/aether/util/ChecksumUtils.java * (edit) maven-resolver-test-util/src/main/java/org/eclipse/aether/internal/test/util/IniArtifactDataReader.java * (edit) maven-resolver-transport-wagon/src/main/java/org/eclipse/aether/transport/wagon/WagonTransporter.java * (edit) maven-resolver-impl/src/main/java/org/eclipse/aether/internal/impl/DefaultFileProcessor.java * (edit) maven-resolver-transport-http/src/test/java/org/eclipse/aether/transport/http/HttpServer.java * (edit) maven-resolver-connector-basic/src/main/java/org/eclipse/aether/connector/basic/PartialFile.java * (edit) maven-resolver-test-util/src/main/java/org/eclipse/aether/internal/test/util/DependencyGraphParser.java * (edit) maven-resolver-test-util/src/main/java/org/eclipse/aether/internal/test/util/TestFileUtils.java * (edit) maven-resolver-connector-basic/src/test/java/org/eclipse/aether/connector/basic/PartialFileTest.java > Exceptions are suppressed incorrectly when closing resources fails. > --- > > Key: MRESOLVER-13 > URL: https://issues.apache.org/jira/browse/MRESOLVER-13 > Project: Maven Resolver > Issue Type: Bug >Reporter: Christian Schulte >Assignee: Christian Schulte > Fix For: Maven Artifact Resolver 1.2.0 pre-reset > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (MRESOLVER-18) DefaultDependencyCollector does not provide pre-managed state for exclusions and properties.
Christian Schulte created MRESOLVER-18: -- Summary: DefaultDependencyCollector does not provide pre-managed state for exclusions and properties. Key: MRESOLVER-18 URL: https://issues.apache.org/jira/browse/MRESOLVER-18 Project: Maven Resolver Issue Type: Improvement Reporter: Christian Schulte Assignee: Christian Schulte Priority: Trivial -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (MRESOLVER-11) Project dependency collection result should contain repositories.
[ https://issues.apache.org/jira/browse/MRESOLVER-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte closed MRESOLVER-11. -- Resolution: Fixed Fix Version/s: (was: Maven Artifact Resolver 1.2.0 pre-reset) Maven Artifact Resolver 1.1.0 > Project dependency collection result should contain repositories. > - > > Key: MRESOLVER-11 > URL: https://issues.apache.org/jira/browse/MRESOLVER-11 > Project: Maven Resolver > Issue Type: Bug >Reporter: Christian Schulte >Assignee: Christian Schulte > Fix For: Maven Artifact Resolver 1.1.0 > > > The resolution result provided when performing project dependency collection > is lacking the repositories from the collection request. Components the > project root node is passed to (transformers, for example), expect this > information to be provided. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (MRESOLVER-14) Statistics should be calculated using System.nanoTime instead of System.currentTimeMillis.
[ https://issues.apache.org/jira/browse/MRESOLVER-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte reopened MRESOLVER-14: Re-opened to update fix version. > Statistics should be calculated using System.nanoTime instead of > System.currentTimeMillis. > -- > > Key: MRESOLVER-14 > URL: https://issues.apache.org/jira/browse/MRESOLVER-14 > Project: Maven Resolver > Issue Type: Bug >Reporter: Christian Schulte >Assignee: Christian Schulte > Fix For: Maven Artifact Resolver 1.2.0 pre-reset > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (MRESOLVER-11) Project dependency collection result should contain repositories.
[ https://issues.apache.org/jira/browse/MRESOLVER-11?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte reopened MRESOLVER-11: Re-opened to update fix version. > Project dependency collection result should contain repositories. > - > > Key: MRESOLVER-11 > URL: https://issues.apache.org/jira/browse/MRESOLVER-11 > Project: Maven Resolver > Issue Type: Bug >Reporter: Christian Schulte >Assignee: Christian Schulte > Fix For: Maven Artifact Resolver 1.1.0 > > > The resolution result provided when performing project dependency collection > is lacking the repositories from the collection request. Components the > project root node is passed to (transformers, for example), expect this > information to be provided. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Reopened] (MRESOLVER-13) Exceptions are suppressed incorrectly when closing resources fails.
[ https://issues.apache.org/jira/browse/MRESOLVER-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte reopened MRESOLVER-13: Re-opened to update fix version. > Exceptions are suppressed incorrectly when closing resources fails. > --- > > Key: MRESOLVER-13 > URL: https://issues.apache.org/jira/browse/MRESOLVER-13 > Project: Maven Resolver > Issue Type: Bug >Reporter: Christian Schulte >Assignee: Christian Schulte > Fix For: Maven Artifact Resolver 1.1.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (MRESOLVER-18) DefaultDependencyCollector does not provide pre-managed state for exclusions and properties.
[ https://issues.apache.org/jira/browse/MRESOLVER-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte closed MRESOLVER-18. -- Resolution: Fixed Fix Version/s: Maven Artifact Resolver 1.1.0 > DefaultDependencyCollector does not provide pre-managed state for exclusions > and properties. > > > Key: MRESOLVER-18 > URL: https://issues.apache.org/jira/browse/MRESOLVER-18 > Project: Maven Resolver > Issue Type: Improvement >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: Maven Artifact Resolver 1.1.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (MRESOLVER-14) Statistics should be calculated using System.nanoTime instead of System.currentTimeMillis.
[ https://issues.apache.org/jira/browse/MRESOLVER-14?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte closed MRESOLVER-14. -- Resolution: Fixed Fix Version/s: (was: Maven Artifact Resolver 1.2.0 pre-reset) Maven Artifact Resolver 1.1.0 > Statistics should be calculated using System.nanoTime instead of > System.currentTimeMillis. > -- > > Key: MRESOLVER-14 > URL: https://issues.apache.org/jira/browse/MRESOLVER-14 > Project: Maven Resolver > Issue Type: Bug >Reporter: Christian Schulte >Assignee: Christian Schulte > Fix For: Maven Artifact Resolver 1.1.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Closed] (MRESOLVER-13) Exceptions are suppressed incorrectly when closing resources fails.
[ https://issues.apache.org/jira/browse/MRESOLVER-13?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte closed MRESOLVER-13. -- Resolution: Fixed Fix Version/s: (was: Maven Artifact Resolver 1.2.0 pre-reset) Maven Artifact Resolver 1.1.0 > Exceptions are suppressed incorrectly when closing resources fails. > --- > > Key: MRESOLVER-13 > URL: https://issues.apache.org/jira/browse/MRESOLVER-13 > Project: Maven Resolver > Issue Type: Bug >Reporter: Christian Schulte >Assignee: Christian Schulte > Fix For: Maven Artifact Resolver 1.1.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MRESOLVER-18) DefaultDependencyCollector does not provide pre-managed state for exclusions and properties.
[ https://issues.apache.org/jira/browse/MRESOLVER-18?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15929199#comment-15929199 ] Hudson commented on MRESOLVER-18: - SUCCESS: Integrated in Jenkins build maven-resolver #47 (See [https://builds.apache.org/job/maven-resolver/47/]) [MRESOLVER-18] DefaultDependencyCollector does not provide pre-managed (schulte: [http://git-wip-us.apache.org/repos/asf/?p=maven-resolver.git&a=commit&h=a245b56afd479640ce12a3cd047b463a629bca0f]) * (edit) maven-resolver-impl/src/main/java/org/eclipse/aether/internal/impl/DefaultDependencyCollector.java * (edit) maven-resolver-util/src/main/java/org/eclipse/aether/util/graph/manager/DependencyManagerUtils.java > DefaultDependencyCollector does not provide pre-managed state for exclusions > and properties. > > > Key: MRESOLVER-18 > URL: https://issues.apache.org/jira/browse/MRESOLVER-18 > Project: Maven Resolver > Issue Type: Improvement >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: Maven Artifact Resolver 1.1.0 > > -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Created] (MDEP-559) Java 9 bytecode cannot be parsed
Ben Alex created MDEP-559:
-
Summary: Java 9 bytecode cannot be parsed
Key: MDEP-559
URL: https://issues.apache.org/jira/browse/MDEP-559
Project: Maven Dependency Plugin
Issue Type: Bug
Components: analyze
Affects Versions: 3.0.0
Environment: Apache Maven 3.3.9
(NON-CANONICAL_2015-11-23T13:17:27+03:00_root; 2015-11-23T21:17:27+11:00)
Maven home: /opt/maven
Java version: 9-ea, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-9-jdk
Default locale: en_AU, platform encoding: UTF-8
OS name: "linux", version: "4.9.11-1-arch", arch: "amd64", family: "unix"
Reporter: Ben Alex
Attempting to run analyze-only against source compiled with Java 9 results in:
{noformat}
[INFO] --- maven-dependency-plugin:3.0.0:analyze-only (config-dependency) @
lmdbjava ---
[DEBUG] Configuring mojo
org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only from plugin
realm ClassRealm[plugin>org.apache.maven.plugins:maven-dependency-plugin:3.0.0,
parent: jdk.internal.loader.ClassLoaders$AppClassLoader@3b764bce]
[DEBUG] Configuring mojo
'org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only' with
basic configurator -->
[DEBUG] (f) analyzer = default
[DEBUG] (f) baseDir = /home/bpa/projects/lmdbjava
[DEBUG] (f) failOnWarning = true
[DEBUG] (f) ignoreNonCompile = false
[DEBUG] (f) outputDirectory = /home/bpa/projects/lmdbjava/target
[DEBUG] (f) outputXML = false
[DEBUG] (f) project = MavenProject: org.lmdbjava:lmdbjava:0.0.6-SNAPSHOT @
/home/bpa/projects/lmdbjava/dependency-reduced-pom.xml
[DEBUG] (f) scriptableFlag = $$%%%
[DEBUG] (f) scriptableOutput = false
[DEBUG] (f) skip = false
[DEBUG] (f) usedDependencies = [org.lmdbjava:lmdbjava-native-linux-x86_64,
org.lmdbjava:lmdbjava-native-windows-x86_64,
org.lmdbjava:lmdbjava-native-osx-x86_64]
[DEBUG] (f) verbose = false
[DEBUG] -- end configuration --
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 7.256 s
[INFO] Finished at: 2017-03-17T17:32:20+11:00
[INFO] Final Memory: 40M/132M
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only
(config-dependency) on project lmdbjava: Execution config-dependency of goal
org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only failed.
IllegalArgumentException -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only
(config-dependency) on project lmdbjava: Execution config-dependency of goal
org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only failed.
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
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:863)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.base/java.lang.reflect.Method.invoke(Method.java:547)
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.PluginExecutionException: Execution
config-dependency of goal
org.apache.maven.plugins:m
