[jira] [Updated] (MARCHETYPES-51) add plugin testing harness to maven-archetype-plugin
[ https://issues.apache.org/jira/browse/MARCHETYPES-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MARCHETYPES-51: - Issue Type: Improvement (was: Dependency upgrade) > add plugin testing harness to maven-archetype-plugin > > > Key: MARCHETYPES-51 > URL: https://issues.apache.org/jira/browse/MARCHETYPES-51 > Project: Maven Archetype Bundles > Issue Type: Improvement > Components: Maven Plugin Archetype >Affects Versions: maven-archetype-plugin-1.3 > Environment: macOS High Sierra >Reporter: Nick Lombard >Assignee: Hervé Boutemy >Priority: Major > Fix For: 1.3 > > Attachments: MARCHETYPES-51.patch > > > I want to update the plugin archetype (for creating new plugins not to be > confused with the archetype plugin) to also include a testing harness unit > test example alongside the currently supplied integration test example. > Once completed the documentation can then be updated to reflect the new > starting point. The documentation currently under Plugin Developers Centre > should also be merged with Cookbook: How To Use Maven Plugin Testing Harness? > But lets start with updating the archetype and take it from there. > Please let me know if there you have any problem with me working on this or > if there are any special requirements you would like to see addressed. > I am going with the assumption that > http://svn.apache.org/viewvc/maven/archetypes is the correct repository to > patch against because this repo has not been migrated to git as yet. Please > correct me if I am wrong. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (SUREFIRE-1510) Jenkins CI fails due to performance of Windows break concurrency of forked JVMs
[
https://issues.apache.org/jira/browse/SUREFIRE-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana closed SUREFIRE-1510.
--
Resolution: Fixed
https://gitbox.apache.org/repos/asf?p=maven-surefire.git;a=commit;h=ee02966ec23638b3ad57f63ba1ae71f886d37ac9
> Jenkins CI fails due to performance of Windows break concurrency of forked
> JVMs
> ---
>
> Key: SUREFIRE-1510
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1510
> Project: Maven Surefire
> Issue Type: Task
> Components: Maven Failsafe Plugin, Maven Surefire Plugin, process
> forking
> Environment: Windows
> ASF Jenkins CI
>Reporter: Tibor Digana
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M1
>
>
> We have a problem with this build
> https://builds.apache.org/job/maven-box/job/maven-surefire/job/master/6
> There are two Build Failures:
> #
> testForkModeOncePerThreadTwoThreads(org.apache.maven.surefire.its.ForkModeIT):
> number of different pids is not as expected expected:<2> but was:<1>
> # test[junit4-twoForks-ff1](org.apache.maven.surefire.its.FailFastJUnitIT):
> wrong number of errors expected:<2> but was:<1>
> The {{ForkModeIT}} missed delays in JUnit test methods, but the
> {{FailFastJUnitIT}} code is ok and the only problem is virtual CPU scheduler.
> We expect that two JVMs start up within 1.5 second and most probably this did
> not happen.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1511) Surefire java.lang.ClassFormatError error when running powermockito textNg tests
[
https://issues.apache.org/jira/browse/SUREFIRE-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16423463#comment-16423463
]
Tibor Digana commented on SUREFIRE-1511:
[~prathyushkp]
Try to run the tests in IntelliJ IDEA or in Ecplise, but you see that Mockito
is arguing and not the Surefire.
> Surefire java.lang.ClassFormatError error when running powermockito textNg
> tests
>
>
> Key: SUREFIRE-1511
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1511
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.21.0
>Reporter: Prathyush
>Priority: Blocker
>
>
> powermock-version : 1.6.6
> mockito-version : 2.0.2-beta
> maven-surefire-plugin version : 2.20.1
> When running tests using below profile am getting below exception
> *Profile :*
>
> sonar-coverage
>
> false
>
>
>
>
>
> org.jacoco
> jacoco-maven-plugin
> 0.7.9
>
>
>
>
>
> org.apache.maven.plugins
> maven-surefire-plugin
> 2.21.0
>
>
> default-test
> test
>
> test
>
>
>
>
>
>
> **/DocGenDistBusinessServiceImplTest.java
> **/TeamworksStipulationCreationListenerImplTest.java
> **/UpdateClosingFeeStateListenerTest.java
> **/SubscribeEvent.java
> **/PublishEvent.java
>
> **/ECBSHelper_Test.java
> **/StipulationImageAssociationServiceRPCMilestoneTest.java
>
> -Xms512m -Xmx10648m ${argLine}
> -javaagent:${settings.localRepository}/org/springframework/spring-instrument/${spring.version}/spring-instrument-${spring.version}.jar
>
>
>
> listener
> com.wellsfargo.core.common.dp.testng.LogTestListener
>
>
> random
>
>
>
> org.jacoco
> jacoco-maven-plugin
>
> true
>
>
>
> agent-for-ut
> initialize
>
> prepare-agent
>
>
> ${basedir}/target/jacoco.exec
>
>
>
> agent-for-it
>
> prepare-agent-integration
>
>
> ${basedir}/target/jacoco.exec
>
>
>
> jacoco-site
> test
>
> report
>
>
>
>
>
> org.eluder.coveralls
> coveralls-maven-plugin
> 4.3.0
>
>
>
>
>
> org.sonarsource.java
> sonar-jacoco-listeners
> 4.15.0.12310
> test
>
>
> org.jacoco
> org.jacoco.agent
> 0.7.9
> runtime
> test
>
>
>
> *Exception:*
> org.mockito.exceptions.base.MockitoException:
> Mockito cannot mock this class: class
> com.wellsfargo.core.business.service.dp.applicationManagement.hmda.reportableData.field.handler.BaseHmdaFieldGetterBusinessHierarchy$$EnhancerByMockitoWithCGLIB$$6b2b5065
> Mockito can only mock visible non-final classes.
> If you're not sure why you're getting this error, please report to the
> mailing list.
> at
> org.powermock.api.extension.listener.AnnotationEnabler.injectSpiesAndInjectToSetters(AnnotationEnabler.java:72)
> at
> org.powermock.api.extension.listener.AnnotationEnabler.beforeTestMethod(AnnotationEnabler.java:64)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.powermock.reflect.internal.WhiteboxImpl.performMethodInvocation(WhiteboxImpl.java:1819)
> at
> org.powermock.reflect.internal.WhiteboxImpl.invokeMethod(WhiteboxImpl.java:691)
> at org.powermock.reflect.Whitebox.invokeMethod(Whitebox.java:415)
> at
> org.powermock.modules.testng.PowerMockTestCase.injectMocks(PowerMockTestCase.java:165)
> at
> org.powermock.modules.testng.PowerMockTestCase.beforePowerMockTestMethod(PowerMockTestCase.java:89)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84)
> at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:564)
> at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213)
> at org.testng.internal.Invoker.invokeMethod(Invoker.java:653)
> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
> at
> org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
> at org.testng.TestRunner.privateRun(TestRunner.java:767)
> at org.testng.TestRunner.run(TestRunner.java:617)
> at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
> at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
> at
[jira] [Commented] (SUREFIRE-1511) Surefire java.lang.ClassFormatError error when running powermockito textNg tests
[
https://issues.apache.org/jira/browse/SUREFIRE-1511?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16423376#comment-16423376
]
Prathyush commented on SUREFIRE-1511:
-
[~tibor17], can you please help on this one?
> Surefire java.lang.ClassFormatError error when running powermockito textNg
> tests
>
>
> Key: SUREFIRE-1511
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1511
> Project: Maven Surefire
> Issue Type: Bug
>Affects Versions: 2.21.0
>Reporter: Prathyush
>Priority: Blocker
>
>
> powermock-version : 1.6.6
> mockito-version : 2.0.2-beta
> maven-surefire-plugin version : 2.20.1
> When running tests using below profile am getting below exception
> *Profile :*
>
> sonar-coverage
>
> false
>
>
>
>
>
> org.jacoco
> jacoco-maven-plugin
> 0.7.9
>
>
>
>
>
> org.apache.maven.plugins
> maven-surefire-plugin
> 2.21.0
>
>
> default-test
> test
>
> test
>
>
>
>
>
>
> **/DocGenDistBusinessServiceImplTest.java
> **/TeamworksStipulationCreationListenerImplTest.java
> **/UpdateClosingFeeStateListenerTest.java
> **/SubscribeEvent.java
> **/PublishEvent.java
>
> **/ECBSHelper_Test.java
> **/StipulationImageAssociationServiceRPCMilestoneTest.java
>
> -Xms512m -Xmx10648m ${argLine}
> -javaagent:${settings.localRepository}/org/springframework/spring-instrument/${spring.version}/spring-instrument-${spring.version}.jar
>
>
>
> listener
> com.wellsfargo.core.common.dp.testng.LogTestListener
>
>
> random
>
>
>
> org.jacoco
> jacoco-maven-plugin
>
> true
>
>
>
> agent-for-ut
> initialize
>
> prepare-agent
>
>
> ${basedir}/target/jacoco.exec
>
>
>
> agent-for-it
>
> prepare-agent-integration
>
>
> ${basedir}/target/jacoco.exec
>
>
>
> jacoco-site
> test
>
> report
>
>
>
>
>
> org.eluder.coveralls
> coveralls-maven-plugin
> 4.3.0
>
>
>
>
>
> org.sonarsource.java
> sonar-jacoco-listeners
> 4.15.0.12310
> test
>
>
> org.jacoco
> org.jacoco.agent
> 0.7.9
> runtime
> test
>
>
>
> *Exception:*
> org.mockito.exceptions.base.MockitoException:
> Mockito cannot mock this class: class
> com.wellsfargo.core.business.service.dp.applicationManagement.hmda.reportableData.field.handler.BaseHmdaFieldGetterBusinessHierarchy$$EnhancerByMockitoWithCGLIB$$6b2b5065
> Mockito can only mock visible non-final classes.
> If you're not sure why you're getting this error, please report to the
> mailing list.
> at
> org.powermock.api.extension.listener.AnnotationEnabler.injectSpiesAndInjectToSetters(AnnotationEnabler.java:72)
> at
> org.powermock.api.extension.listener.AnnotationEnabler.beforeTestMethod(AnnotationEnabler.java:64)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.powermock.reflect.internal.WhiteboxImpl.performMethodInvocation(WhiteboxImpl.java:1819)
> at
> org.powermock.reflect.internal.WhiteboxImpl.invokeMethod(WhiteboxImpl.java:691)
> at org.powermock.reflect.Whitebox.invokeMethod(Whitebox.java:415)
> at
> org.powermock.modules.testng.PowerMockTestCase.injectMocks(PowerMockTestCase.java:165)
> at
> org.powermock.modules.testng.PowerMockTestCase.beforePowerMockTestMethod(PowerMockTestCase.java:89)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:498)
> at
> org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84)
> at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:564)
> at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213)
> at org.testng.internal.Invoker.invokeMethod(Invoker.java:653)
> at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
> at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
> at
> org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
> at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
> at org.testng.TestRunner.privateRun(TestRunner.java:767)
> at org.testng.TestRunner.run(TestRunner.java:617)
> at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
> at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
> at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
> at
[jira] [Created] (SUREFIRE-1511) Surefire java.lang.ClassFormatError error when running powermockito textNg tests
Prathyush created SUREFIRE-1511:
---
Summary: Surefire java.lang.ClassFormatError error when running
powermockito textNg tests
Key: SUREFIRE-1511
URL: https://issues.apache.org/jira/browse/SUREFIRE-1511
Project: Maven Surefire
Issue Type: Bug
Affects Versions: 2.21.0
Reporter: Prathyush
powermock-version : 1.6.6
mockito-version : 2.0.2-beta
maven-surefire-plugin version : 2.20.1
When running tests using below profile am getting below exception
*Profile :*
sonar-coverage
false
org.jacoco
jacoco-maven-plugin
0.7.9
org.apache.maven.plugins
maven-surefire-plugin
2.21.0
default-test
test
test
**/DocGenDistBusinessServiceImplTest.java
**/TeamworksStipulationCreationListenerImplTest.java
**/UpdateClosingFeeStateListenerTest.java
**/SubscribeEvent.java
**/PublishEvent.java
**/ECBSHelper_Test.java
**/StipulationImageAssociationServiceRPCMilestoneTest.java
-Xms512m -Xmx10648m ${argLine}
-javaagent:${settings.localRepository}/org/springframework/spring-instrument/${spring.version}/spring-instrument-${spring.version}.jar
listener
com.wellsfargo.core.common.dp.testng.LogTestListener
random
org.jacoco
jacoco-maven-plugin
true
agent-for-ut
initialize
prepare-agent
${basedir}/target/jacoco.exec
agent-for-it
prepare-agent-integration
${basedir}/target/jacoco.exec
jacoco-site
test
report
org.eluder.coveralls
coveralls-maven-plugin
4.3.0
org.sonarsource.java
sonar-jacoco-listeners
4.15.0.12310
test
org.jacoco
org.jacoco.agent
0.7.9
runtime
test
*Exception:*
org.mockito.exceptions.base.MockitoException:
Mockito cannot mock this class: class
com.wellsfargo.core.business.service.dp.applicationManagement.hmda.reportableData.field.handler.BaseHmdaFieldGetterBusinessHierarchy$$EnhancerByMockitoWithCGLIB$$6b2b5065
Mockito can only mock visible non-final classes.
If you're not sure why you're getting this error, please report to the mailing
list.
at
org.powermock.api.extension.listener.AnnotationEnabler.injectSpiesAndInjectToSetters(AnnotationEnabler.java:72)
at
org.powermock.api.extension.listener.AnnotationEnabler.beforeTestMethod(AnnotationEnabler.java:64)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.powermock.reflect.internal.WhiteboxImpl.performMethodInvocation(WhiteboxImpl.java:1819)
at
org.powermock.reflect.internal.WhiteboxImpl.invokeMethod(WhiteboxImpl.java:691)
at org.powermock.reflect.Whitebox.invokeMethod(Whitebox.java:415)
at
org.powermock.modules.testng.PowerMockTestCase.injectMocks(PowerMockTestCase.java:165)
at
org.powermock.modules.testng.PowerMockTestCase.beforePowerMockTestMethod(PowerMockTestCase.java:89)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:498)
at
org.testng.internal.MethodInvocationHelper.invokeMethod(MethodInvocationHelper.java:84)
at org.testng.internal.Invoker.invokeConfigurationMethod(Invoker.java:564)
at org.testng.internal.Invoker.invokeConfigurations(Invoker.java:213)
at org.testng.internal.Invoker.invokeMethod(Invoker.java:653)
at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:901)
at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1231)
at
org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
at org.testng.TestRunner.privateRun(TestRunner.java:767)
at org.testng.TestRunner.run(TestRunner.java:617)
at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
at org.testng.SuiteRunner.run(SuiteRunner.java:240)
at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:52)
at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:86)
at org.testng.TestNG.runSuitesSequentially(TestNG.java:1224)
at org.testng.TestNG.runSuitesLocally(TestNG.java:1149)
at org.testng.TestNG.run(TestNG.java:1057)
at org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:135)
at
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.executeSingleClass(TestNGDirectoryTestSuite.java:112)
at
org.apache.maven.surefire.testng.TestNGDirectoryTestSuite.execute(TestNGDirectoryTestSuite.java:99)
at
[jira] [Commented] (MNG-6387) Pom files should have a dedicated mime type registered ("application/pom+xml" or similar)
[
https://issues.apache.org/jira/browse/MNG-6387?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16423353#comment-16423353
]
Alex Dubov commented on MNG-6387:
-
https://issues.apache.org/jira/browse/MRM-755
This sort of issues.
But on more diverse scale - for example, when hosting stuff on S3 and
populating Content-Type metadata using a common mime database.
> Pom files should have a dedicated mime type registered ("application/pom+xml"
> or similar)
> -
>
> Key: MNG-6387
> URL: https://issues.apache.org/jira/browse/MNG-6387
> Project: Maven
> Issue Type: Wish
> Components: POM
>Reporter: Alex Dubov
>Priority: Trivial
>
> For the sake of convenience working with ever growing abundance of packages,
> and, thus, pom files, is not it time to give the humble pom file its own,
> dedicated mime type (something to the tune of "application/pom+xml")?
> Presently, the fact that pom files don't have a dedicated mime type causes
> all kinds of minor but annoying issues in all kinds of least expected places.
> Considering that registering a mime type with IANA is a pretty
> straightforward process and that pom files are widely used for all kinds of
> automation purposes (and not exclusively by maven anymore), I, on behalf of
> the wider community, urge you to consider registering a dedicated pom mime
> type.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (SUREFIRE-1510) Jenkins CI fails due to performance of Windows break concurrency of forked JVMs
[
https://issues.apache.org/jira/browse/SUREFIRE-1510?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Tibor Digana updated SUREFIRE-1510:
---
Fix Version/s: 3.0.0-M1
> Jenkins CI fails due to performance of Windows break concurrency of forked
> JVMs
> ---
>
> Key: SUREFIRE-1510
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1510
> Project: Maven Surefire
> Issue Type: Task
> Components: Maven Failsafe Plugin, Maven Surefire Plugin, process
> forking
> Environment: Windows
> ASF Jenkins CI
>Reporter: Tibor Digana
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M1
>
>
> We have a problem with this build
> https://builds.apache.org/job/maven-box/job/maven-surefire/job/master/6
> There are two Build Failures:
> #
> testForkModeOncePerThreadTwoThreads(org.apache.maven.surefire.its.ForkModeIT):
> number of different pids is not as expected expected:<2> but was:<1>
> # test[junit4-twoForks-ff1](org.apache.maven.surefire.its.FailFastJUnitIT):
> wrong number of errors expected:<2> but was:<1>
> The {{ForkModeIT}} missed delays in JUnit test methods, but the
> {{FailFastJUnitIT}} code is ok and the only problem is virtual CPU scheduler.
> We expect that two JVMs start up within 1.5 second and most probably this did
> not happen.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (SUREFIRE-1510) Jenkins CI fails due to performance of Windows break concurrency of forked JVMs
Tibor Digana created SUREFIRE-1510:
--
Summary: Jenkins CI fails due to performance of Windows break
concurrency of forked JVMs
Key: SUREFIRE-1510
URL: https://issues.apache.org/jira/browse/SUREFIRE-1510
Project: Maven Surefire
Issue Type: Task
Components: Maven Failsafe Plugin, Maven Surefire Plugin, process
forking
Environment: Windows
ASF Jenkins CI
Reporter: Tibor Digana
Assignee: Tibor Digana
We have a problem with this build
https://builds.apache.org/job/maven-box/job/maven-surefire/job/master/6
There are two Build Failures:
#
testForkModeOncePerThreadTwoThreads(org.apache.maven.surefire.its.ForkModeIT):
number of different pids is not as expected expected:<2> but was:<1>
# test[junit4-twoForks-ff1](org.apache.maven.surefire.its.FailFastJUnitIT):
wrong number of errors expected:<2> but was:<1>
The {{ForkModeIT}} missed delays in JUnit test methods, but the
{{FailFastJUnitIT}} code is ok and the only problem is virtual CPU scheduler.
We expect that two JVMs start up within 1.5 second and most probably this did
not happen.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] olamy commented on issue #3: Fixed the example code in usage.apt.vm
olamy commented on issue #3: Fixed the example code in usage.apt.vm URL: https://github.com/apache/maven-checkstyle-plugin/pull/3#issuecomment-378091600 @petukhov Thanks for your contribution! 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
[GitHub] olamy closed pull request #3: Fixed the example code in usage.apt.vm
olamy closed pull request #3: Fixed the example code in usage.apt.vm
URL: https://github.com/apache/maven-checkstyle-plugin/pull/3
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 is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/src/site/apt/usage.apt.vm b/src/site/apt/usage.apt.vm
index 8d4a483..0040e48 100644
--- a/src/site/apt/usage.apt.vm
+++ b/src/site/apt/usage.apt.vm
@@ -93,17 +93,17 @@ mvn checkstyle:checkstyle
org.apache.maven.plugins
maven-checkstyle-plugin
${project.version}
+
+ checkstyle.xml
+ UTF-8
+ true
+ true
+ false
+
validate
validate
-
- checkstyle.xml
- UTF-8
- true
- true
- false
-
check
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] (SCM-840) mvn scm:tag reveals SCM git password if fatal occured during git push
[
https://issues.apache.org/jira/browse/SCM-840?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16423138#comment-16423138
]
Michael Osipov commented on SCM-840:
Please show the logout for the error.
> mvn scm:tag reveals SCM git password if fatal occured during git push
> -
>
> Key: SCM-840
> URL: https://issues.apache.org/jira/browse/SCM-840
> Project: Maven SCM
> Issue Type: Improvement
> Components: maven-scm-provider-gitexe
>Affects Versions: 1.9.5
>Reporter: Evgeni Gordeev
>Priority: Major
> Labels: Amazon, Linux
> Fix For: waiting-for-feedback
>
>
> The same error as in SCM-811 but now for {{scm:tag}} command.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (SCM-840) mvn scm:tag reveals SCM git password if fatal occured during git push
[
https://issues.apache.org/jira/browse/SCM-840?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov updated SCM-840:
---
Fix Version/s: waiting-for-feedback
> mvn scm:tag reveals SCM git password if fatal occured during git push
> -
>
> Key: SCM-840
> URL: https://issues.apache.org/jira/browse/SCM-840
> Project: Maven SCM
> Issue Type: Improvement
> Components: maven-scm-provider-gitexe
>Affects Versions: 1.9.5
>Reporter: Evgeni Gordeev
>Priority: Major
> Labels: Amazon, Linux
> Fix For: waiting-for-feedback
>
>
> The same error as in SCM-811 but now for {{scm:tag}} command.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (SCM-763) Password masking for svnexe does not handle all cases
[ https://issues.apache.org/jira/browse/SCM-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16423126#comment-16423126 ] Michael Osipov edited comment on SCM-763 at 4/2/18 8:59 PM: I have pushed now the branch SCM-763 which should solve the problem. It does for me on Windows and Fedora 27 with the Maven SCM Plugin. Snapshots deployed, please test within a week. was (Author: michael-o): I have pushed now the branch SCM-763 which should solve the problem. It does for on Windows and Fedora 27. Please test within a week. > Password masking for svnexe does not handle all cases > - > > Key: SCM-763 > URL: https://issues.apache.org/jira/browse/SCM-763 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-svn >Affects Versions: 1.9 > Environment: Jenkins 1.502 on a SLES11 >Reporter: Tobias Kalmes >Assignee: Michael Osipov >Priority: Major > Fix For: 1.9.6 > > > Passwords are not masked in the log output on Linux machines. The masking > works as intended on Windows machines. On linux machines tho the password is > printed in clear text. This seems to be a problem due to the additional > single quotes that are added around the parameters on linux machines. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SCM-763) Password masking for svnexe does not handle all cases
[ https://issues.apache.org/jira/browse/SCM-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16423126#comment-16423126 ] Michael Osipov commented on SCM-763: I have pushed now the branch SCM-763 which should solve the problem. It does for on Windows and Fedora 27. Please test within a week. > Password masking for svnexe does not handle all cases > - > > Key: SCM-763 > URL: https://issues.apache.org/jira/browse/SCM-763 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-svn >Affects Versions: 1.9 > Environment: Jenkins 1.502 on a SLES11 >Reporter: Tobias Kalmes >Assignee: Michael Osipov >Priority: Major > Fix For: 1.9.6 > > > Passwords are not masked in the log output on Linux machines. The masking > works as intended on Windows machines. On linux machines tho the password is > printed in clear text. This seems to be a problem due to the additional > single quotes that are added around the parameters on linux machines. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (SUREFIRE-1479) SurefireBooterForkException: The forked VM terminated without properly saying goodbye since 2.20.1
[
https://issues.apache.org/jira/browse/SUREFIRE-1479?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16423120#comment-16423120
]
ASF GitHub Bot commented on SUREFIRE-1479:
--
jbliznak closed pull request #179: [SUREFIRE-1479] Force UNIX Standard mode for
ps command on HP-UX OS
URL: https://github.com/apache/maven-surefire/pull/179
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 is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git
a/surefire-booter/src/main/java/org/apache/maven/surefire/booter/PpidChecker.java
b/surefire-booter/src/main/java/org/apache/maven/surefire/booter/PpidChecker.java
index 462eacc9b..32e3ad7c5 100644
---
a/surefire-booter/src/main/java/org/apache/maven/surefire/booter/PpidChecker.java
+++
b/surefire-booter/src/main/java/org/apache/maven/surefire/booter/PpidChecker.java
@@ -36,6 +36,7 @@
import static java.util.regex.Pattern.compile;
import static org.apache.commons.io.IOUtils.closeQuietly;
import static org.apache.commons.lang3.StringUtils.isNotBlank;
+import static org.apache.commons.lang3.SystemUtils.IS_OS_HP_UX;
import static org.apache.commons.lang3.SystemUtils.IS_OS_UNIX;
import static org.apache.commons.lang3.SystemUtils.IS_OS_WINDOWS;
import static org.apache.maven.surefire.booter.ProcessInfo.ERR_PROCESS_INFO;
@@ -295,6 +296,10 @@ ProcessInfo execute( String... command )
ProcessInfo processInfo = INVALID_PROCESS_INFO;
try
{
+if ( IS_OS_HP_UX ) // force to run shell commands in UNIX
Standard mode on HP-UX
+{
+processBuilder.environment().put( "UNIX95", "1" );
+}
process = processBuilder.start();
destroyableCommands.add( process );
Scanner scanner = new Scanner( process.getInputStream(),
charset );
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
> SurefireBooterForkException: The forked VM terminated without properly saying
> goodbye since 2.20.1
> --
>
> Key: SUREFIRE-1479
> URL: https://issues.apache.org/jira/browse/SUREFIRE-1479
> Project: Maven Surefire
> Issue Type: Bug
> Components: Maven Surefire Plugin
>Affects Versions: 2.20.1
>Reporter: Ondrej Lukas
>Assignee: Tibor Digana
>Priority: Major
> Fix For: 3.0.0-M1
>
>
> After upgrade to maven surefire plugin to version 2.20.1 (from version 2.20)
> our testsuite start to fail on HP-UX with:
>
>
> {code:java}
> Process Exit Code: 1 at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.awaitResultsDone(ForkStarter.java:496)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.runSuitesForkPerTestSet(ForkStarter.java:443)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:295)
> at
> org.apache.maven.plugin.surefire.booterclient.ForkStarter.run(ForkStarter.java:246)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeProvider(AbstractSurefireMojo.java:1124)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.executeAfterPreconditionsChecked(AbstractSurefireMojo.java:954)
> at
> org.apache.maven.plugin.surefire.AbstractSurefireMojo.execute(AbstractSurefireMojo.java:832)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:208)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:154)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:309)
> at
[jira] [Comment Edited] (MSHADE-284) Shaded test JARs are always empty
[
https://issues.apache.org/jira/browse/MSHADE-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16423099#comment-16423099
]
Peter De Maeyer edited comment on MSHADE-284 at 4/2/18 8:53 PM:
While fixing this issue, I found MSHADE-285 and MSHADE-286.
was (Author: peterdm):
While fixing this issue, I found MSHADE-285.
> Shaded test JARs are always empty
> -
>
> Key: MSHADE-284
> URL: https://issues.apache.org/jira/browse/MSHADE-284
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: Peter De Maeyer
>Priority: Major
> Attachments: shadeTestJar.patch
>
>
> Shading test JARs using the {{shadeTestJar}} configuration option yields an
> empty test JAR. This has been noticed by others, see for example Steve K's
> answer [on
> StackOverflow|https://stackoverflow.com/questions/5149130/how-can-i-configure-the-maven-shade-plugin-to-include-test-code-in-my-jar/49617516#49617516],
> but people have reverted to other hacks and workarounds to overcome this
> (e.g. use a different plugin).
> Scenario:
> # Create modules {{api}}, {{impl}} and a module {{uber}} which has as sole
> purpose to make an uber JAR for the combination of the first two modules.
> {{uber}} itself has no sources.
> # Both modules have both {{jar}} and {{test-jar}} artifacts.
> # Configure the {{maven-shade-plugin}} in the {{uber}} module with the
> configuration option {{shadeTestJar}} set to {{true}}.
> Expected:
> # Content of {{uber.jar}} is the aggregate content of {{api.jar}} and
> {{impl.jar}}.
> # Content of {{uber-tests.jar}} is the aggregate content of
> {{api-tests.jar}} and {{impl-tests.jar}}.
> Actual:
> # Content of {{uber.jar}} is as expected.
> # {{uber-tests.jar}} is empty.
> Root cause:
> * The implementation of the {{shadeTestJar}} feature in {{ShaderMojo}} is
> buggy and incomplete.
> * The call to {{processArtifactSelectors}} on line 425 doesn't pass the
> {{testArtifacts}}, so they are never correctly filled in.
> * The implementation of {{processArtifactSelectors}} doesn't deal with test
> JARs at all and has to be extended to support them.
> * The "if" statement on line 452 incorrectly treats a test JAR as sources.
> This whole feature looks like it was done in a hurry as a sloppy copy-paste
> job, and in 5 years nobody took the time to report or fix it. Amazing.
> Anyway, you can find my proposed fix in attachment: [^shadeTestJar.patch]. I
> have tested it manually on my project and it works.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Comment Edited] (MSHADE-284) Shaded test JARs are always empty
[
https://issues.apache.org/jira/browse/MSHADE-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16423099#comment-16423099
]
Peter De Maeyer edited comment on MSHADE-284 at 4/2/18 8:53 PM:
While fixing this issue, I also found MSHADE-285 and MSHADE-286.
was (Author: peterdm):
While fixing this issue, I found MSHADE-285 and MSHADE-286.
> Shaded test JARs are always empty
> -
>
> Key: MSHADE-284
> URL: https://issues.apache.org/jira/browse/MSHADE-284
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: Peter De Maeyer
>Priority: Major
> Attachments: shadeTestJar.patch
>
>
> Shading test JARs using the {{shadeTestJar}} configuration option yields an
> empty test JAR. This has been noticed by others, see for example Steve K's
> answer [on
> StackOverflow|https://stackoverflow.com/questions/5149130/how-can-i-configure-the-maven-shade-plugin-to-include-test-code-in-my-jar/49617516#49617516],
> but people have reverted to other hacks and workarounds to overcome this
> (e.g. use a different plugin).
> Scenario:
> # Create modules {{api}}, {{impl}} and a module {{uber}} which has as sole
> purpose to make an uber JAR for the combination of the first two modules.
> {{uber}} itself has no sources.
> # Both modules have both {{jar}} and {{test-jar}} artifacts.
> # Configure the {{maven-shade-plugin}} in the {{uber}} module with the
> configuration option {{shadeTestJar}} set to {{true}}.
> Expected:
> # Content of {{uber.jar}} is the aggregate content of {{api.jar}} and
> {{impl.jar}}.
> # Content of {{uber-tests.jar}} is the aggregate content of
> {{api-tests.jar}} and {{impl-tests.jar}}.
> Actual:
> # Content of {{uber.jar}} is as expected.
> # {{uber-tests.jar}} is empty.
> Root cause:
> * The implementation of the {{shadeTestJar}} feature in {{ShaderMojo}} is
> buggy and incomplete.
> * The call to {{processArtifactSelectors}} on line 425 doesn't pass the
> {{testArtifacts}}, so they are never correctly filled in.
> * The implementation of {{processArtifactSelectors}} doesn't deal with test
> JARs at all and has to be extended to support them.
> * The "if" statement on line 452 incorrectly treats a test JAR as sources.
> This whole feature looks like it was done in a hurry as a sloppy copy-paste
> job, and in 5 years nobody took the time to report or fix it. Amazing.
> Anyway, you can find my proposed fix in attachment: [^shadeTestJar.patch]. I
> have tested it manually on my project and it works.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] jbliznak closed pull request #179: [SUREFIRE-1479] Force UNIX Standard mode for ps command on HP-UX OS
jbliznak closed pull request #179: [SUREFIRE-1479] Force UNIX Standard mode for
ps command on HP-UX OS
URL: https://github.com/apache/maven-surefire/pull/179
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 is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git
a/surefire-booter/src/main/java/org/apache/maven/surefire/booter/PpidChecker.java
b/surefire-booter/src/main/java/org/apache/maven/surefire/booter/PpidChecker.java
index 462eacc9b..32e3ad7c5 100644
---
a/surefire-booter/src/main/java/org/apache/maven/surefire/booter/PpidChecker.java
+++
b/surefire-booter/src/main/java/org/apache/maven/surefire/booter/PpidChecker.java
@@ -36,6 +36,7 @@
import static java.util.regex.Pattern.compile;
import static org.apache.commons.io.IOUtils.closeQuietly;
import static org.apache.commons.lang3.StringUtils.isNotBlank;
+import static org.apache.commons.lang3.SystemUtils.IS_OS_HP_UX;
import static org.apache.commons.lang3.SystemUtils.IS_OS_UNIX;
import static org.apache.commons.lang3.SystemUtils.IS_OS_WINDOWS;
import static org.apache.maven.surefire.booter.ProcessInfo.ERR_PROCESS_INFO;
@@ -295,6 +296,10 @@ ProcessInfo execute( String... command )
ProcessInfo processInfo = INVALID_PROCESS_INFO;
try
{
+if ( IS_OS_HP_UX ) // force to run shell commands in UNIX
Standard mode on HP-UX
+{
+processBuilder.environment().put( "UNIX95", "1" );
+}
process = processBuilder.start();
destroyableCommands.add( process );
Scanner scanner = new Scanner( process.getInputStream(),
charset );
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] (MSHADE-286) Artifacts to be included for shading are not consistently checked for existence
Peter De Maeyer created MSHADE-286:
--
Summary: Artifacts to be included for shading are not consistently
checked for existence
Key: MSHADE-286
URL: https://issues.apache.org/jira/browse/MSHADE-286
Project: Maven Shade Plugin
Issue Type: Improvement
Affects Versions: 3.1.0
Reporter: Peter De Maeyer
While looking at {{ShaderMojo.execute}}, I noticed that the artifacts to be
included for shading are not consistently checked for existence.
For example, on line 404, the main artifact file is _not_ checked for existence:
{code:java}
artifacts.add( project.getArtifact().getFile() );{code}
But immediately below, the sources artifact file _is_ checked for existence:
{code:java}
if ( createSourcesJar )
{
File file = shadedSourcesArtifactFile();
if ( file.isFile() )
{
sourceArtifacts.add( file );
}
}
{code}
Maybe there is a reason for this, but it seems inconsistent - it seems like a
good idea to always check for existence before adding a file. I suppose the
impact of this is very low - it's merely an optimization to omit non-existent
files.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MSHADE-284) Shaded test JARs are always empty
[
https://issues.apache.org/jira/browse/MSHADE-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter De Maeyer updated MSHADE-284:
---
Description:
Shading test JARs using the {{shadeTestJar}} configuration option yields an
empty test JAR. This has been noticed by others, see for example Steve K's
answer [on
StackOverflow|https://stackoverflow.com/questions/5149130/how-can-i-configure-the-maven-shade-plugin-to-include-test-code-in-my-jar/49617516#49617516],
but people have reverted to other hacks and workarounds to overcome this (e.g.
use a different plugin).
Scenario:
# Create modules {{api}}, {{impl}} and a module {{uber}} which has as sole
purpose to make an uber JAR for the combination of the first two modules.
{{uber}} itself has no sources.
# Both modules have both {{jar}} and {{test-jar}} artifacts.
# Configure the {{maven-shade-plugin}} in the {{uber}} module with the
configuration option {{shadeTestJar}} set to {{true}}.
Expected:
# Content of {{uber.jar}} is the aggregate content of {{api.jar}} and
{{impl.jar}}.
# Content of {{uber-tests.jar}} is the aggregate content of {{api-tests.jar}}
and {{impl-tests.jar}}.
Actual:
# Content of {{uber.jar}} is as expected.
# {{uber-tests.jar}} is empty.
Root cause:
* The implementation of the {{shadeTestJar}} feature in {{ShaderMojo}} is
buggy and incomplete.
* The call to {{processArtifactSelectors}} on line 425 doesn't pass the
{{testArtifacts}}, so they are never correctly filled in.
* The implementation of {{processArtifactSelectors}} doesn't deal with test
JARs at all and has to be extended to support them.
* The "if" statement on line 452 incorrectly treats a test JAR as sources.
This whole feature looks like it was done in a hurry as a sloppy copy-paste
job, and in 5 years nobody took the time to report or fix it. Amazing. Anyway;
you can find my proposed fix in attachment: [^shadeTestJar.patch]. I have
tested it manually on my project and it works.
was:
Shading test JARs using the {{shadeTestJar}} configuration option yields an
empty test JAR. This has been noticed by others, see for example Steve K's
answer [on
StackOverflow|https://stackoverflow.com/questions/5149130/how-can-i-configure-the-maven-shade-plugin-to-include-test-code-in-my-jar/49617516#49617516],
but people have reverted to other hacks and workarounds to overcome this (e.g.
use a different plugin).
Scenario:
# Create modules {{api}}, {{impl}} and a module {{uber}} which has as sole
purpose to make an uber JAR for the combination of the first two modules.
{{uber}} itself has no sources.
# Both modules have both {{jar}} and {{test-jar}} artifacts.
# Configure the {{maven-shade-plugin}} in the {{uber}} module with the
configuration option {{shadeTestJar}} set to {{true}}.
Expected:
# Content of {{uber.jar}} is the aggregate content of {{api.jar}} and
{{impl.jar}}.
# Content of {{uber-tests.jar}} is the aggregate content of {{api-tests.jar}}
and {{impl-tests.jar}}.
Actual:
# Content of {{uber.jar}} is as expected.
# {{uber-tests.jar}} is empty.
Root cause:
* The implementation of the {{shadeTestJar}} feature in {{ShaderMojo}} is
buggy and incomplete.
* The call to {{processArtifactSelectors}} on line 425 doesn't pass the
{{testArtifacts}}, so they are never correctly filled in.
* The implementation of {{processArtifactSelectors}} doesn't deal with test
JARs at all and has to be extended to support them.
* The "if" statement on line 452 incorrectly treats a test JAR as sources.
This whole feature looks like it was done in a hurry as a sloppy copy-paste
job, and in 5 years nobody took the time to report or fix it. Amazing. You can
find my proposed fix in attachment: [^shadeTestJar.patch]. I have tested it
manually on my project and it works.
> Shaded test JARs are always empty
> -
>
> Key: MSHADE-284
> URL: https://issues.apache.org/jira/browse/MSHADE-284
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: Peter De Maeyer
>Priority: Major
> Attachments: shadeTestJar.patch
>
>
> Shading test JARs using the {{shadeTestJar}} configuration option yields an
> empty test JAR. This has been noticed by others, see for example Steve K's
> answer [on
> StackOverflow|https://stackoverflow.com/questions/5149130/how-can-i-configure-the-maven-shade-plugin-to-include-test-code-in-my-jar/49617516#49617516],
> but people have reverted to other hacks and workarounds to overcome this
> (e.g. use a different plugin).
> Scenario:
> # Create modules {{api}}, {{impl}} and a module {{uber}} which has as sole
> purpose to make an uber JAR for the combination of the first two modules.
> {{uber}} itself has no sources.
> # Both modules have both {{jar}} and {{test-jar}} artifacts.
> # Configure the {{maven-shade-plugin}}
[jira] [Updated] (MSHADE-284) Shaded test JARs are always empty
[
https://issues.apache.org/jira/browse/MSHADE-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter De Maeyer updated MSHADE-284:
---
Description:
Shading test JARs using the {{shadeTestJar}} configuration option yields an
empty test JAR. This has been noticed by others, see for example Steve K's
answer [on
StackOverflow|https://stackoverflow.com/questions/5149130/how-can-i-configure-the-maven-shade-plugin-to-include-test-code-in-my-jar/49617516#49617516],
but people have reverted to other hacks and workarounds to overcome this (e.g.
use a different plugin).
Scenario:
# Create modules {{api}}, {{impl}} and a module {{uber}} which has as sole
purpose to make an uber JAR for the combination of the first two modules.
{{uber}} itself has no sources.
# Both modules have both {{jar}} and {{test-jar}} artifacts.
# Configure the {{maven-shade-plugin}} in the {{uber}} module with the
configuration option {{shadeTestJar}} set to {{true}}.
Expected:
# Content of {{uber.jar}} is the aggregate content of {{api.jar}} and
{{impl.jar}}.
# Content of {{uber-tests.jar}} is the aggregate content of {{api-tests.jar}}
and {{impl-tests.jar}}.
Actual:
# Content of {{uber.jar}} is as expected.
# {{uber-tests.jar}} is empty.
Root cause:
* The implementation of the {{shadeTestJar}} feature in {{ShaderMojo}} is
buggy and incomplete.
* The call to {{processArtifactSelectors}} on line 425 doesn't pass the
{{testArtifacts}}, so they are never correctly filled in.
* The implementation of {{processArtifactSelectors}} doesn't deal with test
JARs at all and has to be extended to support them.
* The "if" statement on line 452 incorrectly treats a test JAR as sources.
This whole feature looks like it was done in a hurry as a sloppy copy-paste
job, and in 5 years nobody took the time to report or fix it. Amazing. Anyway,
you can find my proposed fix in attachment: [^shadeTestJar.patch]. I have
tested it manually on my project and it works.
was:
Shading test JARs using the {{shadeTestJar}} configuration option yields an
empty test JAR. This has been noticed by others, see for example Steve K's
answer [on
StackOverflow|https://stackoverflow.com/questions/5149130/how-can-i-configure-the-maven-shade-plugin-to-include-test-code-in-my-jar/49617516#49617516],
but people have reverted to other hacks and workarounds to overcome this (e.g.
use a different plugin).
Scenario:
# Create modules {{api}}, {{impl}} and a module {{uber}} which has as sole
purpose to make an uber JAR for the combination of the first two modules.
{{uber}} itself has no sources.
# Both modules have both {{jar}} and {{test-jar}} artifacts.
# Configure the {{maven-shade-plugin}} in the {{uber}} module with the
configuration option {{shadeTestJar}} set to {{true}}.
Expected:
# Content of {{uber.jar}} is the aggregate content of {{api.jar}} and
{{impl.jar}}.
# Content of {{uber-tests.jar}} is the aggregate content of {{api-tests.jar}}
and {{impl-tests.jar}}.
Actual:
# Content of {{uber.jar}} is as expected.
# {{uber-tests.jar}} is empty.
Root cause:
* The implementation of the {{shadeTestJar}} feature in {{ShaderMojo}} is
buggy and incomplete.
* The call to {{processArtifactSelectors}} on line 425 doesn't pass the
{{testArtifacts}}, so they are never correctly filled in.
* The implementation of {{processArtifactSelectors}} doesn't deal with test
JARs at all and has to be extended to support them.
* The "if" statement on line 452 incorrectly treats a test JAR as sources.
This whole feature looks like it was done in a hurry as a sloppy copy-paste
job, and in 5 years nobody took the time to report or fix it. Amazing. Anyway;
you can find my proposed fix in attachment: [^shadeTestJar.patch]. I have
tested it manually on my project and it works.
> Shaded test JARs are always empty
> -
>
> Key: MSHADE-284
> URL: https://issues.apache.org/jira/browse/MSHADE-284
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: Peter De Maeyer
>Priority: Major
> Attachments: shadeTestJar.patch
>
>
> Shading test JARs using the {{shadeTestJar}} configuration option yields an
> empty test JAR. This has been noticed by others, see for example Steve K's
> answer [on
> StackOverflow|https://stackoverflow.com/questions/5149130/how-can-i-configure-the-maven-shade-plugin-to-include-test-code-in-my-jar/49617516#49617516],
> but people have reverted to other hacks and workarounds to overcome this
> (e.g. use a different plugin).
> Scenario:
> # Create modules {{api}}, {{impl}} and a module {{uber}} which has as sole
> purpose to make an uber JAR for the combination of the first two modules.
> {{uber}} itself has no sources.
> # Both modules have both {{jar}} and {{test-jar}} artifacts.
> # Configure the
[jira] [Updated] (MSHADE-284) shadeTestJar doesn't work - shaded test JARs are always empty
[
https://issues.apache.org/jira/browse/MSHADE-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter De Maeyer updated MSHADE-284:
---
Summary: shadeTestJar doesn't work - shaded test JARs are always empty
(was: Shaded test JARs using shadeTestJar are always empty)
> shadeTestJar doesn't work - shaded test JARs are always empty
> -
>
> Key: MSHADE-284
> URL: https://issues.apache.org/jira/browse/MSHADE-284
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: Peter De Maeyer
>Priority: Major
> Attachments: shadeTestJar.patch
>
>
> Shading test JARs using the {{shadeTestJar}} configuration option yields an
> empty test JAR. This has been noticed by others, see for example Steve K's
> answer [on
> StackOverflow|https://stackoverflow.com/questions/5149130/how-can-i-configure-the-maven-shade-plugin-to-include-test-code-in-my-jar/49617516#49617516],
> but people have reverted to other hacks and workarounds to overcome this
> (e.g. use a different plugin).
> Scenario:
> # Create modules {{api}}, {{impl}} and a module {{uber}} which has as sole
> purpose to make an uber JAR for the combination of the first two modules.
> {{uber}} itself has no sources.
> # Both modules have both {{jar}} and {{test-jar}} artifacts.
> # Configure the {{maven-shade-plugin}} in the {{uber}} module with the
> configuration option {{shadeTestJar}} set to {{true}}.
> Expected:
> # Content of {{uber.jar}} is the aggregate content of {{api.jar}} and
> {{impl.jar}}.
> # Content of {{uber-tests.jar}} is the aggregate content of
> {{api-tests.jar}} and {{impl-tests.jar}}.
> Actual:
> # Content of {{uber.jar}} is as expected.
> # {{uber-tests.jar}} is empty.
> Root cause:
> * The implementation of the {{shadeTestJar}} feature in {{ShaderMojo}} is
> buggy and incomplete.
> * The call to {{processArtifactSelectors}} on line 425 doesn't pass the
> {{testArtifacts}}, so they are never correctly filled in.
> * The implementation of {{processArtifactSelectors}} doesn't deal with test
> JARs at all and has to be extended to support them.
> * The "if" statement on line 452 incorrectly treats a test JAR as sources.
> This whole feature looks like it was done in a hurry as a sloppy copy-paste
> job, and in 5 years nobody took the time to report or fix it. Amazing. You
> can find my proposed fix in attachment: [^shadeTestJar.patch]. I have tested
> it manually on my project and it works.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MSHADE-284) Shaded test JARs are always empty
[
https://issues.apache.org/jira/browse/MSHADE-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter De Maeyer updated MSHADE-284:
---
Summary: Shaded test JARs are always empty (was: shadeTestJar doesn't work
- shaded test JARs are always empty)
> Shaded test JARs are always empty
> -
>
> Key: MSHADE-284
> URL: https://issues.apache.org/jira/browse/MSHADE-284
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: Peter De Maeyer
>Priority: Major
> Attachments: shadeTestJar.patch
>
>
> Shading test JARs using the {{shadeTestJar}} configuration option yields an
> empty test JAR. This has been noticed by others, see for example Steve K's
> answer [on
> StackOverflow|https://stackoverflow.com/questions/5149130/how-can-i-configure-the-maven-shade-plugin-to-include-test-code-in-my-jar/49617516#49617516],
> but people have reverted to other hacks and workarounds to overcome this
> (e.g. use a different plugin).
> Scenario:
> # Create modules {{api}}, {{impl}} and a module {{uber}} which has as sole
> purpose to make an uber JAR for the combination of the first two modules.
> {{uber}} itself has no sources.
> # Both modules have both {{jar}} and {{test-jar}} artifacts.
> # Configure the {{maven-shade-plugin}} in the {{uber}} module with the
> configuration option {{shadeTestJar}} set to {{true}}.
> Expected:
> # Content of {{uber.jar}} is the aggregate content of {{api.jar}} and
> {{impl.jar}}.
> # Content of {{uber-tests.jar}} is the aggregate content of
> {{api-tests.jar}} and {{impl-tests.jar}}.
> Actual:
> # Content of {{uber.jar}} is as expected.
> # {{uber-tests.jar}} is empty.
> Root cause:
> * The implementation of the {{shadeTestJar}} feature in {{ShaderMojo}} is
> buggy and incomplete.
> * The call to {{processArtifactSelectors}} on line 425 doesn't pass the
> {{testArtifacts}}, so they are never correctly filled in.
> * The implementation of {{processArtifactSelectors}} doesn't deal with test
> JARs at all and has to be extended to support them.
> * The "if" statement on line 452 incorrectly treats a test JAR as sources.
> This whole feature looks like it was done in a hurry as a sloppy copy-paste
> job, and in 5 years nobody took the time to report or fix it. Amazing. You
> can find my proposed fix in attachment: [^shadeTestJar.patch]. I have tested
> it manually on my project and it works.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MSHADE-285) It should be possible to shade test sources as a JAR
[
https://issues.apache.org/jira/browse/MSHADE-285?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16423100#comment-16423100
]
Peter De Maeyer commented on MSHADE-285:
Feel free to assign back to me, I'd be happy to fix this myself if you agree
with the solution.
> It should be possible to shade test sources as a JAR
>
>
> Key: MSHADE-285
> URL: https://issues.apache.org/jira/browse/MSHADE-285
> Project: Maven Shade Plugin
> Issue Type: Improvement
>Affects Versions: 3.1.0
>Reporter: Peter De Maeyer
>Priority: Major
>
> The configuration option {{createSourcesJar}} allows to shade sources JAR,
> but there is no such option for test sources.
> I see two solutions:
> # Extend the semantics of {{createSourcesJar}} such that, when combined with
> {{shadeTestJar}}, is also creates the _test_ sources JAR.
> # Introduce a new configuration option {{createTestSourcesJar}}, similar to
> {{createSourcesJar}}.
> The former is very intuitive, but it lacks the flexibility to create a JAR,
> sources JAR, test JAR, but _no_ test sources JAR. The latter allows more
> flexibility.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MSHADE-284) Shaded test JARs using shadeTestJar are always empty
[
https://issues.apache.org/jira/browse/MSHADE-284?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16423099#comment-16423099
]
Peter De Maeyer commented on MSHADE-284:
While fixing this issue, I found MSHADE-285.
> Shaded test JARs using shadeTestJar are always empty
>
>
> Key: MSHADE-284
> URL: https://issues.apache.org/jira/browse/MSHADE-284
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: Peter De Maeyer
>Priority: Major
> Attachments: shadeTestJar.patch
>
>
> Shading test JARs using the {{shadeTestJar}} configuration option yields an
> empty test JAR. This has been noticed by others, see for example Steve K's
> answer [on
> StackOverflow|https://stackoverflow.com/questions/5149130/how-can-i-configure-the-maven-shade-plugin-to-include-test-code-in-my-jar/49617516#49617516],
> but people have reverted to other hacks and workarounds to overcome this
> (e.g. use a different plugin).
> Scenario:
> # Create modules {{api}}, {{impl}} and a module {{uber}} which has as sole
> purpose to make an uber JAR for the combination of the first two modules.
> {{uber}} itself has no sources.
> # Both modules have both {{jar}} and {{test-jar}} artifacts.
> # Configure the {{maven-shade-plugin}} in the {{uber}} module with the
> configuration option {{shadeTestJar}} set to {{true}}.
> Expected:
> # Content of {{uber.jar}} is the aggregate content of {{api.jar}} and
> {{impl.jar}}.
> # Content of {{uber-tests.jar}} is the aggregate content of
> {{api-tests.jar}} and {{impl-tests.jar}}.
> Actual:
> # Content of {{uber.jar}} is as expected.
> # {{uber-tests.jar}} is empty.
> Root cause:
> * The implementation of the {{shadeTestJar}} feature in {{ShaderMojo}} is
> buggy and incomplete.
> * The call to {{processArtifactSelectors}} on line 425 doesn't pass the
> {{testArtifacts}}, so they are never correctly filled in.
> * The implementation of {{processArtifactSelectors}} doesn't deal with test
> JARs at all and has to be extended to support them.
> * The "if" statement on line 452 incorrectly treats a test JAR as sources.
> This whole feature looks like it was done in a hurry as a sloppy copy-paste
> job, and in 5 years nobody took the time to report or fix it. Amazing. You
> can find my proposed fix in attachment: [^shadeTestJar.patch]. I have tested
> it manually on my project and it works.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Created] (MSHADE-285) It should be possible to shade test sources as a JAR
Peter De Maeyer created MSHADE-285:
--
Summary: It should be possible to shade test sources as a JAR
Key: MSHADE-285
URL: https://issues.apache.org/jira/browse/MSHADE-285
Project: Maven Shade Plugin
Issue Type: Improvement
Affects Versions: 3.1.0
Reporter: Peter De Maeyer
The configuration option {{createSourcesJar}} allows to shade sources JAR, but
there is no such option for test sources.
I see two solutions:
# Extend the semantics of {{createSourcesJar}} such that, when combined with
{{shadeTestJar}}, is also creates the _test_ sources JAR.
# Introduce a new configuration option {{createTestSourcesJar}}, similar to
{{createSourcesJar}}.
The former is very intuitive, but it lacks the flexibility to create a JAR,
sources JAR, test JAR, but _no_ test sources JAR. The latter allows more
flexibility.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MSHADE-284) Shaded test JARs using shadeTestJar are always empty
[
https://issues.apache.org/jira/browse/MSHADE-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter De Maeyer updated MSHADE-284:
---
Description:
Shading test JARs using the {{shadeTestJar}} configuration option yields an
empty test JAR. This has been noticed by others, see for example Steve K's
answer [on
StackOverflow|https://stackoverflow.com/questions/5149130/how-can-i-configure-the-maven-shade-plugin-to-include-test-code-in-my-jar/49617516#49617516],
but people have reverted to other hacks and workarounds to overcome this (e.g.
use a different plugin).
Scenario:
# Create modules {{api}}, {{impl}} and a module {{uber}} which has as sole
purpose to make an uber JAR for the combination of the first two modules.
{{uber}} itself has no sources.
# Both modules have both {{jar}} and {{test-jar}} artifacts.
# Configure the {{maven-shade-plugin}} in the {{uber}} module with the
configuration option {{shadeTestJar}} set to {{true}}.
Expected:
# Content of {{uber.jar}} is the aggregate content of {{api.jar}} and
{{impl.jar}}.
# Content of {{uber-tests.jar}} is the aggregate content of {{api-tests.jar}}
and {{impl-tests.jar}}.
Actual:
# Content of {{uber.jar}} is as expected.
# {{uber-tests.jar}} is empty.
Root cause:
* The implementation of the {{shadeTestJar}} feature in {{ShaderMojo}} is
buggy and incomplete.
* The call to {{processArtifactSelectors}} on line 425 doesn't pass the
{{testArtifacts}}, so they are never correctly filled in.
* The implementation of {{processArtifactSelectors}} doesn't deal with test
JARs at all and has to be extended to support them.
* The "if" statement on line 452 incorrectly treats a test JAR as sources.
This whole feature looks like it was done in a hurry as a sloppy copy-paste
job, and in 5 years nobody took the time to report or fix it. Amazing. You can
find my proposed fix in attachment: [^shadeTestJar.patch]. I have tested it
manually on my project and it works.
was:
Shading test JARs using the {{shadeTestJar}} configuration option yields an
empty test JAR. This has been noticed by others, see for example Steve K's
answer [on
StackOverflow|https://stackoverflow.com/questions/5149130/how-can-i-configure-the-maven-shade-plugin-to-include-test-code-in-my-jar/49617516#49617516],
but people have reverted to other hacks and workarounds to overcome this (e.g.
use a different plugin).
Scenario:
# Create modules {{api}}, {{impl}} and a module {{uber}} which has as sole
purpose to make an uber JAR for the combination of the first two modules.
{{uber}} itself has no sources.
# Both modules have both {{jar}} and {{test-jar}} artifacts.
# Configure the {{maven-shade-plugin}} in the {{uber}} module with the
configuration option {{shadeTestJar}} set to {{true}}.
Expected:
# Content of {{uber.jar}} is the aggregate content of {{api.jar}} and
{{impl.jar}}.
# Content of {{uber-tests.jar}} is the aggregate content of {{api-tests.jar}}
and {{impl-tests.jar}}.
Actual:
# Content of {{uber.jar}} is as expected.
# {{uber-tests.jar}} is empty.
Root cause:
* The implementation of the {{shadeTestJar}} feature in {{ShaderMojo}} is
buggy and incomplete.
* The call to {{processArtifactSelectors}} on line 425 doesn't pass the
{{testArtifacts}}, so they are never correctly filled in.
* The implementation of {{processArtifactSelectors}} doesn't deal with test
JARs at all and has to be extended to support them.
* The "if" statement on line 452 incorrectly treats a test JAR as sources.
This whole feature looks like it was done in a hurry as a sloppy copy-paste
job, and in 5 years nobody took the time to report or fix it. Amazing. Oh well,
let me be the one that fixes it then. You can find my fix in attachment:
[^shadeTestJar.patch].
> Shaded test JARs using shadeTestJar are always empty
>
>
> Key: MSHADE-284
> URL: https://issues.apache.org/jira/browse/MSHADE-284
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: Peter De Maeyer
>Priority: Major
> Attachments: shadeTestJar.patch
>
>
> Shading test JARs using the {{shadeTestJar}} configuration option yields an
> empty test JAR. This has been noticed by others, see for example Steve K's
> answer [on
> StackOverflow|https://stackoverflow.com/questions/5149130/how-can-i-configure-the-maven-shade-plugin-to-include-test-code-in-my-jar/49617516#49617516],
> but people have reverted to other hacks and workarounds to overcome this
> (e.g. use a different plugin).
> Scenario:
> # Create modules {{api}}, {{impl}} and a module {{uber}} which has as sole
> purpose to make an uber JAR for the combination of the first two modules.
> {{uber}} itself has no sources.
> # Both modules have both {{jar}} and {{test-jar}} artifacts.
> # Configure the
[jira] [Created] (MSHADE-284) Shading test JARs using shadeTestJar does not work
Peter De Maeyer created MSHADE-284:
--
Summary: Shading test JARs using shadeTestJar does not work
Key: MSHADE-284
URL: https://issues.apache.org/jira/browse/MSHADE-284
Project: Maven Shade Plugin
Issue Type: Bug
Affects Versions: 3.1.0
Reporter: Peter De Maeyer
Attachments: shadeTestJar.patch
Shading test JARs using the {{shadeTestJar}} configuration option yields an
empty test JAR. This has been noticed by others, see for example Steve K's
answer [on
StackOverflow|https://stackoverflow.com/questions/5149130/how-can-i-configure-the-maven-shade-plugin-to-include-test-code-in-my-jar/49617516#49617516],
but people have reverted to other hacks and workarounds to overcome this (e.g.
use a different plugin).
Scenario:
# Create modules {{api}}, {{impl}} and a module {{uber}} which has as sole
purpose to make an uber JAR for the combination of the first two modules.
{{uber}} itself has no sources.
# Both modules have both {{jar}} and {{test-jar}} artifacts.
# Configure the {{maven-shade-plugin}} in the {{uber}} module with the
configuration option {{shadeTestJar}} set to {{true}}.
Expected:
# Content of {{uber.jar}} is the aggregate content of {{api.jar}} and
{{impl.jar}}.
# Content of {{uber-tests.jar}} is the aggregate content of {{api-tests.jar}}
and {{impl-tests.jar}}.
Actual:
# Content of {{uber.jar}} is as expected.
# {{uber-tests.jar}} is empty.
Root cause:
* The implementation of the {{shadeTestJar}} feature in {{ShaderMojo}} is
buggy and incomplete.
* The call to {{processArtifactSelectors}} on line 425 doesn't pass the
{{testArtifacts}}, so they are never correctly filled in.
* The implementation of {{processArtifactSelectors}} doesn't deal with test
JARs at all and has to be extended to support them.
* The "if" statement on line 452 incorrectly treats a test JAR as sources.
This whole feature looks like it was done in a hurry as a sloppy copy-paste
job, and in 5 years nobody took the time to report or fix it. Amazing. Oh well,
let me be the one that fixes it then. You can find my fix in attachment:
[^shadeTestJar.patch].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MSHADE-284) Shaded test JARs using shadeTestJar are always empty
[
https://issues.apache.org/jira/browse/MSHADE-284?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Peter De Maeyer updated MSHADE-284:
---
Summary: Shaded test JARs using shadeTestJar are always empty (was:
Shading test JARs using shadeTestJar does not work)
> Shaded test JARs using shadeTestJar are always empty
>
>
> Key: MSHADE-284
> URL: https://issues.apache.org/jira/browse/MSHADE-284
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.1.0
>Reporter: Peter De Maeyer
>Priority: Major
> Attachments: shadeTestJar.patch
>
>
> Shading test JARs using the {{shadeTestJar}} configuration option yields an
> empty test JAR. This has been noticed by others, see for example Steve K's
> answer [on
> StackOverflow|https://stackoverflow.com/questions/5149130/how-can-i-configure-the-maven-shade-plugin-to-include-test-code-in-my-jar/49617516#49617516],
> but people have reverted to other hacks and workarounds to overcome this
> (e.g. use a different plugin).
> Scenario:
> # Create modules {{api}}, {{impl}} and a module {{uber}} which has as sole
> purpose to make an uber JAR for the combination of the first two modules.
> {{uber}} itself has no sources.
> # Both modules have both {{jar}} and {{test-jar}} artifacts.
> # Configure the {{maven-shade-plugin}} in the {{uber}} module with the
> configuration option {{shadeTestJar}} set to {{true}}.
> Expected:
> # Content of {{uber.jar}} is the aggregate content of {{api.jar}} and
> {{impl.jar}}.
> # Content of {{uber-tests.jar}} is the aggregate content of
> {{api-tests.jar}} and {{impl-tests.jar}}.
> Actual:
> # Content of {{uber.jar}} is as expected.
> # {{uber-tests.jar}} is empty.
> Root cause:
> * The implementation of the {{shadeTestJar}} feature in {{ShaderMojo}} is
> buggy and incomplete.
> * The call to {{processArtifactSelectors}} on line 425 doesn't pass the
> {{testArtifacts}}, so they are never correctly filled in.
> * The implementation of {{processArtifactSelectors}} doesn't deal with test
> JARs at all and has to be extended to support them.
> * The "if" statement on line 452 incorrectly treats a test JAR as sources.
> This whole feature looks like it was done in a hurry as a sloppy copy-paste
> job, and in 5 years nobody took the time to report or fix it. Amazing. Oh
> well, let me be the one that fixes it then. You can find my fix in
> attachment: [^shadeTestJar.patch].
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MARCHETYPES-56) finish maven-archetype-profiles
[ https://issues.apache.org/jira/browse/MARCHETYPES-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16423056#comment-16423056 ] Hudson commented on MARCHETYPES-56: --- Build failed in Jenkins: Maven TLP » maven-archetypes » master #6 See https://builds.apache.org/job/maven-box/job/maven-archetypes/job/master/6/ > finish maven-archetype-profiles > --- > > Key: MARCHETYPES-56 > URL: https://issues.apache.org/jira/browse/MARCHETYPES-56 > Project: Maven Archetype Bundles > Issue Type: Task >Reporter: Hervé Boutemy >Priority: Major > > this is a WIP that was never finished: there is still no profile in generated > pom.xml... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MARCHETYPES-56) finish maven-archetype-profiles
[ https://issues.apache.org/jira/browse/MARCHETYPES-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy updated MARCHETYPES-56: - Fix Version/s: (was: 1.3) > finish maven-archetype-profiles > --- > > Key: MARCHETYPES-56 > URL: https://issues.apache.org/jira/browse/MARCHETYPES-56 > Project: Maven Archetype Bundles > Issue Type: Task >Reporter: Hervé Boutemy >Priority: Major > > this is a WIP that was never finished: there is still no profile in generated > pom.xml... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MARCHETYPES-56) finish maven-archetype-profiles
[ https://issues.apache.org/jira/browse/MARCHETYPES-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16423053#comment-16423053 ] Hervé Boutemy commented on MARCHETYPES-56: -- this will be for a next release... > finish maven-archetype-profiles > --- > > Key: MARCHETYPES-56 > URL: https://issues.apache.org/jira/browse/MARCHETYPES-56 > Project: Maven Archetype Bundles > Issue Type: Task >Reporter: Hervé Boutemy >Priority: Major > > this is a WIP that was never finished: there is still no profile in generated > pom.xml... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCM-763) Password masking for svnexe does not handle all cases
[ https://issues.apache.org/jira/browse/SCM-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated SCM-763: --- Summary: Password masking for svnexe does not handle all cases (was: Password masking on linux does not work) > Password masking for svnexe does not handle all cases > - > > Key: SCM-763 > URL: https://issues.apache.org/jira/browse/SCM-763 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-svn >Affects Versions: 1.9 > Environment: Jenkins 1.502 on a SLES11 >Reporter: Tobias Kalmes >Priority: Major > Fix For: 1.9.6 > > > Passwords are not masked in the log output on Linux machines. The masking > works as intended on Windows machines. On linux machines tho the password is > printed in clear text. This seems to be a problem due to the additional > single quotes that are added around the parameters on linux machines. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Assigned] (SCM-763) Password masking for svnexe does not handle all cases
[ https://issues.apache.org/jira/browse/SCM-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov reassigned SCM-763: -- Assignee: Michael Osipov > Password masking for svnexe does not handle all cases > - > > Key: SCM-763 > URL: https://issues.apache.org/jira/browse/SCM-763 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-svn >Affects Versions: 1.9 > Environment: Jenkins 1.502 on a SLES11 >Reporter: Tobias Kalmes >Assignee: Michael Osipov >Priority: Major > Fix For: 1.9.6 > > > Passwords are not masked in the log output on Linux machines. The masking > works as intended on Windows machines. On linux machines tho the password is > printed in clear text. This seems to be a problem due to the additional > single quotes that are added around the parameters on linux machines. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (SCM-763) Password masking for svnexe does not handle all cases
[ https://issues.apache.org/jira/browse/SCM-763?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated SCM-763: --- Fix Version/s: 1.9.6 > Password masking for svnexe does not handle all cases > - > > Key: SCM-763 > URL: https://issues.apache.org/jira/browse/SCM-763 > Project: Maven SCM > Issue Type: Bug > Components: maven-scm-provider-svn >Affects Versions: 1.9 > Environment: Jenkins 1.502 on a SLES11 >Reporter: Tobias Kalmes >Assignee: Michael Osipov >Priority: Major > Fix For: 1.9.6 > > > Passwords are not masked in the log output on Linux machines. The masking > works as intended on Windows machines. On linux machines tho the password is > printed in clear text. This seems to be a problem due to the additional > single quotes that are added around the parameters on linux machines. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MNG-6388) Error Fetching Artifacts: "[B cannot be cast to java.lang.String"
[
https://issues.apache.org/jira/browse/MNG-6388?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Mike Kelly updated MNG-6388:
Component/s: Artifacts and Repositories
> Error Fetching Artifacts: "[B cannot be cast to java.lang.String"
> -
>
> Key: MNG-6388
> URL: https://issues.apache.org/jira/browse/MNG-6388
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 3.5.3
> Environment: $ docker run --rm -it maven:3-jdk-8 mvn --version
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
> 2018-02-24T19:49:05Z)
> Maven home: /usr/share/maven
> Java version: 1.8.0_162, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
> Default locale: en, platform encoding: UTF-8
> OS name: "linux", version: "3.10.0-693.21.1.el7.x86_64", arch: "amd64",
> family: "unix"
>
> $ mvn -version
> Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
> 2018-02-24T14:49:05-05:00)
> Maven home: /opt/local/share/java/maven3
> Java version: 1.8.0_161, vendor: Oracle Corporation
> Java home:
> /Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home/jre
> Default locale: en_US, platform encoding: UTF-8
> OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"
>Reporter: Mike Kelly
>Priority: Major
>
> When using Maven 3.5.3 with Artifactory 5.10.0 configured as a "*" mirror,
> downloads & uploads fail with errors like:
> {noformat}
> [ERROR] Failed to execute goal on project ccc-persistence: Could not resolve
> dependencies for project REDACTED:REDACTED:jar:3.47.0-SNAPSHOT: Failed to
> collect dependencies at org.flywaydb:flyway-core:jar:3.2.1: Failed to read
> artifact descriptor for org.flywaydb:flyway-core:jar:3.2.1: Could not
> transfer artifact org.flywaydb:flyway-core:pom:3.2.1 from/to artifactory
> (https://artifactory.REDACTED.com/artifactory/all): [B cannot be cast to
> java.lang.String -> [Help 1]{noformat}
> I've seen this issue both with the official Docker container, and with Maven
> 3.5.3 from MacPorts; in both cases, downgrading back down to 3.5.2 resolved
> the issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MARCHETYPES-12) When site archetypes (16,17) are built, the index file omits much of the generated output
[ https://issues.apache.org/jira/browse/MARCHETYPES-12?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed MARCHETYPES-12. Resolution: Fixed Assignee: Hervé Boutemy Fix Version/s: 1.3 > When site archetypes (16,17) are built, the index file omits much of the > generated output > - > > Key: MARCHETYPES-12 > URL: https://issues.apache.org/jira/browse/MARCHETYPES-12 > Project: Maven Archetype Bundles > Issue Type: Bug > Components: Maven Site Archetype >Reporter: Sebb >Assignee: Hervé Boutemy >Priority: Major > Fix For: 1.3 > > > Use mvn archetype:generate to build site (type 16) > Run mvn site. > The site home page that is created in target/site/index.html does not include > any of the generated reports. > Similarly for site type 17. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MARCHETYPES-10) Non-ascii characters not handled correctly in French faq.html (generated from faq.fml)
[ https://issues.apache.org/jira/browse/MARCHETYPES-10?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed MARCHETYPES-10. Resolution: Cannot Reproduce this issue is quite old, could be caused by many old issues on encoding that have been fixed now: I can't reproduce nowadays closing: please reopen against the future archetypes version 1.3 that will be released soon > Non-ascii characters not handled correctly in French faq.html (generated from > faq.fml) > -- > > Key: MARCHETYPES-10 > URL: https://issues.apache.org/jira/browse/MARCHETYPES-10 > Project: Maven Archetype Bundles > Issue Type: Bug > Components: Maven Site Archetype >Reporter: Sebb >Priority: Major > > Use mvn archetype:generate to create a site type 17. > Most of the French pages are generated with the correct accents, but faq.html > has "?" instead of "u-grave". > Dunno whether this is a configuration problem or a plugin problem. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] khmarbaise closed pull request #1: Update ASM to latest version
khmarbaise closed pull request #1: Update ASM to latest version
URL: https://github.com/apache/maven-shade-plugin/pull/1
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 is a foreign pull request (from a fork), the diff is supplied
below (as it won't show otherwise due to GitHub magic):
diff --git a/pom.xml b/pom.xml
index d09249d..f3df096 100644
--- a/pom.xml
+++ b/pom.xml
@@ -67,7 +67,7 @@
3.0
${project.version}
-6.0_BETA
+6.1.1
This is an automated message from the Apache Git Service.
To respond to the message, please log on GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
us...@infra.apache.org
With regards,
Apache Git Services
[GitHub] khmarbaise commented on issue #1: Update ASM to latest version
khmarbaise commented on issue #1: Update ASM to latest version URL: https://github.com/apache/maven-shade-plugin/pull/1#issuecomment-378003526 VOTE for new release of maven-shade-plugin 3.1.1 https://www.mail-archive.com/dev@maven.apache.org/msg116597.html has started. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (MSHADE-278) Print out the jar responsible for exceptions like "Error creating shaded jar: invalid LOC header (bad signature)"
[
https://issues.apache.org/jira/browse/MSHADE-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16422884#comment-16422884
]
Hudson commented on MSHADE-278:
---
Build succeeded in Jenkins: Maven TLP » maven-shade-plugin » master #16
See
https://builds.apache.org/job/maven-box/job/maven-shade-plugin/job/master/16/
> Print out the jar responsible for exceptions like "Error creating shaded jar:
> invalid LOC header (bad signature)"
> -
>
> Key: MSHADE-278
> URL: https://issues.apache.org/jira/browse/MSHADE-278
> Project: Maven Shade Plugin
> Issue Type: Improvement
>Affects Versions: 3.1.0
> Environment: Apache Maven 3.5.3
> (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T12:49:05-07:00)
> Maven home: C:\Java\apache-maven-3.5.3\bin\..
> Java version: 1.8.0_162, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_162\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>Reporter: Gary Gregory
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.1.1
>
>
> Print out the jar responsible for exceptions like "Error creating shaded jar:
> invalid LOC header (bad signature)". Then I can delete it and force maven to
> download it again. Otherwise I have no idea which of >100 jars is bad.
> {noformat}
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 40.978 s
> [INFO] Finished at: 2018-03-31T07:59:29-06:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-shade-plugin:3.1.0:shade (default) on project
> http-monitor: Error creating shaded jar: invalid LOC header (bad signature)
> -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-shade-plugin:3.1.0:shade (default) on
> project http-monitor: Error creating shaded jar: invalid LOC header (bad
> signature)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:498)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:289)
> at 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: org.apache.maven.plugin.MojoExecutionException: Error creating
> shaded jar: invalid LOC header (bad signature)
> at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute
> (ShadeMojo.java:546)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
>
[jira] [Closed] (MSHADE-277) Identify issue related IT failure mini-jar-malformed-dependencies/pom.xml
[
https://issues.apache.org/jira/browse/MSHADE-277?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MSHADE-277.
--
Resolution: Done
Assignee: Karl Heinz Marbaise
Fixed in relationship with MSHADE-275
> Identify issue related IT failure mini-jar-malformed-dependencies/pom.xml
> -
>
> Key: MSHADE-277
> URL: https://issues.apache.org/jira/browse/MSHADE-277
> Project: Maven Shade Plugin
> Issue Type: Improvement
>Affects Versions: 3.1.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Blocker
> Fix For: 3.1.1
>
>
> Currently the builds on Jenkins fail with the following IT':
> {code}
> [linux-jdk8] [WARNING] The following builds failed:
> [linux-jdk8] [WARNING] * mini-jar-malformed-dependencies/pom.xml
> [linux-jdk8] [INFO] -
> [linux-jdk8] [WARNING] Ignoring that 1 build failed.
> [linux-jdk8] [INFO] --
> {code}
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MSHADE-283) Add documentation information for GitHub
[ https://issues.apache.org/jira/browse/MSHADE-283?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MSHADE-283. -- Resolution: Done Done in [c96600138e9de525f390d970cd158add7bed7bb0|https://gitbox.apache.org/repos/asf?p=maven-shade-plugin.git;a=commitdiff;h=c96600138e9de525f390d970cd158add7bed7bb0] > Add documentation information for GitHub > > > Key: MSHADE-283 > URL: https://issues.apache.org/jira/browse/MSHADE-283 > Project: Maven Shade Plugin > Issue Type: Improvement >Affects Versions: 3.1.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.1.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MSHADE-278) Print out the jar responsible for exceptions like "Error creating shaded jar: invalid LOC header (bad signature)"
[
https://issues.apache.org/jira/browse/MSHADE-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MSHADE-278.
--
Resolution: Done
Done in
[61a8182cb69ab6a5b4277fb0ee704185c428915f|https://gitbox.apache.org/repos/asf?p=maven-shade-plugin.git;a=commitdiff;h=61a8182cb69ab6a5b4277fb0ee704185c428915f]
Thanks Gary.
> Print out the jar responsible for exceptions like "Error creating shaded jar:
> invalid LOC header (bad signature)"
> -
>
> Key: MSHADE-278
> URL: https://issues.apache.org/jira/browse/MSHADE-278
> Project: Maven Shade Plugin
> Issue Type: Improvement
>Affects Versions: 3.1.0
> Environment: Apache Maven 3.5.3
> (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T12:49:05-07:00)
> Maven home: C:\Java\apache-maven-3.5.3\bin\..
> Java version: 1.8.0_162, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_162\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>Reporter: Gary Gregory
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.1.1
>
>
> Print out the jar responsible for exceptions like "Error creating shaded jar:
> invalid LOC header (bad signature)". Then I can delete it and force maven to
> download it again. Otherwise I have no idea which of >100 jars is bad.
> {noformat}
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 40.978 s
> [INFO] Finished at: 2018-03-31T07:59:29-06:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-shade-plugin:3.1.0:shade (default) on project
> http-monitor: Error creating shaded jar: invalid LOC header (bad signature)
> -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-shade-plugin:3.1.0:shade (default) on
> project http-monitor: Error creating shaded jar: invalid LOC header (bad
> signature)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:498)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:289)
> at 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: org.apache.maven.plugin.MojoExecutionException: Error creating
> shaded jar: invalid LOC header (bad signature)
> at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute
> (ShadeMojo.java:546)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
>
[jira] [Updated] (MSHADE-278) Print out the jar responsible for exceptions like "Error creating shaded jar: invalid LOC header (bad signature)"
[
https://issues.apache.org/jira/browse/MSHADE-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MSHADE-278:
---
Priority: Minor (was: Major)
> Print out the jar responsible for exceptions like "Error creating shaded jar:
> invalid LOC header (bad signature)"
> -
>
> Key: MSHADE-278
> URL: https://issues.apache.org/jira/browse/MSHADE-278
> Project: Maven Shade Plugin
> Issue Type: Improvement
>Affects Versions: 3.1.0
> Environment: Apache Maven 3.5.3
> (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T12:49:05-07:00)
> Maven home: C:\Java\apache-maven-3.5.3\bin\..
> Java version: 1.8.0_162, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_162\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>Reporter: Gary Gregory
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.1.1
>
>
> Print out the jar responsible for exceptions like "Error creating shaded jar:
> invalid LOC header (bad signature)". Then I can delete it and force maven to
> download it again. Otherwise I have no idea which of >100 jars is bad.
> {noformat}
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 40.978 s
> [INFO] Finished at: 2018-03-31T07:59:29-06:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-shade-plugin:3.1.0:shade (default) on project
> http-monitor: Error creating shaded jar: invalid LOC header (bad signature)
> -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-shade-plugin:3.1.0:shade (default) on
> project http-monitor: Error creating shaded jar: invalid LOC header (bad
> signature)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:498)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:289)
> at 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: org.apache.maven.plugin.MojoExecutionException: Error creating
> shaded jar: invalid LOC header (bad signature)
> at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute
> (ShadeMojo.java:546)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
>
[jira] [Commented] (MJMOD-8) NPE on create
[
https://issues.apache.org/jira/browse/MJMOD-8?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16422864#comment-16422864
]
Margaret Stephanie Leber commented on MJMOD-8:
--
Me too.
> NPE on create
> -
>
> Key: MJMOD-8
> URL: https://issues.apache.org/jira/browse/MJMOD-8
> Project: Maven JMod Plugin
> Issue Type: Bug
>Affects Versions: 3.0.0-alpha-2
> Environment: Apache Maven 3.5.0
> Maven home: /usr/share/maven
> Java version: 9-Ubuntu, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-9-openjdk-amd64
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "4.13.0-19-generic", arch: "amd64", family: "unix"
>Reporter: Victor Romero
>Priority: Blocker
>
> Trying to compile with latest snapshot version (as I saw another NPE issue
> for the latest released version here) gets a NPE.
> Steps to reproduce:
> git clone https://github.com/vromero/npe-on-alpha-2.git
> cd npe-on-alpha-2
> mvn clean install -X
> will return :
> {code:java}
> INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 2.144 s
> [INFO] Finished at: 2017-12-12T15:45:10-08:00
> [INFO] Final Memory: 17M/58M
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-jmod-plugin:3.0.0-alpha-2-SNAPSHOT:create
> (default-create) on project about-cli-distribution-jmod: Execution
> default-create of goal
> org.apache.maven.plugins:maven-jmod-plugin:3.0.0-alpha-2-SNAPSHOT:create
> failed.: NullPointerException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-jmod-plugin:3.0.0-alpha-2-SNAPSHOT:create
> (default-create) on project about-cli-distribution-jmod: Execution
> default-create of goal
> org.apache.maven.plugins:maven-jmod-plugin:3.0.0-alpha-2-SNAPSHOT:create
> failed.
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:51)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:309)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:194)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:107)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:993)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:345)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:191)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at jdk.internal.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:564)
> 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: org.apache.maven.plugin.PluginExecutionException: Execution
> default-create of goal
> org.apache.maven.plugins:maven-jmod-plugin:3.0.0-alpha-2-SNAPSHOT:create
> failed.
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:145)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:51)
> at
[jira] [Commented] (MSHADE-278) Print out the jar responsible for exceptions like "Error creating shaded jar: invalid LOC header (bad signature)"
[
https://issues.apache.org/jira/browse/MSHADE-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16422856#comment-16422856
]
Hudson commented on MSHADE-278:
---
Build succeeded in Jenkins: Maven TLP » maven-shade-plugin » MSHADE-278 #3
See
https://builds.apache.org/job/maven-box/job/maven-shade-plugin/job/MSHADE-278/3/
> Print out the jar responsible for exceptions like "Error creating shaded jar:
> invalid LOC header (bad signature)"
> -
>
> Key: MSHADE-278
> URL: https://issues.apache.org/jira/browse/MSHADE-278
> Project: Maven Shade Plugin
> Issue Type: Improvement
>Affects Versions: 3.1.0
> Environment: Apache Maven 3.5.3
> (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T12:49:05-07:00)
> Maven home: C:\Java\apache-maven-3.5.3\bin\..
> Java version: 1.8.0_162, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_162\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>Reporter: Gary Gregory
>Assignee: Karl Heinz Marbaise
>Priority: Major
> Fix For: 3.1.1
>
>
> Print out the jar responsible for exceptions like "Error creating shaded jar:
> invalid LOC header (bad signature)". Then I can delete it and force maven to
> download it again. Otherwise I have no idea which of >100 jars is bad.
> {noformat}
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 40.978 s
> [INFO] Finished at: 2018-03-31T07:59:29-06:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-shade-plugin:3.1.0:shade (default) on project
> http-monitor: Error creating shaded jar: invalid LOC header (bad signature)
> -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-shade-plugin:3.1.0:shade (default) on
> project http-monitor: Error creating shaded jar: invalid LOC header (bad
> signature)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:498)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:289)
> at 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: org.apache.maven.plugin.MojoExecutionException: Error creating
> shaded jar: invalid LOC header (bad signature)
> at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute
> (ShadeMojo.java:546)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
>
[jira] [Commented] (MSHADE-275) Maven Shade Plugin does not work under Java 10
[
https://issues.apache.org/jira/browse/MSHADE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16422855#comment-16422855
]
Hudson commented on MSHADE-275:
---
Build succeeded in Jenkins: Maven TLP » maven-shade-plugin » MSHADE-278 #3
See
https://builds.apache.org/job/maven-box/job/maven-shade-plugin/job/MSHADE-278/3/
> Maven Shade Plugin does not work under Java 10
> --
>
> Key: MSHADE-275
> URL: https://issues.apache.org/jira/browse/MSHADE-275
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.1.0
> Environment: Windows 10, 64 Bit; Java 10, 64 Bit
> Maven 3.3.9, Shade Plugin 3.1.0
>Reporter: Markus Grech
>Assignee: Karl Heinz Marbaise
>Priority: Major
> Fix For: 3.1.1
>
>
> Creating an uber-jar works fine for my project under Java 9, fails under Java
> 10 with the following Exception:
>
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-shade-plugin:3.1.0:shade (default) on project
> compiler: Error creating shaded jar: null: IllegalArgumentException -> [Help
> 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-shade-plugin:3.1.0:shade (default) on
> project compiler: Error creating shaded jar: null
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> 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 java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> 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)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:47)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error creating
> shaded jar: null
> at
> org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:546)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> ... 21 more
> Caused by: java.lang.IllegalArgumentException
> at org.objectweb.asm.ClassReader.(Unknown Source)
> at org.objectweb.asm.ClassReader.(Unknown Source)
> at org.objectweb.asm.ClassReader.(Unknown Source)
> at org.vafer.jdependency.Clazzpath.addClazzpathUnit(Clazzpath.java:201)
> at org.vafer.jdependency.Clazzpath.addClazzpathUnit(Clazzpath.java:132)
> at
> org.apache.maven.plugins.shade.filter.MinijarFilter.(MinijarFilter.java:97)
> at
> org.apache.maven.plugins.shade.mojo.ShadeMojo.getFilters(ShadeMojo.java:834)
> at
> org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:434)
> ... 23 more{code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MSHADE-275) Maven Shade Plugin does not work under Java 10
[
https://issues.apache.org/jira/browse/MSHADE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MSHADE-275.
--
Resolution: Fixed
Done in
[b944a342ee388b6c44a200fb2b3306f244424d8f|https://gitbox.apache.org/repos/asf?p=maven-shade-plugin.git;a=commitdiff;h=b944a342ee388b6c44a200fb2b3306f244424d8f]
> Maven Shade Plugin does not work under Java 10
> --
>
> Key: MSHADE-275
> URL: https://issues.apache.org/jira/browse/MSHADE-275
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.1.0
> Environment: Windows 10, 64 Bit; Java 10, 64 Bit
> Maven 3.3.9, Shade Plugin 3.1.0
>Reporter: Markus Grech
>Assignee: Karl Heinz Marbaise
>Priority: Major
> Fix For: 3.1.1
>
>
> Creating an uber-jar works fine for my project under Java 9, fails under Java
> 10 with the following Exception:
>
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-shade-plugin:3.1.0:shade (default) on project
> compiler: Error creating shaded jar: null: IllegalArgumentException -> [Help
> 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-shade-plugin:3.1.0:shade (default) on
> project compiler: Error creating shaded jar: null
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> 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 java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> 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)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:47)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error creating
> shaded jar: null
> at
> org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:546)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> ... 21 more
> Caused by: java.lang.IllegalArgumentException
> at org.objectweb.asm.ClassReader.(Unknown Source)
> at org.objectweb.asm.ClassReader.(Unknown Source)
> at org.objectweb.asm.ClassReader.(Unknown Source)
> at org.vafer.jdependency.Clazzpath.addClazzpathUnit(Clazzpath.java:201)
> at org.vafer.jdependency.Clazzpath.addClazzpathUnit(Clazzpath.java:132)
> at
> org.apache.maven.plugins.shade.filter.MinijarFilter.(MinijarFilter.java:97)
> at
> org.apache.maven.plugins.shade.mojo.ShadeMojo.getFilters(ShadeMojo.java:834)
> at
> org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:434)
> ... 23 more{code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MSHADE-275) Maven Shade Plugin does not work under Java 10
[
https://issues.apache.org/jira/browse/MSHADE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16422831#comment-16422831
]
Hudson commented on MSHADE-275:
---
Build succeeded in Jenkins: Maven TLP » maven-shade-plugin » master #15
See
https://builds.apache.org/job/maven-box/job/maven-shade-plugin/job/master/15/
> Maven Shade Plugin does not work under Java 10
> --
>
> Key: MSHADE-275
> URL: https://issues.apache.org/jira/browse/MSHADE-275
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.1.0
> Environment: Windows 10, 64 Bit; Java 10, 64 Bit
> Maven 3.3.9, Shade Plugin 3.1.0
>Reporter: Markus Grech
>Assignee: Karl Heinz Marbaise
>Priority: Major
> Fix For: 3.1.1
>
>
> Creating an uber-jar works fine for my project under Java 9, fails under Java
> 10 with the following Exception:
>
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-shade-plugin:3.1.0:shade (default) on project
> compiler: Error creating shaded jar: null: IllegalArgumentException -> [Help
> 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-shade-plugin:3.1.0:shade (default) on
> project compiler: Error creating shaded jar: null
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> 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 java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> 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)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:47)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error creating
> shaded jar: null
> at
> org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:546)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> ... 21 more
> Caused by: java.lang.IllegalArgumentException
> at org.objectweb.asm.ClassReader.(Unknown Source)
> at org.objectweb.asm.ClassReader.(Unknown Source)
> at org.objectweb.asm.ClassReader.(Unknown Source)
> at org.vafer.jdependency.Clazzpath.addClazzpathUnit(Clazzpath.java:201)
> at org.vafer.jdependency.Clazzpath.addClazzpathUnit(Clazzpath.java:132)
> at
> org.apache.maven.plugins.shade.filter.MinijarFilter.(MinijarFilter.java:97)
> at
> org.apache.maven.plugins.shade.mojo.ShadeMojo.getFilters(ShadeMojo.java:834)
> at
> org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:434)
> ... 23 more{code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] khmarbaise commented on issue #1: Update ASM to latest version
khmarbaise commented on issue #1: Update ASM to latest version URL: https://github.com/apache/maven-shade-plugin/pull/1#issuecomment-377986017 Great. So I can continue to make a new release of maven-shade-plugin. Thanks for your feedback. 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
[GitHub] raphw commented on issue #1: Update ASM to latest version
raphw commented on issue #1: Update ASM to latest version URL: https://github.com/apache/maven-shade-plugin/pull/1#issuecomment-377979931 The snapshot works fine with my build. This is an automated message from the Apache Git Service. To respond to the message, please log on GitHub and use the URL above to go to the specific comment. For queries about this service, please contact Infrastructure at: us...@infra.apache.org With regards, Apache Git Services
[jira] [Commented] (MSHADE-278) Print out the jar responsible for exceptions like "Error creating shaded jar: invalid LOC header (bad signature)"
[
https://issues.apache.org/jira/browse/MSHADE-278?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16422765#comment-16422765
]
Hudson commented on MSHADE-278:
---
Build succeeded in Jenkins: Maven TLP » maven-shade-plugin » MSHADE-278 #2
See
https://builds.apache.org/job/maven-box/job/maven-shade-plugin/job/MSHADE-278/2/
> Print out the jar responsible for exceptions like "Error creating shaded jar:
> invalid LOC header (bad signature)"
> -
>
> Key: MSHADE-278
> URL: https://issues.apache.org/jira/browse/MSHADE-278
> Project: Maven Shade Plugin
> Issue Type: Improvement
>Affects Versions: 3.1.0
> Environment: Apache Maven 3.5.3
> (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T12:49:05-07:00)
> Maven home: C:\Java\apache-maven-3.5.3\bin\..
> Java version: 1.8.0_162, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_162\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>Reporter: Gary Gregory
>Assignee: Karl Heinz Marbaise
>Priority: Major
> Fix For: 3.1.1
>
>
> Print out the jar responsible for exceptions like "Error creating shaded jar:
> invalid LOC header (bad signature)". Then I can delete it and force maven to
> download it again. Otherwise I have no idea which of >100 jars is bad.
> {noformat}
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 40.978 s
> [INFO] Finished at: 2018-03-31T07:59:29-06:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-shade-plugin:3.1.0:shade (default) on project
> http-monitor: Error creating shaded jar: invalid LOC header (bad signature)
> -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-shade-plugin:3.1.0:shade (default) on
> project http-monitor: Error creating shaded jar: invalid LOC header (bad
> signature)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:498)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:289)
> at 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: org.apache.maven.plugin.MojoExecutionException: Error creating
> shaded jar: invalid LOC header (bad signature)
> at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute
> (ShadeMojo.java:546)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
>
[jira] [Assigned] (MSHADE-278) Print out the jar responsible for exceptions like "Error creating shaded jar: invalid LOC header (bad signature)"
[
https://issues.apache.org/jira/browse/MSHADE-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise reassigned MSHADE-278:
--
Assignee: Karl Heinz Marbaise
> Print out the jar responsible for exceptions like "Error creating shaded jar:
> invalid LOC header (bad signature)"
> -
>
> Key: MSHADE-278
> URL: https://issues.apache.org/jira/browse/MSHADE-278
> Project: Maven Shade Plugin
> Issue Type: Improvement
>Affects Versions: 3.1.0
> Environment: Apache Maven 3.5.3
> (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T12:49:05-07:00)
> Maven home: C:\Java\apache-maven-3.5.3\bin\..
> Java version: 1.8.0_162, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_162\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>Reporter: Gary Gregory
>Assignee: Karl Heinz Marbaise
>Priority: Major
> Fix For: 3.1.1
>
>
> Print out the jar responsible for exceptions like "Error creating shaded jar:
> invalid LOC header (bad signature)". Then I can delete it and force maven to
> download it again. Otherwise I have no idea which of >100 jars is bad.
> {noformat}
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 40.978 s
> [INFO] Finished at: 2018-03-31T07:59:29-06:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-shade-plugin:3.1.0:shade (default) on project
> http-monitor: Error creating shaded jar: invalid LOC header (bad signature)
> -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-shade-plugin:3.1.0:shade (default) on
> project http-monitor: Error creating shaded jar: invalid LOC header (bad
> signature)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:498)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:289)
> at 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: org.apache.maven.plugin.MojoExecutionException: Error creating
> shaded jar: invalid LOC header (bad signature)
> at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute
> (ShadeMojo.java:546)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
>
[jira] [Updated] (MSHADE-278) Print out the jar responsible for exceptions like "Error creating shaded jar: invalid LOC header (bad signature)"
[
https://issues.apache.org/jira/browse/MSHADE-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MSHADE-278:
---
Fix Version/s: 3.1.1
> Print out the jar responsible for exceptions like "Error creating shaded jar:
> invalid LOC header (bad signature)"
> -
>
> Key: MSHADE-278
> URL: https://issues.apache.org/jira/browse/MSHADE-278
> Project: Maven Shade Plugin
> Issue Type: Improvement
>Affects Versions: 3.1.0
> Environment: Apache Maven 3.5.3
> (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T12:49:05-07:00)
> Maven home: C:\Java\apache-maven-3.5.3\bin\..
> Java version: 1.8.0_162, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_162\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>Reporter: Gary Gregory
>Priority: Major
> Fix For: 3.1.1
>
>
> Print out the jar responsible for exceptions like "Error creating shaded jar:
> invalid LOC header (bad signature)". Then I can delete it and force maven to
> download it again. Otherwise I have no idea which of >100 jars is bad.
> {noformat}
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 40.978 s
> [INFO] Finished at: 2018-03-31T07:59:29-06:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-shade-plugin:3.1.0:shade (default) on project
> http-monitor: Error creating shaded jar: invalid LOC header (bad signature)
> -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-shade-plugin:3.1.0:shade (default) on
> project http-monitor: Error creating shaded jar: invalid LOC header (bad
> signature)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:498)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:289)
> at 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: org.apache.maven.plugin.MojoExecutionException: Error creating
> shaded jar: invalid LOC header (bad signature)
> at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute
> (ShadeMojo.java:546)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
>
[jira] [Commented] (SCM-763) Password masking on linux does not work
[
https://issues.apache.org/jira/browse/SCM-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16422743#comment-16422743
]
Michael Osipov commented on SCM-763:
The following has been tried in Konsole on Fedora 27:
{noformat}
mosipov@localhost SCM-763]$ mvn scm:list -Dpassword=toll
[INFO] Scanning for projects...
[INFO]
[INFO] < net.sf.michael-o.dirctxsrc:dircontextsource >-
[INFO] Building dircontextsource 2.1.1-SNAPSHOT
[INFO] [ jar ]-
[INFO]
[INFO] --- maven-scm-plugin:1.9.6-SNAPSHOT:list (default-cli) @
dircontextsource ---
[INFO] Executing: /bin/sh -c cd /tmp && svn --password '*' --no-auth-cache
--non-interactive list --recursive
file:///D:/Entwicklung/svn-repos/scm-svn-test-at-sign/branches/toll2/.
[ERROR] Provider message:
[ERROR] The svn command failed.
[ERROR] Command output:
[ERROR] svn: E170013: Unable to connect to a repository at URL
'file:///D:/Entwicklung/svn-repos/scm-svn-test-at-sign/branches/toll2'
svn: E180001: Unable to open repository
'file:///D:/Entwicklung/svn-repos/scm-svn-test-at-sign/branches/toll2'{noformat}
as well as with space
{noformat}
mosipov@localhost SCM-763]$ mvn scm:list -Dpassword=toll
[INFO] Scanning for projects...
[INFO]
[INFO] < net.sf.michael-o.dirctxsrc:dircontextsource >-
[INFO] Building dircontextsource 2.1.1-SNAPSHOT
[INFO] [ jar ]-
[INFO]
[INFO] --- maven-scm-plugin:1.9.6-SNAPSHOT:list (default-cli) @
dircontextsource ---
[INFO] Executing: /bin/sh -c cd /tmp && svn --password '*' --no-auth-cache
--non-interactive list --recursive
file:///D:/Entwicklung/svn-repos/scm-svn-test-at-sign/branches/toll2/.
[ERROR] Provider message:
[ERROR] The svn command failed.
[ERROR] Command output:
[ERROR] svn: E170013: Unable to connect to a repository at URL
'file:///D:/Entwicklung/svn-repos/scm-svn-test-at-sign/branches/toll2'
svn: E180001: Unable to open repository
'file:///D:/Entwicklung/svn-repos/scm-svn-test-at-sign/branches/toll2'
{noformat}
Yes, there are shortcoming, but I cannot reproduce the depicted case. Can
someone provide a test sample?
> Password masking on linux does not work
> ---
>
> Key: SCM-763
> URL: https://issues.apache.org/jira/browse/SCM-763
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-svn
>Affects Versions: 1.9
> Environment: Jenkins 1.502 on a SLES11
>Reporter: Tobias Kalmes
>Priority: Major
>
> Passwords are not masked in the log output on Linux machines. The masking
> works as intended on Windows machines. On linux machines tho the password is
> printed in clear text. This seems to be a problem due to the additional
> single quotes that are added around the parameters on linux machines.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[GitHub] petukhov opened a new pull request #3: Fixed the example code in usage.apt.vm
petukhov opened a new pull request #3: Fixed the example code in usage.apt.vm URL: https://github.com/apache/maven-checkstyle-plugin/pull/3 Had the original code copied to my project and it was resulting in an error. After putting the configuration tag directly under the plugin tag everything worked. Here is the related StackOverflow question with the solution: https://stackoverflow.com/questions/49606513/maven-checkstyle-plugin3-0-0check-failed-during-checkstyle-configuration-can/49610945#49610945 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] (MNG-6388) Error Fetching Artifacts: "[B cannot be cast to java.lang.String"
[
https://issues.apache.org/jira/browse/MNG-6388?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16422701#comment-16422701
]
Mike Kelly commented on MNG-6388:
-
Here's a complete backtrace from another impacted project, generated with {{mvn
-X dependency:go-offline}}:
{noformat}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-dependency-plugin:3.0.1:resolve-plugins
(resolve-plugins) on project REDACTED:
org.eclipse.aether.resolution.DependencyResolutionException: Failed to collect
dependencies at
org.springframework.boot:spring-boot-maven-plugin:jar:2.0.0.RELEASE ->
org.apache.maven:maven-archiver:jar:2.6 ->
org.apache.maven:maven-core:jar:2.2.1 ->
org.apache.maven.wagon:wagon-http:jar:1.0-beta-6 ->
org.apache.maven.wagon:wagon-http-shared:jar:1.0-beta-6 ->
commons-httpclient:commons-httpclient:jar:3.1 ->
commons-codec:commons-codec:jar:1.11: Failed to read artifact descriptor for
commons-codec:commons-codec:jar:1.11: Could not transfer artifact
commons-codec:commons-codec:pom:1.11 from/to artifactory
(https://artifactory.REDACTED.com/artifactory/all): [B cannot be cast to
java.lang.String -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-dependency-plugin:3.0.1:resolve-plugins
(resolve-plugins) on project REDACTED:
org.eclipse.aether.resolution.DependencyResolutionException: Failed to collect
dependencies at
org.springframework.boot:spring-boot-maven-plugin:jar:2.0.0.RELEASE ->
org.apache.maven:maven-archiver:jar:2.6 ->
org.apache.maven:maven-core:jar:2.2.1 ->
org.apache.maven.wagon:wagon-http:jar:1.0-beta-6 ->
org.apache.maven.wagon:wagon-http-shared:jar:1.0-beta-6 ->
commons-httpclient:commons-httpclient:jar:3.1 ->
commons-codec:commons-codec:jar:1.11
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:213)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:154)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:146)
at org.apache.maven.lifecycle.internal.MojoExecutor.executeForkedExecutions
(MojoExecutor.java:353)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:198)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:154)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:146)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:289)
at 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: org.apache.maven.plugin.MojoExecutionException:
org.eclipse.aether.resolution.DependencyResolutionException: Failed to collect
dependencies at
org.springframework.boot:spring-boot-maven-plugin:jar:2.0.0.RELEASE ->
org.apache.maven:maven-archiver:jar:2.6 ->
org.apache.maven:maven-core:jar:2.2.1 ->
org.apache.maven.wagon:wagon-http:jar:1.0-beta-6 ->
org.apache.maven.wagon:wagon-http-shared:jar:1.0-beta-6 ->
commons-httpclient:commons-httpclient:jar:3.1 ->
commons-codec:commons-codec:jar:1.11
at org.apache.maven.plugins.dependency.resolvers.ResolvePluginsMojo.doExecute
(ResolvePluginsMojo.java:162)
at org.apache.maven.plugins.dependency.AbstractDependencyMojo.execute
(AbstractDependencyMojo.java:143)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:208)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:154)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
[jira] [Created] (MNG-6388) Error Fetching Artifacts: "[B cannot be cast to java.lang.String"
Mike Kelly created MNG-6388:
---
Summary: Error Fetching Artifacts: "[B cannot be cast to
java.lang.String"
Key: MNG-6388
URL: https://issues.apache.org/jira/browse/MNG-6388
Project: Maven
Issue Type: Bug
Affects Versions: 3.5.3
Environment: $ docker run --rm -it maven:3-jdk-8 mvn --version
Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
2018-02-24T19:49:05Z)
Maven home: /usr/share/maven
Java version: 1.8.0_162, vendor: Oracle Corporation
Java home: /usr/lib/jvm/java-8-openjdk-amd64/jre
Default locale: en, platform encoding: UTF-8
OS name: "linux", version: "3.10.0-693.21.1.el7.x86_64", arch: "amd64", family:
"unix"
$ mvn -version
Apache Maven 3.5.3 (3383c37e1f9e9b3bc3df5050c29c8aff9f295297;
2018-02-24T14:49:05-05:00)
Maven home: /opt/local/share/java/maven3
Java version: 1.8.0_161, vendor: Oracle Corporation
Java home: /Library/Java/JavaVirtualMachines/jdk1.8.0_161.jdk/Contents/Home/jre
Default locale: en_US, platform encoding: UTF-8
OS name: "mac os x", version: "10.12.6", arch: "x86_64", family: "mac"
Reporter: Mike Kelly
When using Maven 3.5.3 with Artifactory 5.10.0 configured as a "*" mirror,
downloads & uploads fail with errors like:
{noformat}
[ERROR] Failed to execute goal on project ccc-persistence: Could not resolve
dependencies for project REDACTED:REDACTED:jar:3.47.0-SNAPSHOT: Failed to
collect dependencies at org.flywaydb:flyway-core:jar:3.2.1: Failed to read
artifact descriptor for org.flywaydb:flyway-core:jar:3.2.1: Could not transfer
artifact org.flywaydb:flyway-core:pom:3.2.1 from/to artifactory
(https://artifactory.REDACTED.com/artifactory/all): [B cannot be cast to
java.lang.String -> [Help 1]{noformat}
I've seen this issue both with the official Docker container, and with Maven
3.5.3 from MacPorts; in both cases, downgrading back down to 3.5.2 resolved the
issue.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (SCM-763) Password masking on linux does not work
[
https://issues.apache.org/jira/browse/SCM-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16422655#comment-16422655
]
Michael Osipov commented on SCM-763:
For the record, it is also broken on Windows too:
{noformat}
PS D:\Entwicklung\Projekte\scm-svn-test-at-sign> mvn scm:list "-Dpassword=mumu
ab"
[INFO] Scanning for projects...
[INFO]
[INFO] < net.sf.michael-o.dirctxsrc:dircontextsource >-
[INFO] Building dircontextsource 2.1.1-SNAPSHOT
[INFO] [ jar ]-
[INFO]
[INFO] --- maven-scm-plugin:1.9.6-SNAPSHOT:list (default-cli) @
dircontextsource ---
[INFO] Executing: cmd.exe /X /C "svn --password * ab" --no-auth-cache
--non-interactive list --recursive
file:///D:/Entwicklung/svn-repos/scm-svn-test-at-sign/branches/toll2/."
[INFO] Working directory: C:\Users\mosipov\AppData\Local\Temp{noformat}
> Password masking on linux does not work
> ---
>
> Key: SCM-763
> URL: https://issues.apache.org/jira/browse/SCM-763
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-svn
>Affects Versions: 1.9
> Environment: Jenkins 1.502 on a SLES11
>Reporter: Tobias Kalmes
>Priority: Major
>
> Passwords are not masked in the log output on Linux machines. The masking
> works as intended on Windows machines. On linux machines tho the password is
> printed in clear text. This seems to be a problem due to the additional
> single quotes that are added around the parameters on linux machines.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MSHADE-278) Print out the jar responsible for exceptions like "Error creating shaded jar: invalid LOC header (bad signature)"
[
https://issues.apache.org/jira/browse/MSHADE-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated MSHADE-278:
Summary: Print out the jar responsible for exceptions like "Error creating
shaded jar: invalid LOC header (bad signature)" (was: Print out the jar
responsible for "Error creating shaded jar: invalid LOC header (bad signature)")
> Print out the jar responsible for exceptions like "Error creating shaded jar:
> invalid LOC header (bad signature)"
> -
>
> Key: MSHADE-278
> URL: https://issues.apache.org/jira/browse/MSHADE-278
> Project: Maven Shade Plugin
> Issue Type: Improvement
>Affects Versions: 3.1.0
> Environment: Apache Maven 3.5.3
> (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T12:49:05-07:00)
> Maven home: C:\Java\apache-maven-3.5.3\bin\..
> Java version: 1.8.0_162, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_162\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>Reporter: Gary Gregory
>Priority: Major
>
> Print out the jar responsible for "Error creating shaded jar: invalid LOC
> header (bad signature)". Then I can delete it and force maven to download it
> again. Otherwise I have no idea which of >100 jars is bad.
> {noformat}
> [INFO]
>
> [INFO] BUILD FAILURE
> [INFO]
>
> [INFO] Total time: 40.978 s
> [INFO] Finished at: 2018-03-31T07:59:29-06:00
> [INFO]
>
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-shade-plugin:3.1.0:shade (default) on project
> http-monitor: Error creating shaded jar: invalid LOC header (bad signature)
> -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-shade-plugin:3.1.0:shade (default) on
> project http-monitor: Error creating shaded jar: invalid LOC header (bad
> signature)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:213)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:81)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
> (SingleThreadedBuilder.java:56)
> at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
> (LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
> at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
> at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
> at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
> at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
> at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
> at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke
> (NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke
> (DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke (Method.java:498)
> at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
> (Launcher.java:289)
> at 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: org.apache.maven.plugin.MojoExecutionException: Error creating
> shaded jar: invalid LOC header (bad signature)
> at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute
> (ShadeMojo.java:546)
> at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
> (DefaultBuildPluginManager.java:137)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:208)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:154)
> at org.apache.maven.lifecycle.internal.MojoExecutor.execute
> (MojoExecutor.java:146)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
> (LifecycleModuleBuilder.java:117)
> at
>
[jira] [Updated] (MSHADE-278) Print out the jar responsible for exceptions like "Error creating shaded jar: invalid LOC header (bad signature)"
[
https://issues.apache.org/jira/browse/MSHADE-278?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Gary Gregory updated MSHADE-278:
Description:
Print out the jar responsible for exceptions like "Error creating shaded jar:
invalid LOC header (bad signature)". Then I can delete it and force maven to
download it again. Otherwise I have no idea which of >100 jars is bad.
{noformat}
[INFO]
[INFO] BUILD FAILURE
[INFO]
[INFO] Total time: 40.978 s
[INFO] Finished at: 2018-03-31T07:59:29-06:00
[INFO]
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-shade-plugin:3.1.0:shade (default) on project
http-monitor: Error creating shaded jar: invalid LOC header (bad signature) ->
[Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-shade-plugin:3.1.0:shade (default) on project
http-monitor: Error creating shaded jar: invalid LOC header (bad signature)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:213)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:154)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:146)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:289)
at 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: org.apache.maven.plugin.MojoExecutionException: Error creating
shaded jar: invalid LOC header (bad signature)
at org.apache.maven.plugins.shade.mojo.ShadeMojo.execute
(ShadeMojo.java:546)
at org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo
(DefaultBuildPluginManager.java:137)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:208)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:154)
at org.apache.maven.lifecycle.internal.MojoExecutor.execute
(MojoExecutor.java:146)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:117)
at org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject
(LifecycleModuleBuilder.java:81)
at
org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build
(SingleThreadedBuilder.java:56)
at org.apache.maven.lifecycle.internal.LifecycleStarter.execute
(LifecycleStarter.java:128)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:305)
at org.apache.maven.DefaultMaven.doExecute (DefaultMaven.java:192)
at org.apache.maven.DefaultMaven.execute (DefaultMaven.java:105)
at org.apache.maven.cli.MavenCli.execute (MavenCli.java:956)
at org.apache.maven.cli.MavenCli.doMain (MavenCli.java:290)
at org.apache.maven.cli.MavenCli.main (MavenCli.java:194)
at sun.reflect.NativeMethodAccessorImpl.invoke0 (Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke
(NativeMethodAccessorImpl.java:62)
at sun.reflect.DelegatingMethodAccessorImpl.invoke
(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke (Method.java:498)
at org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced
(Launcher.java:289)
at org.codehaus.plexus.classworlds.launcher.Launcher.launch
(Launcher.java:229)
at org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode
[jira] [Closed] (SCM-879) JazzChangeLogCommandTest#testListChangesetConsumerWithTimeOnly() fails with NPE on Java 10
[
https://issues.apache.org/jira/browse/SCM-879?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed SCM-879.
--
Resolution: Fixed
Fixed with
[57c9e6caa823011f9c4cc9d0e72790cbc1f23e4a|https://gitbox.apache.org/repos/asf?p=maven-scm.git;a=commit;h=57c9e6caa823011f9c4cc9d0e72790cbc1f23e4a].
> JazzChangeLogCommandTest#testListChangesetConsumerWithTimeOnly() fails with
> NPE on Java 10
> --
>
> Key: SCM-879
> URL: https://issues.apache.org/jira/browse/SCM-879
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-provider-jazz
>Affects Versions: 1.9.5
> Environment: Apache Maven 3.5.3
> (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
> Maven home: D:\Entwicklung\Programme\apache-maven-3.5.3\bin\..
> Java version: 10, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk-10
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 1.9.6
>
>
> Surefire says:
> {noformat}
> Tests run: 6, Failures: 0, Errors: 1, Skipped: 0, Time elapsed: 0.917 sec <<<
> FAILURE! - in
> org.apache.maven.scm.provider.jazz.command.changelog.JazzChangeLogCommandTest
> testListChangesetConsumerWithTimeOnly(org.apache.maven.scm.provider.jazz.command.changelog.JazzChangeLogCommandTest)
> Time elapsed: 0.678 sec <<< ERROR!
> java.lang.NullPointerException
> at
> org.apache.maven.scm.provider.jazz.command.changelog.JazzChangeLogCommandTest.testListChangesetConsumerWithTimeOnly(JazzChangeLogCommandTest.java:294){noformat}
> The error is rooted in
> {{org.apache.maven.scm.provider.jazz.command.changelog.JazzListChangesetConsumer.processModifiedLine(String)}}.
> It does not parse the given time with {{JAZZ_TIMESTAMP_PATTERN_TIME}} *and*
> {{Locale.ENGLISH}}, but relies on the system locale which will fail for
> non-English parsing {{AM/PM}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (SCM-878) AbstractConsumer#parseDate() logs wrong locale in case of a ParseException
[
https://issues.apache.org/jira/browse/SCM-878?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Michael Osipov closed SCM-878.
--
Resolution: Fixed
Fixed with
[c83eee65903c6d1eafd9e51810a3c523037b499b|https://gitbox.apache.org/repos/asf?p=maven-scm.git;a=commit;h=c83eee65903c6d1eafd9e51810a3c523037b499b].
> AbstractConsumer#parseDate() logs wrong locale in case of a ParseException
> --
>
> Key: SCM-878
> URL: https://issues.apache.org/jira/browse/SCM-878
> Project: Maven SCM
> Issue Type: Bug
> Components: maven-scm-api
>Affects Versions: 1.9.5
> Environment: Apache Maven 3.5.3
> (3383c37e1f9e9b3bc3df5050c29c8aff9f295297; 2018-02-24T20:49:05+01:00)
> Maven home: D:\Entwicklung\Programme\apache-maven-3.5.3\bin\..
> Java version: 10, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk-10
> Default locale: de_DE, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>Reporter: Michael Osipov
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 1.9.6
>
>
> While testing SCM with JDK 10 the Jazz provider fails with:
> {noformat}
> skip ParseException: Unparseable date: "Feb 25, 2012 10:13 PM" during parsing
> date Feb 25, 2012 10:13 PM with pattern MMM d, h:mm a with Locale en
> java.text.ParseException: Unparseable date: "Feb 25, 2012 10:13 PM"
> at java.base/java.text.DateFormat.parse(DateFormat.java:395)
> at
> org.apache.maven.scm.util.AbstractConsumer.parseDate(AbstractConsumer.java:112)
> at
> org.apache.maven.scm.util.AbstractConsumer.parseDate(AbstractConsumer.java:68)
> at
> org.apache.maven.scm.provider.jazz.command.changelog.JazzListChangesetConsumer.processModifiedLine(JazzListChangesetConsumer.java:341)
> at
> org.apache.maven.scm.provider.jazz.command.changelog.JazzListChangesetConsumer.consumeLine(JazzListChangesetConsumer.java:249)
> at
> org.apache.maven.scm.provider.jazz.command.changelog.JazzChangeLogCommandTest.testListChangesetConsumer(JazzChangeLogCommandTest.java:159)ListChangesetConsumer.java:341){noformat}
> Looking at the Jazz test code no locale is actually passed, so the default
> locale is used.
> The issue is rooted in the catch warn statement (in
> {{org.apache.maven.scm.util.AbstractConsumer.parseDate(String, String,
> String, Locale)}}) which assumes that a passed null locale defaults to
> {{Locale.ENGLISH}}. It shall display {{Locale.getDefault()}}.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MDEP-605) Add documentation information for GitHub
[ https://issues.apache.org/jira/browse/MDEP-605?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MDEP-605. Resolution: Done Done in [730e6bc2b8369b9155527ff87f32a56118f63fae|https://gitbox.apache.org/repos/asf?p=maven-dependency-plugin.git;a=commitdiff;h=730e6bc2b8369b9155527ff87f32a56118f63fae] > Add documentation information for GitHub > > > Key: MDEP-605 > URL: https://issues.apache.org/jira/browse/MDEP-605 > Project: Maven Dependency Plugin > Issue Type: Improvement >Affects Versions: 3.1.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MDEP-605) Add documentation information for GitHub
[ https://issues.apache.org/jira/browse/MDEP-605?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16422626#comment-16422626 ] Hudson commented on MDEP-605: - Build succeeded in Jenkins: Maven TLP » maven-dependency-plugin » master #9 See https://builds.apache.org/job/maven-box/job/maven-dependency-plugin/job/master/9/ > Add documentation information for GitHub > > > Key: MDEP-605 > URL: https://issues.apache.org/jira/browse/MDEP-605 > Project: Maven Dependency Plugin > Issue Type: Improvement >Affects Versions: 3.1.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.1.0 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSHADE-275) Maven Shade Plugin does not work under Java 10
[
https://issues.apache.org/jira/browse/MSHADE-275?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16422600#comment-16422600
]
Hudson commented on MSHADE-275:
---
Build succeeded in Jenkins: Maven TLP » maven-shade-plugin » MSHADE-275 #13
See
https://builds.apache.org/job/maven-box/job/maven-shade-plugin/job/MSHADE-275/13/
> Maven Shade Plugin does not work under Java 10
> --
>
> Key: MSHADE-275
> URL: https://issues.apache.org/jira/browse/MSHADE-275
> Project: Maven Shade Plugin
> Issue Type: Bug
>Affects Versions: 3.1.0
> Environment: Windows 10, 64 Bit; Java 10, 64 Bit
> Maven 3.3.9, Shade Plugin 3.1.0
>Reporter: Markus Grech
>Assignee: Karl Heinz Marbaise
>Priority: Major
> Fix For: 3.1.1
>
>
> Creating an uber-jar works fine for my project under Java 9, fails under Java
> 10 with the following Exception:
>
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-shade-plugin:3.1.0:shade (default) on project
> compiler: Error creating shaded jar: null: IllegalArgumentException -> [Help
> 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-shade-plugin:3.1.0:shade (default) on
> project compiler: Error creating shaded jar: null
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:212)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:116)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:80)
> at
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder.build(SingleThreadedBuilder.java:51)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:128)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:307)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:193)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:106)
> 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 java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke0(Native
> Method)
> at
> java.base/jdk.internal.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at
> java.base/jdk.internal.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.base/java.lang.reflect.Method.invoke(Method.java:564)
> 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)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:47)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error creating
> shaded jar: null
> at
> org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:546)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> ... 21 more
> Caused by: java.lang.IllegalArgumentException
> at org.objectweb.asm.ClassReader.(Unknown Source)
> at org.objectweb.asm.ClassReader.(Unknown Source)
> at org.objectweb.asm.ClassReader.(Unknown Source)
> at org.vafer.jdependency.Clazzpath.addClazzpathUnit(Clazzpath.java:201)
> at org.vafer.jdependency.Clazzpath.addClazzpathUnit(Clazzpath.java:132)
> at
> org.apache.maven.plugins.shade.filter.MinijarFilter.(MinijarFilter.java:97)
> at
> org.apache.maven.plugins.shade.mojo.ShadeMojo.getFilters(ShadeMojo.java:834)
> at
> org.apache.maven.plugins.shade.mojo.ShadeMojo.execute(ShadeMojo.java:434)
> ... 23 more{code}
>
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MSHADE-282) Remove not used directories rel-path-test-files
[ https://issues.apache.org/jira/browse/MSHADE-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16422598#comment-16422598 ] Hudson commented on MSHADE-282: --- Build succeeded in Jenkins: Maven TLP » maven-shade-plugin » MSHADE-275 #13 See https://builds.apache.org/job/maven-box/job/maven-shade-plugin/job/MSHADE-275/13/ > Remove not used directories rel-path-test-files > --- > > Key: MSHADE-282 > URL: https://issues.apache.org/jira/browse/MSHADE-282 > Project: Maven Shade Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.1.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Trivial > Fix For: 3.1.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSHADE-283) Add documentation information for GitHub
[ https://issues.apache.org/jira/browse/MSHADE-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16422599#comment-16422599 ] Hudson commented on MSHADE-283: --- Build succeeded in Jenkins: Maven TLP » maven-shade-plugin » MSHADE-275 #13 See https://builds.apache.org/job/maven-box/job/maven-shade-plugin/job/MSHADE-275/13/ > Add documentation information for GitHub > > > Key: MSHADE-283 > URL: https://issues.apache.org/jira/browse/MSHADE-283 > Project: Maven Shade Plugin > Issue Type: Improvement >Affects Versions: 3.1.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.1.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MENFORCER-142) Specify enforcer rule in command line without updateing any pom
[ https://issues.apache.org/jira/browse/MENFORCER-142?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16422583#comment-16422583 ] ASF GitHub Bot commented on MENFORCER-142: -- lrozenblyum commented on issue #31: MENFORCER-142 Initial poc implementation of adding rules from cmdline (WIP) URL: https://github.com/apache/maven-enforcer/pull/31#issuecomment-377946805 It's an amazing feature! Any plans integrating it to master and releasing a new plugin version? :) 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 > Specify enforcer rule in command line without updateing any pom > --- > > Key: MENFORCER-142 > URL: https://issues.apache.org/jira/browse/MENFORCER-142 > Project: Maven Enforcer Plugin > Issue Type: Improvement > Components: Plugin >Reporter: Arnaud Bourrée >Priority: Major > Fix For: more-investigation > > > Hello, > How could we specify enforcer:enforce rules from command line? > I want to run command line like following without updating any pom.xml: > mvn enforcer:enforce -Drules=com.acme.UseAcmeParentPom > The goal of this enforcer:enforce rule is to check that Acme's > developers write pom.xml which inherit from acme's parent pom.xml > And because they may not inherit from acme's parent pom.xml, I cannot > specify enforcer rule in. > Regards, > Arnaud. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] lrozenblyum commented on issue #31: MENFORCER-142 Initial poc implementation of adding rules from cmdline (WIP)
lrozenblyum commented on issue #31: MENFORCER-142 Initial poc implementation of adding rules from cmdline (WIP) URL: https://github.com/apache/maven-enforcer/pull/31#issuecomment-377946805 It's an amazing feature! Any plans integrating it to master and releasing a new plugin version? :) 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] (MARCHETYPES-51) add plugin testing harness to maven-archetype-plugin
[ https://issues.apache.org/jira/browse/MARCHETYPES-51?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Hervé Boutemy closed MARCHETYPES-51. Resolution: Fixed Assignee: Hervé Boutemy ok, we'll see later for maven-compat dependency removal > add plugin testing harness to maven-archetype-plugin > > > Key: MARCHETYPES-51 > URL: https://issues.apache.org/jira/browse/MARCHETYPES-51 > Project: Maven Archetype Bundles > Issue Type: Dependency upgrade > Components: Maven Plugin Archetype >Affects Versions: maven-archetype-plugin-1.3 > Environment: macOS High Sierra >Reporter: Nick Lombard >Assignee: Hervé Boutemy >Priority: Major > Fix For: 1.3 > > Attachments: MARCHETYPES-51.patch > > > I want to update the plugin archetype (for creating new plugins not to be > confused with the archetype plugin) to also include a testing harness unit > test example alongside the currently supplied integration test example. > Once completed the documentation can then be updated to reflect the new > starting point. The documentation currently under Plugin Developers Centre > should also be merged with Cookbook: How To Use Maven Plugin Testing Harness? > But lets start with updating the archetype and take it from there. > Please let me know if there you have any problem with me working on this or > if there are any special requirements you would like to see addressed. > I am going with the assumption that > http://svn.apache.org/viewvc/maven/archetypes is the correct repository to > patch against because this repo has not been migrated to git as yet. Please > correct me if I am wrong. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MPH-124) Show parameter aliases in describe goal
[
https://issues.apache.org/jira/browse/MPH-124?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16422569#comment-16422569
]
ASF GitHub Bot commented on MPH-124:
Github user bentatham closed the pull request at:
https://github.com/apache/maven-plugins/pull/134
> Show parameter aliases in describe goal
> ---
>
> Key: MPH-124
> URL: https://issues.apache.org/jira/browse/MPH-124
> Project: Maven Help Plugin
> Issue Type: Improvement
>Affects Versions: 2.2
>Reporter: Ben Tatham
>Assignee: Michael Osipov
>Priority: Major
> Fix For: 3.0.0
>
>
> {{mvn help:describe -Ddetail}} should show the alias as well.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MSHADE-283) Add documentation information for GitHub
[ https://issues.apache.org/jira/browse/MSHADE-283?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16422565#comment-16422565 ] Hudson commented on MSHADE-283: --- Build succeeded in Jenkins: Maven TLP » maven-shade-plugin » master #12 See https://builds.apache.org/job/maven-box/job/maven-shade-plugin/job/master/12/ > Add documentation information for GitHub > > > Key: MSHADE-283 > URL: https://issues.apache.org/jira/browse/MSHADE-283 > Project: Maven Shade Plugin > Issue Type: Improvement >Affects Versions: 3.1.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.1.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MDEP-605) Add documentation information for GitHub
Karl Heinz Marbaise created MDEP-605: Summary: Add documentation information for GitHub Key: MDEP-605 URL: https://issues.apache.org/jira/browse/MDEP-605 Project: Maven Dependency Plugin Issue Type: Improvement Affects Versions: 3.1.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.1.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MDEP-585) Upgrade plexus-archiver to 3.5.
[ https://issues.apache.org/jira/browse/MDEP-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MDEP-585. Resolution: Done Done in [def48d1bcf06bf6d6e4f4f96042585c300347a74|https://gitbox.apache.org/repos/asf?p=maven-dependency-plugin.git;a=commitdiff;h=def48d1bcf06bf6d6e4f4f96042585c300347a74] > Upgrade plexus-archiver to 3.5. > --- > > Key: MDEP-585 > URL: https://issues.apache.org/jira/browse/MDEP-585 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.2 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.1.0 > > > Upgrading plexus-archiver to 3.5 would mean to lift up the JDK minimum to JDK > 7 which should be done in a minor release and not in a patch release... > It looks like we need to upgrade plexus-io in one go with it otherwise tests > are failing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MDEP-585) Upgrade plexus-archiver to 3.5.
[ https://issues.apache.org/jira/browse/MDEP-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16422535#comment-16422535 ] Hudson commented on MDEP-585: - Build succeeded in Jenkins: Maven TLP » maven-dependency-plugin » master #8 See https://builds.apache.org/job/maven-box/job/maven-dependency-plugin/job/master/8/ > Upgrade plexus-archiver to 3.5. > --- > > Key: MDEP-585 > URL: https://issues.apache.org/jira/browse/MDEP-585 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.2 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.1.0 > > > Upgrading plexus-archiver to 3.5 would mean to lift up the JDK minimum to JDK > 7 which should be done in a minor release and not in a patch release... > It looks like we need to upgrade plexus-io in one go with it otherwise tests > are failing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MDEP-585) Upgrade plexus-archiver to 3.5.
[ https://issues.apache.org/jira/browse/MDEP-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16422230#comment-16422230 ] Hudson commented on MDEP-585: - Build succeeded in Jenkins: Maven TLP » maven-dependency-plugin » MDEP-585 #6 See https://builds.apache.org/job/maven-box/job/maven-dependency-plugin/job/MDEP-585/6/ > Upgrade plexus-archiver to 3.5. > --- > > Key: MDEP-585 > URL: https://issues.apache.org/jira/browse/MDEP-585 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.2 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.1.0 > > > Upgrading plexus-archiver to 3.5 would mean to lift up the JDK minimum to JDK > 7 which should be done in a minor release and not in a patch release... > It looks like we need to upgrade plexus-io in one go with it otherwise tests > are failing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MDEP-585) Upgrade plexus-archiver to 3.5.
[ https://issues.apache.org/jira/browse/MDEP-585?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MDEP-585: - Description: Upgrading plexus-archiver to 3.5 would mean to lift up the JDK minimum to JDK 7 which should be done in a minor release and not in a patch release... It looks like we need to upgrade plexus-io in one go with it otherwise tests are failing. was:Upgrading plexus-archiver to 3.5 would mean to lift up the JDK minimum to JDK 7 which should be done in a minor release and not in a patch release... > Upgrade plexus-archiver to 3.5. > --- > > Key: MDEP-585 > URL: https://issues.apache.org/jira/browse/MDEP-585 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.2 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.1.0 > > > Upgrading plexus-archiver to 3.5 would mean to lift up the JDK minimum to JDK > 7 which should be done in a minor release and not in a patch release... > It looks like we need to upgrade plexus-io in one go with it otherwise tests > are failing. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MDEP-594) Dependency reported as "unused declared" when runtime-retention type annotation is used
[
https://issues.apache.org/jira/browse/MDEP-594?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16422194#comment-16422194
]
Karl Heinz Marbaise commented on MDEP-594:
--
Hasn't that being fixed with 3.0.1/3.0.2 of maven-dependency-plugin ?
> Dependency reported as "unused declared" when runtime-retention type
> annotation is used
> ---
>
> Key: MDEP-594
> URL: https://issues.apache.org/jira/browse/MDEP-594
> Project: Maven Dependency Plugin
> Issue Type: Bug
> Components: analyze
>Affects Versions: 3.0.0
> Environment: Apache Maven 3.5.0,
> Oracle Java version: 1.8.0_144
>Reporter: Andreas Hubold
>Priority: Major
> Attachments: example.tgz
>
>
> In the attached example project, module "usage" uses annotation {{@Example}}:
> {code}
> public interface Usage {
> @Example String getEmail();
> }
> {code}
> which is defined in module "annotation" as:
> {code}
> @Target({ElementType.TYPE_USE, ElementType.TYPE_PARAMETER})
> @Retention(RetentionPolicy.RUNTIME)
> public @interface Example {
> }
> {code}
> Consequently, the pom.xml of module "usage" defines a compile-dependency to
> module "annotation" but the dependency:analyze-only goal incorrectly reports
> this as unused dependency:
> {noformat}
> [main] [INFO] --- maven-dependency-plugin:3.0.0:analyze-only
> (analyze-dependencies) @ usage ---
> [main] [WARNING] Unused declared dependencies found:
> [main] [WARNING]com.example:annotation:jar:1.0-SNAPSHOT:compile
> {noformat}
> This false positive is only reported if
> * the annotation is meta-annotated with target TYPE_USE + TYPE_PARAMETER
> * and the source.version/target.version of the compiler plugin for module
> "usage" is 1.8
> There's no false positive if the {{@Target}} meta-annotation is removed or if
> compiler's source/target version is set to 1.7.
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MDEP-584) Upgrade plexus-utils to version 3.1.0
[
https://issues.apache.org/jira/browse/MDEP-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16422190#comment-16422190
]
ASF GitHub Bot commented on MDEP-584:
-
Github user io7m closed the pull request at:
https://github.com/apache/maven-plugins/pull/136
> Upgrade plexus-utils to version 3.1.0
> -
>
> Key: MDEP-584
> URL: https://issues.apache.org/jira/browse/MDEP-584
> Project: Maven Dependency Plugin
> Issue Type: Dependency upgrade
>Affects Versions: 3.0.2
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.1.0
>
>
> Currently an upgrade will fail the following unit tests in maven-dependency
> plugin:
> {code}
> Results :
> Failed tests:
> TestCopyMojo.testCopyOverWriteReleases:694
> TestCopyMojo.testCopyOverWriteSnapshot:723
> TestCopyDependenciesMojo.testOverWriteRelease:592 time = 1504955654000
> should be < to 1504955652000
> TestCopyDependenciesMojo.testOverWriteSnap:661
> Tests run: 244, Failures: 4, Errors: 0, Skipped: 0
> {code}
> I need to investigate those tests...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Closed] (MDEP-584) Upgrade plexus-utils to version 3.1.0
[
https://issues.apache.org/jira/browse/MDEP-584?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MDEP-584.
Resolution: Done
Done in
[399db5c9e677bd0b7a39dabdaeee5a8380c7497a|https://gitbox.apache.org/repos/asf?p=maven-dependency-plugin.git;a=commitdiff;h=399db5c9e677bd0b7a39dabdaeee5a8380c7497a]
> Upgrade plexus-utils to version 3.1.0
> -
>
> Key: MDEP-584
> URL: https://issues.apache.org/jira/browse/MDEP-584
> Project: Maven Dependency Plugin
> Issue Type: Dependency upgrade
>Affects Versions: 3.0.2
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.1.0
>
>
> Currently an upgrade will fail the following unit tests in maven-dependency
> plugin:
> {code}
> Results :
> Failed tests:
> TestCopyMojo.testCopyOverWriteReleases:694
> TestCopyMojo.testCopyOverWriteSnapshot:723
> TestCopyDependenciesMojo.testOverWriteRelease:592 time = 1504955654000
> should be < to 1504955652000
> TestCopyDependenciesMojo.testOverWriteSnap:661
> Tests run: 244, Failures: 4, Errors: 0, Skipped: 0
> {code}
> I need to investigate those tests...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MDEP-584) Upgrade plexus-utils to version 3.1.0
[
https://issues.apache.org/jira/browse/MDEP-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16422187#comment-16422187
]
Mark Raynsford commented on MDEP-584:
-
You're welcome. I'd forgotten about this one!
> Upgrade plexus-utils to version 3.1.0
> -
>
> Key: MDEP-584
> URL: https://issues.apache.org/jira/browse/MDEP-584
> Project: Maven Dependency Plugin
> Issue Type: Dependency upgrade
>Affects Versions: 3.0.2
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.1.0
>
>
> Currently an upgrade will fail the following unit tests in maven-dependency
> plugin:
> {code}
> Results :
> Failed tests:
> TestCopyMojo.testCopyOverWriteReleases:694
> TestCopyMojo.testCopyOverWriteSnapshot:723
> TestCopyDependenciesMojo.testOverWriteRelease:592 time = 1504955654000
> should be < to 1504955652000
> TestCopyDependenciesMojo.testOverWriteSnap:661
> Tests run: 244, Failures: 4, Errors: 0, Skipped: 0
> {code}
> I need to investigate those tests...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MDEP-584) Upgrade plexus-utils to version 3.1.0
[
https://issues.apache.org/jira/browse/MDEP-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16422181#comment-16422181
]
Hudson commented on MDEP-584:
-
Build unstable in Jenkins: Maven TLP » maven-dependency-plugin » MDEP-585 #5
See
https://builds.apache.org/job/maven-box/job/maven-dependency-plugin/job/MDEP-585/5/
> Upgrade plexus-utils to version 3.1.0
> -
>
> Key: MDEP-584
> URL: https://issues.apache.org/jira/browse/MDEP-584
> Project: Maven Dependency Plugin
> Issue Type: Dependency upgrade
>Affects Versions: 3.0.2
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.1.0
>
>
> Currently an upgrade will fail the following unit tests in maven-dependency
> plugin:
> {code}
> Results :
> Failed tests:
> TestCopyMojo.testCopyOverWriteReleases:694
> TestCopyMojo.testCopyOverWriteSnapshot:723
> TestCopyDependenciesMojo.testOverWriteRelease:592 time = 1504955654000
> should be < to 1504955652000
> TestCopyDependenciesMojo.testOverWriteSnap:661
> Tests run: 244, Failures: 4, Errors: 0, Skipped: 0
> {code}
> I need to investigate those tests...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MDEP-585) Upgrade plexus-archiver to 3.5.
[ https://issues.apache.org/jira/browse/MDEP-585?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16422182#comment-16422182 ] Hudson commented on MDEP-585: - Build unstable in Jenkins: Maven TLP » maven-dependency-plugin » MDEP-585 #5 See https://builds.apache.org/job/maven-box/job/maven-dependency-plugin/job/MDEP-585/5/ > Upgrade plexus-archiver to 3.5. > --- > > Key: MDEP-585 > URL: https://issues.apache.org/jira/browse/MDEP-585 > Project: Maven Dependency Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.0.2 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.1.0 > > > Upgrading plexus-archiver to 3.5 would mean to lift up the JDK minimum to JDK > 7 which should be done in a minor release and not in a patch release... -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MDEP-584) Upgrade plexus-utils to version 3.1.0
[
https://issues.apache.org/jira/browse/MDEP-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16422178#comment-16422178
]
Hudson commented on MDEP-584:
-
Build succeeded in Jenkins: Maven TLP » maven-dependency-plugin » master #7
See
https://builds.apache.org/job/maven-box/job/maven-dependency-plugin/job/master/7/
> Upgrade plexus-utils to version 3.1.0
> -
>
> Key: MDEP-584
> URL: https://issues.apache.org/jira/browse/MDEP-584
> Project: Maven Dependency Plugin
> Issue Type: Dependency upgrade
>Affects Versions: 3.0.2
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.1.0
>
>
> Currently an upgrade will fail the following unit tests in maven-dependency
> plugin:
> {code}
> Results :
> Failed tests:
> TestCopyMojo.testCopyOverWriteReleases:694
> TestCopyMojo.testCopyOverWriteSnapshot:723
> TestCopyDependenciesMojo.testOverWriteRelease:592 time = 1504955654000
> should be < to 1504955652000
> TestCopyDependenciesMojo.testOverWriteSnap:661
> Tests run: 244, Failures: 4, Errors: 0, Skipped: 0
> {code}
> I need to investigate those tests...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MDEP-584) Upgrade plexus-utils to version 3.1.0
[
https://issues.apache.org/jira/browse/MDEP-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16422169#comment-16422169
]
Karl Heinz Marbaise commented on MDEP-584:
--
Hi [~io7m] I have taken a the liberty to use your code from your pull request
#136 (slight modifications) and it works. Thanks for this patch..You can close
your PR's now.
> Upgrade plexus-utils to version 3.1.0
> -
>
> Key: MDEP-584
> URL: https://issues.apache.org/jira/browse/MDEP-584
> Project: Maven Dependency Plugin
> Issue Type: Dependency upgrade
>Affects Versions: 3.0.2
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.1.0
>
>
> Currently an upgrade will fail the following unit tests in maven-dependency
> plugin:
> {code}
> Results :
> Failed tests:
> TestCopyMojo.testCopyOverWriteReleases:694
> TestCopyMojo.testCopyOverWriteSnapshot:723
> TestCopyDependenciesMojo.testOverWriteRelease:592 time = 1504955654000
> should be < to 1504955652000
> TestCopyDependenciesMojo.testOverWriteSnap:661
> Tests run: 244, Failures: 4, Errors: 0, Skipped: 0
> {code}
> I need to investigate those tests...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MDEP-584) Upgrade plexus-utils to version 3.1.0
[
https://issues.apache.org/jira/browse/MDEP-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16422166#comment-16422166
]
Hudson commented on MDEP-584:
-
Build succeeded in Jenkins: Maven TLP » maven-dependency-plugin » MDEP-584 #4
See
https://builds.apache.org/job/maven-box/job/maven-dependency-plugin/job/MDEP-584/4/
> Upgrade plexus-utils to version 3.1.0
> -
>
> Key: MDEP-584
> URL: https://issues.apache.org/jira/browse/MDEP-584
> Project: Maven Dependency Plugin
> Issue Type: Dependency upgrade
>Affects Versions: 3.0.2
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.1.0
>
>
> Currently an upgrade will fail the following unit tests in maven-dependency
> plugin:
> {code}
> Results :
> Failed tests:
> TestCopyMojo.testCopyOverWriteReleases:694
> TestCopyMojo.testCopyOverWriteSnapshot:723
> TestCopyDependenciesMojo.testOverWriteRelease:592 time = 1504955654000
> should be < to 1504955652000
> TestCopyDependenciesMojo.testOverWriteSnap:661
> Tests run: 244, Failures: 4, Errors: 0, Skipped: 0
> {code}
> I need to investigate those tests...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Commented] (MDEP-584) Upgrade plexus-utils to version 3.1.0
[
https://issues.apache.org/jira/browse/MDEP-584?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16422160#comment-16422160
]
Hudson commented on MDEP-584:
-
Build unstable in Jenkins: Maven TLP » maven-dependency-plugin » MDEP-584 #3
See
https://builds.apache.org/job/maven-box/job/maven-dependency-plugin/job/MDEP-584/3/
> Upgrade plexus-utils to version 3.1.0
> -
>
> Key: MDEP-584
> URL: https://issues.apache.org/jira/browse/MDEP-584
> Project: Maven Dependency Plugin
> Issue Type: Dependency upgrade
>Affects Versions: 3.0.2
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.1.0
>
>
> Currently an upgrade will fail the following unit tests in maven-dependency
> plugin:
> {code}
> Results :
> Failed tests:
> TestCopyMojo.testCopyOverWriteReleases:694
> TestCopyMojo.testCopyOverWriteSnapshot:723
> TestCopyDependenciesMojo.testOverWriteRelease:592 time = 1504955654000
> should be < to 1504955652000
> TestCopyDependenciesMojo.testOverWriteSnap:661
> Tests run: 244, Failures: 4, Errors: 0, Skipped: 0
> {code}
> I need to investigate those tests...
--
This message was sent by Atlassian JIRA
(v7.6.3#76005)
[jira] [Updated] (MINVOKER-229) Add a property in invoker.properties to check the failed mojo
[ https://issues.apache.org/jira/browse/MINVOKER-229?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MINVOKER-229: - Issue Type: New Feature (was: Bug) > Add a property in invoker.properties to check the failed mojo > - > > Key: MINVOKER-229 > URL: https://issues.apache.org/jira/browse/MINVOKER-229 > Project: Maven Invoker Plugin > Issue Type: New Feature >Reporter: Romain Manni-Bucau >Priority: Major > > using invoker.buildResult = failure we can check a plugin failed but there is > no property to also check which mojo failed. > Issue is you can pass a test where the build failed for another reason than > the expected one. -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Closed] (MSHADE-282) Remove not used directories rel-path-test-files
[ https://issues.apache.org/jira/browse/MSHADE-282?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MSHADE-282. -- Resolution: Done Done in [520cf8483e2a40cd5ab679f09a79d1cd5ec4638b|https://gitbox.apache.org/repos/asf?p=maven-shade-plugin.git;a=commitdiff;h=520cf8483e2a40cd5ab679f09a79d1cd5ec4638b] > Remove not used directories rel-path-test-files > --- > > Key: MSHADE-282 > URL: https://issues.apache.org/jira/browse/MSHADE-282 > Project: Maven Shade Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.1.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Trivial > Fix For: 3.1.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Commented] (MSHADE-282) Remove not used directories rel-path-test-files
[ https://issues.apache.org/jira/browse/MSHADE-282?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16422122#comment-16422122 ] Hudson commented on MSHADE-282: --- Build succeeded in Jenkins: Maven TLP » maven-shade-plugin » master #11 See https://builds.apache.org/job/maven-box/job/maven-shade-plugin/job/master/11/ > Remove not used directories rel-path-test-files > --- > > Key: MSHADE-282 > URL: https://issues.apache.org/jira/browse/MSHADE-282 > Project: Maven Shade Plugin > Issue Type: Dependency upgrade >Affects Versions: 3.1.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Trivial > Fix For: 3.1.1 > > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Deleted] (MDEP-604) Upgrade plexus-utils 3.1.0
[ https://issues.apache.org/jira/browse/MDEP-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise deleted MDEP-604: - > Upgrade plexus-utils 3.1.0 > -- > > Key: MDEP-604 > URL: https://issues.apache.org/jira/browse/MDEP-604 > Project: Maven Dependency Plugin > Issue Type: Improvement >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Trivial > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Updated] (MDEP-604) Upgrade plexus-utils 3.1.0
[ https://issues.apache.org/jira/browse/MDEP-604?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MDEP-604: - > Upgrade plexus-utils 3.1.0 > -- > > Key: MDEP-604 > URL: https://issues.apache.org/jira/browse/MDEP-604 > Project: Maven Dependency Plugin > Issue Type: Improvement >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Trivial > -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MDEP-604) Upgrade plexus-utils 3.1.0
Karl Heinz Marbaise created MDEP-604: Summary: Upgrade plexus-utils 3.1.0 Key: MDEP-604 URL: https://issues.apache.org/jira/browse/MDEP-604 Project: Maven Dependency Plugin Issue Type: Improvement Affects Versions: 3.1.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.1.0 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[jira] [Created] (MSHADE-283) Add documentation information for GitHub
Karl Heinz Marbaise created MSHADE-283: -- Summary: Add documentation information for GitHub Key: MSHADE-283 URL: https://issues.apache.org/jira/browse/MSHADE-283 Project: Maven Shade Plugin Issue Type: Improvement Affects Versions: 3.1.1 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.1.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
[GitHub] khmarbaise commented on issue #1: Update ASM to latest version
khmarbaise commented on issue #1: Update ASM to latest version URL: https://github.com/apache/maven-shade-plugin/pull/1#issuecomment-377887753 Ok created on and provided like this: https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-shade-plugin/3.1.1-SNAPSHOT/maven-shade-plugin-3.1.1-20180402.085120-121.jar Great thanks for your help... 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
[GitHub] khmarbaise commented on issue #1: Update ASM to latest version
khmarbaise commented on issue #1: Update ASM to latest version URL: https://github.com/apache/maven-shade-plugin/pull/1#issuecomment-377887753 Ok created on and provided like this: https://repository.apache.org/content/repositories/snapshots/org/apache/maven/plugins/maven-shade-plugin/3.1.1-SNAPSHOT/maven-shade-plugin-3.1.1-20180402.085120-121.jar 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
[GitHub] raphw commented on issue #1: Update ASM to latest version
raphw commented on issue #1: Update ASM to latest version URL: https://github.com/apache/maven-shade-plugin/pull/1#issuecomment-377886750 Absolutely. It should even work if you fork the repository https://github.com/raphw/byte-buddy as CI picks up all branches. 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] (MSHADE-282) Remove not used directories rel-path-test-files
Karl Heinz Marbaise created MSHADE-282: -- Summary: Remove not used directories rel-path-test-files Key: MSHADE-282 URL: https://issues.apache.org/jira/browse/MSHADE-282 Project: Maven Shade Plugin Issue Type: Dependency upgrade Affects Versions: 3.1.1 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.1.1 -- This message was sent by Atlassian JIRA (v7.6.3#76005)
