Re: maven-deploy pulling extraneous dependency's metadata?!

[Tim Allison]

What?!

On Wed, Jul 10, 2024 at 4:20 PM Tamás Cservenák  wrote:

> Howdy,
>
> reproduced, and is even weirder:
>
> https://gist.github.com/cstamas/4f2e9e68f35da850be60e44c24bc581a#file-gistfile1-txt-L70
>
> Line 70 is what you mention...
>
> But not only that, you have the same stuff INSTALLed as well, see line 32!
> Looking more...
>
>
> On Wed, Jul 10, 2024 at 9:44 PM Tim Allison  wrote:
>
> > Apache Maven 3.9.7 (8b094c9513efc1b9ce2d952b3b9c8eaedaf8cbf0)
> > Maven home: /apache/apache-maven-3.9.7
> > Java version: 11.0.23, vendor: Eclipse Adoptium, runtime:
> > /usr/lib/jvm/temurin-11-jdk-amd64
> > Default locale: en_US, platform encoding: UTF-8
> > OS name: "linux", version: "6.5.0-41-generic", arch: "amd64", family:
> > "unix"
> >
> > I've downgraded the version of the deploy plugin for now. I'll let you
> know
> > if that works. Thank you!
> >
> > On Wed, Jul 10, 2024 at 3:37 PM Tamás Cservenák 
> > wrote:
> >
> > > Howdy,
> > >
> > > This is wierd. What maven version are you using? And what java version?
> > > Will try to reproduce.
> > >
> > > T
> > >
> > > On Wed, Jul 10, 2024, 20:56 Tim Allison  wrote:
> > >
> > > > Hi All,
> > > >   I'm sure this is user error. I recently tried to deploy Apache Tika
> > > with
> > > > maven-deploy-plugin:3.1.2.
> > > > I'm having a problem with deploying a new module we just added.
> > > >
> > > > Our repo is here: https://github.com/apache/tika
> > > >
> > > > I see the usual download/upload pattern, but then after the final
> > > download
> > > > of tika-grpc/metadata.xml, it looks like it is trying to download the
> > > > metadata for xmlbeans?!
> > > >
> > > > What am I doing wrong?
> > > >
> > > > Thank you!
> > > >
> > > > Expected pattern:
> > > >
> > > > [INFO] [INFO] --- deploy:3.1.2:deploy (default-deploy) @ tika-grpc
> ---
> > > > [INFO] Uploading to apache.releases.https:
> > > >
> > > >
> > >
> >
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2.pom
> > > > [INFO] Progress (1): 16 kB
> > > > [INFO]
> > > > [INFO] Uploaded to apache.releases.https:
> > > >
> > > >
> > >
> >
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2.pom
> > > > (16 kB at 9.0 kB/s)
> > > > [INFO] Uploading to apache.releases.https:
> > > >
> > > >
> > >
> >
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2.jar
> > > > [INFO] Uploading to apache.releases.https:
> > > >
> > > >
> > >
> >
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2-sources.jar
> > > > [INFO] Uploading to apache.releases.https:
> > > >
> > > >
> > >
> >
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2.pom.asc
> > > > [INFO] Uploading to apache.releases.https:
> > > >
> > > >
> > >
> >
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2.jar.asc
> > > > [INFO] Uploading to apache.releases.https:
> > > >
> > > >
> > >
> >
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2-sources.jar.asc
> > > > 
> > > >
> > > > [INFO] Uploaded to apache.releases.https:
> > > >
> > > >
> > >
> >
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2.jar.asc
> > > > (833 B at 1.2 kB/s)
> > > > [INFO] Uploaded to apache.releases.https:
> > > >
> > > >
> > >
> >
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2.pom.asc
> > > > (833 B at 1.2 kB/s)
> > > > [INFO] Uploaded to apac

Re: maven-deploy pulling extraneous dependency's metadata?!

[Tim Allison]

Sorry, should have been dev@tika earlier, not private@tika.

I rolled back the deploy-plugin to 3.1.1, which was successful for our last
deployment of 2.9.2. That worked then. It does not work now with this new
tika-grpc module.

On Wed, Jul 10, 2024 at 3:42 PM Tim Allison  wrote:

> Apache Maven 3.9.7 (8b094c9513efc1b9ce2d952b3b9c8eaedaf8cbf0)
> Maven home: /apache/apache-maven-3.9.7
> Java version: 11.0.23, vendor: Eclipse Adoptium, runtime:
> /usr/lib/jvm/temurin-11-jdk-amd64
> Default locale: en_US, platform encoding: UTF-8
> OS name: "linux", version: "6.5.0-41-generic", arch: "amd64", family:
> "unix"
>
> I've downgraded the version of the deploy plugin for now. I'll let you
> know if that works. Thank you!
>
> On Wed, Jul 10, 2024 at 3:37 PM Tamás Cservenák 
> wrote:
>
>> Howdy,
>>
>> This is wierd. What maven version are you using? And what java version?
>> Will try to reproduce.
>>
>> T
>>
>> On Wed, Jul 10, 2024, 20:56 Tim Allison  wrote:
>>
>> > Hi All,
>> >   I'm sure this is user error. I recently tried to deploy Apache Tika
>> with
>> > maven-deploy-plugin:3.1.2.
>> > I'm having a problem with deploying a new module we just added.
>> >
>> > Our repo is here: https://github.com/apache/tika
>> >
>> > I see the usual download/upload pattern, but then after the final
>> download
>> > of tika-grpc/metadata.xml, it looks like it is trying to download the
>> > metadata for xmlbeans?!
>> >
>> > What am I doing wrong?
>> >
>> > Thank you!
>> >
>> > Expected pattern:
>> >
>> > [INFO] [INFO] --- deploy:3.1.2:deploy (default-deploy) @ tika-grpc ---
>> > [INFO] Uploading to apache.releases.https:
>> >
>> >
>> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2.pom
>> > [INFO] Progress (1): 16 kB
>> > [INFO]
>> > [INFO] Uploaded to apache.releases.https:
>> >
>> >
>> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2.pom
>> > (16 kB at 9.0 kB/s)
>> > [INFO] Uploading to apache.releases.https:
>> >
>> >
>> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2.jar
>> > [INFO] Uploading to apache.releases.https:
>> >
>> >
>> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2-sources.jar
>> > [INFO] Uploading to apache.releases.https:
>> >
>> >
>> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2.pom.asc
>> > [INFO] Uploading to apache.releases.https:
>> >
>> >
>> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2.jar.asc
>> > [INFO] Uploading to apache.releases.https:
>> >
>> >
>> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2-sources.jar.asc
>> > 
>> >
>> > [INFO] Uploaded to apache.releases.https:
>> >
>> >
>> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2.jar.asc
>> > (833 B at 1.2 kB/s)
>> > [INFO] Uploaded to apache.releases.https:
>> >
>> >
>> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2.pom.asc
>> > (833 B at 1.2 kB/s)
>> > [INFO] Uploaded to apache.releases.https:
>> >
>> >
>> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2-sources.jar.asc
>> > (833 B at 1.2 kB/s)
>> > 
>> >
>> > [INFO] Uploaded to apache.releases.https:
>> >
>> >
>> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2-sources.jar
>> > (82 kB at 53 kB/s)
>> >
>> > 
>> >
>> > [INFO] Uploaded to apache.releases.https:
>> >
>> >
>> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2.jar
>> > (72 MB at 6.2 MB/s)
>> > [INFO] Downloading from apache.releases.https:
>> >
>> >
>> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/maven-metadata.xml
>> > *[INFO] Downloading from apache.releases.https:
>> >
>> >
>> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/xmlbeans/maven-metadata.xml
>> > <
>> >
>> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/xmlbeans/maven-metadata.xml
>> > >*
>> > [INFO] [WARNING] Could not transfer metadata
>> > org.apache.xmlbeans/maven-metadata.xml from/to apache.releases.https (
>> > https://repository.apache.org/service/local/staging/deploy/maven2):
>> status
>> > code: 400, reason phrase: Bad Request (400)
>> >
>>
>

Re: maven-deploy pulling extraneous dependency's metadata?!

[Tim Allison]

Apache Maven 3.9.7 (8b094c9513efc1b9ce2d952b3b9c8eaedaf8cbf0)
Maven home: /apache/apache-maven-3.9.7
Java version: 11.0.23, vendor: Eclipse Adoptium, runtime:
/usr/lib/jvm/temurin-11-jdk-amd64
Default locale: en_US, platform encoding: UTF-8
OS name: "linux", version: "6.5.0-41-generic", arch: "amd64", family: "unix"

I've downgraded the version of the deploy plugin for now. I'll let you know
if that works. Thank you!

On Wed, Jul 10, 2024 at 3:37 PM Tamás Cservenák  wrote:

> Howdy,
>
> This is wierd. What maven version are you using? And what java version?
> Will try to reproduce.
>
> T
>
> On Wed, Jul 10, 2024, 20:56 Tim Allison  wrote:
>
> > Hi All,
> >   I'm sure this is user error. I recently tried to deploy Apache Tika
> with
> > maven-deploy-plugin:3.1.2.
> > I'm having a problem with deploying a new module we just added.
> >
> > Our repo is here: https://github.com/apache/tika
> >
> > I see the usual download/upload pattern, but then after the final
> download
> > of tika-grpc/metadata.xml, it looks like it is trying to download the
> > metadata for xmlbeans?!
> >
> > What am I doing wrong?
> >
> > Thank you!
> >
> > Expected pattern:
> >
> > [INFO] [INFO] --- deploy:3.1.2:deploy (default-deploy) @ tika-grpc ---
> > [INFO] Uploading to apache.releases.https:
> >
> >
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2.pom
> > [INFO] Progress (1): 16 kB
> > [INFO]
> > [INFO] Uploaded to apache.releases.https:
> >
> >
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2.pom
> > (16 kB at 9.0 kB/s)
> > [INFO] Uploading to apache.releases.https:
> >
> >
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2.jar
> > [INFO] Uploading to apache.releases.https:
> >
> >
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2-sources.jar
> > [INFO] Uploading to apache.releases.https:
> >
> >
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2.pom.asc
> > [INFO] Uploading to apache.releases.https:
> >
> >
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2.jar.asc
> > [INFO] Uploading to apache.releases.https:
> >
> >
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2-sources.jar.asc
> > 
> >
> > [INFO] Uploaded to apache.releases.https:
> >
> >
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2.jar.asc
> > (833 B at 1.2 kB/s)
> > [INFO] Uploaded to apache.releases.https:
> >
> >
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2.pom.asc
> > (833 B at 1.2 kB/s)
> > [INFO] Uploaded to apache.releases.https:
> >
> >
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2-sources.jar.asc
> > (833 B at 1.2 kB/s)
> > 
> >
> > [INFO] Uploaded to apache.releases.https:
> >
> >
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2-sources.jar
> > (82 kB at 53 kB/s)
> >
> > 
> >
> > [INFO] Uploaded to apache.releases.https:
> >
> >
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2.jar
> > (72 MB at 6.2 MB/s)
> > [INFO] Downloading from apache.releases.https:
> >
> >
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/maven-metadata.xml
> > *[INFO] Downloading from apache.releases.https:
> >
> >
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/xmlbeans/maven-metadata.xml
> > <
> >
> https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/xmlbeans/maven-metadata.xml
> > >*
> > [INFO] [WARNING] Could not transfer metadata
> > org.apache.xmlbeans/maven-metadata.xml from/to apache.releases.https (
> > https://repository.apache.org/service/local/staging/deploy/maven2):
> status
> > code: 400, reason phrase: Bad Request (400)
> >
>

maven-deploy pulling extraneous dependency's metadata?!

[Tim Allison]

Hi All,
  I'm sure this is user error. I recently tried to deploy Apache Tika with
maven-deploy-plugin:3.1.2.
I'm having a problem with deploying a new module we just added.

Our repo is here: https://github.com/apache/tika

I see the usual download/upload pattern, but then after the final download
of tika-grpc/metadata.xml, it looks like it is trying to download the
metadata for xmlbeans?!

What am I doing wrong?

Thank you!

Expected pattern:

[INFO] [INFO] --- deploy:3.1.2:deploy (default-deploy) @ tika-grpc ---
[INFO] Uploading to apache.releases.https:
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2.pom
[INFO] Progress (1): 16 kB
[INFO]
[INFO] Uploaded to apache.releases.https:
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2.pom
(16 kB at 9.0 kB/s)
[INFO] Uploading to apache.releases.https:
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2.jar
[INFO] Uploading to apache.releases.https:
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2-sources.jar
[INFO] Uploading to apache.releases.https:
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2.pom.asc
[INFO] Uploading to apache.releases.https:
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2.jar.asc
[INFO] Uploading to apache.releases.https:
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2-sources.jar.asc


[INFO] Uploaded to apache.releases.https:
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2.jar.asc
(833 B at 1.2 kB/s)
[INFO] Uploaded to apache.releases.https:
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2.pom.asc
(833 B at 1.2 kB/s)
[INFO] Uploaded to apache.releases.https:
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2-sources.jar.asc
(833 B at 1.2 kB/s)


[INFO] Uploaded to apache.releases.https:
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2-sources.jar
(82 kB at 53 kB/s)



[INFO] Uploaded to apache.releases.https:
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/3.0.0-BETA2/tika-grpc-3.0.0-BETA2.jar
(72 MB at 6.2 MB/s)
[INFO] Downloading from apache.releases.https:
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/tika/tika-grpc/maven-metadata.xml
*[INFO] Downloading from apache.releases.https:
https://repository.apache.org/service/local/staging/deploy/maven2/org/apache/xmlbeans/maven-metadata.xml
*
[INFO] [WARNING] Could not transfer metadata
org.apache.xmlbeans/maven-metadata.xml from/to apache.releases.https (
https://repository.apache.org/service/local/staging/deploy/maven2): status
code: 400, reason phrase: Bad Request (400)

surefire and system.exit

[Tim Allison]

All,

  I'm trying to upgrade the surefire plugin in Apache Tika, and I'm
running into "forked vm terminated without properly saying goodbye"
[0].

  Tika uses a bunch of dependencies we have no control over.  At one
point, we had a parser with a "feature" that called System.exit.  We
have code that defends against this kind of thing by forking and
monitoring the forked process for early termination, and we'd like to
test this forking code.  Is there any way to test this with more
recent versions of the surefire plugin, or is there a recommended
workaround?

  Thank you.

        Best,

  Tim

[0] 
http://maven.apache.org/surefire/maven-surefire-plugin/faq.html#vm-termination

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

Need help: maven-javadoc-plugin: includeDependencySource: error: module not found on module source path

[Tim Neumann]

Hello everybody,

I'm struggling to get javadoc generation with includeDependencySource
working in my project.

When setting includeDependencySource to true in the pom and running mvn
clean install javadoc:aggregate or mvn clean install javadoc:javadoc

I get the following errors:

First: [ERROR] no reactor project: 

And a few lines later a BUILD FAILURE because the javadoc tool exited
with the following error:
Exit code: 1 -
/path/to/my/project/target/distro-javadoc-sources/--sources/module-info.java:10:
error: module not found on module source path

But the source of the dependency seems to be fetched and unpacked
correctly to
/path/to/my/project/target/distro-javadoc-sources/--sources/
The line (10) where the error is is the module definition of the single
in that project.

The generated javdoc options file contains only one module-source-path:
/path/to/my/project/target/site/apidocs/src which contains a single
empty folder named like the module of my project (not the dependency).

Did anyone have a similar problem before? Any ideas what to try?

If anyone wants to look at the whole pom or try to reproduce it, the
project is on github: https://github.com/fius/jvk in the folder project.
The only dependency of that project is also on github:
https://github.com/FIUS/ICGE2
For trying to get this to work I made some changes to both, which are
not merged yet. See these pull-requests:
https://github.com/FIUS/ICGE2/pull/186 and
https://github.com/FIUS/jvk/pull/71
For this testing I'm using version 2.3.5-Snapshot of the dependency and
just locally running mvn clean install in it instead of uploading it to
a maven repository.

Regards,
Tim

-- 
Tim Neumann (GPG-Key: B5BD 17C3 BD4A 7BA4)  
stv. Referent für IT Betreung
Studierendenvertretung Uni Stuttgart
https://stuvus.uni-stuttgart.de



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

Maven Artifact Resolver Ant Tasks - Transitive Dependency Versions

[Tim N]

I've noticed Maven Artifact Resolver Ant Tasks resolves artifacts
differently to both pure maven and Maven Ant Tasks.

For example, in one project I'm looking at, both pure maven and Maven Ant
Tasks resolves a jar to be "activation-1.1.1.jar", but Maven Artifact
Resolver Ant Tasks resolves to "activation-1.1.jar". The dependency tree
gives the following:
mvn dependency:tree -Dverbose -Dincludes=javax.activation:activation
Using Maven 2 dependency tree to get verbose output, which may be
inconsistent with actual Maven 3 resolution
 company:core:jar:1.0.0-SNAPSHOT
 \- company:model:jar:1.0.0-SNAPSHOT:compile
\- com.sun.mail:javax.mail:jar:1.5.6:compile
   \- javax.activation:activation:jar:1.1.1:compile (version managed
from 1.1)

I gather pure maven does the "version managed from 1.1" change that Maven
Artifact Resolver Ant Tasks isn't doing. Is there any way to get the same
behavior? Can you point me to the documentation on this behavior?

The same command above without "verbose":
mvn dependency:tree -Dincludes=javax.activation:activation
company:core:jar:1.0.0-SNAPSHOT
 \- company:model:jar:1.0.0-SNAPSHOT:compile
\- com.sun.mail:javax.mail:jar:1.5.6:compile
   \- javax.activation:activation:jar:1.1.1:compile

The pure maven command I used to download the JARs is:
mvn -U dependency:copy-dependencies -DoutputDirectory=lib-compile
-DincludeScope=compile

In some cases, the JAR is a minor version out and the project won't compile.

Maven Artifact Resolver Ant Tasks - Remote Repositories

[Tim N]

Does "Maven Artifact Resolver Ant Tasks" respect remote repositories
defined in the specified POM when resolving?

What about remote repositories the specified POM's parent?

Re: Maven Artifact Resolver Ant Tasks - resolve dependency path

[Tim N]

Figured it out...I used  inside 

Maven Ant Tasks to Maven Artifact Resolver Ant Tasks - Calling Maven From Ant

[Tim N]

Maven Ant Tasks had some support for calling Maven from Ant:
https://maven.apache.org/ant-tasks/examples/mvn.html.


Is there anything similar in Maven Artifact Resolver Ant Tasks or another
project?

Re: Maven Ant Tasks - Central 501 HTTPS Required

[Tim N]

> maven-ant-tasks have been deprecated in favor of Maven Artifact Resolver
Ant Tasks: https://maven.apache.org/resolver-ant-tasks/

Fantastic, I'll give that a go. Is it possible to add a link to that
project from https://maven.apache.org/ant-tasks/ ?

Maven Artifact Resolver Ant Tasks - resolve dependency path

[Tim N]

With Maven Ant Task (https://maven.apache.org/ant-tasks/), it was possible
to refer to a dependency on the file-system in ant with, for example,
${org.jacoco:org.jacoco.ant:jar}.

Is it possible to do the same with Maven Artifact Resolver Ant Tasks?

Maven Ant Tasks - Central 501 HTTPS Required

[Tim N]

Yes, I'm still using Ant and Ant Maven Tasks, which has now succumbed to
the "501 HTTPS Required" bug.

I tried a quick fix patch (
https://github.com/tntim96/maven-ant-tasks/commit/b5a89db590e54126164d9d50a5062a0cb4be056c),
but not only does the build fail, the resultant JAR still exhibits the
behaviour, I suppose because it's based on maven 2.2.1 which also doesn't
have the HTTPS fix.Upgrading maven versions appears to be non-trivial.

This tool has worked pretty well for me, so I guess I have a few questions
that didn't appear in the FAQ.

Why was it retired? Is there a better approach to calling the Maven from
Ant?

What is the recommended dependency approach in Ant?

Thanks. I would appreciate any help or tips.

Re: Using Maven 3 with non-standard repository layout (Ivy)

[Tim Astle]

Thanks Robert,

Digging around led me to this option as well:
https://github.com/remis-thoughts/ivy-maven-plugin

Doing this isn't ideal, but more of a necessary evil for a proof of concept.

Thanks!

Tim

On Thu, May 24, 2018 at 1:50 PM, Robert Scholte 
wrote:

> Maven 2 and Maven 3 both use the same structure for repositories ( which
> is called a maven2 repo. Yes the name is a bit confusing ).
> If you want Maven to work with a different kind of repository, e.g. ivy to
> maven2, you need to use a repository manager.
> The only one I am aware of that supports Ivy is Artifactory[1]
>
> thanks,
> Robert
>
> [1] https://www.jfrog.com/confluence/display/RTF/Working+with+Ivy
>
> On Thu, 24 May 2018 03:23:11 +0200, Tim Astle 
> wrote:
>
> I was wondering if anyone had any suggestions for working with a
>> non-standard repository layout?
>>
>> Basically, I have a Maven 3 project but I need to fetch a fetch artifacts
>> from an Ivy repository.
>> http://ant.apache.org/ivy/history/2.0.0/use/info.html
>>
>> Can Maven handle this directly?  If not, is there a way that I could put
>> up
>> an "anti-corruption" repository as a proxy between Maven and the Ivy
>> repository that could transform one layout into the other (and cache the
>> results).
>>
>> Any ideas are welcome.
>>
>> Tim
>>
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Using Maven 3 with non-standard repository layout (Ivy)

[Tim Astle]

I was wondering if anyone had any suggestions for working with a
non-standard repository layout?

Basically, I have a Maven 3 project but I need to fetch a fetch artifacts
from an Ivy repository.
http://ant.apache.org/ivy/history/2.0.0/use/info.html

Can Maven handle this directly?  If not, is there a way that I could put up
an "anti-corruption" repository as a proxy between Maven and the Ivy
repository that could transform one layout into the other (and cache the
results).

Any ideas are welcome.

Tim

RE: Avoid change folder permission when using maven site deploy plugin

[Tim Wu T]

Hi,

Sure, I use maven 3.0.4, the plugin is very normal, maven site plugin 3.4, the 
wagon I use is:


org.apache.maven.wagon
wagon-ssh-external
2.6



Log output:
19:17:48 [INFO] Executing command: /bin/sh -c ssh -i /home/hello/.ssh/id_rsa -o 
'BatchMode yes' abc.def.com 'cd "/proj/webdocs/hello /root/my-docs/my-project"; 
unzip -q -o "wagon9211309153059078952.zip"; rm -f 
"wagon9211309153059078952.zip"'
19:18:25 [INFO] 
19:18:25 [INFO] 
19:18:25 [INFO] Executing command: chmod -Rf g+w,a+rX 
/proj/webdocs/hello/root/my-docs/
19:18:25 [INFO] Executing command: /bin/sh -c ssh -i /home/ hello /.ssh/id_rsa 
-o 'BatchMode yes' abc.def.com 'chmod -Rf g+w,a+rX 
/proj/webdocs/hello/root/my-docs/'

It takes very very long time to change the permissions as this folder contains 
lots of site files.

Br,
Tim
-Original Message-
From: Karl Heinz Marbaise [mailto:khmarba...@gmx.de] 
Sent: 2016年2月3日 20:47
To: Maven Users List
Subject: Re: Avoid change folder permission when using maven site deploy plugin

On 2/3/16 8:13 PM, Tim Wu T wrote:
> Hi All,
>
>
> When we deploy the site to our Linux server, I found maven will 
> execute "chmod -Rf g+w,a+rX " in the log folder every time, and this 
> will takes very long time (Maybe 5-6 minutes)

Can show a little bit more of your log output and in particular which Maven 
version, which plugin do you use? How do you deploy the site ? How is Maven 
called in this case?

Kind regards
Karl Heinz Marbaise
>
> Is there any way to avoid this?
>
> Thanks very much.
>
> Br,
> Tim
>
>


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

Avoid change folder permission when using maven site deploy plugin

[Tim Wu T]

Hi All,


When we deploy the site to our Linux server, I found maven will execute "chmod 
-Rf g+w,a+rX
" in the log folder every time, and this will takes very long time (Maybe 5-6 
minutes)

Is there any way to avoid this?

Thanks very much.

Br,
Tim

classifier on test artifact

[Tim Williams]

Hi all,
Over on Blur we're trying to improve the way we build against the
various hadoop versions.  We currently change the projectVersion to
build the artifact and we'd like to use classifiers to achieve the
same thing (described here[1]).

By setting a "hadoopClassifier" inside the profile and using that
inside the classifier tag, I can get the desired behavior on the main
artifact (e.g. named blur-core-0.2.4-incubating-SNAPSHOT-hadoop2.jar -
where "hadoop2" is the profile).  The problem is that the test-jar
artifact doesn't include the profile name in it.  I've tried adding
the classifier to the execution element of the test-jar goal as well
with no luck.

Is there a way to achieve this?  I'll happily accept pointers to a doc
and read myself if you have such a link...

Thanks,
--tim

[1] - 
http://mail-archives.apache.org/mod_mbox/incubator-blur-dev/201411.mbox/%3CCAG_bHoyAE0EvtjPX8Dim7p5dey6CWNgw0c4OwuJ%2BCWu5Ff1S2A%40mail.gmail.com%3E

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

Re: [VOTE] Name our mascot: "Shotgun" vs "The Maven Owl"

[Tim Astle]

A - Shotgun

Tim

On 12/15/2014 6:39 AM, Stephen Connolly wrote:

After the run-off round, we are left with two names standing.

This second vote will be a straight and simple majority wins.

The vote will be open for at least 72 hours (with the potential of an
extension until I send a message saying that the polls are closed)

There will be no discussion in this thread, we have talked it all enough
already. If you want to discuss something, please use a different thread.

Vote:

[A]: Shotgun
[B]: The Maven Owl

Thank you very much for your time

-Stephen




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

RE: Surefire and testing plugin issue

[Tim Wu T]

Never used maven "testng" plugin to run the test case, maybe you mean the 
dependency is testng?

Surefire plugin could support different test engine, testng/junit3/junit4.

Br,
Tim

-Original Message-
From: Subramanian Olagappan [mailto:osu...@gmail.com] 
Sent: den 27 september 2014 17:08
To: users@maven.apache.org
Subject: Surefire and testing plugin issue

Hi,

I am using maven-surefire-plugin version 2.17 and testng plugin version
6.3.1 (jdk version is 1.7 ). Some of our tests are failing and in the 
testng-results.xml file it is reported as fail. The issue is "maven" is 
reporting the failed tests as "skipped" and the final build status is SUCCESS.

Has anyone faced this issue ? if so what is the soln.

I tried with "surefire-testng" plugin instead of "testng" plugin. With this 
change, maven is properly reporting the failed tests and the final build is 
reported as FAIL

What is the difference between testng and surefire-testng plugin , I don't see 
any mention in the surefire plugin page, so I am not sure if it is correct to 
use this plugin.

Any help is appreciated

Thanks,
Subbu

RE: Try to find 2.0.11-SNAPSHOT-site_en.xml

[Tim Wu T]

I send this post two days ago, just received it :)

The problem already been solved, I created an empty site in the parent pom.xml 
and deploy it.

Br,
Tim

-Original Message-
From: Tim Wu T [mailto:tim.t...@ericsson.com] 
Sent: den 14 maj 2014 20:48
To: Maven Users List
Subject: Try to find 2.0.11-SNAPSHOT-site_en.xml

Hi there,

I met a tricky question, I just transfer from nexus to artifactory, and I met 
this problem when I build our project:

It show me missing this file: in artifactory, 2.0.11-SNAPSHOT-site_en.xml, then 
report a error, is true, we don't have this site file, why I have to keep a 
site descriptor file?

Do you met this problem before?

Thanks in advance.

Br,
Tim

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

Try to find 2.0.11-SNAPSHOT-site_en.xml

[Tim Wu T]

Hi there,

I met a tricky question, I just transfer from nexus to artifactory, and I met 
this problem when I build our project:

It show me missing this file: in artifactory, 2.0.11-SNAPSHOT-site_en.xml, then 
report a error, is true, we don't have this site file, why I have to keep a 
site descriptor file?

Do you met this problem before?

Thanks in advance.

Br,
Tim

RE: Maven sure fire plugin npe problem.

[Tim Wu T]

Hi Stephen,

Thanks for your info, your solution works for me :)

Br,
Tim

-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] 
Sent: den 27 april 2014 11:41
To: Maven Users List
Subject: Re: Maven sure fire plugin npe problem.

You signup for an account on xircles.codehaus.org... Effing jira templating 
does not make it easy to put that notice on the generic login screen so it is 
hard for people to guess... If you go to jira.codehaus.org you can see the not 
to use xircles... But sadly nowhere else :-(

The curse of the spammers forcing a non-jira signup process on the RoW

On Saturday, 26 April 2014, Tim Wu T  wrote:

> Not sure if anyone could show me how to create a TR for this, I don't 
> have a JIRA account.
>
> Br,
> Tim
>
> -Original Message-
> From: Tim Wu T [mailto:tim.t...@ericsson.com ]
> Sent: den 26 april 2014 22:53
> To: Maven Users List
> Subject: RE: Maven sure fire plugin npe problem.
>
> Hi,
>
> After detail investigation, I can prove this is a bug of maven 
> surefire plugin, after version 2.12. That means from 2.12~2.17 it met 
> the same problem.
>
> The problem will happen in a special condition, you don't met any 
> error during the test case execution time, however, you set the result 
> to fail during IInvokedMethodListener#afterInovation, such as 
> result.setStatus(Fail),
>
> Then maven surefire plugin will run ITestListener#onTestFailure method 
> twice and throw a Null pointer exception.
>
> Currently, I rollback our plugin version to 2.12 to avoid this type of 
> problem.
>
> Br,
> Tim
> -Original Message-
> From: kristian.rosenv...@zenior.no 
> [mailto:kristian.rosenv...@zenior.no]
> On Behalf Of Kristian Rosenvold
> Sent: den 25 april 2014 07:42
> To: Maven Users List
> Subject: Re: Maven sure fire plugin npe problem.
>
> It would appear that testng is not reporting the throwable that is 
> cause of the failure. You might want to try a few different testNG 
> versions to see if this is a recently introduced regression.
>
> Surefire should probably not NPE on this, but gaining some insight 
> into the root cause is probably a good thing (tm).
>
> Kristian
>
>
>
> 2014-04-24 21:57 GMT+02:00 Tim Wu T :
>
> > Hi everyone,
> >
> > I am not sure if some of you met this problem before, we have some 
> > smoke test in Jenkins sever, which will run some test case through 
> > maven sure fire plugin, version is 2.17
> >
> > But it will always throw an exception like this:
> > java.lang.NullPointerException
> >  at
> >
> org.apache.maven.surefire.report.SmartStackTraceParser.(SmartSta
> ckTraceParser.java:60)
> >  at
> >
> org.apache.maven.surefire.report.PojoStackTraceWriter.smartTrimmedStac
> kTrace(PojoStackTraceWriter.java:60)
> >  at
> >
> org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunL
> istener.java:328)
> >  at
> >
> org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunL
> istener.java:312)
> >  at
> >
> org.apache.maven.surefire.booter.ForkingRunListener.toString(ForkingRu
> nListener.java:258)
> >  at
> >
> org.apache.maven.surefire.booter.ForkingRunListener.testFailed(Forking
> RunListener.java:137)
> >  at
> >
> org.apache.maven.surefire.testng.TestNGReporter.onTestFailure(TestNGRe
> porter.java:105)
> >  at org.testng.internal.Invoker.runTestListeners(Invoker.java:1901)
> >  at org.testng.internal.Invoker.runTestListeners(Invoker.java:1885)
> >  at org.testng.internal.Invoker.invokeMethod(Invoker.java:788)
> >  at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907)
> >  at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237)
> >  at
> >
> org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorke
> r.java:127)
> >  at
> org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
> >  at org.testng.TestRunner.privateRun(TestRunner.java:767)
> >  at org.testng.TestRunner.run(TestRunner.java:617)
> >  at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
> >  at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
> >  at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
> >  at org.testng.SuiteRunner.run(SuiteRunner.java:240)
> >  at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:51)
> >  at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:85)
> >  at org.testng.TestNG.runSuitesSequentially(TestNG.java:1197)
> >  at org.testng.TestNG.runSuitesLocally(TestNG.java:1122)
> >  at org.testng.TestNG.run(TestNG.java:1030)
> >  at
> > org.apach



