from:"Mirko Friedenhagen"

Stephen, Russel,

thanks for your suggestions so far. I will take a look into the plugins you
mentioned.

Our operations department is using puppet and I did some tiny steps with. I
agree it feels a bit like Maven because it is declarative as well. Now Ruby
is IMO Python's perlish brother, so I am not very fond of it :-).

Regards Mirko
--
Sent from my mobile
On Jul 6, 2013 12:24 AM, Stephen Connolly stephen.alan.conno...@gmail.com
wrote:

On Friday, 5 July 2013, Mirko Friedenhagen wrote:

Hello,

now after some trial and error with custom packaging and lifecycles I
ask myself whether I should proceed or do something completely
different.

What I want to achieve:
- We have loads of web-applications (WARs with a homegrown
configuration tooling)
- Some are single module projects, some are multi-module.
- All should be deployed to an adhoc tomcat instance after the WAR is
built to see whether configurations are solid and to do some
integrative tests.
- Right now we invoke a shell-script which runs several maven goals
(not phases) directly:
mvn clean verify
mvn internal:create-tomcat (special packaging with logback as logger
etc.)
mvn internal:start-tomcat
mvn internal:deploy-war (this one will _modify_ the war's
configuration on the fly before deployment)
mvn webtest:test
mvn internal:stop-tomcat

Now, shell scripts are not very portable and so I thought about two
solutions:

Solution 1:
Create a custom lifecycle called webtest
- My first idea was to create a custom lifecycle[1] which will invoke
some standard standard goals[2], so the complete vodoo could be done
with:

mvn clean verify verify-webtest

- I tried this with a tiny IT project, where I configured failsafe to
do special stuff during the phase webtest of lifecycle webtest.
- However, now failsafe is invoked twice:
--- snip ---
[INFO] --- maven-failsafe-plugin:2.15:integration-test
(default-integration-test-1) @ foss-jar-maven-plugin-test-foss-war ---
[INFO] --- maven-failsafe-plugin:2.15:integration-test
(webtest-integration-test) @ foss-jar-maven-plugin-test-foss-war ---
--- snap ---

- As the tomcat plugins are invoked as well with the wrong lifecycle
default, I guess this will not work out.

Solution 2:

Would be to create a special packaging webtest and have a module in a
multi-module project, one creating the war and the webtest module
picking up the war as dependency and do the vodoo (on demand).
Then I could imagine having two jobs in Jenkins, one
deploying/installing the WAR and another Jenkins-Job running the shell
equivalent from above by only executing module webtest.

Now, I read a lot about Maven being a tool for *building only*, but
in some way I like Maven and developing plugins is quite easy, so I
thought it might be nonetheless a good way.

What do you think, do I have a hammer and now everything looks like a
nail to me?

I have been down your road several times... It feels like a bit of a
siren's call to me...

The most public thing I did down this road is mojo's ship-maven-plugin...
Which does things a, IMHO, more maven way *if* I were to imagine a maven
way for things that take place beyond the (standard) lifecycle

My current thinking is to use chef/puppet/etc for these tasks... But:

1. I am disappointed by how difficult these toolchains make things
2. Puppet is more maven in philosophy but at work our ops team voted for
chef, so harder to try the tool I feel should be best
3. Lab42's module framework for puppet feels better but puppet labs module
framework is closer to puppet as its by the main devs... I wish they can
find a way to interop better.

Or could I use one of the proposed solutions without abusing Maven to
much? Or is invoking the shell script as we do now a much better
solution?

I actually like shell scripts for this type of thing...

If it ain't broke...

Regards and thank you very much for reading up to here!
Mirko
[1]

https://github.com/mfriedenhagen/foss-jar-maven-plugin/blob/master/src/main/resources/META-INF/plexus/components.xml#L103
[2]

https://github.com/mfriedenhagen/foss-jar-maven-plugin/blob/master/src/main/resources/META-INF/plexus/components.xml#L77
[3]

https://github.com/mfriedenhagen/foss-jar-maven-plugin/blob/master/src/it/test-foss-war/pom.xml#L31

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.orgjavascript:;
For additional commands, e-mail: users-h...@maven.apache.org
javascript:;

--
Sent from my phone

Switching Lifecycles on other things than packaging

Hello there,

is there a way to switch to a different lifecycle depending on e.g. a
path/file etc? Or is the agreed way to just have another packaging?

Regards Mirko
-- 
Sent from my mobile

Lifecycles and configuration of plugins

Hello,

I see that versions of plugins are either manageable in the pom or in the
lifecycle.

Now what about configurations of plugins? May these be hidden as well in an
extension/plugin?

I want to hide this because a lot of application developers look at our
company POM and shudder because of it's shere size :-)

Regards Mirko
-- 
Sent from my mobile

Re: Switching Lifecycles on other things than packaging

Hello Barrie,

I know that :-) Our parent pom defines literally dozens of plugins,
configures them *and* adds a few profiles which change the configuration
and the plugins called on the existence of files, the environment (running
in Jenkins?) and I hoped I could split stuff a bit.

Regards Mirko
-- 
Sent from my mobile
On Jul 6, 2013 8:17 AM, Barrie Treloar baerr...@gmail.com wrote:

 On 6 July 2013 15:39, Mirko Friedenhagen mfriedenha...@gmail.com wrote:
  Hello there,
 
  is there a way to switch to a different lifecycle depending on e.g. a
  path/file etc? Or is the agreed way to just have another packaging?

 The lifecycle for the pom comes from packaging.

 The plugins that pom declares then attach themselves to the lifecycle
 stages.

 You can always use a pom packaging to essentiallly do nothing, and
 have all the work done via plugins.

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org

The Maven way for delivery pipelines

2013-07-05 Thread Mirko Friedenhagen

Hello,

now after some trial and error with custom packaging and lifecycles I
ask myself whether I should proceed or do something completely
different.

