Re: I have the right version, but maven can't find it

2010-04-28 Thread Anders Hammar
Just for clearity, that should be done through the dependencyManagament section. depMgmt impacts transitive deps as well. /Anders On Wed, Apr 28, 2010 at 04:08, Justin Edelson justinedel...@gmail.comwrote: Perhaps it is defined in a parent pom. In any case, you can fix this easily by setting

Re: Clearcase with maven release plugin

2010-04-28 Thread Anders Hammar
However, it does only work on the 'main' branch. What do you mean by it only works on the 'main' branch? What are the limitations? The mail you've found is old and I wrote it when I had just started to use the release plugin with clearcase. Since then I've learned more on using that

junit 4.8.1 - org.junit cannot be resolved

2010-04-28 Thread ykyuen
i try to use junit 4.8.1 in my maven project by adding the following dependency in the pom.xml dependency groupIdjunit/groupId artifactIdjunit/artifactId version4.8.1/version scopetest/scope /dependency when i try to write the test case, the org.junit cannot be resolved(i.e. error at

Clearcase with Maven

2010-04-28 Thread Rajesh Kumar
Hi, I am using Clearcase UCM and i am looking for pom.xml sample which does the following things. 1. Create A View with tag specified in pom.xml 2. Check the View Status 3. Clean the View and Create A New View * Any help on this...* -- === Rajesh Kumar Configuration,

Fortify and Maven

2010-04-28 Thread Anders Hammar
I was asked about integrating Fortify (Fortify 360) in the Maven build process. Anyone here with any experience of that? A found an open source Maven plugin, but someone said that Fortify has one of their own... /Anders

Re: I have the right version, but maven can't find it

2010-04-28 Thread Jörg Schaible
Hi Grant, Grant Birchmeier wrote: If anyone can help, I'd appreciate it. This is driving me up the wall. I tried googling, but I couldn't find what I needed. When I build, I get this error: --- Couldn't find a version in [1.2.15, 1.2.16] to match range [1.2.13,1.2.13]

Maven javadoc plugin error

2010-04-28 Thread Saif Kamaal Abulkhair
Hi Maven Experts, I have been trying to generate java docs using the following configuration (see below for pom.xml) and running the command (mvn site, mvn javadoc:javadoc, mvn javadoc,aggregate) and I am getting this error [INFO] Scanning for projects... [INFO]

Re: junit 4.8.1 - org.junit cannot be resolved

2010-04-28 Thread Dirk Olmes
On 04/28/2010 08:46 AM, ykyuen wrote: i try to use junit 4.8.1 in my maven project by adding the following dependency in the pom.xml dependency groupIdjunit/groupId artifactIdjunit/artifactId version4.8.1/version scopetest/scope /dependency when i try to write the test

Re: junit 4.8.1 - org.junit cannot be resolved

2010-04-28 Thread Raphael Ackermann
But it is available in central. http://repository.sonatype.org/index.html#nexus-search;gav~~junit~4.8.1~~ we have been using it for at least a week now. Raphael On Wed, Apr 28, 2010 at 09:59, Dirk Olmes d...@xanthippe.ping.de wrote: On 04/28/2010 08:46 AM, ykyuen wrote: i try to use junit

Re: junit 4.8.1 - org.junit cannot be resolved

2010-04-28 Thread Tony Chemit
Le Wed, 28 Apr 2010 09:59:05 +0200, Dirk Olmes d...@xanthippe.ping.de a écrit : On 04/28/2010 08:46 AM, ykyuen wrote: i try to use junit 4.8.1 in my maven project by adding the following dependency in the pom.xml dependency groupIdjunit/groupId artifactIdjunit/artifactId

Re: junit 4.8.1 - org.junit cannot be resolved

2010-04-28 Thread ykyuen
Yes. i can see the junit-4.8.1.jar in Maven Dependencies of my eclipse project. so i am sure the maven did download the 4.8.1 jar. Tony Chemit wrote: Le Wed, 28 Apr 2010 09:59:05 +0200, Dirk Olmes d...@xanthippe.ping.de a écrit : On 04/28/2010 08:46 AM, ykyuen wrote: i try to use

Re: junit 4.8.1 - org.junit cannot be resolved

2010-04-28 Thread Nick Stolwijk
It seems the 4.8.1 version in central is borked. It doesn't contain any classes. That would explain why your imports can't be resolved. I don't know who did the upload of this artifact, but it is certainly wrong. With regards, Nick Stolwijk ~Java Developer~ IPROFS BV. Claus Sluterweg 125 2012

Re: junit 4.8.1 - org.junit cannot be resolved

2010-04-28 Thread Nick Stolwijk
It seems there has been a faulty upload [1] but it was fixed later. For example, [2] has the right version of junit 4.8.1. I wouldn't trust this release with maven. Based on your mirror you can get the borked version. [1]

Re: junit 4.8.1 - org.junit cannot be resolved

2010-04-28 Thread Tony Chemit
Le Wed, 28 Apr 2010 10:52:48 +0200, Nick Stolwijk nick.stolw...@gmail.com a écrit : It seems the 4.8.1 version in central is borked. It doesn't contain any classes. That would explain why your imports can't be resolved. I don't know who did the upload of this artifact, but it is certainly

Re: junit 4.8.1 - org.junit cannot be resolved

2010-04-28 Thread Nick Stolwijk
That depends on where you look. ;) Take a look at http://repository.sonatype.org/index.html#nexus-search;gav~~junit~4.8.1~~ That one certainly is borked. See also the jira issue in my other mail. There are different versions of this artifact in central/mirrors. As long as not all mirrors purge