--
Sent from my phone

RE: Maven sure fire plugin npe problem.

[Tim Wu T]

Not sure if anyone could show me how to create a TR for this, I don't have a 
JIRA account.

Br,
Tim

-Original Message-
From: Tim Wu T [mailto:tim.t...@ericsson.com] 
Sent: den 26 april 2014 22:53
To: Maven Users List
Subject: RE: Maven sure fire plugin npe problem.

Hi,

After detail investigation, I can prove this is a bug of maven surefire plugin, 
after version 2.12. That means from 2.12~2.17 it met the same problem.

The problem will happen in a special condition, you don't met any error during 
the test case execution time, however, you set the result to fail during 
IInvokedMethodListener#afterInovation, such as result.setStatus(Fail),

Then maven surefire plugin will run ITestListener#onTestFailure method twice 
and throw a Null pointer exception.

Currently, I rollback our plugin version to 2.12 to avoid this type of problem.

Br,
Tim
-Original Message-
From: kristian.rosenv...@zenior.no [mailto:kristian.rosenv...@zenior.no] On 
Behalf Of Kristian Rosenvold
Sent: den 25 april 2014 07:42
To: Maven Users List
Subject: Re: Maven sure fire plugin npe problem.

It would appear that testng is not reporting the throwable that is cause of the 
failure. You might want to try a few different testNG versions to see if this 
is a recently introduced regression.

Surefire should probably not NPE on this, but gaining some insight into the 
root cause is probably a good thing (tm).

Kristian



2014-04-24 21:57 GMT+02:00 Tim Wu T :

> Hi everyone,
>
> I am not sure if some of you met this problem before, we have some 
> smoke test in Jenkins sever, which will run some test case through 
> maven sure fire plugin, version is 2.17
>
> But it will always throw an exception like this:
> java.lang.NullPointerException
>  at
> org.apache.maven.surefire.report.SmartStackTraceParser.(SmartStackTraceParser.java:60)
>  at
> org.apache.maven.surefire.report.PojoStackTraceWriter.smartTrimmedStackTrace(PojoStackTraceWriter.java:60)
>  at
> org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunListener.java:328)
>  at
> org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunListener.java:312)
>  at
> org.apache.maven.surefire.booter.ForkingRunListener.toString(ForkingRunListener.java:258)
>  at
> org.apache.maven.surefire.booter.ForkingRunListener.testFailed(ForkingRunListener.java:137)
>  at
> org.apache.maven.surefire.testng.TestNGReporter.onTestFailure(TestNGReporter.java:105)
>  at org.testng.internal.Invoker.runTestListeners(Invoker.java:1901)
>  at org.testng.internal.Invoker.runTestListeners(Invoker.java:1885)
>  at org.testng.internal.Invoker.invokeMethod(Invoker.java:788)
>  at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907)
>  at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237)
>  at
> org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
>  at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
>  at org.testng.TestRunner.privateRun(TestRunner.java:767)
>  at org.testng.TestRunner.run(TestRunner.java:617)
>  at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
>  at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
>  at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
>  at org.testng.SuiteRunner.run(SuiteRunner.java:240)
>  at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:51)
>  at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:85)
>  at org.testng.TestNG.runSuitesSequentially(TestNG.java:1197)
>  at org.testng.TestNG.runSuitesLocally(TestNG.java:1122)
>  at org.testng.TestNG.run(TestNG.java:1030)
>  at
> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:293)
>  at
> org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:84)
>  at
> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:91)
>  at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
>  at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
>  at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:1
> 03)
>
>
>
> I try to google something, but I don't get any good feedback.
>
> Thanks in advance.
>
> Br,
> Tim
>

-
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 sure fire plugin npe problem.

[Tim Wu T]

Hi,

After detail investigation, I can prove this is a bug of maven surefire plugin, 
after version 2.12. That means from 2.12~2.17 it met the same problem.

The problem will happen in a special condition, you don't met any error during 
the test case execution time, however, you set the result to fail during 
IInvokedMethodListener#afterInovation, such as result.setStatus(Fail),

Then maven surefire plugin will run ITestListener#onTestFailure method twice 
and throw a Null pointer exception.

Currently, I rollback our plugin version to 2.12 to avoid this type of problem.

Br,
Tim
-Original Message-
From: kristian.rosenv...@zenior.no [mailto:kristian.rosenv...@zenior.no] On 
Behalf Of Kristian Rosenvold
Sent: den 25 april 2014 07:42
To: Maven Users List
Subject: Re: Maven sure fire plugin npe problem.

It would appear that testng is not reporting the throwable that is cause of the 
failure. You might want to try a few different testNG versions to see if this 
is a recently introduced regression.

Surefire should probably not NPE on this, but gaining some insight into the 
root cause is probably a good thing (tm).

Kristian



2014-04-24 21:57 GMT+02:00 Tim Wu T :

> Hi everyone,
>
> I am not sure if some of you met this problem before, we have some 
> smoke test in Jenkins sever, which will run some test case through 
> maven sure fire plugin, version is 2.17
>
> But it will always throw an exception like this:
> java.lang.NullPointerException
>  at
> org.apache.maven.surefire.report.SmartStackTraceParser.(SmartStackTraceParser.java:60)
>  at
> org.apache.maven.surefire.report.PojoStackTraceWriter.smartTrimmedStackTrace(PojoStackTraceWriter.java:60)
>  at
> org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunListener.java:328)
>  at
> org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunListener.java:312)
>  at
> org.apache.maven.surefire.booter.ForkingRunListener.toString(ForkingRunListener.java:258)
>  at
> org.apache.maven.surefire.booter.ForkingRunListener.testFailed(ForkingRunListener.java:137)
>  at
> org.apache.maven.surefire.testng.TestNGReporter.onTestFailure(TestNGReporter.java:105)
>  at org.testng.internal.Invoker.runTestListeners(Invoker.java:1901)
>  at org.testng.internal.Invoker.runTestListeners(Invoker.java:1885)
>  at org.testng.internal.Invoker.invokeMethod(Invoker.java:788)
>  at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907)
>  at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237)
>  at
> org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
>  at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
>  at org.testng.TestRunner.privateRun(TestRunner.java:767)
>  at org.testng.TestRunner.run(TestRunner.java:617)
>  at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
>  at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
>  at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
>  at org.testng.SuiteRunner.run(SuiteRunner.java:240)
>  at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:51)
>  at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:85)
>  at org.testng.TestNG.runSuitesSequentially(TestNG.java:1197)
>  at org.testng.TestNG.runSuitesLocally(TestNG.java:1122)
>  at org.testng.TestNG.run(TestNG.java:1030)
>  at
> org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:293)
>  at
> org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:84)
>  at
> org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:91)
>  at
> org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
>  at
> org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
>  at
> org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:1
> 03)
>
>
>
> I try to google something, but I don't get any good feedback.
>
> Thanks in advance.
>
> Br,
> Tim
>

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

