[jira] [Created] (MNG-6300) Multi module release creates empty directories in war file instead of jars
Andreas Kurth created MNG-6300:
--
Summary: Multi module release creates empty directories in war
file instead of jars
Key: MNG-6300
URL: https://issues.apache.org/jira/browse/MNG-6300
Project: Maven
Issue Type: Bug
Affects Versions: 3.5.2
Environment: Linux, Oracle java 1.8.0_152
Reporter: Andreas Kurth
Priority: Critical
Attachments: build.log, mm.zip
After updating to maven 3.5.2 we encounter the following reproducible bug with
multi module builds.
If one of the modules is a war module and depends on another module, the
dependency module will not be included as a jar file in WEB-INF/lib of the war
file, but as an empty directory instead. Non module dependencies will be
included correctly.
This bug does occur when the following conditions are met:
- running release:prepare/release:perform
- element is present, so that release goals are
"deploy site-deploy"
- element contains javadoc-maven-plugin
Please note that when running "mvn install" or "mvn deploy" the resulting war
file is ok, while "mvn release:perform" creates corrupt files as described.
Also, if javadoc-maven-plugin is not present in block, the war file
is fine, too.
I have no idea whether this bug is maven core or rather release-plugin or even
javadoc-plugin related, so I file it here. I prepared a minimal self contained
example and attach it as mm.zip. To run the example, the following steps are
needed:
{code}
cd /tmp
unzip /path/to/mm.zip
cd mm
git init
git add pom.xml mm-lib mm-war .gitignore
git commit
mvn release:prepare
mvn release:perform
{code}
After building the resulting corrupt war file can be found here:
repo/com/example/mm/mm-war/1.0.0/mm-war-1.0.0.war
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Created] (MPOM-170) migrate to Git
Hervé Boutemy created MPOM-170: -- Summary: migrate to Git Key: MPOM-170 URL: https://issues.apache.org/jira/browse/MPOM-170 Project: Maven POMs Issue Type: Task Components: asf Affects Versions: ASF-18 Reporter: Hervé Boutemy Fix For: ASF-19 https://gitbox.apache.org/repos/asf/maven-apache-parent.git CI: https://builds.apache.org/view/M-R/view/Maven/job/ASF%20Parent%20Pom/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MPOM-170) migrate to Git
[ https://issues.apache.org/jira/browse/MPOM-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238861#comment-16238861 ] Hudson commented on MPOM-170: - SUCCESS: Integrated in Jenkins build ASF Parent Pom #167 (See [https://builds.apache.org/job/ASF%20Parent%20Pom/167/]) [MPOM-170] switched to git (hboutemy: [http://svn.apache.org/viewvc/?view=rev&rev=1814263]) * (add) MOVED_TO_GIT > migrate to Git > -- > > Key: MPOM-170 > URL: https://issues.apache.org/jira/browse/MPOM-170 > Project: Maven POMs > Issue Type: Task > Components: asf >Affects Versions: ASF-18 >Reporter: Hervé Boutemy > Fix For: ASF-19 > > > https://gitbox.apache.org/repos/asf/maven-apache-parent.git > CI: https://builds.apache.org/view/M-R/view/Maven/job/ASF%20Parent%20Pom/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MPOM-170) migrate to Git
[ https://issues.apache.org/jira/browse/MPOM-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238873#comment-16238873 ] Hudson commented on MPOM-170: - SUCCESS: Integrated in Jenkins build ASF Parent Pom #170 (See [https://builds.apache.org/job/ASF%20Parent%20Pom/170/]) [MPOM-170] switched to git (hboutemy: [https://gitbox.apache.org/repos/asf?p=maven-apache-parent.git&a=commit&h=4666e18032bfe9c9bce208e865b72dc88a8d380d]) * (add) .gitignore * (edit) pom.xml > migrate to Git > -- > > Key: MPOM-170 > URL: https://issues.apache.org/jira/browse/MPOM-170 > Project: Maven POMs > Issue Type: Task > Components: asf >Affects Versions: ASF-18 >Reporter: Hervé Boutemy > Fix For: ASF-19 > > > https://gitbox.apache.org/repos/asf/maven-apache-parent.git > CI: https://builds.apache.org/view/M-R/view/Maven/job/ASF%20Parent%20Pom/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (MPOM-170) migrate to Git
[ https://issues.apache.org/jira/browse/MPOM-170?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed MPOM-170. -- Resolution: Fixed Assignee: Hervé Boutemy > migrate to Git > -- > > Key: MPOM-170 > URL: https://issues.apache.org/jira/browse/MPOM-170 > Project: Maven POMs > Issue Type: Task > Components: asf >Affects Versions: ASF-18 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy > Fix For: ASF-19 > > > https://gitbox.apache.org/repos/asf/maven-apache-parent.git > CI: https://builds.apache.org/view/M-R/view/Maven/job/ASF%20Parent%20Pom/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (MPOM-171) migrate to Git
Hervé Boutemy created MPOM-171: -- Summary: migrate to Git Key: MPOM-171 URL: https://issues.apache.org/jira/browse/MPOM-171 Project: Maven POMs Issue Type: Task Components: doxia-tools, maven, maven-archeypes, maven-plugins, maven-shared-components, maven-skins Affects Versions: MAVEN-30 Environment: https://gitbox.apache.org/repos/asf/maven-parent.git CI: https://builds.apache.org/view/M-R/view/Maven/job/maven-parent/ Reporter: Hervé Boutemy Assignee: Hervé Boutemy Fix For: MAVEN-31 -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MPOM-171) migrate to Git
[ https://issues.apache.org/jira/browse/MPOM-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238880#comment-16238880 ] Hudson commented on MPOM-171: - FAILURE: Integrated in Jenkins build maven-parent #2095 (See [https://builds.apache.org/job/maven-parent/2095/]) [MPOM-171] switched to git (hboutemy: [http://svn.apache.org/viewvc/?view=rev&rev=1814266]) * (add) MOVED_TO_GIT > migrate to Git > -- > > Key: MPOM-171 > URL: https://issues.apache.org/jira/browse/MPOM-171 > Project: Maven POMs > Issue Type: Task > Components: doxia-tools, maven, maven-archeypes, maven-plugins, > maven-shared-components, maven-skins >Affects Versions: MAVEN-30 > Environment: https://gitbox.apache.org/repos/asf/maven-parent.git > CI: https://builds.apache.org/view/M-R/view/Maven/job/maven-parent/ >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy > Fix For: MAVEN-31 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MPOM-170) migrate to Git
[ https://issues.apache.org/jira/browse/MPOM-170?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238883#comment-16238883 ] Hudson commented on MPOM-170: - SUCCESS: Integrated in Jenkins build ASF Parent Pom #172 (See [https://builds.apache.org/job/ASF%20Parent%20Pom/172/]) [MPOM-170] switched to git (hboutemy: [https://gitbox.apache.org/repos/asf?p=maven-apache-parent.git&a=commit&h=1dc92369a098c4ce36b33edaf2a37a70393440e5]) * (edit) site-pom.xml > migrate to Git > -- > > Key: MPOM-170 > URL: https://issues.apache.org/jira/browse/MPOM-170 > Project: Maven POMs > Issue Type: Task > Components: asf >Affects Versions: ASF-18 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy > Fix For: ASF-19 > > > https://gitbox.apache.org/repos/asf/maven-apache-parent.git > CI: https://builds.apache.org/view/M-R/view/Maven/job/ASF%20Parent%20Pom/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MPOM-171) migrate to Git
[ https://issues.apache.org/jira/browse/MPOM-171?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238885#comment-16238885 ] Hudson commented on MPOM-171: - SUCCESS: Integrated in Jenkins build maven-parent #2098 (See [https://builds.apache.org/job/maven-parent/2098/]) [MPOM-171] switched to Git (hboutemy: [https://gitbox.apache.org/repos/asf?p=maven-parent.git&a=commit&h=02b1cf87a5f64b6a69bbdc7f902c1aee381c052c]) * (edit) maven-archetype-bundles/pom.xml * (edit) maven-skins/pom.xml * (edit) site-pom.xml * (edit) apache-resource-bundles/pom.xml * (edit) doxia-tools/pom.xml * (edit) maven-plugins/pom.xml * (add) .gitignore * (edit) maven-shared-components/pom.xml * (edit) pom.xml > migrate to Git > -- > > Key: MPOM-171 > URL: https://issues.apache.org/jira/browse/MPOM-171 > Project: Maven POMs > Issue Type: Task > Components: doxia-tools, maven, maven-archeypes, maven-plugins, > maven-shared-components, maven-skins >Affects Versions: MAVEN-30 > Environment: https://gitbox.apache.org/repos/asf/maven-parent.git > CI: https://builds.apache.org/view/M-R/view/Maven/job/maven-parent/ >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy > Fix For: MAVEN-31 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MPOM-171) migrate to Git
[ https://issues.apache.org/jira/browse/MPOM-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MPOM-171: --- Environment: (was: https://gitbox.apache.org/repos/asf/maven-parent.git CI: https://builds.apache.org/view/M-R/view/Maven/job/maven-parent/ ) > migrate to Git > -- > > Key: MPOM-171 > URL: https://issues.apache.org/jira/browse/MPOM-171 > Project: Maven POMs > Issue Type: Task > Components: doxia-tools, maven, maven-archeypes, maven-plugins, > maven-shared-components, maven-skins >Affects Versions: MAVEN-30 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy > Fix For: MAVEN-31 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (MPOM-171) migrate to Git
[ https://issues.apache.org/jira/browse/MPOM-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed MPOM-171. -- Resolution: Fixed > migrate to Git > -- > > Key: MPOM-171 > URL: https://issues.apache.org/jira/browse/MPOM-171 > Project: Maven POMs > Issue Type: Task > Components: doxia-tools, maven, maven-archeypes, maven-plugins, > maven-shared-components, maven-skins >Affects Versions: MAVEN-30 > Environment: https://gitbox.apache.org/repos/asf/maven-parent.git > CI: https://builds.apache.org/view/M-R/view/Maven/job/maven-parent/ >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy > Fix For: MAVEN-31 > > -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MPOM-171) migrate to Git
[ https://issues.apache.org/jira/browse/MPOM-171?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MPOM-171: --- Description: https://gitbox.apache.org/repos/asf/maven-parent.git CI: https://builds.apache.org/view/M-R/view/Maven/job/maven-parent/ > migrate to Git > -- > > Key: MPOM-171 > URL: https://issues.apache.org/jira/browse/MPOM-171 > Project: Maven POMs > Issue Type: Task > Components: doxia-tools, maven, maven-archeypes, maven-plugins, > maven-shared-components, maven-skins >Affects Versions: MAVEN-30 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy > Fix For: MAVEN-31 > > > https://gitbox.apache.org/repos/asf/maven-parent.git > CI: https://builds.apache.org/view/M-R/view/Maven/job/maven-parent/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (MSKINS-136) switch to Git
Hervé Boutemy created MSKINS-136: Summary: switch to Git Key: MSKINS-136 URL: https://issues.apache.org/jira/browse/MSKINS-136 Project: Maven Skins Issue Type: Task Components: Default Skin, Fluido Skin Affects Versions: fluido-1.6, default-1.2 Reporter: Hervé Boutemy Assignee: Hervé Boutemy Fix For: fluido-2.0 https://gitbox.apache.org/repos/asf/maven-default-skin.git https://gitbox.apache.org/repos/asf/maven-fluido-skin.git CI: https://builds.apache.org/view/M-R/view/Maven/job/maven-skins/ to be split into 2 new jobs -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MSKINS-136) switch to Git
[ https://issues.apache.org/jira/browse/MSKINS-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238910#comment-16238910 ] Hudson commented on MSKINS-136: --- FAILURE: Integrated in Jenkins build maven-skins #278 (See [https://builds.apache.org/job/maven-skins/278/]) [MSKINS-136] switched to Git (hboutemy: [http://svn.apache.org/viewvc/?view=rev&rev=1814272]) * (add) MOVED_TO_GIT * (edit) README * (add) maven-default-skin/MOVED_TO_GIT * (add) maven-fluido-skin/MOVED_TO_GIT > switch to Git > - > > Key: MSKINS-136 > URL: https://issues.apache.org/jira/browse/MSKINS-136 > Project: Maven Skins > Issue Type: Task > Components: Default Skin, Fluido Skin >Affects Versions: default-1.2, fluido-1.6 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy > Fix For: fluido-2.0 > > > https://gitbox.apache.org/repos/asf/maven-default-skin.git > https://gitbox.apache.org/repos/asf/maven-fluido-skin.git > CI: https://builds.apache.org/view/M-R/view/Maven/job/maven-skins/ > to be split into 2 new jobs -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (MJAVADOC-494) javadoc:aggregate ignores repositories declared in sub-modules
[
https://issues.apache.org/jira/browse/MJAVADOC-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MJAVADOC-494.
---
Resolution: Fixed
Fixed in [r1814274|http://svn.apache.org/viewvc?rev=1814274&view=rev]
This commit also introduces the Mock Repository Manager, so I had to move the
ITs.
Real fix is in
[AbstractJavadocMojo|http://svn.apache.org/viewvc/maven/plugins/trunk/maven-javadoc-plugin/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java?limit_changes=0&r1=1814274&r2=1814273&pathrev=1814274]
> javadoc:aggregate ignores repositories declared in sub-modules
> --
>
> Key: MJAVADOC-494
> URL: https://issues.apache.org/jira/browse/MJAVADOC-494
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: javadoc
>Affects Versions: 3.0.0-M1
> Environment: Maven Javadoc plugin 3.0.0-M1
> Apache Maven 3.5.0
> Java version 1.8.0_144
>Reporter: Martin Desruisseaux
>Assignee: Robert Scholte
>Priority: Major
> Labels: regression
> Fix For: 3.0.0
>
>
> Given a multi-modules project with:
> * A {{… URL A …}} element in the root {{pom.xml}}.
> * Another {{… URL B …}} element in the {{pom.xml}}
> of a module, for downloading a JAR file used only by that specific module (we
> do that in order to depend only on Maven central for all modules except one).
> Then:
> * {{mvn install}} works: it download all JAR files as expected.
> * {{mvn javadoc:javadoc}} also work with both Maven Javadoc plugin 2.10.4 and
> 3.0.0-M1.
> * {{mvn javadoc:aggregate}} with Maven Javadoc plugin 2.10.4 works.
> * {{mvn javadoc:aggregate}} with Maven Javadoc plugin 3.0.0-M1 fails.
> Maven Javadoc plugin 3.0.0-M1 execution produces the following logs
> (simplified for brevity):
> {noformat}
> Downloading: URL A/.../MyArtifact.jar
> Downloading: https://repo.maven.apache.org/maven2/.../MyArtifact.jar
> {noformat}
> No download attempt from URL B is reported, despite the {{}}
> declaration in a sub-module. Note that the JAR is present in my
> {{.m2/repository}} directory but is apparently ignored.
> Downgrading Maven Javadoc plugin to 2.10.4 with everything else identical
> allows successful aggregated Javadoc generation.
> *Note:* another user apparently has [the same issue on stack
> overflow|https://stackoverflow.com/questions/46034250/maven-javadocaggregate-artifacts-could-not-be-resolved].
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MJAVADOC-494) javadoc:aggregate ignores repositories declared in sub-modules
[ https://issues.apache.org/jira/browse/MJAVADOC-494?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238922#comment-16238922 ] Hudson commented on MJAVADOC-494: - SUCCESS: Integrated in Jenkins build maven-plugins #9181 (See [https://builds.apache.org/job/maven-plugins/9181/]) [MJAVADOC-494] javadoc:aggregate ignores repositories declared in sub-modules Introduce mock repository manager restructure IT folders (rfscholte: [http://svn.apache.org/viewvc/?view=rev&rev=1814274]) * (edit) maven-javadoc-plugin/pom.xml * (delete) maven-javadoc-plugin/src/it/MJAVADOC-110 * (delete) maven-javadoc-plugin/src/it/MJAVADOC-126 * (delete) maven-javadoc-plugin/src/it/MJAVADOC-137 * (delete) maven-javadoc-plugin/src/it/MJAVADOC-172 * (delete) maven-javadoc-plugin/src/it/MJAVADOC-180 * (delete) maven-javadoc-plugin/src/it/MJAVADOC-181 * (delete) maven-javadoc-plugin/src/it/MJAVADOC-194 * (delete) maven-javadoc-plugin/src/it/MJAVADOC-250 * (delete) maven-javadoc-plugin/src/it/MJAVADOC-257 * (delete) maven-javadoc-plugin/src/it/MJAVADOC-259 * (delete) maven-javadoc-plugin/src/it/MJAVADOC-262 * (delete) maven-javadoc-plugin/src/it/MJAVADOC-275 * (delete) maven-javadoc-plugin/src/it/MJAVADOC-278 * (delete) maven-javadoc-plugin/src/it/MJAVADOC-320 * (delete) maven-javadoc-plugin/src/it/MJAVADOC-325 * (delete) maven-javadoc-plugin/src/it/MJAVADOC-365 * (delete) maven-javadoc-plugin/src/it/MJAVADOC-369 * (delete) maven-javadoc-plugin/src/it/MJAVADOC-384 * (delete) maven-javadoc-plugin/src/it/MJAVADOC-407 * (delete) maven-javadoc-plugin/src/it/MJAVADOC-414 * (delete) maven-javadoc-plugin/src/it/MJAVADOC-437 * (delete) maven-javadoc-plugin/src/it/MJAVADOC-498_modulepath * (delete) maven-javadoc-plugin/src/it/additional-dependencies * (delete) maven-javadoc-plugin/src/it/additional-dependencies-non-aggregate * (delete) maven-javadoc-plugin/src/it/dependencySource-1 * (delete) maven-javadoc-plugin/src/it/dependencySource-2 * (delete) maven-javadoc-plugin/src/it/dependencySource-3 * (delete) maven-javadoc-plugin/src/it/dependencySource-4 * (delete) maven-javadoc-plugin/src/it/detectLinks * (delete) maven-javadoc-plugin/src/it/javadoc-fix * (add) maven-javadoc-plugin/src/it/mrm * (add) maven-javadoc-plugin/src/it/mrm/3rdparty * (add) maven-javadoc-plugin/src/it/mrm/3rdparty/lib-1.0.pom * (add) maven-javadoc-plugin/src/it/mrm/settings.xml * (delete) maven-javadoc-plugin/src/it/output-encoding * (add) maven-javadoc-plugin/src/it/projects * (add) maven-javadoc-plugin/src/it/projects/MJAVADOC-110 * (add) maven-javadoc-plugin/src/it/projects/MJAVADOC-110/pom.xml * (add) maven-javadoc-plugin/src/it/projects/MJAVADOC-110/test-module * (add) maven-javadoc-plugin/src/it/projects/MJAVADOC-110/test-module/pom.xml * (add) maven-javadoc-plugin/src/it/projects/MJAVADOC-110/test-module/src * (add) maven-javadoc-plugin/src/it/projects/MJAVADOC-110/test-module/src/main * (add) maven-javadoc-plugin/src/it/projects/MJAVADOC-110/test-module/src/main/java * (add) maven-javadoc-plugin/src/it/projects/MJAVADOC-110/test-module/src/main/java/Test.java * (add) maven-javadoc-plugin/src/it/projects/MJAVADOC-110/verify.bsh * (add) maven-javadoc-plugin/src/it/projects/MJAVADOC-126 * (add) maven-javadoc-plugin/src/it/projects/MJAVADOC-126/invoker.properties * (add) maven-javadoc-plugin/src/it/projects/MJAVADOC-126/pom.xml * (add) maven-javadoc-plugin/src/it/projects/MJAVADOC-126/res1 * (add) maven-javadoc-plugin/src/it/projects/MJAVADOC-126/res1/pom.xml * (add) maven-javadoc-plugin/src/it/projects/MJAVADOC-126/res1/src * (add) maven-javadoc-plugin/src/it/projects/MJAVADOC-126/res1/src/main * (add) maven-javadoc-plugin/src/it/projects/MJAVADOC-126/res1/src/main/resources * (add) maven-javadoc-plugin/src/it/projects/MJAVADOC-126/res1/src/main/resources/file1.txt * (add) maven-javadoc-plugin/src/it/projects/MJAVADOC-126/res2 * (add) maven-javadoc-plugin/src/it/projects/MJAVADOC-126/res2/pom.xml * (add) maven-javadoc-plugin/src/it/projects/MJAVADOC-126/res2/src * (add) maven-javadoc-plugin/src/it/projects/MJAVADOC-126/res2/src/main * (add) maven-javadoc-plugin/src/it/projects/MJAVADOC-126/res2/src/main/resources * (add) maven-javadoc-plugin/src/it/projects/MJAVADOC-126/res2/src/main/resources/file2.txt * (add) maven-javadoc-plugin/src/it/projects/MJAVADOC-126/test * (add) maven-javadoc-plugin/src/it/projects/MJAVADOC-126/test/pom.xml * (add) maven-javadoc-plugin/src/it/projects/MJAVADOC-126/test/src * (add) maven-javadoc-plugin/src/it/projects/MJAVADOC-126/test/src/main * (add) maven-javadoc-plugin/src/it/projects/MJAVADOC-126/test/src/main/java * (add) maven-javadoc-plugin/src/it/projects/MJAVADOC-126/test/src/main/java/test * (add) maven-javadoc-plugin/src/it/projects/MJAVADOC-126/test/src/main/java/test/TestClass.java * (add) maven-javadoc-plugin/src/it/projects/MJAVADOC-126/verify.bsh * (add) maven-javadoc-plugin/src/it/projects/MJAVADOC-137 * (add) maven-javadoc-plugin/src/i
[jira] [Updated] (MSKINS-136) switch to Git
[ https://issues.apache.org/jira/browse/MSKINS-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MSKINS-136: - Description: https://gitbox.apache.org/repos/asf/maven-default-skin.git https://gitbox.apache.org/repos/asf/maven-fluido-skin.git CI: https://builds.apache.org/view/M-R/view/Maven/job/maven-skins/ to be split into 2 new jobs: https://builds.apache.org/view/M-R/view/Maven/job/maven-default-skin/ https://builds.apache.org/view/M-R/view/Maven/job/maven-fluido-skin/ was: https://gitbox.apache.org/repos/asf/maven-default-skin.git https://gitbox.apache.org/repos/asf/maven-fluido-skin.git CI: https://builds.apache.org/view/M-R/view/Maven/job/maven-skins/ to be split into 2 new jobs > switch to Git > - > > Key: MSKINS-136 > URL: https://issues.apache.org/jira/browse/MSKINS-136 > Project: Maven Skins > Issue Type: Task > Components: Default Skin, Fluido Skin >Affects Versions: default-1.2, fluido-1.6 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy > Fix For: fluido-2.0 > > > https://gitbox.apache.org/repos/asf/maven-default-skin.git > https://gitbox.apache.org/repos/asf/maven-fluido-skin.git > CI: https://builds.apache.org/view/M-R/view/Maven/job/maven-skins/ > to be split into 2 new jobs: > https://builds.apache.org/view/M-R/view/Maven/job/maven-default-skin/ > https://builds.apache.org/view/M-R/view/Maven/job/maven-fluido-skin/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MSKINS-136) switch to Git
[ https://issues.apache.org/jira/browse/MSKINS-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238963#comment-16238963 ] Hudson commented on MSKINS-136: --- SUCCESS: Integrated in Jenkins build maven-default-skin #3 (See [https://builds.apache.org/job/maven-default-skin/3/]) [MSKINS-136] switched to Git (hboutemy: [https://gitbox.apache.org/repos/asf?p=maven-default-skin.git&a=commit&h=afb0d816329d01a27483f4b6c5109c7af3b73818]) * (edit) pom.xml * (add) .gitignore > switch to Git > - > > Key: MSKINS-136 > URL: https://issues.apache.org/jira/browse/MSKINS-136 > Project: Maven Skins > Issue Type: Task > Components: Default Skin, Fluido Skin >Affects Versions: default-1.2, fluido-1.6 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy > Fix For: fluido-2.0 > > > https://gitbox.apache.org/repos/asf/maven-default-skin.git > https://gitbox.apache.org/repos/asf/maven-fluido-skin.git > CI: https://builds.apache.org/view/M-R/view/Maven/job/maven-skins/ > to be split into 2 new jobs: > https://builds.apache.org/view/M-R/view/Maven/job/maven-default-skin/ > https://builds.apache.org/view/M-R/view/Maven/job/maven-fluido-skin/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (MSKINS-136) switch to Git
[ https://issues.apache.org/jira/browse/MSKINS-136?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed MSKINS-136. Resolution: Fixed Fix Version/s: default-1.3 > switch to Git > - > > Key: MSKINS-136 > URL: https://issues.apache.org/jira/browse/MSKINS-136 > Project: Maven Skins > Issue Type: Task > Components: Default Skin, Fluido Skin >Affects Versions: default-1.2, fluido-1.6 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy > Fix For: default-1.3, fluido-2.0 > > > https://gitbox.apache.org/repos/asf/maven-default-skin.git > https://gitbox.apache.org/repos/asf/maven-fluido-skin.git > CI: https://builds.apache.org/view/M-R/view/Maven/job/maven-skins/ > to be split into 2 new jobs: > https://builds.apache.org/view/M-R/view/Maven/job/maven-default-skin/ > https://builds.apache.org/view/M-R/view/Maven/job/maven-fluido-skin/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MSKINS-136) switch to Git
[ https://issues.apache.org/jira/browse/MSKINS-136?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238964#comment-16238964 ] Hudson commented on MSKINS-136: --- SUCCESS: Integrated in Jenkins build maven-fluido-skin #2 (See [https://builds.apache.org/job/maven-fluido-skin/2/]) [MSKINS-136] switched to Git (hboutemy: [https://gitbox.apache.org/repos/asf?p=maven-fluido-skin.git&a=commit&h=a6cbc617c3fc75757852d652465b0b7372766f00]) * (edit) pom.xml * (add) .gitignore > switch to Git > - > > Key: MSKINS-136 > URL: https://issues.apache.org/jira/browse/MSKINS-136 > Project: Maven Skins > Issue Type: Task > Components: Default Skin, Fluido Skin >Affects Versions: default-1.2, fluido-1.6 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy > Fix For: default-1.3, fluido-2.0 > > > https://gitbox.apache.org/repos/asf/maven-default-skin.git > https://gitbox.apache.org/repos/asf/maven-fluido-skin.git > CI: https://builds.apache.org/view/M-R/view/Maven/job/maven-skins/ > to be split into 2 new jobs: > https://builds.apache.org/view/M-R/view/Maven/job/maven-default-skin/ > https://builds.apache.org/view/M-R/view/Maven/job/maven-fluido-skin/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (DOXIATOOLS-58) switch to Git
Hervé Boutemy created DOXIATOOLS-58: --- Summary: switch to Git Key: DOXIATOOLS-58 URL: https://issues.apache.org/jira/browse/DOXIATOOLS-58 Project: Maven Doxia Tools Issue Type: Task Components: Doxia Converter, Doxia Linkcheck Affects Versions: doxia-converter-1.2, doxia-linkcheck-1.2 Reporter: Hervé Boutemy Assignee: Hervé Boutemy Fix For: doxia-linkcheck-1.3, doxia-converter-1.3 https://gitbox.apache.org/repos/asf/maven-doxia-converter.git https://gitbox.apache.org/repos/asf/maven-doxia-linkcheck.git CI: https://builds.apache.org/view/M-R/view/Maven/job/doxia-tools/ require 2 new jobs: https://builds.apache.org/view/M-R/view/Maven/job/doxia-converter/ https://builds.apache.org/view/M-R/view/Maven/job/doxia-linkcheck/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DOXIATOOLS-58) switch to Git
[ https://issues.apache.org/jira/browse/DOXIATOOLS-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238988#comment-16238988 ] Hudson commented on DOXIATOOLS-58: -- SUCCESS: Integrated in Jenkins build doxia-all #351 (See [https://builds.apache.org/job/doxia-all/351/]) [DOXIATOOLS-58] moved to Git (hboutemy: [http://svn.apache.org/viewvc/?view=rev&rev=1814283]) * (add) ./doxia-tools/doxia-converter/MOVED_TO_GIT * (add) ./doxia-tools/doxia-linkcheck/MOVED_TO_GIT > switch to Git > - > > Key: DOXIATOOLS-58 > URL: https://issues.apache.org/jira/browse/DOXIATOOLS-58 > Project: Maven Doxia Tools > Issue Type: Task > Components: Doxia Converter, Doxia Linkcheck >Affects Versions: doxia-linkcheck-1.2, doxia-converter-1.2 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy > Fix For: doxia-linkcheck-1.3, doxia-converter-1.3 > > > https://gitbox.apache.org/repos/asf/maven-doxia-converter.git > https://gitbox.apache.org/repos/asf/maven-doxia-linkcheck.git > CI: https://builds.apache.org/view/M-R/view/Maven/job/doxia-tools/ > require 2 new jobs: > https://builds.apache.org/view/M-R/view/Maven/job/doxia-converter/ > https://builds.apache.org/view/M-R/view/Maven/job/doxia-linkcheck/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DOXIATOOLS-58) switch to Git
[ https://issues.apache.org/jira/browse/DOXIATOOLS-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16238993#comment-16238993 ] Hudson commented on DOXIATOOLS-58: -- SUCCESS: Integrated in Jenkins build doxia-all #352 (See [https://builds.apache.org/job/doxia-all/352/]) [DOXIATOOLS-58] moved to Git (hboutemy: [http://svn.apache.org/viewvc/?view=rev&rev=1814284]) * (edit) ./doxia-tools/pom.xml > switch to Git > - > > Key: DOXIATOOLS-58 > URL: https://issues.apache.org/jira/browse/DOXIATOOLS-58 > Project: Maven Doxia Tools > Issue Type: Task > Components: Doxia Converter, Doxia Linkcheck >Affects Versions: doxia-linkcheck-1.2, doxia-converter-1.2 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy > Fix For: doxia-linkcheck-1.3, doxia-converter-1.3 > > > https://gitbox.apache.org/repos/asf/maven-doxia-converter.git > https://gitbox.apache.org/repos/asf/maven-doxia-linkcheck.git > CI: https://builds.apache.org/view/M-R/view/Maven/job/doxia-tools/ > require 2 new jobs: > https://builds.apache.org/view/M-R/view/Maven/job/doxia-converter/ > https://builds.apache.org/view/M-R/view/Maven/job/doxia-linkcheck/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Closed] (DOXIATOOLS-58) switch to Git
[ https://issues.apache.org/jira/browse/DOXIATOOLS-58?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed DOXIATOOLS-58. --- Resolution: Fixed > switch to Git > - > > Key: DOXIATOOLS-58 > URL: https://issues.apache.org/jira/browse/DOXIATOOLS-58 > Project: Maven Doxia Tools > Issue Type: Task > Components: Doxia Converter, Doxia Linkcheck >Affects Versions: doxia-linkcheck-1.2, doxia-converter-1.2 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy > Fix For: doxia-linkcheck-1.3, doxia-converter-1.3 > > > https://gitbox.apache.org/repos/asf/maven-doxia-converter.git > https://gitbox.apache.org/repos/asf/maven-doxia-linkcheck.git > CI: https://builds.apache.org/view/M-R/view/Maven/job/doxia-tools/ > require 2 new jobs: > https://builds.apache.org/view/M-R/view/Maven/job/doxia-converter/ > https://builds.apache.org/view/M-R/view/Maven/job/doxia-linkcheck/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (DOXIATOOLS-58) switch to Git
[ https://issues.apache.org/jira/browse/DOXIATOOLS-58?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239012#comment-16239012 ] Hudson commented on DOXIATOOLS-58: -- SUCCESS: Integrated in Jenkins build doxia-all #353 (See [https://builds.apache.org/job/doxia-all/353/]) [DOXIATOOLS-58] moved converter and linkcheck to Git (hboutemy: [http://svn.apache.org/viewvc/?view=rev&rev=1814288]) * (edit) ./site/content/xdoc/source-repository.xml > switch to Git > - > > Key: DOXIATOOLS-58 > URL: https://issues.apache.org/jira/browse/DOXIATOOLS-58 > Project: Maven Doxia Tools > Issue Type: Task > Components: Doxia Converter, Doxia Linkcheck >Affects Versions: doxia-linkcheck-1.2, doxia-converter-1.2 >Reporter: Hervé Boutemy >Assignee: Hervé Boutemy > Fix For: doxia-linkcheck-1.3, doxia-converter-1.3 > > > https://gitbox.apache.org/repos/asf/maven-doxia-converter.git > https://gitbox.apache.org/repos/asf/maven-doxia-linkcheck.git > CI: https://builds.apache.org/view/M-R/view/Maven/job/doxia-tools/ > require 2 new jobs: > https://builds.apache.org/view/M-R/view/Maven/job/doxia-converter/ > https://builds.apache.org/view/M-R/view/Maven/job/doxia-linkcheck/ -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MENFORCER-281) RequirePluginVersions broken with "CI Friendly versions"
[
https://issues.apache.org/jira/browse/MENFORCER-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239042#comment-16239042
]
ASF GitHub Bot commented on MENFORCER-281:
--
jtnord opened a new pull request #28: [MENFORCER-281] added IT to show the
issue.
URL: https://github.com/apache/maven-enforcer/pull/28
Added an IT to demonstrate
[MENFORCER-281](https://issues.apache.org/jira/browse/MENFORCER-281)
Fails with the following which is slightly different to what is observed in
the real project, but is at least a starter for 10
```
[ERROR]
/org/apache/maven/its/enforcer/menforcer281-parent/$%7Brevision%7D/menforcer281-parent-$%7Brevision%7D.pom
java.lang.IllegalArgumentException: Illegal character in path at index 110:
https://X/org/apache/maven/its/enforcer/m
enforcer281-parent/${revision}/maven-metadata.xml
at java.net.URI.create(URI.java:852)
at
org.apache.maven.wagon.providers.http.httpclient.client.methods.HttpGet.(HttpGet.java:69)
at
org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.fillInputData(AbstractHttpClientWagon.java:972)
at
org.apache.maven.wagon.providers.http.AbstractHttpClientWagon.fillInputData(AbstractHttpClientWagon.java:962)
at
org.apache.maven.wagon.StreamWagon.getInputStream(StreamWagon.java:126)
at org.apache.maven.wagon.StreamWagon.getIfNewer(StreamWagon.java:88)
at org.apache.maven.wagon.StreamWagon.get(StreamWagon.java:61)
at
org.apache.maven.repository.legacy.DefaultWagonManager.getRemoteFile(DefaultWagonManager.java:413)
at
org.apache.maven.repository.legacy.DefaultWagonManager.getArtifactMetadata(DefaultWagonManager.java:233)
at
org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.resolve(DefaultRepositoryMetadataManager.java:132)
at
org.apache.maven.artifact.repository.metadata.DefaultRepositoryMetadataManager.resolve(DefaultRepositoryMetadataManager.java:71)
at
org.codehaus.mojo.mrm.maven.ProxyArtifactStore.getMetadata(ProxyArtifactStore.java:480)
at
org.codehaus.mojo.mrm.maven.ProxyArtifactStore.getMetadataLastModified(ProxyArtifactStore.java:536)
at
org.codehaus.mojo.mrm.impl.maven.CompositeArtifactStore.getMetadataLastModified(CompositeArtifactStore.java:339)
at
org.codehaus.mojo.mrm.impl.maven.ArtifactStoreFileSystem.listEntries(ArtifactStoreFileSystem.java:147)
at
org.codehaus.mojo.mrm.impl.digest.AutoDigestFileSystem.listEntries(AutoDigestFileSystem.java:100)
at
org.codehaus.mojo.mrm.api.BaseFileSystem.get(BaseFileSystem.java:89)
at
org.codehaus.mojo.mrm.impl.digest.AutoDigestFileSystem.get(AutoDigestFileSystem.java:185)
at
org.codehaus.mojo.mrm.servlet.FileSystemServlet.doGet(FileSystemServlet.java:157)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:707)
at javax.servlet.http.HttpServlet.service(HttpServlet.java:820)
at
org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:487)
at
org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:362)
at
org.mortbay.jetty.servlet.SessionHandler.handle(SessionHandler.java:181)
at
org.mortbay.jetty.handler.ContextHandler.handle(ContextHandler.java:712)
at
org.mortbay.jetty.handler.HandlerWrapper.handle(HandlerWrapper.java:139)
at org.mortbay.jetty.Server.handle(Server.java:313)
at
org.mortbay.jetty.HttpConnection.handleRequest(HttpConnection.java:506)
at
org.mortbay.jetty.HttpConnection$RequestHandler.headerComplete(HttpConnection.java:830)
at org.mortbay.jetty.HttpParser.parseNext(HttpParser.java:514)
at org.mortbay.jetty.HttpParser.parseAvailable(HttpParser.java:211)
at org.mortbay.jetty.HttpConnection.handle(HttpConnection.java:381)
at
org.mortbay.jetty.bio.SocketConnector$Connection.run(SocketConnector.java:227)
at
org.mortbay.thread.BoundedThreadPool$PoolThread.run(BoundedThreadPool.java:442)
Caused by: java.net.URISyntaxException: Illegal character in path at index
110: https://XX/org/apache/maven/its/enforc
er/menforcer281-parent/${revision}/maven-metadata.xml
at java.net.URI$Parser.fail(URI.java:2848)
at java.net.URI$Parser.checkChars(URI.java:3021)
at java.net.URI$Parser.parseHierarchical(URI.java:3105)
at java.net.URI$Parser.parse(URI.java:3053)
at java.net.URI.(URI.java:588)
at java.net.URI.create(URI.java:850)
... 33 more
[INFO] ..FAILED (5.7 s)
```
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL a
[jira] [Commented] (MENFORCER-276) Allow ignoring dependency scopes in RequireUpperBoundDeps
[ https://issues.apache.org/jira/browse/MENFORCER-276?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239043#comment-16239043 ] ASF GitHub Bot commented on MENFORCER-276: -- oleg-nenashev opened a new pull request #25: MENFORCER-276 - Support ignoring dependency scopes in RequireUpperBoundDeps URL: https://github.com/apache/maven-enforcer/pull/25 We have recently adopted `RequireUpperBoundDeps` in the Jenkins project (https://github.com/jenkinsci/plugin-pom/pull/67). In order to implement it, Jesse Glick added a support of ignoring particular dependencies in [MENFORCER-273](https://issues.apache.org/jira/browse/MENFORCER-273). Sometimes we declare dependencies between plugins for testing purposes (scope=test), and in such case RequireUpperBoundDeps fails the build if there is a test dependency conflicting with the main code. Although it may cause instability of tests (including false positive results), it does not really impact the distributable package in our case. I propose to add another option for filtering of dependency scopes. This pull request also adds some unit tests for `RequireUpperBoundDeps`. Previously it had integration tests only. https://issues.apache.org/jira/browse/MENFORCER-276 @reviewbybees @jglick @stephenc 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 > Allow ignoring dependency scopes in RequireUpperBoundDeps > - > > Key: MENFORCER-276 > URL: https://issues.apache.org/jira/browse/MENFORCER-276 > Project: Maven Enforcer Plugin > Issue Type: New Feature >Reporter: Oleg Nenashev >Priority: Major > > We have recently adopted RequireUpperBoundDeps in the Jenkins project > (https://github.com/jenkinsci/plugin-pom/pull/67). In order to implement it, > [~jgl...@netbeans.org] added a support of ignoring particular dependencies in > MENFORCER-273. > Sometimes we declare dependencies between plugins for testing purposes > (scope=test), and in such case RequireUpperBoundDeps fails the build if there > is a test dependency conflicting with the main code. Although it may cause > instability of tests (including false positive results), it does not really > impact the distributable package in our case. > I propose to add another option for filtering of dependency scopes. -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MENFORCER-281) RequirePluginVersions broken with "CI Friendly versions"
[
https://issues.apache.org/jira/browse/MENFORCER-281?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239045#comment-16239045
]
Simon Tunnat commented on MENFORCER-281:
Thank you for your e-mail.
I will be back from vacation on 05-11-2017.
Your e-mail will not be forwarded. So it will be personally replied after my
return.
For urgent matters please contact: Stefan Schulte (stefanit.schu...@viega.de)
Kind regards
Simon Tunnat
==
Sehr geehrte Damen und Herren,
ich befinde mich zurzeit im Urlaub und werde ab dem 05.11.2017 wieder im Büro
sein.
Ihre E-Mail bleibt in meinem Postfach und wird nach meiner Rückkehr bearbeitet.
In dringenden Fällen wenden Sie sich bitte an: Stefan Schulte
(stefanit.schu...@viega.de)
Mit Freundliche Grüßen
Simon Tunnat
> RequirePluginVersions broken with "CI Friendly versions"
>
>
> Key: MENFORCER-281
> URL: https://issues.apache.org/jira/browse/MENFORCER-281
> Project: Maven Enforcer Plugin
> Issue Type: Bug
> Components: Standard Rules
>Affects Versions: 1.4.1, 3.0.0-M1
>Reporter: James Nord
>Priority: Critical
>
> Maven
> [3.5.0|https://maven.apache.org/docs/3.5.0/release-notes.html#Overview_about_the_changes]
> [introduced CI friendly
> versions|https://maven.apache.org/maven-ci-friendly.html].
> However when used with [multi module
> project|https://maven.apache.org/maven-ci-friendly.html#Multi_Module_Setup]
> the enforcer fails the build as it can not resolve the parent.
> The bug is that the parent resolution of a module in the reactor is
> attempting to use the untransposed version.
> e.g.
> {noformat}
> INFO] --- maven-enforcer-plugin:3.0.0-M1:enforce (display-info) @ sub-module
> ---
> [WARNING] Rule 1: org.apache.maven.plugins.enforcer.RequirePluginVersions
> failed with message:
> Failure to find com.acme.product:parent:pom:0.9.8-${revision}SNAPSHOT in
> https://repo.acme.com/content/groups/all was cached in the local repository,
> resolution will not be reattempted until the update interval of acme-internal
> has elapsed or updates are forced
> com.acme.product:parent:pom:0.9.8-${revision}SNAPSHOT
> from the specified remote repositories:
> acme-internal (https://repo.acme.com/content/groups/all, releases=true,
> snapshots=true)
> {noformat}
> to reproduce create a new multi module project as per the linked page above.
> Add the enforcer plugin and rule to the build
> run {{mvn -Drevision=1.2.3-SNAPSHOT}} and watch the build fail.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MJLINK-4) NPE on execution
[
https://issues.apache.org/jira/browse/MJLINK-4?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239058#comment-16239058
]
Hudson commented on MJLINK-4:
-
SUCCESS: Integrated in Jenkins build maven-plugins #9184 (See
[https://builds.apache.org/job/maven-plugins/9184/])
[MJLINK-4] run this IT only when Java 9 (hboutemy:
[http://svn.apache.org/viewvc/?view=rev&rev=1814295])
* (add)
maven-jlink-plugin/src/it/projects/MJLINK-4_dependencyResolution/invoker.properties
> NPE on execution
> -
>
> Key: MJLINK-4
> URL: https://issues.apache.org/jira/browse/MJLINK-4
> Project: Maven JLink Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha-1
> Environment: Ubuntu 16.04.3 LTS
> Linux 4.4.0-93-generic
>Reporter: Johannes Boesl
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.0.0-alpha-2
>
>
> When I try to run my maven build I get the following exception:
> {noformat}[ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink
> (default-jlink) on project jloadr-jre: Execution default-jlink of goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.:
> NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink
> (default-jlink) on project jloadr-jre: Execution default-jlink of goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:213)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:200)
> at
> org.apache.maven.lifecycle.internal.builder.multithreaded.MultiThreadedBuilder$1.call(MultiThreadedBuilder.java:196)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:514)
> at java.base/java.util.concurrent.FutureTask.run(FutureTask.java:264)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1167)
> at
> java.base/java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:641)
> at java.base/java.lang.Thread.run(Thread.java:844)
> Caused by: org.apache.maven.plugin.PluginExecutionException: Execution
> default-jlink of goal
> org.apache.maven.plugins:maven-jlink-plugin:3.0.0-alpha-1:jlink failed.
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:145)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> ... 11 more
> Caused by: java.lang.NullPointerException
> at
> org.codehaus.plexus.languages.java.jpms.ResolvePathsRequest$1.toPath(ResolvePathsRequest.java:52)
> at
> org.codehaus.plexus.languages.java.jpms.ResolvePathsRequest$1.toPath(ResolvePathsRequest.java:48)
> at
> org.codehaus.plexus.languages.java.jpms.LocationManager.resolvePaths(LocationManager.java:109)
> at
> org.apache.maven.plugins.jlink.JLinkMojo.preparePaths(JLinkMojo.java:347)
> at org.apache.maven.plugins.jlink.JLinkMojo.execute(JLinkMojo.java:264)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> ... 12 more{quote}
> {noformat}
> The cause seems to be that the following code in line 337 in JLinkMojo
> returns a collection with only 'null' entries:
> {{Collection dependencyArtifacts = getCompileClasspathElements(
> getProject() );}}
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MSHADE-234) support java 9 modules (jigsaw)
[ https://issues.apache.org/jira/browse/MSHADE-234?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239140#comment-16239140 ] Romain Manni-Bucau commented on MSHADE-234: --- up? > support java 9 modules (jigsaw) > --- > > Key: MSHADE-234 > URL: https://issues.apache.org/jira/browse/MSHADE-234 > Project: Maven Shade Plugin > Issue Type: New Feature >Reporter: sam rash >Priority: Major > > Java 9 will begin in including the module-info.class file which has the > packages that are exported. It would be great if the shade plugin can detect > the new format, and for any packages that are moved, it updates the module > exports accordingly -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (MSHADE-264) handle module-info merge in shades for java 9 support
Romain Manni-Bucau created MSHADE-264: - Summary: handle module-info merge in shades for java 9 support Key: MSHADE-264 URL: https://issues.apache.org/jira/browse/MSHADE-264 Project: Maven Shade Plugin Issue Type: Improvement Reporter: Romain Manni-Bucau Priority: Major asm uses module-info so we should merge it properly when we are deployed into the appclassloader of a java 9 JVM -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Created] (MSHADE-265) correct merging of module-info in shades
Romain Manni-Bucau created MSHADE-265: - Summary: correct merging of module-info in shades Key: MSHADE-265 URL: https://issues.apache.org/jira/browse/MSHADE-265 Project: Maven Shade Plugin Issue Type: Improvement Reporter: Romain Manni-Bucau -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MSHADE-265) correct merging of module-info in shades
[ https://issues.apache.org/jira/browse/MSHADE-265?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Romain Manni-Bucau updated MSHADE-265: -- Description: Should work by merging of the encountered module info jut also automatic module name in manifest. The hard part being removing the not needed entries which are sometimes not simply the ones of the included classes - SPI need it still > correct merging of module-info in shades > > > Key: MSHADE-265 > URL: https://issues.apache.org/jira/browse/MSHADE-265 > Project: Maven Shade Plugin > Issue Type: Improvement >Reporter: Romain Manni-Bucau > > Should work by merging of the encountered module info jut also automatic > module name in manifest. The hard part being removing the not needed entries > which are sometimes not simply the ones of the included classes - SPI need it > still -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MNG-2971) Variables are not replaced into installed pom file
[
https://issues.apache.org/jira/browse/MNG-2971?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239224#comment-16239224
]
Peng Cheng commented on MNG-2971:
-
Why I'm still observing this in maven 3.5.0?
I thought it was fixed long time ago.
> Variables are not replaced into installed pom file
> --
>
> Key: MNG-2971
> URL: https://issues.apache.org/jira/browse/MNG-2971
> Project: Maven
> Issue Type: Bug
> Components: Deployment, Inheritance and Interpolation
> Environment: Windows, Solaris
> Maven version 2.0.4
>Reporter: Laurent Dauvilaire
>Assignee: Ralph Goers
>Priority: Major
> Fix For: Issues to be reviewed for 3.x
>
> Attachments: pom.xml
>
>
> Variables are not replaced into installed pom file.
> Here is a sample pom file
> {code:xml}
> http://maven.apache.org/POM/4.0.0";
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/maven-v4_0_0.xsd";>
> 4.0.0
> com.xxx.root
> root
> pom
> ${prop.version}
> My Project
> ...
>
> 3.0.20
>
>
> {code}
> The installed pom is into
> $\{localRepository}/com/xxx/root/root/3.0.20/root-3.0.20.pom
> is the same as the project pom file but the version referenced into the
> installed pom file is $\{prop.version} instead of 3.0.20
> which creates problem to artifacts depending of this one.
> Thanks in advance
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MSHADE-265) correct merging of module-info in shades
[ https://issues.apache.org/jira/browse/MSHADE-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239265#comment-16239265 ] Robert Scholte commented on MSHADE-265: --- We had this discussion with a couple of Maven teammember and Mark Reinhold at FOSDEM and we came to the conclusion we should never merge module descriptors. The main reason: you will break strong encapsulation. There is still an open issue for it on the JPMS issue list, waiting to be picked up in a next Java release. I think in case of libraries this cannot be solved. But in case of applications I hope implementing MSHADE-262 will do the job. > correct merging of module-info in shades > > > Key: MSHADE-265 > URL: https://issues.apache.org/jira/browse/MSHADE-265 > Project: Maven Shade Plugin > Issue Type: Improvement >Reporter: Romain Manni-Bucau >Priority: Trivial > > Should work by merging of the encountered module info jut also automatic > module name in manifest. The hard part being removing the not needed entries > which are sometimes not simply the ones of the included classes - SPI need it > still -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MSHADE-264) handle module-info merge in shades for java 9 support
[ https://issues.apache.org/jira/browse/MSHADE-264?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239267#comment-16239267 ] Robert Scholte commented on MSHADE-264: --- duplicate of MSHADE-265? > handle module-info merge in shades for java 9 support > - > > Key: MSHADE-264 > URL: https://issues.apache.org/jira/browse/MSHADE-264 > Project: Maven Shade Plugin > Issue Type: Improvement >Reporter: Romain Manni-Bucau > > asm uses module-info so we should merge it properly when we are deployed into > the appclassloader of a java 9 JVM -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MSHADE-265) correct merging of module-info in shades
[ https://issues.apache.org/jira/browse/MSHADE-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239270#comment-16239270 ] Romain Manni-Bucau commented on MSHADE-265: --- I know but it literally means "dont use shade plugin from now on" and "no migration of shade usages". Im sure we - or oracle - can do something better, in particular with the fatjar/shade/uberjar usage. At least we should provide a transformer with some include exclude config for all type of module info entries. > correct merging of module-info in shades > > > Key: MSHADE-265 > URL: https://issues.apache.org/jira/browse/MSHADE-265 > Project: Maven Shade Plugin > Issue Type: Improvement >Reporter: Romain Manni-Bucau >Priority: Trivial > > Should work by merging of the encountered module info jut also automatic > module name in manifest. The hard part being removing the not needed entries > which are sometimes not simply the ones of the included classes - SPI need it > still -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Commented] (MSHADE-265) correct merging of module-info in shades
[ https://issues.apache.org/jira/browse/MSHADE-265?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239301#comment-16239301 ] Robert Scholte commented on MSHADE-265: --- Let's define the usecases first (maybe with ITs), otherwise the discussion is too abstract. The chance is that modularization does solve some issues we used to solve with shading. > correct merging of module-info in shades > > > Key: MSHADE-265 > URL: https://issues.apache.org/jira/browse/MSHADE-265 > Project: Maven Shade Plugin > Issue Type: Improvement >Reporter: Romain Manni-Bucau >Priority: Trivial > > Should work by merging of the encountered module info jut also automatic > module name in manifest. The hard part being removing the not needed entries > which are sometimes not simply the ones of the included classes - SPI need it > still -- This message was sent by Atlassian JIRA (v6.4.14#64029)
[jira] [Updated] (MNG-6118) Add option to execute goals on a specific module while building a multimodule project
[
https://issues.apache.org/jira/browse/MNG-6118?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Hervé Boutemy updated MNG-6118:
---
Description:
Suppose we have a multimodule which results in a war. In the end we want to run
this war in a container like jetty. Up until now the {{jetty:run}} is executed
on every module, which doesn't make sense for the other modules.
This is just one of several examples where you want to control on which module
to execute a specific goal. In case of wars, the plugin could check for the
packaging type, but in case of jars this won't work.
There should be a generic solution to mark goals for a specific module.
was:
Suppose we have a multimodule which results in a war. In the end we want to run
this war in a container like jetty. Up until know the {{jetty:run}} is executed
on every module, which doesn't make sense for the other modules.
This is just one of several examples where you want to control on which to
execute a specific goal. In case of wars, the plugin could check for the
packaging type, but in case of jars this won't work.
There should be a generic solution to mark goals for a specific module.
> Add option to execute goals on a specific module while building a multimodule
> project
> -
>
> Key: MNG-6118
> URL: https://issues.apache.org/jira/browse/MNG-6118
> Project: Maven
> Issue Type: Improvement
> Components: Command Line, Plugins and Lifecycle
>Reporter: Robert Scholte
>
> Suppose we have a multimodule which results in a war. In the end we want to
> run this war in a container like jetty. Up until now the {{jetty:run}} is
> executed on every module, which doesn't make sense for the other modules.
> This is just one of several examples where you want to control on which
> module to execute a specific goal. In case of wars, the plugin could check
> for the packaging type, but in case of jars this won't work.
> There should be a generic solution to mark goals for a specific module.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
[jira] [Commented] (MNG-6118) Add option to execute goals on a specific module while building a multimodule project
[
https://issues.apache.org/jira/browse/MNG-6118?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16239416#comment-16239416
]
Hervé Boutemy commented on MNG-6118:
bq. solution to mark goals for a specific module
IMHO, we need to go the opposite way: ie mark modules for a specific goal
then have the goal check if the marker is present or not in the current module
> Add option to execute goals on a specific module while building a multimodule
> project
> -
>
> Key: MNG-6118
> URL: https://issues.apache.org/jira/browse/MNG-6118
> Project: Maven
> Issue Type: Improvement
> Components: Command Line, Plugins and Lifecycle
>Reporter: Robert Scholte
>
> Suppose we have a multimodule which results in a war. In the end we want to
> run this war in a container like jetty. Up until now the {{jetty:run}} is
> executed on every module, which doesn't make sense for the other modules.
> This is just one of several examples where you want to control on which
> module to execute a specific goal. In case of wars, the plugin could check
> for the packaging type, but in case of jars this won't work.
> There should be a generic solution to mark goals for a specific module.
--
This message was sent by Atlassian JIRA
(v6.4.14#64029)
