Re: What is going on with maven-javadoc-plugin?

2015-03-13 Thread Marcos Zolnowski
Thank you for this enlightening response.
 

 On Friday, March 13, 2015 2:55 AM, Baptiste Mathus bmat...@batmat.net 
wrote:
   

 Just ich scratching and limited time, that's how OSS works.
Generally, if (like here) the code is moreover already committed, *kindly*
asking for a release on the dev ML can do the trick.

HTH

2015-03-13 2:38 GMT+01:00 Marcos Zolnowski 
marcos.zolnow...@yahoo.com.invalid:

 From:
 http://jira.codehaus.org/browse/MJAVADOC-365?focusedCommentId=363324page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-363324It
 has been about 6 months now since the last activity here. I wonder, what
 can be done with respect to getting a 2.11 or 2.10.2 version with this
 change applied?
 Can anyone tell me why no one does the release of this plugin?




-- 
Baptiste Batmat MATHUS - http://batmat.net
Sauvez un arbre,
Mangez un castor !




Re: What is going on with maven-javadoc-plugin?

2015-03-13 Thread Karl Heinz Marbaise

Hi Marcos,

On 3/13/15 2:38 AM, Marcos Zolnowski wrote:

From: 
http://jira.codehaus.org/browse/MJAVADOC-365?focusedCommentId=363324page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-363324


It has been about 6 months now since the last activity here.
 I wonder, what can be done with respect to getting a 2.11 or 2.10.2
  version with this change applied?


Can anyone tell me why no one does the release of this plugin?



Just based on lack of time...cause there are in the meantime a large 
number of releases have been done and all of the members of the Maven 
team are busy...You should be aware that all of the Maven team (I don't 
any exception) are working on Maven in their spare time...no one is 
doing this fulltime...(apart from being payed for it).


Furthermore there is no vote on the issue...

We are usually focused on issues which have more than one vote or be 
more accurate having at least one vote...


and an other thing is that no one seemed to be interested in, no 
feedback in the jira issue (for more than three years), nor asked 
someone before...except you...


May be i'm able to check within the next days ...

Kind regards
Karl Heinz Marbaise

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



Re: What is going on with maven-javadoc-plugin?

2015-03-13 Thread Marcos Zolnowski
Appearances can be deceiving, when I see the link 
http://maven.apache.org/plugins/maven-javadoc-plugin/team-list.html, there 
seems to be an army of developers.
Now I am aware of the reality of Maven, but I do not understand why a fixed bug 
needs votes.
Bug was fixed 09/Oct/14, 6 months holding a bug fix?
A fixed bug is not a new feature, why should we wait 6 months for more people 
to hit this bug, if we could solve it today?
On Friday, March 13, 2015 5:12 PM, Karl Heinz Marbaise khmarba...@gmx.de 
wrote:



Hi Marcos,


On 3/13/15 2:38 AM, Marcos Zolnowski wrote:
 From: 
 http://jira.codehaus.org/browse/MJAVADOC-365?focusedCommentId=363324page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-363324

It has been about 6 months now since the last activity here.
 I wonder, what can be done with respect to getting a 2.11 or 2.10.2
  version with this change applied?

 Can anyone tell me why no one does the release of this plugin?


Just based on lack of time...cause there are in the meantime a large 
number of releases have been done and all of the members of the Maven 
team are busy...You should be aware that all of the Maven team (I don't 
any exception) are working on Maven in their spare time...no one is 
doing this fulltime...(apart from being payed for it).

Furthermore there is no vote on the issue...

We are usually focused on issues which have more than one vote or be 
more accurate having at least one vote...

and an other thing is that no one seemed to be interested in, no 
feedback in the jira issue (for more than three years), nor asked 
someone before...except you...

May be i'm able to check within the next days ...

Kind regards
Karl Heinz Marbaise

-
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: Do people actually use markdown or should I abandon it and migrate to xdocs?

2015-03-13 Thread Barrie Treloar
Hervé thanks for spotting someone had problems that may be
un-addressed, I completely missed following that through.

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



RE: artifactasc/artifactId missing ?

2015-03-13 Thread Martin Gainty
MGi d/l 
http://search.maven.org/#artifactdetails|net.flexmojos.oss|flexmojos-flex-compiler|7.0.1|jar
 pom/src
when I compile 7.0.1 version i get a raft of unresolved artifacts:

... 22 more
Caused by: org.eclipse.aether.resolution.DependencyResolutionException: The foll
owing artifacts could not be resolved: org.apache.flex:compiler:pom:7.0.1, org.a
pache.flex.compiler:mxmlc:jar:7.0.1, org.apache.flex.compiler:digest:jar:7.0.1,
org.apache.flex.compiler:optimizer:jar:7.0.1, org.apache.flex.compiler:asdoc:jar
:7.0.1, org.apache.flex.compiler:swcdepends:jar:7.0.1, org.testng:testng:jar:jdk
15:6.8.8: Failure to find org.apache.flex:compiler:pom:7.0.1 in http://repositor
y.sonatype.org/content/groups/flexgroup/ was cached in the local repository, res
olution will not be reattempted until the update interval of rso has elapsed or
updates are forced
at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDepen
dencies(DefaultRepositorySystem.java:384)
at org.apache.maven.project.DefaultProjectDependenciesResolver.resolve(D
efaultProjectDependenciesResolver.java:192)
... 23 more
Caused by: org.eclipse.aether.resolution.ArtifactResolutionException: The follow
ing artifacts could not be resolved: org.apache.flex:compiler:pom:7.0.1, org.apa
che.flex.compiler:mxmlc:jar:7.0.1, org.apache.flex.compiler:digest:jar:7.0.1, or
g.apache.flex.compiler:optimizer:jar:7.0.1, org.apache.flex.compiler:asdoc:jar:7
.0.1, org.apache.flex.compiler:swcdepends:jar:7.0.1, org.testng:testng:jar:jdk15
:6.8.8: Failure to find org.apache.flex:compiler:pom:7.0.1 in http://repository.
sonatype.org/content/groups/flexgroup/ was cached in the local repository, resol
ution will not be reattempted until the update interval of rso has elapsed or up
dates are forced
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(Defa
ultArtifactResolver.java:459)
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolveArtif
acts(DefaultArtifactResolver.java:262)
at org.eclipse.aether.internal.impl.DefaultRepositorySystem.resolveDepen
dencies(DefaultRepositorySystem.java:367)
... 24 more
Caused by: org.eclipse.aether.transfer.ArtifactNotFoundException: Failure to fin
d org.apache.flex:compiler:pom:7.0.1 in http://repository.sonatype.org/content/g
roups/flexgroup/ was cached in the local repository, resolution will not be reat
tempted until the update interval of rso has elapsed or updates are forced
at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.newExcepti
on(DefaultUpdateCheckManager.java:232)
at org.eclipse.aether.internal.impl.DefaultUpdateCheckManager.checkArtif
act(DefaultUpdateCheckManager.java:177)
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.gatherDownlo
ads(DefaultArtifactResolver.java:599)
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.performDownl
oads(DefaultArtifactResolver.java:518)
at org.eclipse.aether.internal.impl.DefaultArtifactResolver.resolve(Defa
ultArtifactResolver.java:436)
... 26 more