Maven sure fire plugin npe problem.

[Tim Wu T]

Hi everyone,

I am not sure if some of you met this problem before, we have some smoke test 
in Jenkins sever, which will run some test case through maven sure fire plugin, 
version is 2.17

But it will always throw an exception like this:
java.lang.NullPointerException
 at 
org.apache.maven.surefire.report.SmartStackTraceParser.(SmartStackTraceParser.java:60)
 at 
org.apache.maven.surefire.report.PojoStackTraceWriter.smartTrimmedStackTrace(PojoStackTraceWriter.java:60)
 at 
org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunListener.java:328)
 at 
org.apache.maven.surefire.booter.ForkingRunListener.encode(ForkingRunListener.java:312)
 at 
org.apache.maven.surefire.booter.ForkingRunListener.toString(ForkingRunListener.java:258)
 at 
org.apache.maven.surefire.booter.ForkingRunListener.testFailed(ForkingRunListener.java:137)
 at 
org.apache.maven.surefire.testng.TestNGReporter.onTestFailure(TestNGReporter.java:105)
 at org.testng.internal.Invoker.runTestListeners(Invoker.java:1901)
 at org.testng.internal.Invoker.runTestListeners(Invoker.java:1885)
 at org.testng.internal.Invoker.invokeMethod(Invoker.java:788)
 at org.testng.internal.Invoker.invokeTestMethod(Invoker.java:907)
 at org.testng.internal.Invoker.invokeTestMethods(Invoker.java:1237)
 at 
org.testng.internal.TestMethodWorker.invokeTestMethods(TestMethodWorker.java:127)
 at org.testng.internal.TestMethodWorker.run(TestMethodWorker.java:111)
 at org.testng.TestRunner.privateRun(TestRunner.java:767)
 at org.testng.TestRunner.run(TestRunner.java:617)
 at org.testng.SuiteRunner.runTest(SuiteRunner.java:334)
 at org.testng.SuiteRunner.runSequentially(SuiteRunner.java:329)
 at org.testng.SuiteRunner.privateRun(SuiteRunner.java:291)
 at org.testng.SuiteRunner.run(SuiteRunner.java:240)
 at org.testng.SuiteRunnerWorker.runSuite(SuiteRunnerWorker.java:51)
 at org.testng.SuiteRunnerWorker.run(SuiteRunnerWorker.java:85)
 at org.testng.TestNG.runSuitesSequentially(TestNG.java:1197)
 at org.testng.TestNG.runSuitesLocally(TestNG.java:1122)
 at org.testng.TestNG.run(TestNG.java:1030)
 at 
org.apache.maven.surefire.testng.TestNGExecutor.run(TestNGExecutor.java:293)
 at 
org.apache.maven.surefire.testng.TestNGXmlTestSuite.execute(TestNGXmlTestSuite.java:84)
 at 
org.apache.maven.surefire.testng.TestNGProvider.invoke(TestNGProvider.java:91)
 at 
org.apache.maven.surefire.booter.ForkedBooter.invokeProviderInSameClassLoader(ForkedBooter.java:200)
 at 
org.apache.maven.surefire.booter.ForkedBooter.runSuitesInProcess(ForkedBooter.java:153)
 at 
org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:103)



I try to google something, but I don't get any good feedback.

Thanks in advance.

Br,
Tim

RE: Rule for maven plugin inheritance

[Tim Wu T]

Hi Wayne,

Thanks, will try today.

Br,
Tim

-Original Message-
From: Wayne Fay [mailto:wayne...@gmail.com] 
Sent: den 24 februari 2014 23:11
To: Maven Users List
Subject: Re: Rule for maven plugin inheritance

> At first, I define two maven java doc plugin inside the reporting tag 
> and used to generate different type of javadoc, one for standard javadoc and 
> for customize one.

FYI: I don't use much of the reporting functionality in Maven, just the basics.

> Later, I want to move those two javadoc plug in into the parent pom, I 
> don't use the pluginElement, just want all of our sub project could use it 
> directly.

Generally speaking, you don't include a plugin twice in your pom, you should 
include it once and use  or  to provide different 
configurations for the various executions you require. Read more online:
https://maven.apache.org/plugins/maven-site-plugin/examples/configuring-reports.html

Wayne

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

Rule for maven plugin inheritance

[Tim Wu T]

Hi there,

Met an interesting question recently about plugin inheritance and hope you 
could give me some feedback :)

At first, I define two maven java doc plugin inside the reporting tag and used 
to generate different type of javadoc, one for standard javadoc and for 
customize one.

Later, I want to move those two javadoc plug in into the parent pom, I don't 
use the pluginElement, just want all of our sub project could use it directly.

However, I find only one of them will works, not both like I did them in sub 
projects.

Is there any special rule about this?

Br,
Tim

Re: New logo?

[Tim Pizey]

That looks really nice (though I do have problems with any North
American Indian references).

cheers
TimP

On 14 January 2014 12:08, Stephen Connolly
 wrote:
> Putting maven-20 in context, you get:
>
> http://people.apache.org/~stephenc/maven-logo-contest/maven-20-in-context.png
>
>
> On 14 January 2014 10:37, Stephen Connolly
> wrote:
>
>> My wife had a suggestion... why not make the M in maven out of two tee
>> pees... linking in with the Apache theme...
>>
>> So I present
>>
>> maven-19:
>> https://cwiki.apache.org/confluence/download/attachments/38569278/maven-19.png?version=1&modificationDate=1389695638903&api=v2
>>
>> and finding a use for the feather
>>
>> maven-20:
>> https://cwiki.apache.org/confluence/download/attachments/38569278/maven-20.png?version=1&modificationDate=1389695654233&api=v2
>>
>>
>> On 14 January 2014 10:35, Stephen Connolly <
>> stephen.alan.conno...@gmail.com> wrote:
>>
>>> As a homage to Roy's wife, may I present
>>>
>>> maven-18:
>>> https://cwiki.apache.org/confluence/download/attachments/38569278/maven-18.png?version=1&modificationDate=1389695623134&api=v2
>>>
>>>
>>> On 13 January 2014 15:36, Lyons, Roy  wrote:
>>>
>>>> I asked my wife on the drive to the train today what animal she thinks
>>>> fits Maven.  Her response made me chuckle.
>>>>
>>>> Without hesitation, she said "Honey Badger"
>>>>
>>>> When I asked why, she said that Honey Badgers are part of nature and
>>>> generally do their thing nicely -- but if you piss it off, things will
>>>> get
>>>> really really bad...  She said she had the same experience with Maven.
>>>>  It
>>>> works nicely, but if you try to do something really non-standard, you
>>>> will
>>>> feel its wrath :)
>>>>
>>>> Heh.
>>>>
>>>> Anyhow, I thought it was funny enough to share - not really a serious
>>>> consideration to make a Honey Badger our mascot.
>>>>
>>>> On 1/10/14 1:20 AM, "Kristian Rosenvold" 
>>>> wrote:
>>>>
>>>> >I think the association-work around what maven /is/ is a great way to
>>>> >approach a logo contest elsewhere. I have worked with some great graphic
>>>> >designers in my time, and the kind input the good ones want are
>>>> typically
>>>> >related around your thoughts/feelings around the product rather than
>>>> which
>>>> >particular animal you prefer, which is a bit of a secondary kind of
>>>> input
>>>> >along with all different kinds of other constraints/ideas (the boss
>>>> >prefers
>>>> >blue).
>>>> >
>>>> >When I first encountered maven I had come to the realization that all my
>>>> >ant projects were basically the same, and that there was no reason for
>>>> >customizing
>>>> >what was basically a standard process. So maven gives me associations
>>>> to a
>>>> >mass-production line at a factory, rather than a tailor making
>>>> individual
>>>> >processes. Furthermore, the lifecycle amplifies the idea of a
>>>> >conveyor-belt
>>>> >mass-production line; all parts move through the same conveyor belt
>>>> >process, stopping at
>>>> >individual stages to get work done. I would almost be willing to think
>>>> of
>>>> >a
>>>> >waterfall (Uh-oh...)
>>>> >
>>>> >So it would appear to me that I'm not thinking of an animal at all !
>>>> >
>>>> >Kristian
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >
>>>> >2014/1/9 Mark H. Wood 
>>>> >
>>>> >> On Thu, Jan 09, 2014 at 09:32:54AM -0600, Curtis Rueden wrote:
>>>> >> > All of the logos are OK, but none of them really symbolize anything
>>>> in
>>>> >> > particular about Maven. IMO the best logos encapsulate the purpose
>>>> of
>>>> >>the
>>>> >> > project somehow, either overtly, covertly or both.
>>>> >>
>>>> >> Good point.  I was associating with the name "Maven", looking for a
>>>> >> symbol of in-depth understanding of a specialized field.
>>>> >>
>>>> >> http://en.wiktionary.org/wiki/maven
>>>> >>
>>>> >> So, what does Maven do?  It passes unique source and object code
>>>> >> inputs through a standardized process, guided by an expression of the
>>>> >> relationships among those inputs, to assemble a well-specified
>>>> >> configuration of runnable code.  What does that look like?
>>>> >>
>>>> >> --
>>>> >> Mark H. Wood, Lead System Programmer   mw...@iupui.edu
>>>> >> Machines should not be friendly.  Machines should be obedient.
>>>> >>
>>>>
>>>>
>>>> -
>>>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>>>> For additional commands, e-mail: users-h...@maven.apache.org
>>>>
>>>>
>>>
>>



-- 
Tim Pizey
http://pizey.net/~timp

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

Re: New logo?

[Tim Pizey]

ar
>> > >>we
>> > >> can look into getting the approval to use the image.
>> > >>
>> > >> If we can get a few community contributions then I will start a vote
>> > >> run-off... I don't want to have a run-off with only my contributions
>> as
>> > >>I
>> > >> just don't think that is the spirit of the community that we are (but
>> > >>hey
>> > >> if nobody else is willing to try their hand, perhaps we will be
>> reduced
>> > >>to
>> > >> a run-off of my creations)
>> > >>
>> > >>
>> > >>
>> > >> On 21 December 2013 12:25, Stephen Connolly <
>> > >> stephen.alan.conno...@gmail.com> wrote:
>> > >>
>> > >>> Having thought about it overnight... if people really want to go
>> with a
>> > >>> non-stylised raven we can always ask for permission:
>> > >>>
>> > >>> http://people.apache.org/~stephenc/maven-logo-contest/maven-9.png
>> > >>>
>> > >>> OTOH here is a different stylised version
>> > >>>
>> > >>> http://people.apache.org/~stephenc/maven-logo-contest/maven-10.png
>> > >>>
>> > >>> Finally, here is a raven totem
>> > >>>
>> > >>> http://people.apache.org/~stephenc/maven-logo-contest/maven-11.png
>> > >>>
>> > >>> I think this last one could be put in a forest with sky background...
>> > >>> just haven't had time to do it
>> > >>>
>> > >>>
>> > >>> On 20 December 2013 22:26, Stephen Connolly <
>> > >>> stephen.alan.conno...@gmail.com> wrote:
>> > >>>
>> > >>>> I think we can't go with the raven
>> > >>>>
>> > >>>> http://www.prweb.com/releases/2012/3/prweb9334175.htm
>> > >>>>
>> > >>>> Given that a different non-competing user of the name is using a
>> raven
>> > >>>> in their logo
>> > >>>>
>> > >>>> On Friday, 20 December 2013, Manfred Moser wrote:
>> > >>>>
>> > >>>>> >
>> > >>>>> > On Dec 20, 2013, at 1:01 PM, Manfred Moser
>> > >>>>>
>> > >>>>> > wrote:
>> > >>>>> >
>> > >>>>> >> I would move the Raven closer to the word Maven but otherwise
>> this
>> > >>>>> looks
>> > >>>>> >> good imho. Of course I am not sure if everyone would recognize
>> it
>> > >>>>>as
>> > >>>>> a
>> > >>>>> >> raven ..
>> > >>>>> >
>> > >>>>> > That¹s my problemŠ.  doesn¹t look like a raven to me at all.
>> > >>>>> >
>> > >>>>> > When I first looked at it, I guess the ³mouth + tough² part
>> seemed
>> > >>>>>to
>> > >>>>> look
>> > >>>>> > more like the Seattle SeaHawks logo stuck on a boot with a weird
>> > >>>>> swirly
>> > >>>>> > thing at the ankle.
>> > >>>>> >
>> > >>>>> > In other words, a little to ³abstract² for me.   :-)
>> > >>>>>
>> > >>>>> Fair enough. I guess living in the pacific northwest I am exposed
>> to
>> > >>>>> these
>> > >>>>> depictions a lot so I can tell. But globally we might have to make
>> > >>>>>it a
>> > >>>>> bit clearer. Good input ;-)
>> > >>>>>
>> > >>>>> manfred
>> > >>>>>
>> > >>>>>
>> -
>> > >>>>> To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org
>> > >>>>> For additional commands, e-mail: dev-h...@maven.apache.org
>> > >>>>>
>> > >>>>>
>> > >>>>
>> > >>>> --
>> > >>>> Sent from my phone
>> > >>>>
>> > >>>
>> > >>>
>> > >>
>> >
>> >
>>
>
>
>
> --
> Baptiste  MATHUS - http://batmat.net
> Sauvez un arbre,
> Mangez un castor !



-- 
Tim Pizey
http://pizey.net/~timp

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

Re: New logo?

[Tim Pizey]

Great to see them all in one place.

I like maven-12

my 2p
timp




On 3 January 2014 15:12, Stephen Connolly
 wrote:
> I have created a wiki page to track the logo contest...
>
> https://cwiki.apache.org/confluence/display/MAVEN/Logo+contest
>
>
> On 2 January 2014 21:44, Lyons, Roy  wrote:
>
>> Lettering eh, how about comic sans?  :)
>>
>>
>>
>> ...
>>
>>
>>
>> J/K btw
>>
>> Jason & company might let you re-use the letting from
>> http://blog.sonatype.com/wp-content/uploads/2010/03/maven1.jpg if you
>> wanted something a little edgier and crisp.
>>
>>
>> On 1/2/14 3:36 PM, "Stephen Connolly" 
>> wrote:
>>
>> >Well our current "icon" is somebody's arse behind a laptop... Which with a
>> >cleaner site looks a tad odd
>> >
>> >With the old header bar it was fine though
>> >
>> >I have no issue changing the font or colouring, but I think an actual icon
>> >or emblem is something good to have.
>> >
>> >There was some effort to pick a new font, and I would be happy to see
>> >examples with a different font... My typographic skills are not near the
>> >level of my poor sketching skills, so I have been hoping somebody else
>> >could tackle the lettering
>> >
>> >
>> >On Thursday, 2 January 2014, Mark Derricutt wrote:
>> >
>> >> Is it me or are a lot of these purely changing the icon, not the "logo".
>> >>
>> >> i.e. is the "logo" inclusive of the "mAven" name ( side question - why
>> >>is
>> >> the A always a different colour, historic Ant reference? )
>> >>
>> >> On 3 Jan 2014, at 2:18, Stephen Connolly wrote:
>> >>
>> >> > As 9 is particularly problematic I have sketched -14 which is not a
>> >> direct
>> >> > copy of a silhouette. This still has the issue w.r.t. other marks
>> >>called
>> >> > maven using a silhouetted raven...
>> >>
>> >
>> >
>> >--
>> >Sent from my phone
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>>



-- 
Tim Pizey
http://pizey.net/~timp

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

Re: Release Plugin doesn't commit poms correctly anymore

[Tim Kettler]

Am 20.09.2013 10:46, schrieb Tim Kettler:

Am 20.09.2013 10:10, schrieb Christian Grobmeier:

Hi folks,

I have used the release plugin fro a millions of releases. And suddenly
it stopped working as expected.

I am doing:

$> mvn release:prepare
$> mvn release:perform

And usually I see commits of the kind:

[maven-release-plugin] prepare release v3.2.2

--8<---

Previously i have used release plugin version 2.3.1, but when the error
appeared I upgraded to 2.4.

--- maven-release-plugin:2.4:prepare (default-cli) @ webapp ---
[INFO] Verifying that there are no local modifications...
[INFO]   ignoring changes on: **/pom.xml.backup, **/release.properties,
**/pom.xml.branch, **/pom.xml.next, **/pom.xml.releaseBackup,
**/pom.xml.tag
[INFO] Executing: /bin/sh -c cd /Users/cg/project.git/webapp && git
status --porcelain
[INFO] Working directory: /Users/cg/project.git/webapp

--8<---

Any ideas are much welcome. It doesn't feel well that way.


You probably hit MRELEASE-812 [1]. The release-plugin-2.4 is borked when
using git and releasing not from the repository root.



What you should use is release-plugin-2.4.1. That reverts the scm lib 
back to a working version: http://jira.codehaus.org/browse/MRELEASE-830




Thanks!

Christian


-Tim

[1] http://jira.codehaus.org/browse/MRELEASE-812




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

Re: Release Plugin doesn't commit poms correctly anymore

[Tim Kettler]

Am 20.09.2013 10:10, schrieb Christian Grobmeier:

Hi folks,

I have used the release plugin fro a millions of releases. And suddenly
it stopped working as expected.

I am doing:

$> mvn release:prepare
$> mvn release:perform

And usually I see commits of the kind:

[maven-release-plugin] prepare release v3.2.2

--8<---

Previously i have used release plugin version 2.3.1, but when the error
appeared I upgraded to 2.4.

--- maven-release-plugin:2.4:prepare (default-cli) @ webapp ---
[INFO] Verifying that there are no local modifications...
[INFO]   ignoring changes on: **/pom.xml.backup, **/release.properties,
**/pom.xml.branch, **/pom.xml.next, **/pom.xml.releaseBackup, **/pom.xml.tag
[INFO] Executing: /bin/sh -c cd /Users/cg/project.git/webapp && git
status --porcelain
[INFO] Working directory: /Users/cg/project.git/webapp

--8<---

Any ideas are much welcome. It doesn't feel well that way.


You probably hit MRELEASE-812 [1]. The release-plugin-2.4 is borked when 
using git and releasing not from the repository root.




Thanks!

Christian


-Tim

[1] http://jira.codehaus.org/browse/MRELEASE-812


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

RE: Maven Assembly plugin is not working when install

[Tim Wu T]

Looks like your bind works well.

The assembly was called when the package phase was arrived.

Br,
Tim

-Original Message-
From: Baptiste Mathus [mailto:bmat...@gmail.com] 
Sent: Monday, September 02, 2013 2:47 PM
To: Maven Users List
Subject: Re: Maven Assembly plugin is not working when install

What is actually "wrong"? Could you provide some details?
Le 2 sept. 2013 06:50, "禹航"  a écrit :

