RE: maven 3 multi-module site

I added plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-project-info-reports-plugin/artifactId version2.2/version reportSets reportSet reports reportindex/report /reports /reportSet /reportSets /plugin to the reportPlugins

Re: NoClassDefFoundError when running maven-exec-plugin and Cobertura

We had the same problem. Solution was to add cobertura dependency to the instrumented component. So, just try adding dependency groupIdnet.sourceforge.cobertura/groupId artifactIdcobertura/artifactId version1.9.4.1/version /dependency to your pom and try again. Make

[ANN] Sonar Maven Plugin 2.0-beta-1

Hi, The Mojo team is pleased to announce the release of the Sonar Maven Plugin version 2.0-beta-1. It adds compatibility with Maven 3 when using Sonar 2.4. You can see more about the plugin at: http://mojo.codehaus.org/sonar-maven-plugin/ Release notes :  - [MOJO-1545] support Maven 3. Enjoy,

Re:

Thanks, Benjamin Here it is: [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 1:17.232s [INFO] Finished at: Wed Nov 17 11:02:48 IST 2010

Re: Re:

And here's the full log attached (-X -e turned on): https://dl.dropbox.com/s/j5v14ghotjr2cap/log2.zip?dl=1 - Best regards, Evgeny http://evgeny-goldin.com/ -- View this message in context:

[m3] property ${project.build.directory} returns defect path

Hello, I use Maven v3.0.0 and would like to use the property ${project.build.directory} inside commandlineArgs of the exec-maven-plugin. My configuration looks like this: plugin groupIdorg.codehaus.mojo/groupId artifactIdexec-maven-plugin/artifactId version1.1/version executions

Re: [m3] property ${project.build.directory} returns defect path

Hello, I tested your configuration and it works fine for me (Apache Maven 3.0 and exec-maven-plugin-1.0) First, you can execute : mvn help:effective-pom You will see the real path returned by the property ${project.build.directory}. 2010/11/17 Lars Fischer lfisc...@fastmail.fm Hello, I use

Re:

Evgeny Goldin wrote: [ERROR] urls[65] = file:/C:/Users/evgeny/.m2/repository/plexus/plexus-utils/1.0.2/plexus-utils-1.0.2.jar [ERROR] urls[70] = file:/C:/Users/evgeny/.m2/repository/org/codehaus/plexus/plexus-utils/2.0.5/plexus-utils-2.0.5.jar A classpath conflict, your plugin has a

Forbid users to use a certain artifact and/or version

Hi all, For one of my customers, I have to come up with a solution to have maven completely ignore certain artifacts and/or versions. Does anybody have any ideas on how to do this? I was thinking about using a preant-POM and the enforcer-plugin, but as soon as I make an update, all projects

Re: Forbid users to use a certain artifact and/or version

2010/11/17 Asmann, Roland roland.asm...@adesso.at: Does anybody have any ideas on how to do this? I was thinking about using a preant-POM and the enforcer-plugin, but as soon as I make an update, all projects would have to update their parents as well -- which is exactly what they don't want,

Re: [m3] property ${project.build.directory} returns defect path

Hello Maxime, 2010/11/17 Maxime Gréau greaumax...@gmail.com I tested your configuration and it works fine for me (Apache Maven 3.0 and exec-maven-plugin-1.0) First, you can execute : mvn help:effective-pom You will see the real path returned by the property ${project.build.directory}.

Re: [m3] property ${project.build.directory} returns defect path

I switched to exec-maven-plugin version 1.2. But now I get an error: [ERROR] Failed to execute goal org.codehaus.mojo:exec-maven-plugin:1.2:exec (test2) on project test.test: Command execution failed. Cannot run program echo (in directory D:\development\projects\test) Kind regards, Lars

Re: Forbid users to use a certain artifact and/or version

I fully agree with you, but as the saying goes 'the customer is king'... Ah well, I'll give it another couple of days to tinker around and if nothing else works, I'll tell them to just enforce one of the changes. On 17.11.2010 11:43, Antonio Petrelli wrote: 2010/11/17 Asmann, Roland

Re: [m3] property ${project.build.directory} returns defect path

The windows path bug is fixed in 1.2: http://jira.codehaus.org/browse/MEXEC-81 Kind regards, Lars

Re: [m3] property ${project.build.directory} returns defect path

ok, it's good to know. Maxime. 2010/11/17 Lars Fischer lfisc...@fastmail.fm The windows path bug is fixed in 1.2: http://jira.codehaus.org/browse/MEXEC-81 Kind regards, Lars

Re: Forbid users to use a certain artifact and/or version

2010/11/17 Asmann, Roland roland.asm...@adesso.at: I fully agree with you, but as the saying goes 'the customer is king'... Just curious, the customer develops too? Antonio - To unsubscribe, e-mail:

Re: Forbid users to use a certain artifact and/or version

I possible solution if they already use Nexus, is to upgrade to Nexus Pro and use the procurement feature. Then they can easily block specific artifacts, effectively forcing the developers to change their dependencies. Otherwise they will not be able to build...very effective! :-) /Anders On