What I want to achieve:
- We have loads of web-applications (WARs with a homegrown
configuration tooling)
- Some are single module projects, some are multi-module.
- All should be deployed to an adhoc tomcat instance after the WAR is
built to see whether configurations are solid and to do some
integrative tests.
- Right now we invoke a shell-script which runs several maven goals
(not phases) directly:
mvn clean verify
mvn internal:create-tomcat (special packaging with logback as logger etc.)
mvn internal:start-tomcat
mvn internal:deploy-war (this one will _modify_ the war's
configuration on the fly before deployment)
mvn webtest:test
mvn internal:stop-tomcat

Now, shell scripts are not very portable and so I thought about two solutions:

Solution 1:
Create a custom lifecycle called webtest
- My first idea was to create a custom lifecycle[1] which will invoke
some standard standard goals[2], so the complete vodoo could be done
with:

mvn clean verify verify-webtest

- I tried this with a tiny IT project, where I configured failsafe to
do special stuff during the phase webtest of lifecycle webtest.
- However, now failsafe is invoked twice:
--- snip ---
[INFO] --- maven-failsafe-plugin:2.15:integration-test
(default-integration-test-1) @ foss-jar-maven-plugin-test-foss-war ---
[INFO] --- maven-failsafe-plugin:2.15:integration-test
(webtest-integration-test) @ foss-jar-maven-plugin-test-foss-war ---
--- snap ---

- As the tomcat plugins are invoked as well with the wrong lifecycle
default, I guess this will not work out.

Solution 2:

Would be to create a special packaging webtest and have a module in a
multi-module project, one creating the war and the webtest module
picking up the war as dependency and do the vodoo (on demand).
Then I could imagine having two jobs in Jenkins, one
deploying/installing the WAR and another Jenkins-Job running the shell
equivalent from above by only executing module webtest.

Now, I read a lot about Maven being a tool for *building  only*, but
in some way I like Maven and developing plugins is quite easy, so I
thought it might be nonetheless a good way.

What do you think, do I have a hammer and now everything looks like a
nail to me?
Or could I use one of the proposed solutions without abusing Maven to
much? Or is invoking the shell script as we do now a much better
solution?


Regards and thank you very much for reading up to here!
Mirko
[1] 
https://github.com/mfriedenhagen/foss-jar-maven-plugin/blob/master/src/main/resources/META-INF/plexus/components.xml#L103
[2] 
https://github.com/mfriedenhagen/foss-jar-maven-plugin/blob/master/src/main/resources/META-INF/plexus/components.xml#L77
[3] 
https://github.com/mfriedenhagen/foss-jar-maven-plugin/blob/master/src/it/test-foss-war/pom.xml#L31

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Problems setting up a custom package type II - plugin/mojo versions in components.xml

2013-07-04 Thread Mirko Friedenhagen

Hello Vincent,

thanks for your answer. Just so I get this right: I am looking at my
IT-pom [1] and it has no parent defined. I am running Apache Maven
3.0.5.  In my output I *do not* see the plugin-versions defined in the
super POM from Maven-core (this are the ones defined in
default-bindings.xml[2], right?) but newer ones as they are defined in
the parent-pom of the plugin/extension project.

* Say I have an extension (should be almost the same with a plugin)
with version 2.13 of surefire in the pluginManagement of it's POM.
* I include this extension in a parent pom PP and define 2.14.1 in the
pluginManagement section.
build
pluginManagement
plugins
plugin
artifactIdmaven-surefire-plugin/artifactId
version2.14.1/version
/plugin
/plugins
/pluginManagement
extensions
extension
groupIdg/groupId
artifacta/artifactId
version1.0/version
/extension
/extensions
/build
* In project A inheriting this parent pom I define 2.15 as version.
* Now should I expect the run of 2.15 for A, 2.14.1 for projects just
having PP as parent and all projects not using the PP but the
extension to use 2.13, right?




[1] 
https://github.com/mfriedenhagen/foss-jar-maven-plugin/blob/master/src/it/test-foss-jar/pom.xml
[2] 
https://github.com/apache/maven/blob/master/maven-core/src/main/resources/META-INF/plexus/default-bindings.xml
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/
https://bitbucket.org/mfriedenhagen/


On Thu, Jul 4, 2013 at 8:33 AM, Vincent Latombe
vincent.lato...@gmail.com wrote:
 These are taken from the parent pom (super POM coming from maven core,
 any parent pom that you define)

 Regards,
 Vincent


 2013/7/4 Mirko Friedenhagen mfriedenha...@gmail.com:
 Hello everyone,

 now I am getting greedy :-). I see that you may specify versions for
 the goals being executed during phases in components.xml for custom
 package types.

 Is there a way to convince the versions-maven-plugin etc. to update
 these versions as well?
 Or. where are the versions for the plugins in components taken from?

 Regards Mirko

 -
 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


-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Problems setting up a custom package type

Hello,

I am playing with a custom package type[0], mainly to enforce
execution of check goals.
I read in the mvnref[1] and looked at some samples [2,3].

Now every time I run my integration test[4], the build fails because
the packaging type is not found.