> hi there,
>i try to user maven-assembly plugin to generate a tar.gz.my pom is 
> like
> this:
> *
> 
> 
> org.apache.maven.plugins
> maven-assembly-plugin
> 
> tauras-master
> 
>
> src/main/assembly/assembly-offline.xml
> 
> 
> 
> 
> make-assembly
> package
> 
> single
> 
> 
> 
> 
> 
> *
>
> when i use assembly:single, it works well.
> but when i use install or package, the result is wrong the output of 
> the console:
>
> [INFO]
> [INFO] --- maven-clean-plugin:2.4.1:clean (default-clean) @ 
> tauras-master
> ---
> [INFO] Deleting E:\svn\taurus\tauras-master\target
> [INFO]
> [INFO] --- maven-resources-plugin:2.5:resources (default-resources) @ 
> tauras-master --- [debug] execute contextualize [INFO] Using 'UTF-8' 
> encoding to copy filtered resources.
> [INFO] Copying 1 resource
> [INFO] Copying 1 resource
> [INFO]
> [INFO] --- maven-compiler-plugin:2.5.1:compile (default-compile) @ 
> tauras-master --- [INFO] Compiling 5 source files to 
> E:\svn\taurus\tauras-master\target\classes
> [INFO]
> [INFO] --- maven-resources-plugin:2.5:testResources 
> (default-testResources) @ tauras-master --- [debug] execute 
> contextualize [INFO] Using 'UTF-8' encoding to copy filtered 
> resources.
> [INFO] skip non existing resourceDirectory 
> E:\svn\taurus\tauras-master\src\test\resources
> [INFO]
> [INFO] --- maven-compiler-plugin:2.5.1:testCompile 
> (default-testCompile) @ tauras-master --- [INFO] Not compiling test 
> sources [INFO] [INFO] --- maven-surefire-plugin:2.7.2:test 
> (default-test) @ tauras-master
> ---
> [INFO] Tests are skipped.
> [INFO]
> [INFO] --- maven-jar-plugin:2.4:jar (default-jar) @ tauras-master --- 
> [INFO] Building jar: 
> E:\svn\taurus\tauras-master\target\tauras-master.jar
> *missing
> [INFO] --- maven-assembly-plugin:2.2-beta-5:single (make-assembly) @ 
> **tauras-master --- [INFO] Reading assembly descriptor: 
> src/main/assembly/assembly-offline.xml
> missing*
> [INFO]
> [INFO] --- maven-install-plugin:2.3.1:install (default-install) @ 
> tauras-master ---
>
> Any comments for this?
>

RE: Maven assembly single goal not works.

[Tim Wu T]

Hi,

Really thanks for your suggestion.

More clear now :)

Just one small question, not so clear about this:
(which is needless with your configuration if you don't remove the executions 
part)

Thanks in advance.

Br,
Tim
-Original Message-
From: Roger Brechbühl [mailto:rotscher...@gmail.com] 
Sent: Wednesday, July 31, 2013 4:52 PM
To: Maven Users List
Subject: Re: Maven assembly single goal not works.

when calling assembly:single only, the package phase and all its attached 
plugins are not executed. Especially, the maven-jar-plugin is not executed, so 
no jar file is generated and attached. Hence the error message.

mvn package single:assembly (which is needless with your configuration if you 
don't remove the executions part)

Cheers,
Rotsch



2013/7/31 Tim Wu T 

> HI there,
>
> I try to use the assembly single goal to generate a jar with 
> dependencies, my config looks like this:
>  
>maven-assembly-plugin
>2.3
>
>   
>  
>
> org.testng.TestNG
>  
>   
>   
>
>  jar-with-dependencies
>   
>
>
>   
>  make-assembly 
>  package 
>  
> single
>  
>   
>
>  
>
> I can use the mvn clean install to generate jar with dependnecies 
> well, but if I want to try assembly:single, than it will show me 
> Cannot include project artifact: xx; it doesn't have an associated 
> file or directory.
>
> Any comments for this?
>
> Br,
> Tim
>

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

Maven assembly single goal not works.

[Tim Wu T]

HI there,

I try to use the assembly single goal to generate a jar with dependencies, my 
config looks like this:
 
   maven-assembly-plugin
   2.3
   
  
 

org.testng.TestNG
 
  
  
 
jar-with-dependencies
  
   
   
  
 make-assembly 
 package 
 
single
 
  
   
 

I can use the mvn clean install to generate jar with dependnecies well, but if 
I want to try assembly:single, than it will show me
Cannot include project artifact: xx; it doesn't have an associated file or 
directory.

Any comments for this?

Br,
Tim

RE: plugin for soapui

[Drury, Tim]

There is also a "mock" goal. 

The mock goal configuration is described here: 
http://www.soapui.org/Test-Automation/maven-2x.html#5-4-eviwaresoapuimock-settings

-Original Message-
From: Jorge Infante Osorio [mailto:jorg...@uci.cu] 
Sent: Wednesday, June 26, 2013 7:59 PM
To: 'Maven Users List'
Subject: RE: plugin for soapui

Yes I know:


eviware
maven-soapui-plugin
3.6.1


myTests

test

test



.



But it´s for Integration test during the tests. 
It doesn´t fix in my requirement.


Saludos,
Ing. Jorge Infante Osorio.
CDAE.
Fac. 5.
UCI.
"En un mundo perfecto las pizzas serían una comida saludable, las laptops se
cargarían desde una fuente de corriente inalámbrica y todos los JAR serían
bundles de OSGI "


-Mensaje original-
De: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] En nombre
de Anders Hammar
Enviado el: miércoles, 26 de junio de 2013 15:35
Para: Maven Users List
Asunto: Re: plugin for soapui

There is already a soapUI maven plugin. Talk to the soapUI people!

/Anders


On Wed, Jun 26, 2013 at 8:01 PM, Martin Gainty  wrote:

> Guys-
>
> we used SOAPUI  every day at the bank to test our web-services
>
> if we can get our hands on SOAPUI source we could create a plugin to 
> auto-launch 1)a configurable wsdl to
> 2) a configurable SOAP endpoint using
> 3)configurable SOAP Headers with
> 4)user-supplied SOAP-Body
>
> definite potential for a maven-plugin!
> Martin Gainty
> __
> Jogi és Bizalmassági kinyilatkoztatás/Verzicht und 
> Vertraulichkeitanmerkung/Note de déni et de confidentialité
>
>  Ez az
> üzenet bizalmas.  Ha nem ön az akinek szánva volt, akkor kérjük, hogy 
> jelentse azt nekünk vissza. Semmiféle továbbítása vagy másolatának 
> készítése nem megengedett.  Ez az üzenet csak ismeret cserét szolgál 
> és semmiféle jogi alkalmazhatósága sincs.  Mivel az electronikus 
> üzenetek könnyen megváltoztathatóak, ezért minket semmi felelöség nem 
> terhelhet ezen üzenet tartalma miatt.
>
> Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene 
> Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede 
> unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. 
> Diese Nachricht dient lediglich dem Austausch von Informationen und 
> entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten 
> Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt
uebernehmen.
> Ce message est confidentiel et peut être privilégié. Si vous n'êtes 
> pas le destinataire prévu, nous te demandons avec bonté que pour 
> satisfaire informez l'expéditeur. N'importe quelle diffusion non 
> autorisée ou la copie de ceci est interdite. Ce message sert à 
> l'information seulement et n'aura pas n'importe quel effet légalement 
> obligatoire. Étant donné que les email peuvent facilement être sujets 
> à la manipulation, nous ne pouvons accepter aucune responsabilité pour le
contenu fourni.
>
>
> > From: wayne...@gmail.com
> > Date: Wed, 26 Jun 2013 12:25:15 -0500
> > Subject: Re: plugin for soapui
> > To: users@maven.apache.org
> >
> > > My question is if I can do the same using maven? Generate the war 
> > > file
> of
> > > this mock web service using some maven plugin.
> >
> > I would ask the same question on the soapui list, to see if they 
> > have a Maven plugin that supports your use case.
> >
> > Wayne
> >
> > 
> > - 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

RE: How to curtomize the maven release plugin upload jars?

[Tim Wu T]

Hi Barrie,

Thanks.

Br,
Tim

-Original Message-
From: Barrie Treloar [mailto:baerr...@gmail.com] 
Sent: Tuesday, April 02, 2013 12:35 PM
To: Maven Users List
Subject: Re: How to curtomize the maven release plugin upload jars?

On 2 April 2013 13:53, Tim Wu T  wrote:

> Hi there,
>
> We met an issue recently and maybe you could provide some help for me.
>
> We have project name "A", and we have a branch called branchA except the
> mater branch for this project.
>
> In sometimes, we also want to release the branchA, but it will cause the
> confusion when it was upload the nexus, because the branch and the master
> share the same groupId and artifactId.
>
> Just curious how you solve this type of issue?
>
> Solution 1: Use the different artifactId will be easiest way.
>
> Solution 2: Update the pom.xml maven jar plugin to make it build a jar
> like this: A-branchA.jar. Later, when the release process finished, this
> jar will also be uploaded.


Your branch should be using a *different* version identifier than your
master.

See http://semver.org/

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

How to curtomize the maven release plugin upload jars?

[Tim Wu T]

Hi there,

We met an issue recently and maybe you could provide some help for me.

We have project name "A", and we have a branch called branchA except the mater 
branch for this project.

In sometimes, we also want to release the branchA, but it will cause the 
confusion when it was upload the nexus, because the branch and the master share 
the same groupId and artifactId.

Just curious how you solve this type of issue?

Solution 1: Use the different artifactId will be easiest way.

Solution 2: Update the pom.xml maven jar plugin to make it build a jar like 
this: A-branchA.jar. Later, when the release process finished, this jar will 
also be uploaded.

But I cannot prevent the A.jar upload, any advice?

Great thanks for your help.

Br,
Tim

Re: maven-source-plugin questions

[Tim Kettler]

Am 18.03.2013 06:56, schrieb Kevin Krumwiede:

Are the jars produced by maven-source-plugin intended primarily as a
reference for IDEs and other automated tools, as opposed to being
something you would actually build from?


They are intended primarily as a reference thing.


I ask because I have a project in which a non-Java source is used to
generate Java sources and non-Java resources.  This happens during the
generate-sources phase.  So when maven-sources-plugin runs, the
sources and resources have already been generated and they get
included in the -sources jar.

If the -sources jar is only intended as a reference, then I want to
exclude the generated sources and resources.  I found that I can
exclude the generated sources by binding maven-sources-plugin to the
validate phase, using the jar-no-fork goal, and setting
excludeResources to true.  Binding to the validate phase seems like a
hack, and I don't understand why the generated resources still end up
in the source jar if I don't use excludeResources.


There is a  config option [1] that should do what you want:

  
org.apache.maven.plugins
maven-source-plugin
2.2.1

  
attach-sources

  jar


  
**/exclude/*.java
second/exclude/*.png
...
  

  

  


On the other hand, if the -sources jar is meant to be something you
would build from, then I would want to exclude the generated sources
and resources but include the non-Java source from which they are
generated.  But the only way I know to do that is to add it as a
resource, which causes it to be included in the binary jar as well.

So... which is it, and how do I do it right?


You would use the assembly plugin to generate a full source distribution 
to build your project from.



Thanks,
K


-Tim

[1] 
http://maven.apache.org/plugins/maven-source-plugin/jar-no-fork-mojo.html


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

Re: Unpacking jars into target/classes

[Tim Kettler]

Am 02.03.2013 21:32, schrieb Joachim Durchholz:

Hi all,

I have two jars from an external source and need to merge their contents
into the target/classes tree until the process-classes phase.
I'm not sure what plugin(s) can be used to achieve this effect.


As wholeheartedly as I agree to all what was said about Maven being 
opinionated (in a good way) and that one is best advised to stick to the 
conventions, there are cases where you just can't... and in my 
experience maven is quit good at handling these edge cases.


For the problem at hand, have a look at the truezip-m-p over at the 
codehaus mojo project, it should provide what you want:


  
${project.basedir}/libs/lib1.jar
  

  

  
org.codehaus.mojo
truezip-maven-plugin
1.1

  
copy-lib1-classes

  copy

process-classes

  
${mylib1.archive}

  **/*


  META-INF/MANIFEST.MF


${project.build.outputDirectory}
  

  

  

  