Re: Fortify and Maven

2010-04-28 Thread Anders Hammar
To follow up on my own thread. It turns out that the actually do have their own plugin (maven-sca-plugin). Anyone with experience of that? /Anders On Wed, Apr 28, 2010 at 09:32, Anders Hammar and...@hammar.net wrote: I was asked about integrating Fortify (Fortify 360) in the Maven build

Re: junit 4.8.1 - org.junit cannot be resolved

2010-04-28 Thread Tony Chemit
Le Wed, 28 Apr 2010 11:07:02 +0200, Nick Stolwijk nick.stolw...@gmail.com a écrit : That depends on where you look. ;) Take a look at http://repository.sonatype.org/index.html#nexus-search;gav~~junit~4.8.1~~ That one certainly is borked. See also the jira issue in my other mail. There

Re: junit 4.8.1 - org.junit cannot be resolved

2010-04-28 Thread Nick Stolwijk
Most of the times, mirrors don't update released artifacts, because they should not change. So depending on your mirror you can get the old version. I'm already asking around on nexus irc if someone could resolve this issue at least for the repository.sonatype.org mirror. With regards, Nick

Re: junit 4.8.1 - org.junit cannot be resolved

2010-04-28 Thread Jörg Schaible
Nick Stolwijk wrote: Most of the times, mirrors don't update released artifacts, because they should not change. So depending on your mirror you can get the old version. I'm already asking around on nexus irc if someone could resolve this issue at least for the repository.sonatype.org mirror.

Re: junit 4.8.1 - org.junit cannot be resolved

2010-04-28 Thread Nick Stolwijk
I know, for now I at least got someone to correct the situation between central and repository.sonatype.org. They now have the same artifacts. I am also not happy about the replacement on central. With regards, Nick Stolwijk ~Java Developer~ IPROFS BV. Claus Sluterweg 125 2012 WS Haarlem

Re: junit 4.8.1 - org.junit cannot be resolved

2010-04-28 Thread Juven Xu
I just fixed the repository.sonatype.org mirror. From the ticket http://jira.codehaus.org/browse/MAVENUPLOAD-2695 you can see why this happened: 1) the reporter of the ticket attached a broken junit artifact 2) I uploaded it into central without checking the internal of the jar 3) Paul

maven integration for clearcase info

2010-04-28 Thread Rajesh Kumar
Hi, I am beginner in maven and Clearcase UCM both. Can any body provide me step by step instruction where i can perform following activities? 1. Clearcase setup with maven 2. My pom.xml should create view - Example for Pom.xml 3. How can i satisfy following URL?

Re: Different behavior of Maven 2 and 3 on Flat Projekt Layout

2010-04-28 Thread Marshall Schor
I've taken an approach which separates parents and aggregates. I've put all my parents into one eclipse project, each with a folder naming the parent, and in that folder, a pom.xml; this is of course a flat structure. These I then mvn install into my local repo, and/or deploy. I'm following the

Re: maven scm plugin: accurev scm provider

2010-04-28 Thread eyal edri
Thanks! can you give me an example of how the connectionUrl should look like with accurev? E. On Fri, Apr 23, 2010 at 11:04 AM, Grant Gardner gdgard...@optusnet.com.auwrote: If you want to use the new version, take the code attached to issue, bump parent version to 1.3 and change the