--- snip ---
[DEBUG] Populating class realm
extensionnet.oneandone.maven.plugins:foss-jar-maven-plugin:1.0-SNAPSHOT
[DEBUG]   Included:
net.oneandone.maven.plugins:foss-jar-maven-plugin:jar:1.0-SNAPSHOT
[DEBUG]   Included: org.sonatype.sisu:sisu-inject-bean:jar:2.3.0
[DEBUG]   Included: org.sonatype.sisu:sisu-guice:jar:no_aop:3.1.0
[DEBUG]   Included: org.sonatype.aether:aether-util:jar:1.13.1
[DEBUG]   Included: org.codehaus.plexus:plexus-interpolation:jar:1.14
[DEBUG]   Included: org.codehaus.plexus:plexus-utils:jar:3.0.10
[DEBUG]   Included: org.codehaus.plexus:plexus-component-annotations:jar:1.5.5
[DEBUG]   Included: org.sonatype.plexus:plexus-sec-dispatcher:jar:1.3
[DEBUG]   Included: org.sonatype.plexus:plexus-cipher:jar:1.4
[DEBUG]   Included:
org.apache.maven.plugin-tools:maven-plugin-annotations:jar:3.2
[DEBUG]   Included: com.google.guava:guava:jar:14.0.1
[DEBUG] Extension realms for project
net.oneandone.maven.plugins:foss-jar-maven-plugin-test-foss-jar:foss-jar:1.0-SNAPSHOT:
[ClassRealm[extensionnet.oneandone.maven.plugins:foss-jar-maven-plugin:1.0-SNAPSHOT,
parent: sun.misc.Launcher$AppClassLoader@2ed4a1d3]]
[DEBUG] Created new class realm
projectnet.oneandone.maven.plugins:foss-jar-maven-plugin-test-foss-jar:1.0-SNAPSHOT
[DEBUG] Populating class realm
projectnet.oneandone.maven.plugins:foss-jar-maven-plugin-test-foss-jar:1.0-SNAPSHOT
[DEBUG] Looking up lifecyle mappings for packaging foss-jar from
ClassRealm[projectnet.oneandone.maven.plugins:foss-jar-maven-plugin-test-foss-jar:1.0-SNAPSHOT,
parent: ClassRealm[maven.api, parent: null]]
[ERROR] The build could not read 1 project - [Help 1]
org.apache.maven.project.ProjectBuildingException: Some problems were
encountered while processing the POMs:
[ERROR] Unknown packaging: foss-jar @ line 7, column 16

at 
org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:363)
at org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:636)
at 
org.apache.maven.DefaultMaven.getProjectsForMavenReactor(DefaultMaven.java:585)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:234)
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)
[ERROR]
[ERROR]   The project
net.oneandone.maven.plugins:foss-jar-maven-plugin-test-foss-jar:1.0-SNAPSHOT
(/Users/mirko/workspace/foss/foss-jar/target/it/test-foss-jar/pom.xml)
has 1 error
[ERROR] Unknown packaging: foss-jar @ line 7, column 16
[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/ProjectBuildingException
--- snap ---

I do not understand what I am doing wrong here. Any hints welcome :-).

Regards Mirko
[0] 
https://github.com/mfriedenhagen/foss-jar-maven-plugin/blob/master/src/main/resources/META-INF/plexus/components.xml
[1] 
http://books.sonatype.com/mvnref-book/reference/writing-plugins-sect-plugins-lifecycle.html#ex-override-lifecycle
[2] 
https://github.com/jayway/maven-android-plugin/blob/master/src/main/resources/META-INF/plexus/components.xml
[3] 
https://code.google.com/p/israfil-mojo/source/browse/trunk/maven-flex2-plugin/src/main/resources/META-INF/plexus/components.xml
[4] 
https://github.com/mfriedenhagen/foss-jar-maven-plugin/blob/master/src/it/test-foss-jar/pom.xml
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/
https://bitbucket.org/mfriedenhagen/

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Problems setting up a custom package type

Hello Robert,

