[ANN] Apache Maven Shared Component: Maven Shared Utils Version 0.7 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Shared Component: Maven Shared Utils Version 0.7 This project aims to be a functional replacement for plexus-utils in Maven. It is not a 100% API compatible replacement though but a replacement with improvements: lots of methods got cleaned up, generics got added and we dropped a lot of unused code. http://maven.apache.org/shared/maven-shared-utils/ You should specify the version in your project's plugin configuration: org.apache.maven.shared maven-shared-utils 0.7 Release Notes - Apache Maven Shared Utils - Version 0.7 http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11761&version=20207 Bugs: * [MSHARED-242] - [shared-utils] improve shared utils featuers and introduce generics where possible * [MSHARED-313] - port dotted expression parser fixes from plexus-utils * [MSHARED-369] - ReflectionValueExtractor regression; incorrect parsing Improvement: * [MSHARED-364] - Use NIO Delete when possibly in deleteFiles New Features: * [MSHARED-330] - add StringUtils.endsWithIgnoreCase() Wish: * [MSHARED-257] - extract merge feature from Xpp3Dom Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven Shared Component: Maven Filtering Version 1.3 Released
The Apache Maven team is pleased to announce the release of the Apache Maven Shared Component: Maven Filtering Version 1.3 The goal is to provide a shared component for all plugins that needs to filter resources. http://maven.apache.org/shared/maven-filtering/ You should specify the version in your project's plugin configuration: org.apache.maven.shared maven-filtering 1.3 Release Notes - Maven Filtering - Version 1.3 http://jira.codehaus.org/secure/ReleaseNote.jspa?version=20184&styleName=Text&projectId=11761 Bug: * [MSHARED-325] - maven-filtering 1.2 throws MavenFilteringException: Mark invalid Improvements: * [MSHARED-351] - Update version of plexus-interpolation to 1.19 * [MSHARED-352] - Update version of plexus-utils to 3.0.18 * [MSHARED-353] - Upgrade maven-shared-utils to 0.6 * [MSHARED-354] - Removed dependency plexus-container-default:1.0-alpha-9-stable-1 * [MSHARED-355] - Upgrade to Maven 2.2.1 compatiblity * [MSHARED-366] - Add ability to do Stream/Reader based filtering Enjoy, -The Apache Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven occasionally hangs within Surefire
It took me some digging, but you use a 30 second fork-timeout (configured in the uppermost basepom-foundation). And you increased some sleep times in that module earlier today... :-) Might that be it? 2014-10-23 19:40 GMT+02:00 Whitney Sorenson : > Thanks for the tip, Andreas. > > This seems to have moved us from one problem to another; now we see this > error (again only on Travis and some machines and not on our Jenkins - and > far more often on Java 7 than 8 - > https://travis-ci.org/HubSpot/Singularity/builds/38833718): > > [ERROR] Failed to execute goal > org.apache.maven.plugins:maven-surefire-plugin:2.18-SNAPSHOT:test > (default-test) on project SingularityService: There was a timeout or other > error in the fork -> [Help 1] > > > > On Thu, Oct 23, 2014 at 9:29 AM, Andreas Gudian > wrote: > > > Hi there, > > > > I bet that's a bug that we already fixed for Surefire 2.18 - you could > try > > a current snapshot version to verify if it works for you. > > > > Jira issue: > > https://jira.codehaus.org/plugins/servlet/mobile#issue/SUREFIRE-1091 > > > > We are planning to release 2.18 soonish, definitely this year ;-). > > > > Andreas > > > > Am Mittwoch, 22. Oktober 2014 schrieb Whitney Sorenson : > > > > > Ah, here you go: > > > > > > > > > > > > https://gist.githubusercontent.com/tpetr/1bdd2cfd362f125b4f06/raw/04009f51815f64606c14e7dc87eac9a4259701be/other%20jstack > > > > > > On Wed, Oct 22, 2014 at 4:56 PM, Kristian Rosenvold < > > > kristian.rosenv...@gmail.com > wrote: > > > > > > > It would be equally interesting to see the jstack of the *other* java > > > > process at the same time, since these two processes communicate with > > > > each other. It looks like the booted process is waiting for something > > > > from the main java launcher... > > > > > > > > Kristian > > > > > > > > > > > > 2014-10-22 22:43 GMT+02:00 Whitney Sorenson > > >: > > > > > I'm trying to fix a build issue where Maven hangs running tests. > This > > > > > happens about 30% of the time on our Travis builds. > > > > > > > > > > It never happens on our Jenkins cluster, but it happens > occasionally > > on > > > > > some of our local machines. We were able to capture a jstack and > lsof > > > > from > > > > > the process after it hung. > > > > > > > > > > Any tips on how to debug? Relevant captured data is here: > > > > > > > > > > https://gist.github.com/tpetr/1bdd2cfd362f125b4f06 > > > > > > > > > > I can't file an issue here [1] as I don't have an account. > > > > > > > > > > Thanks; > > > > > > > > > > -Whitney > > > > > > > > > > [1] - > > > > > > > > > > > > > > > http://jira.codehaus.org/browse/SUREFIRE#selectedTab=com.atlassian.jira.plugin.system.project%3Aissues-panel > > > > > > > > - > > > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > > > > > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > > > > > > > > > > > > >
Re: Maven occasionally hangs within Surefire
Thanks for the tip, Andreas. This seems to have moved us from one problem to another; now we see this error (again only on Travis and some machines and not on our Jenkins - and far more often on Java 7 than 8 - https://travis-ci.org/HubSpot/Singularity/builds/38833718): [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.18-SNAPSHOT:test (default-test) on project SingularityService: There was a timeout or other error in the fork -> [Help 1] On Thu, Oct 23, 2014 at 9:29 AM, Andreas Gudian wrote: > Hi there, > > I bet that's a bug that we already fixed for Surefire 2.18 - you could try > a current snapshot version to verify if it works for you. > > Jira issue: > https://jira.codehaus.org/plugins/servlet/mobile#issue/SUREFIRE-1091 > > We are planning to release 2.18 soonish, definitely this year ;-). > > Andreas > > Am Mittwoch, 22. Oktober 2014 schrieb Whitney Sorenson : > > > Ah, here you go: > > > > > > > https://gist.githubusercontent.com/tpetr/1bdd2cfd362f125b4f06/raw/04009f51815f64606c14e7dc87eac9a4259701be/other%20jstack > > > > On Wed, Oct 22, 2014 at 4:56 PM, Kristian Rosenvold < > > kristian.rosenv...@gmail.com > wrote: > > > > > It would be equally interesting to see the jstack of the *other* java > > > process at the same time, since these two processes communicate with > > > each other. It looks like the booted process is waiting for something > > > from the main java launcher... > > > > > > Kristian > > > > > > > > > 2014-10-22 22:43 GMT+02:00 Whitney Sorenson > >: > > > > I'm trying to fix a build issue where Maven hangs running tests. This > > > > happens about 30% of the time on our Travis builds. > > > > > > > > It never happens on our Jenkins cluster, but it happens occasionally > on > > > > some of our local machines. We were able to capture a jstack and lsof > > > from > > > > the process after it hung. > > > > > > > > Any tips on how to debug? Relevant captured data is here: > > > > > > > > https://gist.github.com/tpetr/1bdd2cfd362f125b4f06 > > > > > > > > I can't file an issue here [1] as I don't have an account. > > > > > > > > Thanks; > > > > > > > > -Whitney > > > > > > > > [1] - > > > > > > > > > > http://jira.codehaus.org/browse/SUREFIRE#selectedTab=com.atlassian.jira.plugin.system.project%3Aissues-panel > > > > > > - > > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > > > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > > > > > > >
Re: Maven occasionally hangs within Surefire
Hi there, I bet that's a bug that we already fixed for Surefire 2.18 - you could try a current snapshot version to verify if it works for you. Jira issue: https://jira.codehaus.org/plugins/servlet/mobile#issue/SUREFIRE-1091 We are planning to release 2.18 soonish, definitely this year ;-). Andreas Am Mittwoch, 22. Oktober 2014 schrieb Whitney Sorenson : > Ah, here you go: > > > https://gist.githubusercontent.com/tpetr/1bdd2cfd362f125b4f06/raw/04009f51815f64606c14e7dc87eac9a4259701be/other%20jstack > > On Wed, Oct 22, 2014 at 4:56 PM, Kristian Rosenvold < > kristian.rosenv...@gmail.com > wrote: > > > It would be equally interesting to see the jstack of the *other* java > > process at the same time, since these two processes communicate with > > each other. It looks like the booted process is waiting for something > > from the main java launcher... > > > > Kristian > > > > > > 2014-10-22 22:43 GMT+02:00 Whitney Sorenson >: > > > I'm trying to fix a build issue where Maven hangs running tests. This > > > happens about 30% of the time on our Travis builds. > > > > > > It never happens on our Jenkins cluster, but it happens occasionally on > > > some of our local machines. We were able to capture a jstack and lsof > > from > > > the process after it hung. > > > > > > Any tips on how to debug? Relevant captured data is here: > > > > > > https://gist.github.com/tpetr/1bdd2cfd362f125b4f06 > > > > > > I can't file an issue here [1] as I don't have an account. > > > > > > Thanks; > > > > > > -Whitney > > > > > > [1] - > > > > > > http://jira.codehaus.org/browse/SUREFIRE#selectedTab=com.atlassian.jira.plugin.system.project%3Aissues-panel > > > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > >
Re: Maven Release Plugin Unexpected Behaviour
maven-release-plugin
2.5.1
does the job
as does
mvn org.apache.maven.plugins:maven-release-plugin:2.5.1:prepare
org.apache.maven.plugins:maven-release-plugin:2.5.1:perform
On 23 October 2014 09:51, Vlad Slepukhin wrote:
> Hello!
>
> I has already posted this question to StackOverflow, though I didn’t get
> much help (expect warning about git requirements for 2.5.x version).
>
> The thing is that I’m trying to set up our project deployment to Nexus
> process via release-plugin. My script is:
>
> git checkout -b release-${RELEASE_VERSION}
> mvn org.apache.maven.plugins:maven-release-plugin:2.4.2:prepare
> -DautoVersionSubmodules=true
> -DdevelopmentVersion=${RELEASE_VERSION}.1-SNAPSHOT -DpushChanges=true
> -DreleaseVersion=${RELEASE_VERSION}.0 -Dtag=v${RELEASE_VERSION}.0
> mvn org.apache.maven.plugins:maven-release-plugin:2.4.2:perform
>
> The problem is: if this plugin (and its SCM dependency) is not added to
> the main project pom, it is going to push your artifact to snapshot
> repository with wrong name and WONT’T push updates to your branch.
>
> It seems to repeat this problem:
> https://jira.codehaus.org/browse/MRELEASE-812
>
> However, it was closed in 1.9.1 of maven-scm-provider-gitexe, which I’m
> using right now.
>
> Any ideas on solving this issue without adding next lines to main pom:
>
>
> maven-release-plugin
>2.4.2
>
>
>org.apache.maven.scm
>maven-scm-provider-gitexe
> 1.9.2
>
>
>
>
> --
> Kind Regards,
> Vlad Slepukhin
>
>
Re: Javadoc plugin parsing problem
On Wednesday, 22 October 2014 at 14:08, Michal Konopa wrote:
> Hello all,
> I'm experimenting a little bit with aggregating Javadoc from dependency
> sources - according to:
> http://maven.apache.org/plugins/maven-javadoc-plugin/examples/aggregate-dependency-sources.html
>
> document.
>
> I put the Javadoc plugin inside build tag of my POM :
>
> org.apache.maven.plugins
> maven-javadoc-plugin
> 2.10.1
>
> ${project.build.directory}/javadoc
> ${project.reporting.outputDirectory}/javadoc
>
>
>
> attach-javadocs
> package
>
> jar
>
>
> true
> commons-cli:*
>
>
^ this is wrong, it should be:
commons-cli:*
as in the example at
http://maven.apache.org/plugins/maven-javadoc-plugin/examples/aggregate-dependency-sources.html#Fine-Tuning_Included_Dependencies
( BTW the error indicates this because it says it is expecting a list of
elements but is instead being given a string )
>
>
>
>
>
> But I got the following error:
>
> Failed to execute goal
> org.apache.maven.plugins:maven-javadoc-plugin:2.10.1:jar
> (attach-javadocs) on project simply-iqrf-dpa-v210: Unable to parse
> configuration of mojo
> org.apache.maven.plugins:maven-javadoc-plugin:2.10.1:jar for parameter
> dependencySourceExcludes: Cannot assign configuration entry
> 'dependencySourceExcludes' with value 'commons-cli:*' of type
> java.lang.String to property of type java.util.List -> [Help 1]
> org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
> execute goal org.apache.maven.plugins:maven-javadoc-plugin:2.10.1:jar
> (attach-javadocs) on project simply-iqrf-dpa-v210: Unable to parse
> configuration of mojo
> org.apache.maven.plugins:maven-javadoc-plugin:2.10.1:jar for parameter
> dependencySourceExcludes: Cannot assign configuration entry
> 'dependencySourceExcludes' with value 'commons-cli:*' of type
> java.lang.String to property of type java.util.List
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:221)
> 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:84)
> at
> org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
> at
> org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
> at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
> at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
> at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
> at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
> at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at
> sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at
> sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
> at
> org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
> Caused by: org.apache.maven.plugin.PluginConfigurationException: Unable
> to parse configuration of mojo
> org.apache.maven.plugins:maven-javadoc-plugin:2.10.1:jar for parameter
> dependencySourceExcludes: Cannot assign configuration entry
> 'dependencySourceExcludes' with value 'commons-cli:*' of type
> java.lang.String to property of type java.util.List
> at
> org.apache.maven.plugin.internal.DefaultMavenPluginManager.populatePluginFields(DefaultMavenPluginManager.java:597)
> at
> org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo(DefaultMavenPluginManager.java:529)
> at
> org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:92)
> at
> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
> ... 19 more
> Caused by:
> org.codehaus.plexus.component.configurator.ComponentConfigurationException:
> Cannot assign configuration entry 'dependencySourceExcludes' with value
> 'commons-cli:*' of type java.lang.String to property of type java.util.List
> at
> org.codehaus.plexus.component.configurator.converters.AbstractConfigurationConverter.failIfNotTypeCompatible(AbstractConfigurationConverter.java:172)
> at
> org.codehaus.plexus.component.configurator.converters.composite.CollectionConverter.fromConfiguration(CollectionConverter.java:107)
> at
> org.codehaus.plexus.component.c
Re: Company-wide checkstyle.xml ?
Something similar is done in Geomajas, a separated dependency with the checkstyle configuration. See https://github.com/geomajas/geomajas-build-tools/tree/master/geomajas-checkstyle Kind regards, Joachim On 10/21/2014 02:16 AM, Bernd Eckenfels wrote: Am Mon, 20 Oct 2014 11:47:05 -0400 schrieb Jason van Zyl : The best mechanism I have seen to date for sharing configuration amongst many projects is the Airbase POM in the Airlift project that was developed by Henning (I've cc'd him). It seems that the project is well documented in the readme on Github: https://github.com/airlift/airbase/blob/master/pom.xml However what I see there: - the LICENSE-HEADER.txt template can be shared with modules (each module must define air.main.basedir of its project parent. - PMD is confiuged only with PMD shipped rulesets (/rulesets/java/basic.xml...). I guess this is from the PMD plugin. So custom rules would require a new plugin? So not sure if any of those fix the problem. I suspect packaing the rules up in a plugin dependency might work (as long as they have their own parent). - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Javadoc plugin parsing problem
Hello all,
I'm experimenting a little bit with aggregating Javadoc from dependency
sources - according to:
http://maven.apache.org/plugins/maven-javadoc-plugin/examples/aggregate-dependency-sources.html
document.
I put the Javadoc plugin inside build tag of my POM :
org.apache.maven.plugins
maven-javadoc-plugin
2.10.1
${project.build.directory}/javadoc
${project.reporting.outputDirectory}/javadoc
attach-javadocs
package
jar
true
commons-cli:*
But I got the following error:
Failed to execute goal
org.apache.maven.plugins:maven-javadoc-plugin:2.10.1:jar
(attach-javadocs) on project simply-iqrf-dpa-v210: Unable to parse
configuration of mojo
org.apache.maven.plugins:maven-javadoc-plugin:2.10.1:jar for parameter
dependencySourceExcludes: Cannot assign configuration entry
'dependencySourceExcludes' with value 'commons-cli:*' of type
java.lang.String to property of type java.util.List -> [Help 1]
org.apache.maven.lifecycle.LifecycleExecutionException: Failed to
execute goal org.apache.maven.plugins:maven-javadoc-plugin:2.10.1:jar
(attach-javadocs) on project simply-iqrf-dpa-v210: Unable to parse
configuration of mojo
org.apache.maven.plugins:maven-javadoc-plugin:2.10.1:jar for parameter
dependencySourceExcludes: Cannot assign configuration entry
'dependencySourceExcludes' with value 'commons-cli:*' of type
java.lang.String to property of type java.util.List
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:221)
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:84)
at
org.apache.maven.lifecycle.internal.LifecycleModuleBuilder.buildProject(LifecycleModuleBuilder.java:59)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.singleThreadedBuild(LifecycleStarter.java:183)
at
org.apache.maven.lifecycle.internal.LifecycleStarter.execute(LifecycleStarter.java:161)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:320)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:156)
at org.apache.maven.cli.MavenCli.execute(MavenCli.java:537)
at org.apache.maven.cli.MavenCli.doMain(MavenCli.java:196)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:141)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
at java.lang.reflect.Method.invoke(Method.java:606)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launchEnhanced(Launcher.java:290)
at
org.codehaus.plexus.classworlds.launcher.Launcher.launch(Launcher.java:230)
at
org.codehaus.plexus.classworlds.launcher.Launcher.mainWithExitCode(Launcher.java:409)
at
org.codehaus.plexus.classworlds.launcher.Launcher.main(Launcher.java:352)
Caused by: org.apache.maven.plugin.PluginConfigurationException: Unable
to parse configuration of mojo
org.apache.maven.plugins:maven-javadoc-plugin:2.10.1:jar for parameter
dependencySourceExcludes: Cannot assign configuration entry
'dependencySourceExcludes' with value 'commons-cli:*' of type
java.lang.String to property of type java.util.List
at
org.apache.maven.plugin.internal.DefaultMavenPluginManager.populatePluginFields(DefaultMavenPluginManager.java:597)
at
org.apache.maven.plugin.internal.DefaultMavenPluginManager.getConfiguredMojo(DefaultMavenPluginManager.java:529)
at
org.apache.maven.plugin.DefaultBuildPluginManager.executeMojo(DefaultBuildPluginManager.java:92)
at
org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:209)
... 19 more
Caused by:
org.codehaus.plexus.component.configurator.ComponentConfigurationException:
Cannot assign configuration entry 'dependencySourceExcludes' with value
'commons-cli:*' of type java.lang.String to property of type java.util.List
at
org.codehaus.plexus.component.configurator.converters.AbstractConfigurationConverter.failIfNotTypeCompatible(AbstractConfigurationConverter.java:172)
at
org.codehaus.plexus.component.configurator.converters.composite.CollectionConverter.fromConfiguration(CollectionConverter.java:107)
at
org.codehaus.plexus.component.configurator.converters.ComponentValueSetter.configure(ComponentValueSetter.java:342)
at
org.codehaus.plexus.component.configurator.converters.composite.ObjectWithFieldsConverter.processConfiguration(ObjectWithFieldsCo
Maven Release Plugin Unexpected Behaviour
Hello!
I has already posted this question to StackOverflow, though I didn’t get much
help (expect warning about git requirements for 2.5.x version).
The thing is that I’m trying to set up our project deployment to Nexus process
via release-plugin. My script is:
git checkout -b release-${RELEASE_VERSION}
mvn org.apache.maven.plugins:maven-release-plugin:2.4.2:prepare
-DautoVersionSubmodules=true -DdevelopmentVersion=${RELEASE_VERSION}.1-SNAPSHOT
-DpushChanges=true -DreleaseVersion=${RELEASE_VERSION}.0
-Dtag=v${RELEASE_VERSION}.0
mvn org.apache.maven.plugins:maven-release-plugin:2.4.2:perform
The problem is: if this plugin (and its SCM dependency) is not added to the
main project pom, it is going to push your artifact to snapshot repository with
wrong name and WONT’T push updates to your branch.
It seems to repeat this problem: https://jira.codehaus.org/browse/MRELEASE-812
However, it was closed in 1.9.1 of maven-scm-provider-gitexe, which I’m using
right now.
Any ideas on solving this issue without adding next lines to main pom:
maven-release-plugin
2.4.2
org.apache.maven.scm
maven-scm-provider-gitexe
1.9.2
--
Kind Regards,
Vlad Slepukhin