Range resolution changed from 2.1?

Hi citing a mail from the wicket-user list, as it has nothing to do with the artifact resolved: All is fine as long as I specify a certain version, e.g. 1.4.13 But using a version range does not work, e.g. [1.4.10,1.5) well, that´s just spooky! i tried to reproduce this and while

Re: Forbid users to use a certain artifact and/or version

Yes, the customer in this case is a larger company that is starting to use Maven, or at least, starting to use it correctly now. On 17.11.2010 12:29, Antonio Petrelli wrote: 2010/11/17 Asmann, Roland roland.asm...@adesso.at: I fully agree with you, but as the saying goes 'the customer is

Re: Forbid users to use a certain artifact and/or version

Now that is useful info! I hadn't looked at the Pro version yet, but they were already discussing buying it because of better security measures. Thanks! On 17.11.2010 12:34, Anders Hammar wrote: I possible solution if they already use Nexus, is to upgrade to Nexus Pro and use the procurement

The POM for com.google.gwt:gwt-incubator:jar:2.0.1

Hi everyone. Has anyone else seen this: [WARNING] The POM for com.google.gwt:gwt-incubator:jar:2.0.1 is invalid, transitive dependencies (if any) will not be available, enable debug logging for more details browsing to:

Re: Forbid users to use a certain artifact and/or version

If you only wish to limit artifact downloads based on path information then this is already possible to do in Artifactory OSS version by using include/exclude patterns. If you wish to have more elaborate control then in Artifactory Pro you can use a custom groovy plugin to veto remote downloads

RSA fingerprint problem..

Hi, I'm trying to publish my first release.. running the release:perfom command, but, the shell stop here : [INFO] The authenticity of host '10.121.200.245' can't be established. [INFO] RSA key fingerprint is 03:2a:25:11:bd:c5:5c:39:ca:9f:25:b9:ae:8b:51:23. So, I did those corrections : I added

Re: RSA fingerprint problem..

ssh once interactively and answer the question. On Wed, Nov 17, 2010 at 9:22 AM, jeb001 jeremy.jar...@gmail.com wrote: Hi, I'm trying to publish my first release.. running the release:perfom command, but, the shell stop here : [INFO] The authenticity of host '10.121.200.245' can't be

New version of Eclipse from Springsource

I know that everyone thinks that I must have shares in Springsource/VMWare but I just find that it is the best way to run Eclipse and build web applications. There is a new version available. Look at the datasheet at the bottom of the page on this link.

Re: New version of Eclipse from Springsource

On Wed, Nov 17, 2010 at 9:31 AM, Ron Wheeler rwhee...@artifact-software.com wrote: I know that everyone thinks that I must have shares in Springsource/VMWare but I just find that it is the best way to run Eclipse and build web applications. There is a new version available. Look at the

Maven site error with version range

