[jira] [Commented] (MRELEASE-979) Support NamingPolicies to manage Branch and Tag names
[ https://issues.apache.org/jira/browse/MRELEASE-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15959702#comment-15959702 ] ASF GitHub Bot commented on MRELEASE-979: - Github user hgschmie closed the pull request at: https://github.com/apache/maven-release/pull/17 > Support NamingPolicies to manage Branch and Tag names > - > > Key: MRELEASE-979 > URL: https://issues.apache.org/jira/browse/MRELEASE-979 > Project: Maven Release Plugin > Issue Type: Improvement > Components: branch, prepare, update-versions >Affects Versions: 2.5.3 >Reporter: Henning Schmiedehausen > Fix For: 3.0.0 > > > The newly introduced VersionPolicy facility allows managing the development > and release versions of projects when releasing, branching and updating > versions. > Most organizations will also have a policy around how branches and tags are > named (which often have to match specific versioning patterns). The current > VersionPolicy implementations do not allow this but it should be possible. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Resolved] (MRELEASE-979) Support NamingPolicies to manage Branch and Tag names
[ https://issues.apache.org/jira/browse/MRELEASE-979?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Henning Schmiedehausen resolved MRELEASE-979. - Resolution: Fixed Changes applied to trunk are working fine. > Support NamingPolicies to manage Branch and Tag names > - > > Key: MRELEASE-979 > URL: https://issues.apache.org/jira/browse/MRELEASE-979 > Project: Maven Release Plugin > Issue Type: Improvement > Components: branch, prepare, update-versions >Affects Versions: 2.5.3 >Reporter: Henning Schmiedehausen > Fix For: 3.0.0 > > > The newly introduced VersionPolicy facility allows managing the development > and release versions of projects when releasing, branching and updating > versions. > Most organizations will also have a policy around how branches and tags are > named (which often have to match specific versioning patterns). The current > VersionPolicy implementations do not allow this but it should be possible. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MRELEASE-979) Support NamingPolicies to manage Branch and Tag names
[ https://issues.apache.org/jira/browse/MRELEASE-979?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15959695#comment-15959695 ] Henning Schmiedehausen commented on MRELEASE-979: - To close this thread out: The current version on master works for me and my needs. > Support NamingPolicies to manage Branch and Tag names > - > > Key: MRELEASE-979 > URL: https://issues.apache.org/jira/browse/MRELEASE-979 > Project: Maven Release Plugin > Issue Type: Improvement > Components: branch, prepare, update-versions >Affects Versions: 2.5.3 >Reporter: Henning Schmiedehausen > Fix For: 3.0.0 > > > The newly introduced VersionPolicy facility allows managing the development > and release versions of projects when releasing, branching and updating > versions. > Most organizations will also have a policy around how branches and tags are > named (which often have to match specific versioning patterns). The current > VersionPolicy implementations do not allow this but it should be possible. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MPOM-164) Require Maven 3.0 to build ASF projects
[
https://issues.apache.org/jira/browse/MPOM-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15959692#comment-15959692
]
Karl Heinz Marbaise commented on MPOM-164:
--
Fixed also [log message in SVN|https://svn.apache.org/r1790440]
> Require Maven 3.0 to build ASF projects
> ---
>
> Key: MPOM-164
> URL: https://issues.apache.org/jira/browse/MPOM-164
> Project: Maven POMs
> Issue Type: Improvement
> Components: asf
>Affects Versions: ASF-18
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: ASF-19
>
>
> Currently we use {{prerequisites}} in ASF parent pom which does not make
> sense cause it is not inherited nor is it being checked for the appropriate
> Maven version furthermore with Maven 3.5.0 it will produce a WARNING.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (MPOM-164) Require Maven 3.0 to build ASF projects
[
https://issues.apache.org/jira/browse/MPOM-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MPOM-164:
-
Summary: Require Maven 3.0 to build ASF projects (was: Removed
prerequisites from pom use maven-enforcer instead)
> Require Maven 3.0 to build ASF projects
> ---
>
> Key: MPOM-164
> URL: https://issues.apache.org/jira/browse/MPOM-164
> Project: Maven POMs
> Issue Type: Improvement
> Components: asf
>Affects Versions: ASF-18
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: ASF-19
>
>
> Currently we use {{prerequisites}} in ASF parent pom which does not make
> sense cause it is not inherited nor is it being checked for the appropriate
> Maven version furthermore with Maven 3.5.0 it will produce a WARNING.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Closed] (MDEPLOY-218) deploy-file is inconsistent with install-file behavior.
[
https://issues.apache.org/jira/browse/MDEPLOY-218?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Robert Scholte closed MDEPLOY-218.
--
Resolution: Not A Problem
Assignee: Robert Scholte
For the usecase a different plugin should be used. I don't think there's a real
issue here, won't investigate it, so closing as "Not a problem" for now.
> deploy-file is inconsistent with install-file behavior.
> ---
>
> Key: MDEPLOY-218
> URL: https://issues.apache.org/jira/browse/MDEPLOY-218
> Project: Maven Deploy Plugin
> Issue Type: Bug
> Components: deploy:deploy-file
>Affects Versions: 2.8.2
>Reporter: Yujue Li
>Assignee: Robert Scholte
> Labels: build
>
> The following configuration, install-file will take effect, but deploy-file
> will not take effect.
> {code:xml}
>
>
>
> org.apache.maven.plugins
> maven-install-plugin
> 2.5.2
> false
>
> true
>
>
>
> org.apache.maven.plugins
> maven-install-plugin
> 2.5.2
> false
>
>
> core-install
> install
>
> install-file
>
>
>
> ${basedir}/pom-deployment.xml
>
> com.platform-dev.projects
> core
> ${c.version}
> pom
>
>
>
>
>
> org.apache.maven.plugins
> maven-deploy-plugin
> false
> 2.8.2
>
> true
>
>
>
> org.apache.maven.plugins
> maven-deploy-plugin
> 2.8.2
> false
>
>
> core-deploy
> deploy
>
> deploy-file
>
>
>
> ${basedir}/pom-deployment.xml
>
> com.platform-dev.projects
> core
> ${c.version}
> pom
>
> http://192.168.2.241:7001/nexus/content/repositories/releases
>
> platform-release
>
>
>
>
>
>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (MPOM-164) Removed prerequisites from pom use maven-enforcer instead
[
https://issues.apache.org/jira/browse/MPOM-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15959676#comment-15959676
]
Robert Scholte commented on MPOM-164:
-
Maybe we should change the title, because it describes the proposed change but
the impact is not clear, e.g. "Require Maven 3.0 to build ASF projects". Such
a line is IMHO much better within the release notes.
> Removed prerequisites from pom use maven-enforcer instead
> -
>
> Key: MPOM-164
> URL: https://issues.apache.org/jira/browse/MPOM-164
> Project: Maven POMs
> Issue Type: Improvement
> Components: asf
>Affects Versions: ASF-18
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: ASF-19
>
>
> Currently we use {{prerequisites}} in ASF parent pom which does not make
> sense cause it is not inherited nor is it being checked for the appropriate
> Maven version furthermore with Maven 3.5.0 it will produce a WARNING.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (MPOM-164) Removed prerequisites from pom use maven-enforcer instead
[
https://issues.apache.org/jira/browse/MPOM-164?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15959607#comment-15959607
]
Hudson commented on MPOM-164:
-
SUCCESS: Integrated in Jenkins build ASF Parent Pom #161 (See
[https://builds.apache.org/job/ASF%20Parent%20Pom/161/])
[MPOM-164] Removed prerequisites from pom use maven-enforcer instead
(khmarbaise: [http://svn.apache.org/viewvc/?view=rev=1790440])
* (edit) pom.xml
> Removed prerequisites from pom use maven-enforcer instead
> -
>
> Key: MPOM-164
> URL: https://issues.apache.org/jira/browse/MPOM-164
> Project: Maven POMs
> Issue Type: Improvement
> Components: asf
>Affects Versions: ASF-18
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: ASF-19
>
>
> Currently we use {{prerequisites}} in ASF parent pom which does not make
> sense cause it is not inherited nor is it being checked for the appropriate
> Maven version furthermore with Maven 3.5.0 it will produce a WARNING.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Closed] (MPOM-164) Removed prerequisites from pom use maven-enforcer instead
[
https://issues.apache.org/jira/browse/MPOM-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MPOM-164.
Resolution: Fixed
Done in [r1790440|https://svn.apache.org/r1790440]
> Removed prerequisites from pom use maven-enforcer instead
> -
>
> Key: MPOM-164
> URL: https://issues.apache.org/jira/browse/MPOM-164
> Project: Maven POMs
> Issue Type: Improvement
> Components: asf
>Affects Versions: ASF-18
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: ASF-19
>
>
> Currently we use {{prerequisites}} in ASF parent pom which does not make
> sense cause it is not inherited nor is it being checked for the appropriate
> Maven version furthermore with Maven 3.5.0 it will produce a WARNING.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (MPOM-164) Removed prerequisites from pom use maven-enforcer instead
Karl Heinz Marbaise created MPOM-164:
Summary: Removed prerequisites from pom use maven-enforcer instead
Key: MPOM-164
URL: https://issues.apache.org/jira/browse/MPOM-164
Project: Maven POMs
Issue Type: Improvement
Components: asf
Affects Versions: ASF-18
Reporter: Karl Heinz Marbaise
Assignee: Karl Heinz Marbaise
Priority: Minor
Fix For: ASF-19
Currently we use {{prerequisites}} in ASF parent pom which does not make sense
cause it is not inherited nor is it being checked for the appropriate Maven
version furthermore with Maven 3.5.0 it will produce a WARNING.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (MRRESOURCES-101) NPE - Error rendering velocity resource
[
https://issues.apache.org/jira/browse/MRRESOURCES-101?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15959543#comment-15959543
]
Karl Heinz Marbaise commented on MRRESOURCES-101:
-
Hi Daniel, first thanks for your patch...but against which state of the repos
have you made that patch...maybe I mistaken something...
> NPE - Error rendering velocity resource
> ---
>
> Key: MRRESOURCES-101
> URL: https://issues.apache.org/jira/browse/MRRESOURCES-101
> Project: Maven Remote Resources Plugin
> Issue Type: Bug
>Affects Versions: 1.5
>Reporter: Daniel Klessing
> Attachments: mrresources_npe.diff
>
>
> We noticed that occasionally the maven-remote-resources-plugin kills our
> build as a NPE with the message "Error rendering velocity resource" happend.
> Luckily I succeeded today in getting a stacktrace of the issue:
> {code}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process (default)
> on project parent: Error rendering velocity resource. NullPointerException ->
> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute
> goal org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process
> (default) on project parent: Error rendering velocity resource.
> 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 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 rendering
> velocity resource.
> at
> org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.processResourceBundles(ProcessRemoteResourcesMojo.java:1246)
> at
> org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.execute(ProcessRemoteResourcesMojo.java:520)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
> ... 20 more
> Caused by: java.lang.NullPointerException
> at
> org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.processResourceBundles(ProcessRemoteResourcesMojo.java:1232)
> ... 23 more
> [ERROR]
> [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/MojoExecutionException
> {code}
> Looking into the code I noticed that an "unguarded close()" in a
> finally-block is the culprit. By replacing it with a call to
> {{IOUtil.close()}} the problem is gone. See the attached patch/diff.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Created] (MNGSITE-304) "Configuring Maven" guide contains misformatted tags
dennis lucero created MNGSITE-304: - Summary: "Configuring Maven" guide contains misformatted tags Key: MNGSITE-304 URL: https://issues.apache.org/jira/browse/MNGSITE-304 Project: Maven Project Web Site Issue Type: Bug Reporter: dennis lucero Priority: Trivial See https://maven.apache.org/guides/mini/guide-configuring-maven.html#Profiles . subsection , ul, li and so on should probably be HTML tags instead of italic text. -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (MRRESOURCES-101) NPE - Error rendering velocity resource
[
https://issues.apache.org/jira/browse/MRRESOURCES-101?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Daniel Klessing updated MRRESOURCES-101:
Description:
We noticed that occasionally the maven-remote-resources-plugin kills our build
as a NPE with the message "Error rendering velocity resource" happend.
Luckily I succeeded today in getting a stacktrace of the issue:
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process (default) on
project parent: Error rendering velocity resource. NullPointerException ->
[Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process (default) on
project parent: Error rendering velocity resource.
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 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 rendering
velocity resource.
at
org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.processResourceBundles(ProcessRemoteResourcesMojo.java:1246)
at
org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.execute(ProcessRemoteResourcesMojo.java:520)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
... 20 more
Caused by: java.lang.NullPointerException
at
org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.processResourceBundles(ProcessRemoteResourcesMojo.java:1232)
... 23 more
[ERROR]
[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/MojoExecutionException
{code}
Looking into the code I noticed that an "unguarded close()" in a finally-block
is the culprit. By replacing it with a call to {{IOUtil.close()}} the problem
is gone. See the attached patch/diff.
was:
We noticed that occasionally the maven-remote-resources-plugin kills our build
as a NPE with the message "Error rendering velocity resource" happend.
Luckily I succeeded today in getting a stacktrace of the issue:
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process (default) on
project parent: Error rendering velocity resource. NullPointerException ->
[Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process (default) on
project parent: Error rendering velocity resource.
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
[jira] [Created] (MRRESOURCES-101) NPE - Error rendering velocity resource
Daniel Klessing created MRRESOURCES-101:
---
Summary: NPE - Error rendering velocity resource
Key: MRRESOURCES-101
URL: https://issues.apache.org/jira/browse/MRRESOURCES-101
Project: Maven Remote Resources Plugin
Issue Type: Bug
Affects Versions: 1.5
Reporter: Daniel Klessing
Attachments: mrresources_npe.diff
We noticed that occasionally the maven-remote-resources-plugin kills our build
as a NPE with the message "Error rendering velocity resource" happend.
Luckily I succeeded today in getting a stacktrace of the issue:
{code}
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process (default) on
project parent: Error rendering velocity resource. NullPointerException ->
[Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute goal
org.apache.maven.plugins:maven-remote-resources-plugin:1.5:process (default) on
project parent: Error rendering velocity resource.
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 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 rendering
velocity resource.
at
org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.processResourceBundles(ProcessRemoteResourcesMojo.java:1246)
at
org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.execute(ProcessRemoteResourcesMojo.java:520)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:134)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:207)
... 20 more
Caused by: java.lang.NullPointerException
at
org.apache.maven.plugin.resources.remote.ProcessRemoteResourcesMojo.processResourceBundles(ProcessRemoteResourcesMojo.java:1232)
... 23 more
[ERROR]
[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/MojoExecutionException
{code}
Looking into the code I noticed that an "unguarded close()" in a finally-block
is the culprit. By replacing it with a call to IOUtils.close() the problem is
gone. See the attached patch/diff.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (WAGON-486) Wagon fails to download artifacts if number of dropped pooled connections (by intermediate) are greater than default retry count
[ https://issues.apache.org/jira/browse/WAGON-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated WAGON-486: - Summary: Wagon fails to download artifacts if number of dropped pooled connections (by intermediate) are greater than default retry count (was: Wagon fails to download artifact if number of dropped pooled connections by intermediate are bigger then default retry count) > Wagon fails to download artifacts if number of dropped pooled connections (by > intermediate) are greater than default retry count > > > Key: WAGON-486 > URL: https://issues.apache.org/jira/browse/WAGON-486 > Project: Maven Wagon > Issue Type: Bug >Reporter: Martin Myslík > Attachments: build-failure-maven-3.5.0-patched-debug.txt, > build-failure-maven-3.5.0-patched-debug-updated.txt, > build-failure-vanilla.txt, build-success-keep-alive-false.txt, > build-success-maven-3.5.0-patched-debug.txt, build-success-pooling-false.txt, > dump-failed-build.pcap, dump.pcap > > > I was recently discussing and issue with Atlassian team concerning failing > build on Atlassian Pipelines when running Maven build for more than 5 minutes. > The issue was with NAT timeout which kills all idle connections after 5 > mintues and Maven does not try to reconnect once the connection is killed > (and hence cannot download artifacts from Maven central). > Please, take a look at the open issue (it contains more detailed description > and also comments from Atlassian which suggested opening an issue with > Maven): > https://bitbucket.org/site/master/issues/13988/pipelines-kills-idle-maven-connections > Could you, please, take a minute and explain how could proceed with solving > this issue? I am not sure whether this is something that Maven should handle > or whether it is Atlassians issue. > Thank you for your input. > This is the link to my public repo with test project running tests for 15 > mintues. This build fails on Pipelines because of Maven connection that is > being killed during the test: https://bitbucket.org/Smedzlatko/del-me -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Updated] (WAGON-486) Wagon fails to download artifact if number of dropped pooled connections by intermediate are bigger then default retry count
[ https://issues.apache.org/jira/browse/WAGON-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Michael Osipov updated WAGON-486: - Summary: Wagon fails to download artifact if number of dropped pooled connections by intermediate are bigger then default retry count (was: Maven does not attempt to reconnect reset connections) > Wagon fails to download artifact if number of dropped pooled connections by > intermediate are bigger then default retry count > > > Key: WAGON-486 > URL: https://issues.apache.org/jira/browse/WAGON-486 > Project: Maven Wagon > Issue Type: Bug >Reporter: Martin Myslík > Attachments: build-failure-maven-3.5.0-patched-debug.txt, > build-failure-maven-3.5.0-patched-debug-updated.txt, > build-failure-vanilla.txt, build-success-keep-alive-false.txt, > build-success-maven-3.5.0-patched-debug.txt, build-success-pooling-false.txt, > dump-failed-build.pcap, dump.pcap > > > I was recently discussing and issue with Atlassian team concerning failing > build on Atlassian Pipelines when running Maven build for more than 5 minutes. > The issue was with NAT timeout which kills all idle connections after 5 > mintues and Maven does not try to reconnect once the connection is killed > (and hence cannot download artifacts from Maven central). > Please, take a look at the open issue (it contains more detailed description > and also comments from Atlassian which suggested opening an issue with > Maven): > https://bitbucket.org/site/master/issues/13988/pipelines-kills-idle-maven-connections > Could you, please, take a minute and explain how could proceed with solving > this issue? I am not sure whether this is something that Maven should handle > or whether it is Atlassians issue. > Thank you for your input. > This is the link to my public repo with test project running tests for 15 > mintues. This build fails on Pipelines because of Maven connection that is > being killed during the test: https://bitbucket.org/Smedzlatko/del-me -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (WAGON-486) Maven does not attempt to reconnect reset connections
[
https://issues.apache.org/jira/browse/WAGON-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15958989#comment-15958989
]
Michael Osipov commented on WAGON-486:
--
Checked the unpatched one, it completely resembles the debug output. {{TLS 1.2
Application Data}} => {{RST}}. As many times as the connections where open. The
{{DefaultHttpRequestRetryHandler}} kicks in and tries three times. Since we
have more than three broken connections, request for
{{maven-reporting-api-2.2.1.pom}} is deemed to fail.
Now, how do you expect the patch to look like? I don't want to close connection
by default after {{n}} min because this is not a regular issue.
> Maven does not attempt to reconnect reset connections
> -
>
> Key: WAGON-486
> URL: https://issues.apache.org/jira/browse/WAGON-486
> Project: Maven Wagon
> Issue Type: Bug
>Reporter: Martin Myslík
> Attachments: build-failure-maven-3.5.0-patched-debug.txt,
> build-failure-maven-3.5.0-patched-debug-updated.txt,
> build-failure-vanilla.txt, build-success-keep-alive-false.txt,
> build-success-maven-3.5.0-patched-debug.txt, build-success-pooling-false.txt,
> dump-failed-build.pcap, dump.pcap
>
>
> I was recently discussing and issue with Atlassian team concerning failing
> build on Atlassian Pipelines when running Maven build for more than 5 minutes.
> The issue was with NAT timeout which kills all idle connections after 5
> mintues and Maven does not try to reconnect once the connection is killed
> (and hence cannot download artifacts from Maven central).
> Please, take a look at the open issue (it contains more detailed description
> and also comments from Atlassian which suggested opening an issue with
> Maven):
> https://bitbucket.org/site/master/issues/13988/pipelines-kills-idle-maven-connections
> Could you, please, take a minute and explain how could proceed with solving
> this issue? I am not sure whether this is something that Maven should handle
> or whether it is Atlassians issue.
> Thank you for your input.
> This is the link to my public repo with test project running tests for 15
> mintues. This build fails on Pipelines because of Maven connection that is
> being killed during the test: https://bitbucket.org/Smedzlatko/del-me
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (WAGON-486) Maven does not attempt to reconnect reset connections
[ https://issues.apache.org/jira/browse/WAGON-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Myslík updated WAGON-486: Attachment: dump-failed-build.pcap [~michael-o] Here is the dump for the unpatched jar, as requested. > Maven does not attempt to reconnect reset connections > - > > Key: WAGON-486 > URL: https://issues.apache.org/jira/browse/WAGON-486 > Project: Maven Wagon > Issue Type: Bug >Reporter: Martin Myslík > Attachments: build-failure-maven-3.5.0-patched-debug.txt, > build-failure-maven-3.5.0-patched-debug-updated.txt, > build-failure-vanilla.txt, build-success-keep-alive-false.txt, > build-success-maven-3.5.0-patched-debug.txt, build-success-pooling-false.txt, > dump-failed-build.pcap, dump.pcap > > > I was recently discussing and issue with Atlassian team concerning failing > build on Atlassian Pipelines when running Maven build for more than 5 minutes. > The issue was with NAT timeout which kills all idle connections after 5 > mintues and Maven does not try to reconnect once the connection is killed > (and hence cannot download artifacts from Maven central). > Please, take a look at the open issue (it contains more detailed description > and also comments from Atlassian which suggested opening an issue with > Maven): > https://bitbucket.org/site/master/issues/13988/pipelines-kills-idle-maven-connections > Could you, please, take a minute and explain how could proceed with solving > this issue? I am not sure whether this is something that Maven should handle > or whether it is Atlassians issue. > Thank you for your input. > This is the link to my public repo with test project running tests for 15 > mintues. This build fails on Pipelines because of Maven connection that is > being killed during the test: https://bitbucket.org/Smedzlatko/del-me -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (WAGON-486) Maven does not attempt to reconnect reset connections
[
https://issues.apache.org/jira/browse/WAGON-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15958921#comment-15958921
]
Michael Osipov commented on WAGON-486:
--
Read the dump file, it pretty much looks like expected after the patch. Filter
for {{(ip.dst == 151.101.32.215 || ip.src == 151.101.32.215) && tcp.port ==
34456}} and see packets 8272, 8363, 8364, 8365, 8366:
{noformat}
827221.328162 10.244.71.4 151.101.32.215 TCP 68 34456 →
443 [ACK] Seq=154235 Ack=8528726 Win=473728 Len=0 TSval=10874206
TSecr=3108788332
8363389.026936 10.244.71.4 151.101.32.215 TLSv1.2 99
Encrypted Alert
8364389.026992 10.244.71.4 151.101.32.215 TCP 68 34456 →
443 [FIN, ACK] Seq=154266 Ack=8528726 Win=473728 Len=0 TSval=11241904
TSecr=3108788332
8365389.027333 151.101.32.215 10.244.71.4 TCP 56 443 →
34456 [RST] Seq=8528726 Win=1894912 Len=0
8366389.027427 151.101.32.215 10.244.71.4 TCP 56 443 →
34456 [RST] Seq=8528726 Win=1894912 Len=0
{noformat}
Last known request was at 21,3 seconds, 5 minutes passed and the HttpClient
knows that it has to evict the connection. I tells the TLS peer to close, sends
{{FIN, ACK}} and waits for an {{ACK}} likely, but the server has already closed
the connection and responds with {{RST}} for all other connections (see source
port).
Can you upload another gzipped dump without the patched JAR? I'd like to see
the opposite.
> Maven does not attempt to reconnect reset connections
> -
>
> Key: WAGON-486
> URL: https://issues.apache.org/jira/browse/WAGON-486
> Project: Maven Wagon
> Issue Type: Bug
>Reporter: Martin Myslík
> Attachments: build-failure-maven-3.5.0-patched-debug.txt,
> build-failure-maven-3.5.0-patched-debug-updated.txt,
> build-failure-vanilla.txt, build-success-keep-alive-false.txt,
> build-success-maven-3.5.0-patched-debug.txt, build-success-pooling-false.txt,
> dump.pcap
>
>
> I was recently discussing and issue with Atlassian team concerning failing
> build on Atlassian Pipelines when running Maven build for more than 5 minutes.
> The issue was with NAT timeout which kills all idle connections after 5
> mintues and Maven does not try to reconnect once the connection is killed
> (and hence cannot download artifacts from Maven central).
> Please, take a look at the open issue (it contains more detailed description
> and also comments from Atlassian which suggested opening an issue with
> Maven):
> https://bitbucket.org/site/master/issues/13988/pipelines-kills-idle-maven-connections
> Could you, please, take a minute and explain how could proceed with solving
> this issue? I am not sure whether this is something that Maven should handle
> or whether it is Atlassians issue.
> Thank you for your input.
> This is the link to my public repo with test project running tests for 15
> mintues. This build fails on Pipelines because of Maven connection that is
> being killed during the test: https://bitbucket.org/Smedzlatko/del-me
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Updated] (WAGON-486) Maven does not attempt to reconnect reset connections
[ https://issues.apache.org/jira/browse/WAGON-486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Martin Myslík updated WAGON-486: Attachment: dump.pcap Please, find the tcpdump attached. > Maven does not attempt to reconnect reset connections > - > > Key: WAGON-486 > URL: https://issues.apache.org/jira/browse/WAGON-486 > Project: Maven Wagon > Issue Type: Bug >Reporter: Martin Myslík > Attachments: build-failure-maven-3.5.0-patched-debug.txt, > build-failure-maven-3.5.0-patched-debug-updated.txt, > build-failure-vanilla.txt, build-success-keep-alive-false.txt, > build-success-maven-3.5.0-patched-debug.txt, build-success-pooling-false.txt, > dump.pcap > > > I was recently discussing and issue with Atlassian team concerning failing > build on Atlassian Pipelines when running Maven build for more than 5 minutes. > The issue was with NAT timeout which kills all idle connections after 5 > mintues and Maven does not try to reconnect once the connection is killed > (and hence cannot download artifacts from Maven central). > Please, take a look at the open issue (it contains more detailed description > and also comments from Atlassian which suggested opening an issue with > Maven): > https://bitbucket.org/site/master/issues/13988/pipelines-kills-idle-maven-connections > Could you, please, take a minute and explain how could proceed with solving > this issue? I am not sure whether this is something that Maven should handle > or whether it is Atlassians issue. > Thank you for your input. > This is the link to my public repo with test project running tests for 15 > mintues. This build fails on Pipelines because of Maven connection that is > being killed during the test: https://bitbucket.org/Smedzlatko/del-me -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (MNG-6156) Resolving dependencies is not thread-safe
[
https://issues.apache.org/jira/browse/MNG-6156?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15958498#comment-15958498
]
Roland Illig commented on MNG-6156:
---
Hello [~michael-o], did you find time to look into this issue?
> Resolving dependencies is not thread-safe
> -
>
> Key: MNG-6156
> URL: https://issues.apache.org/jira/browse/MNG-6156
> Project: Maven
> Issue Type: Bug
> Components: Artifacts and Repositories
>Affects Versions: 3.3.9
>Reporter: Roland Illig
> Attachments: dependency-list.txt, dependency-list-x.zip,
> wagon-not-threadsafe.zip
>
>
> When building a multi-module project in parallel, Maven updates the local
> Maven repository without taking into account that other threads or processes
> might do the same at the same time.
> To reproduce:
> 1. unpack the attached project
> 2. {{mvn dependency:list -U -B -T100}}
> See the attached {{dependency-list.txt}} for an example output.
> First thing to notice is that the dependency is downloaded 100 times. This is
> unexpected, since the Reactor should coordinate all the modules.
> Second thing to notice is that the build fails, since a dependency "cannot be
> found". This is wrong, since the dependency _can_ be found, it's just not
> processed properly.
> I suspect the {{legacy.DefaultWagonManager}} to be the cause of this, since
> the typical error messages are:
> * {{"Downloaded file does not exist: "}}
> * {{"Error copying temporary file to the final destination: "}}
> * {{"*** CHECKSUM FAILED - RETRYING"}}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Commented] (WAGON-486) Maven does not attempt to reconnect reset connections
[
https://issues.apache.org/jira/browse/WAGON-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15958484#comment-15958484
]
Michael Osipov commented on WAGON-486:
--
You can also use {{tcpdump}} on the interface. Wireshark will happily read the
file.
> Maven does not attempt to reconnect reset connections
> -
>
> Key: WAGON-486
> URL: https://issues.apache.org/jira/browse/WAGON-486
> Project: Maven Wagon
> Issue Type: Bug
>Reporter: Martin Myslík
> Attachments: build-failure-maven-3.5.0-patched-debug.txt,
> build-failure-maven-3.5.0-patched-debug-updated.txt,
> build-failure-vanilla.txt, build-success-keep-alive-false.txt,
> build-success-maven-3.5.0-patched-debug.txt, build-success-pooling-false.txt
>
>
> I was recently discussing and issue with Atlassian team concerning failing
> build on Atlassian Pipelines when running Maven build for more than 5 minutes.
> The issue was with NAT timeout which kills all idle connections after 5
> mintues and Maven does not try to reconnect once the connection is killed
> (and hence cannot download artifacts from Maven central).
> Please, take a look at the open issue (it contains more detailed description
> and also comments from Atlassian which suggested opening an issue with
> Maven):
> https://bitbucket.org/site/master/issues/13988/pipelines-kills-idle-maven-connections
> Could you, please, take a minute and explain how could proceed with solving
> this issue? I am not sure whether this is something that Maven should handle
> or whether it is Atlassians issue.
> Thank you for your input.
> This is the link to my public repo with test project running tests for 15
> mintues. This build fails on Pipelines because of Maven connection that is
> being killed during the test: https://bitbucket.org/Smedzlatko/del-me
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
[jira] [Comment Edited] (WAGON-486) Maven does not attempt to reconnect reset connections
[ https://issues.apache.org/jira/browse/WAGON-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15958418#comment-15958418 ] Martin Myslík edited comment on WAGON-486 at 4/6/17 7:16 AM: - [~michael-o] Thank you, Michael, for the comprehensive answer. I now understand the problem more clearly. I will try to run WIreshark during the Pipelines build and capture the traffic. was (Author: m.myslik): [~michael-o] Thank you, Michael, for the comprehensive answer. I now udnerstand the problem more clearly. I am not sure if I will be able to run WireShark during the Pipelines build but I will try to figure out some way to capture the traffic. > Maven does not attempt to reconnect reset connections > - > > Key: WAGON-486 > URL: https://issues.apache.org/jira/browse/WAGON-486 > Project: Maven Wagon > Issue Type: Bug >Reporter: Martin Myslík > Attachments: build-failure-maven-3.5.0-patched-debug.txt, > build-failure-maven-3.5.0-patched-debug-updated.txt, > build-failure-vanilla.txt, build-success-keep-alive-false.txt, > build-success-maven-3.5.0-patched-debug.txt, build-success-pooling-false.txt > > > I was recently discussing and issue with Atlassian team concerning failing > build on Atlassian Pipelines when running Maven build for more than 5 minutes. > The issue was with NAT timeout which kills all idle connections after 5 > mintues and Maven does not try to reconnect once the connection is killed > (and hence cannot download artifacts from Maven central). > Please, take a look at the open issue (it contains more detailed description > and also comments from Atlassian which suggested opening an issue with > Maven): > https://bitbucket.org/site/master/issues/13988/pipelines-kills-idle-maven-connections > Could you, please, take a minute and explain how could proceed with solving > this issue? I am not sure whether this is something that Maven should handle > or whether it is Atlassians issue. > Thank you for your input. > This is the link to my public repo with test project running tests for 15 > mintues. This build fails on Pipelines because of Maven connection that is > being killed during the test: https://bitbucket.org/Smedzlatko/del-me -- This message was sent by Atlassian JIRA (v6.3.15#6346)
[jira] [Commented] (WAGON-486) Maven does not attempt to reconnect reset connections
[ https://issues.apache.org/jira/browse/WAGON-486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15958418#comment-15958418 ] Martin Myslík commented on WAGON-486: - [~michael-o] Thank you, Michael, for the comprehensive answer. I now udnerstand the problem more clearly. I am not sure if I will be able to run WireShark during the Pipelines build but I will try to figure out some way to capture the traffic. > Maven does not attempt to reconnect reset connections > - > > Key: WAGON-486 > URL: https://issues.apache.org/jira/browse/WAGON-486 > Project: Maven Wagon > Issue Type: Bug >Reporter: Martin Myslík > Attachments: build-failure-maven-3.5.0-patched-debug.txt, > build-failure-maven-3.5.0-patched-debug-updated.txt, > build-failure-vanilla.txt, build-success-keep-alive-false.txt, > build-success-maven-3.5.0-patched-debug.txt, build-success-pooling-false.txt > > > I was recently discussing and issue with Atlassian team concerning failing > build on Atlassian Pipelines when running Maven build for more than 5 minutes. > The issue was with NAT timeout which kills all idle connections after 5 > mintues and Maven does not try to reconnect once the connection is killed > (and hence cannot download artifacts from Maven central). > Please, take a look at the open issue (it contains more detailed description > and also comments from Atlassian which suggested opening an issue with > Maven): > https://bitbucket.org/site/master/issues/13988/pipelines-kills-idle-maven-connections > Could you, please, take a minute and explain how could proceed with solving > this issue? I am not sure whether this is something that Maven should handle > or whether it is Atlassians issue. > Thank you for your input. > This is the link to my public repo with test project running tests for 15 > mintues. This build fails on Pipelines because of Maven connection that is > being killed during the test: https://bitbucket.org/Smedzlatko/del-me -- This message was sent by Atlassian JIRA (v6.3.15#6346)