Directory structure:
- external (directory tree that holds the externally-provided files)
   - libs
 - cubes.jar (class files)
 - cubes-resources.jar (nonclass files)
   - license etc. (other data, irrelevant to task at hand)
   (yeah I know the structure sucks, can't do anything about it)
- target (maven scratchpad)
   - classes (files for main artifact jar are collected here I think)

I need the files inside libs/cubes.jar and libs/cubes-resource.jar
unpacked and placed inside target/classes, preserving the in-jar
directory structure.

I want this to run in the process-classes, latest, because that's the
last pertinent phase that m2e will run.

What's the best (least-hassle) plugin that will do this?

Regards,
Jo


-Tim



P.S.: Please resist the temptation to tell me that I want the wrong
thing. I need help with solving a problem, I don't need a lecture.

-
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: Release:perform failing on git ...

[Tim Wu T]

At Jenkins maven release plugin:

There is an option called: Configure M2 Extra Build Steps

You can config your pre steps.

Br,
Tim



-Original Message-
From: Benson Margulies [mailto:bimargul...@gmail.com] 
Sent: Friday, March 08, 2013 9:53 AM
To: Maven Users List
Subject: Re: Release:perform failing on git ...

Actually, I know what's happening.

To talk to this repo, I need to use a custom ssh key.

At command level, I use a shell script:

git clone --config ssh.key=/users/benson/.ssh/id_basis_rsa "$@"

THe question is, how do I get the m-r-p to do this?


On Thu, Mar 7, 2013 at 8:49 PM, Tim Wu T  wrote:

> I think it should better for you to provide more stacktrace.
>
> [ERROR] The git-clone command failed. This message is too limited to find
> the root cause.
>
> Br,
> Tim
> -Original Message-
> From: Benson Margulies [mailto:bimargul...@gmail.com]
> Sent: Friday, March 08, 2013 9:47 AM
> To: Maven Users List
> Subject: Release:perform failing on git ...
>
> release plugin 2.3.2
>
> prepare does fine.
>
> perform fails with:
>
> [INFO] --- maven-release-plugin:2.3.2:perform (default-cli) @
> find-jug-dist-dir-maven-plugin ---
> [INFO] Checking out the project to perform the release ...
> [INFO] Executing: /bin/sh -c cd
> /Users/benson/x/find-jug-dist-dir-maven-plugin/target && git clone --branch
> find-jug-dist-dir-maven-plugin-1
> g...@github.com:basis-technology-corp/find-jug-dist-dir-maven-plugin.git
> /Users/benson/x/find-jug-dist-dir-maven-plugin/target/checkout
> [INFO] Working directory:
> /Users/benson/x/find-jug-dist-dir-maven-plugin/target
> [ERROR] The git-clone command failed.
>
> scm looks like:
>
> 
>   scm:git:g...@github.com:
> basis-technology-corp/find-jug-dist-dir-maven-plugin.git
>   scm:git:g...@github.com:
>
> basis-technology-corp/find-jug-dist-dir-maven-plugin.git
>   
> https://github.com/basis-technology-corp/find-jug-dist-dir-maven-plugin
> 
>   HEAD
> 
>
> -
> 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: Release:perform failing on git ...

[Tim Wu T]

I think it should better for you to provide more stacktrace.

[ERROR] The git-clone command failed. This message is too limited to find the 
root cause.

Br,
Tim
-Original Message-
From: Benson Margulies [mailto:bimargul...@gmail.com] 
Sent: Friday, March 08, 2013 9:47 AM
To: Maven Users List
Subject: Release:perform failing on git ...

release plugin 2.3.2

prepare does fine.

perform fails with:

[INFO] --- maven-release-plugin:2.3.2:perform (default-cli) @
find-jug-dist-dir-maven-plugin ---
[INFO] Checking out the project to perform the release ...
[INFO] Executing: /bin/sh -c cd
/Users/benson/x/find-jug-dist-dir-maven-plugin/target && git clone --branch
find-jug-dist-dir-maven-plugin-1
g...@github.com:basis-technology-corp/find-jug-dist-dir-maven-plugin.git
/Users/benson/x/find-jug-dist-dir-maven-plugin/target/checkout
[INFO] Working directory:
/Users/benson/x/find-jug-dist-dir-maven-plugin/target
[ERROR] The git-clone command failed.

scm looks like:


  scm:git:g...@github.com:
basis-technology-corp/find-jug-dist-dir-maven-plugin.git
  scm:git:g...@github.com:
basis-technology-corp/find-jug-dist-dir-maven-plugin.git
  
https://github.com/basis-technology-corp/find-jug-dist-dir-maven-plugin

  HEAD


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

Re: Antwort: Re: Maven Shade Plugin

[Tim Kettler]

Am 01.03.2013 08:26, schrieb Jörg Schaible:

Hi Tim,

Tim Kettler wrote:


Am 28.02.2013 19:47, schrieb Joachim Durchholz:

Am 28.02.2013 16:24, schrieb Jan Engler:

At first: in fact this is only one artifact. The full jar contains all
classes of the dependecies, the api a reduced set (using filtern in the
shade plugin).


Is there a (conceivable) Maven build that uses api.jar as a dependency?
Then it must be the main artifact at its GAV (groupId/artifact/version)
coordinate.

Is there a (conceivable) Maven build that uses full.jar as a dependency?
Then it must be the main artifact at its GAV coordinate.

If both jars need to be main artifacts, they need to go to different GAV
coordinates. Because the dependent projects that need either api.jar or
full.jar have no way of specifying which of them they actually need, the
dependency section in their poms can only specify the GAV coordinate.


That's not correct. The classifier is part of the artifact coordinates
just like group, artifact(name) and version. A POM can just as well
depend on a secondary artifact:


  foo
  bar
  1.0
  api


The complete coordinates of an artifact are GAVTC: group,
artifact(name), version, type (default is jar), classifier (default is
empty).


That's not the real problem. What actually *is* a problem, if you depend on
different artifacts that bring both jars as transitive dependencies - you
cannot exclude e.g. the -api, because for exclusions you can only specify
GA. :-/


Ouch, never ran into this one.


- Jörg


-Tim


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

Re: Antwort: Re: Maven Shade Plugin

[Tim Kettler]

Am 28.02.2013 19:47, schrieb Joachim Durchholz:

Am 28.02.2013 16:24, schrieb Jan Engler:

At first: in fact this is only one artifact. The full jar contains all
classes of the dependecies, the api a reduced set (using filtern in the
shade plugin).


Is there a (conceivable) Maven build that uses api.jar as a dependency?
Then it must be the main artifact at its GAV (groupId/artifact/version)
coordinate.

Is there a (conceivable) Maven build that uses full.jar as a dependency?
Then it must be the main artifact at its GAV coordinate.

If both jars need to be main artifacts, they need to go to different GAV
coordinates. Because the dependent projects that need either api.jar or
full.jar have no way of specifying which of them they actually need, the
dependency section in their poms can only specify the GAV coordinate.


That's not correct. The classifier is part of the artifact coordinates 
just like group, artifact(name) and version. A POM can just as well 
depend on a secondary artifact:


  
foo
bar
1.0
api
  

The complete coordinates of an artifact are GAVTC: group, 
artifact(name), version, type (default is jar), classifier (default is 
empty).



Even if I split that up into 2 projects, I cannot define modules then in
the pom, right?


I'm not sure about that, I was never quite able to figure out what their
purpose is.

They might be just what you need to manage deployment of multiple
related projects. But that's just a gut feeling I have; I'll leave the
answer to that to the real experts.

 > I need to do s/t like that:

- Build up all modules (to be sure that everything is up to date)
- Build the shaded artifacts
- cross-compile them (using ikvm)
- put the artifact with some other stuff  (doc, examples, dlls, etc).into
one zip (in fact three: windows, linux, mac)
- deploy all artifacts into nexus (or maybe somewhere else using wagon)


Whoah. That ikvm and multi-arch stuff is way out of my league.

-
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-nar-plugin (version?)

[Tim Astle]

Thanks for the clarification.

I posted to this mailing list because that's what is listed on the 
maven-nar-plugin site.

http://duns.github.com/maven-nar-plugin/mail-lists.html

Can that be updated as well?

Is this the correct issue tracker: 
http://duns.github.com/maven-nar-plugin/mail-lists.html


FYI, I subscribed to the google mailing list.  Certainly don't mind 
assisting in the project.


Tim


On 1/16/2013 4:17 PM, Curtis Rueden wrote:

Hi all,

We are still unifying the various forks of maven-nar-plugin, so there is no
new official release version yet.

The maven-nar mailing list is at:
https://groups.google.com/forum/?fromgroups#!forum/maven-nar

It seems that all of the involved people are very busy, so progress is
rather slow. We welcome any additional help!

To avoid confusion, I updated the project readme (at
https://github.com/maven-nar/maven-nar-plugin) to reflect the current
project status and links, including a link to the mailing list.

Regards,
Curtis


On Wed, Jan 16, 2013 at 8:53 AM, Mark Donszelmann <
mark.donszelm...@gmail.com> wrote:


Hi

I wrote the NAR plugin, but have no longer time to maintain it.

I donated it (with approval of Sonatype) to a bunch of people who would
like to maintain it.

Its under

https://github.com/maven-nar

I guess with mailing lists and doc

Regards
Mark Donszelmann (duns)
On Jan 16, 2013, at 3:44 PM, Wayne Fay  wrote:


Nar is not a product of the Maven PMC, and so will never be an
official org.apache.maven.plugin anything.

Right, but whose product is it today and how do we find the latest
official release?

The groupId suggests that would be codeswarm.org. But there may be
other parties who have their own branches etc.

Wayne

-
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

maven-nar-plugin (version?)

[Tim Astle]

I'm trying out the maven-nar-plugin and I found a version on maven 
central that has the following 
signature: org.codeswarm:maven-nar-plugin:20121119


I didn't see 20121119 as a tag in the versions listed here: 
https://issues.sonatype.org/browse/NAR


The source seems pretty much the same as the head of the master 
(https://github.com/duns/maven-nar-plugin) as I used that to step 
through the debugger tosee if I could identify an issue.


My question is, "Is there an official 
org.apache.maven.plugin:maven-nar-plugin deployed?"


I didn't see it in Apache Snapshots. 
https://repository.apache.org/content/groups/snapshots/org/apache/maven/plugins/ 
and the "org.codeswarm" groupId on Maven Central makes me think that 
someone just took the master and deployed their own, unofficial, release.


Can an official snapshot or possible tagged release be deployed to the 
Apache Maven Repos?



Tim

Re: Re: Why does mvn compiile using java 1.3?

[Tim Pizey]

On 30 November 2012 13:42, Aliaksei Lahachou wrote:
> Hello everyone,
>
> I'm am against updating default version to 1.7. My favourite option would
> be to use the lowest possible version of JDK and give a warning if version
> is not specified explicitly

I too am in favour of maintaining the current behaviour, explicit
declaration of version, or you get 1.3.

Explicit versioning is what Maven is all about!

cheers
Tim

-- 
Tim Pizey - http://pizey.net/~timp

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

Re: maven-archetype-simple: JUnit 3.8 is really old.

[Tim Pizey]

Hi Steinar,

Thank you for this, no doubt you are right.

We now superstitiously continue with JUnit 3 naming conventions for
test classes and test methods,
whether we are using Junit3, 4 or TestNG (yes we use all three!)

It was indeed when TestNG was introduced that we had this problem.

For my taste I would not move away from a classic version, but I am
not fashionable :)

If you have not yet used Jenkins have a go: you will not look back.

thanks
Tim


On 28 September 2012 16:08, Steinar Bang wrote:
>>>>>> Tim Pizey :
>
>> Not everyone uses annotations, the surefire plugin requires the JUnit
>> 3.8.1 naming conventions,
>
> That doesn't seem to be the case:
>  http://maven.apache.org/plugins/maven-surefire-plugin/examples/junit.html
>
> Quote:
>   "Surefire supports three different generations of JUnit: JUnit 3.8.x,
>JUnit 4.x (serial provider) and JUnit 4.7 (junit-core provider with
>parallel support)."
>
>> the Jenkins plugins assume the same conventions.
>
> Hm... I haven't yet tried Jenkins, but I would surprised if Jenkins does
> anything outside of what maven would do, for a maven build...?
>
>> We have been bitten by People using JUnit4 and TestNG and hence
>> skipping tests in Jenkins.
>
> I found this on Stack Overflow, someone who had surefire not picking up
> tests marked with annotations:
>  
> http://stackoverflow.com/questions/2021771/surefire-is-not-picking-up-junit-4-tests
>
> It seems that in this case, this was a case of TestNG requiring JUnit
> 3.8.1 and shadowing a later dependance of JUnit 4.
>
>
> -----
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>



-- 
Tim Pizey - http://pizey.net/~timp

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

Re: maven-archetype-simple: JUnit 3.8 is really old.

[Tim Pizey]

Hi,

Yes it is old, but it is the best JUnit :)
The 4 series jumped the shark for me·

Old != bad.

I am not trying to start a flame war here, but assumed that it was
3.8.1 deliberately,
as this is the best JUnit can get.

Not everyone uses annotations, the surefire plugin requires the JUnit
3.8.1 naming conventions,
the Jenkins plugins assume the same conventions. We have been bitten
by People using JUnit4 and TestNG
and hence skipping tests in Jenkins.

I would do not think it would be an improvement to change this.

cheers
Tim




On 28 September 2012 11:25, Olivier Lamy  wrote:
> Hi,
> Agree it's old :-)
>
> Jira project is here: http://jira.codehaus.org/browse/MARCHETYPES
>
> 2012/9/28 Steinar Bang :
>> I created a project with maven-archetype-simple, and it creates a
>> project with a dependey to JUnit 3.8.1.
>>
>> JUnit 3.8.1 is really old.  In fact it's so old I've been unable to
>> google when it was released.  The oldest relase I find is the release of
>> JUnit 4.5 in 2008 http://www.junit.org/node/401
>>
>> Ah... found something: Release date: 5 September 2002.
>>  http://grepcode.com/snapshot/repo1.maven.org/maven2/junit/junit/3.8.1
>>
>> Really, really old!
>>
>> I would have liked to report an issue for this, but I have been unable
>> to figure out what the newest version is, and what issues have been
>> reported and fixed.
>>
>> The newest site for maven-archetype-plugin seems to be for version
>> 1.0-alpha7, dated February 8 2008
>>  http://maven.apache.org/plugins/maven-archetype-plugin-1.0-alpha-7/
>>
>> The issue site shows versions 2.3, 2.4, and 2.x, all listed under the
>> heading of "Unreleased":
>>  http://jira.codehaus.org/browse/ARCHETYPE
>>
>> I am confused...
>>
>>
>> -
>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
>> For additional commands, e-mail: users-h...@maven.apache.org
>>
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>



-- 
Tim Pizey - http://pizey.net/~timp

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

RE: maven3 snapshots in local repo

[Tim Eck]

Thanks, that is the most reasonable thing to do. Brining in a dependency
on aether a great choice for my usage(s) though. Fortunately it should be
pretty obvious in my case if this hack/assumption ever breaks. 

-Original Message-
From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On
Behalf Of Anders Hammar
Sent: Tuesday, September 25, 2012 3:04 AM
To: Maven Users List
Subject: Re: maven3 snapshots in local repo

I would recommend that you use Aether in that non-maven code to interact
with remote and local repo. This is what Maven does and it will then
ensure you don't run into issues.

/Anders

On Tue, Sep 25, 2012 at 12:13 AM, Tim Eck  wrote:
> Using mvn 3.0.4, when a SNAPSHOT artifact is resolved from a remote 
> repo it seems that my local repository ends up with both a -SNAPSHOT 
> artifact and a timestamped version (the remote end has only timestamped
versions).
> I'm curious if I can rely on this behavior since I have other 
> (non-maven) code that interacts with my local maven repo.
>
> For example, from a dependency like so:
>
> 
> foo
> bar
> 1.0.0-SNAPSHOT
> 
>
> I end up with with two identical jars  in my local repo after 
> resolving
> it:
>
> bar-1.0.0-20120924.201711-2.jar
> bar-1.0.0-SNAPSHOT.jar
>
> I think the code in
> org.eclipse.aether.internal.impl.DefaultArtifactResolver::getFile()  
> is responsible for making this additional copy
>
>
>
>
>
>
> -
> 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

maven3 snapshots in local repo

[Tim Eck]

Using mvn 3.0.4, when a SNAPSHOT artifact is resolved from a remote repo
it seems that my local repository ends up with both a -SNAPSHOT artifact
and a timestamped version (the remote end has only timestamped versions).
I'm curious if I can rely on this behavior since I have other (non-maven)
code that interacts with my local maven repo. 

For example, from a dependency like so:


foo
bar
1.0.0-SNAPSHOT


I end up with with two identical jars  in my local repo after resolving
it:

bar-1.0.0-20120924.201711-2.jar
bar-1.0.0-SNAPSHOT.jar

I think the code in
org.eclipse.aether.internal.impl.DefaultArtifactResolver::getFile()  is
responsible for making this additional copy






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

RE: Multi-module site problems: parent pom not downloaded

[Tim Wu T]

Hi

Maybe you can try adding mirror to make it download only though your repo.

Br,
Tim

-Original Message-
From: Laird Nelson [mailto:ljnel...@gmail.com] 
Sent: Tuesday, July 03, 2012 6:25 AM
To: Maven Users List
Subject: Multi-module site problems: parent pom not downloaded

My apologies for what I am sure is just dumb user error.  However, I could
not find the proper documentation to read.

I have a multi-module project.  All of the submodules inherit from the root
pom.xml.

This root pom.xml inherits, in turn, from a corporate pom.xml that is
hosted elsewhere.  Consequently it has no relative path, and the implied
relative path of .. obviously does not resolve.  This is all fine; no other
aspects of Maven have problems with this arrangement.

When I invoke mvn site from the root, the site plugin attempts to locate
this corporate pom in the repository.  It is present locally.

However, the site plugin attempts to download it from--only--Maven central,
where it is not found.

The build fails at this point with this error:

[INFO]

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-site-plugin:3.0:site (default-site) on
project ngp-parent: SiteToolException: Unable to read local module-POM: 1
problem was encountered while building the effective model for
com.foobar:foobar-bizbaw:1.010-SNAPSHOT
[ERROR] [FATAL] Non-resolvable parent POM for
com.foobar:foobar-parent:1.010-SNAPSHOT: Could not find artifact
com.foobar:foobar-corporate-pom:pom:12 in central (
http://repo1.maven.org/maven2) and 'parent.relativePath' points at wrong
local POM @ com.foobar:foobar-parent:1.010-SNAPSHOT,
/Users/ljnelson/Projects/foobar/pom.xml, line 10, column 11

What do I do to start diagnosing this error?  I stress again that version
12 of the corporate pom is indeed in the local repository, and is present
in one of the repositories present in my settings.xml.  Neither repository
is consulted.

Thanks,
Laird

-- 
http://about.me/lairdnelson

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

RE: Code coverage report for multi module maven project reports zero in some modules

[Tim Wu T]

Hi,

I met the same problem with you, now, I use jenkins cobuertural plugin, which 
will help me generate a whole report, not only include some packages :)

Br,
Tim

-Original Message-
From: kfmoh...@uci.edu [mailto:kfmoh...@uci.edu] 
Sent: Sunday, July 01, 2012 9:51 AM
To: Maven Users List
Subject: Re: Code coverage report for multi module maven project reports zero 
in some modules

Yes, I have moduleA, moduleB, moduleC, moduleD, moduleE and module F. I
run JUnit tests from module F.

The report in the moduleF/target... directory has the required coverage
information. However, the coverage report in the other modules reports
line and code coverage as zero.

I did try to use the aggregate option with setting it to true, to see an
aggregate coverage report for all modules, it gives the aggregate report,
but again only for packages in moduleF(from where we run JUnit tests) and
reports as zero for all other modules.

I am trying what was suggested in the first response to this question.

Is there a way that we generate the code coverage report for all modules,
with out using ant and only with use of cobertura ?

Thanks

> Aggregated cobertura report will execute cobertura on each module and then
> merge the single reports. It will not help if, for example, you have tests
> in module A and want to have coverage of module B.
>
>
> On Sat, Jun 30, 2012 at 10:46 AM, Patrick Mohr  wrote:
>
>> On Sat, Jun 30, 2012 at 12:18 AM, Aliaksei Lahachou <
>> aliaksei.lahac...@gmail.com> wrote:
>>
>> > Hi!
>> >
>> > cobertura:cobertura executes it's own lifecycle: instruments the
>> classes,
>> > instrumented classes are saved to target/generated-classes/cobertura,
>> and
>> > executes unit tests. Instrumented classes dump coverage data to
>> > target/conbertura/cobertura.ser. There are two things to understand:
>> >
>> > 1. When cobertura:cobertura is executed, dependencies are not
>> instrumented.
>> > You have to have enabled instrumentation, see cobertura:instrument
>> goal.
>> > This will produce jars with instrumented classes, so be careful not to
>> > distribute them.
>> > 2. Each module will write coverage data to it's own
>> > target/conbertura/cobertura.ser file. I think it's possible to
>> configure
>> > instrumentation so that all jars write to the same cobertura.ser file,
>> but
>> > I don't know whether it's normal, and I never tried that.
>> >
>> >
>> I want to say that there's a cobertura target.  Something like
>> cobertura:aggregate that will combine the results off all the unit
>> tests,
>> for the module that's being tested.  That probably won't be what you
>> want,
>> but I think it would be a lot closer.  This is all from memory though,
>> so
>> make sure to check it's actually what you want.
>>
>



-
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

maven release plugin with CVS, alternative to CVSPRO for client?

[Tim Dugan]

Hi All,

I'd like to try out the maven release plugin and I have a CVS repository.

>From a link off the Maven Wiki 
>(http://docs.codehaus.org/display/MAVENUSER/Create+a+release+using+CVSNT)  and 
>from a great write up here ( 
>http://java.dzone.com/articles/automating-releases-maven-0 ) it looks like 
>I'll need CVSNT (now CVSPRO ) as a CVS client.  Does anyone know if there is a 
>free / non trial alternative?  My company has a policy against using trial 
>versions of software.

Thanks!
Tim

RE: How to run parallel test suite files in Maven

[Tim Wu T]

It seems threadcount and parallel tag is not a correct choice, it only include 
"method, classes and test.

Try this:
2

Br,
Tim

-Original Message-
From: kristian.rosenv...@zenior.no [mailto:kristian.rosenv...@zenior.no] On 
Behalf Of Kristian Rosenvold
Sent: Tuesday, June 26, 2012 1:44 PM
To: Maven Users List
Subject: Re: How to run parallel test suite files in Maven

Probably not; if you switch to "classes" there should be some threading.

Is there any good reason why you choose the generally inferior
"methods" threading ?

Kristian


2012/6/26 sreekumar :
> Hi Team
>
> I am try to run parallel test suitesXML files from Maven as below
>
> 
>                        
>                                org.apache.maven.plugins
>                                maven-surefire-plugin
>                                2.12
>
>                                
>
>                                        methods
>                                        2
>
>                                        
>                                                
> testng-vm1.xml
>                                                
> testng-vm2.xml
>
>                                        
>                                
>
>                        
>
> When i execute with above code, the last testng xml file only (i.e
> testng-vm2.xml) is running.  But i want to run both xml files parallel .
>
>
> Please let me know is it possible to run parallel suites through Maven?
>
> --
> View this message in context: 
> http://maven.40175.n5.nabble.com/How-to-run-parallel-test-suite-files-in-Maven-tp5712022.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> -
> 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

RE: maven dependency plugin and maven 3

[Tim Wu T]

Hi Anders,

Thanks :), my mistake.

Br,
Tim



Ericsson

TIM WU
Software Designer

CBC/XIT/J
100102, China
Phone 84768153 (13153)
SMS/MMS +86 13810715183
tim.t...@ericsson.com
www.ericsson.com



This Communication is Confidential. We only send and receive email on the basis 
of the terms set out at www.ericsson.com/email_disclaimer

-Original Message-
From: anders.g.ham...@gmail.com [mailto:anders.g.ham...@gmail.com] On Behalf Of 
Anders Hammar
Sent: Monday, June 04, 2012 5:24 PM
To: Maven Users List
Subject: Re: maven dependency plugin and maven 3

Please don't hijack someone else's thread. Start a new thread instead.
Also, this question is much more appropriate on the Nexus users
mailing list. This is a generic Maven mailing list.

/Anders

On Mon, Jun 4, 2012 at 11:19 AM, Tim Wu T  wrote:
> Do you know if there is any small tool for us to deploy the 3pp jar into 
> nexus in additional to the nexus gui?
>
> Br,
> Tim
>
>
>
> Ericsson
>
> TIM WU
> Software Designer
>
> CBC/XIT/J
> 100102, China
> Phone 84768153 (13153)
> SMS/MMS +86 13810715183
> tim.t...@ericsson.com
> www.ericsson.com
>
>
>
> This Communication is Confidential. We only send and receive email on the 
> basis of the terms set out at www.ericsson.com/email_disclaimer
> -Original Message-
> From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com]
> Sent: Monday, June 04, 2012 4:10 PM
> To: Maven Users List
> Subject: Re: maven dependency plugin and maven 3
>
> From what I recall, nobody has yet updated dependency:tree to query
> aether's graph directly rather than go through the emulation of 2.x's API
> for examining the dependency tree. When I last chatted on this with
> Benjamin, he left me with the distinct impression that I should not rely on
> the output of dependency:tree when run on m3 until it has been adapted to
> query aether's graph more directly... But having said all that, I usually
> find it "good enough" and it may just be some edge cases that Benjamin was
> referring to, in which case I would suspect this is one of those edges.
>
> On Sunday, 3 June 2012, Jason van Zyl wrote:
>
>> You need to make a test case so we can reproduce it. It's impossible to
>> tell whether it's you, your environment, the dependency plugin or Maven
>> itself from looking at the textual output of the build.
>>
>> On Jun 3, 2012, at 11:42 AM, Anthony Dahanne wrote:
>>
>> > Hello  all,
>> > sorry to bump ... :-(
>> > but I'm still having issues understanding what's wrong with the maven
>> > dependency plugin and maven 3...
>> > I attached a pom to demonstrate the problem :
>> > Using maven 3,
>> > 1) do a mvn package
>> > 2) then do a mvn
>> >
>> org.apache.maven.plugins:maven-dependency-plugin:2.4:purge-local-repository
>> > -Dverbose=true   -DresolutionFuzziness=version -U
>> >
>> > You will see the following output :
>> > [INFO] --- maven-dependency-plugin:2.4:purge-local-repository
>> > (default-cli) @ pof ---
>> > [WARNING] Missing POM for javax.servlet:servlet-api:jar:2.5
>> > [INFO] Skipping: pof. It cannot be resolved.
>> > [INFO] Nothing to do for project: net.dahanne:pof:jar:1.0.0-SNAPSHOT
>> >
>> > But I can tell you javax.servlet:servlet-api:jar:2.5 has a pom, and is
>> > already installed in the local maven repository.
>> >
>> > Could you guys share some light on this ? I think the maven dependency
>> > plugin is not working fine with maven 3 , as opposed to what the
>> > documentation says :
>> > https://cwiki.apache.org/MAVEN/maven-3x-plugin-compatibility-matrix.html
>> >
>> > Thanks,
>> > Anthony
>> >
>> >
>> > -- Forwarded message --
>> > From: Anthony Dahanne >
>> > Date: Thu, May 31, 2012 at 5:50 PM
>> > Subject: maven dependency plugin and maven 3
>> > To: users@maven.apache.org 
>> >
>> >
>> > Hello all,
>> > I'm only using maven 3 on my machine (be it command line or m2e).
>> > I tried to use the maven dependency plugin on a project,
>> >
>> > mvn
>> org.apache.maven.plugins:maven-dependency-plugin:2.4:purge-local-repository
>> > -Dverbose=true   -DresolutionFuzziness=version
>> >
>> > and it printed such warnings :
>> >
>> > [WARNING] Missing POM for javax.servlet:servlet-api:jar:2.5
>> > [WARNING] Missing POM for org.easymock:easymock:jar:3.0
>> > [WARNING] Missing POM for junit:junit:jar:4.8.2
>> >
>> > 