Marvin did NOT push his 7.0.1 flex dependencies 
artifactdcompiler/artifactId,artifactdmxmlc/artifactId,artifactdasdoc/artifactId..23
 more.. up to the repository.sonatype.org nexus repository

until Marvin pushes his dependencies to repository.sonatype.org nexus repo
i have no choice but to revert to what I have for now

thanks curtis,
Martin


 From: ctrue...@wisc.edu
 Date: Fri, 13 Mar 2015 10:10:26 -0500
 Subject: Re: artifactasc/artifactId missing ?
 To: users@maven.apache.org
 
 Hi Martin,
 
 org.sonatype.flexmojos:flexmojos-flex-compiler:3.8-SNAPSHOT is ancient.
 There are several new major versions, including a groupId change to
 net.flexmojos.oss:
 
 https://repository.sonatype.org/#nexus-search;quick~flexmojos-flex-compiler
 
 The latest on Maven Central is:
 net.flexmojos.oss:flexmojos-flex-compiler:7.0.1
 
 http://search.maven.org/#artifactdetails%7Cnet.flexmojos.oss%7Cflexmojos-flex-compiler%7C7.0.1%7Cjar
 
 Regards,
 Curtis
 
 On Thu, Mar 12, 2015 at 6:57 PM, Martin Gainty mgai...@hotmail.com wrote:
 
 
 
 
   Subject: Re: artifactasc/artifactId missing ?
   From: manf...@mosabuam.com
   To: users@maven.apache.org
   Date: Thu, 12 Mar 2015 23:38:41 +0100
  
   I can not find it on https://oss.sonatype.org/ or
  https://repository.sonatype.org/ even when logged in.
  
   Manfred
 
  MGno tooling trickery unfortunately/MG
 
  MGThis is Marvin Froeder's flexmojos-flex-compiler which compiles
  mxml/MG
  MGcurrently packaged as org.sonatype.flexmojos/MG
  MGthe GAV/MG
  groupIdorg.sonatype.flexmojos/groupId
  artifactIdflexmojos-flex-compiler/artifactId
  version3.8-SNAPSHOT/version
 
  MG org.sonatype.flexmojos:asc:3.0 is requested in original
  dependency/MG
 
  
   Martin Gainty wrote on 12.03.2015 15:07:
  
flex-compiler-mojo identitifies dependency
dependency
   groupIdorg.sonatype.flexmojos/groupId

Re: What is going on with maven-javadoc-plugin?

2015-03-13 Thread Karl Heinz Marbaise

Hi Marcos,

now i would suggest to subscribe on the DEV mailing list and become an 
active member of the community and check the VOTEd release and see if it 
works for you...and please give feedback about it...


Kind regards
Karl Heinz Marbaise

On 3/13/15 10:27 PM, Marcos Zolnowski wrote:

Appearances can be deceiving, when I see the link 
http://maven.apache.org/plugins/maven-javadoc-plugin/team-list.html, there 
seems to be an army of developers.
Now I am aware of the reality of Maven, but I do not understand why a fixed bug 
needs votes.
Bug was fixed 09/Oct/14, 6 months holding a bug fix?
A fixed bug is not a new feature, why should we wait 6 months for more people 
to hit this bug, if we could solve it today?
On Friday, March 13, 2015 5:12 PM, Karl Heinz Marbaise khmarba...@gmx.de 
wrote:



Hi Marcos,


On 3/13/15 2:38 AM, Marcos Zolnowski wrote:

From: 
http://jira.codehaus.org/browse/MJAVADOC-365?focusedCommentId=363324page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-363324


It has been about 6 months now since the last activity here.

I wonder, what can be done with respect to getting a 2.11 or 2.10.2
  version with this change applied?



Can anyone tell me why no one does the release of this plugin?



Just based on lack of time...cause there are in the meantime a large
number of releases have been done and all of the members of the Maven
team are busy...You should be aware that all of the Maven team (I don't
any exception) are working on Maven in their spare time...no one is
doing this fulltime...(apart from being payed for it).

Furthermore there is no vote on the issue...

We are usually focused on issues which have more than one vote or be
more accurate having at least one vote...

and an other thing is that no one seemed to be interested in, no
feedback in the jira issue (for more than three years), nor asked
someone before...except you...

May be i'm able to check within the next days ...

Kind regards
Karl Heinz Marbaise

-
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