thanks for the quick answer, however I still get the same error :-(.
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/
https://bitbucket.org/mfriedenhagen/


On Wed, Jul 3, 2013 at 10:50 PM, Robert Scholte rfscho...@apache.org wrote:
 Hi Mirko,

 you're missing an org.apache.maven.artifact.handler.ArtifactHandler, which
 you can find in [2]

 Robert

 Op Wed, 03 Jul 2013 22:46:04 +0200 schreef Mirko Friedenhagen
 mfriedenha...@gmail.com:

 Hello,

 I am playing with a custom package type[0], mainly to enforce
 execution of check goals.
 I read in the mvnref[1] and looked at some samples [2,3].

 Now every time I run my integration test[4], the build fails because
 the packaging type is not found.

 --- snip ---
 [DEBUG] Populating class realm
 extensionnet.oneandone.maven.plugins:foss-jar-maven-plugin:1.0-SNAPSHOT
 [DEBUG]   Included:
 net.oneandone.maven.plugins:foss-jar-maven-plugin:jar:1.0-SNAPSHOT
 [DEBUG]   Included: org.sonatype.sisu:sisu-inject-bean:jar:2.3.0
 [DEBUG]   Included: org.sonatype.sisu:sisu-guice:jar:no_aop:3.1.0
 [DEBUG]   Included: org.sonatype.aether:aether-util:jar:1.13.1
 [DEBUG]   Included: org.codehaus.plexus:plexus-interpolation:jar:1.14
 [DEBUG]   Included: org.codehaus.plexus:plexus-utils:jar:3.0.10
 [DEBUG]   Included:
 org.codehaus.plexus:plexus-component-annotations:jar:1.5.5
 [DEBUG]   Included: org.sonatype.plexus:plexus-sec-dispatcher:jar:1.3
 [DEBUG]   Included: org.sonatype.plexus:plexus-cipher:jar:1.4
 [DEBUG]   Included:
 org.apache.maven.plugin-tools:maven-plugin-annotations:jar:3.2
 [DEBUG]   Included: com.google.guava:guava:jar:14.0.1
 [DEBUG] Extension realms for project

 net.oneandone.maven.plugins:foss-jar-maven-plugin-test-foss-jar:foss-jar:1.0-SNAPSHOT:

 [ClassRealm[extensionnet.oneandone.maven.plugins:foss-jar-maven-plugin:1.0-SNAPSHOT,
 parent: sun.misc.Launcher$AppClassLoader@2ed4a1d3]]
 [DEBUG] Created new class realm

 projectnet.oneandone.maven.plugins:foss-jar-maven-plugin-test-foss-jar:1.0-SNAPSHOT
 [DEBUG] Populating class realm

 projectnet.oneandone.maven.plugins:foss-jar-maven-plugin-test-foss-jar:1.0-SNAPSHOT
 [DEBUG] Looking up lifecyle mappings for packaging foss-jar from

 ClassRealm[projectnet.oneandone.maven.plugins:foss-jar-maven-plugin-test-foss-jar:1.0-SNAPSHOT,
 parent: ClassRealm[maven.api, parent: null]]
 [ERROR] The build could not read 1 project - [Help 1]
 org.apache.maven.project.ProjectBuildingException: Some problems were
 encountered while processing the POMs:
 [ERROR] Unknown packaging: foss-jar @ line 7, column 16

 at
 org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:363)
 at
 org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:636)
 at
 org.apache.maven.DefaultMaven.getProjectsForMavenReactor(DefaultMaven.java:585)
 at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:234)
 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)
 [ERROR]
 [ERROR]   The project

 net.oneandone.maven.plugins:foss-jar-maven-plugin-test-foss-jar:1.0-SNAPSHOT
 (/Users/mirko/workspace/foss/foss-jar/target/it/test-foss-jar/pom.xml)
 has 1 error
 [ERROR] Unknown packaging: foss-jar @ line 7, column 16
 [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/ProjectBuildingException
 --- snap ---

 I do not understand what I am doing wrong here. Any hints welcome :-).

 Regards Mirko
 [0]
 https://github.com/mfriedenhagen/foss-jar-maven-plugin/blob/master/src/main/resources/META-INF/plexus/components.xml
 [1]
 http://books.sonatype.com/mvnref-book/reference/writing-plugins-sect-plugins-lifecycle.html#ex-override-lifecycle
 [2]
 https://github.com/jayway/maven-android-plugin/blob/master/src/main/resources/META-INF/plexus/components.xml
 [3]
 https://code.google.com/p/israfil-mojo/source/browse/trunk/maven-flex2-plugin/src/main/resources/META-INF/plexus/components.xml
 [4

Re: Problems setting up a custom package type

Hello Stuart,

thanks! That did the trick. I do not know why Netbeans did not mark
the XML as invalid :-(. Now the IT still fails because rules are
missing for enforcer, but this is a trivial problem to tackle.

Thx again
Mirko
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/
https://bitbucket.org/mfriedenhagen/


On Wed, Jul 3, 2013 at 11:37 PM, Stuart McCulloch mccu...@gmail.com wrote:
 On 3 Jul 2013, at 22:05, Mirko Friedenhagen wrote:

 Hello Robert,

 thanks for the quick answer, however I still get the same error :-(.

 It looks like you have mismatched tags on line 27 of your components.xml:

validateorg.apache.maven.plugins:maven-enforcer-plugin:enforce/package

 Regards Mirko
 --
 http://illegalstateexception.blogspot.com/
 https://github.com/mfriedenhagen/
 https://bitbucket.org/mfriedenhagen/


 On Wed, Jul 3, 2013 at 10:50 PM, Robert Scholte rfscho...@apache.org wrote:
 Hi Mirko,

 you're missing an org.apache.maven.artifact.handler.ArtifactHandler, which
 you can find in [2]

 Robert

 Op Wed, 03 Jul 2013 22:46:04 +0200 schreef Mirko Friedenhagen
 mfriedenha...@gmail.com:

 Hello,

 I am playing with a custom package type[0], mainly to enforce
 execution of check goals.
 I read in the mvnref[1] and looked at some samples [2,3].

 Now every time I run my integration test[4], the build fails because
 the packaging type is not found.

 --- snip ---
 [DEBUG] Populating class realm
 extensionnet.oneandone.maven.plugins:foss-jar-maven-plugin:1.0-SNAPSHOT
 [DEBUG]   Included:
 net.oneandone.maven.plugins:foss-jar-maven-plugin:jar:1.0-SNAPSHOT
 [DEBUG]   Included: org.sonatype.sisu:sisu-inject-bean:jar:2.3.0
 [DEBUG]   Included: org.sonatype.sisu:sisu-guice:jar:no_aop:3.1.0
 [DEBUG]   Included: org.sonatype.aether:aether-util:jar:1.13.1
 [DEBUG]   Included: org.codehaus.plexus:plexus-interpolation:jar:1.14
 [DEBUG]   Included: org.codehaus.plexus:plexus-utils:jar:3.0.10
 [DEBUG]   Included:
 org.codehaus.plexus:plexus-component-annotations:jar:1.5.5
 [DEBUG]   Included: org.sonatype.plexus:plexus-sec-dispatcher:jar:1.3
 [DEBUG]   Included: org.sonatype.plexus:plexus-cipher:jar:1.4
 [DEBUG]   Included:
 org.apache.maven.plugin-tools:maven-plugin-annotations:jar:3.2
 [DEBUG]   Included: com.google.guava:guava:jar:14.0.1
 [DEBUG] Extension realms for project

 net.oneandone.maven.plugins:foss-jar-maven-plugin-test-foss-jar:foss-jar:1.0-SNAPSHOT:

 [ClassRealm[extensionnet.oneandone.maven.plugins:foss-jar-maven-plugin:1.0-SNAPSHOT,
 parent: sun.misc.Launcher$AppClassLoader@2ed4a1d3]]
 [DEBUG] Created new class realm

 projectnet.oneandone.maven.plugins:foss-jar-maven-plugin-test-foss-jar:1.0-SNAPSHOT
 [DEBUG] Populating class realm

 projectnet.oneandone.maven.plugins:foss-jar-maven-plugin-test-foss-jar:1.0-SNAPSHOT
 [DEBUG] Looking up lifecyle mappings for packaging foss-jar from

 ClassRealm[projectnet.oneandone.maven.plugins:foss-jar-maven-plugin-test-foss-jar:1.0-SNAPSHOT,
 parent: ClassRealm[maven.api, parent: null]]
 [ERROR] The build could not read 1 project - [Help 1]
 org.apache.maven.project.ProjectBuildingException: Some problems were
 encountered while processing the POMs:
 [ERROR] Unknown packaging: foss-jar @ line 7, column 16

at
 org.apache.maven.project.DefaultProjectBuilder.build(DefaultProjectBuilder.java:363)
at
 org.apache.maven.DefaultMaven.collectProjects(DefaultMaven.java:636)
at
 org.apache.maven.DefaultMaven.getProjectsForMavenReactor(DefaultMaven.java:585)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:234)
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)
 [ERROR]
 [ERROR]   The project

 net.oneandone.maven.plugins:foss-jar-maven-plugin-test-foss-jar:1.0-SNAPSHOT
 (/Users/mirko/workspace/foss/foss-jar/target/it/test-foss-jar/pom.xml)
 has 1 error
 [ERROR] Unknown packaging: foss-jar @ line 7, column 16
 [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

Problems setting up a custom package type II - plugin/mojo versions in components.xml

Hello everyone,

now I am getting greedy :-). I see that you may specify versions for
the goals being executed during phases in components.xml for custom
package types.

Is there a way to convince the versions-maven-plugin etc. to update
these versions as well?
Or. where are the versions for the plugins in components taken from?

Regards Mirko

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Versions plugin for plugin updates only

2013-07-01 Thread Mirko Friedenhagen

Hello org,

you may perhaps define a configuration section in which you define an
include with groupId/artifactId for your plugins, then only those are
updated.

Regards Mirko
-- 
Sent from my mobile
On Jul 1, 2013 12:01 AM, org.apache.maven.u...@io7m.com wrote:

 Hello.

 Is it possible to get the Versions plugin to only update the version
 numbers of plugins?

 When running versions:use-latest-releases, the plugin immediately
 folds all my dependencies version ranges into the latest version, which
 is a huge pain as I then have to go back and reset them. I'd rather
 have it manage my plugin versions and not touch anything else.

 I could specify various excludes according to the plugin's usage page,
 but this then requires that I know about the contents of each POM and
 therefore can't be automated reliably.

 -
 To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
 For additional commands, e-mail: users-h...@maven.apache.org

[ANN] extra-enforcer-rules 1.0-alpha-5 Released

2013-06-24 Thread Mirko Friedenhagen

Hi,

The Mojo team is pleased to announce the release of the 1.0-alpha-5
version of the extra-enforcer-rules.

Extra Enforcer Rules. These are extra rules for Apache Maven's Enforcer Plugin.

http://mojo.codehaus.org/extra-enforcer-rules/

To get this update, simply specify the version in your project's
plugin configuration:

 build
pluginManagement
  plugins
plugin
  groupIdorg.apache.maven.plugins/groupId
  artifactIdmaven-enforcer-plugin/artifactId
  version1.0/version
  dependencies
dependency
  groupIdorg.codehaus.mojo/groupId
  artifactIdextra-enforcer-rules/artifactId
  version1.0-alpha-5/version
/dependency
  /dependencies
/plugin
  /plugins
/pluginManagement
  /build

Release Notes

We solved 3 issues:
http://jira.codehaus.org/issues/?jql=fixVersion%20%3D%20%22extra-enforcer-rules-1.0-alpha-5%22%20AND%20project%20%3D%20MOJO

** Bug
* [MOJO-1929] - NullPointerException in requirePropertyDiverges if
configuration is put in execution
* [MOJO-1931] - RequirePropertyDiverges fails if configuration
elements are in wrong order



** Improvement
* [MOJO-1930] - RFE: RequirePropertyDiverges: Extend the rule to
include a custom message

Enjoy,

The Mojo team.

Mirko Friedenhagen

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Problem with multi-module site

2013-06-19 Thread Mirko Friedenhagen

If I remember correctly, one problem is, when the name/directory of the
module does not equal the artifactId of the module.

Regards Mirko
-- 
Sent from my mobile
On Jun 20, 2013 1:04 AM, Russell Gold r...@gold-family.us wrote:

 I am using the site-maven-plugin (version 3.3) and cannot seem to get it
 to work. Using the exact same site.xml and additional files (faq, apt and
 xhtml types) that worked fine in a single project site, I am not getting
 breadcrumbs or custom menu items. I do get the submodules with their own
 sites, each of which is inheriting the reports from the parent, but that's
 it.

 My (58K) project is at
 http://russgold.github.io/russgold/maven-video/sample10.zip

 Thanks
 Russ
 -
 Come read my webnovel, Take a Lemon http://www.takealemon.com,
 and listen to the Misfile radio play 
 http://www.gold-family.us/audio/misfile.html!

Re: Multiple invocation of report goal with different configurations?

2013-05-21 Thread Mirko Friedenhagen

Hello,

I now opened a pull request for jacoco[1] and somehow there seems to
be a change between maven-site-plugin-3.2 and maven-site-plugin-3.3,
the latter one allows to define multiple reportSets like in the
example below resp. on github[2]

[1] https://github.com/jacoco/jacoco/pull/105
[2] 
https://github.com/mfriedenhagen/jacoco/blob/5718ea545a9ad17ae057ebc224062d1e0cf7d0a1/jacoco-maven-plugin.test/it/it-site-failsafe/pom.xml#L103
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/
https://bitbucket.org/mfriedenhagen/


On Sun, May 19, 2013 at 8:37 PM, Mirko Friedenhagen
mfriedenha...@gmail.com wrote:
 Hello,

 configuring-reports[1] states:
 
 If you want to choose only some reports from a plugin, or if you want
 to run a report *multiple times with a different configuration*, you
 need to configure report sets:
 
 I now tried this with the jacoco-maven-plugin to differentiate between
 unit and integration tests like this:

 reporting
 plugins
 plugin
 groupIdorg.jacoco/groupId
 artifactIdjacoco-maven-plugin/artifactId
 version 0.6.2.201302030002/version
 reportSets
 reportSet
 idunit-tests/id
 reports
 reportreport/report
 /reports
 configuration

 dataFile${project.build.directory}/jacoco.exec/dataFile
 /configuration
 /reportSet
 reportSet
 idintegration-tests/id
 reports
 reportreport/report
 /reports
 configuration

 dataFile${project.build.directory}/jacoco-it.exec/dataFile
 /configuration
 /reportSet
 /reportSets
 /plugin
 /plugins
 /reporting

 However, this does not work, as the configuration of the second
 reportSet will always override the first one. Looking into the
 plugin's code, this seems quite obvious:
 getOutputName[2] will always return jacoco/index and
 setReportOutputDirectory[3] will always just append jacoco to given
 parameter reportOutputDirectory.
 And in my sample project, the report goal will only be executed once.

 So my question: is there an example, where the same report mojo
 configured twice will be executed twice and return two different
 reports?


 Regards Mirko
 [1] 
 http://maven.apache.org/plugins/maven-site-plugin/examples/configuring-reports.html
 [2] 
 https://github.com/jacoco/jacoco/blob/master/jacoco-maven-plugin/src/org/jacoco/maven/ReportMojo.java#L131
 [3] 
 https://github.com/jacoco/jacoco/blob/master/jacoco-maven-plugin/src/org/jacoco/maven/ReportMojo.java#L182

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Multiple invocation of report goal with different configurations?

2013-05-19 Thread Mirko Friedenhagen

Hello,

configuring-reports[1] states:

If you want to choose only some reports from a plugin, or if you want
to run a report *multiple times with a different configuration*, you
need to configure report sets:

I now tried this with the jacoco-maven-plugin to differentiate between
unit and integration tests like this:

reporting
plugins
plugin
groupIdorg.jacoco/groupId
artifactIdjacoco-maven-plugin/artifactId
version 0.6.2.201302030002/version
reportSets
reportSet
idunit-tests/id
reports
reportreport/report
/reports
configuration

dataFile${project.build.directory}/jacoco.exec/dataFile
/configuration
/reportSet
reportSet
idintegration-tests/id
reports
reportreport/report
/reports
configuration

dataFile${project.build.directory}/jacoco-it.exec/dataFile
/configuration
/reportSet
/reportSets
/plugin
/plugins
/reporting

However, this does not work, as the configuration of the second
reportSet will always override the first one. Looking into the
plugin's code, this seems quite obvious:
getOutputName[2] will always return jacoco/index and
setReportOutputDirectory[3] will always just append jacoco to given
parameter reportOutputDirectory.
And in my sample project, the report goal will only be executed once.

So my question: is there an example, where the same report mojo
configured twice will be executed twice and return two different
reports?


Regards Mirko
[1] 
http://maven.apache.org/plugins/maven-site-plugin/examples/configuring-reports.html
[2] 
https://github.com/jacoco/jacoco/blob/master/jacoco-maven-plugin/src/org/jacoco/maven/ReportMojo.java#L131
[3] 
https://github.com/jacoco/jacoco/blob/master/jacoco-maven-plugin/src/org/jacoco/maven/ReportMojo.java#L182

-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Automatically remove version overrides from child POMs

2013-05-04 Thread Mirko Friedenhagen

Hello Robert,

you could use the enforcer-plugin to enforce specific versions, then at
least you have an easy way to identify those projects. We exclude all
versions of spring and then include the latest version again, e.g.

Regards Mirko
-- 
Sent from my mobile
On May 4, 2013 12:54 AM, Enyedi, Robert reny...@ebay.com wrote:

 Hi,

 We're using a parent POM which manages the versions of tens of
 dependencies.  I occasionally encounter modules within my group that
 override some of those managed versions.

 Assuming the overrides are not legit, is there an automatic way to remove
 them from the child POMs? I was hoping that the
 versions:update-child-modules mojo would help, but it doesn't seem to do
 what I need.

 Thanks,
 Robert

Re: Lightweight maven-releases, or an alternative to the maven-release-plugin

2013-05-01 Thread Mirko Friedenhagen

Hello there,

I. find prepare and perform quite heavyweight my self. After prepare did
build everything successfully, it throws away everything, just tags the
source and starts over again during perform.

prepare already checks with scm means, that there are no modifications and
in my experience tagging is the most harmless operation in the whole
process (well, would I still use CVS that could be different).

So running prepare with prepareGoals set to -DperformRelease=true clean
deploy does what *I* want.

- checks I have everything in SCM
- does modify POMs for release.
- deploys to staging
- only on success of this tags the sources
- go back to SNAPSHOT.

git and svn (when not doing the strange remoteTagging) are capable of
tagging always.
Worst thing that might happen: bad stuff in staging for a short time.

Regards Mirko
--
Sent from my mobile
On May 1, 2013 9:15 PM, Robert Scholte rfscho...@apache.org wrote:

Graham, well said.

Although the pom.xml is the easiest way to discover the version, it is not
the best location, since it would require a commit.
The solution must be found in a generated file which will be added to the
artifact during packaging. Here you could add a timestamp or revision.

Robert

Op Wed, 01 May 2013 12:44:19 +0200 schreef Graham Leggett
minf...@sharp.fm:

On 30 Apr 2013, at 11:21 PM, Roger Brechbühl rotscher...@gmail.com
wrote:

Maybe somebody is interested in how a release could be built in a more
lightweight and safe way than with the maven-release-plugin. Especially
recommended for nightly releases.

It's not yet released, but basically fully working:

*mvn clean install -Dversion.override=1.2.3-S-5*

https://github.com/rotscher/**emerging/tree/version.**
override-with_maven_install-2.**4https://github.com/rotscher/emerging/tree/version.override-with_maven_install-2.4

Maven has a very clear definition of a release, being an artefact that
can traced back to the precise code via a tag, and a build that can be
repeated. This is as opposed to a snapshot, which has no well defined
origin.

You might approach this two ways, you might create nightly snapshots
and have them deployed somewhere suitable, using mvn deploy.

Alternatively if you want to create proper nightly releases (in the
maven sense), you could feed a custom version number into the release
plugin to represent your release, but this starts to smell like that's
what a snapshot is for.

Regards,
Graham
--

--**--**-
To unsubscribe, e-mail:
users-unsubscribe@maven.**apache.orgusers-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org

Re: Maven Problems

2013-04-20 Thread Mirko Friedenhagen

Hello Benjamin,

settings are from /home/gen3builder, maven looks for security in /root.

Do you now run bamboo as user root and did you run it as gen3builder before?

Regards Mirko
-- 
Sent from my mobile
On Apr 20, 2013 10:17 AM, benjamin_joy...@ao.uscourts.gov wrote:

 I have been having an issue with a deploy through maven.  I migrated our
 copy of bamboo  to a new server recently and for one of our plans we use
 Maven and its cargo plugin to connect to JBoss and pull and install a .war
 file.  however, on the new install this command always fails with a
 invokerlocater socket error.  I will lpost the stack trace below.  both
 systems are running RHEL and while they are running different versions I
 have attempted to move it to a server running the same version  and it
 still fails.  SO that rules out that as an issue.  I have verified that
 ssh, scp, ftp, Get, and ping all work between the servers, and there are
 no active firewalls.  I have also tried modifying the hostname and that
 change the hostname on my server in the error, but did not affect the
 problem itself.

 This is the Command run that fails. If I run the same command from the old
 server it succeeds.  Everything down to where it says ERROR] FATAL ERROR
 is identical to the successful run accept that instead of the ERROR]
 FATAL ERROR I get a success.  Any help or ideas will be much apreciated
 as I am running out of things to try.


 [root@fppsappdev pacts-gen3-view-war]#
 /opt/devl/apache-maven-2.2.1/bin/mvn clean install
 org.codehaus.cargo:cargo-maven2-plugin:redeploy -s
 /home/gen3builder/.m2/settings_fppsint.xml -e
 + Error stacktraces are turned on.
 [WARNING] Not decrypting password for server 'fppsint.gtwy.dcn' due to
 exception in security handler.
 Ensure that you have configured your master password file (and relocation
 if appropriate)
 See the installation instructions for details.
 Cause: /root/.m2/settings-security.xml (No such file or directory)
 [WARNING] Not decrypting password for server 'ao.opps.releases' due to
 exception in security handler.
 Ensure that you have configured your master password file (and relocation
 if appropriate)
 See the installation instructions for details.
 Cause: /root/.m2/settings-security.xml (No such file or directory)
 [WARNING] Not decrypting password for server 'ao.opps.snapshots' due to
 exception in security handler.
 Ensure that you have configured your master password file (and relocation
 if appropriate)
 See the installation instructions for details.
 Cause: /root/.m2/settings-security.xml (No such file or directory)
 [INFO] Scanning for projects...
 [INFO]
 
 [INFO] Building pacts-gen3-view-war
 [INFO]task-segment: [clean, install,
 org.codehaus.cargo:cargo-maven2-plugin:redeploy]
 [INFO]
 
 [INFO] [clean:clean {execution: default-clean}]
 [INFO] Deleting directory
 /home/gen3builder/client-data-transfer/pacts-gen3-view-war/target
 [INFO] [resources:resources {execution: default-resources}]
 [WARNING] Using platform encoding (UTF-8 actually) to copy filtered
 resources, i.e. build is platform dependent!
 [INFO] Copying 3 resources
 [INFO] snapshot gov.usc.codex:codex-core:1.4.12-SNAPSHOT: checking for
 updates from public-snapshots
 [INFO] snapshot gov.usc.codex:codex:1.4.12-SNAPSHOT: checking for updates
 from public-snapshots
 [INFO] snapshot gov.usc.ao:pacts-gen3-controller-jar:0.1.10-SNAPSHOT:
 checking for updates from public-snapshots
 [INFO] snapshot gov.usc.codex:codex-converter:1.4.12-SNAPSHOT: checking
 for updates from public-snapshots
 [INFO] snapshot gov.usc.codex:codex-uspps-v1:1.4.12-SNAPSHOT: checking for
 updates from public-snapshots
 [INFO] snapshot gov.usc.commons:esb-http-util:2.13.0-SNAPSHOT: checking
 for updates from public-snapshots
 [INFO] snapshot gov.usc.commons:usc-commons-esb:2.13.0-SNAPSHOT: checking
 for updates from public-snapshots
 [INFO] [compiler:compile {execution: default-compile}]
 [INFO] No sources to compile
 [INFO] [resources:testResources {execution: default-testResources}]
 [WARNING] Using platform encoding (UTF-8 actually) to copy filtered
 resources, i.e. build is platform dependent!
 [INFO] skip non existing resourceDirectory

 /home/gen3builder/client-data-transfer/pacts-gen3-view-war/src/test/resources
 [INFO] [compiler:testCompile {execution: default-testCompile}]
 [INFO] No sources to compile
 [INFO] [surefire:test {execution: default-test}]
 [INFO] No tests to run.
 [INFO] [war:war {execution: default-war}]
 [INFO] Packaging webapp
 [INFO] Assembling webapp [pacts-gen3-view-war] in

 [/home/gen3builder/client-data-transfer/pacts-gen3-view-war/target/pacts-gen3]
 [INFO] Processing war project
 [INFO] Copying webapp webResources

 [/home/gen3builder/client-data-transfer/pacts-gen3-view-war/src/main/webapp]
 to