RE: maven dependency plugin and maven 3

[Tim Wu T]

Do you know if there is any small tool for us to deploy the 3pp jar into nexus 
in additional to the nexus gui?

Br,
Tim



Ericsson

TIM WU
Software Designer

CBC/XIT/J
100102, China
Phone 84768153 (13153)
SMS/MMS +86 13810715183
tim.t...@ericsson.com
www.ericsson.com



This Communication is Confidential. We only send and receive email on the basis 
of the terms set out at www.ericsson.com/email_disclaimer
-Original Message-
From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] 
Sent: Monday, June 04, 2012 4:10 PM
To: Maven Users List
Subject: Re: maven dependency plugin and maven 3

>From what I recall, nobody has yet updated dependency:tree to query
aether's graph directly rather than go through the emulation of 2.x's API
for examining the dependency tree. When I last chatted on this with
Benjamin, he left me with the distinct impression that I should not rely on
the output of dependency:tree when run on m3 until it has been adapted to
query aether's graph more directly... But having said all that, I usually
find it "good enough" and it may just be some edge cases that Benjamin was
referring to, in which case I would suspect this is one of those edges.

On Sunday, 3 June 2012, Jason van Zyl wrote:

> You need to make a test case so we can reproduce it. It's impossible to
> tell whether it's you, your environment, the dependency plugin or Maven
> itself from looking at the textual output of the build.
>
> On Jun 3, 2012, at 11:42 AM, Anthony Dahanne wrote:
>
> > Hello  all,
> > sorry to bump ... :-(
> > but I'm still having issues understanding what's wrong with the maven
> > dependency plugin and maven 3...
> > I attached a pom to demonstrate the problem :
> > Using maven 3,
> > 1) do a mvn package
> > 2) then do a mvn
> >
> org.apache.maven.plugins:maven-dependency-plugin:2.4:purge-local-repository
> > -Dverbose=true   -DresolutionFuzziness=version -U
> >
> > You will see the following output :
> > [INFO] --- maven-dependency-plugin:2.4:purge-local-repository
> > (default-cli) @ pof ---
> > [WARNING] Missing POM for javax.servlet:servlet-api:jar:2.5
> > [INFO] Skipping: pof. It cannot be resolved.
> > [INFO] Nothing to do for project: net.dahanne:pof:jar:1.0.0-SNAPSHOT
> >
> > But I can tell you javax.servlet:servlet-api:jar:2.5 has a pom, and is
> > already installed in the local maven repository.
> >
> > Could you guys share some light on this ? I think the maven dependency
> > plugin is not working fine with maven 3 , as opposed to what the
> > documentation says :
> > https://cwiki.apache.org/MAVEN/maven-3x-plugin-compatibility-matrix.html
> >
> > Thanks,
> > Anthony
> >
> >
> > -- Forwarded message --
> > From: Anthony Dahanne >
> > Date: Thu, May 31, 2012 at 5:50 PM
> > Subject: maven dependency plugin and maven 3
> > To: users@maven.apache.org 
> >
> >
> > Hello all,
> > I'm only using maven 3 on my machine (be it command line or m2e).
> > I tried to use the maven dependency plugin on a project,
> >
> > mvn
> org.apache.maven.plugins:maven-dependency-plugin:2.4:purge-local-repository
> > -Dverbose=true   -DresolutionFuzziness=version
> >
> > and it printed such warnings :
> >
> > [WARNING] Missing POM for javax.servlet:servlet-api:jar:2.5
> > [WARNING] Missing POM for org.easymock:easymock:jar:3.0
> > [WARNING] Missing POM for junit:junit:jar:4.8.2
> >
> > before telling me that the build was successful.
> > Thing is, it did not purge anything from my repo; because of those
> > warnings actually; launching the same command with -X, I could see :
> > [DEBUG] Verifying availability of
> >
> /Users/anthony/.m2/repository/javax/servlet/servlet-api/2.5/servlet-api-2.5.pom
> > from []
> > [WARNING] Missing POM for javax.servlet:servlet-api:jar:2.5: Error
> > resolving project artifact: Could not find artifact
> > javax.servlet:servlet-api:pom:2.5 for project
> > javax.servlet:servlet-api:pom:2.5
> > [DEBUG]   javax.servlet:servlet-api:jar:2.5:provided (selected for
> provided)
> >
> > and... I can tell you
> >
> /Users/anthony/.m2/repository/javax/servlet/servlet-api/2.5/servlet-api-2.5.pom
> > exists and contains :
> > 
> >  4.0.0
> >  javax.servlet
> >  servlet-api
> >  2.5
> > 
> >
> > Debugging the code a little, I could notice that this goal was using
> >
> org.apache.maven.artifact.resolver.DefaultArtifactResolver#resolveTransitively
> > from maven-artifact-manager 2.0.9 to find the dependencies.
> >
> > I am won

Re: Filters only work in 3.0.4

[Tim Pizey]

On 10 May 2012 17:44, I  wrote:
> Hi,
>
> I have a filters block:
>     
>      
> /etc/${project.artifactId}/${project.artifactId}.properties
>     
> as given here:
> http://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html
> I was delighted with this!
>
> However I find that this has only started to work in 3.0.4, which I happened
> to have on my laptop.
>
> It does not work on 3.0.3, I have tried many combinations of
>
>  
>    
>      
>        org.apache.maven.plugins
>        maven-resources-plugin
>        2.5
>        
>         
>          org.apache.maven.shared
>          maven-filtering
>          1.0
>         
>        
>      
>    
>  
>
> but these do not seem to have had any effect.
>
> I can update to 3.0.4 on the build server, but it would be nice find a
> configuration which worked on 3.0.3
> and 2.x maven as well.
>

  

  org.apache.maven.plugins
  maven-resources-plugin
      2.5

  


Does enable the  to work on 3.0.3 and 3.0.4, have not tested on 2.x

cheers
Tim


-- 
Tim Pizey - http://pizey.net/~timp

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

Filters only work in 3.0.4

[Tim Pizey]

Hi,

I have a filters block:
 
  
/etc/${project.artifactId}/${project.artifactId}.properties
 
as given here:
http://maven.apache.org/plugins/maven-resources-plugin/examples/filter.html
I was delighted with this!

However I find that this has only started to work in 3.0.4, which I happened
to have on my laptop.

It does not work on 3.0.3, I have tried many combinations of

  

  
org.apache.maven.plugins
maven-resources-plugin
2.5

 
  org.apache.maven.shared
  maven-filtering
  1.0
 

  

  

but these do not seem to have had any effect.

I can update to 3.0.4 on the build server, but it would be nice find a
configuration which worked on 3.0.3
and 2.x maven as well.

cheers
Tim


-- 
Tim Pizey - http://pizey.net/~timp

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

Re: Custom plugin - how to resolve wildcards in excludes/includes

[Tim Drury]

Take a look at PlexusUtils' FileUtils class:
http://plexus.codehaus.org/plexus-utils/apidocs/org/codehaus/plexus/util/FileUtils.html

Look at the getFileName() methods and variants.  They use DirectoryScanner
which handles "**" wildcards and such.

-tim

On Wed, Apr 25, 2012 at 1:17 PM, jaybytez  wrote:

> So I am creating a custom plugin that we are using for compiling things
> like
> Drools Rules.
>
> I have successfully injected and used excludes to help exclude files from
> this compilation.
>
> I would like to take advantage of the wildcarding commonly used in
> includes/excludes like "**/*.xls".
>
> Is there a Maven/Mojo class that can be used to help resolve or match a
> String to these expressions, as I assume these aren't standard regular
> expressions.
>
> That way if I have multiple files, I could use this helper class in my
> custom plugin to match resources files with the exclusion list.
>
> Thanks...
>
> --
> View this message in context:
> http://maven.40175.n5.nabble.com/Custom-plugin-how-to-resolve-wildcards-in-excludes-includes-tp5665480p5665480.html
> Sent from the Maven - Users mailing list archive at Nabble.com.
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

another eclipse multi module vs. flat question

[Tim Dugan]

I'm new to maven and very much used to the "application per eclipse project, 
and common library per eclipse project".  

I know "multi module vs. flat"  has been discussed multiple times on this list, 
but I've not seen general "pros/cons, rules of thumb, etc."  of when an 
application should be part of a multi-module vs. split out to another eclipse 
project.  

I'm going under the assumption in the "maven way" it's OK to have multiple 
applications living as part of a multi-module, for example foo_webapp and 
cmd_line_client both dependant on lib_a

MyMultiModuleProject
->lib_a
->foo_webapp
->cmd_line_client

But what decides that foo_webapp and cmd_line belong here, just their 
dependency on lib_a and the desire to share pom config & version them together? 
 For example, should a few new applications, also dependent on lib_a should 
live here?  When does it end?   Or perhaps if "lib_a" is expected to be widely 
reusable it should live outside the multi-module...or

Any links to references greatly appreciated...

Thanks for your input!
Tim




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

idea about capture maven output by something other than text logs

[Tim Drury]

I've been throwing around an idea for a bit and wanted to run it by the
list to see if it's worth pursuing or if it's been considered and rejected.

Running through text logs of maven output to determine exactly what has
happened during the build is tedious and, well, unexciting.  I'd like to be
able to visualize maven output as an object graph of modules, phases,
plugins, etc..  I'd like to be able to drill down into a module to see
exactly how the artifact was built.  I'd like to know what caused the
compiler plugin to run or skip compilation.  I'd like to see exactly where
dependencies were pulled from when included in a war.

I had the idea of using maven's events to capture the necessary object
graph and store it in some persistent manner for later retrieval.  And I'd
like to create a simple UI for traversing the object graph graphically -
perhaps using Eclipse GEF.

A few things are missing for this: events are missing timestamps and
plugins don't really throw events at all.  I'd like to see, e.g., the
compiler plugin throw one or more events describing why it ran, what it
compiled, and what the results were.

Thoughts?

-tim

RE: Unable to update index for central|http://repo1.maven.org/maven2

[Tim Wu T]

Hi,

Pls check the network connection using ping repo1.maven.org

Maybe there are some changes in your network.

If the result of ping is failure, you need add a proxy in your settgins.xml.

Br,
Tim

-Original Message-
From: zhangwujun [mailto:zhangwu...@neusoft.com] 
Sent: Saturday, March 31, 2012 10:07 AM
To: users
Subject: Unable to update index for central|http://repo1.maven.org/maven2

hello,these days,I try many ways to update index for 
central(http://repo1.maven.org/maven2 ),but,all failure.Can you tell me the 
reason and how to sovle this problem,thank you very mach.




zhangwujun
---
Confidentiality Notice: The information contained in this e-mail and any 
accompanying attachment(s) 
is intended only for the use of the intended recipient and may be confidential 
and/or privileged of 
Neusoft Corporation, its subsidiaries and/or its affiliates. If any reader of 
this communication is 
not the intended recipient, unauthorized use, forwarding, printing,  storing, 
disclosure or copying 
is strictly prohibited, and may be unlawful.If you have received this 
communication in error,please 
immediately notify the sender by return e-mail, and delete the original message 
and all copies from 
your system. Thank you. 
---

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

Re: Producing 2 jars from same sources with different java version ?

[Tim Pizey]

On 16 March 2012 09:49, jerem  wrote:
> Hi,
>
> I wonder if it would be possible with Maven to produce, from a same module
> sources, 2 different jars with classes compiled with different source and
> target values ?
>
> I'm up to using "-d " as compilerArgument of the
> maven-compiler-plugin, but it fails with :
> " javac: invalid flag: -d "
>
> If I run maven with -X option and test the javac command-line logged, it
> works though ...
>
> If that worked I would have 2 executions of compiler (producing
> target/classes-15 and target/classes-16), then would use 2 executions of
> maven-jar-plugin to produce both jars with different classifiers if
> possible.
>
> Thanks for help,
> Jeremie

I suggest you use profiles then you can specify different
compiler options in each profile and invoke with

mvn deploy -Pjava15
mvn deploy -Pjava16

cheers
Tim



-- 
Tim Pizey - http://pizey.net/~timp

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

RE: Avoid constant manual artifact installation in Netbeans

[Tim Wu T]

Hi,

Maybe you can try assembley plugin, like this:

maven-assembly-plugin


GG
package

single




bin

src

jar-with-dependencies








-Original Message-
From: new2maven [mailto:ralf.but...@web.de] 
Sent: Friday, March 16, 2012 1:15 PM
To: users@maven.apache.org
Subject: Avoid constant manual artifact installation in Netbeans

Hi there,

I work on a Maven project which makes use of a jar-file via a dependency.
The jar-file is modified on a daily basis.
Whenever a new jar-file is built, I usually go to the jar-dependency in the
Maven project and click on 'Manually install artifact'. I was wondering if
there is a mechanism to automate it. So, whenever a new jar file is built
the dependency gets updated as well.

Many thanks in advance!
Sarah

--
View this message in context: 
http://maven.40175.n5.nabble.com/Avoid-constant-manual-artifact-installation-in-Netbeans-tp5569994p5569994.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
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 2 can not use Alternate Doclets

[Tim Wu T]

I had found the reason why it not runs. I add the following info in the pom, it 
generate the docs:



attach-javadocs

jar




I just curious, if I do not add this, what will happen?

Br,
Tim

-Original Message-
From: Tim Wu T [mailto:tim.t...@ericsson.com] 
Sent: Tuesday, March 13, 2012 10:26 AM
To: Maven Users List
Subject: Maven 2 can not use Alternate Doclets

Hi there,

I am trying to use maven javadoc plugin generate customized java-doc, I found 
Maven 3 works well, it can identify our defined doclet, however, maven 2 do not 
recognized it.

The related plugin info can be found as follows:

org.apache.maven.plugins
maven-javadoc-plugin
2.8

xx.MyDoclet



xx.mydoc.generator

generator

0.1-SNAPSHOT



${project.basedir}/docgen
-outputfile 
"my.html"

true
aa.bb.cc.test



Do you know why? Great thanks for your help.

Br,
Tim


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

RE: Dependency in the local repository is ignored

[Drury, Tim]

If this is a multi-module project, and you run eclipse:eclipse, I'm fairly sure 
eclipse will resolve the dependency as a project dependency, not a library 
dependency.  Look in your Build Path and select the Project tab to see if the 
dependent project is there.

-Original Message-
From: Alex [mailto:zeita...@googlemail.com] 
Sent: Tuesday, March 06, 2012 12:04 PM
To: Maven Users List
Subject: Re: Dependency in the local repository is ignored

Thanks a lot for all answers.

> What do you mean by ignored? Explain this in more detail.
I compile and install jar from one project and using it in another project.
It is installed in local repository but it is not included into .classpath
. There are all external dependencies but not my own jar.

>What is the exact command line you used to install?
To build and install my jar into local repository I use just
"mvn clean", "mvn install" or from eclipse m2e's menu "install"

to include my jar into the eclipse's ".classpath" file of the other project
I use:
mvn eclipse:clean
mvn eclipse:eclipse

>Have you tried:
>1) mvn -X eclipse:eclipse and seeing if any of the debug reports
>removing or ignoring it
>2) backup .classpath .project and .settings then recreating
>3) Checking and older version in source control
>4) New instance of Eclipse
I tried all from above except mvn -X eclipse:eclipse. I will try it
tomorrow when I will get access to working computer.
Alex

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

RE: Cobertura instrumentation in complex projects

[Drury, Tim]

I've done exactly this and it's a pain.  I didn't want cobertura-instrumented 
jars from possibly infecting our production jars, so I have a Jenkins project 
that uses a private maven repo to build the entire product.  The final 
deliverable has a "cobertura" classifier and this is deployed to Artifactory.  
Another Jenkins project runs daily to pick up this artifact and deploy it to 
our integration test server.

However, all this is only the start of your problems.  Getting cobertura data 
files from the integration server in an automated fashion is very hard.  I had 
to write a web service to fetch the data from the (well documented) cobertura 
static class and return it to the caller.  After my integration test cases run, 
a maven plugin I wrote fetches that data, and I use the Jenkins cobertura 
plugin to turn it into html reports.  

I'm in the process of scrapping all that in favor of jacoco which instruments 
the code on-the-fly via a javaagent running in the container.

-tim

-Original Message-
From: Jim McCaskey [mailto:jim.mccas...@pervasive.com] 
Sent: Tuesday, March 06, 2012 12:00 PM
To: 'users@maven.apache.org'
Subject: Cobertura instrumentation in complex projects

Hello all,

I have a fairly large build in which we use cobertura extensively to look at 
unit test code coverage for our project.  We also have separate integration 
tests that we would like to run using these instrumented binaries.  There is 
some good documentation on how to accomplish that here:

http://mojo.codehaus.org/cobertura-maven-plugin/instrumentingDeploymentArtifact.html

While that would work for a simple case, I'm struggling with trying to 
visualize how this would work in a complex case.  We have several separate 
builds that accumulate to make up the install package that we then push to our 
integration testing systems.  So everyone one of our couple hundred jar's which 
are fed from all these builds would need to be published to a Maven repository 
so that the install builds could pick them up.  But if I push them to my 
standard SNAPSHOT repository it would overwrite my existing non-instrumented 
versions.

We only envision needing this run on a nightly basis.  One suggestion that has 
been proposed is to do the "publish with classifier" thing and a profile that 
turns on cobertura.

https://maven.apache.org/plugins/maven-deploy-plugin/examples/deploying-with-classifiers.html

Frankly, I'm not sure how that plumbing would work at this point, but I suppose 
it's possible.  Having said that, I think we just got done having that 
conversation on this list and the answer is that that is "not the maven way".

I'm positive I'm not the first one in this boat.  Any thoughts?

-Jim





-
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: Dependency in the local repository is ignored

[Drury, Tim]

If you already have eclipse projects set up, try running:

mvn eclipse:clean eclipse:eclipse


-Original Message-
From: Alex [mailto:zeita...@googlemail.com] 
Sent: Tuesday, March 06, 2012 10:28 AM
To: users@maven.apache.org
Subject: Dependency in the local repository is ignored