maven-javadoc-plugin:aggregate and maven plugin module does not work

2010-04-28 Thread wujek.srujek
Hi. I have project whose structure is the following: A (packaging: pom) A-core (packaging jar) A-maven-plugin (packaging maven-plugin) pom.xml from A has this: build plugins plugin groupIdorg.apache.maven.plugins/groupId

Re: plugin execution inheritance

2010-04-28 Thread solo1970
In this particular case, we don't have the same POM for inhertance/aggregation. I don't have any experience in writing Maven plugins, but could I write a lpugin that calls these 3 plugins sonia Stephen Connolly-2 wrote: remember that inheritance does not have to follow aggregation

Re: plugin execution inheritance

2010-04-28 Thread solo1970
I don't have any experience in writing Maven plugins, but could I write a plugin that calls these 3 plugins sonia Anders Hammar wrote: No, you cannot import a pluginManagement section. And I cannot think of any other solution for you than to specify the same configuration for each

Release plugin and updating a release with some fixes

2010-04-28 Thread napple fabble
I use release plugin to update my pom.xml and create tags in subversion. I just created a new release with it. While development was ongoing, my pom.xmls had version 1.5-SNAPSHOT. Release plugin created tag 1.5 and updated my trunk to 1.6-SNAPSHOT. So everything is as I want. The only thing I

Re: Release plugin and updating a release with some fixes

2010-04-28 Thread Kumar Ampani
If you are not using the release:perform, how are you creating the releaser artifact 1.5 ? I am guessing you are running the install or deploy from the new tag 1.5. As far rescue changes, you will have to make changes to trunk or tag and then merge them to the other. Ideally I would create

Re: Release plugin and updating a release with some fixes

2010-04-28 Thread Wes Wannemacher
If you're not using release:perform and you aren't pushing a blessed jar anywhere (i.e. nexus), then you could just mvn release:rollback (it might not be rollback, but there is some command that rolls things back). Then, make your fixes and do release:prepare again. I will add that the whole

Re: Release plugin and updating a release with some fixes

2010-04-28 Thread Wendy Smoak
On Wed, Apr 28, 2010 at 10:23 AM, napple fabble jm.postili...@gmail.com wrote: The only thing I need to do is mvn release:prepare. This creates the correct tag and updates trunk as I want it to. I haven't had any need for release:perform. Really? Where are you getting the released artifacts

getting multiple forms of the build date

2010-04-28 Thread Marshall Schor
There's a new way to get the build date, documented here: http://maven.apache.org/guides/introduction/introduction-to-the-pom.html - search for maven.build.timestamp. This is nice. I would like to have multiple versions of this. For instance, the whole date/time spec for including in Jar

Re: I have the right version, but maven can't find it

2010-04-28 Thread Mark H. Wood
On Wed, Apr 28, 2010 at 09:55:05AM +0200, Jörg Schaible wrote: [snip] but you should probably ask the developers of the artifacts in question why they think they need exactly those versions. Find the artifacts with dependency:tree. Definitely ask them that. I find that depending on a

Re: I have the right version, but maven can't find it

2010-04-28 Thread Grant Birchmeier
I've been in contact with the developer, and the solution is underway. Thanks, all. -Grant On Wed, Apr 28, 2010 at 11:21 AM, Mark H. Wood mw...@iupui.edu wrote: On Wed, Apr 28, 2010 at 09:55:05AM +0200, Jörg Schaible wrote: [snip] but you should probably ask the developers of the artifacts

Re: Fortify and Maven

2010-04-28 Thread Larry Suto
Hi I have integrated that plugin into many projects. What are you trying to do? On Wed, Apr 28, 2010 at 2:11 AM, Anders Hammar and...@hammar.net wrote: To follow up on my own thread. It turns out that the actually do have their own plugin (maven-sca-plugin). Anyone with experience of that?

Re: junit 4.8.1 - org.junit cannot be resolved

2010-04-28 Thread Wayne Fay
1) the reporter of the ticket attached a broken junit artifact 2) I uploaded it into central without checking the internal of the jar 3) Paul Kinghttp://jira.codehaus.org/secure/ViewProfile.jspa?name=paulk_asertfound it's broken and notified me 4) I fixed the broken junit in central so

