[jira] [Updated] (MNG-6346) ... was unexpected at this time when using -f option and path contains brackets

[ https://issues.apache.org/jira/browse/MNG-6346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MNG-6346: -- Fix Version/s: 3.6.1 > ... was unexpected at this time when using -f option and path

[jira] [Assigned] (MNG-6346) ... was unexpected at this time when using -f option and path contains brackets

[ https://issues.apache.org/jira/browse/MNG-6346?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MNG-6346: - Assignee: Sylwester Lachiewicz > ... was unexpected at this time when using -f

[jira] [Commented] (MNG-6346) ... was unexpected at this time when using -f option and path contains brackets

[ https://issues.apache.org/jira/browse/MNG-6346?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734695#comment-16734695 ] Sylwester Lachiewicz commented on MNG-6346: --- To debug the issue set environment variable 

[jira] [Closed] (MNG-6063) rg.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable

[ https://issues.apache.org/jira/browse/MNG-6063?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MNG-6063. - Resolution: Won't Fix > rg.apache.maven.InternalErrorException: Internal error: >

[jira] [Commented] (MNG-6063) rg.apache.maven.InternalErrorException: Internal error: java.lang.RuntimeException: "No solution found because the problem is unsatisfiable

[ https://issues.apache.org/jira/browse/MNG-6063?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734699#comment-16734699 ] Sylwester Lachiewicz commented on MNG-6063: --- This issue has been auto closed because it has been

[jira] [Updated] (MNG-6069) Migrate to non deprecated parts of Commons CLI

[ https://issues.apache.org/jira/browse/MNG-6069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MNG-6069: -- Fix Version/s: (was: 3.6.x-candidate) 3.6.1 > Migrate to non

[jira] [Assigned] (MNG-6069) Migrate to non deprecated parts of Commons CLI

[ https://issues.apache.org/jira/browse/MNG-6069?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MNG-6069: - Assignee: Sylwester Lachiewicz (was: Karl Heinz Marbaise) > Migrate to non

[jira] [Comment Edited] (MJAVADOC-555) Javadoc:aggregate, Javadoc:jar fail if one of the modules does not contain module-info.java

[ https://issues.apache.org/jira/browse/MJAVADOC-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734600#comment-16734600 ] Gili edited comment on MJAVADOC-555 at 1/5/19 2:02 AM: --- The JDK issue is saying

[jira] [Commented] (MJAVADOC-555) Javadoc:aggregate, Javadoc:jar fail if one of the modules does not contain module-info.java

[ https://issues.apache.org/jira/browse/MJAVADOC-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734669#comment-16734669 ] Gili commented on MJAVADOC-555: --- I just noticed that in the 3rd comment Jonathan Gibson writes "this

[jira] [Updated] (MNG-6506) Mojos are unable to load package annotations on Java >= 9

[ https://issues.apache.org/jira/browse/MNG-6506?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MNG-6506: --- Description: On Java 9 and above, calls to {{java.lang.Package.getAnnotation(Class)}} from within a

[jira] [Comment Edited] (MJAVADOC-561) Not possible to link to JDK classes since Java 11

[ https://issues.apache.org/jira/browse/MJAVADOC-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16733751#comment-16733751 ] Gili edited comment on MJAVADOC-561 at 1/5/19 2:27 AM: --- Okay, now we've got a

[jira] [Updated] (MNG-6262) getCanonicalFile() is not used consistently during project resolution

[ https://issues.apache.org/jira/browse/MNG-6262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MNG-6262: -- Description: This bug manifests with... * maven 3.5.0 *AND WITH* maven built from

[jira] [Updated] (MNG-6262) getCanonicalFile() is not used consistently during project resolution

[ https://issues.apache.org/jira/browse/MNG-6262?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MNG-6262: -- Fix Version/s: 3.x / Backlog > getCanonicalFile() is not used consistently during

[jira] [Commented] (MNG-6541) less restrictive "is referencing itself" check

[ https://issues.apache.org/jira/browse/MNG-6541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734711#comment-16734711 ] Sylwester Lachiewicz commented on MNG-6541: --- I was pretty sure that I saw that code somewhere..

[jira] [Reopened] (WAGON-541) Command Line Not Showing ReasonPhrase for Errors

[ https://issues.apache.org/jira/browse/WAGON-541?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Brian Fox reopened WAGON-541: - We've also experienced this as a regression. When the server chooses to provide additional context, it is

[jira] [Assigned] (MNG-6469) Upload to Nexus hangs

[ https://issues.apache.org/jira/browse/MNG-6469?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MNG-6469: - Assignee: Sylwester Lachiewicz > Upload to Nexus hangs > - >

[jira] [Comment Edited] (WAGON-541) Command Line Not Showing ReasonPhrase for Errors

[ https://issues.apache.org/jira/browse/WAGON-541?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734730#comment-16734730 ] Brian Fox edited comment on WAGON-541 at 1/5/19 1:59 AM: - We've also experienced

[jira] [Comment Edited] (MJAVADOC-561) Not possible to link to JDK classes since Java 11

[ https://issues.apache.org/jira/browse/MJAVADOC-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16733751#comment-16733751 ] Gili edited comment on MJAVADOC-561 at 1/5/19 2:45 AM: --- Okay, now we've got a

[jira] [Assigned] (MNG-6520) Update assembly descriptors to 2.0.0

[ https://issues.apache.org/jira/browse/MNG-6520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MNG-6520: - Assignee: Sylwester Lachiewicz > Update assembly descriptors to 2.0.0 >

[jira] [Updated] (MNG-6520) Update assembly descriptors to 2.0.0

[ https://issues.apache.org/jira/browse/MNG-6520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MNG-6520: -- Fix Version/s: 3.6.1 > Update assembly descriptors to 2.0.0 >

[jira] [Updated] (MNG-6520) Update assembly descriptors to 2.0.0

[ https://issues.apache.org/jira/browse/MNG-6520?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MNG-6520: -- Description: Update namespaces to the version compatible with 3.0+ maven-assembly-plugin

[jira] [Commented] (MNG-6543) Upgrade plexus classworld to support java 9+ ClassLoader.findClass(String moduleName, String name) in Mojos

[ https://issues.apache.org/jira/browse/MNG-6543?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734783#comment-16734783 ] Hervé Boutemy commented on MNG-6543: oh yes, MNG-6506 is exactly what I was looking for: thanks

[jira] [Updated] (MNG-6374) ModelBuilder hangs with malformed pom.xml

[ https://issues.apache.org/jira/browse/MNG-6374?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MNG-6374: -- Fix Version/s: 3.6.x-candidate > ModelBuilder hangs with malformed pom.xml >

[jira] [Comment Edited] (MJAVADOC-561) Not possible to link to JDK classes since Java 11

[ https://issues.apache.org/jira/browse/MJAVADOC-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16733751#comment-16733751 ] Gili edited comment on MJAVADOC-561 at 1/5/19 2:46 AM: --- Okay, now we've got a

[jira] [Commented] (MJAVADOC-555) Javadoc:aggregate, Javadoc:jar fail if one of the modules does not contain module-info.java

[ https://issues.apache.org/jira/browse/MJAVADOC-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734646#comment-16734646 ] Robert Scholte commented on MJAVADOC-555: - Something changed. I will try to get in touch with

[jira] [Updated] (MNG-5577) Convert the core to use JSR 330 and remove the use of Plexus

[ https://issues.apache.org/jira/browse/MNG-5577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MNG-5577: -- Fix Version/s: 3.6.x-candidate > Convert the core to use JSR 330 and remove the use of

[jira] [Commented] (MNG-5995) Maven itself cannot run without maven-compat

[ https://issues.apache.org/jira/browse/MNG-5995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734655#comment-16734655 ] Robert Scholte commented on MNG-5995: - Right, ideally maven-compat is not available on the classpath,

[jira] [Updated] (MNG-6355) HTTP connector does not honor nonProxyHosts when following redirects

[ https://issues.apache.org/jira/browse/MNG-6355?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MNG-6355: -- Fix Version/s: 3.x / Backlog > HTTP connector does not honor nonProxyHosts when

[jira] [Assigned] (MNG-5577) Convert the core to use JSR 330 and remove the use of Plexus

[ https://issues.apache.org/jira/browse/MNG-5577?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz reassigned MNG-5577: - Assignee: Sylwester Lachiewicz (was: Jason van Zyl) > Convert the core to use

[jira] [Updated] (MNG-5950) Only first active proxy considered

[ https://issues.apache.org/jira/browse/MNG-5950?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MNG-5950: -- Fix Version/s: 3.x / Backlog > Only first active proxy considered >

[jira] [Comment Edited] (MJAVADOC-561) Not possible to link to JDK classes since Java 11

[ https://issues.apache.org/jira/browse/MJAVADOC-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16733982#comment-16733982 ] Michael Osipov edited comment on MJAVADOC-561 at 1/4/19 10:32 AM: -- bq.

[GitHub] jc7447 commented on issue #1: Manage default value in filters

jc7447 commented on issue #1: Manage default value in filters URL: https://github.com/apache/maven-filtering/pull/1#issuecomment-451419198 Related issue is here : https://issues.apache.org/jira/browse/MSHARED-793 This is an

[jira] [Commented] (MSHARED-793) Support for default value

[ https://issues.apache.org/jira/browse/MSHARED-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734065#comment-16734065 ] Michael Osipov commented on MSHARED-793: I think we was solely referring to the default value

[jira] [Commented] (MJAVADOC-561) Not possible to link to JDK classes since Java 11

[ https://issues.apache.org/jira/browse/MJAVADOC-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734032#comment-16734032 ] Gili commented on MJAVADOC-561: --- {quote}That is not true, Oracle JDK won't receive any free updates,

[jira] [Reopened] (SCM-889) Jazz tag command creates snapshot in wrong workspace

[ https://issues.apache.org/jira/browse/SCM-889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Chris Graham reopened SCM-889: -- Assignee: Chris Graham (was: Michael Osipov) Can I please have a bit more information about the usage

[jira] [Commented] (SCM-889) Jazz tag command creates snapshot in wrong workspace

[ https://issues.apache.org/jira/browse/SCM-889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734087#comment-16734087 ] Michael Osipov commented on SCM-889: [~ChrisGWarp], please do not reopen issues. I has been fixed. If

[jira] [Commented] (MJAVADOC-561) Not possible to link to JDK classes since Java 11

[ https://issues.apache.org/jira/browse/MJAVADOC-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734048#comment-16734048 ] Michael Osipov commented on MJAVADOC-561: - Found this issue too. Oracle is introducing a lot of

[jira] [Commented] (MSHARED-793) Support for default value

[ https://issues.apache.org/jira/browse/MSHARED-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734057#comment-16734057 ] Michael Osipov commented on MSHARED-793: The default token must be {{:-}} like people are used

[jira] [Commented] (MSHARED-793) Support for default value

[ https://issues.apache.org/jira/browse/MSHARED-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734070#comment-16734070 ] Robert Scholte commented on MSHARED-793: Still, up until now I haven't hit any issue with this,

[jira] [Commented] (MSHARED-793) Support for default value

[ https://issues.apache.org/jira/browse/MSHARED-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734062#comment-16734062 ] Robert Scholte commented on MSHARED-793: I really wonder if this makes sense. How can a Spring

[jira] [Created] (MSHARED-793) Support for default value

Jean-Charles Manoury created MSHARED-793: Summary: Support for default value Key: MSHARED-793 URL: https://issues.apache.org/jira/browse/MSHARED-793 Project: Maven Shared Components

[jira] [Comment Edited] (SCM-889) Jazz tag command creates snapshot in wrong workspace

[ https://issues.apache.org/jira/browse/SCM-889?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734087#comment-16734087 ] Michael Osipov edited comment on SCM-889 at 1/4/19 12:17 PM: - [~ChrisGWarp],

[jira] [Commented] (MASSEMBLY-888) jar-with-dependencies performance can be greatly improved by using the cache

[ https://issues.apache.org/jira/browse/MASSEMBLY-888?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16733987#comment-16733987 ] Robin Karlsson commented on MASSEMBLY-888: -- I've just verified that the issues are fixed with

[jira] [Commented] (MJAVADOC-561) Not possible to link to JDK classes since Java 11

[ https://issues.apache.org/jira/browse/MJAVADOC-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16733982#comment-16733982 ] Michael Osipov commented on MJAVADOC-561: - bq. OpenJDK 11 will not receive any "stability

[jira] [Commented] (MPLUGIN-341) Make the plugin tool modular or at least module-ready

[ https://issues.apache.org/jira/browse/MPLUGIN-341?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16733995#comment-16733995 ] Robert Scholte commented on MPLUGIN-341: I'm pretty sure that the answer is "Automatic Modules".

[GitHub] dedabob commented on issue #4: [MJAVADOC-527] - detectLinks may pass invalid urls to javadoc

dedabob commented on issue #4: [MJAVADOC-527] - detectLinks may pass invalid urls to javadoc URL: https://github.com/apache/maven-javadoc-plugin/pull/4#issuecomment-451456219 Commit 37948091426b28df45f42b04fbf25ba96cce3ab9 was the rebased code, then commit

[GitHub] dedabob commented on issue #4: [MJAVADOC-527] - detectLinks may pass invalid urls to javadoc

dedabob commented on issue #4: [MJAVADOC-527] - detectLinks may pass invalid urls to javadoc URL: https://github.com/apache/maven-javadoc-plugin/pull/4#issuecomment-451457576 Commit 8f6c55b01a691f07989d83b05afb4edb9379e1aa is the new rebase.

[jira] [Commented] (MJAVADOC-561) Not possible to link to JDK classes since Java 11

[ https://issues.apache.org/jira/browse/MJAVADOC-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734180#comment-16734180 ] Michael Osipov commented on MJAVADOC-561: - Rory O'Donnell of Oracle has also confirmed this on

[jira] [Commented] (MJAVADOC-555) Javadoc:aggregate, Javadoc:jar fail if one of the modules does not contain module-info.java

[ https://issues.apache.org/jira/browse/MJAVADOC-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734204#comment-16734204 ] Gili commented on MJAVADOC-555: --- {{javadoc:jar}} is similarly impacted. Reading

[jira] [Comment Edited] (MSHARED-793) Support for default value

[ https://issues.apache.org/jira/browse/MSHARED-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734247#comment-16734247 ] Michael Osipov edited comment on MSHARED-793 at 1/4/19 3:44 PM: Right,

[jira] [Commented] (MJAVADOC-561) Not possible to link to JDK classes since Java 11

[ https://issues.apache.org/jira/browse/MJAVADOC-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734194#comment-16734194 ] Michael Osipov commented on MJAVADOC-561: - [~cowwoc], can we close this issue as "Not A

[jira] [Commented] (MSHARED-793) Support for default value

[ https://issues.apache.org/jira/browse/MSHARED-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734226#comment-16734226 ] Jean-Charles Manoury commented on MSHARED-793: -- Sorry I shouldn't have mentioned Spring

[jira] [Commented] (MJAVADOC-561) Not possible to link to JDK classes since Java 11

[ https://issues.apache.org/jira/browse/MJAVADOC-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734175#comment-16734175 ] Gili commented on MJAVADOC-561: --- I think we dodged a bullet. Here is my public bug report, as promised:

[GitHub] michael-o commented on issue #4: [MJAVADOC-527] - detectLinks may pass invalid urls to javadoc

michael-o commented on issue #4: [MJAVADOC-527] - detectLinks may pass invalid urls to javadoc URL: https://github.com/apache/maven-javadoc-plugin/pull/4#issuecomment-451459020 Thank you, I will take a look at it. This is

[jira] [Updated] (MJAVADOC-555) Javadoc:aggregate, Javadoc:jar fail if one of the modules does not contain module-info.java

[ https://issues.apache.org/jira/browse/MJAVADOC-555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gili updated MJAVADOC-555: -- Summary: Javadoc:aggregate, Javadoc:jar fail if one of the modules does not contain module-info.java (was:

[jira] [Updated] (MJAVADOC-555) Javadoc:aggregate, Javadoc:jar fails if one of the modules does not contain module-info.java

[ https://issues.apache.org/jira/browse/MJAVADOC-555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gili updated MJAVADOC-555: -- Summary: Javadoc:aggregate, Javadoc:jar fails if one of the modules does not contain module-info.java (was:

[jira] [Commented] (MJAVADOC-561) Not possible to link to JDK classes since Java 11

[ https://issues.apache.org/jira/browse/MJAVADOC-561?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734202#comment-16734202 ] Gili commented on MJAVADOC-561: --- [~michael-o] Yes, I'll move the JDK 12 stuff to MJAVADOC-555. > Not

[GitHub] michael-o commented on issue #4: [MJAVADOC-527] - detectLinks may pass invalid urls to javadoc

michael-o commented on issue #4: [MJAVADOC-527] - detectLinks may pass invalid urls to javadoc URL: https://github.com/apache/maven-javadoc-plugin/pull/4#issuecomment-451463405 I have pushed branch MJAVADOC-527, take a look at the history. This what I have expected. I will now go on with

[jira] [Closed] (MJAVADOC-561) Not possible to link to JDK classes since Java 11

[ https://issues.apache.org/jira/browse/MJAVADOC-561?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MJAVADOC-561. --- Resolution: Not A Problem Assignee: Michael Osipov Fix Version/s: (was:

[jira] [Commented] (MSHARED-793) Support for default value

[ https://issues.apache.org/jira/browse/MSHARED-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734231#comment-16734231 ] Michael Osipov commented on MSHARED-793: I have the exact same case at work. I solved it that

[jira] [Updated] (MJAVADOC-555) Javadoc:aggregate, Javadoc:jar fails if one of the modules does not contain module-info.java

[ https://issues.apache.org/jira/browse/MJAVADOC-555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gili updated MJAVADOC-555: -- Component/s: jar > Javadoc:aggregate, Javadoc:jar fails if one of the modules does not contain >

[jira] [Commented] (MSHARED-793) Support for default value

[ https://issues.apache.org/jira/browse/MSHARED-793?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734247#comment-16734247 ] Robert Scholte commented on MSHARED-793: Right, so none of these files is being used by Maven,

[jira] [Created] (MJAVADOC-563) Javadoc generation fails if module name contains restricted keyword in non-terminal position

Gili created MJAVADOC-563: - Summary: Javadoc generation fails if module name contains restricted keyword in non-terminal position Key: MJAVADOC-563 URL: https://issues.apache.org/jira/browse/MJAVADOC-563

[jira] [Commented] (MJAVADOC-527) detectLinks may pass invalid URLs to javadoc(1)

[ https://issues.apache.org/jira/browse/MJAVADOC-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734359#comment-16734359 ] Hudson commented on MJAVADOC-527: - Build failed in Jenkins: Maven TLP » maven-javadoc-plugin »

[GitHub] michael-o commented on issue #9: [MJAVADOC-513] make order of classpath predictable

michael-o commented on issue #9: [MJAVADOC-513] make order of classpath predictable URL: https://github.com/apache/maven-javadoc-plugin/pull/9#issuecomment-451509703 I agree with @rfscholte . This is an automated message

[jira] [Commented] (MDEP-613) Analyze failed: Unsupported class file major version 55 (Java 11)

[ https://issues.apache.org/jira/browse/MDEP-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734384#comment-16734384 ] Hudson commented on MDEP-613: - Build succeeded in Jenkins: Maven TLP » maven-dependency-plugin » master #54

[GitHub] khmarbaise commented on issue #8: [MDEP-613] - Fixes bug Analyze failed: Unsupported class file major version 55 (Java 11)

khmarbaise commented on issue #8: [MDEP-613] - Fixes bug Analyze failed: Unsupported class file major version 55 (Java 11) URL: https://github.com/apache/maven-dependency-plugin/pull/8#issuecomment-451516848 Ok. Build your PR successfully. Thanks for your contribution.

[GitHub] khmarbaise closed pull request #8: [MDEP-613] - Fixes bug Analyze failed: Unsupported class file major version 55 (Java 11)

khmarbaise closed pull request #8: [MDEP-613] - Fixes bug Analyze failed: Unsupported class file major version 55 (Java 11) URL: https://github.com/apache/maven-dependency-plugin/pull/8 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is

[jira] [Updated] (MDEP-625) Upgrade maven-artifact-transfer to 0.10.1

[ https://issues.apache.org/jira/browse/MDEP-625?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MDEP-625: - Summary: Upgrade maven-artifact-transfer to 0.10.1 (was: Upgrade maven-artifact-transfer

[GitHub] kwin closed pull request #9: [MJAVADOC-513] make order of classpath predictable

kwin closed pull request #9: [MJAVADOC-513] make order of classpath predictable URL: https://github.com/apache/maven-javadoc-plugin/pull/9 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of provenance: As this

[GitHub] kwin commented on issue #9: [MJAVADOC-513] make order of classpath predictable

kwin commented on issue #9: [MJAVADOC-513] make order of classpath predictable URL: https://github.com/apache/maven-javadoc-plugin/pull/9#issuecomment-451520042 @michael-o This has been partially merged already. This is an

[jira] [Updated] (MJAVADOC-555) Javadoc:aggregate, Javadoc:jar fail if one of the modules does not contain module-info.java

[ https://issues.apache.org/jira/browse/MJAVADOC-555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gili updated MJAVADOC-555: -- Attachment: javadoc-cannot-link-to-automatic-modules.zip > Javadoc:aggregate, Javadoc:jar fail if one of the

[jira] [Commented] (MJAVADOC-555) Javadoc:aggregate, Javadoc:jar fail if one of the modules does not contain module-info.java

[ https://issues.apache.org/jira/browse/MJAVADOC-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734426#comment-16734426 ] Robert Scholte commented on MJAVADOC-555: - It is already fixed, see

[jira] [Commented] (MJAVADOC-555) Javadoc:aggregate, Javadoc:jar fail if one of the modules does not contain module-info.java

[ https://issues.apache.org/jira/browse/MJAVADOC-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734445#comment-16734445 ] Gili commented on MJAVADOC-555: --- [~rfscholte] I just noticed our comments crossed paths. I checked out

[jira] [Closed] (MDEP-613) Analyze failed: Unsupported class file major version 55 (Java 11)

[ https://issues.apache.org/jira/browse/MDEP-613?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MDEP-613. Resolution: Done > Analyze failed: Unsupported class file major version 55 (Java 11) >

[jira] [Commented] (MDEP-613) Analyze failed: Unsupported class file major version 55 (Java 11)

[ https://issues.apache.org/jira/browse/MDEP-613?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734352#comment-16734352 ] Karl Heinz Marbaise commented on MDEP-613: -- Done in

[jira] [Commented] (MJAVADOC-527) detectLinks may pass invalid URLs to javadoc(1)

[ https://issues.apache.org/jira/browse/MJAVADOC-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734358#comment-16734358 ] Hudson commented on MJAVADOC-527: - Build failed in Jenkins: Maven TLP » maven-javadoc-plugin »

[jira] [Commented] (MJAVADOC-563) Javadoc generation fails if module name contains restricted keyword in non-terminal position

[ https://issues.apache.org/jira/browse/MJAVADOC-563?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734434#comment-16734434 ] Gili commented on MJAVADOC-563: --- Quoting

[jira] [Commented] (MJAVADOC-555) Javadoc:aggregate, Javadoc:jar fail if one of the modules does not contain module-info.java

[ https://issues.apache.org/jira/browse/MJAVADOC-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734469#comment-16734469 ] Robert Scholte commented on MJAVADOC-555: - To see my result, clone the project and run {{mvn

[jira] [Comment Edited] (MJAVADOC-555) Javadoc:aggregate, Javadoc:jar fail if one of the modules does not contain module-info.java

[ https://issues.apache.org/jira/browse/MJAVADOC-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734428#comment-16734428 ] Gili edited comment on MJAVADOC-555 at 1/4/19 6:11 PM: --- You mentioned that you

[jira] [Commented] (MJAVADOC-555) Javadoc:aggregate, Javadoc:jar fail if one of the modules does not contain module-info.java

[ https://issues.apache.org/jira/browse/MJAVADOC-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734428#comment-16734428 ] Gili commented on MJAVADOC-555: --- You mentioned that you managed to work around this problem using

[GitHub] asfgit closed pull request #4: [MJAVADOC-527] - detectLinks may pass invalid urls to javadoc

asfgit closed pull request #4: [MJAVADOC-527] - detectLinks may pass invalid urls to javadoc URL: https://github.com/apache/maven-javadoc-plugin/pull/4 This is a PR merged from a forked repository. As GitHub hides the original diff on merge, it is displayed below for the sake of

[jira] [Closed] (MJAVADOC-527) detectLinks may pass invalid URLs to javadoc(1)

[ https://issues.apache.org/jira/browse/MJAVADOC-527?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov closed MJAVADOC-527. --- Resolution: Fixed Fixed with

[GitHub] khmarbaise commented on issue #4: (doc) - Add note on dependecy:tree -Dverbose support in 3.0+

khmarbaise commented on issue #4: (doc) - Add note on dependecy:tree -Dverbose support in 3.0+ URL: https://github.com/apache/maven-dependency-plugin/pull/4#issuecomment-451517732 Hi, could you please so kind to rebase your PR against most recent master. I appreciate to merge you PR

[GitHub] grimsa commented on issue #4: (doc) - Add note on dependecy:tree -Dverbose support in 3.0+

grimsa commented on issue #4: (doc) - Add note on dependecy:tree -Dverbose support in 3.0+ URL: https://github.com/apache/maven-dependency-plugin/pull/4#issuecomment-451534166 Rebased on master. Also updated the suggestion to use an older version of the plugin instead of debug flag

[jira] [Commented] (MJAVADOC-527) detectLinks may pass invalid URLs to javadoc(1)

[ https://issues.apache.org/jira/browse/MJAVADOC-527?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734474#comment-16734474 ] Hudson commented on MJAVADOC-527: - Build failed in Jenkins: Maven TLP » maven-javadoc-plugin » master

[jira] [Commented] (MJAVADOC-555) Javadoc:aggregate, Javadoc:jar fail if one of the modules does not contain module-info.java

[ https://issues.apache.org/jira/browse/MJAVADOC-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734537#comment-16734537 ] Gili commented on MJAVADOC-555: --- [~rfscholte] I see what you are doing: * Using --patch-module to

[GitHub] plamentotev commented on issue #2: [MJAR-238] Allow setting of module main class

plamentotev commented on issue #2: [MJAR-238] Allow setting of module main class URL: https://github.com/apache/maven-jar-plugin/pull/2#issuecomment-451536961 @eolivelli Looks like the build failed because of some problem with the windows machine (could not delete the workspace)

[jira] [Commented] (MJAVADOC-555) Javadoc:aggregate, Javadoc:jar fail if one of the modules does not contain module-info.java

[ https://issues.apache.org/jira/browse/MJAVADOC-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734547#comment-16734547 ] Gili commented on MJAVADOC-555: --- That is really odd. Maybe something is different about our environments.

[jira] [Commented] (MJAVADOC-555) Javadoc:aggregate, Javadoc:jar fail if one of the modules does not contain module-info.java

[ https://issues.apache.org/jira/browse/MJAVADOC-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734568#comment-16734568 ] Hudson commented on MJAVADOC-555: - Build failed in Jenkins: Maven TLP » maven-javadoc-plugin »

[GitHub] eolivelli commented on issue #2: [MJAR-238] Allow setting of module main class

eolivelli commented on issue #2: [MJAR-238] Allow setting of module main class URL: https://github.com/apache/maven-jar-plugin/pull/2#issuecomment-451546885 We are experiencing problems with Windows machines. We have to wait a bit, I am sorry. I will launch the build again as soon as

[jira] [Commented] (MJAVADOC-555) Javadoc:aggregate, Javadoc:jar fail if one of the modules does not contain module-info.java

[ https://issues.apache.org/jira/browse/MJAVADOC-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734541#comment-16734541 ] Robert Scholte commented on MJAVADOC-555: - Just added the other testcase to the branch, works

[jira] [Updated] (MJAVADOC-555) Javadoc:aggregate, Javadoc:jar fail if one of the modules does not contain module-info.java

[ https://issues.apache.org/jira/browse/MJAVADOC-555?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Gili updated MJAVADOC-555: -- Attachment: toolchains.xml > Javadoc:aggregate, Javadoc:jar fail if one of the modules does not contain >

[jira] [Commented] (MNG-5995) Maven itself cannot run without maven-compat

[ https://issues.apache.org/jira/browse/MNG-5995?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734563#comment-16734563 ] Sylwester Lachiewicz commented on MNG-5995: --- No, with my change You can just remove

[jira] [Commented] (MJAVADOC-555) Javadoc:aggregate, Javadoc:jar fail if one of the modules does not contain module-info.java

[ https://issues.apache.org/jira/browse/MJAVADOC-555?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734571#comment-16734571 ] Robert Scholte commented on MJAVADOC-555: - I'm not using toolchain, I'm running it directly on

[jira] [Updated] (MNG-6083) Maven 3.3.9 breaks release:perform by not including maven.config

[ https://issues.apache.org/jira/browse/MNG-6083?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MNG-6083: -- Priority: Major (was: Blocker) > Maven 3.3.9 breaks release:perform by not including

[jira] [Updated] (MNG-6024) maven-antrun-plugin:instrument failing NoClassDefFoundError: org/slf4j/LoggerFactory

[ https://issues.apache.org/jira/browse/MNG-6024?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MNG-6024: -- Priority: Major (was: Blocker) > maven-antrun-plugin:instrument failing

[jira] [Updated] (MNG-6275) ServiceLoaderFactory can't find implementations via ClassRealm

[ https://issues.apache.org/jira/browse/MNG-6275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz updated MNG-6275: -- Fix Version/s: (was: 3.5.2) 3.x / Backlog > ServiceLoaderFactory

[jira] [Closed] (MNG-5817) Maven 3.3, gradle-maven-plugin fails missing class org/slf4j/impl/NewMojoLogger

[ https://issues.apache.org/jira/browse/MNG-5817?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Sylwester Lachiewicz closed MNG-5817. - Resolution: Won't Fix > Maven 3.3, gradle-maven-plugin fails missing class >

[jira] [Commented] (MJAVADOC-562) Ability to pass --release to Javadoc tool

[ https://issues.apache.org/jira/browse/MJAVADOC-562?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16734608#comment-16734608 ] Michael Osipov commented on MJAVADOC-562: - I agree. > Ability to pass --release to Javadoc

  1   2   >