[jira] [Updated] (MRELEASE-703) [PATCH] Migration from obsolete plexus-maven-plugin to plexus-containers-component-metadata
[ https://issues.apache.org/jira/browse/MRELEASE-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte updated MRELEASE-703: Fix Version/s: 3.0 > [PATCH] Migration from obsolete plexus-maven-plugin to > plexus-containers-component-metadata > --- > > Key: MRELEASE-703 > URL: https://issues.apache.org/jira/browse/MRELEASE-703 > Project: Maven Release Plugin > Issue Type: Improvement >Affects Versions: 2.0 >Reporter: Jaromír Cápík > Fix For: 3.0 > > Attachments: 004_mavenreleaseplugin_componentmetadata.patch > > > The attached patch retires the obsolete plexus-maven-plugin and generates the > metadata with plexus-containers-component-metadata instead. > NOTE : The result XML file has a different order of elements, but all of them > are present. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MRELEASE-703) [PATCH] Migration from obsolete plexus-maven-plugin to plexus-containers-component-metadata
[
https://issues.apache.org/jira/browse/MRELEASE-703?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272215#comment-15272215
]
Robert Scholte commented on MRELEASE-703:
-
[r1742411|http://svn.apache.org/viewvc?rev=1742411&view=rev] replaces
{{generate-resources}} with {{generate-metadata}} after some required
preparations to switch.
> [PATCH] Migration from obsolete plexus-maven-plugin to
> plexus-containers-component-metadata
> ---
>
> Key: MRELEASE-703
> URL: https://issues.apache.org/jira/browse/MRELEASE-703
> Project: Maven Release Plugin
> Issue Type: Improvement
>Affects Versions: 2.0
>Reporter: Jaromír Cápík
> Fix For: 3.0
>
> Attachments: 004_mavenreleaseplugin_componentmetadata.patch
>
>
> The attached patch retires the obsolete plexus-maven-plugin and generates the
> metadata with plexus-containers-component-metadata instead.
> NOTE : The result XML file has a different order of elements, but all of them
> are present.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Closed] (MRELEASE-703) [PATCH] Migration from obsolete plexus-maven-plugin to plexus-containers-component-metadata
[ https://issues.apache.org/jira/browse/MRELEASE-703?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Robert Scholte closed MRELEASE-703. --- Resolution: Fixed Assignee: Robert Scholte Fix completed in [r1742413|http://svn.apache.org/viewvc?rev=1742413&view=rev] > [PATCH] Migration from obsolete plexus-maven-plugin to > plexus-containers-component-metadata > --- > > Key: MRELEASE-703 > URL: https://issues.apache.org/jira/browse/MRELEASE-703 > Project: Maven Release Plugin > Issue Type: Improvement >Affects Versions: 2.0 >Reporter: Jaromír Cápík >Assignee: Robert Scholte > Fix For: 3.0 > > Attachments: 004_mavenreleaseplugin_componentmetadata.patch > > > The attached patch retires the obsolete plexus-maven-plugin and generates the > metadata with plexus-containers-component-metadata instead. > NOTE : The result XML file has a different order of elements, but all of them > are present. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MRESOURCES-217) Updated plexus-utils to 3.0.23
Karl Heinz Marbaise created MRESOURCES-217: -- Summary: Updated plexus-utils to 3.0.23 Key: MRESOURCES-217 URL: https://issues.apache.org/jira/browse/MRESOURCES-217 Project: Maven Resources Plugin Issue Type: Improvement Affects Versions: 3.0.0 Reporter: Karl Heinz Marbaise Priority: Minor Fix For: 3.0.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MRESOURCES-217) Updated plexus-utils to 3.0.23
[ https://issues.apache.org/jira/browse/MRESOURCES-217?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MRESOURCES-217. -- Resolution: Fixed Assignee: Christian Schulte Done in [r174235|http://svn.apache.org/r1742353] > Updated plexus-utils to 3.0.23 > -- > > Key: MRESOURCES-217 > URL: https://issues.apache.org/jira/browse/MRESOURCES-217 > Project: Maven Resources Plugin > Issue Type: Improvement >Affects Versions: 3.0.0 >Reporter: Karl Heinz Marbaise >Assignee: Christian Schulte >Priority: Minor > Fix For: 3.0.0 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MJAVADOC-423) wrong link generation for org.xml.sax.helpers.DefaultHandler
[ https://issues.apache.org/jira/browse/MJAVADOC-423?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15272260#comment-15272260 ] Roman Ivanov commented on MJAVADOC-423: --- OpenJDK issue: https://bugs.openjdk.java.net/browse/JDK-8155805 > wrong link generation for org.xml.sax.helpers.DefaultHandler > > > Key: MJAVADOC-423 > URL: https://issues.apache.org/jira/browse/MJAVADOC-423 > Project: Maven Javadoc Plugin > Issue Type: Bug >Affects Versions: 2.10.1 >Reporter: Roman Ivanov > Attachments: linkcheck.html > > > Review report: > http://checkstyle.sourceforge.net/linkcheck.html > javadoc plugin - > https://github.com/checkstyle/checkstyle/blob/master/pom.xml#L524 > here you can see number of broken links as: > "http://docs.oracle.com/javase/6/docs/api/org/xml/sax/helpers.DefaultHandler.html?is-external=true: > 404 Not Found > " > problem is in "helpers.DefaultHandler.html" should be > "helpers/DefaultHandler.html" > I switched to java7 in latest code of checkstyle > (https://github.com/checkstyle/checkstyle) project , but problem is the same. > to reproduce problem please do : > git clone https://github.com/checkstyle/checkstyle > cd checkstyle > mvn -Pdistro clean package > after that review linkcheck maven report. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SUREFIRE-1246) Surefire + Cobertura: Shutdown of Forked JVM timeouts before all thread ends
Ivo Pinheiro created SUREFIRE-1246: -- Summary: Surefire + Cobertura: Shutdown of Forked JVM timeouts before all thread ends Key: SUREFIRE-1246 URL: https://issues.apache.org/jira/browse/SUREFIRE-1246 Project: Maven Surefire Issue Type: Bug Components: Maven Surefire Plugin Affects Versions: 2.19.1 Reporter: Ivo Pinheiro There should be a possibility to configure the Embedded shutdown timeout, to a value greater than 30 seconds. When using cobertura to evaluate the code coverage, and with a big number of tests to run, the surefire plugin does not wait for cobertura writes all cobertura information to cobertura.ser because the 30 seconds embedded shutdown timeout is not sufficient. Is it possible to add a configuration property to surefire-plugin to configure the embedded timeout time? -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MNG-6017) Removing ArtifactHandler for par
Karl Heinz Marbaise created MNG-6017: Summary: Removing ArtifactHandler for par Key: MNG-6017 URL: https://issues.apache.org/jira/browse/MNG-6017 Project: Maven Issue Type: Improvement Components: core Affects Versions: 3.3.9 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Priority: Minor Fix For: 3.4.0 Remove the ArtifactHandler definition for par lifecycle which has been [removed in Maven 3.3.9|MNG-5892] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MNG-6017) Removing ArtifactHandler for par LifeCycle
[ https://issues.apache.org/jira/browse/MNG-6017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MNG-6017: - Summary: Removing ArtifactHandler for par LifeCycle (was: Removing ArtifactHandler for par) > Removing ArtifactHandler for par LifeCycle > -- > > Key: MNG-6017 > URL: https://issues.apache.org/jira/browse/MNG-6017 > Project: Maven > Issue Type: Improvement > Components: core >Affects Versions: 3.3.9 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.4.0 > > > Remove the ArtifactHandler definition for par lifecycle which has been > [removed in Maven 3.3.9|MNG-5892] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Closed] (MNG-6017) Removing ArtifactHandler for par LifeCycle
[ https://issues.apache.org/jira/browse/MNG-6017?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MNG-6017. Resolution: Fixed Done in [f70e22ead6342e0dc68a3421c8b534e7b7bf6a8d|https://git-wip-us.apache.org/repos/asf?p=maven.git;a=commit;h=f70e22ead6342e0dc68a3421c8b534e7b7bf6a8d] > Removing ArtifactHandler for par LifeCycle > -- > > Key: MNG-6017 > URL: https://issues.apache.org/jira/browse/MNG-6017 > Project: Maven > Issue Type: Improvement > Components: core >Affects Versions: 3.3.9 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.4.0 > > > Remove the ArtifactHandler definition for par lifecycle which has been > [removed in Maven 3.3.9|MNG-5892] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (MNG-6017) Removing ArtifactHandler for par LifeCycle
[ https://issues.apache.org/jira/browse/MNG-6017?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273082#comment-15273082 ] Hudson commented on MNG-6017: - FAILURE: Integrated in maven-3.x #1264 (See [https://builds.apache.org/job/maven-3.x/1264/]) [MNG-6017] Removing ArtifactHandler for par LifeCycle o Removed (khmarbaise: rev f70e22ead6342e0dc68a3421c8b534e7b7bf6a8d) * maven-core/src/site/apt/artifact-handlers.apt * maven-core/src/main/resources/META-INF/plexus/artifact-handlers.xml > Removing ArtifactHandler for par LifeCycle > -- > > Key: MNG-6017 > URL: https://issues.apache.org/jira/browse/MNG-6017 > Project: Maven > Issue Type: Improvement > Components: core >Affects Versions: 3.3.9 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.4.0 > > > Remove the ArtifactHandler definition for par lifecycle which has been > [removed in Maven 3.3.9|MNG-5892] -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Moved] (MSHARED-514) if filter file does not exist it should optionally ignore it, not just throw an exception
[
https://issues.apache.org/jira/browse/MSHARED-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise moved MRESOURCES-144 to MSHARED-514:
Affects Version/s: (was: 2.4.3)
maven-filtering-3.1.0
Key: MSHARED-514 (was: MRESOURCES-144)
Project: Maven Shared Components (was: Maven Resources Plugin)
> if filter file does not exist it should optionally ignore it, not just throw
> an exception
> -
>
> Key: MSHARED-514
> URL: https://issues.apache.org/jira/browse/MSHARED-514
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-filtering
>Affects Versions: maven-filtering-3.1.0
>Reporter: richard stevenson
>Assignee: Olivier Lamy (*$^¨%`£)
>Priority: Minor
> Attachments: maven-filter.patch
>
>
> If you have a list of filter files
>
> a.properties
> b.properties
> ${prop.name}.properties
>
> It would be nice to tell the resources plugin to optioanlly ignore a file if
> it does not exist. Currently get the following stack trace:
> org.apache.maven.lifecycle.LifecycleExecutionException: Error loading
> property f
> ile 'D:\projects\.../src/main/filters/a.filter.properties'
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:719)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> fecycle(DefaultLifecycleExecutor.java:556)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> ltLifecycleExecutor.java:535)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> dleFailures(DefaultLifecycleExecutor.java:387)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> ts(DefaultLifecycleExecutor.java:348)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> fecycleExecutor.java:180)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6
> 0)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error loading
> propert
> y file 'D:\projects\.../src/main/filters/a.filter.properties'
> at
> org.apache.maven.plugin.resources.ResourcesMojo.execute(ResourcesMojo
> .java:269)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> nManager.java:490)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:694)
> ... 17 more
> Caused by: org.apache.maven.shared.filtering.MavenFilteringException: Error
> load
> ing property file 'D:\projects\.../src/main/filters/a.properties'
> at
> org.apache.maven.shared.filtering.DefaultMavenFileFilter.loadProperti
> es(DefaultMavenFileFilter.java:274)
> at
> org.apache.maven.shared.filtering.DefaultMavenFileFilter.getDefaultFi
> lterWrappers(DefaultMavenFileFilter.java:199)
> at
> org.apache.maven.shared.filtering.DefaultMavenResourcesFiltering.filt
> erResources(DefaultMavenResourcesFiltering.java:162)
> at
> org.apache.maven.plugin.resources.ResourcesMojo.execute(ResourcesMojo
> .java:265)
> ... 19 more
> Caused by: java.io.FileNotFoundException:
> D:\projects\.../src/main/filters/a.fil
> ter.properties
> at
> org.apache.maven.shared.filtering.PropertyUtils.loadPropertyFile(Prop
> ertyUtils.java:65)
> at
> org.apache.maven.shared.filtering.DefaultMavenFileFilter.loadProperti
> es(DefaultMavenFileFilter.java:269)
> ... 22 more
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Updated] (MSHARED-514) if filter file does not exist it should optionally ignore it, not just throw an exception
[
https://issues.apache.org/jira/browse/MSHARED-514?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MSHARED-514:
Component/s: maven-filtering
> if filter file does not exist it should optionally ignore it, not just throw
> an exception
> -
>
> Key: MSHARED-514
> URL: https://issues.apache.org/jira/browse/MSHARED-514
> Project: Maven Shared Components
> Issue Type: Improvement
> Components: maven-filtering
>Affects Versions: maven-filtering-3.1.0
>Reporter: richard stevenson
>Assignee: Olivier Lamy (*$^¨%`£)
>Priority: Minor
> Attachments: maven-filter.patch
>
>
> If you have a list of filter files
>
> a.properties
> b.properties
> ${prop.name}.properties
>
> It would be nice to tell the resources plugin to optioanlly ignore a file if
> it does not exist. Currently get the following stack trace:
> org.apache.maven.lifecycle.LifecycleExecutionException: Error loading
> property f
> ile 'D:\projects\.../src/main/filters/a.filter.properties'
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:719)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLi
> fecycle(DefaultLifecycleExecutor.java:556)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau
> ltLifecycleExecutor.java:535)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan
> dleFailures(DefaultLifecycleExecutor.java:387)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen
> ts(DefaultLifecycleExecutor.java:348)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi
> fecycleExecutor.java:180)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
> at
> org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:6
> 0)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.
> java:39)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces
> sorImpl.java:25)
> at java.lang.reflect.Method.invoke(Method.java:597)
> at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315)
> at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
> at
> org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430)
> at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
> Caused by: org.apache.maven.plugin.MojoExecutionException: Error loading
> propert
> y file 'D:\projects\.../src/main/filters/a.filter.properties'
> at
> org.apache.maven.plugin.resources.ResourcesMojo.execute(ResourcesMojo
> .java:269)
> at
> org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi
> nManager.java:490)
> at
> org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa
> ultLifecycleExecutor.java:694)
> ... 17 more
> Caused by: org.apache.maven.shared.filtering.MavenFilteringException: Error
> load
> ing property file 'D:\projects\.../src/main/filters/a.properties'
> at
> org.apache.maven.shared.filtering.DefaultMavenFileFilter.loadProperti
> es(DefaultMavenFileFilter.java:274)
> at
> org.apache.maven.shared.filtering.DefaultMavenFileFilter.getDefaultFi
> lterWrappers(DefaultMavenFileFilter.java:199)
> at
> org.apache.maven.shared.filtering.DefaultMavenResourcesFiltering.filt
> erResources(DefaultMavenResourcesFiltering.java:162)
> at
> org.apache.maven.plugin.resources.ResourcesMojo.execute(ResourcesMojo
> .java:265)
> ... 19 more
> Caused by: java.io.FileNotFoundException:
> D:\projects\.../src/main/filters/a.fil
> ter.properties
> at
> org.apache.maven.shared.filtering.PropertyUtils.loadPropertyFile(Prop
> ertyUtils.java:65)
> at
> org.apache.maven.shared.filtering.DefaultMavenFileFilter.loadProperti
> es(DefaultMavenFileFilter.java:269)
> ... 22 more
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
[jira] [Created] (WAGON-455) Upgrade of 'plexus-utils' to version 3.0.23.
Christian Schulte created WAGON-455: --- Summary: Upgrade of 'plexus-utils' to version 3.0.23. Key: WAGON-455 URL: https://issues.apache.org/jira/browse/WAGON-455 Project: Maven Wagon Issue Type: Task Reporter: Christian Schulte Assignee: Christian Schulte Priority: Trivial Fix For: 2.11 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (WAGON-455) Upgrade of 'plexus-utils' to version 3.0.23.
[ https://issues.apache.org/jira/browse/WAGON-455?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte resolved WAGON-455. - Resolution: Fixed > Upgrade of 'plexus-utils' to version 3.0.23. > > > Key: WAGON-455 > URL: https://issues.apache.org/jira/browse/WAGON-455 > Project: Maven Wagon > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: 2.11 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Commented] (WAGON-455) Upgrade of 'plexus-utils' to version 3.0.23.
[ https://issues.apache.org/jira/browse/WAGON-455?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=15273440#comment-15273440 ] Hudson commented on WAGON-455: -- FAILURE: Integrated in maven-wagon #1304 (See [https://builds.apache.org/job/maven-wagon/1304/]) [WAGON-455] Upgrade of 'plexus-utils' to version 3.0.23. (schulte2005: rev 120bfe90cca2da583ed2317dd19d9389b5ba6306) * pom.xml [WAGON-455] Upgrade of 'plexus-utils' to version 3.0.23. (schulte2005: rev f3462c3f276b2449689eda1f52c3fa1f8e2177ae) * wagon-tcks/wagon-tck-http/src/main/java/org/apache/maven/wagon/tck/http/Assertions.java * wagon-tcks/wagon-tck-http/src/main/java/org/apache/maven/wagon/tck/http/fixture/LatencyServlet.java * wagon-providers/wagon-ssh/src/main/java/org/apache/maven/wagon/providers/ssh/jsch/AbstractJschWagon.java * wagon-providers/wagon-ssh-common/src/main/java/org/apache/maven/wagon/providers/ssh/ScpHelper.java * wagon-provider-api/src/main/java/org/apache/maven/wagon/StreamWagon.java * wagon-provider-test/src/main/java/org/apache/maven/wagon/StreamingWagonTestCase.java * wagon-providers/wagon-http/src/main/java/org/apache/maven/wagon/providers/http/AbstractHttpClientWagon.java * wagon-provider-test/src/main/java/org/apache/maven/wagon/http/HttpWagonTestCase.java * wagon-tcks/wagon-tck-http/src/main/java/org/apache/maven/wagon/tck/http/util/TestUtil.java * wagon-providers/wagon-ssh-common-test/src/main/java/org/apache/maven/wagon/providers/ssh/TestPublickeyAuthenticator.java * wagon-providers/wagon-ssh-common/src/main/java/org/apache/maven/wagon/providers/ssh/knownhost/StreamKnownHostsProvider.java * wagon-provider-api/src/main/java/org/apache/maven/wagon/AbstractWagon.java * wagon-providers/wagon-ftp/src/main/java/org/apache/maven/wagon/providers/ftp/FtpWagon.java * wagon-providers/wagon-http-lightweight/src/main/java/org/apache/maven/wagon/providers/http/LightweightHttpWagon.java * wagon-providers/wagon-webdav-jackrabbit/src/main/java/org/apache/maven/wagon/providers/webdav/AbstractHttpClientWagon.java > Upgrade of 'plexus-utils' to version 3.0.23. > > > Key: WAGON-455 > URL: https://issues.apache.org/jira/browse/WAGON-455 > Project: Maven Wagon > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: 2.11 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MNG-6018) Internal errors building eclipse-repository Tycho project
Barys Dubauski created MNG-6018: --- Summary: Internal errors building eclipse-repository Tycho project Key: MNG-6018 URL: https://issues.apache.org/jira/browse/MNG-6018 Project: Maven Issue Type: Bug Components: core Reporter: Barys Dubauski I'm running a maven/tycho build of the small project containing .product file. The project has eclipse-repository packaging type. Typical command is: mvn clean install. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MNG-6018) Internal errors building eclipse-repository Tycho project
[ https://issues.apache.org/jira/browse/MNG-6018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barys Dubauski updated MNG-6018: Attachment: debug.log The output of running mvn clean install -X > debug.log command > Internal errors building eclipse-repository Tycho project > - > > Key: MNG-6018 > URL: https://issues.apache.org/jira/browse/MNG-6018 > Project: Maven > Issue Type: Bug > Components: core >Reporter: Barys Dubauski > Attachments: debug.log > > > I'm running a maven/tycho build of the small project containing .product > file. The project has eclipse-repository packaging type. > Typical command is: mvn clean install. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MNG-6018) Internal errors building eclipse-repository Tycho project
[ https://issues.apache.org/jira/browse/MNG-6018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barys Dubauski updated MNG-6018: Attachment: MNG-6018.zip Sample project where the error happens. > Internal errors building eclipse-repository Tycho project > - > > Key: MNG-6018 > URL: https://issues.apache.org/jira/browse/MNG-6018 > Project: Maven > Issue Type: Bug > Components: core >Reporter: Barys Dubauski > Attachments: MNG-6018.zip, debug.log > > > I'm running a maven/tycho build of the small project containing .product > file. The project has eclipse-repository packaging type. > Typical command is: mvn clean install. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MNG-6018) Internal errors building eclipse-repository Tycho project
[ https://issues.apache.org/jira/browse/MNG-6018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barys Dubauski updated MNG-6018: Description: I'm running a maven/tycho build of the small project containing .product file. The project has eclipse-repository packaging type. Steps: 1. Unpack the MNG-6018.zip 2. cd products/com.ibm.build.ccb.test.rcp.hello.world 3. mvn clean install I'm using latest Maven 3.3.9 and Tycho 0.24.0 was: I'm running a maven/tycho build of the small project containing .product file. The project has eclipse-repository packaging type. Typical command is: mvn clean install. > Internal errors building eclipse-repository Tycho project > - > > Key: MNG-6018 > URL: https://issues.apache.org/jira/browse/MNG-6018 > Project: Maven > Issue Type: Bug > Components: core >Reporter: Barys Dubauski > Attachments: MNG-6018.zip, debug.log > > > I'm running a maven/tycho build of the small project containing .product > file. The project has eclipse-repository packaging type. > Steps: > 1. Unpack the MNG-6018.zip > 2. cd products/com.ibm.build.ccb.test.rcp.hello.world > 3. mvn clean install > I'm using latest Maven 3.3.9 and Tycho 0.24.0 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Updated] (MNG-6018) Internal errors building eclipse-repository Tycho project
[ https://issues.apache.org/jira/browse/MNG-6018?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Barys Dubauski updated MNG-6018: Description: I'm running a maven/tycho build of the small project containing .product file. The project has eclipse-repository packaging type. Steps: 1. Unpack the MNG-6018.zip 2. cd products/com.ibm.build.ccb.test.rcp.hello.world 3. mvn clean install I'm using latest Maven 3.3.9 and Tycho 0.24.0 on Mac OS X 10.11.4 El Capitan. was: I'm running a maven/tycho build of the small project containing .product file. The project has eclipse-repository packaging type. Steps: 1. Unpack the MNG-6018.zip 2. cd products/com.ibm.build.ccb.test.rcp.hello.world 3. mvn clean install I'm using latest Maven 3.3.9 and Tycho 0.24.0 > Internal errors building eclipse-repository Tycho project > - > > Key: MNG-6018 > URL: https://issues.apache.org/jira/browse/MNG-6018 > Project: Maven > Issue Type: Bug > Components: core >Reporter: Barys Dubauski > Attachments: MNG-6018.zip, debug.log > > > I'm running a maven/tycho build of the small project containing .product > file. The project has eclipse-repository packaging type. > Steps: > 1. Unpack the MNG-6018.zip > 2. cd products/com.ibm.build.ccb.test.rcp.hello.world > 3. mvn clean install > I'm using latest Maven 3.3.9 and Tycho 0.24.0 on Mac OS X 10.11.4 El Capitan. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (SCM-824) Upgrade of 'plexus-utils' to 3.0.23.
Christian Schulte created SCM-824: - Summary: Upgrade of 'plexus-utils' to 3.0.23. Key: SCM-824 URL: https://issues.apache.org/jira/browse/SCM-824 Project: Maven SCM Issue Type: Task Reporter: Christian Schulte Assignee: Christian Schulte Priority: Trivial Fix For: 1.9.5 -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Resolved] (SCM-824) Upgrade of 'plexus-utils' to 3.0.23.
[ https://issues.apache.org/jira/browse/SCM-824?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Christian Schulte resolved SCM-824. --- Resolution: Fixed > Upgrade of 'plexus-utils' to 3.0.23. > > > Key: SCM-824 > URL: https://issues.apache.org/jira/browse/SCM-824 > Project: Maven SCM > Issue Type: Task >Reporter: Christian Schulte >Assignee: Christian Schulte >Priority: Trivial > Fix For: 1.9.5 > > -- This message was sent by Atlassian JIRA (v6.3.4#6332)
[jira] [Created] (MDEP-526) copy and copy-dependencies should take latest release version from version range
abhishek sinha created MDEP-526: --- Summary: copy and copy-dependencies should take latest release version from version range Key: MDEP-526 URL: https://issues.apache.org/jira/browse/MDEP-526 Project: Maven Dependency Plugin Issue Type: Improvement Components: copy, copy-dependencies Reporter: abhishek sinha Priority: Minor In my pom, I have specified version range in properties like: [1.3.16, 1.4.0-SNAPSHOT) Currently copy and copy-dependency goals will copy latest SNAPSHOT jar to specified output directory. My requirement is to have have a configuration which allows to copy latest released jar from the specified version range. I checked out source code for maven-dependency-plugin and did some modification to make it work. So if this improvement is accepted then how can I contribute to the solution I have. -- This message was sent by Atlassian JIRA (v6.3.4#6332)
