date:20180222

[jira] [Commented] (MRAR-71) Upgrade parent to 31

2018-02-22 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/MRAR-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16374026#comment-16374026
 ] 

Hudson commented on MRAR-71:


Build succeeded in Jenkins: Maven TLP » maven-rar-plugin » master #4

See https://builds.apache.org/job/maven-box/job/maven-rar-plugin/job/master/4/

> Upgrade parent to 31
> 
>
> Key: MRAR-71
> URL: https://issues.apache.org/jira/browse/MRAR-71
> Project: Maven Rar Plugin
>  Issue Type: Dependency upgrade
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MRAR-70) Upgrade plexus-utils 3.1.0

2018-02-22 Thread Karl Heinz Marbaise (JIRA)


 [ 
https://issues.apache.org/jira/browse/MRAR-70?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Heinz Marbaise closed MRAR-70.
---
Resolution: Fixed

Done in 
[5b83e94210ac3754bb9756ab912858704fc8cb3e|https://gitbox.apache.org/repos/asf?p=maven-rar-plugin.git;a=commitdiff;h=5b83e94210ac3754bb9756ab912858704fc8cb3e]

> Upgrade plexus-utils 3.1.0
> --
>
> Key: MRAR-70
> URL: https://issues.apache.org/jira/browse/MRAR-70
> Project: Maven Rar Plugin
>  Issue Type: Dependency upgrade
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Major
> Fix For: 3.0.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (SUREFIRE-1489) Implement lock() and zip() in jenkinsfile

2018-02-22 Thread Tibor Digana (JIRA)

Tibor Digana created SUREFIRE-1489:
--

 Summary: Implement lock() and zip() in jenkinsfile
 Key: SUREFIRE-1489
 URL: https://issues.apache.org/jira/browse/SUREFIRE-1489
 Project: Maven Surefire
  Issue Type: Task
Reporter: Tibor Digana
Assignee: Tibor Digana
 Fix For: 2.21.0


INFRA installed Groovy functions {{lock()}} and {{zip()}}.
jenkinsfile can be updated



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (ARCHETYPE-530) [archetype:create-from-project] Proxy configuration from settings.xml is not taken into account

2018-02-22 Thread Michal Telpski (JIRA)


[ 
https://issues.apache.org/jira/browse/ARCHETYPE-530?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373797#comment-16373797
 ] 

Michal Telpski commented on ARCHETYPE-530:
--

It looks like same applies to authentication to repositories using:
{code:java}

  id
  user
  pass
{code}
Command-line call:

{{mvn -s  archetype:create-from-project 
-Darchetype.postPhase=deploy}}

results in maven-deploy-plugin failure:

{{Could not transfer metadata from/to maven-snapshots: Not authorized , 
ReasonPhrase:Unauthorized. -> [Help 1]}}

although that call (w/o archetype generation) would work:

{{mvn -s  deploy}}

 

There is a workaround though: separate archetype creation and deployment:

{{mvn -s  archetype:create-from-project && mvn -s  -f 
target/generated-sources/archetype deploy}}

 

Btw. is this the same issue as originally reported one?

> [archetype:create-from-project] Proxy configuration from settings.xml is not 
> taken into account
> ---
>
> Key: ARCHETYPE-530
> URL: https://issues.apache.org/jira/browse/ARCHETYPE-530
> Project: Maven Archetype
>  Issue Type: Bug
>  Components: Plugin
>Affects Versions: 3.0.1
>Reporter: Vadym Lotar
>Priority: Major
>
> Hello,
> While trying to create an archetype out of source project applying global 
> settings.xml which contains proxy configuration, plugin fails with the 
> following error:
> {color:red}[INFO] Scanning for projects...
> [INFO] Downloading: 
> https://repo.maven.apache.org/maven2/org/apache/maven/archetype/archetype-packaging/3.0.1/archetype-packaging-3.0.1.pom
> [ERROR] [ERROR] Some problems were encountered while processing the POMs:
> [ERROR] Unresolveable build extension: Plugin 
> org.apache.maven.archetype:archetype-packaging:3.0.1 or one of its 
> dependencies could not be resolved: Failed to read artifact descriptor for 
> org.apache.maven.archetype:archetype-packaging:jar:3.0.1 @ 
> [ERROR] Unknown packaging: maven-archetype @ line 8, column 14
>  @ 
> [ERROR] The build could not read 1 project -> [Help 1]
> [ERROR]   
> [ERROR]   The project com.adidas.pc:kafka_consumer-archetype:1.0-SNAPSHOT 
> (/opt/jenkins/workspace/PC/pcdsp/archetypes/kafka-consumer-archetype-build/target/generated-sources/archetype/pom.xml)
>  has 2 errors
> [ERROR] Unresolveable build extension: Plugin 
> org.apache.maven.archetype:archetype-packaging:3.0.1 or one of its 
> dependencies could not be resolved: Failed to read artifact descriptor for 
> org.apache.maven.archetype:archetype-packaging:jar:3.0.1: Could not transfer 
> artifact org.apache.maven.archetype:archetype-packaging:pom:3.0.1 from/to 
> central (https://repo.maven.apache.org/maven2): Connect to 
> repo.maven.apache.org:443 [repo.maven.apache.org/151.101.112.215] failed: 
> Connection timed out (Connection timed out) -> [Help 2]
> [ERROR] Unknown packaging: maven-archetype @ line 8, column 14{color}
> It appeared that the plugin creates new 
> org.apache.maven.shared.invoker.InvocationRequest to "package" the archetype 
> without applying configuration specified in settings.xml.
> Being more precise, I feel like the invocation request itself has to be built 
> in a little bit different way here, so local and global settings.xml are 
> passed:
> org/apache/maven/archetype/creator/FilesetArchetypeCreator.java:281
> Please, let me know if more information needs to be provided.
> Best.
> 
> {color:red}[ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-archetype-plugin:3.0.1:create-from-project 
> (default-cli) on project kafka_consumer: Invoker process ended with result 
> different than 0! -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal 
> org.apache.maven.plugins:maven-archetype-plugin:3.0.1:create-from-project 
> (default-cli) on project kafka_consumer: Invoker process ended with result 
> different than 0!
>   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

[jira] [Commented] (MNG-6286) ArrayIndexOutOfBoundsException: MXParser.java:2502

2018-02-22 Thread JIRA


[ 
https://issues.apache.org/jira/browse/MNG-6286?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373699#comment-16373699
 ] 

Jörg Hohwiller commented on MNG-6286:
-

Retested with 3.5.2 - works like a charm. Thanks so much. Awesome. Colors in 
console log!

> ArrayIndexOutOfBoundsException: MXParser.java:2502
> --
>
> Key: MNG-6286
> URL: https://issues.apache.org/jira/browse/MNG-6286
> Project: Maven
>  Issue Type: Bug
>  Components: core
>Affects Versions: 3.5.0
> Environment: Apache Maven 3.5.0 
> (ff8f5e7444045639af65f6095c62210b5713f426; 2017-04-03T21:39:06+02:00)
> Java version: 1.8.0_111, vendor: Oracle Corporation
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "windows"
>Reporter: Jörg Hohwiller
>Assignee: Robert Scholte
>Priority: Major
>
> I found a regression bug with maven 3.5.0. The error I get is:
> {code}
> [ERROR] 24777
> java.lang.ArrayIndexOutOfBoundsException: 24777
> at 
> org.codehaus.plexus.util.xml.pull.MXParser.parsePI(MXParser.java:2502)
> at 
> org.codehaus.plexus.util.xml.pull.MXParser.parseEpilog(MXParser.java:1604)
> at 
> org.codehaus.plexus.util.xml.pull.MXParser.nextImpl(MXParser.java:1434)
> at org.codehaus.plexus.util.xml.pull.MXParser.next(MXParser.java:1131)
> at 
> org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:3856)
> at 
> org.apache.maven.model.io.xpp3.MavenXpp3Reader.read(MavenXpp3Reader.java:595)
> at 
> org.apache.maven.model.io.DefaultModelReader.read(DefaultModelReader.java:109)
> at 
> org.apache.maven.model.io.DefaultModelReader.read(DefaultModelReader.java:82)
> at 
> org.apache.maven.model.building.DefaultModelProcessor.read(DefaultModelProcessor.java:81)
> at 
> org.apache.maven.model.building.DefaultModelBuilder.readModel(DefaultModelBuilder.java:535)
> at 
> org.apache.maven.model.building.DefaultModelBuilder.readParentExternally(DefaultModelBuilder.java:1097)
> at 
> org.apache.maven.model.building.DefaultModelBuilder.readParent(DefaultModelBuilder.java:829)
> at 
> org.apache.maven.model.building.DefaultModelBuilder.build(DefaultModelBuilder.java:331)
> at 
> org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.loadPom(DefaultArtifactDescriptorReader.java:321)
> at 
> org.apache.maven.repository.internal.DefaultArtifactDescriptorReader.readArtifactDescriptor(DefaultArtifactDescriptorReader.java:199)
> at 
> org.eclipse.aether.internal.impl.DefaultDependencyCollector.resolveCachedArtifactDescriptor(DefaultDependencyCollector.java:544)
> at 
> org.eclipse.aether.internal.impl.DefaultDependencyCollector.getArtifactDescriptorResult(DefaultDependencyCollector.java:528)
> at 
> org.eclipse.aether.internal.impl.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:418)
> at 
> org.eclipse.aether.internal.impl.DefaultDependencyCollector.processDependency(DefaultDependencyCollector.java:372)
> at 
> org.eclipse.aether.internal.impl.DefaultDependencyCollector.process(DefaultDependencyCollector.java:360)
> at 
> org.eclipse.aether.internal.impl.DefaultDependencyCollector.collectDependencies(DefaultDependencyCollector.java:263)
> at 
> org.eclipse.aether.internal.impl.DefaultRepositorySystem.collectDependencies(DefaultRepositorySystem.java:325)
> at 
> org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(DefaultProjectDependenciesResolver.java:169)
> at 
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.getDependencies(LifecycleDependencyResolver.java:195)
> at 
> org.apache.maven.lifecycle.internal.LifecycleDependencyResolver.resolveProjectDependencies(LifecycleDependencyResolver.java:127)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.ensureDependenciesAreResolved(MojoExecutor.java:246)
> at 
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:200)
> 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

[jira] [Commented] (MRAR-70) Upgrade plexus-utils 3.1.0

2018-02-22 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/MRAR-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373648#comment-16373648
 ] 