Mit freundlichem Gruß
Karl-Heinz Marbaise
--
SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893
Dipl.Ing.(FH) Karl-Heinz MarbaiseICQ#: 135949029
Hauptstrasse 177 USt.IdNr: DE191347579
52146 Würselen   http://www.soebes.de

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



Re: What is going on with maven-javadoc-plugin?

2015-03-13 Thread Karl Heinz Marbaise

Hi Marcos,

On 3/13/15 10:27 PM, Marcos Zolnowski wrote:

Appearances can be deceiving, when I see the link 
http://maven.apache.org/plugins/maven-javadoc-plugin/team-list.html,

 there seems to be an army of developers.


Now I am aware of the reality of Maven,


Not really ...Okhere is the reality:

$ cat pom.xml | grep roleCommitter | wc -l
  24
$ cat pom.xml | grep rolePMC | wc -l
  27

24 Committers, 27 PMC's...= 51 who can change the code...(i wouldn't 
call this an army ;-)..


The number of people who have changed code  (this area: 
https://svn.apache.org/repos/asf/maven/): I haven't checked those which 
are git in the meantime and i didn't check on Maven core itself...


from 2011/01/01 till 2011/12/31: 33
from 2012/01/01 till 2012/12/31: 25
from 2013/01/01 till 2013/12/31: 25
from 2014/01/01 till 2014/12/31: 26
from 2015/01/01 till today : 16 (this reduces down to platoon 
instead of an army ;-)..


This means in average only 50% are actively working...(2015 is not ended 
yet)..


Don't get me wrong here...I not blaming anybody...this is an open source 
project and everybody does what he/she can if he/she likes to...



 but I do not understand why a fixed bug needs votes.

Bug was fixed 09/Oct/14,
You are right. I have mistaken the bug you are referencing with another 
one..forget about that...



6 months holding a bug fix?


something missed. I wrote:

 May be i'm able to check within the next days ...


Furthermore nobody is holding...just we have done 49 releases on those 6 
months...this means in average every 3-4 days a new release...




A fixed bug is not a new feature, why should we wait 6 months for more people 
to hit this bug, if we could solve it today?




On Friday, March 13, 2015 5:12 PM, Karl Heinz Marbaise khmarba...@gmx.de 
wrote:



Hi Marcos,


On 3/13/15 2:38 AM, Marcos Zolnowski wrote:

From: 
http://jira.codehaus.org/browse/MJAVADOC-365?focusedCommentId=363324page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#comment-363324


It has been about 6 months now since the last activity here.

I wonder, what can be done with respect to getting a 2.11 or 2.10.2
  version with this change applied?



Can anyone tell me why no one does the release of this plugin?



Just based on lack of time...cause there are in the meantime a large
number of releases have been done and all of the members of the Maven
team are busy...You should be aware that all of the Maven team (I don't
any exception) are working on Maven in their spare time...no one is
doing this fulltime...(apart from being payed for it).

Furthermore there is no vote on the issue...

We are usually focused on issues which have more than one vote or be
more accurate having at least one vote...

and an other thing is that no one seemed to be interested in, no
feedback in the jira issue (for more than three years), nor asked
someone before...except you...

May be i'm able to check within the next days ...

Kind regards
Karl Heinz Marbaise


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



Re: Cannot run integration tests in maven archetype project with failsave

2015-03-13 Thread Martin Gütlein
I tried moving myproject/myproject-api-impl/src/test to 
myproject/src/test. But the tests are not found ([INFO] No tests to 
run.).


The reason could be that there is no source folder indented in the root 
project folder, I had to create it.
The failsave tests, though, are configured in the root pom.xml (not 
within the module myproject-api-impl/pom.xml).


Martin


Am 13.03.2015 um 09:34 schrieb Sandra Parsick:

I would move the integration tests from myproject-api-impl to the war module

Regards,

Sandra

Am 13.03.2015 um 09:18 schrieb Martin Gütlein:

The failsave integration tests do not run. They should be applied to the
whole service (war). But they are defined within a module
(myproject-api-impl) and are therefore skipped. I could not figure out
how to configure this.

Martin


Am 13.03.2015 um 09:00 schrieb Hervé BOUTEMY:

sorry, can't understand the case: problem when building the archetype?
with
project generated from archetype?

Regards,

Hervé

Le vendredi 13 mars 2015 08:54:06 Martin Gütlein a écrit :

Anyone?
Where could I get some help on this issue (already tried stackoverflow
as well)?

Martin

Am 10.03.2015 um 19:59 schrieb Martin Gütlein:

Hi,

I would like to run integration tests on my project, performing and
testing rest-calls to my server.

I have a maven project layout like with modules:
MyProject-api
MyProject-api-impl
MyProject-webapp
MyProject-webapp-exec
MyProject-webapp-it
(see https://tomcat.apache.org/maven-plugin-2.0-beta-1/archetype.html)

The IT tests are defined in
MyProject-api-impl/src/test/java/.../..IT.java This may be part of the
problem, because they should be applied not only to the
project-api-impl, but to the entire project. How can I specify this?

Kind regards,
Martin

I'll post parts of my pom.xml at the end of this mail. When I run mvn
verify the output looks like this:

$ mvn clean verify
[INFO] Scanning for projects...
[INFO]


[INFO] Reactor Build Order:
[INFO]
[INFO] MyProject
[INFO] MyProject-api
[INFO] MyProject-api-impl
[INFO] MyProject-webapp
[INFO] MyProject-webapp-exec
[INFO]
[INFO]


[INFO] Building MyProject 0.2
[INFO]


[INFO]
...
[INFO]
[INFO] --- tomcat7-maven-plugin:2.0:run-war-only (tomcat7-run) @
MyProject ---
[INFO] Skipping non-war project
[INFO]
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @
MyProject ---
[INFO] No tests to run.
[INFO]
[INFO] --- tomcat7-maven-plugin:2.0:shutdown (tomcat7-shutdown) @
MyProject ---
[INFO]
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ MyProject
---
[INFO] No tests to run.
[INFO]
[INFO]


[INFO] Building MyProject-api 0.2
[INFO]


[INFO]

[INFO]
[INFO]


[INFO] Building MyProject-api-impl 0.2
[INFO]


[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @
MyProject-api-impl ---
[INFO] Deleting
/home/martin/workspace/myproject/MyProject-api-impl/target
[INFO]
[INFO] --- maven-enforcer-plugin:1.0.1:enforce (enforce-java) @
MyProject-api-impl ---
[INFO]
[INFO] --- maven-resources-plugin:2.3:resources (default-resources) @
MyProject-api-impl ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/martin/workspace/myproject/MyProject-api-impl/src/main/resources
[INFO]
[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @
MyProject-api-impl ---
[INFO] Compiling 280 source files to
/home/martin/workspace/myproject/MyProject-api-impl/target/classes
[INFO]
[INFO] --- maven-resources-plugin:2.3:testResources
(default-testResources) @ MyProject-api-impl ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/martin/workspace/myproject/MyProject-api-impl/src/test/resources
[INFO]
[INFO] --- maven-compiler-plugin:2.5.1:testCompile
(default-testCompile) @ MyProject-api-impl ---
[INFO] Compiling 4 source files to
/home/martin/workspace/myproject/MyProject-api-impl/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:2.12.3:test (default-test) @
MyProject-api-impl ---
[INFO] Tests are skipped.
[INFO]
[INFO] --- maven-jar-plugin:2.2:jar (default-jar) @ MyProject-api-impl
---
[INFO] Building jar:
/home/martin/workspace/myproject/MyProject-api-impl/target/MyProject-api-i

mpl-0.2.jar [INFO]
[INFO] --- tomcat7-maven-plugin:2.0:run-war-only (tomcat7-run) @
MyProject-api-impl ---
[INFO] Skipping non-war project
[INFO]
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @
MyProject-api-impl ---
[INFO] Failsafe report directory:

Re: Cannot run integration tests in maven archetype project with failsave

2015-03-13 Thread Martin Gütlein
The failsave integration tests do not run. They should be applied to the 
whole service (war). But they are defined within a module 
(myproject-api-impl) and are therefore skipped. I could not figure out 
how to configure this.


Martin


Am 13.03.2015 um 09:00 schrieb Hervé BOUTEMY:

sorry, can't understand the case: problem when building the archetype? with
project generated from archetype?

Regards,

Hervé

Le vendredi 13 mars 2015 08:54:06 Martin Gütlein a écrit :

Anyone?
Where could I get some help on this issue (already tried stackoverflow
as well)?

Martin

Am 10.03.2015 um 19:59 schrieb Martin Gütlein:

Hi,

I would like to run integration tests on my project, performing and
testing rest-calls to my server.

I have a maven project layout like with modules:
MyProject-api
MyProject-api-impl
MyProject-webapp
MyProject-webapp-exec
MyProject-webapp-it
(see https://tomcat.apache.org/maven-plugin-2.0-beta-1/archetype.html)

The IT tests are defined in
MyProject-api-impl/src/test/java/.../..IT.java This may be part of the
problem, because they should be applied not only to the
project-api-impl, but to the entire project. How can I specify this?

Kind regards,
Martin

I'll post parts of my pom.xml at the end of this mail. When I run mvn
verify the output looks like this:

$ mvn clean verify
[INFO] Scanning for projects...
[INFO]

[INFO] Reactor Build Order:
[INFO]
[INFO] MyProject
[INFO] MyProject-api
[INFO] MyProject-api-impl
[INFO] MyProject-webapp
[INFO] MyProject-webapp-exec
[INFO]
[INFO]

[INFO] Building MyProject 0.2
[INFO]

[INFO]
...
[INFO]
[INFO] --- tomcat7-maven-plugin:2.0:run-war-only (tomcat7-run) @
MyProject ---
[INFO] Skipping non-war project
[INFO]
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @
MyProject ---
[INFO] No tests to run.
[INFO]
[INFO] --- tomcat7-maven-plugin:2.0:shutdown (tomcat7-shutdown) @
MyProject ---
[INFO]
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ MyProject ---
[INFO] No tests to run.
[INFO]
[INFO]

[INFO] Building MyProject-api 0.2
[INFO]

[INFO]

[INFO]
[INFO]

[INFO] Building MyProject-api-impl 0.2
[INFO]

[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @
MyProject-api-impl ---
[INFO] Deleting
/home/martin/workspace/myproject/MyProject-api-impl/target
[INFO]
[INFO] --- maven-enforcer-plugin:1.0.1:enforce (enforce-java) @
MyProject-api-impl ---
[INFO]
[INFO] --- maven-resources-plugin:2.3:resources (default-resources) @
MyProject-api-impl ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/martin/workspace/myproject/MyProject-api-impl/src/main/resources
[INFO]
[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @
MyProject-api-impl ---
[INFO] Compiling 280 source files to
/home/martin/workspace/myproject/MyProject-api-impl/target/classes
[INFO]
[INFO] --- maven-resources-plugin:2.3:testResources
(default-testResources) @ MyProject-api-impl ---
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory
/home/martin/workspace/myproject/MyProject-api-impl/src/test/resources
[INFO]
[INFO] --- maven-compiler-plugin:2.5.1:testCompile
(default-testCompile) @ MyProject-api-impl ---
[INFO] Compiling 4 source files to
/home/martin/workspace/myproject/MyProject-api-impl/target/test-classes
[INFO]
[INFO] --- maven-surefire-plugin:2.12.3:test (default-test) @
MyProject-api-impl ---
[INFO] Tests are skipped.
[INFO]
[INFO] --- maven-jar-plugin:2.2:jar (default-jar) @ MyProject-api-impl
---
[INFO] Building jar:
/home/martin/workspace/myproject/MyProject-api-impl/target/MyProject-api-i
mpl-0.2.jar [INFO]
[INFO] --- tomcat7-maven-plugin:2.0:run-war-only (tomcat7-run) @
MyProject-api-impl ---
[INFO] Skipping non-war project
[INFO]
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @
MyProject-api-impl ---
[INFO] Failsafe report directory:
/home/martin/workspace/myproject/MyProject-api-impl/target/failsafe-report
s

---

  T E S T S

---
Running org.kramerlab.myproject.api.impl.services.CompoundIT
anonymous  GET to http://localhost:8080
failed, please start services first!






Parts of my pom.xml in the root project folder:

build

 pluginManagement
 
   plugins
 
 ...
 
 plugin
 
   groupIdorg.apache.tomcat.maven/groupId



Re: Do people actually use markdown or should I abandon it and migrate to xdocs?

2015-03-13 Thread Hervé BOUTEMY
community is large: a lot of people use a lot of formats with maven-site-
plugin
and a lot of people have their own opinion about the format for the future :)

That's the first time I hear about 10 minutes to generate the hand-written 
markup (whatever the format is or the number of files): what can take time are 
the reports, but not markup
For example, 10 seconds is the time to render markup from the Maven's site
[INFO] Rendering 185 Doxia documents: 144 apt, 4 fml, 28 markdown, 9 xdoc

Can you please open a Jira issue, with example or at least log for me to 
understand where time is going?
(in maven-site-plugin 3.4, I added the previous output to more clearly 
distinguish reports from handwritten Doxia documents, see MSITE-714)


Then that's the first time I hear about maven-site-plugin's Markdown threading 
issues: is there any Jira issue about it, with example to reproduce?

notice that multi-module site plugin already stresses core regarding reports 
(with aggregate reports requiring modules): I don't think building the site in 
parallel is a great idea, or at least that it is really well tested
Perhaps you should aboid this one (you don't build the site on each code 
build, aren't you?)

Regards,

Hervé

Le jeudi 12 mars 2015 14:11:59 Kevin Burton a écrit :
 I really wanted to live in the future but I think Markdown support in Maven
 is really lacking.
 
 1. it’s super slow.  I have a moderate sized project (10 small files) and
 it takes like 10 minutes to generate my site.
 
 2.  It’s buggy.  If you have two projects and a multi-module build you
 can’t use threaded builds.
 
 Now it looks as if my documentation generation has completely locked up.
 I’m not sure what change I made but 9/10 times I run it locks up in an
 infinite loop.
 
 I imagine if no one else is actually using it then I should probably just
 use what the community is running.


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



Re: Cannot run integration tests in maven archetype project with failsave

2015-03-13 Thread Hervé BOUTEMY
sorry, can't understand the case: problem when building the archetype? with 
project generated from archetype?

Regards,

Hervé

Le vendredi 13 mars 2015 08:54:06 Martin Gütlein a écrit :
 Anyone?
 Where could I get some help on this issue (already tried stackoverflow
 as well)?
 
 Martin
 
 Am 10.03.2015 um 19:59 schrieb Martin Gütlein:
  Hi,
  
  I would like to run integration tests on my project, performing and
  testing rest-calls to my server.
  
  I have a maven project layout like with modules:
  MyProject-api
  MyProject-api-impl
  MyProject-webapp
  MyProject-webapp-exec
  MyProject-webapp-it
  (see https://tomcat.apache.org/maven-plugin-2.0-beta-1/archetype.html)
  
  The IT tests are defined in
  MyProject-api-impl/src/test/java/.../..IT.java This may be part of the
  problem, because they should be applied not only to the
  project-api-impl, but to the entire project. How can I specify this?
  
  Kind regards,
  Martin
  
  I'll post parts of my pom.xml at the end of this mail. When I run mvn
  verify the output looks like this:
  
  $ mvn clean verify
  [INFO] Scanning for projects...
  [INFO]
  
  [INFO] Reactor Build Order:
  [INFO]
  [INFO] MyProject
  [INFO] MyProject-api
  [INFO] MyProject-api-impl
  [INFO] MyProject-webapp
  [INFO] MyProject-webapp-exec
  [INFO]
  [INFO]
  
  [INFO] Building MyProject 0.2
  [INFO]
  
  [INFO]
  ...
  [INFO]
  [INFO] --- tomcat7-maven-plugin:2.0:run-war-only (tomcat7-run) @
  MyProject ---
  [INFO] Skipping non-war project
  [INFO]
  [INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @
  MyProject ---
  [INFO] No tests to run.
  [INFO]
  [INFO] --- tomcat7-maven-plugin:2.0:shutdown (tomcat7-shutdown) @
  MyProject ---
  [INFO]
  [INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ MyProject ---
  [INFO] No tests to run.
  [INFO]
  [INFO]
  
  [INFO] Building MyProject-api 0.2
  [INFO]
  
  [INFO]
  
  [INFO]
  [INFO]
  
  [INFO] Building MyProject-api-impl 0.2
  [INFO]
  
  [INFO]
  [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @
  MyProject-api-impl ---
  [INFO] Deleting
  /home/martin/workspace/myproject/MyProject-api-impl/target
  [INFO]
  [INFO] --- maven-enforcer-plugin:1.0.1:enforce (enforce-java) @
  MyProject-api-impl ---
  [INFO]
  [INFO] --- maven-resources-plugin:2.3:resources (default-resources) @
  MyProject-api-impl ---
  [INFO] Using 'UTF-8' encoding to copy filtered resources.
  [INFO] skip non existing resourceDirectory
  /home/martin/workspace/myproject/MyProject-api-impl/src/main/resources
  [INFO]
  [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @
  MyProject-api-impl ---
  [INFO] Compiling 280 source files to
  /home/martin/workspace/myproject/MyProject-api-impl/target/classes
  [INFO]
  [INFO] --- maven-resources-plugin:2.3:testResources
  (default-testResources) @ MyProject-api-impl ---
  [INFO] Using 'UTF-8' encoding to copy filtered resources.
  [INFO] skip non existing resourceDirectory
  /home/martin/workspace/myproject/MyProject-api-impl/src/test/resources
  [INFO]
  [INFO] --- maven-compiler-plugin:2.5.1:testCompile
  (default-testCompile) @ MyProject-api-impl ---
  [INFO] Compiling 4 source files to
  /home/martin/workspace/myproject/MyProject-api-impl/target/test-classes
  [INFO]
  [INFO] --- maven-surefire-plugin:2.12.3:test (default-test) @
  MyProject-api-impl ---
  [INFO] Tests are skipped.
  [INFO]
  [INFO] --- maven-jar-plugin:2.2:jar (default-jar) @ MyProject-api-impl
  ---
  [INFO] Building jar:
  /home/martin/workspace/myproject/MyProject-api-impl/target/MyProject-api-i
  mpl-0.2.jar [INFO]
  [INFO] --- tomcat7-maven-plugin:2.0:run-war-only (tomcat7-run) @
  MyProject-api-impl ---
  [INFO] Skipping non-war project
  [INFO]
  [INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @
  MyProject-api-impl ---
  [INFO] Failsafe report directory:
  /home/martin/workspace/myproject/MyProject-api-impl/target/failsafe-report
  s
  
  ---
  
   T E S T S
  
  ---
  Running org.kramerlab.myproject.api.impl.services.CompoundIT
  anonymous  GET to http://localhost:8080
  failed, please start services first!
  
  
  
  
  
  
  Parts of my pom.xml in the root project folder:
  
  build
  
  pluginManagement
  
plugins
  
  ...
  
  plugin
  
groupIdorg.apache.tomcat.maven/groupId
  
  

Re: Cannot run integration tests in maven archetype project with failsave

2015-03-13 Thread Sandra Parsick
I would move the integration tests from myproject-api-impl to the war module

Regards,

Sandra

Am 13.03.2015 um 09:18 schrieb Martin Gütlein:
 The failsave integration tests do not run. They should be applied to the
 whole service (war). But they are defined within a module
 (myproject-api-impl) and are therefore skipped. I could not figure out
 how to configure this.
 
 Martin
 
 
 Am 13.03.2015 um 09:00 schrieb Hervé BOUTEMY:
 sorry, can't understand the case: problem when building the archetype?
 with
 project generated from archetype?

 Regards,

 Hervé

 Le vendredi 13 mars 2015 08:54:06 Martin Gütlein a écrit :
 Anyone?
 Where could I get some help on this issue (already tried stackoverflow
 as well)?

 Martin

 Am 10.03.2015 um 19:59 schrieb Martin Gütlein:
 Hi,

 I would like to run integration tests on my project, performing and
 testing rest-calls to my server.

 I have a maven project layout like with modules:
 MyProject-api
 MyProject-api-impl
 MyProject-webapp
 MyProject-webapp-exec
 MyProject-webapp-it
 (see https://tomcat.apache.org/maven-plugin-2.0-beta-1/archetype.html)

 The IT tests are defined in
 MyProject-api-impl/src/test/java/.../..IT.java This may be part of the
 problem, because they should be applied not only to the
 project-api-impl, but to the entire project. How can I specify this?

 Kind regards,
 Martin

 I'll post parts of my pom.xml at the end of this mail. When I run mvn
 verify the output looks like this:

 $ mvn clean verify
 [INFO] Scanning for projects...
 [INFO]
 

 [INFO] Reactor Build Order:
 [INFO]
 [INFO] MyProject
 [INFO] MyProject-api
 [INFO] MyProject-api-impl
 [INFO] MyProject-webapp
 [INFO] MyProject-webapp-exec
 [INFO]
 [INFO]
 

 [INFO] Building MyProject 0.2
 [INFO]
 

 [INFO]
 ...
 [INFO]
 [INFO] --- tomcat7-maven-plugin:2.0:run-war-only (tomcat7-run) @
 MyProject ---
 [INFO] Skipping non-war project
 [INFO]
 [INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @
 MyProject ---
 [INFO] No tests to run.
 [INFO]
 [INFO] --- tomcat7-maven-plugin:2.0:shutdown (tomcat7-shutdown) @
 MyProject ---
 [INFO]
 [INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ MyProject
 ---
 [INFO] No tests to run.
 [INFO]
 [INFO]
 

 [INFO] Building MyProject-api 0.2
 [INFO]
 

 [INFO]
 
 [INFO]
 [INFO]
 

 [INFO] Building MyProject-api-impl 0.2
 [INFO]
 

 [INFO]
 [INFO] --- maven-clean-plugin:2.5:clean (default-clean) @
 MyProject-api-impl ---
 [INFO] Deleting
 /home/martin/workspace/myproject/MyProject-api-impl/target
 [INFO]
 [INFO] --- maven-enforcer-plugin:1.0.1:enforce (enforce-java) @
 MyProject-api-impl ---
 [INFO]
 [INFO] --- maven-resources-plugin:2.3:resources (default-resources) @
 MyProject-api-impl ---
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] skip non existing resourceDirectory
 /home/martin/workspace/myproject/MyProject-api-impl/src/main/resources
 [INFO]
 [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @
 MyProject-api-impl ---
 [INFO] Compiling 280 source files to
 /home/martin/workspace/myproject/MyProject-api-impl/target/classes
 [INFO]
 [INFO] --- maven-resources-plugin:2.3:testResources
 (default-testResources) @ MyProject-api-impl ---
 [INFO] Using 'UTF-8' encoding to copy filtered resources.
 [INFO] skip non existing resourceDirectory
 /home/martin/workspace/myproject/MyProject-api-impl/src/test/resources
 [INFO]
 [INFO] --- maven-compiler-plugin:2.5.1:testCompile
 (default-testCompile) @ MyProject-api-impl ---
 [INFO] Compiling 4 source files to
 /home/martin/workspace/myproject/MyProject-api-impl/target/test-classes
 [INFO]
 [INFO] --- maven-surefire-plugin:2.12.3:test (default-test) @
 MyProject-api-impl ---
 [INFO] Tests are skipped.
 [INFO]
 [INFO] --- maven-jar-plugin:2.2:jar (default-jar) @ MyProject-api-impl
 ---
 [INFO] Building jar:
 /home/martin/workspace/myproject/MyProject-api-impl/target/MyProject-api-i

 mpl-0.2.jar [INFO]
 [INFO] --- tomcat7-maven-plugin:2.0:run-war-only (tomcat7-run) @
 MyProject-api-impl ---
 [INFO] Skipping non-war project
 [INFO]
 [INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @
 MyProject-api-impl ---
 [INFO] Failsafe report directory:
 /home/martin/workspace/myproject/MyProject-api-impl/target/failsafe-report

 s

 ---

   T E S T S

 ---
 Running org.kramerlab.myproject.api.impl.services.CompoundIT
 anonymous  GET to 

Re: Cannot run integration tests in maven archetype project with failsave

2015-03-13 Thread Martin Gütlein

Anyone?
Where could I get some help on this issue (already tried stackoverflow 
as well)?


Martin

Am 10.03.2015 um 19:59 schrieb Martin Gütlein:

Hi,

I would like to run integration tests on my project, performing and 
testing rest-calls to my server.


I have a maven project layout like with modules:
MyProject-api
MyProject-api-impl
MyProject-webapp
MyProject-webapp-exec
MyProject-webapp-it
(see https://tomcat.apache.org/maven-plugin-2.0-beta-1/archetype.html)

The IT tests are defined in 
MyProject-api-impl/src/test/java/.../..IT.java This may be part of the 
problem, because they should be applied not only to the 
project-api-impl, but to the entire project. How can I specify this?


Kind regards,
Martin

I'll post parts of my pom.xml at the end of this mail. When I run mvn 
verify the output looks like this:


$ mvn clean verify
[INFO] Scanning for projects...
[INFO] 


[INFO] Reactor Build Order:
[INFO]
[INFO] MyProject
[INFO] MyProject-api
[INFO] MyProject-api-impl
[INFO] MyProject-webapp
[INFO] MyProject-webapp-exec
[INFO]
[INFO] 


[INFO] Building MyProject 0.2
[INFO] 


[INFO]
...
[INFO]
[INFO] --- tomcat7-maven-plugin:2.0:run-war-only (tomcat7-run) @ 
MyProject ---

[INFO] Skipping non-war project
[INFO]
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ 
MyProject ---

[INFO] No tests to run.
[INFO]
[INFO] --- tomcat7-maven-plugin:2.0:shutdown (tomcat7-shutdown) @ 
MyProject ---

[INFO]
[INFO] --- maven-failsafe-plugin:2.12.4:verify (default) @ MyProject ---
[INFO] No tests to run.
[INFO]
[INFO] 


[INFO] Building MyProject-api 0.2
[INFO] 


[INFO]

[INFO]
[INFO] 


[INFO] Building MyProject-api-impl 0.2
[INFO] 


[INFO]
[INFO] --- maven-clean-plugin:2.5:clean (default-clean) @ 
MyProject-api-impl ---
[INFO] Deleting 
/home/martin/workspace/myproject/MyProject-api-impl/target

[INFO]
[INFO] --- maven-enforcer-plugin:1.0.1:enforce (enforce-java) @ 
MyProject-api-impl ---

[INFO]
[INFO] --- maven-resources-plugin:2.3:resources (default-resources) @ 
MyProject-api-impl ---

[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/martin/workspace/myproject/MyProject-api-impl/src/main/resources

[INFO]
[INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ 
MyProject-api-impl ---
[INFO] Compiling 280 source files to 
/home/martin/workspace/myproject/MyProject-api-impl/target/classes

[INFO]
[INFO] --- maven-resources-plugin:2.3:testResources 
(default-testResources) @ MyProject-api-impl ---

[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] skip non existing resourceDirectory 
/home/martin/workspace/myproject/MyProject-api-impl/src/test/resources

[INFO]
[INFO] --- maven-compiler-plugin:2.5.1:testCompile 
(default-testCompile) @ MyProject-api-impl ---
[INFO] Compiling 4 source files to 
/home/martin/workspace/myproject/MyProject-api-impl/target/test-classes

[INFO]
[INFO] --- maven-surefire-plugin:2.12.3:test (default-test) @ 
MyProject-api-impl ---

[INFO] Tests are skipped.
[INFO]
[INFO] --- maven-jar-plugin:2.2:jar (default-jar) @ MyProject-api-impl 
---
[INFO] Building jar: 
/home/martin/workspace/myproject/MyProject-api-impl/target/MyProject-api-impl-0.2.jar

[INFO]
[INFO] --- tomcat7-maven-plugin:2.0:run-war-only (tomcat7-run) @ 
MyProject-api-impl ---

[INFO] Skipping non-war project
[INFO]
[INFO] --- maven-failsafe-plugin:2.12.4:integration-test (default) @ 
MyProject-api-impl ---
[INFO] Failsafe report directory: 
/home/martin/workspace/myproject/MyProject-api-impl/target/failsafe-reports


---
 T E S T S
---
Running org.kramerlab.myproject.api.impl.services.CompoundIT
anonymous  GET to http://localhost:8080
failed, please start services first!






Parts of my pom.xml in the root project folder:

build
pluginManagement
  plugins
...
plugin
  groupIdorg.apache.tomcat.maven/groupId
artifactIdtomcat7-maven-plugin/artifactId
  version2.0/version
  executions
execution
  idtomcat7-run/id
  goals
goalrun-war-only/goal
  /goals
  phasepre-integration-test/phase
  configuration
forktrue/fork
  /configuration
/execution
execution
  idtomcat7-shutdown/id
  goals
goalshutdown/goal

[ANN] Apache Maven Archetype 2.3 Released

2015-03-13 Thread Benson Margulies
The Apache Maven team is pleased to announce the release of Apache
Maven Archetype 2.3.

Archetype is a tool for setting up new Maven projects.

This is the last release intended to provide support for Maven 2.2.x.

Release notes: 
http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=11095version=18127

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: artifactasc/artifactId missing ?

2015-03-13 Thread Martin Gainty
asc (mxml compiler) project is buried in flexover-sdk (last touched in 2007)

https://code.google.com/p/flexcover-sdk/source/checkout

here are the dependencies from build.xml
property name=mxmlc.classpath value=xercesPatch.jar asc.jar xercesImpl.jar 
xmlParserAPIs.jar afe.jar aglj32.jar rideau.jar batik-awt-util.jar 
batik-bridge.jar batik-css.jar batik-dom.jar batik-ext.jar batik-gvt.jar 
batik-parser.jar batik-script.jar batik-svg-dom.jar batik-svggen.jar 
batik-util.jar batik-transcoder.jar batik-xml.jar mm-velocity-1.4.jar 
commons-collections.jar commons-discovery.jar commons-logging.jar license.jar 
swfutils.jar flex-fontkit.jar flex-messaging-common.jar mxmlc_ja.jar 
xalan.jar/

with the exception of mm-velocity version 1.4 
it looks like I have much work to make this a proper pom

Bedankt/Danke
Martin 
__  
  


 From: mgai...@hotmail.com
 To: users@maven.apache.org
 Subject: RE: artifactasc/artifactId missing ?
 Date: Thu, 12 Mar 2015 19:57:09 -0400
 
   
   
 
 
  Subject: Re: artifactasc/artifactId missing ?
  From: manf...@mosabuam.com
  To: users@maven.apache.org
  Date: Thu, 12 Mar 2015 23:38:41 +0100
  
  I can not find it on https://oss.sonatype.org/ or 
  https://repository.sonatype.org/ even when logged in.
  
  Manfred
 
 MGno tooling trickery unfortunately/MG
 
 MGThis is Marvin Froeder's flexmojos-flex-compiler which compiles mxml/MG
 MGcurrently packaged as org.sonatype.flexmojos/MG
 MGthe GAV/MG
 groupIdorg.sonatype.flexmojos/groupId
 artifactIdflexmojos-flex-compiler/artifactId
 version3.8-SNAPSHOT/version
 
 MG org.sonatype.flexmojos:asc:3.0 is requested in original dependency/MG
 
  
  Martin Gainty wrote on 12.03.2015 15:07:
  
   flex-compiler-mojo identitifies dependency
   dependency
  groupIdorg.sonatype.flexmojos/groupId
  artifactIdasc/artifactId
  version3.0/version
  /dependency
   
   which I cannot locate
   any suggestions where to find this artifact would be GREATLY appreciated
   
   thanks/bedankt
   Martin 
   __ 
 
  
   
  
  -
  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
  For additional commands, e-mail: users-h...@maven.apache.org
  
 
  

Re: artifactasc/artifactId missing ?

2015-03-13 Thread Curtis Rueden
Hi Martin,

org.sonatype.flexmojos:flexmojos-flex-compiler:3.8-SNAPSHOT is ancient.
There are several new major versions, including a groupId change to
net.flexmojos.oss:

https://repository.sonatype.org/#nexus-search;quick~flexmojos-flex-compiler

The latest on Maven Central is:
net.flexmojos.oss:flexmojos-flex-compiler:7.0.1

http://search.maven.org/#artifactdetails%7Cnet.flexmojos.oss%7Cflexmojos-flex-compiler%7C7.0.1%7Cjar

Regards,
Curtis

On Thu, Mar 12, 2015 at 6:57 PM, Martin Gainty mgai...@hotmail.com wrote:




  Subject: Re: artifactasc/artifactId missing ?
  From: manf...@mosabuam.com
  To: users@maven.apache.org
  Date: Thu, 12 Mar 2015 23:38:41 +0100
 
  I can not find it on https://oss.sonatype.org/ or
 https://repository.sonatype.org/ even when logged in.
 
  Manfred

 MGno tooling trickery unfortunately/MG

 MGThis is Marvin Froeder's flexmojos-flex-compiler which compiles
 mxml/MG
 MGcurrently packaged as org.sonatype.flexmojos/MG
 MGthe GAV/MG
 groupIdorg.sonatype.flexmojos/groupId
 artifactIdflexmojos-flex-compiler/artifactId
 version3.8-SNAPSHOT/version

 MG org.sonatype.flexmojos:asc:3.0 is requested in original
 dependency/MG

 
  Martin Gainty wrote on 12.03.2015 15:07:
 
   flex-compiler-mojo identitifies dependency
   dependency
  groupIdorg.sonatype.flexmojos/groupId
  artifactIdasc/artifactId
  version3.0/version
  /dependency
  
   which I cannot locate
   any suggestions where to find this artifact would be GREATLY
 appreciated
  
   thanks/bedankt
   Martin
   __
  
  
 
  -
  To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
  For additional commands, e-mail: users-h...@maven.apache.org