Re: String index out of range: -12 in ReleaseUtils.loadResolvedDependencies() when using Parent-Module-Layout

Hello,

I probably found the cause: in our Jenkins instance we had set
 MAVEN_OPTS=-Ddependency.locations.enabled=false. This caused no
problems during normal SNAPSHOT runs but we could not get the
release-plugin working. Nothing was seen even with -X, release.properties
is not even started. Removing the property above from MAVEN_OPTS solved the
proplem. I am not sure whether and where to create an issue for this (maybe
it just works as intended :-)).

Regards
Mirko

Regards Mirko
-- 
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/
https://bitbucket.org/mfriedenhagen/


On Fri, Jan 18, 2013 at 5:13 PM, Wayne Fay wayne...@gmail.com wrote:

 Looks like a section of code that could benefit from some debug-level
 logging. Then OP could just turn on -X and send us more useful output.

 Wayne

 On Fri, Jan 18, 2013 at 8:26 AM, Robert Scholte rfscho...@apache.org
 wrote:
 
 http://maven.apache.org/maven-release/maven-release-manager/xref/org/apache/maven/shared/release/config/ReleaseUtils.html#256
 
  I'm interested in your release.properties as well.
  It looks like there's a property starting with 'dependency.' which
 doesn't
  end with '.development' or '.release'
  This should not be possible.
 
  thanks,
  Robert
 
  Op Fri, 18 Jan 2013 09:11:39 +0100 schreef thorsten.h...@vkb.de:
 
 
  Hi,
 
  maven-release-plugin:2.4:prepare failed: String index out of range: -12
 
  at org.apache.maven.lifecycle.internal.MojoExecutor.execute
  (MojoExecutor.java:225)
 
 
  *snip*
 
  Have you tried running mvn -e -X ...?
  Perhaps there's something missing in your pom.xml, such as an invalid
  property that is referenced somewhere, an empty or missing plugin
  configuration section etc.pp.
 
 
  HTH
 
  Thorsten
 
 
  -
  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