Hudson commented on MRAR-70:


Build succeeded in Jenkins: Maven TLP » maven-rar-plugin » MRAR-71 #2

See https://builds.apache.org/job/maven-box/job/maven-rar-plugin/job/MRAR-71/2/

> Upgrade plexus-utils 3.1.0
> --
>
> Key: MRAR-70
> URL: https://issues.apache.org/jira/browse/MRAR-70
> Project: Maven Rar Plugin
>  Issue Type: Dependency upgrade
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Major
> Fix For: 3.0.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MRAR-71) Upgrade parent to 31

2018-02-22 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/MRAR-71?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373649#comment-16373649
 ] 

Hudson commented on MRAR-71:


Build succeeded in Jenkins: Maven TLP » maven-rar-plugin » MRAR-71 #2

See https://builds.apache.org/job/maven-box/job/maven-rar-plugin/job/MRAR-71/2/

> Upgrade parent to 31
> 
>
> Key: MRAR-71
> URL: https://issues.apache.org/jira/browse/MRAR-71
> Project: Maven Rar Plugin
>  Issue Type: Dependency upgrade
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MRAR-70) Upgrade plexus-utils 3.1.0

2018-02-22 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/MRAR-70?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373645#comment-16373645
 ] 

Hudson commented on MRAR-70:


Build succeeded in Jenkins: Maven TLP » maven-rar-plugin » master #3

See https://builds.apache.org/job/maven-box/job/maven-rar-plugin/job/master/3/

> Upgrade plexus-utils 3.1.0
> --
>
> Key: MRAR-70
> URL: https://issues.apache.org/jira/browse/MRAR-70
> Project: Maven Rar Plugin
>  Issue Type: Dependency upgrade
>Affects Versions: 3.0.0
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Major
> Fix For: 3.0.0
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MSITE-811) Upgrade parent to 31

2018-02-22 Thread Karl Heinz Marbaise (JIRA)

Karl Heinz Marbaise created MSITE-811:
-

 Summary: Upgrade parent to 31
 Key: MSITE-811
 URL: https://issues.apache.org/jira/browse/MSITE-811
 Project: Maven Site Plugin
  Issue Type: Improvement
Affects Versions: 3.7.1
Reporter: Karl Heinz Marbaise
Assignee: Karl Heinz Marbaise
 Fix For: 3.7.1






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MTOOLCHAINS-22) Upgrade parent to 31

2018-02-22 Thread Karl Heinz Marbaise (JIRA)

Karl Heinz Marbaise created MTOOLCHAINS-22:
--

 Summary: Upgrade parent to 31
 Key: MTOOLCHAINS-22
 URL: https://issues.apache.org/jira/browse/MTOOLCHAINS-22
 Project: Maven Toolchains Plugin
  Issue Type: Improvement
Affects Versions: 3.0.0
Reporter: Karl Heinz Marbaise
Assignee: Karl Heinz Marbaise
 Fix For: 3.0.0






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MVERIFIER-24) Upgrade parent to 31

2018-02-22 Thread Karl Heinz Marbaise (JIRA)

Karl Heinz Marbaise created MVERIFIER-24:


 Summary: Upgrade parent to 31
 Key: MVERIFIER-24
 URL: https://issues.apache.org/jira/browse/MVERIFIER-24
 Project: Maven Verifier Plugin
  Issue Type: Improvement
Affects Versions: 3.0.0
Reporter: Karl Heinz Marbaise
Assignee: Karl Heinz Marbaise
 Fix For: 3.0.0






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (MJAR-245) Additional attached jar: role of classifyer

2018-02-22 Thread Karl Heinz Marbaise (JIRA)


 [ 
https://issues.apache.org/jira/browse/MJAR-245?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Heinz Marbaise updated MJAR-245:
-
Fix Version/s: 3.1.0

> Additional attached jar: role of classifyer 
> 
>
> Key: MJAR-245
> URL: https://issues.apache.org/jira/browse/MJAR-245
> Project: Maven JAR Plugin
>  Issue Type: Bug
>  Components: site
>Affects Versions: 3.0.2
>Reporter: Ernst Reissner
>Priority: Major
> Fix For: 3.1.0
>
>
> On 
> [https://maven.apache.org/plugins/maven-jar-plugin/examples/attached-jar.html,]
> a classifier is given.
> Missing information: creates a jar file:
> project-version-classifier.jar.
> This is vital.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MJAR-244) Missing documentation: unsatisfied link

2018-02-22 Thread Karl Heinz Marbaise (JIRA)


 [ 
https://issues.apache.org/jira/browse/MJAR-244?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Heinz Marbaise closed MJAR-244.

Resolution: Duplicate

> Missing documentation: unsatisfied link 
> 
>
> Key: MJAR-244
> URL: https://issues.apache.org/jira/browse/MJAR-244
> Project: Maven JAR Plugin
>  Issue Type: Bug
>  Components: site
>Affects Versions: 3.0.2
>Reporter: Ernst Reissner
>Priority: Major
>
> On homepage [https://maven.apache.org/plugins/maven-jar-plugin/]
> the link "Creating an executable jar file" is not satisfied.
> Is this no longer possible? Then this has to be removed.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MWAR-412) Upgrade parent to 31

2018-02-22 Thread Karl Heinz Marbaise (JIRA)

Karl Heinz Marbaise created MWAR-412:


 Summary: Upgrade parent to 31
 Key: MWAR-412
 URL: https://issues.apache.org/jira/browse/MWAR-412
 Project: Maven WAR Plugin
  Issue Type: Improvement
Affects Versions: 3.3.0
Reporter: Karl Heinz Marbaise
Assignee: Karl Heinz Marbaise
 Fix For: 3.3.0






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MSOURCES-110) Add IT to prevent readonly=true problem with parameter

2018-02-22 Thread Karl Heinz Marbaise (JIRA)

Karl Heinz Marbaise created MSOURCES-110:


 Summary: Add IT to prevent readonly=true problem with parameter
 Key: MSOURCES-110
 URL: https://issues.apache.org/jira/browse/MSOURCES-110
 Project: Maven Source Plugin
  Issue Type: Improvement
Affects Versions: 3.0.2
Reporter: Karl Heinz Marbaise
 Fix For: 3.0.2


We should add an integration test to prevent adding a {{readonly=true}} to 
parameters. 



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MSOURCES-109) Upgrade parent to 31

2018-02-22 Thread Karl Heinz Marbaise (JIRA)


 [ 
https://issues.apache.org/jira/browse/MSOURCES-109?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Heinz Marbaise closed MSOURCES-109.

Resolution: Fixed

Done in 
[b58d27605f761c41380a3c6c5cc35ad159ebed38|https://gitbox.apache.org/repos/asf?p=maven-source-plugin.git;a=commitdiff;h=b58d27605f761c41380a3c6c5cc35ad159ebed38]

> Upgrade parent to 31
> 
>
> Key: MSOURCES-109
> URL: https://issues.apache.org/jira/browse/MSOURCES-109
> Project: Maven Source Plugin
>  Issue Type: Improvement
>Affects Versions: 3.0.2
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.2
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Reopened] (MSOURCES-108) Remove the readonly=true from finalName

2018-02-22 Thread Robert Scholte (JIRA)


 [ 
https://issues.apache.org/jira/browse/MSOURCES-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Robert Scholte reopened MSOURCES-108:
-

Please add an integration test to prevent regression in the future. It is quite 
easy to add the readOnly again in the future, since that's what we do for most 
packaging plugins.

> Remove the readonly=true from finalName
> ---
>
> Key: MSOURCES-108
> URL: https://issues.apache.org/jira/browse/MSOURCES-108
> Project: Maven Source Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.2
>
>
> The current parameter {{finalName}} is defined with {{readonly = true}} which 
> I think is wrong, cause it makes sense to set it...
> Use case: 
> https://stackoverflow.com/questions/48918003/how-to-include-source-code-inside-the-mvn-built-jar



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MSOURCES-109) Upgrade parent to 31

2018-02-22 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/MSOURCES-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373380#comment-16373380
 ] 

