[jira] [Assigned] (DOXIASITETOOLS-223) wrong coordinates for jai_core: hyphen should be underscore
[
https://issues.apache.org/jira/browse/DOXIASITETOOLS-223?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Sylwester Lachiewicz reassigned DOXIASITETOOLS-223:
---
Assignee: Sylwester Lachiewicz
> wrong coordinates for jai_core: hyphen should be underscore
> ---
>
> Key: DOXIASITETOOLS-223
> URL: https://issues.apache.org/jira/browse/DOXIASITETOOLS-223
> Project: Maven Doxia Sitetools
> Issue Type: Bug
>Reporter: Elliotte Rusty Harold
>Assignee: Sylwester Lachiewicz
>Priority: Major
>
> {noformat}[INFO] --- maven-enforcer-plugin:1.4.1:enforce
> (enforce-bytecode-version) @ doxia-doc-renderer ---
> [WARNING] Failure to find javax.media:jai-core:jar:1.1.3 in
> https://repo.maven.apache.org/maven2 was cached in the local repository,
> resolution will not be reattempted until the update interval of central has
> elapsed or updates are forced
> Try downloading the file manually from the project website.
> Then, install it using the command:
> mvn install:install-file -DgroupId=javax.media -DartifactId=jai-core
> -Dversion=1.1.3 -Dpackaging=jar -Dfile=/path/to/file
> Alternatively, if you host your own repository you can deploy the file there:
> mvn deploy:deploy-file -DgroupId=javax.media -DartifactId=jai-core
> -Dversion=1.1.3 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url]
> -DrepositoryId=[id]
> Path to dependency:
> 1) org.apache.maven.doxia:doxia-doc-renderer:jar:1.9.3-SNAPSHOT
> 2) org.apache.maven.doxia:doxia-module-fo:jar:1.9.1
> 3) org.apache.xmlgraphics:fop:jar:2.4
> 4) org.apache.xmlgraphics:fop-core:jar:2.4
> 5) javax.media:jai-core:jar:1.1.3
> javax.media:jai-core:jar:1.1.3
> from the specified remote repositories:
> apache.snapshots (https://repository.apache.org/snapshots, releases=false,
> snapshots=true),
> central (https://repo.maven.apache.org/maven2, releases=true,
> snapshots=false){noformat}
> It looks like that should be javax.media:jai_core:jar:1.1.3 (that is,
> hyphen --> underscore)
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MSHARED-863) Possible NPEx in Maven30DependencyResolver.resolveDependencies
[
https://issues.apache.org/jira/browse/MSHARED-863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17056476#comment-17056476
]
Piotr Zygielo commented on MSHARED-863:
---
{quote}Code can be simplified and javadoc should make clear these arguments
should never be null.
{quote}
How about
[https://github.com/apache/maven-artifact-transfer/commit/b5cc4be6c616c6a1be37dd8cbb183fb6710e409f],
where author of change for DependencyResolver interface said:
{quote}@param dependencies the dependencies to resolve, can be null
{quote}
> Possible NPEx in Maven30DependencyResolver.resolveDependencies
> --
>
> Key: MSHARED-863
> URL: https://issues.apache.org/jira/browse/MSHARED-863
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-artifact-transfer
>Affects Versions: maven-artifact-transfer-0.12.0
>Reporter: Piotr Zygielo
>Priority: Major
>
> Possible NPEx in
> [Maven30DependencyResolver.resolveDependencies|https://github.com/apache/maven-artifact-transfer/blob/dc0d6bd30b855e147576c4e9cdfacf1382d69f07/src/main/java/org/apache/maven/shared/transfer/dependencies/resolve/internal/Maven30DependencyResolver.java#L156]
> {code:java}
> List aetherDependencies = new ArrayList(
> mavenDependencies.size() );
> if ( mavenDependencies != null )
> {
> aetherDependencies = new ArrayList(
> mavenDependencies.size() );
> ...
> {code}
> Line 161
> {code:java}
> if ( mavenDependencies != null )
> {code}
> suggests that {{mavenDependencies}} can be {{null}}.
> However in such case previous {{mavenDependencies.size()}} results in
> {{NPEx}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MSHARED-863) Possible NPEx in Maven30DependencyResolver.resolveDependencies
[
https://issues.apache.org/jira/browse/MSHARED-863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17056432#comment-17056432
]
Robert Scholte commented on MSHARED-863:
Collections and Maps should never be {{null}}, they should at least be an empty
instance. Code can be simplified and javadoc should make clear these arguments
should never be {{null}}.
> Possible NPEx in Maven30DependencyResolver.resolveDependencies
> --
>
> Key: MSHARED-863
> URL: https://issues.apache.org/jira/browse/MSHARED-863
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-artifact-transfer
>Affects Versions: maven-artifact-transfer-0.12.0
>Reporter: Piotr Zygielo
>Priority: Major
>
> Possible NPEx in
> [Maven30DependencyResolver.resolveDependencies|https://github.com/apache/maven-artifact-transfer/blob/dc0d6bd30b855e147576c4e9cdfacf1382d69f07/src/main/java/org/apache/maven/shared/transfer/dependencies/resolve/internal/Maven30DependencyResolver.java#L156]
> {code:java}
> List aetherDependencies = new ArrayList(
> mavenDependencies.size() );
> if ( mavenDependencies != null )
> {
> aetherDependencies = new ArrayList(
> mavenDependencies.size() );
> ...
> {code}
> Line 161
> {code:java}
> if ( mavenDependencies != null )
> {code}
> suggests that {{mavenDependencies}} can be {{null}}.
> However in such case previous {{mavenDependencies.size()}} results in
> {{NPEx}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MSHARED-863) Possible NPEx in Maven30DependencyResolver.resolveDependencies
[
https://issues.apache.org/jira/browse/MSHARED-863?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17056428#comment-17056428
]
Michael Osipov commented on MSHARED-863:
[~rfscholte], that is a good catch. WDYT?
> Possible NPEx in Maven30DependencyResolver.resolveDependencies
> --
>
> Key: MSHARED-863
> URL: https://issues.apache.org/jira/browse/MSHARED-863
> Project: Maven Shared Components
> Issue Type: Bug
> Components: maven-artifact-transfer
>Affects Versions: maven-artifact-transfer-0.12.0
>Reporter: Piotr Zygielo
>Priority: Major
>
> Possible NPEx in
> [Maven30DependencyResolver.resolveDependencies|https://github.com/apache/maven-artifact-transfer/blob/dc0d6bd30b855e147576c4e9cdfacf1382d69f07/src/main/java/org/apache/maven/shared/transfer/dependencies/resolve/internal/Maven30DependencyResolver.java#L156]
> {code:java}
> List aetherDependencies = new ArrayList(
> mavenDependencies.size() );
> if ( mavenDependencies != null )
> {
> aetherDependencies = new ArrayList(
> mavenDependencies.size() );
> ...
> {code}
> Line 161
> {code:java}
> if ( mavenDependencies != null )
> {code}
> suggests that {{mavenDependencies}} can be {{null}}.
> However in such case previous {{mavenDependencies.size()}} results in
> {{NPEx}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[GitHub] [maven-changes-plugin] michael-o commented on issue #10: new http
michael-o commented on issue #10: new http URL: https://github.com/apache/maven-changes-plugin/pull/10#issuecomment-597270152 My bad, it does not. But Azul does: https://www.azul.com/downloads/zulu-community/?=java-7-lts=x86-64-bit=jdk This is an automated message from the Apache Git Service. To respond to the message, please log on to 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
[GitHub] [maven-changes-plugin] elharo commented on issue #10: new http
elharo commented on issue #10: new http URL: https://github.com/apache/maven-changes-plugin/pull/10#issuecomment-597269417 Also, looks like that might have to be done by a Jenkins administrator? I.e. we don't configure it in this repo as we might do with Travis? This is an automated message from the Apache Git Service. To respond to the message, please log on to 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
[GitHub] [maven-changes-plugin] elharo commented on issue #11: update commons collections
elharo commented on issue #11: update commons collections URL: https://github.com/apache/maven-changes-plugin/pull/11#issuecomment-597263192 Jenkins passes this one. This is an automated message from the Apache Git Service. To respond to the message, please log on to 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
[GitHub] [maven-changes-plugin] elharo commented on issue #10: new http
elharo commented on issue #10: new http URL: https://github.com/apache/maven-changes-plugin/pull/10#issuecomment-597262851 Does AdoptOpenJDK ship a Java 7 VM? This is an automated message from the Apache Git Service. To respond to the message, please log on to 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
[GitHub] [maven-changes-plugin] elharo opened a new pull request #11: update commons collections
elharo opened a new pull request #11: update commons collections URL: https://github.com/apache/maven-changes-plugin/pull/11 @michael-o Let's take these one at a time... This is an automated message from the Apache Git Service. To respond to the message, please log on to 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
[GitHub] [maven-changes-plugin] michael-o commented on issue #10: new http
michael-o commented on issue #10: new http URL: https://github.com/apache/maven-changes-plugin/pull/10#issuecomment-597238320 We'd need either Azul Zulu or AdoptOpenJDK on Jenkins. This is an automated message from the Apache Git Service. To respond to the message, please log on to 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
[GitHub] [maven-changes-plugin] elharo commented on issue #10: new http
elharo commented on issue #10: new http URL: https://github.com/apache/maven-changes-plugin/pull/10#issuecomment-597237957 https://www.baeldung.com/java-7-tls-v12 This is an automated message from the Apache Git Service. To respond to the message, please log on to 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
[GitHub] [maven-changes-plugin] michael-o commented on issue #10: new http
michael-o commented on issue #10: new http URL: https://github.com/apache/maven-changes-plugin/pull/10#issuecomment-597238017 Can you apply? -Djavax.net.debug=all This is an automated message from the Apache Git Service. To respond to the message, please log on to 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
[GitHub] [maven-changes-plugin] elharo commented on issue #10: new http
elharo commented on issue #10: new http URL: https://github.com/apache/maven-changes-plugin/pull/10#issuecomment-597237040 Yep, this definitely causes the test to fail but only on JDK7: org.apache.maven.plugin.MojoExecutionException: Couldn't resolve the skin. at org.apache.maven.plugins.jira.JiraUnicodeTestCase.testUnicodeReport(JiraUnicodeTestCase.java:76) Caused by: org.apache.maven.shared.transfer.artifact.resolve.ArtifactResolverException: Failed to read artifact descriptor for org.apache.maven.skins:maven-default-skin:jar:1.0 at org.apache.maven.plugins.jira.JiraUnicodeTestCase.testUnicodeReport(JiraUnicodeTestCase.java:76) Caused by: org.sonatype.aether.resolution.ArtifactDescriptorException: Failed to read artifact descriptor for org.apache.maven.skins:maven-default-skin:jar:1.0 at org.apache.maven.plugins.jira.JiraUnicodeTestCase.testUnicodeReport(JiraUnicodeTestCase.java:76) Caused by: org.sonatype.aether.resolution.ArtifactResolutionException: Could not transfer artifact org.apache.maven.skins:maven-default-skin:pom:1.0 from/to central (https://repo.maven.apache.org/maven2): Received fatal alert: protocol_version at org.apache.maven.plugins.jira.JiraUnicodeTestCase.testUnicodeReport(JiraUnicodeTestCase.java:76) Caused by: org.sonatype.aether.transfer.ArtifactTransferException: Could not transfer artifact org.apache.maven.skins:maven-default-skin:pom:1.0 from/to central (https://repo.maven.apache.org/maven2): Received fatal alert: protocol_version Caused by: org.apache.maven.wagon.TransferFailedException: Received fatal alert: protocol_version Caused by: javax.net.ssl.SSLException: Received fatal alert: protocol_version This is an automated message from the Apache Git Service. To respond to the message, please log on to 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
[GitHub] [maven-changes-plugin] elharo closed pull request #9: revert http updates
elharo closed pull request #9: revert http updates URL: https://github.com/apache/maven-changes-plugin/pull/9 This is an automated message from the Apache Git Service. To respond to the message, please log on to 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
[GitHub] [maven-changes-plugin] elharo opened a new pull request #10: new http
elharo opened a new pull request #10: new http URL: https://github.com/apache/maven-changes-plugin/pull/10 Let's see what Jenkins makes of this. This is an automated message from the Apache Git Service. To respond to the message, please log on to 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] (MJAVADOC-642) Setting maven.javadoc.isoffline seems to have no effect
[
https://issues.apache.org/jira/browse/MJAVADOC-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17056099#comment-17056099
]
Michael Osipov commented on MJAVADOC-642:
-
There is your problem. The documentation is bad/incomplete and you did pass
{{-Dmaven.javadoc.isOffline}}. The property is {{-Dsettings.offline}}. Please
retry.
> Setting maven.javadoc.isoffline seems to have no effect
> ---
>
> Key: MJAVADOC-642
> URL: https://issues.apache.org/jira/browse/MJAVADOC-642
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: jar
>Affects Versions: 3.1.1
>Reporter: Thomas Cunningham
>Priority: Major
> Fix For: waiting-for-feedback
>
>
> I'm trying to work around MJAVADOC-641 and the proxy issues that we are
> having, and I'd like to set isOffline to true. I tried to do this my
> setting -Dmaven.javadoc.isOffline=true in my maven invocation, and it doesn't
> seem to take effect. Setting isOffline to true within the
> allows my build to succeed.
> Am I using the wrong command line property for isOffline?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MJAVADOC-642) Setting maven.javadoc.isoffline seems to have no effect
[ https://issues.apache.org/jira/browse/MJAVADOC-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17056025#comment-17056025 ] Thomas Cunningham commented on MJAVADOC-642: It's here, but I'm not sure how to set it [https://github.com/apache/maven-javadoc-plugin/blob/master/src/main/java/org/apache/maven/plugins/javadoc/AbstractJavadocMojo.java#L342-L343] > Setting maven.javadoc.isoffline seems to have no effect > --- > > Key: MJAVADOC-642 > URL: https://issues.apache.org/jira/browse/MJAVADOC-642 > Project: Maven Javadoc Plugin > Issue Type: Bug > Components: jar >Affects Versions: 3.1.1 >Reporter: Thomas Cunningham >Priority: Major > Fix For: waiting-for-feedback > > > I'm trying to work around MJAVADOC-641 and the proxy issues that we are > having, and I'd like to set isOffline to true. I tried to do this my > setting -Dmaven.javadoc.isOffline=true in my maven invocation, and it doesn't > seem to take effect. Setting isOffline to true within the > allows my build to succeed. > Am I using the wrong command line property for isOffline? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MNGSITE-395) Community Maven Mirrors and citizenship
Elliotte Rusty Harold created MNGSITE-395: - Summary: Community Maven Mirrors and citizenship Key: MNGSITE-395 URL: https://issues.apache.org/jira/browse/MNGSITE-395 Project: Maven Project Web Site Issue Type: New Feature Reporter: Elliotte Rusty Harold The community page https://maven.apache.org/community.html should discuss the appropriate use and abuse of public Maven Central mirrors as an alternative to Maven Central itself. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MNGSITE-394) Update community page with slack info
Elliotte Rusty Harold created MNGSITE-394: - Summary: Update community page with slack info Key: MNGSITE-394 URL: https://issues.apache.org/jira/browse/MNGSITE-394 Project: Maven Project Web Site Issue Type: Bug Reporter: Elliotte Rusty Harold and remove IRC? Anyone still using that? https://maven.apache.org/community.html -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Commented] (MJAVADOC-642) Setting maven.javadoc.isoffline seems to have no effect
[
https://issues.apache.org/jira/browse/MJAVADOC-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17055957#comment-17055957
]
Michael Osipov commented on MJAVADOC-642:
-
It is only mentioned in {{}}, but there is no reference. That seems odd.
> Setting maven.javadoc.isoffline seems to have no effect
> ---
>
> Key: MJAVADOC-642
> URL: https://issues.apache.org/jira/browse/MJAVADOC-642
> Project: Maven Javadoc Plugin
> Issue Type: Bug
> Components: jar
>Affects Versions: 3.1.1
>Reporter: Thomas Cunningham
>Priority: Major
> Fix For: waiting-for-feedback
>
>
> I'm trying to work around MJAVADOC-641 and the proxy issues that we are
> having, and I'd like to set isOffline to true. I tried to do this my
> setting -Dmaven.javadoc.isOffline=true in my maven invocation, and it doesn't
> seem to take effect. Setting isOffline to true within the
> allows my build to succeed.
> Am I using the wrong command line property for isOffline?
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MJAVADOC-642) Setting maven.javadoc.isoffline seems to have no effect
[ https://issues.apache.org/jira/browse/MJAVADOC-642?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17055908#comment-17055908 ] Thomas Cunningham commented on MJAVADOC-642: [~michael-o] I found it mentioned here : [https://maven.apache.org/plugins/maven-javadoc-plugin/javadoc-mojo.html] > Setting maven.javadoc.isoffline seems to have no effect > --- > > Key: MJAVADOC-642 > URL: https://issues.apache.org/jira/browse/MJAVADOC-642 > Project: Maven Javadoc Plugin > Issue Type: Bug > Components: jar >Affects Versions: 3.1.1 >Reporter: Thomas Cunningham >Priority: Major > Fix For: waiting-for-feedback > > > I'm trying to work around MJAVADOC-641 and the proxy issues that we are > having, and I'd like to set isOffline to true. I tried to do this my > setting -Dmaven.javadoc.isOffline=true in my maven invocation, and it doesn't > seem to take effect. Setting isOffline to true within the > allows my build to succeed. > Am I using the wrong command line property for isOffline? -- This message was sent by Atlassian Jira (v8.3.4#803005)
[GitHub] [maven-help-plugin] croister commented on a change in pull request #5: [MPH-164] - Effective-pom ignores artifact argument
croister commented on a change in pull request #5: [MPH-164] - Effective-pom
ignores artifact argument
URL: https://github.com/apache/maven-help-plugin/pull/5#discussion_r390197733
##
File path: src/main/java/org/apache/maven/plugins/help/EffectivePomMojo.java
##
@@ -111,6 +112,7 @@ public void execute()
if ( StringUtils.isNotEmpty( artifact ) )
{
project = getMavenProject( artifact );
+projects = Collections.emptyList();
Review comment:
If you run "mvn help:effective-pom
-Dartifact=org.apache.maven.plugins:maven-help-plugin" in a folder with a
simple pom (no modules defined in the pom) it will output the effective pom for
the maven-help-plugin as expected.
But if you run the same command in a folder with a more complex pom (where
there are one or more modules defined in the pom) it will output the effective
pom for these insted of the expected output.
This is caused by "artifact" only overriding the "project" variable and not
the "projects" variable.
Thinking about it again now I should probably set "projects" to be a list
only containing the "artifact". Will update the commit.
This is an automated message from the Apache Git Service.
To respond to the message, please log on to 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] (MNG-6876) ExecutionEvent/EventSpy
Nick Cross created MNG-6876: --- Summary: ExecutionEvent/EventSpy Key: MNG-6876 URL: https://issues.apache.org/jira/browse/MNG-6876 Project: Maven Issue Type: Task Components: Documentation: General Reporter: Nick Cross Provide more detailed documentation on the ExecutionEvent and https://maven.apache.org/examples/maven-3-lifecycle-extensions.html so its clear when certain 'phases' / 'hooks' are called e.g. * if a dependency is scope import when is it resolved ? * Difference between session start in AbstractMavenLifecycleParticipant and AbstractExecutionListener ? * I have found https://dev-maziarz.blogspot.com/2015/03/maven-323-internals-how-it-works.html and https://github.com/khmarbaise/test-maven-eventspy but it would be nice to have internal documentation/examples which demonstrate this. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Comment Edited] (MJAVADOC-610) Support multirelease jar
[
https://issues.apache.org/jira/browse/MJAVADOC-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17055670#comment-17055670
]
Olivier Lamy edited comment on MJAVADOC-610 at 3/10/20, 7:58 AM:
-
[~rfscholte] thanks for that but finally I'm not sure what to do with that
because we simply have 2 java class with exactly the same name. Javadoc can
render only one page per class...
with the sample project the options file contains
{quote}--patch-module
com.foo='/Users/olamy/dev/sources/maven/plugins/maven-javadoc-plugin/target/it/MJAVADOC-610_mrjar/src/main/java9:/Users/olamy/dev/sources/maven/plugins/maven-javadoc-plugin/target/it/MJAVADOC-610_mrjar/src/main/java'
{quote}
which is fine but as class have same name but if you add another class in
src/main/java9 you will see it in the rendered javadoc.
Honestly not sure what to do... Seems to be a misconception somewhere... :)
was (Author: olamy):
[~rfscholte] thanks for that but finally I'm not sure what to do with that
because we simply have 2 java class with exactly the same name. Javadoc can
render only one page per class...
> Support multirelease jar
>
>
> Key: MJAVADOC-610
> URL: https://issues.apache.org/jira/browse/MJAVADOC-610
> Project: Maven Javadoc Plugin
> Issue Type: Improvement
>Affects Versions: 3.1.0
>Reporter: Robert Scholte
>Assignee: Robert Scholte
>Priority: Major
> Fix For: 3.2.0
>
>
> When having a multirelease jar, all sourcefolders need to be added. Now only
> the main sourcefolder is added.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
[jira] [Commented] (MJAVADOC-610) Support multirelease jar
[ https://issues.apache.org/jira/browse/MJAVADOC-610?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17055670#comment-17055670 ] Olivier Lamy commented on MJAVADOC-610: --- [~rfscholte] thanks for that but finally I'm not sure what to do with that because we simply have 2 java class with exactly the same name. Javadoc can render only one page per class... > Support multirelease jar > > > Key: MJAVADOC-610 > URL: https://issues.apache.org/jira/browse/MJAVADOC-610 > Project: Maven Javadoc Plugin > Issue Type: Improvement >Affects Versions: 3.1.0 >Reporter: Robert Scholte >Assignee: Robert Scholte >Priority: Major > Fix For: 3.2.0 > > > When having a multirelease jar, all sourcefolders need to be added. Now only > the main sourcefolder is added. -- This message was sent by Atlassian Jira (v8.3.4#803005)
[jira] [Created] (MSHARED-863) Possible NPEx in Maven30DependencyResolver.resolveDependencies
Piotr Zygielo created MSHARED-863:
-
Summary: Possible NPEx in
Maven30DependencyResolver.resolveDependencies
Key: MSHARED-863
URL: https://issues.apache.org/jira/browse/MSHARED-863
Project: Maven Shared Components
Issue Type: Bug
Components: maven-artifact-transfer
Affects Versions: maven-artifact-transfer-0.12.0
Reporter: Piotr Zygielo
Possible NPEx in
[Maven30DependencyResolver.resolveDependencies|https://github.com/apache/maven-artifact-transfer/blob/dc0d6bd30b855e147576c4e9cdfacf1382d69f07/src/main/java/org/apache/maven/shared/transfer/dependencies/resolve/internal/Maven30DependencyResolver.java#L156]
{code:java}
List aetherDependencies = new ArrayList(
mavenDependencies.size() );
if ( mavenDependencies != null )
{
aetherDependencies = new ArrayList(
mavenDependencies.size() );
...
{code}
Line 161
{code:java}
if ( mavenDependencies != null )
{code}
suggests that {{mavenDependencies}} can be {{null}}.
However in such case previous {{mavenDependencies.size()}} results in {{NPEx}}.
--
This message was sent by Atlassian Jira
(v8.3.4#803005)