Dear All,
I am looking for a solution since several days already. The problem:
All of a sudden one of my dependencies is ignored.
I am installing it using
mvn install
And when I am running
mvn eclipse:eclipse
It is not listed in the Referenced Libriries node although it is present in
the local repository.
I installed the newest releases of maven, eclipse, m2eclipse.
Please, please help
Alex

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

Re: EventSpy not registered?

[Tim Drury]

I was missing plexus/components.xml.  Got it working now.  Thanks, all.

-tim

On Mon, Mar 5, 2012 at 6:47 PM, Jason van Zyl  wrote:

> Here's a working example of an event spy. You can build it and drop it
> into the ${m2_home}/lib/ext directory:
>
> https://github.com/etesla/tesla-profiler
>
> On Mar 5, 2012, at 6:04 PM, Tim Drury wrote:
>
> > No, I hadn't but I just did and same result - nothing in the output logs.
> >
> > -tim
> >
> > On Mon, Mar 5, 2012 at 5:56 PM, Olivier Lamy  wrote:
> >
> >> Did you add you jar in $M2_HOME/lib/ext/ ?
> >>
> >> 2012/3/5 Tim Drury :
> >>> I wrote a class that extends maven 3.0.4 AbstractEventSpy and simply
> >> writes
> >>> to a java.util.logging.Logger at info level (and System.out) when each
> >>> method is called.  I run it via:
> >>>
> >>> mvn
> >> -Dmaven.ext.class.path=/Users/tdrury/.m2/.../mavenspy-0.1-SNAPSHOT.jar
> >>> -X clean install
> >>>
> >>> yet I get nothing in the output indicating my EventSpy is being called.
> >>> Any clues?
> >>>
> >>> -tim
> >>
> >>
> >>
> >> --
> >> Olivier Lamy
> >> Talend: http://coders.talend.com
> >> http://twitter.com/olamy | http://linkedin.com/in/olamy
> >>
> >> -
> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> >> For additional commands, e-mail: users-h...@maven.apache.org
> >>
> >>
>
> Thanks,
>
> Jason
>
> --
> Jason van Zyl
> Founder,  Apache Maven
> http://twitter.com/jvanzyl
> -
>
> Three people can keep a secret provided two of them are dead.
>
>  -- Unknown
>
>
>
>
>

Re: EventSpy not registered?

[Tim Drury]

No, I hadn't but I just did and same result - nothing in the output logs.

-tim

On Mon, Mar 5, 2012 at 5:56 PM, Olivier Lamy  wrote:

> Did you add you jar in $M2_HOME/lib/ext/ ?
>
> 2012/3/5 Tim Drury :
> > I wrote a class that extends maven 3.0.4 AbstractEventSpy and simply
> writes
> > to a java.util.logging.Logger at info level (and System.out) when each
> > method is called.  I run it via:
> >
> > mvn
> -Dmaven.ext.class.path=/Users/tdrury/.m2/.../mavenspy-0.1-SNAPSHOT.jar
> > -X clean install
> >
> > yet I get nothing in the output indicating my EventSpy is being called.
> >  Any clues?
> >
> > -tim
>
>
>
> --
> Olivier Lamy
> Talend: http://coders.talend.com
> http://twitter.com/olamy | http://linkedin.com/in/olamy
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: Is it possible to use a jar overlay pattern, like the war overlay?

[Tim Pizey]

Thanks, that looks very promising.
Tim

On 23 February 2012 23:06, Wayne Fay  wrote:
>> What I have done is create  source jar of the first one and unpack
>> that into the second,
>> but it would be really nice to use an overlay plugin,
>> excluding the single resource file and including a different one.
>
> No plugin that I am aware of supports this specific use-case but
> perhaps Shade can help?
>
> http://maven.apache.org/plugins/maven-shade-plugin/examples/resource-transformers.html
>
> Wayne
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>



-- 
Tim Pizey - http://pizey.net/~timp

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

Is it possible to use a jar overlay pattern, like the war overlay?

[Tim Pizey]

Hi,

I have a jar which uses the hyperjaxb plugin.
I would like to make a similar one, with one .xsd file different.

What I have done is create  source jar of the first one and unpack
that into the second,
but it would be really nice to use an overlay plugin,
excluding the single resource file and including a different one.

Is there a plugin for that?

cheers
Tim


-- 
Tim Pizey - http://pizey.net/~timp

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

RE: compiler errors hidden when building Maven project on Jenkins

[Drury, Tim]

>And the OP is probably using the "evil" Maven project type and not a
>freestyle project with a maven build step

I am.  Is this bad? 

-tim

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

compiler errors hidden when building Maven project on Jenkins

[Drury, Tim]

I've asked this question on the Jenkins email list a week ago (where I think it 
belongs) and on StackOverflow, but I've gotten no results.  I know this isn't a 
Maven issue per se' because a local build does show compiler syntax errors, but 
I'm at wits end and hoping someone on this list may have seen this issue before 
and offer some insight.

I've posted this question to StackOverflow here: 
http://stackoverflow.com/questions/9229020/jenkins-not-showing-maven-compiler-errors

I'll summarize here, but to see full output I hope you wouldn't mind clicking 
that link - the output is long and better encapsulated there then in this email.