Re: Fortify and Maven

2010-04-28 Thread Anders Hammar
I was asked to look into this and is basically wondering about any gotchas. Any issues you've encountered? Have you used it integrated in the build process through a profile, or have you just used the plugin from command line (mvn sca:scan and similar)? /Anders On Wed, Apr 28, 2010 at 19:24,

Release dependency fails (2.0.9 vs 2.2.1)

2010-04-28 Thread Randall Fidler
Hello, Using Maven 2.2.1, release:perform seems to break in that it cannot find a dependency. I switch back to using Maven 2.0.9 and all is well. Simple example... Parent pom (1.0.0.0_b0-snapshot) | | Child A (1.0.0.0_b0-snapshot) | Child B (1.0.0.0_b0-snapshot)

Re: Fortify and Maven

2010-04-28 Thread Larry Suto
I have done both and have not encountered too many problems. The one thing that you might want to consider removing plugin management in the Fortify profiles. Otherwise you have to declare the sca plugin in every module during an aggregate scan On Wed, Apr 28, 2010 at 11:09 AM, Anders Hammar

Re: Release dependency fails (2.0.9 vs 2.2.1)

2010-04-28 Thread Jörg Schaible
Hi Randall, Randall Fidler wrote: Hello, Using Maven 2.2.1, release:perform seems to break in that it cannot find a dependency. I switch back to using Maven 2.0.9 and all is well. Simple example... Parent pom (1.0.0.0_b0-snapshot) | | Child A

Re: Fortify and Maven

2010-04-28 Thread Anders Hammar
Ok, thanks Larry. I'll post back if I run into any troubles. /Anders On Wed, Apr 28, 2010 at 20:23, Larry Suto larry.s...@gmail.com wrote: I have done both and have not encountered too many problems. The one thing that you might want to consider removing plugin management in the Fortify

Configure jetty port in profiles

2010-04-28 Thread darniz
Hi All I figured out how to start jetty on default port on 80 with http and https. plugin groupIdorg.mortbay.jetty/groupId artifactIdmaven-jetty-plugin/artifactId version6.1.16/version configuration

RE: Release dependency fails (2.0.9 vs 2.2.1)

2010-04-28 Thread Jörg Schaible
Randall Fidler wrote: Jorg, Direct reference in Child_B dependency section to Child_A. Can you post the pom of Child_B and the parent ? - Jörg Thanks! -Randall -Original Message- From: Jörg Schaible [mailto:joerg.schai...@gmx.de] Sent: Wednesday, April 28, 2010 12:11

Re: [ANN] Apache Maven 3.0-beta-1 Released

2010-04-28 Thread Hervé BOUTEMY
FYI, this has just been fixed (thanks Kristian). The fix is in Maven 3 trunk, then won't be available to general public before Maven 3.0-beta-2 release: no ETA ;) I just compiled Maven trunk for myself then maven-site-plugin 3.0 branch, and everything is now ok. Regards, Hervé Le samedi 24

RE: Release plugin and updating a release with some fixes

2010-04-28 Thread Martin Gainty
2 separate and distinct versions to be simultaneous merged with an artifact dependency may cause integration havoc later on..e.g. trunk-1.5 merged with dependency-artifactV1.5 trunk-1.6 merged with dependency-artifactV1.6 best to use point release .1 .2 as wes mentioned trunk1.5 merges with

maven-compiler-plugin with axis2-wsdl2code-maven-plugin

2010-04-28 Thread bon
Hi all, I have a issue when using maven-compiler-plugin with axis2-wsdl2code-maven-plugin. Whenever I enable generateServicesXmltrue/generateServicesXml in the axis2-wsdl2code-maven-plugin. The exclude option in maven-compiler-plugin will not work excludes

Release Plugin and local working copy changes

2010-04-28 Thread Mark Derricutt
Hi all, I was discussing last night with some friends about problems they've had lately with the release plugin, it seems that the plugin is no longer checking for modified files in the working copy and aborting the release:prepare process ( against a subversion repository ). I've not had a

Re: maven scm plugin: accurev scm provider

2010-04-28 Thread Grant Gardner
the site documentation for that version is available here http://lastweekend.com.au/projects/maven-scm-provider-accurev/site/ On Wed, 28 Apr 2010 14:11:07 +0300, eyal edri eyal.e...@gmail.com wrote: Thanks! can you give me an example of how the connectionUrl should look like with accurev?