Hudson commented on MSOURCES-109:
-

Build succeeded in Jenkins: Maven TLP » maven-source-plugin » master #4

See 
https://builds.apache.org/job/maven-box/job/maven-source-plugin/job/master/4/

> Upgrade parent to 31
> 
>
> Key: MSOURCES-109
> URL: https://issues.apache.org/jira/browse/MSOURCES-109
> Project: Maven Source Plugin
>  Issue Type: Improvement
>Affects Versions: 3.0.2
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.2
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MSOURCES-108) Remove the readonly=true from finalName

2018-02-22 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/MSOURCES-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373349#comment-16373349
 ] 

Hudson commented on MSOURCES-108:
-

Build succeeded in Jenkins: Maven TLP » maven-source-plugin » master #3

See 
https://builds.apache.org/job/maven-box/job/maven-source-plugin/job/master/3/

> Remove the readonly=true from finalName
> ---
>
> Key: MSOURCES-108
> URL: https://issues.apache.org/jira/browse/MSOURCES-108
> Project: Maven Source Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.2
>
>
> The current parameter {{finalName}} is defined with {{readonly = true}} which 
> I think is wrong, cause it makes sense to set it...
> Use case: 
> https://stackoverflow.com/questions/48918003/how-to-include-source-code-inside-the-mvn-built-jar



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MSOURCES-108) Remove the readonly=true from finalName

2018-02-22 Thread Karl Heinz Marbaise (JIRA)


 [ 
https://issues.apache.org/jira/browse/MSOURCES-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Heinz Marbaise closed MSOURCES-108.

Resolution: Fixed

Fixed in 
[c45a5a5e3c8d353ae2f270ae45438fac390b559d|https://gitbox.apache.org/repos/asf?p=maven-source-plugin.git;a=commitdiff;h=c45a5a5e3c8d353ae2f270ae45438fac390b559d]

> Remove the readonly=true from finalName
> ---
>
> Key: MSOURCES-108
> URL: https://issues.apache.org/jira/browse/MSOURCES-108
> Project: Maven Source Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.2
>
>
> The current parameter {{finalName}} is defined with {{readonly = true}} which 
> I think is wrong, cause it makes sense to set it...
> Use case: 
> https://stackoverflow.com/questions/48918003/how-to-include-source-code-inside-the-mvn-built-jar



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MSOURCES-108) Remove the readonly=true from finalName

2018-02-22 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/MSOURCES-108?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373357#comment-16373357
 ] 

Hudson commented on MSOURCES-108:
-

Build succeeded in Jenkins: Maven TLP » maven-source-plugin » MSOURCES-109 #2

See 
https://builds.apache.org/job/maven-box/job/maven-source-plugin/job/MSOURCES-109/2/

> Remove the readonly=true from finalName
> ---
>
> Key: MSOURCES-108
> URL: https://issues.apache.org/jira/browse/MSOURCES-108
> Project: Maven Source Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.2
>
>
> The current parameter {{finalName}} is defined with {{readonly = true}} which 
> I think is wrong, cause it makes sense to set it...
> Use case: 
> https://stackoverflow.com/questions/48918003/how-to-include-source-code-inside-the-mvn-built-jar



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MSOURCES-109) Upgrade parent to 31

2018-02-22 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/MSOURCES-109?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373358#comment-16373358
 ] 

Hudson commented on MSOURCES-109:
-

Build succeeded in Jenkins: Maven TLP » maven-source-plugin » MSOURCES-109 #2

See 
https://builds.apache.org/job/maven-box/job/maven-source-plugin/job/MSOURCES-109/2/

> Upgrade parent to 31
> 
>
> Key: MSOURCES-109
> URL: https://issues.apache.org/jira/browse/MSOURCES-109
> Project: Maven Source Plugin
>  Issue Type: Improvement
>Affects Versions: 3.0.2
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.2
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MSOURCES-109) Upgrade parent to 31

2018-02-22 Thread Karl Heinz Marbaise (JIRA)

Karl Heinz Marbaise created MSOURCES-109:


 Summary: Upgrade parent to 31
 Key: MSOURCES-109
 URL: https://issues.apache.org/jira/browse/MSOURCES-109
 Project: Maven Source Plugin
  Issue Type: Improvement
Affects Versions: 3.0.2
Reporter: Karl Heinz Marbaise
Assignee: Karl Heinz Marbaise
 Fix For: 3.0.2






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (MSOURCES-108) Remove the readonly=true from finalName

