[jira] [Commented] (MJAVADOC-449) javadoc:aggregate fails with JDK 9
[
https://issues.apache.org/jira/browse/MJAVADOC-449?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594487#comment-16594487
]
Lewis John McGibbney commented on MJAVADOC-449:
---
javadoc:aggregate fails with following JDK
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
2018-06-17T11:33:14-07:00)
Maven home: /usr/local/Cellar/maven/3.5.4/libexec
Java version: 10.0.2, vendor: Oracle Corporation, runtime:
/Library/Java/JavaVirtualMachines/jdk-10.0.2.jdk/Contents/Home
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "Mac"
maven-javadoc-plugin version 3.0.1
> javadoc:aggregate fails with JDK 9
> --
>
> Key: MJAVADOC-449
> URL: https://issues.apache.org/jira/browse/MJAVADOC-449
> Project: Maven Javadoc Plugin
> Issue Type: Bug
>Affects Versions: 2.10.3
>Reporter: Hervé Boutemy
>Assignee: Robert Scholte
>Priority: Major
> Attachments: 20180618-MJAVADOC449.zip,
> maven-javadoc-plugin-aggregate-test.zip
>
>
> trying {{mvn -Preporting site}} with Maven core and maven-javadoc-plugin
> upgraded to 2.10.4-SNAPSHOT to benefit from already JDK 9 related fixed
> issues shows another one
> {noformat}[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-site-plugin:3.4:site (default-site) on project
> maven: Error generating maven-javadoc-plugin:2.10.4-SNAPSHOT:aggregate:
> Unable to resolve artifact:groupId = 'org.apache.maven.plugin-tools'
> [ERROR] artifactId = 'maven-plugin-tools-javadoc'
> [ERROR] version = '3.4': Missing:
> [ERROR] --
> [ERROR] 1) com.sun:tools:jar:1.4.2
> [ERROR]
> [ERROR] Try downloading the file manually from the project website.
> [ERROR]
> [ERROR] Then, install it using the command:
> [ERROR] mvn install:install-file -DgroupId=com.sun -DartifactId=tools
> -Dversion=1.4.2 -Dpackaging=jar -Dfile=/path/to/file
> [ERROR]
> [ERROR] Alternatively, if you host your own repository you can deploy the
> file there:
> [ERROR] mvn deploy:deploy-file -DgroupId=com.sun -DartifactId=tools
> -Dversion=1.4.2 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
> -DrepositoryId=[id]
> [ERROR]
> [ERROR] Path to dependency:
> [ERROR] 1) org.apache.maven.plugin-tools:maven-plugin-tools-javadoc:jar:3.4
> [ERROR] 2) com.sun:tools:jar:1.4.2
> [ERROR]
> [ERROR] --
> [ERROR] 1 required artifact is missing.
> [ERROR]
> [ERROR] for artifact:
> [ERROR] org.apache.maven.plugin-tools:maven-plugin-tools-javadoc:jar:3.4
> [ERROR]
> [ERROR] from the specified remote repositories:
> [ERROR] apache.snapshots (http://repository.apache.org/snapshots,
> releases=false, snapshots=true),
> [ERROR] central (https://repo.maven.apache.org/maven2, releases=true,
> snapshots=false)
> [ERROR] -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the -e
> switch.
> [ERROR] Re-run Maven using the -X switch to enable full debug logging.
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/MojoExecutionException{noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (ARCHETYPE-274) Conditionally include or exclude a file from archetype during generation
[ https://issues.apache.org/jira/browse/ARCHETYPE-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594461#comment-16594461 ] Gregory Amerson edited comment on ARCHETYPE-274 at 8/28/18 3:38 AM: I agree with [~ljnelson] Allowing filtering of archetype-metadata.xml would allow the control over which files are included or excluding via property expansion. Unless someone is working on this, our company is willing to work on this feature request. was (Author: gamerson): I agree with [~ljnelson] Allowing filtering of archetype-metadata.xml would allow the control over which files are included or excluding via property expansion. Unless someone is working on this, our company will work on this feature request. > Conditionally include or exclude a file from archetype during generation > > > Key: ARCHETYPE-274 > URL: https://issues.apache.org/jira/browse/ARCHETYPE-274 > Project: Maven Archetype > Issue Type: Improvement > Components: Generator >Affects Versions: 2.0-alpha-4 >Reporter: Dan Allen >Priority: Major > > I would like to be able to control which files are placed into the generated > project based on the value of a property that is defined during > archetype:generate. For instance, I forsee the following prompt: > Define value for groupId: : com.example > Define value for artifactId: : myproject > Define value for package: com.example: : > Define value for extraSupport: : y > Based on the value of extraSupport, I want to include (or not include) a file > in the generated project. If the user does not want the extra support, I > don't want to clutter up the generated project with unnecessary files. > It's all about customization of the project based on what the developer > intends to use. While I could create a whole other archetype, sometimes the > changes are so slight that it would be easier to include/exclude a file. > Is there a way to control this behavior using the archetype-metadata.xml > descriptor? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (ARCHETYPE-274) Conditionally include or exclude a file from archetype during generation
[ https://issues.apache.org/jira/browse/ARCHETYPE-274?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594461#comment-16594461 ] Gregory Amerson commented on ARCHETYPE-274: --- I agree with [~ljnelson] Allowing filtering of archetype-metadata.xml would allow the control over which files are included or excluding via property expansion. Unless someone is working on this, our company will work on this feature request. > Conditionally include or exclude a file from archetype during generation > > > Key: ARCHETYPE-274 > URL: https://issues.apache.org/jira/browse/ARCHETYPE-274 > Project: Maven Archetype > Issue Type: Improvement > Components: Generator >Affects Versions: 2.0-alpha-4 >Reporter: Dan Allen >Priority: Major > > I would like to be able to control which files are placed into the generated > project based on the value of a property that is defined during > archetype:generate. For instance, I forsee the following prompt: > Define value for groupId: : com.example > Define value for artifactId: : myproject > Define value for package: com.example: : > Define value for extraSupport: : y > Based on the value of extraSupport, I want to include (or not include) a file > in the generated project. If the user does not want the extra support, I > don't want to clutter up the generated project with unnecessary files. > It's all about customization of the project based on what the developer > intends to use. While I could create a whole other archetype, sometimes the > changes are so slight that it would be easier to include/exclude a file. > Is there a way to control this behavior using the archetype-metadata.xml > descriptor? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6311) Maven intolerably slow when import scope used heavily in large project
[
https://issues.apache.org/jira/browse/MNG-6311?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594231#comment-16594231
]
Sylwester Lachiewicz commented on MNG-6311:
---
Test with [~dchr] patch on the public spring-boot project (pre-warmed with mvn
clean to download all dependencies)
{noformat}
c:\p\spring-boot>\programs\apache-maven-3.5.4\bin\mvn clean
1080 [INFO] org.apache.maven.cli.event.ExecutionEventLogger - Scanning for
projects...
18247 [WARNING] org.apache.maven.DefaultMaven - The project
org.springframework.boot:spring-boot-parent:pom:2.1.0.BUILD-SNAPSHOT [..]
18280 [INFO] org.apache.maven.cli.event.ExecutionEventLogger -
18296 [INFO] org.apache.maven.cli.event.ExecutionEventLogger - Reactor Build
Order:
18315 [INFO] org.apache.maven.cli.event.ExecutionEventLogger -
18323 [INFO] org.apache.maven.cli.event.ExecutionEventLogger - Spring Boot
Build [pom]
...
31813 [INFO] org.apache.maven.cli.event.ExecutionEventLogger - Total time:
30.753 s
31829 [INFO] org.apache.maven.cli.event.ExecutionEventLogger - Finished at:
2018-08-27T23:05:53+02:00
31841 [INFO] org.apache.maven.cli.event.ExecutionEventLogger -
{noformat}
{noformat}
c:\p\spring-boot>\programs\apache-maven-3.6.0-6311\bin\mvn clean
1199 [INFO] org.apache.maven.cli.event.ExecutionEventLogger - Scanning for
projects...
4902 [WARNING] org.apache.maven.DefaultMaven - The project
org.springframework.boot:spring-boot-parent:pom:2.1.0.BUILD-SNAPSHOT [..]
4926 [INFO] org.apache.maven.cli.event.ExecutionEventLogger -
4932 [INFO] org.apache.maven.cli.event.ExecutionEventLogger - Reactor Build
Order:
4936 [INFO] org.apache.maven.cli.event.ExecutionEventLogger -
4941 [INFO] org.apache.maven.cli.event.ExecutionEventLogger - Spring Boot Build
[pom]
...
16102 [INFO] org.apache.maven.cli.event.ExecutionEventLogger - Total time:
14.927 s
16121 [INFO] org.apache.maven.cli.event.ExecutionEventLogger - Finished at:
2018-08-27T23:07:26+02:00
16131 [INFO] org.apache.maven.cli.event.ExecutionEventLogger -
{noformat}
Without the patch, the initial scan takes *17,1sec* and with the patch applied
- only *3,7sec*
[~tnikolay] could help us with testing and try build maven from
[https://github.com/slachiewicz/maven/tree/fix/MNG-6311] and share results?
> Maven intolerably slow when import scope used heavily in large project
> --
>
> Key: MNG-6311
> URL: https://issues.apache.org/jira/browse/MNG-6311
> Project: Maven
> Issue Type: Bug
> Components: core, Performance
>Affects Versions: 3.5.0, 3.5.2
>Reporter: David Churcher
>Priority: Major
> Labels: performance
> Attachments: Call-tree-–-All-threads-together.html,
> anon-hierarchy-maven-output.zip, modelcachefix.diff
>
>
> I have a build performance problem that is identical to MNG-5312, and has
> appeared since MNG-6030 in Maven v3.5.0 reversed the patch for MNG-5312,
> removing the ModelCache from some of the overloads for
> DefaultProjectBuilder.build.
> As in MNG-5312 the problem is in a large proprietary project. It uses up to 8
> levels of parent POMs, many of which use the import scope and have large
> dependency-management sections, and has hundreds of dependencies that also
> use the same parent POM hierarchy. Adding some logging shows that Maven does
> over 800,000 uncached reads of parent POM files, which takes about half an
> hour. With model caching this goes down to a few seconds.
> I've attached a patch that fixes this by using a class-level ModelCache in
> DefaultProjectBuilder. This does not suffer from the memory usage problems
> reported in MNG-6030.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MPOM-197) Replace deprecated plexus-maven-plugin with plexus-component-metadata plugin
[
https://issues.apache.org/jira/browse/MPOM-197?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594232#comment-16594232
]
Hervé Boutemy commented on MPOM-197:
I had a look to see where plexus-maven-plugin was still used and if it could be
replaced.
Result:it is used for the report mojo, that does not exist in
plexus-component-metadata
then I'm -1 to remove plexus-maven-plugin from Maven parent POM
> Replace deprecated plexus-maven-plugin with plexus-component-metadata plugin
>
>
> Key: MPOM-197
> URL: https://issues.apache.org/jira/browse/MPOM-197
> Project: Maven POMs
> Issue Type: Wish
> Components: maven
>Affects Versions: MAVEN-32
>Reporter: Sylwester Lachiewicz
>Priority: Minor
> Fix For: MAVEN-33
>
>
> Replace the deprecated
> [{{plexus-maven-plugin}}|https://codehaus-plexus.github.io/plexus-maven-plugin/],
> which only supports Plexus Javadoc Tags, with its successor:
> [{{plexus-component-metadata}}|https://codehaus-plexus.github.io/plexus-containers/plexus-component-metadata/],
> which support both Plexus Javadoc Tags and Plexus Java Annotations,
>
> Remove plugin from dependencies so other projects should also modify
> configuration and try also to migrate to Java Annotation from Javadoc Tags.
> More information how to upgrade: [Maven Developer Cook Book - upgrade
> information|https://maven.apache.org/plugin-developers/cookbook/plexus-plugin-upgrade.html]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] joshelser commented on issue #6: [MSKIN-137] Make the hamburger menu work with the top-navigation enab…
joshelser commented on issue #6: [MSKIN-137] Make the hamburger menu work with the top-navigation enab… URL: https://github.com/apache/maven-fluido-skin/pull/6#issuecomment-416370863 Tried to build the HBase maven site with this, but got an error. ``` [INFO] Parent project loaded from repository: org.apache:apache:pom:18 [INFO] Relativizing decoration links with respect to project URL: http://hbase.apache.org [INFO] Rendering site with org.apache.maven.skins:maven-fluido-skin:jar:1.8-hbase skin. [INFO] Skipped "About" report (maven-project-info-reports-plugin:2.9:index), file "index.html" already exists for the English version. [INFO] Rendering 14 Doxia documents: 14 xdoc [ERROR] ResourceManager : unable to find resource 'site-macros.vm' in any resource loader. [ERROR] #parse(): cannot find template 'site-macros.vm', called from template META-INF/maven/site.vm at (18, 1) ``` The error seems to be coming from `./src/main/resources/META-INF/maven/site.vm`, but I don't know why it can find site.vm but not site-macros.vm which is in the same directory. Obligatory, it may be something brutally obvious. Haven't dug yet :) This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Updated] (MINSTALL-126) localRepositoryPath for install like for install-file
[ https://issues.apache.org/jira/browse/MINSTALL-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MINSTALL-126: - Fix Version/s: 3.0.0 > localRepositoryPath for install like for install-file > - > > Key: MINSTALL-126 > URL: https://issues.apache.org/jira/browse/MINSTALL-126 > Project: Maven Install Plugin > Issue Type: Improvement >Reporter: Michael Vorburger >Priority: Major > Fix For: 3.0.0 > > > I believe there are real world use cases where to have a localRepositoryPath > available for maven-install-plugin's install goal like it currently is for > the install-file goal would be useful. > http://blog2.vorburger.ch/2016/06/maven-install-into-additional.html is a > Blog post I wrote with some background about why this would be useful. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MPOM-197) Replace deprecated plexus-maven-plugin with plexus-component-metadata plugin
[
https://issues.apache.org/jira/browse/MPOM-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MPOM-197:
-
Fix Version/s: MAVEN-33
> Replace deprecated plexus-maven-plugin with plexus-component-metadata plugin
>
>
> Key: MPOM-197
> URL: https://issues.apache.org/jira/browse/MPOM-197
> Project: Maven POMs
> Issue Type: Wish
> Components: maven
>Affects Versions: MAVEN-32
>Reporter: Sylwester Lachiewicz
>Priority: Minor
> Fix For: MAVEN-33
>
>
> Replace the deprecated
> [{{plexus-maven-plugin}}|https://codehaus-plexus.github.io/plexus-maven-plugin/],
> which only supports Plexus Javadoc Tags, with its successor:
> [{{plexus-component-metadata}}|https://codehaus-plexus.github.io/plexus-containers/plexus-component-metadata/],
> which support both Plexus Javadoc Tags and Plexus Java Annotations,
>
> Remove plugin from dependencies so other projects should also modify
> configuration and try also to migrate to Java Annotation from Javadoc Tags.
> More information how to upgrade: [Maven Developer Cook Book - upgrade
> information|https://maven.apache.org/plugin-developers/cookbook/plexus-plugin-upgrade.html]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MPOM-197) Replace deprecated plexus-maven-plugin with plexus-component-metadata plugin
[
https://issues.apache.org/jira/browse/MPOM-197?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MPOM-197:
-
Affects Version/s: MAVEN-32
> Replace deprecated plexus-maven-plugin with plexus-component-metadata plugin
>
>
> Key: MPOM-197
> URL: https://issues.apache.org/jira/browse/MPOM-197
> Project: Maven POMs
> Issue Type: Wish
> Components: maven
>Affects Versions: MAVEN-32
>Reporter: Sylwester Lachiewicz
>Priority: Minor
> Fix For: MAVEN-33
>
>
> Replace the deprecated
> [{{plexus-maven-plugin}}|https://codehaus-plexus.github.io/plexus-maven-plugin/],
> which only supports Plexus Javadoc Tags, with its successor:
> [{{plexus-component-metadata}}|https://codehaus-plexus.github.io/plexus-containers/plexus-component-metadata/],
> which support both Plexus Javadoc Tags and Plexus Java Annotations,
>
> Remove plugin from dependencies so other projects should also modify
> configuration and try also to migrate to Java Annotation from Javadoc Tags.
> More information how to upgrade: [Maven Developer Cook Book - upgrade
> information|https://maven.apache.org/plugin-developers/cookbook/plexus-plugin-upgrade.html]
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MNG-6467) Remove plugin definition from pom file which is inherited
Karl Heinz Marbaise created MNG-6467: Summary: Remove plugin definition from pom file which is inherited Key: MNG-6467 URL: https://issues.apache.org/jira/browse/MNG-6467 Project: Maven Issue Type: Improvement Components: Errors, General Affects Versions: 3.6.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.6.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] joshelser commented on issue #6: [MSKIN-137] Make the hamburger menu work with the top-navigation enab…
joshelser commented on issue #6: [MSKIN-137] Make the hamburger menu work with the top-navigation enab… URL: https://github.com/apache/maven-fluido-skin/pull/6#issuecomment-416346933 Let me test this out, @slachiewicz. Thanks. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Created] (MPOM-207) Upgrade maven-compiler-plugin to version 3.8.0
Karl Heinz Marbaise created MPOM-207: Summary: Upgrade maven-compiler-plugin to version 3.8.0 Key: MPOM-207 URL: https://issues.apache.org/jira/browse/MPOM-207 Project: Maven POMs Issue Type: Dependency upgrade Components: maven Affects Versions: MAVEN-32 Reporter: Karl Heinz Marbaise Fix For: MAVEN-33 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1537) ClassNotFoundException with m-surefire-p 2.22.0
[
https://issues.apache.org/jira/browse/SUREFIRE-1537?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594124#comment-16594124
]
Thorsten Heit commented on SUREFIRE-1537:
-
[~tibor17]:
I haven't added the output of mvn test, but as you can see in the output of
{{mvn -X}} there are differences in the test classpath. The
{{ClassNotFoundException}} occurs with m-surefire-p 2.22.0 because of the
missing dependency.
No, it's not about JavaFX, it's an internal project dependency that is missing
in 2.22.0.
> ClassNotFoundException with m-surefire-p 2.22.0
> ---
>
> Key: SUREFIRE-1537
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1537
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.22.0
> Environment: Windows 8.1 x64
> Maven 3.5.4
> Java 10.0.1
>Reporter: Thorsten Heit
>Priority: Major
>
> With Surefire plugin 2.22.0 a JUnit test in one of our projects doesn't work
> anymore; a ClassNotFoundException is thrown when using {{mvn clean test}}.
> Using 2.21.0 everyhing works.
> This is the output of {{mvn dependency:tree}}:
> {noformat}
> [INFO] Scanning for projects...
> [INFO]
> [INFO] -< myorg:facade >-
> [INFO] Building facade 2018.2.0-SNAPSHOT
> [INFO] [ jar
> ]-
> [INFO]
> [INFO] --- maven-dependency-plugin:2.8:tree (default-cli) @ facade ---
> [INFO] myorg:facade:jar:2018.2.0-SNAPSHOT
> [INFO] +- myorg:accessors:jar:2018.2.0:compile
> [INFO] | +- myorg:myids:jar:2018.2.0:compile
> [INFO] | +- myorg:output:jar:2018.2.0:compile
> [INFO] | \- org.slf4j:slf4j-api:jar:1.8.0-beta2:compile
> [INFO] +- myorg:utilities:jar:2.2.0:compile
> [INFO] +- com.sun.mail:javax.mail:jar:1.6.1:test
> [INFO] +- javax.activation:javax.activation-api:jar:1.2.0:test
> [INFO] +- externals:externallib:jar:2.1.3:compile
> [INFO] | +- org.apache.xmlgraphics:fop:jar:2.2:compile
> [INFO] | | +- org.apache.xmlgraphics:xmlgraphics-commons:jar:2.2:compile
> [INFO] | | +- org.apache.xmlgraphics:batik-svg-dom:jar:1.9:compile
> [INFO] | | | +- org.apache.xmlgraphics:batik-css:jar:1.9:compile
> [INFO] | | | +- org.apache.xmlgraphics:batik-dom:jar:1.9:compile
> [INFO] | | | +- org.apache.xmlgraphics:batik-parser:jar:1.9:compile
> [INFO] | | | +- org.apache.xmlgraphics:batik-util:jar:1.9:compile
> [INFO] | | | | +- org.apache.xmlgraphics:batik-constants:jar:1.9:compile
> [INFO] | | | | \- org.apache.xmlgraphics:batik-i18n:jar:1.9:compile
> [INFO] | | | \- xml-apis:xml-apis-ext:jar:1.3.04:compile
> [INFO] | | +- org.apache.xmlgraphics:batik-bridge:jar:1.9:compile
> [INFO] | | | +- org.apache.xmlgraphics:batik-anim:jar:1.9:compile
> [INFO] | | | +- org.apache.xmlgraphics:batik-script:jar:1.9:compile
> [INFO] | | | \- org.apache.xmlgraphics:batik-xml:jar:1.9:compile
> [INFO] | | +- org.apache.xmlgraphics:batik-awt-util:jar:1.9:compile
> [INFO] | | +- org.apache.xmlgraphics:batik-gvt:jar:1.9:compile
> [INFO] | | +- org.apache.xmlgraphics:batik-transcoder:jar:1.9:compile
> [INFO] | | | \- org.apache.xmlgraphics:batik-svggen:jar:1.9:compile
> [INFO] | | +- org.apache.xmlgraphics:batik-extension:jar:1.9:compile
> [INFO] | | +- org.apache.xmlgraphics:batik-ext:jar:1.9:compile
> [INFO] | | +-
> org.apache.avalon.framework:avalon-framework-api:jar:4.3.1:compile
> [INFO] | | +-
> org.apache.avalon.framework:avalon-framework-impl:jar:4.3.1:compile
> [INFO] | | \- org.apache.pdfbox:fontbox:jar:2.0.4:compile
> [INFO] | +- commons-io:commons-io:jar:2.5:compile
> [INFO] | \- org.slf4j:jcl-over-slf4j:jar:1.8.0-beta2:compile
> [INFO] +- myorg:business-objects:jar:2018.2.0:compile
> [INFO] +-
> org.eclipse.jdt:org.eclipse.jdt.annotation:jar:1.1.0-v20130513-1648:provided
> [INFO] \- junit:junit:jar:4.12:test
> [INFO]\- org.hamcrest:hamcrest-core:jar:1.3:test
> [INFO]
>
> [INFO] BUILD SUCCESS
> [INFO]
>
> [INFO] Total time: 5.184 s
> [INFO] Finished at: 2018-07-12T09:24:08+02:00
> [INFO]
>
> {noformat}
> The supposedly missing class when using 2.22.0 is contained in the dependency
> *externals:externallib* (see above) which itself is contained as a direct
> compile-time dependency in my project.
> What I see is that the output of {{mvn -X test}} differs between the two
> plugin versions:
> 2.21.0:
> {noformat}
> (...)
> [INFO] --- maven-surefire-plugin:2.21.0:test (default-test) @ facade ---
> (...)
> [DEBUG] test(compact) classpath: test-classes output-2018.2.0.jar
> slf4j-api-1.8.0-beta2.jar
[GitHub] slachiewicz opened a new pull request #6: [MSKIN-137] Make the hamburger menu work with the top-navigation enab…
slachiewicz opened a new pull request #6: [MSKIN-137] Make the hamburger menu work with the top-navigation enab… URL: https://github.com/apache/maven-fluido-skin/pull/6 …led and sidebar-navigation disabled @joshelser could you verify? Closes: #1 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (MSHADE-297) Including feature.xml in shaded jar
[
https://issues.apache.org/jira/browse/MSHADE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594096#comment-16594096
]
Karl Heinz Marbaise commented on MSHADE-297:
If I correctly remember my OSGi experience a {{feature.xml}} describes a group
of {{services/bundles}} which have a defined interface and using maven-shade
will violate that (it breaks the decoupling of the features)...and the result
can't be correct If I correctly remember...
> Including feature.xml in shaded jar
> ---
>
> Key: MSHADE-297
> URL: https://issues.apache.org/jira/browse/MSHADE-297
> Project: Maven Shade Plugin
> Issue Type: Bug
>Reporter: Pratiksha Tiwari
>Priority: Major
>
> I am trying to use feature.xml as a dependency in my project. The maven shade
> plugin while including the jars gives the following error : Failed to execute
> goal org.apache.maven.plugins:maven-shade-plugin:2.2:shade (default) on
> project: Error creating shaded jar: error in opening zip file
> /feature.xml
> Is it possible to include this using shade plugin? Otherwise what alternative
> method can be used?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (ARCHETYPE-555) My archetype is not in the catalog.xml
[ https://issues.apache.org/jira/browse/ARCHETYPE-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16594083#comment-16594083 ] Matthias Fuchs commented on ARCHETYPE-555: -- Hello? Is there any news on this? > My archetype is not in the catalog.xml > -- > > Key: ARCHETYPE-555 > URL: https://issues.apache.org/jira/browse/ARCHETYPE-555 > Project: Maven Archetype > Issue Type: Bug >Reporter: Matthias Fuchs >Priority: Blocker > Labels: archetype, catalog, maven > > This is the url to the archetype: > [https://search.maven.org/artifact/io.spot-next.archetypes/archetype-empty/1.0.6-BETA-20180817/maven-archetype] > > It is declared as archetype, so it should be in the catalog file too, right? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSKINS-137) Enable "Hamburger menu" with top-nav only
[ https://issues.apache.org/jira/browse/MSKINS-137?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593825#comment-16593825 ] ASF GitHub Bot commented on MSKINS-137: --- joshelser commented on issue #1: MSKINS-137 Make the hamburger menu work with the top-navigation ena… URL: https://github.com/apache/maven-fluido-skin/pull/1#issuecomment-416265843 Let me try to do that today. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org > Enable "Hamburger menu" with top-nav only > - > > Key: MSKINS-137 > URL: https://issues.apache.org/jira/browse/MSKINS-137 > Project: Maven Skins > Issue Type: Improvement >Reporter: Josh Elser >Priority: Major > > Revitalizing this old PR https://github.com/apache/maven-skins/pull/4 > Still an issue for us down in HBase. Changes seem to apply and have worked in > local testing on the HBase site. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] joshelser commented on issue #1: MSKINS-137 Make the hamburger menu work with the top-navigation ena…
joshelser commented on issue #1: MSKINS-137 Make the hamburger menu work with the top-navigation ena… URL: https://github.com/apache/maven-fluido-skin/pull/1#issuecomment-416265843 Let me try to do that today. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (MSHADE-297) Including feature.xml in shaded jar
[
https://issues.apache.org/jira/browse/MSHADE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593527#comment-16593527
]
Robert Scholte commented on MSHADE-297:
---
I'm not familiar with {{feature.xml}}, can you attach a small (=minimal)
example project?
> Including feature.xml in shaded jar
> ---
>
> Key: MSHADE-297
> URL: https://issues.apache.org/jira/browse/MSHADE-297
> Project: Maven Shade Plugin
> Issue Type: Bug
>Reporter: Pratiksha Tiwari
>Priority: Major
>
> I am trying to use feature.xml as a dependency in my project. The maven shade
> plugin while including the jars gives the following error : Failed to execute
> goal org.apache.maven.plugins:maven-shade-plugin:2.2:shade (default) on
> project: Error creating shaded jar: error in opening zip file
> /feature.xml
> Is it possible to include this using shade plugin? Otherwise what alternative
> method can be used?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MSHADE-297) Including feature.xml in shaded jar
[ https://issues.apache.org/jira/browse/MSHADE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593522#comment-16593522 ] Pratiksha Tiwari commented on MSHADE-297: - [~rfscholte] I want to expose few of my jars as a feature that is why adding it in the form of xml. The only place I am facing issue is to integrate it with shade plugin. Is it possible to do such thing with the plugin? > Including feature.xml in shaded jar > --- > > Key: MSHADE-297 > URL: https://issues.apache.org/jira/browse/MSHADE-297 > Project: Maven Shade Plugin > Issue Type: Bug >Reporter: Pratiksha Tiwari >Priority: Major > > I am trying to use feature.xml as a dependency in my project. The maven shade > plugin while including the jars gives the following error : Failed to execute > goal org.apache.maven.plugins:maven-shade-plugin:2.2:shade (default) on > project: Error creating shaded jar: error in opening zip file > /feature.xml > Is it possible to include this using shade plugin? Otherwise what alternative > method can be used? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSHADE-297) Including feature.xml in shaded jar
[ https://issues.apache.org/jira/browse/MSHADE-297?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593492#comment-16593492 ] Robert Scholte commented on MSHADE-297: --- In general: all dependencies end up on the classpath, so specifying an xml-file as dependency is awkward, it is not acessible. Where is this file coming from? Maybe you want to use [maven-remote-resources-plugin|https://maven.apache.org/plugins/maven-remote-resources-plugin/] > Including feature.xml in shaded jar > --- > > Key: MSHADE-297 > URL: https://issues.apache.org/jira/browse/MSHADE-297 > Project: Maven Shade Plugin > Issue Type: Bug >Reporter: Pratiksha Tiwari >Priority: Major > > I am trying to use feature.xml as a dependency in my project. The maven shade > plugin while including the jars gives the following error : Failed to execute > goal org.apache.maven.plugins:maven-shade-plugin:2.2:shade (default) on > project: Error creating shaded jar: error in opening zip file > /feature.xml > Is it possible to include this using shade plugin? Otherwise what alternative > method can be used? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MSHADE-297) Including feature.xml in shaded jar
Pratiksha Tiwari created MSHADE-297: --- Summary: Including feature.xml in shaded jar Key: MSHADE-297 URL: https://issues.apache.org/jira/browse/MSHADE-297 Project: Maven Shade Plugin Issue Type: Bug Reporter: Pratiksha Tiwari I am trying to use feature.xml as a dependency in my project. The maven shade plugin while including the jars gives the following error : Failed to execute goal org.apache.maven.plugins:maven-shade-plugin:2.2:shade (default) on project: Error creating shaded jar: error in opening zip file /feature.xml Is it possible to include this using shade plugin? Otherwise what alternative method can be used? -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Reopened] (SUREFIRE-1562) Support Java 11
[ https://issues.apache.org/jira/browse/SUREFIRE-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte reopened SUREFIRE-1562: -- > Support Java 11 > --- > > Key: SUREFIRE-1562 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1562 > Project: Maven Surefire > Issue Type: Improvement >Reporter: Tibor Digana >Assignee: Tibor Digana >Priority: Major > Fix For: 2.22.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1520) ClassNotFoundException with forkCount>1 and junit5
[
https://issues.apache.org/jira/browse/SUREFIRE-1520?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593393#comment-16593393
]
Jens Teglhus Møller commented on SUREFIRE-1520:
---
Hi
I have now re-tested with suggested changes and it seems like the problem has
indeed been solved.
What I did was to remove plugin dependencies from surefire/failsafe plugin
config and add junit-jupiter-engine as a regular project dependency (I also
removed the surefire-logger-api dependency workaround).
Best regards Jens
> ClassNotFoundException with forkCount>1 and junit5
> --
>
> Key: SUREFIRE-1520
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1520
> Project: Maven Surefire
> Issue Type: Bug
> Components: JUnit 5.x support, Maven Surefire Plugin
>Affects Versions: 2.21.0
>Reporter: Stefan Küttner
>Priority: Major
>
> maven-version: 3.2.5 / 3.3.9
> OS: Windows 7
> Java 8 (compiler level & runtime)
> {code:xml|title=pom.xml (effective-pom)|collapse=true}
>
> maven-surefire-plugin
> 2.21.0
>
>
> default-test
> test
>
> test
>
>
>
> **/*IntegrationTest.java
>
> false
> 2
> true
>
> 3600
>
> -Djava.util.logging.config.file=${project.base.dir}logging.properties
> alphabetical
>
> **/*Test.java
>
>
>
>
>
>
> org.junit.platform
> junit-platform-surefire-provider
> 1.2.0
> compile
>
>
> org.junit.vintage
> junit-vintage-engine
> 5.2.0
> compile
>
>
> org.junit.jupiter
> junit-jupiter-engine
> 5.2.0
> compile
>
>
>
> 2
> true
> 3600
>
> -Djava.util.logging.config.file=${project.base.dir}logging.properties
> alphabetical
> false
>
> **/*Test.java
>
>
> **/*PerfTest.java
> **/*IntegrationTest.java
>
>
>
> {code}
> result is
> {code:java|title=java.lang.ClassNotFoundException:
> org.apache.maven.plugin.surefire.log.api.ConsoleLogger|collapse=true}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-surefire-plugin:2.21.0:test (default-test) on
> project mts.ctsm: Execution default-test of goal
> org.apache.maven.plugins:maven-surefire-plugin:2.21.0:test failed:
> java.lang.ClassNotFoundException:
> org.apache.maven.plugin.surefire.log.api.ConsoleLogger -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-surefire-plugin:2.21.0:test
> (default-test) on project mts.ctsm: Execution default-test of goal
> org.apache.maven.plugins:maven-surefire-plugin:2.21.0:test failed:
> java.lang.ClassNotFoundException:
> org.apache.maven.plugin.surefire.log.api.ConsoleLogger
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:224)
> 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:120)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:355)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:155)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:584)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:216)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:160)
> 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:498)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
>
[jira] [Commented] (MNG-5951) add an option to avoid path addition to inherited URLs
[
https://issues.apache.org/jira/browse/MNG-5951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593336#comment-16593336
]
Mark Raynsford commented on MNG-5951:
-
bq. why not for project.distributionManagement.site
In my case, I'm not using the maven-site-plugin. I have a custom plugin that
only executes in the parent POM of each project and doesn't have any kind of
per-module page generation.
> add an option to avoid path addition to inherited URLs
> --
>
> Key: MNG-5951
> URL: https://issues.apache.org/jira/browse/MNG-5951
> Project: Maven
> Issue Type: Improvement
> Components: Inheritance and Interpolation
>Affects Versions: 3.0.5, 3.1.1, 3.2.5, 3.3.9
>Reporter: Jörg Sesterhenn
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.6.x-candidate
>
> Attachments: MNG-5951.zip
>
>
> What I am trying to achieve is
> the definition of a project.url in a parent pom
> in a way that all children inherit a url ending with
> {code}
> ${project.groupId}/${project.artifactId}/${project.version}/
> {code}
> in order to be able to publish sites of all artifacts in all versions in
> parallel
> without having to redefine the url in every child pom.
> This is currently not working as expected in maven due to the default child
> urls calculation which leads to urls that add up parent urls like
> http://my.domain.de/sites/de.enterprise.calculatorsGroupId/calculator-artifactID/1.0.0-SNAPSHOT/internetAppParentPOM/calculatorParentPom/calculator-artifactID/
> The part *"internetAppParentPOM/calculatorParentPom/"* is added by automatic
> child url calculation (those are the artifactIds of all parent poms beneath
> our enterprise parent pom where the url is defined) and *is expexted to not
> be there at all*. The repeated artifactID at the end of the url is
> superfluous as well but tollerable.
> I expect maven-core to be changed so that I can turn on/off the automatic
> calculation of child URLs as an option which is by default on (current
> behaviour so nothing will change unless configured explicitly).
> See the discussion in MSITE-672.
> As this can not be done in the maven-site-plugin there needs to be a change
> in Maven itself (core), in Maven Model Builder, ie the way effective model is
> calculated, and more precisely in the inheritance step:
> http://maven.apache.org/ref/current/maven-model-builder/.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (SUREFIRE-1562) Support Java 11
[ https://issues.apache.org/jira/browse/SUREFIRE-1562?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed SUREFIRE-1562. Resolution: Fixed I'm missing a description. What do you need? If this is related to plexus-java, I've improved it a lot, being able to remove asm dependency for most cases. > Support Java 11 > --- > > Key: SUREFIRE-1562 > URL: https://issues.apache.org/jira/browse/SUREFIRE-1562 > Project: Maven Surefire > Issue Type: Improvement >Reporter: Tibor Digana >Assignee: Tibor Digana >Priority: Major > Fix For: 2.22.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-5951) add an option to avoid path addition to inherited URLs
[
https://issues.apache.org/jira/browse/MNG-5951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593317#comment-16593317
]
Robert Scholte commented on MNG-5951:
-
To calculate URLs you need to use the buildtime folder structure. And it should
be based by the aggregator, not the parent.
I do agree that this can be solved once we have the consumer pom in place.
> add an option to avoid path addition to inherited URLs
> --
>
> Key: MNG-5951
> URL: https://issues.apache.org/jira/browse/MNG-5951
> Project: Maven
> Issue Type: Improvement
> Components: Inheritance and Interpolation
>Affects Versions: 3.0.5, 3.1.1, 3.2.5, 3.3.9
>Reporter: Jörg Sesterhenn
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.6.x-candidate
>
> Attachments: MNG-5951.zip
>
>
> What I am trying to achieve is
> the definition of a project.url in a parent pom
> in a way that all children inherit a url ending with
> {code}
> ${project.groupId}/${project.artifactId}/${project.version}/
> {code}
> in order to be able to publish sites of all artifacts in all versions in
> parallel
> without having to redefine the url in every child pom.
> This is currently not working as expected in maven due to the default child
> urls calculation which leads to urls that add up parent urls like
> http://my.domain.de/sites/de.enterprise.calculatorsGroupId/calculator-artifactID/1.0.0-SNAPSHOT/internetAppParentPOM/calculatorParentPom/calculator-artifactID/
> The part *"internetAppParentPOM/calculatorParentPom/"* is added by automatic
> child url calculation (those are the artifactIds of all parent poms beneath
> our enterprise parent pom where the url is defined) and *is expexted to not
> be there at all*. The repeated artifactID at the end of the url is
> superfluous as well but tollerable.
> I expect maven-core to be changed so that I can turn on/off the automatic
> calculation of child URLs as an option which is by default on (current
> behaviour so nothing will change unless configured explicitly).
> See the discussion in MSITE-672.
> As this can not be done in the maven-site-plugin there needs to be a change
> in Maven itself (core), in Maven Model Builder, ie the way effective model is
> calculated, and more precisely in the inheritance step:
> http://maven.apache.org/ref/current/maven-model-builder/.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MDEP-518) Dependency resolution fails in threaded builds
[
https://issues.apache.org/jira/browse/MDEP-518?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593276#comment-16593276
]
Charl Thiem commented on MDEP-518:
--
Hi, still not a single comment in 2 years? This still happens
{code}
mvn --version
Apache Maven 3.5.4 (1edded0938998edf8bf061f1ceb3cfdeccf443fe;
2018-06-17T20:33:14+02:00)
Maven home: /opt/current/maven
Java version: 1.8.0_181, vendor: Oracle Corporation, runtime:
/opt/jdk1.8.0_181/jre
Default locale: en_ZA, platform encoding: UTF-8
OS name: "linux", version: "4.15.0-33-generic", arch: "amd64", family: "unix"
{code}
> Dependency resolution fails in threaded builds
> --
>
> Key: MDEP-518
> URL: https://issues.apache.org/jira/browse/MDEP-518
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: resolve, resolve-plugins
>Affects Versions: 2.10
> Environment: Linux
>Reporter: Troy Telford
>Priority: Major
>
> This issue sounds similar to MDEP-442, but it may be unrelated.
> I suspect the same problem may occur in both {{dependency:resolve}} and
> {{dependency:resolve-plugins}}.
> The same error occurs when I use {{mvn install}}; but {{dependency:resolve}}
> is a more tightly-focused problem report.
> I have a large multi-module project, with more than 40 modules, and a
> large-ish build node with 24 cores. {{mvn -T1C dependency:resolve
> dependency:resolve-plugins}} will typically (94/100 attempts) fail to
> download all of the dependencies required, with an error similar to:
> {noformat}
> Failed to read artifact descriptor for com.foo:machine:jar:1.2.3-SNAPSHOT:
> Could not transfer artifact com.foo.somegroup:dependency_4:jar:3.0.0 from/to
> snapshot-repository (https://nexus.foo.com/content/repositories/releases):
> /home/userid/.m2/repository/com/foo/somegroup/dependency_4/3.0.0/dependency_4-3.0.0.pom.part
> (No such file or directory) -> [Help 1]
> -> com.foo.somegroup:dependency_4:jar:3.0.0
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:220)
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:127)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:257)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:200)
> 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.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:188)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:184)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:471)
> at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:334)
> at java.util.concurrent.FutureTask.run(FutureTask.java:166)
> at
> java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
> at
> java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
> at java.lang.Thread.run(Thread.java:722)
> Caused by: org.apache.maven.project.DependencyResolutionException: Could not
> resolve dependencies for project com.foo:machine:jar:1.2.3-SNAPSHOT: Failed
> to collect dependencies at com.foo:dependency_1:jar:1.2.3-SNAPSHOT ->
> com.foo:dependency_2:jar:1.2.3-SNAPSHOT ->
> com.foo:dependency_3:jar:1.2.3-SNAPSHOT ->
> com.foo.somegroup:dependency_4:jar:3.0.0
> at
> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:180)
> at
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:195)
> ... 16 more
> Caused by: org.eclipse.aether.collection.DependencyCollectionException:
> Failed to collect dependencies at com.foo:dependency_1:jar:1.2.3-SNAPSHOT ->
> com.foo:dependency_2:jar:1.2.3-SNAPSHOT ->
> com.foo:dependency_3:jar:1.2.3-SNAPSHOT ->
> com.foo.somegroup:dependency_4:jar:3.0.0
> at
> org.eclipse.aether.internal.impl.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:291)
> at
>
[jira] [Commented] (MNG-5951) add an option to avoid path addition to inherited URLs
[
https://issues.apache.org/jira/browse/MNG-5951?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16593229#comment-16593229
]
Hervé Boutemy commented on MNG-5951:
why not for project.distributionManagement.site, for the 4 other values, I'm
not convinced: this will lead to duplication, since the values can be used in
many ways
IMHO, this is a perfect fit for build POM vs consumer POM: more prerequisites
on build side, since the algorithm is more complex and would be extensible
through extensions, but still easy use on consumer side (when the use is not at
build time but at consume time)
Notice: this is future, if really complex inheritance calculation are required
until now, just a "append" boolean seems to match most expectations
and your remarks make me think it's not wise to add full extensibility until we
have build vs consumer POM
> add an option to avoid path addition to inherited URLs
> --
>
> Key: MNG-5951
> URL: https://issues.apache.org/jira/browse/MNG-5951
> Project: Maven
> Issue Type: Improvement
> Components: Inheritance and Interpolation
>Affects Versions: 3.0.5, 3.1.1, 3.2.5, 3.3.9
>Reporter: Jörg Sesterhenn
>Assignee: Hervé Boutemy
>Priority: Major
> Fix For: 3.6.x-candidate
>
> Attachments: MNG-5951.zip
>
>
> What I am trying to achieve is
> the definition of a project.url in a parent pom
> in a way that all children inherit a url ending with
> {code}
> ${project.groupId}/${project.artifactId}/${project.version}/
> {code}
> in order to be able to publish sites of all artifacts in all versions in
> parallel
> without having to redefine the url in every child pom.
> This is currently not working as expected in maven due to the default child
> urls calculation which leads to urls that add up parent urls like
> http://my.domain.de/sites/de.enterprise.calculatorsGroupId/calculator-artifactID/1.0.0-SNAPSHOT/internetAppParentPOM/calculatorParentPom/calculator-artifactID/
> The part *"internetAppParentPOM/calculatorParentPom/"* is added by automatic
> child url calculation (those are the artifactIds of all parent poms beneath
> our enterprise parent pom where the url is defined) and *is expexted to not
> be there at all*. The repeated artifactID at the end of the url is
> superfluous as well but tollerable.
> I expect maven-core to be changed so that I can turn on/off the automatic
> calculation of child URLs as an option which is by default on (current
> behaviour so nothing will change unless configured explicitly).
> See the discussion in MSITE-672.
> As this can not be done in the maven-site-plugin there needs to be a change
> in Maven itself (core), in Maven Model Builder, ie the way effective model is
> calculated, and more precisely in the inheritance step:
> http://maven.apache.org/ref/current/maven-model-builder/.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