I have a Maven project that declares a dependency on another Maven artifact using an open ended version range, such as this: dependency groupIdorg.terracotta.toolkit/groupId artifactIdterracotta-toolkit-1.0/artifactId version[1.0.0-SNAPSHOT,]/version /dependency (I

RE: Forbid users to use a certain artifact and/or version

-Original Message- From: Antonio Petrelli [mailto:antonio.petre...@gmail.com] 2010/11/17 Asmann, Roland roland.asm...@adesso.at: Does anybody have any ideas on how to do this? I was thinking about using a preant-POM and the enforcer-plugin, but as soon as I make an update, all projects

Re: Maven site error with version range

On 2010-11-17 16:54, Jason Voegele wrote: I have a Maven project that declares a dependency on another Maven artifact using an open ended version range, such as this: dependency groupIdorg.terracotta.toolkit/groupId artifactIdterracotta-toolkit-1.0/artifactId

Re: Re:

Ah, I should have seen it by myself. Thanks! I will add the exclusion. - Best regards, Evgeny http://evgeny-goldin.com/ -- View this message in context: http://maven.40175.n5.nabble.com/An-API-incompatibility-was-encountered-for-using-plexus-utils-tp3265343p3269467.html Sent from the

How to verify a jar in Maven after it is packaged?

I have a scenario, where in I need to sanity check the generate jar for duplicate entries. I have a seperate implementaion that does the sanity check, but how do I use that class to verify the jar? It would be nice if I can run a test to verify the jar's integrity but the test phase occurs before

Re: How to verify a jar in Maven after it is packaged?

Ideally, you would write a plugin goal and bind it to the verify phase. But if you don't want to do that, you can use the exec plugin to execute some arbitrary Java class (again, in the verify phase). See http://mojo.codehaus.org/exec-maven-plugin/ for details on the exec plugin. Justin On Wed,

Re: Range resolution changed from 2.1?

AFAIK the changes to range resolution were reverted, tho I've never used mixed level numbers, we use [1.3.19,2.0.0) - always to the three levels. Mark -- Great artists are extremely selfish and arrogant things — Steven Wilson, Porcupine Tree On Thu, Nov 18, 2010 at 12:03 AM, uwe schaefer

shade plugin duplicated classes?

Hi, I am using the shade plugin when doing an mvn assembly:assembly to create an uber jar which includes my project and all supporting jars. The resulting JAR is quite large and when I do a jar -tvf | grep someclassname.class I always get 2 entries returned for EVERY CLASS. The sizes are the

Re: Range resolution changed from 2.1?

On 11/17/2010 07:22 PM, Mark Derricutt wrote: Hi Mark, AFAIK the changes to range resolution were reverted, tho I've never used mixed level numbers, we use [1.3.19,2.0.0) - always to the three levels. in the case looked at, even those do not work as expected 1.4.9 1.4.10 not to mention

Problem with release plugin versions

Hi all, This morning I attempted to perform a release using maven v 2.2.1 (r801777; 2009-08-07 07:16:01+1200). Maven downloaded new versions of all my plugins, and now I receive the following error when trying to perform a mvn release:prepare mvn release:perform [INFO]

[ANN] Maven Wagon 1.0-beta-7 Released

The Maven team is pleased to announce the release of the Maven Wagon, version 1.0-beta-7 Maven Wagon is a transport abstraction that is used in Maven's artifact and repository handling code. http://maven.apache.org/wagon/ Release Notes - Maven Wagon - Version 1.0-beta-7 ** Bug *

Re: Problem with release plugin versions

Try mvn help:effective-pom to see if you've locked in the version. Otherwise, we would need to know if you were using a repository manager. - Brett On 18/11/2010, at 7:38 AM, Todd Nine wrote: Hi all, This morning I attempted to perform a release using maven v 2.2.1 (r801777; 2009-08-07

Re: New version of Eclipse from Springsource

This seems off-topic for the Maven list? On 18/11/2010, at 2:31 AM, Ron Wheeler wrote: I know that everyone thinks that I must have shares in Springsource/VMWare but I just find that it is the best way to run Eclipse and build web applications. There is a new version available. Look at

RE: New version of Eclipse from Springsource

Ron any updates for maven-eclipse-plugin..if so which version? please ping me offline as eclipse is considered O/T for maven thanks, Martin Gainty __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist

Re: New version of Eclipse from Springsource

On 18/11/2010, at 9:51 AM, Brett Porter wrote: This seems off-topic for the Maven list? Perhaps not. I like the fact that STS comes bundled with Maven 2.2.1 and m2e. If you're a Maven developer then this is a good IDE bundle. Kind regards, Christopher

Re: Problem with release plugin versions

Hi Brett, There wasn't any version in my pom. I believe I've found the issue. I had a repository that connected to github, which is issuing 301 redirects. This bug is the underlying issue http://jira.codehaus.org/browse/WAGON-314 Maven is downloading the http response as the pom.xml, which

Re: New version of Eclipse from Springsource

This seems off-topic for the Maven list? Perhaps not. I like the fact that STS comes bundled with Maven 2.2.1 and m2e. If you're a Maven developer then this is a good IDE bundle. I personally don't particularly mind the occasional Maven-related announcement like this, and believe there are a

Deploying properties files.

Hi, In my project I have a lot of *.properties files as well as some third party *.exe files. I know that using resources plugin I'm able to copy all this stuff to my target directory. What about deploying this things from target dir to remote repository ? I couldn't find any function that

Re: Deploying properties files.

On Wed, Nov 17, 2010 at 8:25 PM, asdas adasads zestriddle123...@gmail.com wrote:    In my project I have a lot of *.properties files as well as some third party *.exe files. I know that using resources plugin I'm able to copy all this stuff to my target directory. What about deploying this

Re: Deploying properties files.

It would help if you elaborate what you are exactly trying to achieve. To install arbitrary artifacts to the repository, you can use build-helper-maven-plugin http://mojo.codehaus.org/build-helper-maven-plugin/attach-artifact-mojo.html Kalpak Hi, In my project I have a lot of

Re: New version of Eclipse from Springsource

On 17/11/2010 6:42 PM, Wayne Fay wrote: This seems off-topic for the Maven list? Perhaps not. I like the fact that STS comes bundled with Maven 2.2.1 and m2e. If you're a Maven developer then this is a good IDE bundle. I personally don't particularly mind the occasional Maven-related