2018-02-22 Thread Karl Heinz Marbaise (JIRA)


 [ 
https://issues.apache.org/jira/browse/MSOURCES-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Heinz Marbaise updated MSOURCES-108:
-
Description: 
The current parameter {{finalName}} is defined with {{readonly = true}} which I 
think is wrong, cause it makes sense to set it...

Use case: 
https://stackoverflow.com/questions/48918003/how-to-include-source-code-inside-the-mvn-built-jar

  was:The current parameter {{finalName}} is defined with {{readonly = true}} 
which I think is wrong, cause it makes sense to set it...


> Remove the readonly=true from finalName
> ---
>
> Key: MSOURCES-108
> URL: https://issues.apache.org/jira/browse/MSOURCES-108
> Project: Maven Source Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.2
>
>
> The current parameter {{finalName}} is defined with {{readonly = true}} which 
> I think is wrong, cause it makes sense to set it...
> Use case: 
> https://stackoverflow.com/questions/48918003/how-to-include-source-code-inside-the-mvn-built-jar



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (MSOURCES-108) Remove the readonly=true from finalName

2018-02-22 Thread Karl Heinz Marbaise (JIRA)


 [ 
https://issues.apache.org/jira/browse/MSOURCES-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Heinz Marbaise updated MSOURCES-108:
-
Description: The current parameter {{finalName}} is defined with {{readonly 
= true}} which I think is wrong, cause it makes sense to set it...  (was: 
Currently the [documentation 
states|https://maven.apache.org/plugins/maven-source-plugin/examples/configureplugin.html]
 to be able to set {{finalName}} which is not possible cause the {{finalName}} 
is defined {{readonly}} in code and does not has any effect.)

> Remove the readonly=true from finalName
> ---
>
> Key: MSOURCES-108
> URL: https://issues.apache.org/jira/browse/MSOURCES-108
> Project: Maven Source Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.2
>
>
> The current parameter {{finalName}} is defined with {{readonly = true}} which 
> I think is wrong, cause it makes sense to set it...



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Updated] (MSOURCES-108) Remove the readonly=true from finalName

2018-02-22 Thread Karl Heinz Marbaise (JIRA)


 [ 
https://issues.apache.org/jira/browse/MSOURCES-108?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Heinz Marbaise updated MSOURCES-108:
-
Summary: Remove the readonly=true from finalName  (was: Remove the 
mentioned finalName cause it can't be set)

> Remove the readonly=true from finalName
> ---
>
> Key: MSOURCES-108
> URL: https://issues.apache.org/jira/browse/MSOURCES-108
> Project: Maven Source Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.2
>
>
> Currently the [documentation 
> states|https://maven.apache.org/plugins/maven-source-plugin/examples/configureplugin.html]
>  to be able to set {{finalName}} which is not possible cause the 
> {{finalName}} is defined {{readonly}} in code and does not has any effect.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MRESOURCES-242) Fix integration test include-git-ignore

2018-02-22 Thread Karl Heinz Marbaise (JIRA)


 [ 
https://issues.apache.org/jira/browse/MRESOURCES-242?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Heinz Marbaise closed MRESOURCES-242.
--
Resolution: Fixed

Done in 
[92395368f8f6511adafdcae3453d33e630f05c1a|https://gitbox.apache.org/repos/asf?p=maven-resources-plugin.git;a=commitdiff;h=92395368f8f6511adafdcae3453d33e630f05c1a]

> Fix integration test include-git-ignore
> ---
>
> Key: MRESOURCES-242
> URL: https://issues.apache.org/jira/browse/MRESOURCES-242
> Project: Maven Resources Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.3
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Blocker
> Fix For: 3.0.3
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Closed] (MRESOURCES-241) Upgrade parent to 31

2018-02-22 Thread Karl Heinz Marbaise (JIRA)


 [ 
https://issues.apache.org/jira/browse/MRESOURCES-241?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Heinz Marbaise closed MRESOURCES-241.
--
Resolution: Fixed

Done in 
[26368d4264fb7627de34a642e8c2e35901410533|https://gitbox.apache.org/repos/asf?p=maven-resources-plugin.git;a=commitdiff;h=26368d4264fb7627de34a642e8c2e35901410533]

> Upgrade parent to 31
> 
>
> Key: MRESOURCES-241
> URL: https://issues.apache.org/jira/browse/MRESOURCES-241
> Project: Maven Resources Plugin
>  Issue Type: Dependency upgrade
>Affects Versions: 3.0.3
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.3
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MSOURCES-108) Remove the mentioned finalName cause it can't be set

2018-02-22 Thread Karl Heinz Marbaise (JIRA)

Karl Heinz Marbaise created MSOURCES-108:


 Summary: Remove the mentioned finalName cause it can't be set
 Key: MSOURCES-108
 URL: https://issues.apache.org/jira/browse/MSOURCES-108
 Project: Maven Source Plugin
  Issue Type: Bug
Affects Versions: 3.0.1
Reporter: Karl Heinz Marbaise
Assignee: Karl Heinz Marbaise
 Fix For: 3.0.2


Currently the [documentation 
states|https://maven.apache.org/plugins/maven-source-plugin/examples/configureplugin.html]
 to be able to set {{finalName}} which is not possible cause the {{finalName}} 
is defined {{readonly}} in code and does not has any effect.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MRESOURCES-242) Fix integration test include-git-ignore

2018-02-22 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/MRESOURCES-242?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373274#comment-16373274
 ] 

Hudson commented on MRESOURCES-242:
---

Build succeeded in Jenkins: Maven TLP » maven-resources-plugin » master #4

See 
https://builds.apache.org/job/maven-box/job/maven-resources-plugin/job/master/4/

> Fix integration test include-git-ignore
> ---
>
> Key: MRESOURCES-242
> URL: https://issues.apache.org/jira/browse/MRESOURCES-242
> Project: Maven Resources Plugin
>  Issue Type: Bug
>Affects Versions: 3.0.3
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Blocker
> Fix For: 3.0.3
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MRESOURCES-242) Fix integration test include-git-ignore

2018-02-22 Thread Karl Heinz Marbaise (JIRA)

Karl Heinz Marbaise created MRESOURCES-242:
--

 Summary: Fix integration test include-git-ignore
 Key: MRESOURCES-242
 URL: https://issues.apache.org/jira/browse/MRESOURCES-242
 Project: Maven Resources Plugin
  Issue Type: Bug
Affects Versions: 3.0.3
Reporter: Karl Heinz Marbaise
Assignee: Karl Heinz Marbaise
 Fix For: 3.0.3






--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MJAVADOC-427) "Error fetching URL" for valid non-Java API links

2018-02-22 Thread JIRA


[ 
https://issues.apache.org/jira/browse/MJAVADOC-427?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373244#comment-16373244
 ] 

Guillaume Boué commented on MJAVADOC-427:
-

Yes, since {{javadoc}} currently doesn't follow redirects, we can do it in the 
plugin and then feed {{javadoc}} the last redirect location. I'll work on this.

> "Error fetching URL" for valid non-Java API links
> -
>
> Key: MJAVADOC-427
> URL: https://issues.apache.org/jira/browse/MJAVADOC-427
> Project: Maven Javadoc Plugin
>  Issue Type: Bug
>Affects Versions: 2.10.3
> Environment: Windows 7
> Apache Maven 3.2.1
> java version "1.8.0_05"
> Java(TM) SE Runtime Environment (build 1.8.0_05-b13)
> Java HotSpot(TM) 64-Bit Server VM (build 25.5-b02, mixed mode)
>Reporter: Selena Renee Phillips
>Priority: Major
> Attachments: testcase-detectLinks-enabled-no-manual-link-config.zip, 
> testcase-detectLinks-enabled-with-manual-link-config-no-trailing-slash.zip, 
> testcase-detectLinks-enabled-with-manual-link-config-trailing-slash.zip, 
> testcases-detectLinks-disabled-with-manual-link-config-no-trailing-slash.zip, 
> testcases-detectLinks-disabled-with-manual-link-config-trailing-slash.zip
>
>
> When I generate Javadoc for a simple project with 3rd party dependencies, no 
> configuration generates links for these dependencies. For valid Javadoc links 
> which have a package-list, I get the following error:
> [WARNING] javadoc: warning - Error fetching URL
> Test Cases w/ results (sample project(s)) attached:
> *1. No manual link configuration. 'detectLinks' is set to true.*
> {code:title=pom.xml - No manual link configuration with 
> detectLinks=true|borderStyle=solid}
> 
> org.apache.maven.plugins
> maven-javadoc-plugin
> 2.10.3
> 
> 
> ${project.basedir}/target
> javadoc
> Epiphany
> Epiphany
> private
> true
> true
> true
> true
> 
> 
> 
> 
> javadoc
> test-javadoc
> 
> 
> 
> 
> {code}
> Output of 'mvn javadoc:javadoc':
> {code:title=Resulting output for mvn javadoc:javadoc - No manual link 
> configuration with detectLinks=true|borderStyle=solid}
> [INFO] Scanning for projects...
> [INFO]
> [INFO] Using the builder 
> org.apache.maven.lifecycle.internal.builder.singlethreaded.SingleThreadedBuilder
>  with a thread count of 1
> [INFO]
> [INFO] 
> 
> [INFO] Building epiphany 1.0-SNAPSHOT
> [INFO] 
> 
> [INFO]
> [INFO] >>> maven-javadoc-plugin:2.10.3:javadoc (default-cli) @ epiphany >>>
> [INFO]
> [INFO] <<< maven-javadoc-plugin:2.10.3:javadoc (default-cli) @ epiphany <<<
> SNIP DOWNLOADING INFO.
> [INFO]
> [INFO] --- maven-javadoc-plugin:2.10.3:javadoc (default-cli) @ epiphany ---
> [ERROR] Error fetching link: 
> http://selenium.googlecode.com/selenium-java/apidocs/package-list. Ignored it.
> [ERROR] Error fetching link: 
> http://selenium.googlecode.com/selenium-api/apidocs/package-list. Ignored it.
> [ERROR] Error fetching link: 
> http://selenium.googlecode.com/selenium-support/apidocs/package-list. Ignored 
> it.
> [ERROR] Error fetching link: 
> http://code.google.com/p/guava-libraries/guava/apidocs/package-list. Ignored 
> it.
> [ERROR] Error fetching link: 
> http://logback.qos.ch/logback-core/apidocs/package-list. Ignored it.
> [ERROR] Error fetching link: 
> http://logback.qos.ch/logback-classic/apidocs/package-list. Ignored it.
> [ERROR] Error fetching link: http://testng.org/apidocs/package-list. Ignored 
> it.
> [INFO]
> Loading source files for package com.example...
> Constructing Javadoc information...
> Standard Doclet version 1.8.0_05
> Building tree for all the packages and classes...
> Generating 
> C:\Users\sephilli\git\javadoc-bug\target\javadoc\com\example\AbstractLoadable.html...
> .SNIP
> 1 warning
> [WARNING] Javadoc Warnings
> [WARNING] javadoc: warning - Error fetching URL: http://www.slf4j.org/apidocs
> [INFO] 
> 
> [INFO] BUILD SUCCESS
> [INFO] 
> 
> [INFO] Total time: 13.694 s
> [INFO] Finished at: 2015-04-18T08:24:05-05:00
> [INFO] Final Memory: 16M/92M
> [INFO] 
> 
> {code}
> I expected

[jira] [Commented] (MNG-6359) Non-resolvable parent POM with gitbash (MINGW64_NT-10.0)

2018-02-22 Thread JIRA


[ 
https://issues.apache.org/jira/browse/MNG-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373242#comment-16373242
 ] 

Guillaume Boué commented on MNG-6359:
-

You can run the build in debug mode with the {{-X}} flag, which could help 
track down the issue (by comparing logs for example). By the way, are you sure 
that you're running the same Maven version in cmd.exe and Git Bash? Check with 
{{mvn --version}}.

> Non-resolvable parent POM with gitbash (MINGW64_NT-10.0)
> 
>
> Key: MNG-6359
> URL: https://issues.apache.org/jira/browse/MNG-6359
> Project: Maven
>  Issue Type: Bug
>  Components: POM
>Affects Versions: 3.5.0, 3.5.2
> Environment: Run from gitbash
> GNU bash, version 4.4.12(1)-release (x86_64-pc-msys)
> Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d; 
> 2017-10-18T08:58:13+01:00)
> Maven home: C:\Program Files\Apache\maven
> Java version: 1.8.0_161, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_161\jre
> Default locale: en_IE, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>Reporter: Ian Dunbar
>Priority: Minor
> Attachments: mm.zip
>
>
> The attached multimodule example fails to build when run from gitbash on 
> windows 10. I've derived it from this example 
> [https://github.com/jamesward/maven-multi-module-example] but modified to 
> match my scenario.
> It works fine from CMD shell on the same machine with the same Apache Maven 
> install. It's only with gitbash that the issue occurs. I see that the mvn 
> launcher has specific sections for mingw derived shells like gitbash, so 
> possibly something is wrong there.
>  
> The issue occurs when the project has no artifacts yet in .m2 repo. So please 
> remove .m2/repository/com/jamesward prior to testing.
> The transition from working to non-working in gitbash is with the addition of 
> the parent section in the toplevel pom.xml, so there seems to be something 
> wrong with the parent resolution in the toplevel when run from gitbash
> Steps:
>  * remove .m2/repository/com/jamesward
>  * unzip the example
>  * run gitbash in that folder
>  * mvn clean install
>  * *fails to build*
>  * 
>  * change to cmd.exe
>  * mvn clean install
>  * *builds correctly*
> Error log:
>  
> {{[INFO] Scanning for projects...}}
> {{[ERROR] [ERROR] Some problems were encountered while processing the POMs:}}
> {{[FATAL] Non-resolvable parent POM for com.jamesward:core:1.0-SNAPSHOT: 
> Could not find artifact com.jamesward:parent:pom:1.0-SNAPSHOT and 
> 'parent.relativePath' points at wrong local POM @ line 6, column 13}}
> {{[FATAL] Non-resolvable parent POM for com.jamesward:app:[unknown-version]: 
> Could not find artifact com.jamesward:parent:pom:1.0-SNAPSHOT and 
> 'parent.relativePath' points at wrong local POM @ line 6, column 13}}
> {{ @}}
> {{[ERROR] The build could not read 2 projects -> [Help 1]}}
> {{[ERROR]}}
> {{[ERROR] The project com.jamesward:core:1.0-SNAPSHOT (C:\mm\core\pom.xml) 
> has 1 error}}
> {{[ERROR] Non-resolvable parent POM for com.jamesward:core:1.0-SNAPSHOT: 
> Could not find artifact com.jamesward:parent:pom:1.0-SNAPSHOT and 
> 'parent.relativePath' points at wrong local POM @ line 6, column 13 -> [Help 
> 2]}}
> {{[ERROR]}}
> {{[ERROR] The project com.jamesward:app:[unknown-version] (C:\mm\app\pom.xml) 
> has 1 error}}
> {{[ERROR] Non-resolvable parent POM for com.jamesward:app:[unknown-version]: 
> Could not find artifact com.jamesward:parent:pom:1.0-SNAPSHOT and 
> 'parent.relativePath' points at wrong local POM @ line 6, column 13 -> [Help 
> 2]}}
> {{[ERROR]}}
> {{[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.}}
> {{[ERROR] Re-run Maven using the -X switch to enable full debug logging.}}
> {{[ERROR]}}
> {{[ERROR] For more information about the errors and possible solutions, 
> please read the following articles:}}
> {{[ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException}}
> {{[ERROR] [Help 2] 
> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (MRESOURCES-239) Resources do not copy with Maven 3.3.9

2018-02-22 Thread Karl Heinz Marbaise (JIRA)


[ 
https://issues.apache.org/jira/browse/MRESOURCES-239?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373237#comment-16373237
 ] 

Karl Heinz Marbaise edited comment on MRESOURCES-239 at 2/22/18 6:47 PM:
-

The simple solution is that the {{filtering}} does not belong into 
{{resources}} it belongs into {{resource}} tag instead which means it should 
look like this:
{code:xml}



org.apache.maven.plugins
maven-resources-plugin
3.0.2

true

${project.build.directory}/allConfig



true

src/main/resources





{code}
Apart from the misplaces {{}} in the {{outputDirectory}} tag.

And yes I've checked with Maven 3.3.3 and previous versions which erroneously 
accepted this wrong configuration.


was (Author: khmarbaise):
The simple solution is that the {{filtering}} does not belong into 
{{resources}} it belongs into {{resource}} tag instead which means it should 
look like this:
{code:xml}



org.apache.maven.plugins
maven-resources-plugin
3.0.2

true

${project.build.directory}/allConfig



true

src/main/resources





{code}
Apart from the misplaces {{}} in the {{outputDirectory}} tag.


> Resources do not copy with Maven 3.3.9
> --
>
> Key: MRESOURCES-239
> URL: https://issues.apache.org/jira/browse/MRESOURCES-239
> Project: Maven Resources Plugin
>  Issue Type: Bug
>  Components: copy
>Affects Versions: 3.0.2
>Reporter: Kory Lasker
>Priority: Major
> Attachments: testingMaven.7z
>
>
> Using a simple POM, I try to copy a filtered file to a specific output 
> directory:
> {code}
> http://maven.apache.org/POM/4.0.0; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
>   4.0.0
>   me.app
>   testingMaven
>   0.0.1-SNAPSHOT
>   
>   
>   
>   
>   org.apache.maven.plugins
>   maven-resources-plugin
>   3.0.2
>   
>   true
>   
> ${project.build.directory}/allConfig}
>   
>   true
>   
>   
> src/main/resources
>   
>   
>   
>   
>   
>   
>   
>   
>   dev
>   
>   Development Build 
> ${maven.build.timestamp}
>   
>   
>   
> 
> {code}
> I then run mvn resources::resources -P dev with debugging and get this:
> {code}
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 
> 2015-11-10T10:41:47-06:00)
> Maven home: C:\Program Files (x86)\apache-maven-3.3.9
> Java version: 1.8.0_131, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_131\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos"
> [DEBUG] Created new class realm maven.api
> [DEBUG] Importing foreign packages into class realm maven.api
> [DEBUG]   Imported: javax.enterprise.inject.* < plexus.core
> [DEBUG]   Imported: javax.enterprise.util.* < plexus.core
> [DEBUG]   Imported:

[jira] [Closed] (MRESOURCES-239) Resources do not copy with Maven 3.3.9

2018-02-22 Thread Karl Heinz Marbaise (JIRA)


 [ 
https://issues.apache.org/jira/browse/MRESOURCES-239?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Heinz Marbaise closed MRESOURCES-239.
--
Resolution: Not A Bug

The simple solution is that the {{filtering}} does not belong into 
{{resources}} it belongs into {{resource}} tag instead which means it should 
look like this:
{code:xml}



org.apache.maven.plugins
maven-resources-plugin
3.0.2

true

${project.build.directory}/allConfig



true

src/main/resources





{code}
Apart from the misplaces {{}} in the {{outputDirectory}} tag.


> Resources do not copy with Maven 3.3.9
> --
>
> Key: MRESOURCES-239
> URL: https://issues.apache.org/jira/browse/MRESOURCES-239
> Project: Maven Resources Plugin
>  Issue Type: Bug
>  Components: copy
>Affects Versions: 3.0.2
>Reporter: Kory Lasker
>Priority: Major
> Attachments: testingMaven.7z
>
>
> Using a simple POM, I try to copy a filtered file to a specific output 
> directory:
> {code}
> http://maven.apache.org/POM/4.0.0; 
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
>   xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
>   4.0.0
>   me.app
>   testingMaven
>   0.0.1-SNAPSHOT
>   
>   
>   
>   
>   org.apache.maven.plugins
>   maven-resources-plugin
>   3.0.2
>   
>   true
>   
> ${project.build.directory}/allConfig}
>   
>   true
>   
>   
> src/main/resources
>   
>   
>   
>   
>   
>   
>   
>   
>   dev
>   
>   Development Build 
> ${maven.build.timestamp}
>   
>   
>   
> 
> {code}
> I then run mvn resources::resources -P dev with debugging and get this:
> {code}
> Apache Maven 3.3.9 (bb52d8502b132ec0a5a3f4c09453c07478323dc5; 
> 2015-11-10T10:41:47-06:00)
> Maven home: C:\Program Files (x86)\apache-maven-3.3.9
> Java version: 1.8.0_131, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_131\jre
> Default locale: en_US, platform encoding: Cp1252
> OS name: "windows 7", version: "6.1", arch: "amd64", family: "dos"
> [DEBUG] Created new class realm maven.api
> [DEBUG] Importing foreign packages into class realm maven.api
> [DEBUG]   Imported: javax.enterprise.inject.* < plexus.core
> [DEBUG]   Imported: javax.enterprise.util.* < plexus.core
> [DEBUG]   Imported: javax.inject.* < plexus.core
> [DEBUG]   Imported: org.apache.maven.* < plexus.core
> [DEBUG]   Imported: org.apache.maven.artifact < plexus.core
> [DEBUG]   Imported: org.apache.maven.classrealm < plexus.core
> [DEBUG]   Imported: org.apache.maven.cli < plexus.core
> [DEBUG]   Imported: org.apache.maven.configuration < plexus.core
> [DEBUG]   Imported: org.apache.maven.exception < plexus.core
> [DEBUG]   Imported: org.apache.maven.execution < plexus.core
> [DEBUG]   Imported: org.apache.maven.execution.scope < plexus.core
> [DEBUG]   Imported: org.apache.maven.lifecycle < plexus.core
> [DEBUG]   Imported: org.apache.maven.model < plexus.core
> [DEBUG]   Imported: org.apache.maven.monitor < plexus.core
> [DEBUG]   Imported: org.apache.maven.plugin < plexus.core
> [DEBUG]   Imported: org.apache.maven.profiles < plexus.core
> [DEBUG]   Imported: org.apache.maven.project < plexus.core
> [DEBUG]   Imported: org.apache.maven.reporting < plexus.core
> [DEBUG]   Imported: org.apache.maven.repository < plexus.core
> [DEBUG]   Imported: org.apache.maven.rtinfo < plexus.core
> [DEBUG]   Imported: org.apache.maven.settings < plexus.core
> [DEBUG]   Imported: org.apache.maven.toolchain < plexus.core
>

[jira] [Closed] (MRESOURCES-240) Add some binnary types to nonFilteredFileExte‌nsion by default

2018-02-22 Thread Karl Heinz Marbaise (JIRA)


 [ 
https://issues.apache.org/jira/browse/MRESOURCES-240?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Karl Heinz Marbaise closed MRESOURCES-240.
--
Resolution: Won't Fix
  Assignee: Karl Heinz Marbaise

Unfortunately I have the same opinion. Otherwise this would mean the list will 
grow over the time...

> Add some binnary types to nonFilteredFileExte‌nsion by default
> ---
>
> Key: MRESOURCES-240
> URL: https://issues.apache.org/jira/browse/MRESOURCES-240
> Project: Maven Resources Plugin
>  Issue Type: Improvement
>  Components: filtering
>Reporter: Flávio Casas de Arcega
>Assignee: Karl Heinz Marbaise
>Priority: Minor
>  Labels: easyfix, patch
>
> Hi!
> I had problems with filtering binnary resources, fonts and icons from my 
> application where corrupted during the build process.
> To solve, I added this configuration to the maven-resources-plugin:
> 
>   
>   
>   maven-resources-plugin
>   
>   
>   
> svg
>   
> woff
>   
> woff2
>   
> ttf
>   
> eot
>   
> otf
>   
>   
>   
>   
> 
> And I was wondering if this binnary types coudn't be excluded from filters by 
> default.
> I think It would be possible, changing the 
> org.apache.maven.shared.maven-filtering plugin by applying this patch to the 
> org.apache.maven.shared.filtering.DefaultMavenResourcesFiltering class:
> 79a80,85
> > this.defaultNonFilteredFileExtensions.add( "svg" );
> > this.defaultNonFilteredFileExtensions.add( "woff" );
> > this.defaultNonFilteredFileExtensions.add( "woff2" );
> > this.defaultNonFilteredFileExtensions.add( "ttf" );
> > this.defaultNonFilteredFileExtensions.add( "eot" );
> > this.defaultNonFilteredFileExtensions.add( "otf" );
> Only a suggestion, thanks 4 all...



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MRESOURCES-241) Upgrade parent to 31

2018-02-22 Thread Hudson (JIRA)


[ 
https://issues.apache.org/jira/browse/MRESOURCES-241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16373233#comment-16373233
 ] 

Hudson commented on MRESOURCES-241:
---

Build succeeded in Jenkins: Maven TLP » maven-resources-plugin » master #3

See 
https://builds.apache.org/job/maven-box/job/maven-resources-plugin/job/master/3/

> Upgrade parent to 31
> 
>
> Key: MRESOURCES-241
> URL: https://issues.apache.org/jira/browse/MRESOURCES-241
> Project: Maven Resources Plugin
>  Issue Type: Dependency upgrade
>Affects Versions: 3.0.3
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.0.3
>
>




--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (MPMD-254) An API incompatibility was encountered while executing org.apache.maven.plugins:maven-pmd-plugin:3.9.0:pmd

2018-02-22 Thread Roman Ivanov (JIRA)

Roman Ivanov created MPMD-254:
-

 Summary: An API incompatibility was encountered while executing 
org.apache.maven.plugins:maven-pmd-plugin:3.9.0:pmd
 Key: MPMD-254
 URL: https://issues.apache.org/jira/browse/MPMD-254
 Project: Maven PMD Plugin
  Issue Type: Bug
Affects Versions: 3.9.0
Reporter: Roman Ivanov


code base [https://github.com/checkstyle/checkstyle/]

jsut did update from 3.8 to 3.9.0 at 
[https://github.com/checkstyle/checkstyle/blob/master/pom.xml#L214]

{code}
$ mvn verify

[INFO] 
[INFO] BUILD FAILURE
[INFO] 
[INFO] Total time: 02:40 min
[INFO] Finished at: 2018-02-22T08:18:54-08:00
[INFO] Final Memory: 63M/615M
[INFO] 
[ERROR] Failed to execute goal 
org.apache.maven.plugins:maven-pmd-plugin:3.9.0:pmd (pmd) on project 
checkstyle: Execution pmd of goal 
org.apache.maven.plugins:maven-pmd-plugin:3.9.0:pmd failed: An API 
incompatibility was encountered while executing 
org.apache.maven.plugins:maven-pmd-plugin:3.9.0:pmd: 
java.lang.IllegalAccessError: tried to access method 
net.sourceforge.pmd.util.ResourceLoader.()V from class 
org.apache.maven.plugins.pmd.PmdReport
[ERROR] -
[ERROR] realm =plugin>org.apache.maven.plugins:maven-pmd-plugin:3.9.0
[ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
[ERROR] urls[0] = 
file:/home/user/.m2/repository/org/apache/maven/plugins/maven-pmd-plugin/3.9.0/maven-pmd-plugin-3.9.0.jar
[ERROR] urls[1] = 
file:/home/user/.m2/repository/net/sourceforge/pmd/pmd-java/5.8.1/pmd-java-5.8.1.jar
[ERROR] urls[2] = 
file:/home/user/.m2/repository/jaxen/jaxen/1.1.6/jaxen-1.1.6.jar
[ERROR] urls[3] = 
file:/home/user/.m2/repository/net/java/dev/javacc/javacc/5.0/javacc-5.0.jar
[ERROR] urls[4] = 
file:/home/user/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8.jar
[ERROR] urls[5] = 
file:/home/user/.m2/repository/org/ow2/asm/asm/5.0.4/asm-5.0.4.jar
[ERROR] urls[6] = 
file:/home/user/.m2/repository/net/sourceforge/saxon/saxon/9.1.0.8/saxon-9.1.0.8-dom.jar
[ERROR] urls[7] = 
file:/home/user/.m2/repository/net/sourceforge/pmd/pmd-core/5.8.1/pmd-core-5.8.1.jar
[ERROR] urls[8] = 
file:/home/user/.m2/repository/com/beust/jcommander/1.48/jcommander-1.48.jar
[ERROR] urls[9] = 
file:/home/user/.m2/repository/org/apache/commons/commons-lang3/3.4/commons-lang3-3.4.jar
[ERROR] urls[10] = 
file:/home/user/.m2/repository/com/google/code/gson/gson/2.5/gson-2.5.jar
[ERROR] urls[11] = 
file:/home/user/.m2/repository/net/sourceforge/pmd/pmd-javascript/5.8.1/pmd-javascript-5.8.1.jar
[ERROR] urls[12] = 
file:/home/user/.m2/repository/org/mozilla/rhino/1.7.7/rhino-1.7.7.jar
[ERROR] urls[13] = 
file:/home/user/.m2/repository/net/sourceforge/pmd/pmd-jsp/5.8.1/pmd-jsp-5.8.1.jar
[ERROR] urls[14] = 
file:/home/user/.m2/repository/org/sonatype/sisu/sisu-inject-bean/1.4.2/sisu-inject-bean-1.4.2.jar
[ERROR] urls[15] = 
file:/home/user/.m2/repository/org/sonatype/sisu/sisu-guice/2.1.7/sisu-guice-2.1.7-noaop.jar
[ERROR] urls[16] = 
file:/home/user/.m2/repository/org/slf4j/jul-to-slf4j/1.7.25/jul-to-slf4j-1.7.25.jar
[ERROR] urls[17] = 
file:/home/user/.m2/repository/org/apache/maven/doxia/doxia-sink-api/1.7/doxia-sink-api-1.7.jar
[ERROR] urls[18] = 
file:/home/user/.m2/repository/org/apache/maven/doxia/doxia-logging-api/1.7/doxia-logging-api-1.7.jar
[ERROR] urls[19] = 
file:/home/user/.m2/repository/org/apache/maven/doxia/doxia-decoration-model/1.7/doxia-decoration-model-1.7.jar
[ERROR] urls[20] = 
file:/home/user/.m2/repository/org/codehaus/plexus/plexus-component-annotations/1.6/plexus-component-annotations-1.6.jar
[ERROR] urls[21] = 
file:/home/user/.m2/repository/org/apache/maven/doxia/doxia-site-renderer/1.7/doxia-site-renderer-1.7.jar
[ERROR] urls[22] = 
file:/home/user/.m2/repository/org/apache/maven/doxia/doxia-core/1.7/doxia-core-1.7.jar
[ERROR] urls[23] = 
file:/home/user/.m2/repository/commons-lang/commons-lang/2.4/commons-lang-2.4.jar
[ERROR] urls[24] = 
file:/home/user/.m2/repository/xmlunit/xmlunit/1.5/xmlunit-1.5.jar
[ERROR] urls[25] = 
file:/home/user/.m2/repository/org/apache/maven/doxia/doxia-skin-model/1.7/doxia-skin-model-1.7.jar
[ERROR] urls[26] = 
file:/home/user/.m2/repository/org/apache/maven/doxia/doxia-module-xhtml/1.7/doxia-module-xhtml-1.7.jar
[ERROR] urls[27] = 
file:/home/user/.m2/repository/org/apache/maven/doxia/doxia-module-fml/1.7/doxia-module-fml-1.7.jar
[ERROR] urls[28] = 
file:/home/user/.m2/repository/org/codehaus/plexus/plexus-i18n/1.0-beta-7/plexus-i18n-1.0-beta-7.jar
[ERROR] urls[29] = 
file:/home/user/.m2/repository/junit/junit/3.8.1/junit-3.8.1.jar
[ERROR] urls[30] =

[jira] [Commented] (WAGON-495) checkoutDirectory leak

2018-02-22 Thread ASF GitHub Bot (JIRA)


[ 
https://issues.apache.org/jira/browse/WAGON-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16372753#comment-16372753
 ] 

ASF GitHub Bot commented on WAGON-495:
--

GitHub user basinilya opened a pull request:

https://github.com/apache/maven-wagon/pull/46

[WAGON-495] fix testWagonPutDirectoryWhenDirectoryAlreadyExists false 
positive



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/basinilya/maven-wagon WAGON-495

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven-wagon/pull/46.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #46


commit 7443918a2255d351241e5edc04ddfcb2cebdcc78
Author: Ilya Basin 
Date:   2018-02-18T19:34:20Z

[WAGON-498] use maven-scm 1.9.6-SNAPSHOT

commit 09d3d542726d189644f0c7de63067afa5f94608d
Author: Ilya Basin 
Date:   2018-02-18T19:49:30Z

[WAGON-498] ScmWagon should work in binary mode when possible

commit c982129f0ad3d34d9d15ed0d7c0659c322a2c7f3
Author: Ilya Basin 
Date:   2018-02-22T08:13:52Z

[WAGON-495] fix testWagonPutDirectoryWhenDirectoryAlreadyExists false
positive




> checkoutDirectory leak
> --
>
> Key: WAGON-495
> URL: https://issues.apache.org/jira/browse/WAGON-495
> Project: Maven Wagon
>  Issue Type: Bug
>  Components: wagon-scm
>Affects Versions: 3.0.0, 3.0.1
>Reporter: Ilya Basin
>Priority: Major
>
> During deploy artifacts to SVN an instance of ScmWagon is initialized and 
> artifact metadata is downloaded to a local folder. After that maven tries to 
> upload the jar file. ScmWagon.put(File,String) is called which internally 
> overwrites the checkoutDirectory field and checks out the repo again to 
> another temporary folder. The original folder is forgotten.
> Maven uploads jars, poms, checksums and for each file ScmWagon checks out a 
> new directory.
> In the end the closeConnection() method is called which removes the last used 
> folder.
> UPD: this causes false positive in 
> testWagonPutDirectoryWhenDirectoryAlreadyExists(): the test deletes the test 
> checkout dir before calling get(), but the wagon checkout dir remains and the 
> file is retrieved from there.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[GitHub] maven-wagon pull request #46: [WAGON-495] fix testWagonPutDirectoryWhenDirec...

2018-02-22 Thread basinilya

GitHub user basinilya opened a pull request:

https://github.com/apache/maven-wagon/pull/46

[WAGON-495] fix testWagonPutDirectoryWhenDirectoryAlreadyExists false 
positive



You can merge this pull request into a Git repository by running:

$ git pull https://github.com/basinilya/maven-wagon WAGON-495

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/maven-wagon/pull/46.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #46


commit 7443918a2255d351241e5edc04ddfcb2cebdcc78
Author: Ilya Basin 
Date:   2018-02-18T19:34:20Z

[WAGON-498] use maven-scm 1.9.6-SNAPSHOT

commit 09d3d542726d189644f0c7de63067afa5f94608d
Author: Ilya Basin 
Date:   2018-02-18T19:49:30Z

[WAGON-498] ScmWagon should work in binary mode when possible

commit c982129f0ad3d34d9d15ed0d7c0659c322a2c7f3
Author: Ilya Basin 
Date:   2018-02-22T08:13:52Z

[WAGON-495] fix testWagonPutDirectoryWhenDirectoryAlreadyExists false
positive




---

[jira] [Created] (MRELEASE-999) When GIT tag cannot be created release succeeds but version tagged is not overriden

2018-02-22 Thread Blanca Rojo Martin (JIRA)

Blanca Rojo Martin created MRELEASE-999:
---

 Summary: When GIT tag cannot be created release succeeds but 
version tagged is not overriden
 Key: MRELEASE-999
 URL: https://issues.apache.org/jira/browse/MRELEASE-999
 Project: Maven Release Plugin
  Issue Type: Bug
Reporter: Blanca Rojo Martin
 Attachments: image-2018-02-22-10-10-50-833.png, 
image-2018-02-22-10-11-43-062.png

We run release for a tag that already existed in GIT, as we had been testing 
the release process and we forgot to delete the tags.

When running the release plugin we got a successful execution. However, as the 
tag already existed it wasn't overwritten and we released the wrong version, 
the one that already existed in that old tag. We would expect the release 
plugin to break if the tag cannot be overridden so that it doesn't become a 
case of looking through thousand lines of code to check.

Logs were:

!image-2018-02-22-10-10-50-833.png!

And after a while the old tag was checked out and released:

!image-2018-02-22-10-11-43-062.png!



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Commented] (MNG-6359) Non-resolvable parent POM with gitbash (MINGW64_NT-10.0)

2018-02-22 Thread Ian Dunbar (JIRA)


[ 
https://issues.apache.org/jira/browse/MNG-6359?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16372610#comment-16372610
 ] 

Ian Dunbar commented on MNG-6359:
-

Thanks for trying to reproduce. I removed the .m2 folder entirely, but it still 
has the same issue. I'll see if I can reproduce on a different machine.

Is there a way to trace the evaluation of the artifact resolution? I could then 
compare why running from cmd.exe on the same machine  doesn't experience the 
issue.

> Non-resolvable parent POM with gitbash (MINGW64_NT-10.0)
> 
>
> Key: MNG-6359
> URL: https://issues.apache.org/jira/browse/MNG-6359
> Project: Maven
>  Issue Type: Bug
>  Components: POM
>Affects Versions: 3.5.0, 3.5.2
> Environment: Run from gitbash
> GNU bash, version 4.4.12(1)-release (x86_64-pc-msys)
> Apache Maven 3.5.2 (138edd61fd100ec658bfa2d307c43b76940a5d7d; 
> 2017-10-18T08:58:13+01:00)
> Maven home: C:\Program Files\Apache\maven
> Java version: 1.8.0_161, vendor: Oracle Corporation
> Java home: C:\Program Files\Java\jdk1.8.0_161\jre
> Default locale: en_IE, platform encoding: Cp1252
> OS name: "windows 10", version: "10.0", arch: "amd64", family: "windows"
>Reporter: Ian Dunbar
>Priority: Minor
> Attachments: mm.zip
>
>
> The attached multimodule example fails to build when run from gitbash on 
> windows 10. I've derived it from this example 
> [https://github.com/jamesward/maven-multi-module-example] but modified to 
> match my scenario.
> It works fine from CMD shell on the same machine with the same Apache Maven 
> install. It's only with gitbash that the issue occurs. I see that the mvn 
> launcher has specific sections for mingw derived shells like gitbash, so 
> possibly something is wrong there.
>  
> The issue occurs when the project has no artifacts yet in .m2 repo. So please 
> remove .m2/repository/com/jamesward prior to testing.
> The transition from working to non-working in gitbash is with the addition of 
> the parent section in the toplevel pom.xml, so there seems to be something 
> wrong with the parent resolution in the toplevel when run from gitbash
> Steps:
>  * remove .m2/repository/com/jamesward
>  * unzip the example
>  * run gitbash in that folder
>  * mvn clean install
>  * *fails to build*
>  * 
>  * change to cmd.exe
>  * mvn clean install
>  * *builds correctly*
> Error log:
>  
> {{[INFO] Scanning for projects...}}
> {{[ERROR] [ERROR] Some problems were encountered while processing the POMs:}}
> {{[FATAL] Non-resolvable parent POM for com.jamesward:core:1.0-SNAPSHOT: 
> Could not find artifact com.jamesward:parent:pom:1.0-SNAPSHOT and 
> 'parent.relativePath' points at wrong local POM @ line 6, column 13}}
> {{[FATAL] Non-resolvable parent POM for com.jamesward:app:[unknown-version]: 
> Could not find artifact com.jamesward:parent:pom:1.0-SNAPSHOT and 
> 'parent.relativePath' points at wrong local POM @ line 6, column 13}}
> {{ @}}
> {{[ERROR] The build could not read 2 projects -> [Help 1]}}
> {{[ERROR]}}
> {{[ERROR] The project com.jamesward:core:1.0-SNAPSHOT (C:\mm\core\pom.xml) 
> has 1 error}}
> {{[ERROR] Non-resolvable parent POM for com.jamesward:core:1.0-SNAPSHOT: 
> Could not find artifact com.jamesward:parent:pom:1.0-SNAPSHOT and 
> 'parent.relativePath' points at wrong local POM @ line 6, column 13 -> [Help 
> 2]}}
> {{[ERROR]}}
> {{[ERROR] The project com.jamesward:app:[unknown-version] (C:\mm\app\pom.xml) 
> has 1 error}}
> {{[ERROR] Non-resolvable parent POM for com.jamesward:app:[unknown-version]: 
> Could not find artifact com.jamesward:parent:pom:1.0-SNAPSHOT and 
> 'parent.relativePath' points at wrong local POM @ line 6, column 13 -> [Help 
> 2]}}
> {{[ERROR]}}
> {{[ERROR] To see the full stack trace of the errors, re-run Maven with the -e 
> switch.}}
> {{[ERROR] Re-run Maven using the -X switch to enable full debug logging.}}
> {{[ERROR]}}
> {{[ERROR] For more information about the errors and possible solutions, 
> please read the following articles:}}
> {{[ERROR] [Help 1] 
> http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingException}}
> {{[ERROR] [Help 2] 
> http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelException}}



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (SCM-870) ScmProvider.checkOut() should honor fileSet.getFileList()

2018-02-22 Thread Ilya Basin (JIRA)

Ilya Basin created SCM-870:
--

 Summary: ScmProvider.checkOut() should honor fileSet.getFileList()
 Key: SCM-870
 URL: https://issues.apache.org/jira/browse/SCM-870
 Project: Maven SCM
  Issue Type: New Feature
Reporter: Ilya Basin


If fileSet.getFileList() is not empty, the checkout commands should checkout 
only files requested.

For SVN and CVS it means that the common prefix of the fileList should be 
appended to the repo URL.

The git implementation should clone with --no-checkout and then checkout the 
files from the list.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Comment Edited] (MDEP-559) Java 9 bytecode cannot be parsed

2018-02-22 Thread Giovanni Lovato (JIRA)


[ 
https://issues.apache.org/jira/browse/MDEP-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16372559#comment-16372559
 ] 

Giovanni Lovato edited comment on MDEP-559 at 2/22/18 9:10 AM:
---

What's the current status of this? Is there a version of the plugin I can test 
with Java 9?

Current 3.0.3-SNAPSHOT fails for me with:
{code:java}
Execution default-cli of goal 
org.apache.maven.plugins:maven-dependency-plugin:3.0.3-SNAPSHOT:analyze-only 
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:955)
    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.PluginExecutionException: Execution 
default-cli of goal 
org.apache.maven.plugins:maven-dependency-plugin:3.0.3-SNAPSHOT:analyze-only 
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 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:955)
    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: 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.apache.maven.shared.dependency.analyzer.asm.DependencyClassFileVisitor.visitClass
 (DependencyClassFileVisitor.java:65)
    at 
org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.visitClass 
(ClassFileVisitorUtils.java:163)
    at 
org.apache.maven.shared.dependency.analyzer.ClassFileVisitorUtils.acceptDirectory
 (ClassFileVisitorUtils.java:143)
    at

[jira] [Commented] (MDEP-559) Java 9 bytecode cannot be parsed

2018-02-22 Thread Giovanni Lovato (JIRA)


[ 
https://issues.apache.org/jira/browse/MDEP-559?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=16372559#comment-16372559
 ] 

Giovanni Lovato commented on MDEP-559:
--

What's the current status of this? Is there a version of the plugin I can test 
with Java 9?

> Java 9 bytecode cannot be parsed
> 
>
> Key: MDEP-559
> URL: https://issues.apache.org/jira/browse/MDEP-559
> Project: Maven Dependency Plugin
>  Issue Type: Bug
>  Components: analyze
>Affects Versions: 3.0.0
> Environment: Apache Maven 3.3.9 
> (NON-CANONICAL_2015-11-23T13:17:27+03:00_root; 2015-11-23T21:17:27+11:00)
> Maven home: /opt/maven
> Java version: 9-ea, vendor: Oracle Corporation
> Java home: /usr/lib/jvm/java-9-jdk
> Default locale: en_AU, platform encoding: UTF-8
> OS name: "linux", version: "4.9.11-1-arch", arch: "amd64", family: "unix"
>Reporter: Ben Alex
>Assignee: Robert Scholte
>Priority: Major
>
> Attempting to run analyze-only against source compiled with Java 9 results in:
> {noformat}
> [INFO] --- maven-dependency-plugin:3.0.0:analyze-only (config-dependency) @ 
> lmdbjava ---
> [DEBUG] Configuring mojo 
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only from 
> plugin realm 
> ClassRealm[plugin>org.apache.maven.plugins:maven-dependency-plugin:3.0.0, 
> parent: jdk.internal.loader.ClassLoaders$AppClassLoader@3b764bce]
> [DEBUG] Configuring mojo 
> 'org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only' with 
> basic configurator -->
> [DEBUG]   (f) analyzer = default
> [DEBUG]   (f) baseDir = /home/bpa/projects/lmdbjava
> [DEBUG]   (f) failOnWarning = true
> [DEBUG]   (f) ignoreNonCompile = false
> [DEBUG]   (f) outputDirectory = /home/bpa/projects/lmdbjava/target
> [DEBUG]   (f) outputXML = false
> [DEBUG]   (f) project = MavenProject: org.lmdbjava:lmdbjava:0.0.6-SNAPSHOT @ 
> /home/bpa/projects/lmdbjava/dependency-reduced-pom.xml
> [DEBUG]   (f) scriptableFlag = $$%%%
> [DEBUG]   (f) scriptableOutput = false
> [DEBUG]   (f) skip = false
> [DEBUG]   (f) usedDependencies = [org.lmdbjava:lmdbjava-native-linux-x86_64, 
> org.lmdbjava:lmdbjava-native-windows-x86_64, 
> org.lmdbjava:lmdbjava-native-osx-x86_64]
> [DEBUG]   (f) verbose = false
> [DEBUG] -- end configuration --
> [INFO] 
> 
> [INFO] BUILD FAILURE
> [INFO] 
> 
> [INFO] Total time: 7.256 s
> [INFO] Finished at: 2017-03-17T17:32:20+11:00
> [INFO] Final Memory: 40M/132M
> [INFO] 
> 
> [ERROR] Failed to execute goal 
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only 
> (config-dependency) on project lmdbjava: Execution config-dependency of goal 
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only failed. 
> IllegalArgumentException -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute 
> goal org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only 
> (config-dependency) on project lmdbjava: Execution config-dependency of goal 
> org.apache.maven.plugins:maven-dependency-plugin:3.0.0:analyze-only failed.
>   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:547)

[jira] [Updated] (WAGON-495) checkoutDirectory leak

2018-02-22 Thread Ilya Basin (JIRA)


 [ 
https://issues.apache.org/jira/browse/WAGON-495?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
 ]

Ilya Basin updated WAGON-495:
-
Description: 
During deploy artifacts to SVN an instance of ScmWagon is initialized and 
artifact metadata is downloaded to a local folder. After that maven tries to 
upload the jar file. ScmWagon.put(File,String) is called which internally 
overwrites the checkoutDirectory field and checks out the repo again to another 
temporary folder. The original folder is forgotten.

Maven uploads jars, poms, checksums and for each file ScmWagon checks out a new 
directory.

In the end the closeConnection() method is called which removes the last used 
folder.

UPD: this causes false positive in 
testWagonPutDirectoryWhenDirectoryAlreadyExists(): the test deletes the test 
checkout dir before calling get(), but the wagon checkout dir remains and the 
file is retrieved from there.

  was:
During deploy artifacts to SVN an instance of ScmWagon is initialized and 
artifact metadata is downloaded to a local folder. After that maven tries to 
upload the jar file. ScmWagon.put(File,String) is called which internally 
overwrites the checkoutDirectory field and checks out the repo again to another 
temporary folder. The original folder is forgotten.

Maven uploads jars, poms, checksums and for each file ScmWagon checks out a new 
directory.

In the end the closeConnection() method is called which removes the last used 
folder.


> checkoutDirectory leak
> --
>
> Key: WAGON-495
> URL: https://issues.apache.org/jira/browse/WAGON-495
> Project: Maven Wagon
>  Issue Type: Bug
>  Components: wagon-scm
>Affects Versions: 3.0.0, 3.0.1
>Reporter: Ilya Basin
>Priority: Major
>
> During deploy artifacts to SVN an instance of ScmWagon is initialized and 
> artifact metadata is downloaded to a local folder. After that maven tries to 
> upload the jar file. ScmWagon.put(File,String) is called which internally 
> overwrites the checkoutDirectory field and checks out the repo again to 
> another temporary folder. The original folder is forgotten.
> Maven uploads jars, poms, checksums and for each file ScmWagon checks out a 
> new directory.
> In the end the closeConnection() method is called which removes the last used 
> folder.
> UPD: this causes false positive in 
> testWagonPutDirectoryWhenDirectoryAlreadyExists(): the test deletes the test 
> checkout dir before calling get(), but the wagon checkout dir remains and the 
> file is retrieved from there.



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

[jira] [Created] (SUREFIRE-1488) Native library in Surefire1295AttributeJvmCrashesToTestsIT caused unstable test

2018-02-22 Thread Tibor Digana (JIRA)

Tibor Digana created SUREFIRE-1488:
--

 Summary: Native library in 
Surefire1295AttributeJvmCrashesToTestsIT caused unstable test
 Key: SUREFIRE-1488
 URL: https://issues.apache.org/jira/browse/SUREFIRE-1488
 Project: Maven Surefire
  Issue Type: Task
Reporter: Tibor Digana
 Fix For: 2.21.0


Investigate the main purpose of this IT and investigate the {{exit()}} function.
See this discussion:
https://github.com/michaeltandy/crashjvm/issues/1



--
This message was sent by Atlassian JIRA
(v7.6.3#76005)

47 matches

Mail list logo