Re: String index out of range: -12 in ReleaseUtils.loadResolvedDependencies() when using Parent-Module-Layout

Hello Robert,

I created http://jira.codehaus.org/browse/MRELEASE-834
(release:prepare fails when a system property starting with dependency
is given).
Regards Mirko
--
http://illegalstateexception.blogspot.com/
https://github.com/mfriedenhagen/
https://bitbucket.org/mfriedenhagen/


On Fri, Apr 12, 2013 at 6:39 PM, Robert Scholte rfscho...@apache.org wrote:
 Hi Mirko,

 Hmmm, just noticed I answered the wrong message of this thread :S
 But this is interesting.

 I can't find a JIRA issue for it, so feel free to create one.

 Robert

 Op Fri, 12 Apr 2013 17:44:29 +0200 schreef Mirko Friedenhagen
 mfriedenha...@gmail.com:


 Hello,

 I probably found the cause: in our Jenkins instance we had set
  MAVEN_OPTS=-Ddependency.locations.enabled=false. This caused no
 problems during normal SNAPSHOT runs but we could not get the
 release-plugin working. Nothing was seen even with -X,
 release.properties
 is not even started. Removing the property above from MAVEN_OPTS solved
 the
 proplem. I am not sure whether and where to create an issue for this
 (maybe
 it just works as intended :-)).

 Regards
 Mirko

 Regards Mirko


 -
 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