When Jenkins 1.450 builds my maven 3 project, if there are compiler errors all 
I get is an exception from the maven-compiler-plugin (2.0.2) and not the actual 
syntax errors you usually see.  When building locally, you _do_ get the syntax 
errors.  Jenkins used to show the compiler syntax errors but stopped doing so 
about two weeks ago.  What changed?  We switched from maven 2.2.1 to maven 
3.0.4, but I'm fairly certain we got compiler errors in the output just after 
the switch (but can't verify this).

I found a similar (possibly the same) issue on Jenkins' Jira: 
https://issues.jenkins-ci.org/browse/JENKINS-10333 but no action had been taken.

Has anyone else seen this?  Is this a Jenkins issue or a Maven issue (or both)?

-tim

Tim Drury
Architect
SAP Manufacturing Execution (SAP ME)
Supply Chain Management
SAP Labs, LLC
T +1 404 943 2088
F +1 610 492 2257
mailto:t.dr...@sap.com
www.sap.com

Please consider the impact on the environment before printing this e-mail.

Re: How to turn off project assembly generation

[Tim Pizey]

Hi Dennis,

Thanks, doh, that will be the explicit configuration I put in some years ago!

I have removed all explicit configuration of the assembly plugin  and
it is back to expected behaviour.

thanks again
Tim


On 10 February 2012 19:10, Dennis Lundberg  wrote:
> Hi Tim
>
> Maven does not produce such assemblies by default. Somewhere in your
> project's POM hierarchy you should find a configuration for
> maven-assembly-plugin.
>
> To find it you can use this command:
>
> mvn help:effective-pom
>
> On 2012-02-10 20:07, Tim Pizey wrote:
>> Hi,
>>
>> I have seen that the default (in maven 2.2) is now to generate a series of
>> -project.zip, -project.tar.bz2, -project.tar.gz files.
>>
>> I have read the site but cannot figure out how to configure my pom to
>> only produce the
>> .jar outputs.
>>
>> thanks in advance
>> Tim
>>
>>
-- 
Tim Pizey - http://pizey.net/~timp

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

How to turn off project assembly generation

[Tim Pizey]

Hi,

I have seen that the default (in maven 2.2) is now to generate a series of
-project.zip, -project.tar.bz2, -project.tar.gz files.

I have read the site but cannot figure out how to configure my pom to
only produce the
.jar outputs.

thanks in advance
Tim


-- 
Tim Pizey - http://pizey.net/~timp

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

RE: Release perform met exception because of strange project structure.

[Tim Wu T]

Hi Wayne,

I had changed the project structure now, it works well.

Thanks for your comments.

Brs,
Tim

-Original Message-
From: Wayne Fay [mailto:wayne...@gmail.com] 
Sent: Saturday, January 21, 2012 12:30 AM
To: Maven Users List
Subject: Re: Release perform met exception because of strange project structure.

> Do you have any idea for this? If I should change the structure or if there
> is other method can solve this?

Changing the structure seems like the most pragmatic solution to your problem.

Wayne

-
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

Release perform met exception because of strange project structure.

[Tim Wu T]

Hi there,

I met a tricky problem about release.

I used jenkins release plug in to do the release, in the past, everything is 
ok. However, yesterday, there is a new project, the project structure like this:

Project
-.git
--myproject
 pom.xml
 ...

This structure is very strange because in the past, the .git folder should be 
in the myproject.

When I release this project in manve perform phase, there is an exception, you 
can find it as follows:

[INFO] [ERROR] The goal you specified requires a project to execute but there 
is no POM in this directory 
(/home/xx/.jenkins/jobs/ABC/workspace/bde/target/checkout). Please verify you 
invoked Maven from the correct directory. -> [Help 1]

This is the command:

[DEBUG] Executing: /bin/sh -c cd 
/home/etigwuu/.jenkins/jobs/DCMLTE_BDE/workspace/bde/target/checkout && 
/home/gg/maven/apache-maven-3.0.3/bin/mvn -B -X -D 
maven.repo.local=/home/xx/.m2/repository -s /home/xx/.m2/settings.xml -D 
performRelease=true -P default-repo deploy
[INFO] Apache Maven 3.0.3 (r1075438; 2011-03-01 01:31:09+0800)

Because it runs the maven common in the checkout folder, however, the pom is in 
the sub-folder, so the error happens.

Do you have any idea for this? If I should change the structure or if there is 
other method can solve this?

Brs,
Tim

RE: skip cobertura for a module

[Drury, Tim]

I just looked at the cobertura maven source the other day, so I took another 
look.  skipMojo() is the first call in the instrument plugin and if skip is 
true it should log at INFO level: "Skipping cobertura execution"

While I don't have a solution to your issue, I can tell you that cobertura is 
definitely running on this module.

-tim

-Original Message-
From: Jim McCaskey [mailto:jim.mccas...@pervasive.com] 
Sent: Monday, December 12, 2011 2:20 PM
To: 'users@maven.apache.org'
Subject: skip cobertura for a module

Hello all,

I tried posting this on the codehaus user list but it won't accept my e-mails.  
So let's try here:

I'm having an issue with the cobertura plugin.  I have a muti-module build that 
I invoke like this on a nightly basis:

mvn install site:site findbugs:findbugs cobertura:cobertura

Now all of the modules in the build should build using cobertura, except one.  
We have some custom stuff that is not entirely the "Maven way" and want to 
ignore it for the sake of running cobertura (it does not contain code anyway).  
Here's where I start hitting trouble.  It seems that I cannot get the skip to 
work.  It always at least runs the prepare.  It's not corbertura that's failing 
(one of our in house plugins unfortunately), but I don't want that prepare to 
run at all.  

Ideally I would just use a skip like this:


org.codehaus.mojo
cobertura-maven-plugin

true



But when I put that in, it still invokes cobertura.  At least I see it say this:

[INFO] Preparing cobertura:cobertura

And it proceeds to run all the other plugins again.  To be pedantic, I tried 
this as well:


org.codehaus.mojo
cobertura-maven-plugin

true




clean
check
cobertura
dump-datafile
instrument





But that had similar results.

I also tried putting this property in the pom:


true


Again, that did not stop it from running the prepare bit.  It seems to always 
run the prepare.  

How do I turn cobertura off for this one module?

-Jim


-
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 Project - in repository or in current modular project

[Tim Mickelson]

Thanks a million, as I said, now I will as soon as I have time study 
this suggestion and when I have resolved my issue I will give my 
version here for future users with similar problems.


On mercoledì 2 novembre 2011 11.46.21, Stephen Connolly wrote:

 /**
  * @parameter expression="${reactorProjects}"
  * @required
  * @readonly
  */
 private List/**/ reactorProjects;

will in your mojo will give you the list of reactor projects (if
targetting JRE 1.5+ you can safely uncomment the generics qualifier)

for (MavenProject project: reactorProjects) {
   if (project.getGroupId().equals(groupId)&&
project.getArtifactId().equals(artifactId)&&
project.getVersion().equals(version)) {
 for (Artifact artifact: project.getAttachedArtifacts() {
   if (artifact.getClassifier().equals(classifier)&&
artifact.getType().equals(type)) {
 return artifact.getFile();
 }
   }
}
return null;

If you get a null file back or if the file does not exist fall
back to resolving from the local/remote repos

On 2 November 2011 09:52, Tim Mickelson  wrote:

   Thanks, I think I've understood your strategy, that immediately brings me
to the problem that I'm lacking documentation. Could you please give me an
simple example how to do this, at least the two most important passes and I
should be on a go I think :)

   Of course if I resolve my problem then I will give an exhausted
explanation how I went about it so that future users searching this thread
see me through.

   Tim

On 02/11/2011 10.15, Stephen Connolly wrote:

On 2 November 2011 09:06, Tim Mickelson  wrote:

  I want to write a plugin to maven that copies the flex modules from a flex
project (type swf) which contains modules. This  because the flexmojos does
not do this. My problem is that independent of how the flexmodules are
configured in the pom of the flex project they are saved on the local
repository with a naming convention using artifactId, version and the name
in lowercase as configured in the pom.

  I need to copy them as configured in the pom. Well, actually this is not a
great problem, just some manipulation extracting information from the pom
and I'm done. The problem is, that when flex project is in some way part of
my project (modular) then the files are not saved with this convention but
in the path as configured in the pom and with the name as configured in the
pom.

  I would like to know, how I can distinguish if the swf project that I have
at hand is in the repository, because it was previously installed or if it
is part of my current project. I don't know if I've explained myself well,
with being in my current project I mean specifically the case in which I
have a pom that has e.g. two modules, one for the swf, and then one war
where I want to put the peaces together.

You should be looking for the references to the files from the
reactor's attached artifacts not on the disk directly, so you'd
iterate through the reactorProjects looking for the one with the
matching GAV, if present then you look at that project's attached
artifacts for the matching GAVCT and if the getFile() != null then
that is your file. Otherwise if you have not found the file, then hit
the repositories.

That is the _correct_ way in principle

What I cannot recall is if there are some handy helper methods/utility
classes to do just that for you or whether you have to reinvent the
wheel each time

-Stephen

  Any link to documentation is welcome, all I can find is to simple from e.g.
the maven site or the complete guide.

  Tim

-
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 Project - in repository or in current modular project

[Tim Mickelson]

  Thanks, I think I've understood your strategy, that immediately 
brings me to the problem that I'm lacking documentation. Could you 
please give me an simple example how to do this, at least the two most 
important passes and I should be on a go I think :)


  Of course if I resolve my problem then I will give an exhausted 
explanation how I went about it so that future users searching this 
thread see me through.


  Tim

On 02/11/2011 10.15, Stephen Connolly wrote:

On 2 November 2011 09:06, Tim Mickelson  wrote:

  I want to write a plugin to maven that copies the flex modules from a flex
project (type swf) which contains modules. This  because the flexmojos does
not do this. My problem is that independent of how the flexmodules are
configured in the pom of the flex project they are saved on the local
repository with a naming convention using artifactId, version and the name
in lowercase as configured in the pom.

  I need to copy them as configured in the pom. Well, actually this is not a
great problem, just some manipulation extracting information from the pom
and I'm done. The problem is, that when flex project is in some way part of
my project (modular) then the files are not saved with this convention but
in the path as configured in the pom and with the name as configured in the
pom.

  I would like to know, how I can distinguish if the swf project that I have
at hand is in the repository, because it was previously installed or if it
is part of my current project. I don't know if I've explained myself well,
with being in my current project I mean specifically the case in which I
have a pom that has e.g. two modules, one for the swf, and then one war
where I want to put the peaces together.


You should be looking for the references to the files from the
reactor's attached artifacts not on the disk directly, so you'd
iterate through the reactorProjects looking for the one with the
matching GAV, if present then you look at that project's attached
artifacts for the matching GAVCT and if the getFile() != null then
that is your file. Otherwise if you have not found the file, then hit
the repositories.

That is the _correct_ way in principle

What I cannot recall is if there are some handy helper methods/utility
classes to do just that for you or whether you have to reinvent the
wheel each time

-Stephen


  Any link to documentation is welcome, all I can find is to simple from e.g.
the maven site or the complete guide.

  Tim


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

Maven Project - in repository or in current modular project

[Tim Mickelson]

  I want to write a plugin to maven that copies the flex modules from a 
flex project (type swf) which contains modules. This  because the 
flexmojos does not do this. My problem is that independent of how the 
flexmodules are configured in the pom of the flex project they are saved 
on the local repository with a naming convention using artifactId, 
version and the name in lowercase as configured in the pom.


  I need to copy them as configured in the pom. Well, actually this is 
not a great problem, just some manipulation extracting information from 
the pom and I'm done. The problem is, that when flex project is in some 
way part of my project (modular) then the files are not saved with this 
convention but in the path as configured in the pom and with the name as 
configured in the pom.


  I would like to know, how I can distinguish if the swf project that I 
have at hand is in the repository, because it was previously installed 
or if it is part of my current project. I don't know if I've explained 
myself well, with being in my current project I mean specifically the 
case in which I have a pom that has e.g. two modules, one for the swf, 
and then one war where I want to put the peaces together.



  Any link to documentation is welcome, all I can find is to simple 
from e.g. the maven site or the complete guide.


  Tim

Re: Problems with MAVEN's-ANT on OpenVMS

[Tim Pizey]

Wow Wayne, brilliant response!


On 20 October 2011 22:51, Wayne Fay  wrote:
>> With knowing the details about our environment
>> would you expect that Lucene written in clean Java
>> is not operating on such a platform?
>
> Without a comprehensive analysis of the source code for Lucene (and
> potentially, some or all of its dependencies) it is impossible to say
> anything conclusive about how well it may operate on OpenVMS or any
> other operating system except for those explicitly supported (and
> tested) by the dev team. Java isn't truly write-once run-anywhere,
> despite such claims ~10-15 years back.
>
> I looked at your stacktrace and the problem seemed to be related to a
> NumberFormatException thrown by java.lang.Long.parseLong() that is not
> being caught and handled by Lucene:
>
> Caused by: java.lang.NumberFormatException: For input string: "1."
>        at 
> java.lang.NumberFormatException.forInputString(NumberFormatException.java:48)
>        at java.lang.Long.parseLong(Long.java:419)
>        at 
> org.apache.lucene.index.SegmentInfos.generationFromSegmentsFileName(SegmentInfos.java:199)
>
> I found a Lucene JIRA issue that is loosely related:
> https://issues.apache.org/jira/browse/LUCENE-3008
>
> Looks like line 211 in trunk is the issue (was line 199 in the stacktrace):
> http://svn.apache.org/viewvc/lucene/dev/trunk/lucene/src/java/org/apache/lucene/index/SegmentInfos.java?view=markup
>
> The source code is:
>   return 
> Long.parseLong(fileName.substring(1+IndexFileNames.SEGMENTS.length()),
>      Character.MAX_RADIX);
>
> A quick look at the Java API shows:
> http://download.oracle.com/javase/1,5.0/docs/api/java/lang/Long.html#parseLong(java.lang.String,%20int)
>  An exception of type NumberFormatException is thrown if any of the
> following situations occurs:
>    * Any character of the string is not a digit of the specified
> radix, except that the first character may be a minus sign '-'
> ('\u002d') provided that the string is longer than length 1.
>
> The decimal character in the string "1." is not valid in the radix
> defined by Character.MAX_RADIX. So, you'll need to figure out where
> that filename of "1." is coming from -- either OpenVMS or Lucene --
> and somehow get rid of the decimal in the filename. Or just rename
> that file from 1. to simply 1 in your filesystem.
>
> Without access to an OpenVMS system and having no real understanding
> of Lucene's internals, I can't really look into it any more at this
> point. You probably need to email the Lucene Users list and ask if
> anyone has successfully gotten it to run on OpenVMS (I'm guessing not)
> and get things patched up before you can make more progress with
> getting Nexus running on it. Or take the more reasonable approach and
> simply install Nexus on a Windows box in your office. ;-)
>
> Wayne
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>



-- 
Tim Pizey - http://pizey.net/~timp
Centre for Genomics and Global Health - http://cggh.org

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

Re: How to use latest versions of all dependencies and plugins

[Tim Pizey]

On 20 August 2011 10:45, Ansgar Konermann
 wrote:
>
> Am 20.08.2011 11:37 schrieb "Tim Pizey" :
>>
>> Hi,
>>
>> I see from
>> https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-PluginMetaversionResolution
>>
>> Plugin Metaversion Resolution
>> Internally, Maven 2.x used the special version markers RELEASE and
>> LATEST to support automatic plugin version resolution. These
>> metaversions were also recognized in the  element for a
>>  declaration. For the sake of reproducible builds, Maven 3.x
>> no longer supports usage of these metaversions in the POM. As a
>> result, users will need to replace occurrences of these metaversions
>> with a concrete version.
>>
>> What is the right way now to cover the developers use case where I
>> want to discover and use the latest version of everything,
>> see what breaks, fix and upgrade to latest.
>
> One option is to use maven-version-plugin to update dependency/parent
> versions, potentially on a branch dedicated for this purpose, run mvn clean
> verify on your ci server for this branch and see if/what breaks. If all your
> tests are still green, merge the poms of this branch into your main line. If
> you preferr one single development line, omit the dedicated branch.
>


Great, thanks Ansgar

cheers
Tim

-- 
Tim Pizey - http://pizey.net/~timp
Centre for Genomics and Global Health - http://cggh.org

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

How to use latest versions of all dependencies and plugins

[Tim Pizey]

Hi,

I see from 
https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-PluginMetaversionResolution

Plugin Metaversion Resolution
Internally, Maven 2.x used the special version markers RELEASE and
LATEST to support automatic plugin version resolution. These
metaversions were also recognized in the  element for a
 declaration. For the sake of reproducible builds, Maven 3.x
no longer supports usage of these metaversions in the POM. As a
result, users will need to replace occurrences of these metaversions
with a concrete version.

What is the right way now to cover the developers use case where I
want to discover and use the latest version of everything,
see what breaks, fix and upgrade to latest.

I can see that using LATEST was not the right solution, is there a
command line flag?


cheers
Tim







-- 
Tim Pizey - http://pizey.net/~timp
Centre for Genomics and Global Health - http://cggh.org

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

Re: How to run tests in jetty

[Tim Pizey]

On 18 May 2011 18:19, Victor Grazi  wrote:
> Hi - I am wondering if there is any way to tell maven 3 to launch jetty and
> then execute some unit testers, and finally tear down jetty?
>
> What is the best way to do this?

http://docs.codehaus.org/display/JETTY/Maven+Jetty+Plugin
Automatic execution of the plugin

cheers
Tim

-- 
Tim Pizey - http://pizey.net/~timp
Centre for Genomics and Global Health - http://cggh.org

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

Re: Maven 3.0.3 hanging / having timeouts often?

[Tim Pizey]

On 12 May 2011 11:50, Alex Lopez  wrote:
>
> Em 12-05-2011 01:22, Andrew Robinson escreveu:
>>
>> I have been using maven 2.2.1 for a while at my company and we just
>> switched
>> to maven 3. I have rebuilt my computer (ubuntu maverick 10.04 32-bit ==>
>> ubuntu natty 11.04 64-bit) and installed maven 3.
>>
>> In maven 3.0.3, (I have not seen it with maven 2.2.1), it stops
>> downloading
>> after a few to several downloads. If I ^C the build, and keep re-running
>> it,
>
> +1, I've been having this kind of 'hangs', using maven 3.0.2 and artifactory
> 2.3.1 (sometimes when running maven site, sometimes performing a build),
> then ^C seems to get maven to continue doing what it was doing and
> eventually end with success...

Me too, on win7/cygwin. I thought it was a cygwin problem.

cheers
-- 
Tim Pizey - http://pizey.net/~timp
Centre for Genomics and Global Health - http://cggh.org

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

Re: Maven3 missing dependency message is no longer helpful

[Tim Pizey]

On 10 May 2011 10:42, Tim Pizey wrote:
> Hi,
>
> In Maven2 when a dependency could not be found in any repository
> then there was a helpful message giving the command to install locally
> of deploy to your repository.
>
> Please can we have it back?

How can one now deploy to a repository using scp from the command line?


mvn deploy:deploy-file -Durl=scp://paneris.net/data/www/ /
-DrepositoryId=paneris -Dfile=lib/grddl.jar -DgroupId=com.hp.hpl.jena /
-DartifactId=grddl -Dversion=0.3 -Dpackaging=jar

Fails as scp is no longer supported, but there is nowhare to
add the configuration.

The loss of scp is proving a big problem to me.

Thanks for any help

Tim




-- 
Tim Pizey - http://pizey.net/~timp
Centre for Genomics and Global Health - http://cggh.org

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

Maven3 missing dependency message is no longer helpful

[Tim Pizey]

Hi,

In Maven2 when a dependency could not be found in any repository
then there was a helpful message giving the command to install locally
of deploy to your repository.

Please can we have it back?

cheers
Tim

-- 
Tim Pizey - http://pizey.net/~timp
Centre for Genomics and Global Health - http://cggh.org

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

Re: search.maven.org working for you

[Tim]

Works fine for me on an MBP downforeveryoneorjustme also says it's down.
Probably just a bug on their end.

On Fri, May 6, 2011 at 9:03 AM, John Patrick  wrote:

> Just wondering anyone else using a Mac, if so does
> http://search.maven.org/ display anything for you when you click
> Search, or Advanced Search, or Browse or Quick Stats.
>
> Is it just my MacBook Pro, Mac's or everyone. Also
> http://www.downforeveryoneorjustme.com/search.maven.org reports the
> site as down, is that n purpose its blocked.
>
> I've tried the follow all on my MacBook Pro, everything has latest
> patches...
> Firefox 4
> Chrome
> Safari
>
> Cheers,
> John
>
> -
> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
> For additional commands, e-mail: users-h...@maven.apache.org
>
>

Re: overriding goal's configuration from command line?

[Tim Kettler]

Hi,

you can look that up in the documentation of the goal [1]. If an 
expression is defined for a parameter that is what you can use as a 
property on the commandline. In your example: -Dmaven.compiler.source=1.5


-Tim

[1] http://maven.apache.org/plugins/maven-compiler-plugin/compile-mojo.html

Am 14.04.2011 12:16, schrieb amaresh mourya:

Hi,

How do I override compiler source to be used If I run mvn compiler:compile
from the command line.

Compiler:compile goal has parameter called source. Doesn't that mean If I
run
[ mvn compiler:compile -Dsource=1.5 ] it should use 1.5 instead of 1.6?

My POM is like :


http://maven.apache.org/POM/4.0.0";>
 4.0.0
 Application6
 mavenProj
 1.0-SNAPSHOT
 Project for mavenProj
 
 
 
 org.apache.maven.plugins
 maven-compiler-plugin
 2.0.2
 
 1.6
 1.6
 
 
   




thanks
--Amaresh

On Thu, Apr 14, 2011 at 3:22 PM, Stephen Connolly<
stephen.alan.conno...@gmail.com>  wrote:


what you can do in that case is define properties in the pom and use
those properties to define the default-cli values.

properties set via the CLI override properties declared in the POM.

  http://maven.apache.org/POM/4.0.0";>
 4.0.0
 Application6
 mavenProj
 1.0-SNAPSHOT
 Project for mavenProj
 
welcome
chandan
 
 
 
  
 MyPlugins
 hiPlugin
 1.0
 
 
default-cli
 
 hi
 
  
  ${greetings}
  ${person}
 
 
 
 
 
 
  
  
  
  

Note that the property names do not have to be the same as the
@parameter expression="${myplugin.greeting}"  style
default properties you specified in your mojo, but usually you would
keep them the same... unless you are relying on those properties for
the lifecycle-invoked goals

-Stephen

On 14 April 2011 10:28, amaresh mourya  wrote:

Hi All,

I have a POM which has a plugin. I have configured it to use some

specific

settings at the time of command line invocation of the goal. I set these
configurations in execution ID as "default-cli".

This MyPlugins:hiPlugin:1.0:hi goals just prints the output in format of

:

${person} says ${greetings}
When I ran goal (MyPlugins:hiPlugin:1.0:hi) on command line I got the
expected output that was : "Chandan says Welcome"
But My question is why am I not able to override these configurations

from

command line, I wanted to run goal with parameter

(MyPlugins:hiPlugin:1.0:hi

-Dperson=Vishal) to get the output as "Vishal says Welcome". But I am

still

getting output "Chandan says Welcome".

Here is my POM.

http://maven.apache.org/POM/4.0.0";>
4.0.0
Application6
mavenProj
1.0-SNAPSHOT
Project for mavenProj


 
MyPlugins
hiPlugin
1.0


   default-cli

hi

 
 welcome
 chandan












Thanks,
Amaresh







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

Re: Missing artifact org.apache.cxf

[Tim Kettler]

I should have expressed myself more clearly. The preferred solution is 
just to omit the  element. and declare the dependency like Stuart 
showed in his mail:



   org.apache.cxf
   cxf-bundle
   2.3.3
 

This should work. Only declare the maven-bundle-plugin if you have a 
good reason to do so.


The attachment you sent was stripped from your mail somewhere and didn't 
reach the list. If you haven't got it working by now, you can paste it 
to pastebin.com and share the link, so that we can have a look.


-Tim

Am 12.04.2011 15:32, schrieb HIRRI El Houssein Amine:

Dear Stuart McCulloch,
I already use


org.apache.cxf
cxf-bundle
2.3.3


in my file (you can check the attached file to my previous post), and the
problem persist, but when I add the plugin 'maven-bundle-plugin the problem
seem to be solved

--
View this message in context: 
http://maven.40175.n5.nabble.com/Missing-artifact-org-apache-cxf-tp4297947p4298193.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
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: Missing artifact org.apache.cxf

[Tim Kettler]

In fact, the artifact in question is an osgi bundle build with the 
maven-bundle-plugin and as such has the packing set to 'bundle'.


Normally one refers to such artifacts just like normal 'jar' artifacts 
omitting the type.


If you need to refer to them as 'bundle' artifact you need to add the 
maven-bundle-plugin to the  section of your pom and add 
true to make maven aware of the non standard 
packaging.


-Tim

Am 12.04.2011 14:45, schrieb Anders Hammar:

There is no such artifact with packaging 'bundle' I believe. You should
probably change to 'jar'.
Where are you getting the incorrect info from?

/Anders

On Tue, Apr 12, 2011 at 14:43, HIRRI El Houssein Amine
wrote:


Thank you all for your replay,
I just changed the cxf version to 2.3.3 but, I still have the same problem.
I also removed the .m2/repository folder, and then a new one was created
with a lot of jars, but the one for cxf-bundle contain no jar file.

Here is the error message:
12/04/11 13:37:38 GMT: Missing artifact
org.apache.cxf:cxf-bundle:bundle:2.3.3:compile
12/04/11 13:37:38 GMT: Missing artifact
com.sun.xml.bind:jaxb-xjc:jar:2.2.1.1:compile
12/04/11 13:37:38 GMT: Missing artifact
org.bouncycastle:bcprov-jdk15:jar:1.45:runtime

Attached is my file
http://maven.40175.n5.nabble.com/file/n4298099/pom.xml
pom.xml


--
View this message in context:
http://maven.40175.n5.nabble.com/Missing-artifact-org-apache-cxf-tp4297947p4298099.html
Sent from the Maven - Users mailing list archive at Nabble.com.

-
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: How to get my plugin to execute in a particular phase?

[Tim Kettler]

Am 12.04.2011 01:50, schrieb Hilco Wijbenga:

Hi all,


Hi,


I'm following the online documentation to write a plugin
(http://maven.apache.org/guides/mini/guide-configuring-plugins.html).
I have

package sample.plugin;

import org.apache.maven.plugin.AbstractMojo;
import org.apache.maven.plugin.MojoExecutionException;

/**
  * Says "Hi" to the user.
  *
  * @goal sayhi
  * @phase generate-sources
  */
public class GreetingMojo extends AbstractMojo {
   /**
* The greeting to display.
*
* @parameter expression="${sayhi.greeting}" default-value="Hello World!"
*/
   private String greeting;

   /**
* @execute phase="generate-sources"
*/


The @execute invokes a parallel build of the project, up to the 
specified phase. Is that really what you want?



   @Override
   public void execute() throws MojoExecutionException {
 getLog().info(greeting);
   }
}

This works if I invoke the plugin directly (i.e. mvn greeting:sayhi).
I have it configured as


   org.example.maven.plugins
   greeting-maven-plugin
   0.1-SNAPSHOT
   
 Howdy!
   


so it prints "Howdy!". Excellent, so far.

But despite the "@phase generate-sources" and "@execute
generate-sources" I cannot get it to run in the generate-sources phase
by simply invoking something like "mvn compile". (I'm using Maven
3.0.3 and maven-plugin-api 3.0.)

How do I get the greeting plugin to run (by default) in a particular
phase? (I know I can use  to configure it explicitly but
the documentation seems to indicate I can configure a default phase.)


From the Mojo API Specification [1]:

"
@phase:
Defines a default phase to bind a mojo execution to if the user does not 
explicitly set a phase in the POM. Note: This annotation will not 
automagically make a mojo run when the plugin declaration is added to 
the POM. It merely enables the user to omit the  element from the 
surrounding  element.

"

To execute a goal you must declare an execution somewhere, either in the 
projects pom or in a parent. The only way around this is to create a 
custom packaging [2] and bind the goal to a lifecycle phase for the 
packaging



Cheers,
Hilco


-Tim

[1] http://maven.apache.org/developers/mojo-api-specification.html
[2] 
http://www.sonatype.com/books/mvnref-book/reference/writing-plugins-sect-plugins-lifecycle.html


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

Re: Reuse of configuration

[Tim Kettler]

Am 12.04.2011 00:50, schrieb emerson:

All my CI configuration is done in a profile (build and report
plugins). This is so that I have the option to not generate the
reports when running an "on demand" CI, and to generate only during
nightly builds.

As all my projects will have the same number of reports and site
related build configuration, I wanted to keep it inside a profile.

I read somewhere that the profiles can't be inherited. If this is
correct, what is the approach recommended to not have to repeat this
same configuration in every single project?


You are right, profiles are not inherited per se. AFAIK, when maven 
calculates the effective pom for an execution it will parse the parent 
pom and if it includes a profile to be activated, apply it. This 
interpolated parent pom is the basis for what is inherited to the child.


So you can just put your CI related config in a profile in a parent pom 
and activate it when building a child. This will work just like you 
would expect.



thanks
Emeson


-Tim

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

Re: source:jar includes resources; source:test-jar does not; similarly fo jar:jar and jar:test-jar

[Tim Kettler]

Hi,

Am 11.04.2011 13:00, schrieb sebb:

I'm trying to add source and binary test jars to a project.

Now source:jar works fine; it picks up N&L from the  section.

However, source:test-jar appears to ignore the  section -
is that intentional, or an oversight? In any case, how does one get it
to add the resources?

Similarly for the binary test jar - it does not seem to want to
include the resources.


Yes, that's how it works AFAIK. source:jar includes the resources from 
the  section and source:test-jar includes the resources from 
the  section. Same for the jar plugin. Makes sense to me.



How do I fix these issuse


If you absolutely need to include the non-test resources the best way to 
go is probably to use the assembly plugin and create a custom assembly 
descriptor.


-Tim

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

Re: Default phase of a plugin

[Tim Kettler]

Am 11.04.2011 10:39, schrieb amaresh mourya:

Hi All,


Hi,


I created my own plugin and bind a goal to 'install' phase via '@phase
install' in the goal's MOJO. My question is if I run this goal via
myPlugin:Mygoal in command line, will it execute all the previous phases? I
am expecting all phases above install to be exceuted, that are
(validate,compile,test,package, integration-test, verify etc).


No, if you run maven with a single goal given in the commandline it will 
just execute that goal. Nothing else.




I am hoping this to happen because same thin happens when we run 'mvn
package', it executes all the previous phases before package. On the
contrary I found this link over the discussion and I got confused.
http://www.mail-archive.com/users@maven.apache.org/msg105538.html

If any goal ran from the command line doesn't go through lifecycle phase
then how mvn package executes all the previous phases of it.


You've got that wrong. 'package' isn't a *goal* but a *phase* in the 
default build lifecyle [1]. When you invoke a phase, all phases before 
are executed, too.



Thanks
--Amaresh



-Tim

[1] 
http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html


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

Re: is confusing me..

[Tim Kettler]

The documentation is a little bit ambigious. What it means is:

In  you specify the default configuration and versions 
of plugins used unless explicitly overwritten. Think of it as a 
template. No plugin goal is executed just because you mention it in 
 section.


To actually execute a plugin you need to reference it in the 
 section of a (inheriting) pom or, as you have propably 
done invoke it explicitly via 'mvn myplugin:mygoal'. Either way, the 
configuration from the  section is picked up.


-Tim

Am 11.04.2011 08:18, schrieb amaresh mourya:

But its in  section. maven documentation says it won't be
available to child POM unless I specify that plugin in  section.

Please see following lines in my previous discussions:

*PluginManagement does ONE THING ONLY (essentially).
It provides a central location for all of your plugin versioning and
configuration.
THAT'S IT.

You still need to declare the  in the  section of your
various poms (children or parents) where you actually want to USE any
of those plugins in your build.*


http://www.mail-archive.com/users@maven.apache.org/msg115850.html


thanks
--Amaresh

On Mon, Apr 11, 2011 at 11:43 AM, Charles Williamswrote:


amaresh,

you include the plugin in the "Parent" therefore it is automatically
available in the child.

chuck


On 04/11/2011 08:08 AM, amaresh mourya wrote:


Hi I have a parent pom and a child POM.

*Parent POM is like : *


http://maven.apache.org/POM/4.0.0";>
 4.0.0
 Application6
 Application6
 1.0-SNAPSHOT
 
 mavenProj
 
 pom
 
 
 
 
 MyPlugins
 hiPlugin
 1.0
 
 welcome
 
 
 
 
 
 
 
 228655859
 hosted
 http://localhost/hostedRepo/
 
 



*And Child POM is : *


http://maven.apache.org/POM/4.0.0";>
 4.0.0
 Application6
 mavenProj
 1.0-SNAPSHOT
 Project for mavenProj
 
 Application6
 Application6
 1.0-SNAPSHOT
 


Please note that I have created a maven plugin (hiPlugin) that takes a
string via   and just shows it.

*Question : My question is when I rum this plugin's goal on the child POM
I
am getting the output. I was expecting nothing to happen since I haven't
specified

 MyPlugins
 hiPlugin

  section in my child POM. And the maven documentation also says you won't
be
able to run any plugin defined the the plugiManagement section unless you
specify that plugin in child POM. here is the link :
http://maven.apache.org/pom.html#Plugin_Management



Thanks,
Amaresh
**
*




-
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