[GitHub] based2 commented on issue #188: mime js from text/javascript to application/javascript
based2 commented on issue #188: mime js from text/javascript to application/javascript URL: https://github.com/apache/maven-surefire/pull/188#issuecomment-401584376 https://issues.apache.org/jira/browse/SUREFIRE-1532 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Created] (SUREFIRE-1532) MIME type for javascript is now officially application/javascript
Basile Chandesris created SUREFIRE-1532: --- Summary: MIME type for javascript is now officially application/javascript Key: SUREFIRE-1532 URL: https://issues.apache.org/jira/browse/SUREFIRE-1532 Project: Maven Surefire Issue Type: Bug Components: Maven Surefire Report Plugin Affects Versions: 2.22.0 Reporter: Basile Chandesris ref [http://www.rfc-editor.org/rfc/rfc4329.txt |http://www.rfc-editor.org/rfc/rfc4329.txt]Scripting Media Types src [https://stackoverflow.com/questions/189850/what-is-the-javascript-mime-type-for-the-type-attribute-of-a-script-tag] "This is a common mistake. The MIME type for javascript wasn't standardized for years. It's now officially: "application/javascript"." github https://github.com/apache/maven-surefire/pull/188#issuecomment-401559853 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MRESOLVER-7) Download dependency POMs in parallel
[ https://issues.apache.org/jira/browse/MRESOLVER-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528933#comment-16528933 ] ASF GitHub Bot commented on MRESOLVER-7: slachiewicz commented on issue #10: [MRESOLVER-7] Download dependency POMs in parallel v2 URL: https://github.com/apache/maven-resolver/pull/10#issuecomment-401574365 I did rebase code and I compile few projects with clean repo - it looks good and fast. @steve-todorov could you try to test with Your projects also? 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 > Download dependency POMs in parallel > > > Key: MRESOLVER-7 > URL: https://issues.apache.org/jira/browse/MRESOLVER-7 > Project: Maven Resolver > Issue Type: Improvement >Affects Versions: Aether 1.0.2 >Reporter: Harald Wellmann >Priority: Major > > h3. Background > When building a project with dependencies not yet available in the local > repository, I noticed that Maven 3.3.9/Aether 1.0.2 first downloads the > dependency POMs _sequentially_ and then proceeds downloading the dependency > JARs with up to 5 threads _in parallel_. > Due to this, when first building a project with a large number of > dependencies, downloading a large number of small POMs may take a lot longer > than downloading the much larger JARs, or even longer than building the > project itself, especially when a repository manager is used which increases > the download latency. > h3. Enhancement > Download POMs of (transitive) dependencies in parallel to significantly speed > up initial builds of large projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] slachiewicz commented on issue #10: [MRESOLVER-7] Download dependency POMs in parallel v2
slachiewicz commented on issue #10: [MRESOLVER-7] Download dependency POMs in parallel v2 URL: https://github.com/apache/maven-resolver/pull/10#issuecomment-401574365 I did rebase code and I compile few projects with clean repo - it looks good and fast. @steve-todorov could you try to test with Your projects also? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Assigned] (JXR-125) Upgrade to Maven 3.0 compatiblity
[ https://issues.apache.org/jira/browse/JXR-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte reassigned JXR-125: -- Assignee: Robert Scholte > Upgrade to Maven 3.0 compatiblity > - > > Key: JXR-125 > URL: https://issues.apache.org/jira/browse/JXR-125 > Project: Maven JXR > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Robert Scholte >Priority: Minor > Fix For: 3.0.0 > > > Upgrade minimum to Maven 3.0.5. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MRESOLVER-7) Download dependency POMs in parallel
[ https://issues.apache.org/jira/browse/MRESOLVER-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528898#comment-16528898 ] ASF GitHub Bot commented on MRESOLVER-7: michael-o edited a comment on issue #10: [MRESOLVER-7] Download dependency POMs in parallel v2 URL: https://github.com/apache/maven-resolver/pull/10#issuecomment-401566300 @steve-todorov Did you try the patch yourself? Unfortunately, there is a very little amount of people working on Resolver right now. I am personally too busy. There is so much new code that I have trouble to understand it, especially because I am not fully comfortable with the Resolver code. But I am still looking into it. @slachiewicz Can you rebase again? 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 > Download dependency POMs in parallel > > > Key: MRESOLVER-7 > URL: https://issues.apache.org/jira/browse/MRESOLVER-7 > Project: Maven Resolver > Issue Type: Improvement >Affects Versions: Aether 1.0.2 >Reporter: Harald Wellmann >Priority: Major > > h3. Background > When building a project with dependencies not yet available in the local > repository, I noticed that Maven 3.3.9/Aether 1.0.2 first downloads the > dependency POMs _sequentially_ and then proceeds downloading the dependency > JARs with up to 5 threads _in parallel_. > Due to this, when first building a project with a large number of > dependencies, downloading a large number of small POMs may take a lot longer > than downloading the much larger JARs, or even longer than building the > project itself, especially when a repository manager is used which increases > the download latency. > h3. Enhancement > Download POMs of (transitive) dependencies in parallel to significantly speed > up initial builds of large projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] michael-o edited a comment on issue #10: [MRESOLVER-7] Download dependency POMs in parallel v2
michael-o edited a comment on issue #10: [MRESOLVER-7] Download dependency POMs in parallel v2 URL: https://github.com/apache/maven-resolver/pull/10#issuecomment-401566300 @steve-todorov Did you try the patch yourself? Unfortunately, there is a very little amount of people working on Resolver right now. I am personally too busy. There is so much new code that I have trouble to understand it, especially because I am not fully comfortable with the Resolver code. But I am still looking into it. @slachiewicz Can you rebase again? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (MRESOLVER-7) Download dependency POMs in parallel
[ https://issues.apache.org/jira/browse/MRESOLVER-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528897#comment-16528897 ] ASF GitHub Bot commented on MRESOLVER-7: michael-o commented on issue #10: [MRESOLVER-7] Download dependency POMs in parallel v2 URL: https://github.com/apache/maven-resolver/pull/10#issuecomment-401566300 @steve-todorov Did you try the patch yourself? Unfortunately, there is a very little amount of people working on Resolver right now. I am personally too busy. There is so much new code that I have trouble to understand it, especially because I am not fully comfortable with the Resolver code. @slachiewicz Can you rebase again? 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 > Download dependency POMs in parallel > > > Key: MRESOLVER-7 > URL: https://issues.apache.org/jira/browse/MRESOLVER-7 > Project: Maven Resolver > Issue Type: Improvement >Affects Versions: Aether 1.0.2 >Reporter: Harald Wellmann >Priority: Major > > h3. Background > When building a project with dependencies not yet available in the local > repository, I noticed that Maven 3.3.9/Aether 1.0.2 first downloads the > dependency POMs _sequentially_ and then proceeds downloading the dependency > JARs with up to 5 threads _in parallel_. > Due to this, when first building a project with a large number of > dependencies, downloading a large number of small POMs may take a lot longer > than downloading the much larger JARs, or even longer than building the > project itself, especially when a repository manager is used which increases > the download latency. > h3. Enhancement > Download POMs of (transitive) dependencies in parallel to significantly speed > up initial builds of large projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] michael-o commented on issue #10: [MRESOLVER-7] Download dependency POMs in parallel v2
michael-o commented on issue #10: [MRESOLVER-7] Download dependency POMs in parallel v2 URL: https://github.com/apache/maven-resolver/pull/10#issuecomment-401566300 @steve-todorov Did you try the patch yourself? Unfortunately, there is a very little amount of people working on Resolver right now. I am personally too busy. There is so much new code that I have trouble to understand it, especially because I am not fully comfortable with the Resolver code. @slachiewicz Can you rebase again? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Closed] (MINSTALL-145) Remove unused dependencies in pom
[ https://issues.apache.org/jira/browse/MINSTALL-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MINSTALL-145. Resolution: Done Done in [8d915f3072c5179ba69c6386691cf378bb6a0bb4|https://gitbox.apache.org/repos/asf?p=maven-install-plugin.git;a=commitdiff;h=8d915f3072c5179ba69c6386691cf378bb6a0bb4] > Remove unused dependencies in pom > - > > Key: MINSTALL-145 > URL: https://issues.apache.org/jira/browse/MINSTALL-145 > Project: Maven Install Plugin > Issue Type: Task >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Trivial > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MINSTALL-145) Remove unused dependencies in pom
[ https://issues.apache.org/jira/browse/MINSTALL-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528892#comment-16528892 ] Hudson commented on MINSTALL-145: - Build succeeded in Jenkins: Maven TLP » maven-install-plugin » master #11 See https://builds.apache.org/job/maven-box/job/maven-install-plugin/job/master/11/ > Remove unused dependencies in pom > - > > Key: MINSTALL-145 > URL: https://issues.apache.org/jira/browse/MINSTALL-145 > Project: Maven Install Plugin > Issue Type: Task >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Trivial > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MSHARED-698) Change the package to org.apache.maven.shared.transfer.*
[
https://issues.apache.org/jira/browse/MSHARED-698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MSHARED-698.
---
Resolution: Done
Done in
[3a01c3d5dec38f6a24051fc80f5c639190d32f9f|https://gitbox.apache.org/repos/asf?p=maven-artifact-transfer.git;a=commitdiff;h=3a01c3d5dec38f6a24051fc80f5c639190d32f9f]
> Change the package to org.apache.maven.shared.transfer.*
>
>
> Key: MSHARED-698
> URL: https://issues.apache.org/jira/browse/MSHARED-698
> Project: Maven Shared Components
> Issue Type: Task
> Components: maven-artifact-transfer
>Affects Versions: maven-artifact-transfer-0.10.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Critical
> Fix For: maven-artifact-transfer-0.10.0
>
>
> We should change the package from {{org.apache.maven.shared}} to
> {{org.apache.maven.shared.transfer.*}} to be in line with other shared
> components.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MSHARED-698) Change the package to org.apache.maven.shared.transfer.*
[
https://issues.apache.org/jira/browse/MSHARED-698?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528886#comment-16528886
]
Hudson commented on MSHARED-698:
Build succeeded in Jenkins: Maven TLP » maven-artifact-transfer » master #23
See
https://builds.apache.org/job/maven-box/job/maven-artifact-transfer/job/master/23/
> Change the package to org.apache.maven.shared.transfer.*
>
>
> Key: MSHARED-698
> URL: https://issues.apache.org/jira/browse/MSHARED-698
> Project: Maven Shared Components
> Issue Type: Task
> Components: maven-artifact-transfer
>Affects Versions: maven-artifact-transfer-0.10.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Critical
> Fix For: maven-artifact-transfer-0.10.0
>
>
> We should change the package from {{org.apache.maven.shared}} to
> {{org.apache.maven.shared.transfer.*}} to be in line with other shared
> components.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (SUREFIRE-1531) Option to switch-off Java 9 modules
[
https://issues.apache.org/jira/browse/SUREFIRE-1531?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Lukáš Křečan updated SUREFIRE-1531:
---
Description:
I am working on a library and I am adding support for Java 9 modules. Surefire
2.21.0 by default executes tests with Java 9 modules switched-on if it detects
module-info.java While it may make sense in some cases, in my case I'd like the
switch it off.
The reason is simple. I am using Mockito to mock an interface that extends a
Spring interface. Mockito has to create an implementation of this interface
(proxy or subclass) and for this it needs to have access to the Spring
interfaces. If Java 9 modules are enabled for the tests I have to manually add
such dependencies to Surefire configuration, which does not make much sense. To
makes things worse, the interface actually extends two Spring interfaces form
two different Spring modules so the configuration is almost impossible to get
right.
So far I am at and I am still getting IllegalAccessErrors
{code:java}
--add-exports spring.context/org.springframework.scheduling=org.mockito
--add-exports spring.beans/org.springframework.beans.factory=org.mockito
{code}
I would prefer to switch-off the Java 9 modules for the test module altogether
(same behavior as pre 2.21.0)
The test is here
[https://github.com/lukas-krecan/ShedLock/blob/java9/shedlock-spring/src/test/java/net/javacrumbs/shedlock/spring/CleanupTest.java]
If you want, I can send a pull request.
was:
I am working on a library and I am adding support for Java 9 modules. Surefire
2.21.0 by default executes tests with Java 9 modules switched-on if it detects
module-info.java While it may make sense in some cases, in my case I'd like the
switch it off.
The reason is simple. I am using Mockito to mock an interface that extends a
Spring interface. Mockito has to create an implementation of this interface
(proxy or subclass) and for this it need to have access to the Spring
interfaces. If Java 9 modules are enabled for the tests I have to manually add
such dependencies to Surefire configuration, which does not make much sense. To
makes things worse, the interface actually extends two Spring interfaces form
two different Spring modules so the configuration is almost impossible to get
right.
So far I am at and I am still getting IllegalAccessErrors
{code:java}
--add-exports spring.context/org.springframework.scheduling=org.mockito
--add-exports spring.beans/org.springframework.beans.factory=org.mockito
{code}
I would prefer to switch-off the Java 9 modules for the test module altogether
(same behavior as pre 2.21.0)
The test is here
[https://github.com/lukas-krecan/ShedLock/blob/java9/shedlock-spring/src/test/java/net/javacrumbs/shedlock/spring/CleanupTest.java]
If you want, I can send a pull request.
> Option to switch-off Java 9 modules
> ---
>
> Key: SUREFIRE-1531
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1531
> Project: Maven Surefire
> Issue Type: Improvement
> Components: Maven Surefire Plugin
>Affects Versions: 2.22.0
>Reporter: Lukáš Křečan
>Priority: Major
>
> I am working on a library and I am adding support for Java 9 modules.
> Surefire 2.21.0 by default executes tests with Java 9 modules switched-on if
> it detects module-info.java While it may make sense in some cases, in my case
> I'd like the switch it off.
> The reason is simple. I am using Mockito to mock an interface that extends a
> Spring interface. Mockito has to create an implementation of this interface
> (proxy or subclass) and for this it needs to have access to the Spring
> interfaces. If Java 9 modules are enabled for the tests I have to manually
> add such dependencies to Surefire configuration, which does not make much
> sense. To makes things worse, the interface actually extends two Spring
> interfaces form two different Spring modules so the configuration is almost
> impossible to get right.
> So far I am at and I am still getting IllegalAccessErrors
> {code:java}
> --add-exports spring.context/org.springframework.scheduling=org.mockito
> --add-exports spring.beans/org.springframework.beans.factory=org.mockito
> {code}
> I would prefer to switch-off the Java 9 modules for the test module
> altogether (same behavior as pre 2.21.0)
>
> The test is here
> [https://github.com/lukas-krecan/ShedLock/blob/java9/shedlock-spring/src/test/java/net/javacrumbs/shedlock/spring/CleanupTest.java]
>
> If you want, I can send a pull request.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (SUREFIRE-1531) Option to switch-off Java 9 modules
Lukáš Křečan created SUREFIRE-1531:
--
Summary: Option to switch-off Java 9 modules
Key: SUREFIRE-1531
URL: https://issues.apache.org/jira/browse/SUREFIRE-1531
Project: Maven Surefire
Issue Type: Improvement
Components: Maven Surefire Plugin
Affects Versions: 2.22.0
Reporter: Lukáš Křečan
I am working on a library and I am adding support for Java 9 modules. Surefire
2.21.0 by default executes tests with Java 9 modules switched-on if it detects
module-info.java While it may make sense in some cases, in my case I'd like the
switch it off.
The reason is simple. I am using Mockito to mock an interface that extends a
Spring interface. Mockito has to create an implementation of this interface
(proxy or subclass) and for this it need to have access to the Spring
interfaces. If Java 9 modules are enabled for the tests I have to manually add
such dependencies to Surefire configuration, which does not make much sense. To
makes things worse, the interface actually extends two Spring interfaces form
two different Spring modules so the configuration is almost impossible to get
right.
So far I am at and I am still getting IllegalAccessErrors
{code:java}
--add-exports spring.context/org.springframework.scheduling=org.mockito
--add-exports spring.beans/org.springframework.beans.factory=org.mockito
{code}
I would prefer to switch-off the Java 9 modules for the test module altogether
(same behavior as pre 2.21.0)
The test is here
[https://github.com/lukas-krecan/ShedLock/blob/java9/shedlock-spring/src/test/java/net/javacrumbs/shedlock/spring/CleanupTest.java]
If you want, I can send a pull request.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Assigned] (MSHARED-698) Change the package to org.apache.maven.shared.transfer.*
[
https://issues.apache.org/jira/browse/MSHARED-698?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise reassigned MSHARED-698:
---
Assignee: Karl Heinz Marbaise
> Change the package to org.apache.maven.shared.transfer.*
>
>
> Key: MSHARED-698
> URL: https://issues.apache.org/jira/browse/MSHARED-698
> Project: Maven Shared Components
> Issue Type: Task
> Components: maven-artifact-transfer
>Affects Versions: maven-artifact-transfer-0.10.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Critical
> Fix For: maven-artifact-transfer-0.10.0
>
>
> We should change the package from {{org.apache.maven.shared}} to
> {{org.apache.maven.shared.transfer.*}} to be in line with other shared
> components.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MINSTALL-145) Remove unused dependencies in pom
[ https://issues.apache.org/jira/browse/MINSTALL-145?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528875#comment-16528875 ] Hudson commented on MINSTALL-145: - Build succeeded in Jenkins: Maven TLP » maven-install-plugin » MINSTALL-145 #3 See https://builds.apache.org/job/maven-box/job/maven-install-plugin/job/MINSTALL-145/3/ > Remove unused dependencies in pom > - > > Key: MINSTALL-145 > URL: https://issues.apache.org/jira/browse/MINSTALL-145 > Project: Maven Install Plugin > Issue Type: Task >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Trivial > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MINSTALL-145) Remove unused dependencies in pom
[ https://issues.apache.org/jira/browse/MINSTALL-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MINSTALL-145: - Summary: Remove unused dependencies in pom (was: Removed unused dependencies in pom) > Remove unused dependencies in pom > - > > Key: MINSTALL-145 > URL: https://issues.apache.org/jira/browse/MINSTALL-145 > Project: Maven Install Plugin > Issue Type: Task >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Trivial > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MINSTALL-145) Removed unused dependencies in pom
Karl Heinz Marbaise created MINSTALL-145: Summary: Removed unused dependencies in pom Key: MINSTALL-145 URL: https://issues.apache.org/jira/browse/MINSTALL-145 Project: Maven Install Plugin Issue Type: Task Affects Versions: 3.0.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSHARED-741) Upgrade commons-codec to 1.11
[ https://issues.apache.org/jira/browse/MSHARED-741?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528867#comment-16528867 ] Hudson commented on MSHARED-741: Build succeeded in Jenkins: Maven TLP » maven-artifact-transfer » master #22 See https://builds.apache.org/job/maven-box/job/maven-artifact-transfer/job/master/22/ > Upgrade commons-codec to 1.11 > - > > Key: MSHARED-741 > URL: https://issues.apache.org/jira/browse/MSHARED-741 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-artifact-transfer >Affects Versions: maven-artifact-transfer-0.10.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: maven-artifact-transfer-0.10.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MSHARED-741) Upgrade commons-codec to 1.11
[ https://issues.apache.org/jira/browse/MSHARED-741?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MSHARED-741. --- Resolution: Done Done in [305fdad3f70543617ca19b297ab18b2ed7a9851b|https://gitbox.apache.org/repos/asf?p=maven-artifact-transfer.git;a=commitdiff;h=305fdad3f70543617ca19b297ab18b2ed7a9851b] > Upgrade commons-codec to 1.11 > - > > Key: MSHARED-741 > URL: https://issues.apache.org/jira/browse/MSHARED-741 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-artifact-transfer >Affects Versions: maven-artifact-transfer-0.10.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: maven-artifact-transfer-0.10.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MSHARED-741) Upgrade commons-codec to 1.11
Karl Heinz Marbaise created MSHARED-741: --- Summary: Upgrade commons-codec to 1.11 Key: MSHARED-741 URL: https://issues.apache.org/jira/browse/MSHARED-741 Project: Maven Shared Components Issue Type: Dependency upgrade Components: maven-artifact-transfer Affects Versions: maven-artifact-transfer-0.10.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: maven-artifact-transfer-0.10.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] Tibor17 commented on issue #188: mime js from text/javascript to application/javascript
Tibor17 commented on issue #188: mime js from text/javascript to application/javascript URL: https://github.com/apache/maven-surefire/pull/188#issuecomment-401559853 ok, pls create a new Jira issue, see the link in `issueManagement` in Surefire parent pom.xml. Then rewrite this issue title and commit to something like `[SUREFIRE-12345] Jira Title`. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Deleted] (MSHARED-740) Upgrade maven-shared-utils to 3.2.1
[ https://issues.apache.org/jira/browse/MSHARED-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise deleted MSHARED-740: > Upgrade maven-shared-utils to 3.2.1 > --- > > Key: MSHARED-740 > URL: https://issues.apache.org/jira/browse/MSHARED-740 > Project: Maven Shared Components > Issue Type: Dependency upgrade >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MSHARED-740) Upgrade maven-shared-utils to 3.2.1
[ https://issues.apache.org/jira/browse/MSHARED-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MSHARED-740: > Upgrade maven-shared-utils to 3.2.1 > --- > > Key: MSHARED-740 > URL: https://issues.apache.org/jira/browse/MSHARED-740 > Project: Maven Shared Components > Issue Type: Dependency upgrade >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MSHARED-740) Upgrade maven-shared-utils to 3.2.1
[ https://issues.apache.org/jira/browse/MSHARED-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MSHARED-740: Fix Version/s: (was: maven-artifact-transfer-0.10.0) > Upgrade maven-shared-utils to 3.2.1 > --- > > Key: MSHARED-740 > URL: https://issues.apache.org/jira/browse/MSHARED-740 > Project: Maven Shared Components > Issue Type: Dependency upgrade >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MSHARED-740) Upgrade maven-shared-utils to 3.2.1
[ https://issues.apache.org/jira/browse/MSHARED-740?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MSHARED-740: Component/s: (was: maven-artifact-transfer) > Upgrade maven-shared-utils to 3.2.1 > --- > > Key: MSHARED-740 > URL: https://issues.apache.org/jira/browse/MSHARED-740 > Project: Maven Shared Components > Issue Type: Dependency upgrade >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MSHARED-740) Upgrade maven-shared-utils to 3.2.1
Karl Heinz Marbaise created MSHARED-740: --- Summary: Upgrade maven-shared-utils to 3.2.1 Key: MSHARED-740 URL: https://issues.apache.org/jira/browse/MSHARED-740 Project: Maven Shared Components Issue Type: Dependency upgrade Components: maven-artifact-transfer Affects Versions: maven-artifact-transfer-0.10.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: maven-artifact-transfer-0.10.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSHARED-739) Upgrade mave-surefire/failsafe-plugin 2.21.0
[ https://issues.apache.org/jira/browse/MSHARED-739?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528850#comment-16528850 ] Hudson commented on MSHARED-739: Build succeeded in Jenkins: Maven TLP » maven-jarsigner » MSHARED-739 #2 See https://builds.apache.org/job/maven-box/job/maven-jarsigner/job/MSHARED-739/2/ > Upgrade mave-surefire/failsafe-plugin 2.21.0 > > > Key: MSHARED-739 > URL: https://issues.apache.org/jira/browse/MSHARED-739 > Project: Maven Shared Components > Issue Type: Dependency upgrade > Components: maven-jarsigner >Affects Versions: maven-jarsigner-3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Blocker > Fix For: maven-jarsigner-3.0.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MSHARED-739) Upgrade mave-surefire/failsafe-plugin 2.21.0
Karl Heinz Marbaise created MSHARED-739: --- Summary: Upgrade mave-surefire/failsafe-plugin 2.21.0 Key: MSHARED-739 URL: https://issues.apache.org/jira/browse/MSHARED-739 Project: Maven Shared Components Issue Type: Dependency upgrade Components: maven-jarsigner Affects Versions: maven-jarsigner-3.0.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: maven-jarsigner-3.0.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MRESOLVER-7) Download dependency POMs in parallel
[ https://issues.apache.org/jira/browse/MRESOLVER-7?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528845#comment-16528845 ] ASF GitHub Bot commented on MRESOLVER-7: steve-todorov commented on issue #10: [MRESOLVER-7] Download dependency POMs in parallel v2 URL: https://github.com/apache/maven-resolver/pull/10#issuecomment-401558666 Hi guys, are there any plans for this to be merged anytime soon? We have a bit project which might benefit from this. Is there anything more needed to be done? 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 > Download dependency POMs in parallel > > > Key: MRESOLVER-7 > URL: https://issues.apache.org/jira/browse/MRESOLVER-7 > Project: Maven Resolver > Issue Type: Improvement >Affects Versions: Aether 1.0.2 >Reporter: Harald Wellmann >Priority: Major > > h3. Background > When building a project with dependencies not yet available in the local > repository, I noticed that Maven 3.3.9/Aether 1.0.2 first downloads the > dependency POMs _sequentially_ and then proceeds downloading the dependency > JARs with up to 5 threads _in parallel_. > Due to this, when first building a project with a large number of > dependencies, downloading a large number of small POMs may take a lot longer > than downloading the much larger JARs, or even longer than building the > project itself, especially when a repository manager is used which increases > the download latency. > h3. Enhancement > Download POMs of (transitive) dependencies in parallel to significantly speed > up initial builds of large projects. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] steve-todorov commented on issue #10: [MRESOLVER-7] Download dependency POMs in parallel v2
steve-todorov commented on issue #10: [MRESOLVER-7] Download dependency POMs in parallel v2 URL: https://github.com/apache/maven-resolver/pull/10#issuecomment-401558666 Hi guys, are there any plans for this to be merged anytime soon? We have a bit project which might benefit from this. Is there anything more needed to be done? This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (MJLINK-6) Allow set the jmods path
[ https://issues.apache.org/jira/browse/MJLINK-6?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528809#comment-16528809 ] Roberto Araujo commented on MJLINK-6: - [~sellersj] this is exactly my use case > Allow set the jmods path > > > Key: MJLINK-6 > URL: https://issues.apache.org/jira/browse/MJLINK-6 > Project: Maven JLink Plugin > Issue Type: Improvement >Affects Versions: 3.0.0-alpha-2 >Reporter: Roberto Araujo >Priority: Minor > > The current version of the plugin hard-coded the `jmods` folder (based on > `jlink` binary location). But, for instance, if I want to build a runtime > image for Linux running the build in a OSX the runtime image will not be > compatible. > I suggest to allow users define the JDK `jmods` folder, and if nothing is > set, use the one based on the JAVA_HOME/Toolchain configuration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MSHARED-703) Try to identify why IT's not running with Maven 3.0.5
[ https://issues.apache.org/jira/browse/MSHARED-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MSHARED-703. --- Resolution: Done Done with [7b1771cadcc746afdd5f43475345f2452f061f99|https://gitbox.apache.org/repos/asf?p=maven-artifact-transfer.git;a=commitdiff;h=7b1771cadcc746afdd5f43475345f2452f061f99] > Try to identify why IT's not running with Maven 3.0.5 > - > > Key: MSHARED-703 > URL: https://issues.apache.org/jira/browse/MSHARED-703 > Project: Maven Shared Components > Issue Type: Task > Components: maven-artifact-transfer >Affects Versions: maven-artifact-transfer-0.10.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Critical > Fix For: maven-artifact-transfer-0.10.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MSHARED-705) Remove updateReleaseInfo from ProjectInstallerRequest
[
https://issues.apache.org/jira/browse/MSHARED-705?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MSHARED-705.
---
Resolution: Implemented
Assignee: Karl Heinz Marbaise
Done with
[7b1771cadcc746afdd5f43475345f2452f061f99|https://gitbox.apache.org/repos/asf?p=maven-artifact-transfer.git;a=commitdiff;h=7b1771cadcc746afdd5f43475345f2452f061f99]
> Remove updateReleaseInfo from ProjectInstallerRequest
> -
>
> Key: MSHARED-705
> URL: https://issues.apache.org/jira/browse/MSHARED-705
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-artifact-transfer
>Affects Versions: maven-artifact-transfer-0.10.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: maven-artifact-transfer-0.10.0
>
>
> Currently the class {{ProjectInstallerRequest}} contains an attribute
> {{updateReleaseInfo}} which should be removed.
> The question is what it's exactly causing?
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MSHARED-695) Move checksum creation from install part to deploy part
[ https://issues.apache.org/jira/browse/MSHARED-695?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MSHARED-695. --- Resolution: Done Done in [7b1771cadcc746afdd5f43475345f2452f061f99|https://gitbox.apache.org/repos/asf?p=maven-artifact-transfer.git;a=commitdiff;h=7b1771cadcc746afdd5f43475345f2452f061f99] > Move checksum creation from install part to deploy part > --- > > Key: MSHARED-695 > URL: https://issues.apache.org/jira/browse/MSHARED-695 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-artifact-transfer >Affects Versions: maven-artifact-transfer-0.10.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Blocker > Fix For: maven-artifact-transfer-0.10.0 > > > We should remove the checksum generation from install parts and move them > consistently to the deploy part instead -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] based2 opened a new pull request #188: mime js from text/javascript to application/javascript
based2 opened a new pull request #188: mime js from text/javascript to application/javascript URL: https://github.com/apache/maven-surefire/pull/188 https://stackoverflow.com/questions/189850/what-is-the-javascript-mime-type-for-the-type-attribute-of-a-script-tag "This is a common mistake. The MIME type for javascript wasn't standardized for years. It's now officially: "application/javascript"." http://www.rfc-editor.org/rfc/rfc4329.txt This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (MSHARED-695) Move checksum creation from install part to deploy part
[ https://issues.apache.org/jira/browse/MSHARED-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528752#comment-16528752 ] Hudson commented on MSHARED-695: Build succeeded in Jenkins: Maven TLP » maven-artifact-transfer » master #20 See https://builds.apache.org/job/maven-box/job/maven-artifact-transfer/job/master/20/ > Move checksum creation from install part to deploy part > --- > > Key: MSHARED-695 > URL: https://issues.apache.org/jira/browse/MSHARED-695 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-artifact-transfer >Affects Versions: maven-artifact-transfer-0.10.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Blocker > Fix For: maven-artifact-transfer-0.10.0 > > > We should remove the checksum generation from install parts and move them > consistently to the deploy part instead -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSHARED-695) Move checksum creation from install part to deploy part
[ https://issues.apache.org/jira/browse/MSHARED-695?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528746#comment-16528746 ] Hudson commented on MSHARED-695: Build succeeded in Jenkins: Maven TLP » maven-artifact-transfer » MSHARED-695 #17 See https://builds.apache.org/job/maven-box/job/maven-artifact-transfer/job/MSHARED-695/17/ > Move checksum creation from install part to deploy part > --- > > Key: MSHARED-695 > URL: https://issues.apache.org/jira/browse/MSHARED-695 > Project: Maven Shared Components > Issue Type: Improvement > Components: maven-artifact-transfer >Affects Versions: maven-artifact-transfer-0.10.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Blocker > Fix For: maven-artifact-transfer-0.10.0 > > > We should remove the checksum generation from install parts and move them > consistently to the deploy part instead -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6424) Upgrade plexus-interpolation to 1.25
[ https://issues.apache.org/jira/browse/MNG-6424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528730#comment-16528730 ] Hudson commented on MNG-6424: - Build failed in Jenkins: Maven TLP » maven » master #32 See https://builds.apache.org/job/maven-box/job/maven/job/master/32/ > Upgrade plexus-interpolation to 1.25 > > > Key: MNG-6424 > URL: https://issues.apache.org/jira/browse/MNG-6424 > Project: Maven > Issue Type: Dependency upgrade >Affects Versions: 3.5.4 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.6.x-candidate > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MJMOD-14) Upgrade plexus-java 0.9.10
[ https://issues.apache.org/jira/browse/MJMOD-14?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528712#comment-16528712 ] Hudson commented on MJMOD-14: - Build succeeded in Jenkins: Maven TLP » maven-jmod-plugin » master #9 See https://builds.apache.org/job/maven-box/job/maven-jmod-plugin/job/master/9/ > Upgrade plexus-java 0.9.10 > -- > > Key: MJMOD-14 > URL: https://issues.apache.org/jira/browse/MJMOD-14 > Project: Maven JMod Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.0-alpha-1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Blocker > Fix For: 3.0.0-alpha-2 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-6424) Upgrade plexus-interpolation to 1.25
[ https://issues.apache.org/jira/browse/MNG-6424?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528710#comment-16528710 ] ASF GitHub Bot commented on MNG-6424: - asfgit closed pull request #172: [MNG-6424] - Upgrade plexus-interpolation to 1.25 URL: https://github.com/apache/maven/pull/172 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 > Upgrade plexus-interpolation to 1.25 > > > Key: MNG-6424 > URL: https://issues.apache.org/jira/browse/MNG-6424 > Project: Maven > Issue Type: Dependency upgrade >Affects Versions: 3.5.4 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.6.x-candidate > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] asfgit closed pull request #172: [MNG-6424] - Upgrade plexus-interpolation to 1.25
asfgit closed pull request #172: [MNG-6424] - Upgrade plexus-interpolation to 1.25 URL: https://github.com/apache/maven/pull/172 This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Created] (MJMOD-14) Upgrade plexus-java 0.9.10
Karl Heinz Marbaise created MJMOD-14: Summary: Upgrade plexus-java 0.9.10 Key: MJMOD-14 URL: https://issues.apache.org/jira/browse/MJMOD-14 Project: Maven JMod Plugin Issue Type: Dependency upgrade Affects Versions: 3.0.0-alpha-1 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.0.0-alpha-2 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MCHECKSTYLE-356) print the checkstyle violations in descending order of line number
[ https://issues.apache.org/jira/browse/MCHECKSTYLE-356?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jagadish Prasath Ramu updated MCHECKSTYLE-356: -- Description: By default, the report form checkstyle prints the errors as it is found from beginning to end of file i.e., e.g: Line 5: Unused import Line 10: Missing space etc., Instead, it would be better if the report is printed in the reverse order e.g: Line 10: Missing space etc., Line 5: Unused import. As we fix the issues one by one, we end up changing the code and the line number changes. It results in missing the exact line number in which the remaining errors has occurred. So, we end up running the checkstyle multiple times. Instead, if there is an option to print the results in descending order (of a file's line number), it might help to avoid this inconvenience. was: By default, the report form checkstyle prints the errors as it is found from beginning to end of file i.e., e.g: Line 5: Unused import Line 10: Missing space etc., Instead, it would be better if the report is printed in the reverse order e.g: Line 10: Missing space etc., Line 5: Unused import. As we fix the issues one by one, we end up changing the code and the line number changes It results in missing the exact line number in which the remaining errors has occurred. So, we end up running the checkstyle multiple times. Instead, if there is an option to print the results in descending order (of a file's line number), it might help to avoid this inconvenience. > print the checkstyle violations in descending order of line number > -- > > Key: MCHECKSTYLE-356 > URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-356 > Project: Maven Checkstyle Plugin > Issue Type: Improvement > Components: checkstyle:checkstyle >Reporter: Jagadish Prasath Ramu >Priority: Major > > By default, the report form checkstyle prints the errors as it is found from > beginning to end of file i.e., > > e.g: > Line 5: Unused import > Line 10: Missing space etc., > > Instead, it would be better if the report is printed in the reverse order > e.g: > Line 10: Missing space etc., > Line 5: Unused import. > > As we fix the issues one by one, we end up changing the code and the line > number changes. It results in missing the exact line number in which the > remaining errors has occurred. So, we end up running the checkstyle multiple > times. Instead, if there is an option to print the results in descending > order (of a file's line number), it might help to avoid this inconvenience. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MCHECKSTYLE-356) print the checkstyle violations in descending order of line number
Jagadish Prasath Ramu created MCHECKSTYLE-356: - Summary: print the checkstyle violations in descending order of line number Key: MCHECKSTYLE-356 URL: https://issues.apache.org/jira/browse/MCHECKSTYLE-356 Project: Maven Checkstyle Plugin Issue Type: Improvement Components: checkstyle:checkstyle Reporter: Jagadish Prasath Ramu By default, the report form checkstyle prints the errors as it is found from beginning to end of file i.e., e.g: Line 5: Unused import Line 10: Missing space etc., Instead, it would be better if the report is printed in the reverse order e.g: Line 10: Missing space etc., Line 5: Unused import. As we fix the issues one by one, we end up changing the code and the line number changes It results in missing the exact line number in which the remaining errors has occurred. So, we end up running the checkstyle multiple times. Instead, if there is an option to print the results in descending order (of a file's line number), it might help to avoid this inconvenience. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (JXR-100) Method declaration: using spaces before or after parenthesis prevents cross references generation
[ https://issues.apache.org/jira/browse/JXR-100?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed JXR-100. -- Resolution: Fixed Fix Version/s: 3.0.0 Fixed in [7fde60ac0d88e0c99ab28c83aedfd6428dfd8977|https://gitbox.apache.org/repos/asf?p=maven-jxr.git;a=commit;h=7fde60ac0d88e0c99ab28c83aedfd6428dfd8977] > Method declaration: using spaces before or after parenthesis prevents cross > references generation > - > > Key: JXR-100 > URL: https://issues.apache.org/jira/browse/JXR-100 > Project: Maven JXR > Issue Type: Bug > Components: jxr >Affects Versions: 2.3 >Reporter: Davide Cavestro >Assignee: Robert Scholte >Priority: Major > Fix For: 3.0.0 > > Attachments: missinglinks.png, my-app.zip > > > Launching JXR on a file containing method declarations with no spaces between > the method name and the parenthesis also generates links to method parameters > types. > Adding a whitespace before or after method declaration prevents link > generation, i.e. I get the method declaration in plain text, with no > clickable reference to _App_ type. > !missinglinks.png! > I've attached the example project as [^my-app.zip]. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-5958) java.lang.String cannot be cast to org.apache.maven.lifecycle.mapping.LifecyclePhase
[
https://issues.apache.org/jira/browse/MNG-5958?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528604#comment-16528604
]
Hudson commented on MNG-5958:
-
Build failed in Jenkins: Maven TLP » maven » MNG-6424 #3
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6424/3/
> java.lang.String cannot be cast to
> org.apache.maven.lifecycle.mapping.LifecyclePhase
>
>
> Key: MNG-5958
> URL: https://issues.apache.org/jira/browse/MNG-5958
> Project: Maven
> Issue Type: Bug
> Components: Plugins and Lifecycle
>Affects Versions: 3.3.9
> Environment: win 8.1
>Reporter: Meytal Genah
>Assignee: Christian Schulte
>Priority: Minor
> Fix For: 3.5.0-alpha-1, 3.5.0
>
>
> Our app uses flex mojo.
> We upgraded from Maven 3.3.3 to Maven 3.3.9 and when building we get:
> {noformat}[ERROR] Internal error: java.lang.ClassCastException:
> java.lang.String cannot be cast to
> org.apache.maven.lifecycle.mapping.LifecyclePhase -> [Help 1]
> org.apache.maven.InternalErrorException: Internal error:
> java.lang.ClassCastException: java.lang.String cannot be cast to
> org.apache.maven.lifecycle.mapping.LifecyclePhas
> e
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:121)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:863)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:288)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:199)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:497)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:289)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:229)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:415)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:356)
> Caused by: java.lang.ClassCastException: java.lang.String cannot be cast to
> org.apache.maven.lifecycle.mapping.LifecyclePhase
> at
> org.apache.maven.lifecycle.internal.DefaultLifecyclePluginAnalyzer.getPluginsBoundByDefaultToAllLifecycles(DefaultLifecyclePluginAnalyzer.java:119)
> at
> org.apache.maven.model.plugin.DefaultLifecycleBindingsInjector.injectLifecycleBindings(DefaultLifecycleBindingsInjector.java:64)
> at
> org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:451)
> at
> org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:421)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:620)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:626)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:626)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:626)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:626)
> at
> org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:411)
> at
> org.apache.maven.graph.DefaultGraphBuilder.collectProjects(DefaultGraphBuilder.java:419)
> at
> org.apache.maven.graph.DefaultGraphBuilder.getProjectsForMavenReactor(DefaultGraphBuilder.java:410)
> at
> org.apache.maven.graph.DefaultGraphBuilder.build(DefaultGraphBuilder.java:83)
> at org.apache.maven.DefaultMaven.buildGraph(DefaultMaven.java:491)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:219)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> ... 11 more{noformat}
> I didn’t see anyone encountering the same problem. Maybe it is related to the
> fix of https://issues.apache.org/jira/browse/MNG-5805.
> Also, according to the stack trace, the invalid casting is in this line:
> {code:java}LifecyclePhase goals =
> goalsForLifecyclePhase.getValue();{code}
> this is the content of the pom.xml:
> {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.myapp.plugin
> GUI
> trunk
>
>
[jira] [Commented] (MNG-6426) IT for MNG-6127 fails on Java 9+
[
https://issues.apache.org/jira/browse/MNG-6426?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528599#comment-16528599
]
Hudson commented on MNG-6426:
-
Build failed in Jenkins: Maven TLP » maven » MNG-6424 #3
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6424/3/
> IT for MNG-6127 fails on Java 9+
>
>
> Key: MNG-6426
> URL: https://issues.apache.org/jira/browse/MNG-6426
> Project: Maven
> Issue Type: Bug
> Components: Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> Failure on Java 10 in Windows:
> {noformat}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile)
> on project mng-6127-plugin: Compilation failure
> [ERROR]
> /D:/Entwicklung/Projekte/maven-integration-testing/core-it-suite/target/test-classes/mng-6127-plugin-execution-configuration-interference/plugin/src/main/java/org/apache/maven/its/mng6127/plugin/TestMojo.java:[67,13]
> try-with-resources is not supported in -source 6
> [ERROR] (use -source 7 or higher to enable try-with-resources)
> [ERROR] -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile
> (default-compile) on project mng-6127-plugin: Compilation failure
> {noformat}
> The compiled plugin uses Java 7, but the code introduced in
> ee3cae93ce70f9ff1898b5c10f3cce59898923af autoresets everything to 1.6.
> Drop all occurencies of {{maven.compiler.*}} and remove the
> try-with-resources statement.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6127) Fix plugin execution configuration interference
[ https://issues.apache.org/jira/browse/MNG-6127?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528600#comment-16528600 ] Hudson commented on MNG-6127: - Build failed in Jenkins: Maven TLP » maven » MNG-6424 #3 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6424/3/ > Fix plugin execution configuration interference > --- > > Key: MNG-6127 > URL: https://issues.apache.org/jira/browse/MNG-6127 > Project: Maven > Issue Type: Bug > Components: core >Affects Versions: 3.3.9 >Reporter: Mario Krizmanic >Assignee: Robert Scholte >Priority: Major > Fix For: 3.5.2 > > > The plugin execution configuration may interfere across maven modules > included in a build in case a plugin extension provides a default > configuration. > Because the custom plugin configuration defined in the maven modules is > merged to the plugin execution configuration and the merged configuration is > re-used during building the other included maven modules, so the other maven > modules may be build using the invalid configuration. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MNG-5940) Change the maven-source-plugin jar goal into jar-no-fork in Maven Super POM
[
https://issues.apache.org/jira/browse/MNG-5940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528598#comment-16528598
]
Hudson commented on MNG-5940:
-
Build failed in Jenkins: Maven TLP » maven » MNG-6424 #3
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6424/3/
> Change the maven-source-plugin jar goal into jar-no-fork in Maven Super POM
> ---
>
> Key: MNG-5940
> URL: https://issues.apache.org/jira/browse/MNG-5940
> Project: Maven
> Issue Type: Improvement
> Components: core
>Reporter: Karl Heinz Marbaise
>Assignee: Michael Osipov
>Priority: Minor
> Fix For: 3.5.4
>
>
> At the moment the {{maven-source-plugin:jar}} goal is defined in the Maven
> super pom:
> {code:xml}
>
> true
> maven-source-plugin
>
>
> attach-sources
>
> jar
>
>
>
>
> {code}
> where the goal of {{maven-source-plugin}} should be changed from {{jar}} into
> {{jar-no-fork}}, cause most of the time you need to override this behaviour.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6428) IT for MNG-5958 fails on Java 9+
[
https://issues.apache.org/jira/browse/MNG-6428?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528603#comment-16528603
]
Hudson commented on MNG-6428:
-
Build failed in Jenkins: Maven TLP » maven » MNG-6424 #3
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6424/3/
> IT for MNG-5958 fails on Java 9+
>
>
> Key: MNG-6428
> URL: https://issues.apache.org/jira/browse/MNG-6428
> Project: Maven
> Issue Type: Bug
> Components: Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> The failure lies in the parsing of the error log. It expects:
> {noformat}
> verifier.verifyTextInLog( "[ERROR] Internal error:
> java.lang.ClassCastException: "
> + "org.apache.maven.lifecycle.mapping.LifecyclePhase cannot
> be cast to java.lang.String -> [Help 1]" );
> {noformat}
> while Java 9+ includes the module name:
> {noformat}
> [ERROR] Internal error: java.lang.ClassCastException:
> org.apache.maven.lifecycle.mapping.LifecyclePhase cannot be cast to
> java.base/java.lang.String -> [Help 1]
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-6427) IT for MNG-1957 fails on Java 9+
[
https://issues.apache.org/jira/browse/MNG-6427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528601#comment-16528601
]
Hudson commented on MNG-6427:
-
Build failed in Jenkins: Maven TLP » maven » MNG-6424 #3
See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6424/3/
> IT for MNG-1957 fails on Java 9+
>
>
> Key: MNG-6427
> URL: https://issues.apache.org/jira/browse/MNG-6427
> Project: Maven
> Issue Type: Bug
> Components: Integration Tests
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
>
> The execution fails with:
> {noformat}
> junit.framework.ComparisonFailure: expected: but was:
> at
> org.apache.maven.it.MavenITmng1957JdkActivationWithVersionRangeTest.testitMNG1957(MavenITmng1957JdkActivationWithVersionRangeTest.java:64)
> {noformat}
> This is caused by incorrect JDK ranges in the {{pom.xml}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MNG-1957) clause in the activation section has to provide more complex expressions.
[ https://issues.apache.org/jira/browse/MNG-1957?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528602#comment-16528602 ] Hudson commented on MNG-1957: - Build failed in Jenkins: Maven TLP » maven » MNG-6424 #3 See https://builds.apache.org/job/maven-box/job/maven/job/MNG-6424/3/ > clause in the activation section has to provide more complex > expressions. > - > > Key: MNG-1957 > URL: https://issues.apache.org/jira/browse/MNG-1957 > Project: Maven > Issue Type: Improvement > Components: POM >Affects Versions: 2.0, 2.0.1 >Reporter: Trustin Lee >Assignee: Brett Porter >Priority: Major > Fix For: 2.1.0 > > Attachments: MNG-1957-maven-project.patch > > > For now, provides only one operator '!' which means negation, but > it would be great if i can use '+' and ~ operator: > 1.5+ > 1.1 ~ 1.4 > ~ 1.3 > 1.4 ~ -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MJLINK-19) update plexus-java / asm so it will work on java 10.0.1
[
https://issues.apache.org/jira/browse/MJLINK-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528588#comment-16528588
]
Hudson commented on MJLINK-19:
--
Build succeeded in Jenkins: Maven TLP » maven-jlink-plugin » MJLINK-19 #3
See
https://builds.apache.org/job/maven-box/job/maven-jlink-plugin/job/MJLINK-19/3/
> update plexus-java / asm so it will work on java 10.0.1
> ---
>
> Key: MJLINK-19
> URL: https://issues.apache.org/jira/browse/MJLINK-19
> Project: Maven JLink Plugin
> Issue Type: Dependency upgrade
>Affects Versions: 3.0.0-alpha-2
>Reporter: Jim Sellers
>Priority: Major
>
> To get it to work on mac / java 10, I had to bump up asm 6.2. This is similar
> to MCOMPILER-342
> plexus-java 0.9.10 uses asm 6.2 transitively.
> I'm not sure if some versions are being held back for compatibility reasons
> (like maven core) but here's what's out of date.
> {code:title=versions:display-dependency-updates}
> [INFO] The following dependencies in Dependencies have newer versions:
> [INFO] org.apache.commons:commons-lang3 .. 3.6 ->
> 3.7
> [INFO] org.apache.maven:maven-core . 3.0 ->
> 3.5.4
> [INFO] org.apache.maven:maven-plugin-api ... 3.0 ->
> 3.5.4
> [INFO] org.assertj:assertj-core . 1.7.1 ->
> 3.10.0
> [INFO] org.codehaus.plexus:plexus-archiver . 3.5 ->
> 3.6.0
> [INFO] org.codehaus.plexus:plexus-java .. 0.9.7 ->
> 0.9.10
> [INFO] org.mockito:mockito-core ... 1.10.19 ->
> 2.19.0
> [INFO]
> [INFO] artifact org.apache.maven.shared:maven-shared-resources: checking for
> updates from central
> [INFO] No dependencies in pluginManagement of plugins have newer versions.
> [INFO]
> [INFO] artifact org.codehaus.mojo:extra-enforcer-rules: checking for updates
> from central
> [INFO] The following dependencies in Plugin Dependencies have newer versions:
> [INFO] org.codehaus.mojo:extra-enforcer-rules .. 1.0-beta-7 ->
> 1.0-beta-9
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (MJLINK-19) update plexus-java / asm so it will work on java 10.0.1
[
https://issues.apache.org/jira/browse/MJLINK-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528576#comment-16528576
]
Karl Heinz Marbaise edited comment on MJLINK-19 at 6/30/18 7:13 AM:
* plexus-java 0.9.10
* plexus-archiver 3.6.0
* assertj-core 2.9.1 (max cause latest for JDK 7)
* mockito-core 2.19.0
was (Author: khmarbaise):
* plexus-java 0.9.10
* plexus-archiver 3.6.0
> update plexus-java / asm so it will work on java 10.0.1
> ---
>
> Key: MJLINK-19
> URL: https://issues.apache.org/jira/browse/MJLINK-19
> Project: Maven JLink Plugin
> Issue Type: Dependency upgrade
>Affects Versions: 3.0.0-alpha-2
>Reporter: Jim Sellers
>Priority: Major
>
> To get it to work on mac / java 10, I had to bump up asm 6.2. This is similar
> to MCOMPILER-342
> plexus-java 0.9.10 uses asm 6.2 transitively.
> I'm not sure if some versions are being held back for compatibility reasons
> (like maven core) but here's what's out of date.
> {code:title=versions:display-dependency-updates}
> [INFO] The following dependencies in Dependencies have newer versions:
> [INFO] org.apache.commons:commons-lang3 .. 3.6 ->
> 3.7
> [INFO] org.apache.maven:maven-core . 3.0 ->
> 3.5.4
> [INFO] org.apache.maven:maven-plugin-api ... 3.0 ->
> 3.5.4
> [INFO] org.assertj:assertj-core . 1.7.1 ->
> 3.10.0
> [INFO] org.codehaus.plexus:plexus-archiver . 3.5 ->
> 3.6.0
> [INFO] org.codehaus.plexus:plexus-java .. 0.9.7 ->
> 0.9.10
> [INFO] org.mockito:mockito-core ... 1.10.19 ->
> 2.19.0
> [INFO]
> [INFO] artifact org.apache.maven.shared:maven-shared-resources: checking for
> updates from central
> [INFO] No dependencies in pluginManagement of plugins have newer versions.
> [INFO]
> [INFO] artifact org.codehaus.mojo:extra-enforcer-rules: checking for updates
> from central
> [INFO] The following dependencies in Plugin Dependencies have newer versions:
> [INFO] org.codehaus.mojo:extra-enforcer-rules .. 1.0-beta-7 ->
> 1.0-beta-9
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MJLINK-19) update plexus-java / asm so it will work on java 10.0.1
[
https://issues.apache.org/jira/browse/MJLINK-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528582#comment-16528582
]
Hudson commented on MJLINK-19:
--
Build succeeded in Jenkins: Maven TLP » maven-jlink-plugin » MJLINK-19 #2
See
https://builds.apache.org/job/maven-box/job/maven-jlink-plugin/job/MJLINK-19/2/
> update plexus-java / asm so it will work on java 10.0.1
> ---
>
> Key: MJLINK-19
> URL: https://issues.apache.org/jira/browse/MJLINK-19
> Project: Maven JLink Plugin
> Issue Type: Dependency upgrade
>Affects Versions: 3.0.0-alpha-2
>Reporter: Jim Sellers
>Priority: Major
>
> To get it to work on mac / java 10, I had to bump up asm 6.2. This is similar
> to MCOMPILER-342
> plexus-java 0.9.10 uses asm 6.2 transitively.
> I'm not sure if some versions are being held back for compatibility reasons
> (like maven core) but here's what's out of date.
> {code:title=versions:display-dependency-updates}
> [INFO] The following dependencies in Dependencies have newer versions:
> [INFO] org.apache.commons:commons-lang3 .. 3.6 ->
> 3.7
> [INFO] org.apache.maven:maven-core . 3.0 ->
> 3.5.4
> [INFO] org.apache.maven:maven-plugin-api ... 3.0 ->
> 3.5.4
> [INFO] org.assertj:assertj-core . 1.7.1 ->
> 3.10.0
> [INFO] org.codehaus.plexus:plexus-archiver . 3.5 ->
> 3.6.0
> [INFO] org.codehaus.plexus:plexus-java .. 0.9.7 ->
> 0.9.10
> [INFO] org.mockito:mockito-core ... 1.10.19 ->
> 2.19.0
> [INFO]
> [INFO] artifact org.apache.maven.shared:maven-shared-resources: checking for
> updates from central
> [INFO] No dependencies in pluginManagement of plugins have newer versions.
> [INFO]
> [INFO] artifact org.codehaus.mojo:extra-enforcer-rules: checking for updates
> from central
> [INFO] The following dependencies in Plugin Dependencies have newer versions:
> [INFO] org.codehaus.mojo:extra-enforcer-rules .. 1.0-beta-7 ->
> 1.0-beta-9
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MJLINK-19) update plexus-java / asm so it will work on java 10.0.1
[
https://issues.apache.org/jira/browse/MJLINK-19?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MJLINK-19:
--
Issue Type: Dependency upgrade (was: Improvement)
> update plexus-java / asm so it will work on java 10.0.1
> ---
>
> Key: MJLINK-19
> URL: https://issues.apache.org/jira/browse/MJLINK-19
> Project: Maven JLink Plugin
> Issue Type: Dependency upgrade
>Affects Versions: 3.0.0-alpha-2
>Reporter: Jim Sellers
>Priority: Major
>
> To get it to work on mac / java 10, I had to bump up asm 6.2. This is similar
> to MCOMPILER-342
> plexus-java 0.9.10 uses asm 6.2 transitively.
> I'm not sure if some versions are being held back for compatibility reasons
> (like maven core) but here's what's out of date.
> {code:title=versions:display-dependency-updates}
> [INFO] The following dependencies in Dependencies have newer versions:
> [INFO] org.apache.commons:commons-lang3 .. 3.6 ->
> 3.7
> [INFO] org.apache.maven:maven-core . 3.0 ->
> 3.5.4
> [INFO] org.apache.maven:maven-plugin-api ... 3.0 ->
> 3.5.4
> [INFO] org.assertj:assertj-core . 1.7.1 ->
> 3.10.0
> [INFO] org.codehaus.plexus:plexus-archiver . 3.5 ->
> 3.6.0
> [INFO] org.codehaus.plexus:plexus-java .. 0.9.7 ->
> 0.9.10
> [INFO] org.mockito:mockito-core ... 1.10.19 ->
> 2.19.0
> [INFO]
> [INFO] artifact org.apache.maven.shared:maven-shared-resources: checking for
> updates from central
> [INFO] No dependencies in pluginManagement of plugins have newer versions.
> [INFO]
> [INFO] artifact org.codehaus.mojo:extra-enforcer-rules: checking for updates
> from central
> [INFO] The following dependencies in Plugin Dependencies have newer versions:
> [INFO] org.codehaus.mojo:extra-enforcer-rules .. 1.0-beta-7 ->
> 1.0-beta-9
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MJLINK-19) update plexus-java / asm so it will work on java 10.0.1
[
https://issues.apache.org/jira/browse/MJLINK-19?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16528576#comment-16528576
]
Karl Heinz Marbaise commented on MJLINK-19:
---
* plexus-java 0.9.10
* plexus-archiver 3.6.0
> update plexus-java / asm so it will work on java 10.0.1
> ---
>
> Key: MJLINK-19
> URL: https://issues.apache.org/jira/browse/MJLINK-19
> Project: Maven JLink Plugin
> Issue Type: Improvement
>Affects Versions: 3.0.0-alpha-2
>Reporter: Jim Sellers
>Priority: Major
>
> To get it to work on mac / java 10, I had to bump up asm 6.2. This is similar
> to MCOMPILER-342
> plexus-java 0.9.10 uses asm 6.2 transitively.
> I'm not sure if some versions are being held back for compatibility reasons
> (like maven core) but here's what's out of date.
> {code:title=versions:display-dependency-updates}
> [INFO] The following dependencies in Dependencies have newer versions:
> [INFO] org.apache.commons:commons-lang3 .. 3.6 ->
> 3.7
> [INFO] org.apache.maven:maven-core . 3.0 ->
> 3.5.4
> [INFO] org.apache.maven:maven-plugin-api ... 3.0 ->
> 3.5.4
> [INFO] org.assertj:assertj-core . 1.7.1 ->
> 3.10.0
> [INFO] org.codehaus.plexus:plexus-archiver . 3.5 ->
> 3.6.0
> [INFO] org.codehaus.plexus:plexus-java .. 0.9.7 ->
> 0.9.10
> [INFO] org.mockito:mockito-core ... 1.10.19 ->
> 2.19.0
> [INFO]
> [INFO] artifact org.apache.maven.shared:maven-shared-resources: checking for
> updates from central
> [INFO] No dependencies in pluginManagement of plugins have newer versions.
> [INFO]
> [INFO] artifact org.codehaus.mojo:extra-enforcer-rules: checking for updates
> from central
> [INFO] The following dependencies in Plugin Dependencies have newer versions:
> [INFO] org.codehaus.mojo:extra-enforcer-rules .. 1.0-beta-7 ->
> 1.0-beta-9
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