Re: Maven-release-plugin error

Hello,

my first guess would be the spaces in your workspace path, you could try to
check out to C:/tmp/myprj and retry. Second guess: on windows path names
must not be longer than 255 characters (at least Mercurial had problems
with this), again, a checkout to C:/tmp/myprj could help.

Regards Mirko
-- 
Sent from my mobile
On Apr 12, 2013 8:59 PM, Zanzerkia, Robert robert.zanzer...@fmr.com
wrote:


 Hi,
  I am getting below error (SCM is Jazz RTC).
  Is there some convention about workspace name and snapshot name has to
 match?
  Is there a switch to override it?
  I also noticed that the original workspace I had specified get's changed
 as follows...
 RTCURL:PORT are replaced with real ones in my POM.

 scm
 connectionscm:jazz:https://RTCURL:PROT
 /jazz:uCMDB-PatternDev-0.0.6/connection

 developerConnectionscm:jazz:https://RTCURL:PROT:uCMDB-PatternDev-0.0.6
 /developerConnection
 urlhttps://RTCURL:PROT/jazz:uCMDB-PatternDev-0.0.6/url
 /scm
 build



 Thanks,
 Robert

 [INFO] Tagging release with the label uCMDB-PatternDev-0.0.6...
 [INFO] Executing: cmd.exe /X /C scm status --username a408072 --password
 *
 --wide
 [INFO] Working directory: C:\Documents and
 Settings\a408072.DMN1\workspace301\EI
  AS-ITAM uCMDB Pattern DEV
 [INFO] Executing: cmd.exe /X /C scm create snapshot --repository-uri
 https://RTCURLHERE/jazz --username x --password * --name
 uCMDB-PatternDev-0
 .0.6 --description [maven-release-plugin]  copy for tag
 uCMDB-PatternDev-0.0.6
  uCMDB-PatternDev-0.0.6
 [INFO] Working directory: C:\Documents and
 Settings\a408072.DMN1\workspace301\EI
  AS-ITAM uCMDB Pattern DEV
 [ERROR] Error: Selector uCMDB-PatternDev-0.0.6 did not match any
 workspaces
 Problem running 'create snapshot':
 Could not find workspace or stream specified by selector
 uCMDB-PatternDev-0.0.6
 

 [INFO]
 
 [INFO] BUILD FAILURE
 [INFO]
 
 [INFO] Total time: 2:09.255s
 [INFO] Finished at: Fri Apr 12 11:33:22 EDT 2013
 [INFO] Final Memory: 9M/247M
 [INFO]
 
 [ERROR] Failed to execute goal
 org.apache.maven.plugins:maven-release-plugin:2.4
 .1:prepare (default-cli) on project uCMDB-PatternDev: Unable to tag SCM
 [ERROR] Provider message:
 [ERROR] Error code for Jazz SCM tag (SNAPSHOT) command - 9
 [ERROR] Command output:
 [ERROR] Selector uCMDB-PatternDev-0.0.6 did not match any workspaces
 [ERROR] Problem running 'create snapshot':
 [ERROR] Could not find workspace or stream specified by selector
 uCMDB-PatternD
 ev-0.0.6
 [ERROR] - [Help 1]
 [ERROR]
 [ERROR] To see the full stack trace of the errors, re-run Maven with the
 -e swit
 ch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR]
 [ERROR] For more information about the errors and possible solutions,
 please rea
 d the following articles:
 [ERROR] [Help 1]
 http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureExc
 eption

Re: Maven-release-plugin error