Re: I have the right version, but maven can't find it
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 the version in your pom. Justin On Apr 27, 2010, at 8:59 PM, Grant Birchmeier gbirchme...@connamara.com wrote: I can't find where the range is specified. My output says: --- Path to dependency: 1) com.connamara.ontrade:simplespreader:jar:1.0 2) org.marketcetera:ors:jar:1.6.0 --- But neither pom specifies a version for log4j. I'm not even sure why it looking for 1.2.13 as opposed to something later. I see that the file you linked was last updated March 31, which probably explains why this trouble just started, as we last did a build prior to that. I got it to build by hacking my ~/.m2/repository/log4j/log4j/maven-metadata-central.xml to include 1.2.13. This is not really an optimal solution, as every user will need to do this. Is there a better way? (Our software uses third-party components with their own poms. Until now, we haven't had any trouble with the Maven part. Clearly, though, I'm still kind of new to this.) -Grant On Tue, Apr 27, 2010 at 7:26 PM, Justin Edelson justinedel...@gmail.com wrote: Because you're using a range, which requires better metadata than log4j has. See http://repo1.maven.org/maven2/log4j/log4j/maven-metadata.xml On 4/27/10 8:21 PM, 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] log4j:log4j:jar:null --- But when I list the contents of my repo dir, I clearly have a 1.2.13 version: --- 1143 ~/$ ls ~/.m2/repository/log4j/log4j/ 1.2.13/ 1.2.14/ 1.2.15/ maven-metadata-central.xml [...etc...] --- So if I have 1.2.13 in my repo, then why is maven only finding 1.2.14 and 1.2.15? Thanks to anyone who can help -Grant - 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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Clearcase with maven release plugin
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 combination as well as there has been new releases of the release plugin as well as the scm parts. So, it works on any branch, not just the main branch. (However, you cannot make a branch.) As long as the view you're using is set up correctly, things will work with the release plugin. Some quick things: * Create $user.home/.scm/clearcase-settings.xml containing clearcase-settings useVWSParameterfalse/useVWSParameter /clearcase-settings I've created the clearcase-settings.xml file in %HOME% on my Windows machine. And because I found a post somewhere, where they've put it in a .scm directory, so I copied it there. But I keep getting the following error: [INFO] Unable to checkout from SCM Provider message: The cleartool command failed. Command output: cleartool: Error: Unrecognized command option: -vws. I have the feeling that my settings file is ignored Do you have an idea how I should proceed? Sorry, no. If the file is stored as $user.home/.scm/clearcase-settings.xml it should be picked up. Are you sure it is in the right location (for the right user)? Execute Maven in debug mode (-X) and possibly you could get more info. According to the doc, you could put the file in $maven.home/conf/clearcase-settings.xml as well. You could try that to get something working. Here's the doc that's available: http://maven.apache.org/scm/clearcase.html /Anders
junit 4.8.1 - org.junit cannot be resolved
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 import org.junit.Assert). but if i change the junit version to 4.7. no problem at all. did i do anything wrong? Thanks. Kit -- View this message in context: http://old.nabble.com/junit-4.8.1---org.junit-cannot-be-resolved-tp28385338p28385338.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
Clearcase with Maven
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, Build and Release Engineer Blog: http://www.scmGalaxy.com Email: raj...@scmgalaxy.com
Fortify and Maven
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
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] log4j:log4j:jar:null --- [snip] So if I have 1.2.13 in my repo, then why is maven only finding 1.2.14 and 1.2.15? Actually you (in your project) or some of your dependencies declare version ranges for log4j and one requires log4j to be used exactly in version 1.2.13 while another say it must have log4j 1.2.15 or 1.2.16. This requirements can obviously not be fulfilled. As Anders already recommended, use a depMgmt section to override the version with the one you like to use, 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. - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven javadoc plugin error
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]
[INFO] Building Jfoundation Web Servicelocator
[INFO]task-segment: [site]
[INFO]
-
this realm =
app0.child-container[org.apache.maven.plugins:maven-javadoc-plugin:
2.5]
urls[0] =
file:/D:/Saif/Maven-Repo/m2/org/apache/maven/plugins/maven-javadoc-plu
gin/2.5/maven-javadoc-plugin-2.5.jar
urls[1] =
file:/D:/Saif/Maven-Repo/m2/org/codehaus/plexus/plexus-utils/1.1/plexu
s-utils-1.1.jar
Number of imports: 10
import: org.codehaus.classworlds.en...@a6c57a42
import: org.codehaus.classworlds.en...@12f43f3b
import: org.codehaus.classworlds.en...@20025374
import: org.codehaus.classworlds.en...@f8e44ca4
import: org.codehaus.classworlds.en...@92758522
import: org.codehaus.classworlds.en...@ebf2705b
import: org.codehaus.classworlds.en...@bb25e54
import: org.codehaus.classworlds.en...@bece5185
import: org.codehaus.classworlds.en...@3fee8e37
import: org.codehaus.classworlds.en...@3fee19d8
this realm = plexus.core
urls[0] =
file:/D:/Apps/JavaSoftwares/Maven-2.2.1/lib/maven-2.2.1-uber.jar
Number of imports: 10
import: org.codehaus.classworlds.en...@a6c57a42
import: org.codehaus.classworlds.en...@12f43f3b
import: org.codehaus.classworlds.en...@20025374
import: org.codehaus.classworlds.en...@f8e44ca4
import: org.codehaus.classworlds.en...@92758522
import: org.codehaus.classworlds.en...@ebf2705b
import: org.codehaus.classworlds.en...@bb25e54
import: org.codehaus.classworlds.en...@bece5185
import: org.codehaus.classworlds.en...@3fee8e37
import: org.codehaus.classworlds.en...@3fee19d8
-
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error getting reports from the plugin
'org.apache.maven.plugins:maven-jav
adoc-plugin:2.5': Unable to load the mojo
'org.apache.maven.plugins:maven-javado
c-plugin:2.5:test-jar' in the plugin
'org.apache.maven.plugins:maven-javadoc-plu
gin'. A required class is missing:
org/codehaus/plexus/archiver/ArchiverExceptio
n
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 1 second
[INFO] Finished at: Wed Apr 28 11:19:27 GST 2010
[INFO] Final Memory: 6M/13M
[INFO]
//- pom.xml
--
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
parent
groupIdjfoundation-web2/groupId
artifactIdjfoundation-web2/artifactId
version1.0.0/version
/parent
groupIdjfoundation-web2/groupId
nameJfoundation Web Servicelocator/name
artifactIdjw-servicelocator/artifactId
version${jfoundation.version}/version
packagingjar/packaging
dependencies
dependency
groupIdjfoundation-web2/groupId
artifactIdjw-jsf-core/artifactId
/dependency
dependency
groupIdjfoundation/groupId
artifactIdjf-core-implementation/artifactId
/dependency
dependency
groupIdognl/groupId
artifactIdognl/artifactId
version2.7.3/version
/dependency
/dependencies
reporting
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-javadoc-plugin/artifactId
version2.6.1/version
/plugin
/plugins
/reporting
/project
//-end
pom--
Any inputs wll be of great help.
Thanks in advance.
Saif Kamaal
Emirates Group Information Technology
Tel:+971 55 4023898
Extn: +971 04 2033912
saif.abulkh...@emirates.com mailto:patrick.n...@emirates.com
Re: junit 4.8.1 - org.junit cannot be resolved
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 case, the org.junit cannot be resolved(i.e. error at import org.junit.Assert). but if i change the junit version to 4.7. no problem at all. did i do anything wrong? No, it's just that JUnit 4.8.1 isn't available in the central repo (for now). -dirk - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: junit 4.8.1 - org.junit cannot be resolved
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 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 import org.junit.Assert). but if i change the junit version to 4.7. no problem at all. did i do anything wrong? No, it's just that JUnit 4.8.1 isn't available in the central repo (for now). -dirk - 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: junit 4.8.1 - org.junit cannot be resolved
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 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 import org.junit.Assert). but if i change the junit version to 4.7. no problem at all. did i do anything wrong? When you have this error, is it in a IDEA ? or when you launch a maven build ? No, it's just that JUnit 4.8.1 isn't available in the central repo (for now). I can see it on central here : http://repo1.maven.org/maven2/junit/junit/4.8.1/ -dirk - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Tony Chemit tél: +33 (0) 2 40 50 29 28 email: che...@codelutin.com http://www.codelutin.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: junit 4.8.1 - org.junit cannot be resolved
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 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 import org.junit.Assert). but if i change the junit version to 4.7. no problem at all. did i do anything wrong? When you have this error, is it in a IDEA ? or when you launch a maven build ? No, it's just that JUnit 4.8.1 isn't available in the central repo (for now). I can see it on central here : http://repo1.maven.org/maven2/junit/junit/4.8.1/ -dirk - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Tony Chemit tél: +33 (0) 2 40 50 29 28 email: che...@codelutin.com http://www.codelutin.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://old.nabble.com/junit-4.8.1---org.junit-cannot-be-resolved-tp28385338p28386045.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
Re: junit 4.8.1 - org.junit cannot be resolved
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 WS Haarlem http://www.iprofs.nl On Wed, Apr 28, 2010 at 10:22 AM, ykyuen yingkity...@gmail.com wrote: 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 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 import org.junit.Assert). but if i change the junit version to 4.7. no problem at all. did i do anything wrong? When you have this error, is it in a IDEA ? or when you launch a maven build ? No, it's just that JUnit 4.8.1 isn't available in the central repo (for now). I can see it on central here : http://repo1.maven.org/maven2/junit/junit/4.8.1/ -dirk - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Tony Chemit tél: +33 (0) 2 40 50 29 28 email: che...@codelutin.com http://www.codelutin.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://old.nabble.com/junit-4.8.1---org.junit-cannot-be-resolved-tp28385338p28386045.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: junit 4.8.1 - org.junit cannot be resolved
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] http://jira.codehaus.org/browse/MAVENUPLOAD-2695?page=com.atlassian.jira.plugin.system.issuetabpanels%3Aall-tabpanel#issue-tabs [2] http://mirrors.ibiblio.org/pub/mirrors/maven2/junit/junit/4.8.1/ With regards, Nick Stolwijk ~Java Developer~ IPROFS BV. Claus Sluterweg 125 2012 WS Haarlem http://www.iprofs.nl On Wed, Apr 28, 2010 at 10:52 AM, Nick Stolwijk nick.stolw...@gmail.com wrote: 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 WS Haarlem http://www.iprofs.nl On Wed, Apr 28, 2010 at 10:22 AM, ykyuen yingkity...@gmail.com wrote: 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 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 import org.junit.Assert). but if i change the junit version to 4.7. no problem at all. did i do anything wrong? When you have this error, is it in a IDEA ? or when you launch a maven build ? No, it's just that JUnit 4.8.1 isn't available in the central repo (for now). I can see it on central here : http://repo1.maven.org/maven2/junit/junit/4.8.1/ -dirk - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Tony Chemit tél: +33 (0) 2 40 50 29 28 email: che...@codelutin.com http://www.codelutin.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://old.nabble.com/junit-4.8.1---org.junit-cannot-be-resolved-tp28385338p28386045.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: junit 4.8.1 - org.junit cannot be resolved
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 wrong. Nope, there is some classes inside the jar. For me there is nothing wrong with the artifact on central. With regards, Nick Stolwijk ~Java Developer~ IPROFS BV. Claus Sluterweg 125 2012 WS Haarlem http://www.iprofs.nl On Wed, Apr 28, 2010 at 10:22 AM, ykyuen yingkity...@gmail.com wrote: 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 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 import org.junit.Assert). but if i change the junit version to 4.7. no problem at all. did i do anything wrong? When you have this error, is it in a IDEA ? or when you launch a maven build ? No, it's just that JUnit 4.8.1 isn't available in the central repo (for now). I can see it on central here : http://repo1.maven.org/maven2/junit/junit/4.8.1/ -dirk - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Tony Chemit tél: +33 (0) 2 40 50 29 28 email: che...@codelutin.com http://www.codelutin.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://old.nabble.com/junit-4.8.1---org.junit-cannot-be-resolved-tp28385338p28386045.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 -- Tony Chemit tél: +33 (0) 2 40 50 29 28 email: che...@codelutin.com http://www.codelutin.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: junit 4.8.1 - org.junit cannot be resolved
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 their old version, I wouldn't trust this version. Normally, central had a very strict policy, what is on central, stays on central, but it seems someone slipped this time. With regards, Nick Stolwijk ~Java Developer~ IPROFS BV. Claus Sluterweg 125 2012 WS Haarlem http://www.iprofs.nl On Wed, Apr 28, 2010 at 11:01 AM, Tony Chemit che...@codelutin.com wrote: 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 wrong. Nope, there is some classes inside the jar. For me there is nothing wrong with the artifact on central. With regards, Nick Stolwijk ~Java Developer~ IPROFS BV. Claus Sluterweg 125 2012 WS Haarlem http://www.iprofs.nl On Wed, Apr 28, 2010 at 10:22 AM, ykyuen yingkity...@gmail.com wrote: 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 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 import org.junit.Assert). but if i change the junit version to 4.7. no problem at all. did i do anything wrong? When you have this error, is it in a IDEA ? or when you launch a maven build ? No, it's just that JUnit 4.8.1 isn't available in the central repo (for now). I can see it on central here : http://repo1.maven.org/maven2/junit/junit/4.8.1/ -dirk - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Tony Chemit tél: +33 (0) 2 40 50 29 28 email: che...@codelutin.com http://www.codelutin.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://old.nabble.com/junit-4.8.1---org.junit-cannot-be-resolved-tp28385338p28386045.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 -- Tony Chemit tél: +33 (0) 2 40 50 29 28 email: che...@codelutin.com http://www.codelutin.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: Fortify and Maven
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 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: junit 4.8.1 - org.junit cannot be resolved
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 are different versions of this artifact in central/mirrors. As long as not all mirrors purge their old version, I wouldn't trust this version. Normally, central had a very strict policy, what is on central, stays on central, but it seems someone slipped this time. Ok I tought that only http://repo1.maven.org/maven2/ was central, and mirrors could be cleaned. (but still respects the policy of central)... With regards, Nick Stolwijk ~Java Developer~ IPROFS BV. Claus Sluterweg 125 2012 WS Haarlem http://www.iprofs.nl On Wed, Apr 28, 2010 at 11:01 AM, Tony Chemit che...@codelutin.com wrote: 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 wrong. Nope, there is some classes inside the jar. For me there is nothing wrong with the artifact on central. With regards, Nick Stolwijk ~Java Developer~ IPROFS BV. Claus Sluterweg 125 2012 WS Haarlem http://www.iprofs.nl On Wed, Apr 28, 2010 at 10:22 AM, ykyuen yingkity...@gmail.com wrote: 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 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 import org.junit.Assert). but if i change the junit version to 4.7. no problem at all. did i do anything wrong? When you have this error, is it in a IDEA ? or when you launch a maven build ? No, it's just that JUnit 4.8.1 isn't available in the central repo (for now). I can see it on central here : http://repo1.maven.org/maven2/junit/junit/4.8.1/ -dirk - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Tony Chemit tél: +33 (0) 2 40 50 29 28 email: che...@codelutin.com http://www.codelutin.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://old.nabble.com/junit-4.8.1---org.junit-cannot-be-resolved-tp28385338p28386045.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 -- Tony Chemit tél: +33 (0) 2 40 50 29 28 email: che...@codelutin.com http://www.codelutin.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 -- Tony Chemit tél: +33 (0) 2 40 50 29 28 email: che...@codelutin.com http://www.codelutin.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: junit 4.8.1 - org.junit cannot be resolved
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 Stolwijk ~Java Developer~ IPROFS BV. Claus Sluterweg 125 2012 WS Haarlem http://www.iprofs.nl On Wed, Apr 28, 2010 at 11:21 AM, Tony Chemit che...@codelutin.com wrote: 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 are different versions of this artifact in central/mirrors. As long as not all mirrors purge their old version, I wouldn't trust this version. Normally, central had a very strict policy, what is on central, stays on central, but it seems someone slipped this time. Ok I tought that only http://repo1.maven.org/maven2/ was central, and mirrors could be cleaned. (but still respects the policy of central)... With regards, Nick Stolwijk ~Java Developer~ IPROFS BV. Claus Sluterweg 125 2012 WS Haarlem http://www.iprofs.nl On Wed, Apr 28, 2010 at 11:01 AM, Tony Chemit che...@codelutin.com wrote: 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 wrong. Nope, there is some classes inside the jar. For me there is nothing wrong with the artifact on central. With regards, Nick Stolwijk ~Java Developer~ IPROFS BV. Claus Sluterweg 125 2012 WS Haarlem http://www.iprofs.nl On Wed, Apr 28, 2010 at 10:22 AM, ykyuen yingkity...@gmail.com wrote: 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 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 import org.junit.Assert). but if i change the junit version to 4.7. no problem at all. did i do anything wrong? When you have this error, is it in a IDEA ? or when you launch a maven build ? No, it's just that JUnit 4.8.1 isn't available in the central repo (for now). I can see it on central here : http://repo1.maven.org/maven2/junit/junit/4.8.1/ -dirk - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Tony Chemit tél: +33 (0) 2 40 50 29 28 email: che...@codelutin.com http://www.codelutin.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://old.nabble.com/junit-4.8.1---org.junit-cannot-be-resolved-tp28385338p28386045.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 -- Tony Chemit tél: +33 (0) 2 40 50 29 28 email: che...@codelutin.com http://www.codelutin.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 -- Tony Chemit tél: +33 (0) 2 40 50 29 28 email: che...@codelutin.com http://www.codelutin.com - To
Re: junit 4.8.1 - org.junit cannot be resolved
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. Actually it was a failure to exchange the artifact in first place. That has always been the policy on central and this incident demonstrates exactly why. For other known broken jars (esp. the ones containing javax. stuff) it has always been stated, that they must release a new version. So why should it be different in this case? You'll need junit 4.8.1-1 or the like to solve the problem - 4.8.1 is already tainted. With all those people using local repo managers you will never get a consistent situation anymore. - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: junit 4.8.1 - org.junit cannot be resolved
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 http://www.iprofs.nl On Wed, Apr 28, 2010 at 11:50 AM, Jörg Schaible joerg.schai...@gmx.de wrote: 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. Actually it was a failure to exchange the artifact in first place. That has always been the policy on central and this incident demonstrates exactly why. For other known broken jars (esp. the ones containing javax. stuff) it has always been stated, that they must release a new version. So why should it be different in this case? You'll need junit 4.8.1-1 or the like to solve the problem - 4.8.1 is already tainted. With all those people using local repo managers you will never get a consistent situation anymore. - Jörg - 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: junit 4.8.1 - org.junit cannot be resolved
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 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 the broken junit 4.8.1 did exist in central for about 6 hours :( this explains why we ask pgp signatures for artifacts which wants to be synced. On Wed, Apr 28, 2010 at 5:27 PM, Nick Stolwijk nick.stolw...@gmail.comwrote: 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 Stolwijk ~Java Developer~ IPROFS BV. Claus Sluterweg 125 2012 WS Haarlem http://www.iprofs.nl On Wed, Apr 28, 2010 at 11:21 AM, Tony Chemit che...@codelutin.com wrote: 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~~http://repository.sonatype.org/index.html#nexus-search;gav%7E%7Ejunit%7E4.8.1%7E%7E 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 their old version, I wouldn't trust this version. Normally, central had a very strict policy, what is on central, stays on central, but it seems someone slipped this time. Ok I tought that only http://repo1.maven.org/maven2/ was central, and mirrors could be cleaned. (but still respects the policy of central)... With regards, Nick Stolwijk ~Java Developer~ IPROFS BV. Claus Sluterweg 125 2012 WS Haarlem http://www.iprofs.nl On Wed, Apr 28, 2010 at 11:01 AM, Tony Chemit che...@codelutin.com wrote: 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 wrong. Nope, there is some classes inside the jar. For me there is nothing wrong with the artifact on central. With regards, Nick Stolwijk ~Java Developer~ IPROFS BV. Claus Sluterweg 125 2012 WS Haarlem http://www.iprofs.nl On Wed, Apr 28, 2010 at 10:22 AM, ykyuen yingkity...@gmail.com wrote: 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 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 import org.junit.Assert). but if i change the junit version to 4.7. no problem at all. did i do anything wrong? When you have this error, is it in a IDEA ? or when you launch a maven build ? No, it's just that JUnit 4.8.1 isn't available in the central repo (for now). I can see it on central here : http://repo1.maven.org/maven2/junit/junit/4.8.1/ -dirk - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Tony Chemit tél: +33 (0) 2 40 50 29 28 email: che...@codelutin.com http://www.codelutin.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://old.nabble.com/junit-4.8.1---org.junit-cannot-be-resolved-tp28385338p28386045.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
maven integration for clearcase info
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? scm:clearcasedelimiter[view_name]delimiterconfig_specdelimitervob_namedelimiterstream_name coz clearcase does give any config_spec 4. Any other info which i need to get maven integration work for clearcase -- === Rajesh Kumar Configuration, Build and Release Engineer
Re: Different behavior of Maven 2 and 3 on Flat Projekt Layout
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 convention of labeling these with version
like 1, 2, 3 ... see for instance the common apache pom
(http://repo1.maven.org/maven2/org/apache/apache/7/apache-7.pom). Using
m2eclipse you can select the folder containing a pom, right click, and
pick the run - mvn install to do this very easily (or from the main
Eclipse run menu, once you do it once this right-click way, because it
gets set up as an Eclipse run configuration).
The aggregate poms just do aggregation, and are not parents of anything.
With this approach, I think that there is no need to have relativePath set.
-Marshall
On 4/27/2010 5:17 AM, subir.sasiku...@wipro.com wrote:
You need to add a relativePath for parent elements. Its mandatory in
Maven 3.
Add those and your builds should work.
And you can always see other issues about compatibility by googling.
Subir
-Original Message-
From: Robert Einsle [mailto:rob...@einsle.de]
Sent: Tuesday, April 27, 2010 12:59 PM
To: Maven Users List
Subject: Different behavior of Maven 2 and 3 on Flat Projekt Layout
Hy List,
lets assume i have 3 Projects:
xx.yy.app.parent
xx.yy.app.module1
xx.yy.app.module2
.parent is Parent of both modules
--- cut ---
parent
artifactIdxx.yy.app.parent/artifactId
groupIdxx.yy.app/groupId
version1.0.0-SNAPSHOT/version
/parent
modelVersion4.0.0/modelVersion
groupIdxx.yy.app/groupId
artifactIdxx.yy.app.module1/artifactId
version1.0.0-SNAPSHOT/version
nameModule 1/name
--- cut ---
, in .parent the both modules are linked with:
--- cut ---
modules
module../xx.yy.app.module1/module
module../xx.yy.app.module2/module
/modules
--- cut ---
Now i start clean package on Eclipse, my output is:
--- cut ---
[INFO] Scanning for projects...
[ERROR] The build could not read 2 projects - [Help 1]
[ERROR] The project xx.yy.app:xx.yy.app.module1:1.0.0-SNAPSHOT
(D:\Eclipse_Workspaces\maven-3.5.2\xx.yy.app.module1\pom.xml) has 1
error
[ERROR] Non-resolvable parent POM
xx.yy.app:xx.yy.app.parent:1.0.0-SNAPSHOT for
xx.yy.app:xx.yy.app.module1:1.0.0-SNAPSHOT: Failed to resolve POM for
xx.yy.app:xx.yy.app.parent:1.0.0-SNAPSHOT due to Missing:
--
1) xx.yy.app:xx.yy.app.parent:pom:1.0.0-SNAPSHOT
--
1 required artifact is missing.
for artifact:
xx.yy.app:xx.yy.app.parent:pom:1.0.0-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2, releases=true,
snapshots=false)
- [Help 2]
[ERROR] The project xx.yy.app:xx.yy.app.module2:1.0.0-SNAPSHOT
(D:\Eclipse_Workspaces\maven-3.5.2\xx.yy.app.module2\pom.xml) has 1
error
[ERROR] Non-resolvable parent POM
xx.yy.app:xx.yy.app.parent:1.0.0-SNAPSHOT for
xx.yy.app:xx.yy.app.module2:1.0.0-SNAPSHOT: Failed to resolve POM for
xx.yy.app:xx.yy.app.parent:1.0.0-SNAPSHOT due to Missing:
--
1) xx.yy.app:xx.yy.app.parent:pom:1.0.0-SNAPSHOT
--
1 required artifact is missing.
for artifact:
xx.yy.app:xx.yy.app.parent:pom:1.0.0-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2, releases=true,
snapshots=false)
- [Help 2]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the
-e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/ProjectBuildingExceptio
n
[ERROR] [Help 2]
http://cwiki.apache.org/confluence/display/MAVEN/UnresolvableModelExcept
ion
--- cut ---
when i run this on Maven 2.2.1
--- cut ---
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] Application Parent
[INFO] Module 1
[INFO] Module 2
[INFO]
[INFO] Building Application Parent
[INFO]task-segment: [clean, package]
[INFO]
[INFO] [clean:clean {execution: default-clean}] [INFO]
[site:attach-descriptor {execution: default-attach-descriptor}] [INFO]
[INFO] Building Module 1
[INFO]task-segment: [clean, package]
[INFO]
[INFO] [clean:clean {execution: default-clean}] [INFO] Deleting
directory D:\Eclipse_Workspaces\maven-3.5.2\xx.yy.app.module1\target
[INFO] [resources:resources {execution: default-resources}] [WARNING]
Using platform encoding (Cp1252 actually) to copy filtered resources,
i.e. build is platform
Re: maven scm plugin: accurev scm provider
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 artifact version to 1.4-SNAPSHOT then build and install to your local repository. Then in your project pom add this as a dependency to the maven-scm-plugin as follows. build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-scm-plugin/artifactId version1.3/version dependencies dependency groupIdorg.apache.maven.scm/groupId artifactIdmaven-scm-provider-accurev/artifactId version1.4-SNAPSHOT/version /dependency /dependencies /plugin plugins /build On Wed, 21 Apr 2010 15:56:50 +0300, eyal edri eyal.e...@gmail.com wrote: Anyone has used accurev + scm plugin yet? i know issue 445 on the scm-accurev-provider should fix most problems once ver 1.4 is due, is there any way i can use the plugin in the meantime and test connection to the accurev server? thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Eyal Edri
maven-javadoc-plugin:aggregate and maven plugin module does not work
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
artifactIdmaven-javadoc-plugin/artifactId
executions
execution
phasepackage/phase
goals
goalaggregate/goal
/goals
configuration
links
linkhttp://www.testng.org/javadocs//link
linkhttp://www.dbunit.org/apidocs//link
linkhttp://java.sun.com/javaee/6/docs/api//link
/links
showprivate/show
/configuration
/execution
/executions
/plugin
/plugins
/build
Now when I invoke 'mvn clean package' I get this output:
$ mvn -v
Apache Maven 2.2.1 (r801777; 2009-08-06 21:16:01+0200)
Java version: 1.6.0_19
...
$ mvn -Dmaven.test.skip -Dquiet=true package
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] A
[INFO] A Core
[INFO] A Maven Plugin
[INFO]
[INFO] Building A
[INFO]task-segment: [package]
[INFO]
[INFO] [site:attach-descriptor {execution: default-attach-descriptor}]
[INFO] Preparing javadoc:aggregate
[INFO]
[INFO] Building A
[INFO]
[WARNING] Removing: aggregate from forked lifecycle, to prevent recursive
invocation.
[INFO] No goals needed for project - skipping
[INFO]
[INFO] Building A Core
[INFO]
[WARNING] Removing: aggregate from forked lifecycle, to prevent recursive
invocation.
[INFO] No goals needed for project - skipping
[INFO]
[INFO] Building A Maven Plugin
[INFO]
[WARNING] Removing: aggregate from forked lifecycle, to prevent recursive
invocation.
[INFO] No goals needed for project - skipping
[INFO] [javadoc:aggregate {execution: default}]
[INFO]
[INFO] Building A Core
[INFO]task-segment: [package]
[INFO]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Copying 1 resource
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Compiling 58 source files to
C:\users\SR\Workspace\A\ACore\target\classes
[INFO] [resources:testResources {execution: default-testResources}]
[INFO] Copying 16 resources
[INFO] [compiler:testCompile {execution: default-testCompile}]
[INFO] Not compiling test sources
[INFO] [surefire:test {execution: default-test}]
[INFO] Tests are skipped.
[INFO] [jar:jar {execution: default-jar}]
[INFO] Building jar:
C:\users\SR\Workspace\A\ACore\target\a-core-0.9-SNAPSHOT.jar
[INFO] Preparing javadoc:aggregate
[INFO]
[INFO] Building A
[INFO]
[WARNING] Removing: aggregate from forked lifecycle, to prevent recursive
invocation.
[INFO] No goals needed for project - skipping
[INFO]
[INFO] Building A Core
[INFO]
[WARNING] Removing: aggregate from forked lifecycle, to prevent recursive
invocation.
[INFO] No goals needed for project - skipping
[INFO]
[INFO] Building A Maven Plugin
[INFO]
[WARNING] Removing: aggregate from forked lifecycle, to prevent recursive
invocation.
[INFO] No goals needed for project - skipping
[INFO] [javadoc:aggregate {execution: default}]
[INFO]
[INFO] Building A Maven Plugin
[INFO]task-segment: [package]
[INFO]
[INFO] [plugin:descriptor {execution: default-descriptor}]
[INFO] Using 2 extractors.
[INFO] Applying extractor for language: java
[INFO] Extractor for language: java found 2 mojo descriptors.
[INFO]
Re: plugin execution inheritance
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 (just that life is easier when it does) On 27 April 2010 20:58, solo1970 sonia.lodoviche...@ericsson.com wrote: Hello, We had created a POM which had the execution of 3 plugins in the PluginManagement section and all the POMs needing this plugin execution, was inheriting from it. We are restructuring code and now we cannot inherit from that POM anymore because we don't have a common parent. Can I import a pluginManagement section, just like the import in dependencies??? Is there any other way to achieve this??? I hope it's clear Sonia -- View this message in context: http://old.nabble.com/plugin-execution-inheritance-tp28381340p28381340.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 -- View this message in context: http://old.nabble.com/plugin-execution-inheritance-tp28381340p28387757.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
Re: plugin execution inheritance
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 project (unless you can change to inherit from a common parent somewhere in the inheritance chain). /Anders On Tue, Apr 27, 2010 at 21:58, solo1970 sonia.lodoviche...@ericsson.comwrote: Hello, We had created a POM which had the execution of 3 plugins in the PluginManagement section and all the POMs needing this plugin execution, was inheriting from it. We are restructuring code and now we cannot inherit from that POM anymore because we don't have a common parent. Can I import a pluginManagement section, just like the import in dependencies??? Is there any other way to achieve this??? I hope it's clear Sonia -- View this message in context: http://old.nabble.com/plugin-execution-inheritance-tp28381340p28381340.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 -- View this message in context: http://old.nabble.com/plugin-execution-inheritance-tp28381340p28387758.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
Release plugin and updating a release with some fixes
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 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. QUESTION: What do I do when I find some last bugs while installing the release and want to fix them. I would ideally like to have both 1.5 tag and the trunk (1.6-SNAPSHOT) updated with the fixes. Can I do this somehow conveniently with release plugin, or do I have to do it manually (if so, what's the best approach? just fix trunk and copy the changed to the tag?). -- View this message in context: http://maven-users.828.n2.nabble.com/Release-plugin-and-updating-a-release-with-some-fixes-tp4974743p4974743.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
Re: Release plugin and updating a release with some fixes
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 another release 1.5.1 using release;prepare and perform which will create a tag for 1.5.1 as well so that you will have reproducable builds for both 1.5 and 1.5.1 On 4/28/10, napple fabble jm.postili...@gmail.com wrote: 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 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. QUESTION: What do I do when I find some last bugs while installing the release and want to fix them. I would ideally like to have both 1.5 tag and the trunk (1.6-SNAPSHOT) updated with the fixes. Can I do this somehow conveniently with release plugin, or do I have to do it manually (if so, what's the best approach? just fix trunk and copy the changed to the tag?). -- View this message in context: http://maven-users.828.n2.nabble.com/Release-plugin-and-updating-a-release-with-some-fixes-tp4974743p4974743.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 -- Sent from my mobile device - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Release plugin and updating a release with some fixes
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 thing sounds a bit hackish and you should get an MRM. Then, if you find bugs, you can make a branch based on the 1.5 tag, fix your bugs, then merge the changes back to trunk. You can also release from the branch and name it 1.5.1 (or similar). -Wes On Wed, Apr 28, 2010 at 10:23 AM, napple fabble jm.postili...@gmail.com wrote: 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 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. QUESTION: What do I do when I find some last bugs while installing the release and want to fix them. I would ideally like to have both 1.5 tag and the trunk (1.6-SNAPSHOT) updated with the fixes. Can I do this somehow conveniently with release plugin, or do I have to do it manually (if so, what's the best approach? just fix trunk and copy the changed to the tag?). -- View this message in context: http://maven-users.828.n2.nabble.com/Release-plugin-and-updating-a-release-with-some-fixes-tp4974743p4974743.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 -- Wes Wannemacher Head Engineer, WanTii, Inc. Need Training? Struts, Spring, Maven, Tomcat... Ask me for a quote! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Release plugin and updating a release with some fixes
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 then? Release Perform is what checks out from the newly created tag and builds the artifacts... QUESTION: What do I do when I find some last bugs while installing the release and want to fix them. I would ideally like to have both 1.5 tag and the trunk (1.6-SNAPSHOT) updated with the fixes. Can I do this somehow conveniently with release plugin, or do I have to do it manually (if so, what's the best approach? just fix trunk and copy the changed to the tag?). What scm tool are you using? The following assumes Subversion: Generally tags are not changed, the point is to know exactly what code your release came from. If you find you need to make a fix, then you can branch from the tag -- in your case the version number on your branch might be 1.5.1-SNAPSHOT. Then you would merge the fix from the branch to your 1.6-SNAPSHOT trunk. At that point you can release one or both with the fix. But version 1.5 should not be updated with the fix -- it's already released. Just move on to 1.5.1. Version numbers are free. :) If you really, really want Version 1.5 to be perfect, then consider releasing some alpha/beta/milestone/release candidates beforehand. -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
getting multiple forms of the build date
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 Manifests, and just the month and year for substituting in to documentation publication date. Is there a way to get multiple, different formats for this? -Marshall - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: I have the right version, but maven can't find it
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 specific version is often a sign of poor-quality code (perhaps the dependent, perhaps the dependency, could even be both). -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Balance your desire for bells and whistles with the reality that only a little more than 2 percent of world population has broadband. -- Ledford and Tyler, _Google Analytics 2.0_ pgpzkvAKU9TZU.pgp Description: PGP signature
Re: I have the right version, but maven can't find it
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 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 specific version is often a sign of poor-quality code (perhaps the dependent, perhaps the dependency, could even be both). -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Balance your desire for bells and whistles with the reality that only a little more than 2 percent of world population has broadband. -- Ledford and Tyler, _Google Analytics 2.0_ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Fortify and Maven
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? /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 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: junit 4.8.1 - org.junit cannot be resolved
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 the broken junit 4.8.1 did exist in central for about 6 hours :( So is the new policy to fix broken artifacts, or leave them broken? IMO they must remain broken and version-bumped to deploy fixes. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Fortify and Maven
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, Larry Suto larry.s...@gmail.com wrote: 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? /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 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
Release dependency fails (2.0.9 vs 2.2.1)
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) -- has a dependency to child A 1.0.0.0_b0-snapshot With 2.0.9, can release b0 (mvn clean, release:prepare, release:perform on parent) and Child B is updated to depend on Child A 1.0.0.0_b0 and all is well - release is complete. When I update to Maven 2.2.1, Child A 1.0.0.0_b1 is built (it's in the target dir) but Child_B complains that it cannot find the dependency. I do have the pom locked down to use version 2.0 beta 7 of the release plugin so I'm going to try taking off that lockdown and see what I get with Maven 2.2.1. Anybody else experience release plugin problems of this nature with 2.2.x? Thanks! Randall
Re: Fortify and Maven
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 and...@hammar.net wrote: 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, Larry Suto larry.s...@gmail.com wrote: 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? /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 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: Release dependency fails (2.0.9 vs 2.2.1)
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 (1.0.0.0_b0-snapshot) | Child B (1.0.0.0_b0-snapshot) -- has a dependency to child A 1.0.0.0_b0-snapshot With 2.0.9, can release b0 (mvn clean, release:prepare, release:perform on parent) and Child B is updated to depend on Child A 1.0.0.0_b0 and all is well - release is complete. When I update to Maven 2.2.1, Child A 1.0.0.0_b1 is built (it's in the target dir) but Child_B complains that it cannot find the dependency. I do have the pom locked down to use version 2.0 beta 7 of the release plugin so I'm going to try taking off that lockdown and see what I get with Maven 2.2.1. Anybody else experience release plugin problems of this nature with 2.2.x? I remember to run into similar problems, however, it was already from 2.0.9 to 2.0.10 ... or so ;-) How do you reference ChildA in ChildB? Version inherited from depMgmt of parent? Own depMgmt in ChildB? Direct version in depepndencies section of ChildB? Indirect version definition with properties soemwhere? - Jörg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Fortify and Maven
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 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 and...@hammar.net wrote: 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, Larry Suto larry.s...@gmail.com wrote: 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? /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 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
Configure jetty port in profiles
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
scanIntervalSeconds10/scanIntervalSeconds
jettyEnvXml${basedir}/src/test/resources/jetty-env.xml/jettyEnvXml
connectors
connector
implementation=org.mortbay.jetty.nio.SelectChannelConnector
port80/port
maxIdleTime6/maxIdleTime
/connector
connector
implementation=org.mortbay.jetty.security.SslSocketConnector
port443/port
maxIdleTime6/maxIdleTime
keystorec:/xxx-ssl.keystore/keystore
passwordxxx/password
keyPasswordxxx/keyPassword
/connector
/connectors
/configuration
/plugin
The issue is that i want to change the jetty port only for my machine. So i
came accorss setting profiles.i can activate a specific profile using maven
jetty:run -Denvironment=mylocaljetty then that profile is pulled in
something like this
profile
activation
property
nameenvironment/name
valuemylocaljetty/value
/property
/activation
...
/profile
the issue is that in profile element how can i speciy the jetty:port and the
https credential detail. any examples.
Thanks
darniz
--
View this message in context:
http://old.nabble.com/Configure-jetty-port-in-profiles-tp28394619p28394619.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
RE: Release dependency fails (2.0.9 vs 2.2.1)
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 PM To: users@maven.apache.org Subject: Re: Release dependency fails (2.0.9 vs 2.2.1) 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 (1.0.0.0_b0-snapshot) | Child B (1.0.0.0_b0-snapshot) -- has a dependency to child A 1.0.0.0_b0-snapshot With 2.0.9, can release b0 (mvn clean, release:prepare, release:perform on parent) and Child B is updated to depend on Child A 1.0.0.0_b0 and all is well - release is complete. When I update to Maven 2.2.1, Child A 1.0.0.0_b1 is built (it's in the target dir) but Child_B complains that it cannot find the dependency. I do have the pom locked down to use version 2.0 beta 7 of the release plugin so I'm going to try taking off that lockdown and see what I get with Maven 2.2.1. Anybody else experience release plugin problems of this nature with 2.2.x? I remember to run into similar problems, however, it was already from 2.0.9 to 2.0.10 ... or so ;-) How do you reference ChildA in ChildB? Version inherited from depMgmt of parent? Own depMgmt in ChildB? Direct version in depepndencies section of ChildB? Indirect version definition with properties soemwhere? - Jörg - 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: [ANN] Apache Maven 3.0-beta-1 Released
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 avril 2010, Kristian Rosenvold a écrit : This will be fixed real soon, the site plugin needs a minor update. On Fri, Apr 23, 2010 at 11:06 PM, Kathryn Huxtable kath...@kathrynhuxtable.org wrote: Any reason why mvn clean package on the checked out source would yield: [INFO] --- maven-compiler-plugin:2.1:compile (default-compile) @ maven-site-plugin --- [INFO] Compiling 23 source files to /Users/huxtable/Documents/workspace/maven-site-plugin-3.0-beta-1-SNAPSHOT /target/classes [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] /Users/huxtable/Documents/workspace/maven-site-plugin-3.0-beta-1-SNAPSHOT /src/main/java/org/apache/maven/plugins/site/DefaultMavenReportExecutor.ja va:[209,41] cannot find symbol symbol : method calculateForkedExecutions(org.apache.maven.plugin.MojoExecution,org.apach e.maven.execution.MavenSession) location: interface org.apache.maven.lifecycle.LifecycleExecutor [ERROR] /Users/huxtable/Documents/workspace/maven-site-plugin-3.0-beta-1-SNAPSHOT /src/main/java/org/apache/maven/plugins/site/DefaultMavenReportExecutor.ja va:[213,45] cannot find symbol symbol : method executeForkedExecutions(org.apache.maven.plugin.MojoExecution,org.apache. maven.execution.MavenSession) location: interface org.apache.maven.lifecycle.LifecycleExecutor [INFO] 2 errors [INFO] - [INFO] [INFO] BUILD FAILURE -K On Apr 23, 2010, at 3:42 PM, Kathryn Huxtable wrote: Great! I'll try it out and let you know. You're probably already doing integration testing, so you probably already know anything I'll report. I'l check the JIRA before I complain... Thanks! -K On Apr 23, 2010, at 3:02 PM, Hervé BOUTEMY wrote: this one isn't done by Jason, but this won't give you an ETA neither ;) maven-site-plugin 3.0-beta-1 shouldn't be far: see [1] you can install it for yourself and see if it works we will probably put the release out in the next weeks Regards, Hervé https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+and+site+plug in Le vendredi 23 avril 2010, Kathryn Huxtable a écrit : I know Jason says he won't give ETAs, but is there any ETA on the site reporting? I make a lot of use of it, and I doubt I'm alone. My personal preference is to find some way to integrate the docbkx plugin with the site framework. I've got some code that does this for Maven 2, and it works for Maven 3, but the reports aren't generated. -K On Apr 23, 2010, at 8:05 AM, Benjamin Bentmann wrote: The Maven team is pleased to announce the release of Apache Maven 3.0-beta-1. Maven is a project comprehension and build tool, designed to simplify the process of maintaining a healthy development lifecycle for your project. You can read more here: http://maven.apache.org/ Downloads of source and binary distributions are listed in our download section: http://maven.apache.org/download.html A major goal of Maven 3.0 is to be compatible, to the extent possible, with existing plugins and projects designed for Maven 2.x. Users interested in testing this beta release should have a glance at the compatibility notes for known differences between Maven 3.0 and Maven 2.x: http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html If you encounter unexpected problems while using Maven 3.0-beta-1, please feel free to contact us via the Maven developer list: http://maven.apache.org/mail-lists.html Release Notes - Maven 2 3 - Version 3.0-beta-1 ** Bug * [MNG-1751] - merging metadata doesn't fail when timestamp is in the future * [MNG-2103] - Inheritance of plugin overrides that of execution * [MNG-] - dependency to dependency without source code fails * [MNG-2276] - profile activation by property doesn't work with properties defined in settings. * [MNG-2994] - Snapshot repositories are not checked when using ranges * [MNG-3092] - Version ranges with non-snapshot bounds can contain snapshot versions * [MNG-3133] - DefaultModelInheritence::appendPath assumes it is operating on interpolated/literal paths * [MNG-3470] - Build does not fail on corrupted POM even with checksumPolicy=fail * [MNG-3477] - Authentication failures on dependency download aren't reported
RE: Release plugin and updating a release with some fixes
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 dependency 1.5 =1.5.1 and then promote from that point.. otherwise you'll have to 'manage' (branch..merge..and run integrations tests) 2 separate trees Martin Gainty __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité 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. Date: Wed, 28 Apr 2010 11:13:31 -0400 Subject: Re: Release plugin and updating a release with some fixes From: w...@wantii.com To: users@maven.apache.org 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 thing sounds a bit hackish and you should get an MRM. Then, if you find bugs, you can make a branch based on the 1.5 tag, fix your bugs, then merge the changes back to trunk. You can also release from the branch and name it 1.5.1 (or similar). -Wes On Wed, Apr 28, 2010 at 10:23 AM, napple fabble jm.postili...@gmail.com wrote: 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 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. QUESTION: What do I do when I find some last bugs while installing the release and want to fix them. I would ideally like to have both 1.5 tag and the trunk (1.6-SNAPSHOT) updated with the fixes. Can I do this somehow conveniently with release plugin, or do I have to do it manually (if so, what's the best approach? just fix trunk and copy the changed to the tag?). -- View this message in context: http://maven-users.828.n2.nabble.com/Release-plugin-and-updating-a-release-with-some-fixes-tp4974743p4974743.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 -- Wes Wannemacher Head Engineer, WanTii, Inc. Need Training? Struts, Spring, Maven, Tomcat... Ask me for a quote! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org _ The New Busy think 9 to 5 is a cute idea. Combine multiple calendars with Hotmail. http://www.windowslive.com/campaign/thenewbusy?tile=multicalendarocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_5
maven-compiler-plugin with axis2-wsdl2code-maven-plugin
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 exclude**/excluded.java/exclude /excludes Is it a bug or I have something wrong in my POM.xml? There is how I define my plugins: plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration source1.5/source target1.5/target excludes excludetarget/**/MediatorServiceSkeleton.java/exclude /excludes generatedSourcesDirectorytarget/generatedSourcesDirectory /configuration /plugin plugin groupIdorg.apache.axis2.maven2/groupId artifactIdaxis2-wsdl2code-maven-plugin/artifactId version1.3/version executions execution goals goalwsdl2code/goal /goals configuration packageNamecom.openlane.mediator.mediatorservice/packageName wsdlFilesrc/main/webapp/WEB-INF/services/MediatorService/META-INF/MediatorService.wsdl/wsdlFile generateServerSidetrue/generateServerSide generateServicesXmltrue/generateServicesXml generateServerSideInterfacetrue/generateServerSideInterface databindingNameadb/databindingName outputDirectorytarget/outputDirectory /configuration /execution /executions dependencies dependency groupIdorg.apache.axis2/groupId artifactIdaxis2/artifactId version1.3/version /dependency /dependencies /plugin /plugins Thanks David
Release Plugin and local working copy changes
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 chance to try and reproduce it myself, does anyone know if anything changed in this regard lately? Mark -- Pull me down under... - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven scm plugin: accurev scm provider
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? E. On Fri, Apr 23, 2010 at 11:04 AM, Grant Gardner gr...@lastweekend.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 artifact version to 1.4-SNAPSHOT then build and install to your local repository. Then in your project pom add this as a dependency to the maven-scm-plugin as follows. build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-scm-plugin/artifactId version1.3/version dependencies dependency groupIdorg.apache.maven.scm/groupId artifactIdmaven-scm-provider-accurev/artifactId version1.4-SNAPSHOT/version /dependency /dependencies /plugin plugins /build On Wed, 21 Apr 2010 15:56:50 +0300, eyal edri eyal.e...@gmail.com wrote: Anyone has used accurev + scm plugin yet? i know issue 445 on the scm-accurev-provider should fix most problems once ver 1.4 is due, is there any way i can use the plugin in the meantime and test connection to the accurev server? thanks. - 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
