Re: Changing the groupId/artifactId of an artifact in the next version but keep maven conflict detection
The closest you will get is to deploy a relocation pom at the old GA with the new V., e.g. at groupIdorg.drools/groupId artifactIddrools-repository/artifactId version5.2.0/version it's not perfect (i.e. it will only notify people using ranges and only fools use ranges!) and it does not do exactly what you want, but it will at least give a bit more of a hint. I should probably add some goals to v-m-p to help trace relocation poms and add exclusions for the old locations to the tree -Stephen On 18 January 2011 07:58, Geoffrey De Smet ge0ffrey.s...@gmail.com wrote: Hi, We have a pom.xml for the drools guvnor repository jar, with this identification: groupIdorg.drools/groupId artifactIddrools-repository/artifactId version5.1.0/version Now, for the next version of that jar, we need to change the identification to: groupIdorg.drools.guvnor/groupId artifactIdguvnor-repository/artifactId version5.2.0/version It's the same code in the jar, but the original identification was wrong and we're fixing that now. The problem is, what happens if one of our users has this dependency tree? - foo -- foo depends on bar --- bar depends on org.drools:drools-repository:5.1.0 -- foo depends on org.drools.guvnor:guvnor-repository:5.2.0 Maven will not detect the dependency conflict between - org.drools:drools-repository:5.1.0 - org.drools.guvnor:guvnor-repository:5.2.0 and it will put both of them in the classpath, instead of just 5.2.0. Is there any way to tell maven in the 5.2.0 pom.xml, something like this: groupIdorg.drools.guvnor/groupId artifactIdguvnor-repository/artifactId version5.2.0/version legacy-identifications legacy-identification groupIdorg.drools/groupId artifactIddrools-repository/artifactId legacy-identification /legacy-identifications So it does detect the dependency conflict and lets just 5.2.0 survive? -- With kind regards, Geoffrey De Smet - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven release:perform deploy failed access denied
Ok, I'll try to precise what I'm saying. I understand that in the distrMgt, I have to set snapshot, release and eventually site url.. I understood in the log that the deploy task needs that tag. I noticed too that I need another tag in the pom file, a repositories tag. I wonder why I have to set twice where are my repositories ? Here's my file : repositories !-- use the following if you're not using a snapshot version. -- repository idrepository-releases/id nameReleases Repository/name url http://nexus/content/repositories/DNSCEReleases//url snapshots enabledfalse/enabled /snapshots /repository repository id-repository-snapshots/id nameSnapshots Repository/name urlhttp://nexus/content/repositories/DNSCESnapshots//url releases enabledfalse/enabled /releases snapshots enabledtrue/enabled /snapshots /repository /repositories distributionManagement !-- use the following if you're not using a snapshot version. -- repository idrepository-releases/id nameRepository Name/name urlhttp://nexus/content/repositories/DNSCESnapshots//url /repository !-- use the following if you ARE using a snapshot version. -- snapshotRepository idrepository-snapshots/id nameSnapshots Repository/name urlhttp://nexus/content/repositories/DNSCESnapshots//url /snapshotRepository /distributionManagement Maybe, in the distributionMgt tag, I just have to set the id of the repo described upon it ? Thx -- View this message in context: http://maven.40175.n5.nabble.com/Maven-release-perform-deploy-failed-access-denied-tp3339497p3345810.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: set up maven repository for all the mirrors
I should be possible, of course. I'd suggest to talk to Your company's network admin about Apache and DNS configuration. On 17/01/11 19:38, anemdhana wrote: Hello everyone, I found this is really useful to setup internal maven repository http://www.jfrog.org/products.php, which takes care of getting dependencies by looking into all repositories. A simple question, I want to setup this in an intranet environment; by allowing ldap authentication; Right now, I am able to access in my local box as, http://localhost:8080/artifactory with jetty-7 servelt container running on port 8080. is it possible to have customized url by having apache-webserver installed, like, http://repo.mycompany.com/artifactory - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven release:perform deploy failed access denied
Those are two totally different things. distMgmt is where you want to deploy to. repositories declare what repos you want to pull artifacts you depend on. /Anders On Tue, Jan 18, 2011 at 09:40, jeb001 jeremy.jar...@gmail.com wrote: Ok, I'll try to precise what I'm saying. I understand that in the distrMgt, I have to set snapshot, release and eventually site url.. I understood in the log that the deploy task needs that tag. I noticed too that I need another tag in the pom file, a repositories tag. I wonder why I have to set twice where are my repositories ? Here's my file : repositories !-- use the following if you're not using a snapshot version. -- repository idrepository-releases/id nameReleases Repository/name url http://nexus/content/repositories/DNSCEReleases/ /url snapshots enabledfalse/enabled /snapshots /repository repository id-repository-snapshots/id nameSnapshots Repository/name urlhttp://nexus/content/repositories/DNSCESnapshots/ /url releases enabledfalse/enabled /releases snapshots enabledtrue/enabled /snapshots /repository /repositories distributionManagement !-- use the following if you're not using a snapshot version. -- repository idrepository-releases/id nameRepository Name/name urlhttp://nexus/content/repositories/DNSCESnapshots//url /repository !-- use the following if you ARE using a snapshot version. -- snapshotRepository idrepository-snapshots/id nameSnapshots Repository/name urlhttp://nexus/content/repositories/DNSCESnapshots//url /snapshotRepository /distributionManagement Maybe, in the distributionMgt tag, I just have to set the id of the repo described upon it ? Thx -- View this message in context: http://maven.40175.n5.nabble.com/Maven-release-perform-deploy-failed-access-denied-tp3339497p3345810.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: Maven release:perform deploy failed access denied
Ok ! So, repository should design my nexus server ? and distMgt should design a file server ? -- View this message in context: http://maven.40175.n5.nabble.com/Maven-release-perform-deploy-failed-access-denied-tp3339497p3345828.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: Maven release:perform deploy failed access denied
Nope. you can (and should) deploy to your nexus/artifactory server. you can (and should) pull dependencies from your nexus/artifactory server. However, you might use groups to aggregate several repos in your nexus server so that you only need the one repository definition (and better yet keep that in your settings.xml as repository definitions in pom.xml files are discouraged... they slow down a build and they are set in stone repository urls are something that is known to change) I think the issue you are having originally is that you are trying to deploy to a group... nexus does not let you do that. -Stephen On 18 January 2011 08:49, jeb001 jeremy.jar...@gmail.com wrote: Ok ! So, repository should design my nexus server ? and distMgt should design a file server ? -- View this message in context: http://maven.40175.n5.nabble.com/Maven-release-perform-deploy-failed-access-denied-tp3339497p3345828.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: problem when upgrading from maven2 to maven3
See the Maven 3 compatibility note on dependency resolution: https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-DependencyResolution. It suggests to inspect the dependency tree that is printed when running Maven in debug mode. On 18/01/11 04:17, 刘勇坡 wrote: Can you tell me what I can do? and why a project work with maven2 well can't not be build with maven3? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven release:perform deploy failed access denied
ok... If I try to sum up... First issue was to use a groups URL of nexus.. ok, it's correct now. Then, both of the distMgt tag and repository set the same URL.. but repositories tag have to be moved in the settings.xml. Am I right now ? -- View this message in context: http://maven.40175.n5.nabble.com/Maven-release-perform-deploy-failed-access-denied-tp3339497p3345851.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: Maven release:perform deploy failed access denied
Normally, the urls for deploying snapshots and release are different. Surely there must be some kind of help/info where you work on how to configure this? Most of these configs depend on how the infrastructure is set up and it's very hard for us to tell you how your environment is. /Anders On Tue, Jan 18, 2011 at 10:08, jeb001 jeremy.jar...@gmail.com wrote: ok... If I try to sum up... First issue was to use a groups URL of nexus.. ok, it's correct now. Then, both of the distMgt tag and repository set the same URL.. but repositories tag have to be moved in the settings.xml. Am I right now ? -- View this message in context: http://maven.40175.n5.nabble.com/Maven-release-perform-deploy-failed-access-denied-tp3339497p3345851.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: Maven release:perform deploy failed access denied
On 18 January 2011 09:08, jeb001 jeremy.jar...@gmail.com wrote: ok... If I try to sum up... First issue was to use a groups URL of nexus.. ok, it's correct now. Correct Then, both of the distMgt tag and repository set the same URL.. Incorrect... distMgt should point to the repo. repositories should point to the group that aggregates the repo and central and whatever other repos you want. but repositories tag have to be moved in the settings.xml. It's optional to move it, but its best practice... in fact better practice is just to use a mirrorOf*/mirrorOf and not have any repositories in your settings.xml Am I right now ? -- View this message in context: http://maven.40175.n5.nabble.com/Maven-release-perform-deploy-failed-access-denied-tp3339497p3345851.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: Changing the groupId/artifactId of an artifact in the next version but keep maven conflict detection
All this emphasizes how important it is to get the GA right in the beginning. As long as no one depends on your artifacts it's not a big deal, but when you have lots of users you will cause issues. If you absolutely do need to change GA, you must broadcast this to your users very clearly! The issues that could arise are not easily understandable, IMHO, to the normal devs just using Maven as a magic dependency management tool. /Anders On Tue, Jan 18, 2011 at 09:04, Stephen Connolly stephen.alan.conno...@gmail.com wrote: The closest you will get is to deploy a relocation pom at the old GA with the new V., e.g. at groupIdorg.drools/groupId artifactIddrools-repository/artifactId version5.2.0/version it's not perfect (i.e. it will only notify people using ranges and only fools use ranges!) and it does not do exactly what you want, but it will at least give a bit more of a hint. I should probably add some goals to v-m-p to help trace relocation poms and add exclusions for the old locations to the tree -Stephen On 18 January 2011 07:58, Geoffrey De Smet ge0ffrey.s...@gmail.com wrote: Hi, We have a pom.xml for the drools guvnor repository jar, with this identification: groupIdorg.drools/groupId artifactIddrools-repository/artifactId version5.1.0/version Now, for the next version of that jar, we need to change the identification to: groupIdorg.drools.guvnor/groupId artifactIdguvnor-repository/artifactId version5.2.0/version It's the same code in the jar, but the original identification was wrong and we're fixing that now. The problem is, what happens if one of our users has this dependency tree? - foo -- foo depends on bar --- bar depends on org.drools:drools-repository:5.1.0 -- foo depends on org.drools.guvnor:guvnor-repository:5.2.0 Maven will not detect the dependency conflict between - org.drools:drools-repository:5.1.0 - org.drools.guvnor:guvnor-repository:5.2.0 and it will put both of them in the classpath, instead of just 5.2.0. Is there any way to tell maven in the 5.2.0 pom.xml, something like this: groupIdorg.drools.guvnor/groupId artifactIdguvnor-repository/artifactId version5.2.0/version legacy-identifications legacy-identification groupIdorg.drools/groupId artifactIddrools-repository/artifactId legacy-identification /legacy-identifications So it does detect the dependency conflict and lets just 5.2.0 survive? -- With kind regards, Geoffrey De Smet - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven release:perform deploy failed access denied
On 18 January 2011 09:25, Stephen Connolly stephen.alan.conno...@gmail.com wrote: On 18 January 2011 09:08, jeb001 jeremy.jar...@gmail.com wrote: ok... If I try to sum up... First issue was to use a groups URL of nexus.. ok, it's correct now. Correct Then, both of the distMgt tag and repository set the same URL.. Incorrect... distMgt should point to the repo. repositories should point to the group that aggregates the repo and central and whatever other repos you want. but repositories tag have to be moved in the settings.xml. It's optional to move it, but its best practice... in fact better practice is just to use a mirrorOf*/mirrorOf and not have any repositories in your settings.xml Just to clarify: If you have repositories in your pom.xml then every build which needs to check for artifacts will check central and all the repositories listed in your pom... that is two web requests and the request to central will be first, slowing down your build and increasing your bandwidth bills... when you change your infrastructure, any projects depending on the old deployed pom will gain an extra invalid url to check against and you will have to wait for that to time-out during a build... so this gives the slowest build If you have repositories in your settings.xml you still get multiple repositories but at least you can update invalid urls and remove having to wait for the timeout If you use mirrorOf*/mirrorOf in your settings.xml then you only ever have one respoitory queried during your build so this gives the fastest builds... also mirrorOf handles both pluginRepositories and repositories reducing xml verbage Am I right now ? -- View this message in context: http://maven.40175.n5.nabble.com/Maven-release-perform-deploy-failed-access-denied-tp3339497p3345851.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven release:perform deploy failed access denied
Ok, so.. In my settings.xml : mirror idrepository/id nameMiror nexus/name urlhttp://nexus/content/groups/MyRepositories//url mirrorOf*,!repository-releases,!repository-snapshots/mirrorOf /mirror in the pom.xml I removed repositories tag and keep that : distributionManagement !-- use the following if you're not using a snapshot version. -- repository idrepository-releases/id nameRepository Name/name urlhttp://nexus/content/repositories/Releases//url /repository !-- use the following if you ARE using a snapshot version. -- snapshotRepository idrepository-snapshots/id nameSnapshots Repository/name urlhttp://nexus/content/repositories/Snapshots//url /snapshotRepository /distributionManagement I'm still having that error :-( : [INFO] [INFO] Failed to configure plugin parameters for: org.apache.maven.plugins:maven-deploy-plugin:2.4 [INFO] [INFO] check that the following section of the pom.xml is present and correct: [INFO] [INFO] distributionManagement [INFO] !-- use the following if you're not using a snapshot version. -- [INFO] repository [INFO] idrepo/id [INFO] nameRepository Name/name [INFO] urlscp://host/path/to/repo/url [INFO] /repository [INFO] !-- use the following if you ARE using a snapshot version. -- [INFO] snapshotRepository [INFO] idrepo/id [INFO] nameRepository Name/name [INFO] urlscp://host/path/to/repo/url [INFO] /snapshotRepository [INFO] /distributionManagement [INFO] [INFO] Cause: Class 'org.apache.maven.artifact.repository.ArtifactRepository' cannot be instantiated ... -- View this message in context: http://maven.40175.n5.nabble.com/Maven-release-perform-deploy-failed-access-denied-tp3339497p3345882.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: Maven release:perform deploy failed access denied
with more details from the logs... INFO] [DEBUG] Trace [INFO] org.apache.maven.lifecycle.LifecycleExecutionException: Error configuring: org.apache.maven.plugins:maven-deploy-plugin. Reason: Unable to parse the created DOM for plugin configuration [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:723) [INFO] at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556) -- View this message in context: http://maven.40175.n5.nabble.com/Maven-release-perform-deploy-failed-access-denied-tp3339497p3345894.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: Maven release:perform deploy failed access denied
INFO] [DEBUG] Trace [INFO] org.apache.maven.lifecycle.LifecycleExecutionException: Error configuring: org.apache.maven.plugins:maven-deploy-plugin. Reason: Unable to parse the created DOM for plugin configuration I've seen this a few times related to the deploy plugin in the last ~8 months, but haven't seen any follow up posts saying oh we solved it, here's what was wrong. But I assume the other posters must have fixed their troubles, or they'd still be making noise and complaining about how they can't deploy things any more. So please, once you sort this out, post back with the root cause and your solution, for the benefit of others on the ml... Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven release:perform deploy failed access denied
So please, once you sort this out, post back with the root cause and your solution, for the benefit of others on the ml... Hmmm going back and looking at a few of those emails, I think the problem is that people are putting the distributionManagement node in the wrong spot in their pom file. It does not go inside build/ or anywhere else, but rather should simply be directly inside project/. What is the xpath to this node in your pom file? It should be simply /project/distributionManagement. Anything else will cause problems. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
One project per package or multiple packages in same project?
Hi, In http://maven.40175.n5.nabble.com/Maven-Problem-in-including-excluding-some-java-packages-in-the-src-while-creating-a-jar-td2641836.htmlAnders strongly discouraged having more than one package per project. However, I have a Maven conceptual doubt regarding this and thought you might be able to help. I have a webapp project in the format: -Parent --ModuleServices --ModulePersistence --ModuleWeb Packaging the Parent returns what I am really interested in, the .WAR file returned from the ModuleWeb. However, I do need more than one WAR: two for the client (one with a test profile, with some test configuration strings like test-db and that returns a myproject-test.war; and another myproject.war which will be the production environment). Both will be installed on the same machine. Now, in addition to this, you also might see that these .war will be specific to a particular client (it's his db, his credentials..). Until I saw this post, I had different maven profiles (these 2 plus a development one) and my only doubt was which profile will be active when I deploy the maven artifact?). Now it got me thinking: should I have one project per profile instead? Although I follow your logic, this approach seems cumbersome and I'm not even sure how I'd implement it. Can you share your thoughts on how the best Maven approach would be? Thank you for your help, Miguel Almeida
Re: Maven release:perform deploy failed access denied
..unfortunately, I think I'm right in the pom structure : ?xml version=1.0 encoding=UTF-8? 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/xsd/maven-4.0.0.xsd; modelVersion4.0.0/modelVersion groupIdxxx/groupId artifactIdxxx/artifactId version0.0.7-SNAPSHOT/version packagingpom/packaging namexxx/name urlxxx/url properties project.build.sourceEncodingUTF-8/project.build.sourceEncoding /properties dependencies !-- -- /dependencies build plugins plugin artifactIdmaven-compiler-plugin/artifactId version2.3.1/version configuration source1.5/source target1.5/target /configuration /plugin plugin artifactIdmaven-release-plugin/artifactId version2.0-beta-9/version configuration / /plugin plugin artifactIdmaven-javadoc-plugin/artifactId version2.5/version configuration minmemory128m/minmemory maxmemory1g/maxmemory skiptrue/skip /configuration /plugin /plugins /build scm developerConnectionscm:cvs:xxx/developerConnection /scm distributionManagement !--- /distributionManagement modules modulexx/module modulexx/module modulexx/module /modules /project -- View this message in context: http://maven.40175.n5.nabble.com/Maven-release-perform-deploy-failed-access-denied-tp3339497p3345936.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: One project per package or multiple packages in same project?
Have different projects for the different wars and then externalize any configuration stuff outside of your wars. We've been over this many times now. Here's one thread in the archive: http://www.mail-archive.com/users@maven.apache.org/msg115082.html /Anders On Tue, Jan 18, 2011 at 11:17, Miguel Almeida migueldealme...@gmail.comwrote: Hi, In http://maven.40175.n5.nabble.com/Maven-Problem-in-including-excluding-some-java-packages-in-the-src-while-creating-a-jar-td2641836.htmlAnders strongly discouraged having more than one package per project. However, I have a Maven conceptual doubt regarding this and thought you might be able to help. I have a webapp project in the format: -Parent --ModuleServices --ModulePersistence --ModuleWeb Packaging the Parent returns what I am really interested in, the .WAR file returned from the ModuleWeb. However, I do need more than one WAR: two for the client (one with a test profile, with some test configuration strings like test-db and that returns a myproject-test.war; and another myproject.war which will be the production environment). Both will be installed on the same machine. Now, in addition to this, you also might see that these .war will be specific to a particular client (it's his db, his credentials..). Until I saw this post, I had different maven profiles (these 2 plus a development one) and my only doubt was which profile will be active when I deploy the maven artifact?). Now it got me thinking: should I have one project per profile instead? Although I follow your logic, this approach seems cumbersome and I'm not even sure how I'd implement it. Can you share your thoughts on how the best Maven approach would be? Thank you for your help, Miguel Almeida
Re: Maven release:perform deploy failed access denied
On 18 January 2011 09:40, jeb001 jeremy.jar...@gmail.com wrote: Ok, so.. In my settings.xml : mirror idrepository/id nameMiror nexus/name urlhttp://nexus/content/groups/MyRepositories//url mirrorOf*,!repository-releases,!repository-snapshots/mirrorOf not related to your issue, but still just mirrorOf*/mirrorOf you should have http://nexus/content/groups/MyRepositories/ aggregating all the repos even repository-releases and repository-snapshots /mirror in the pom.xml I removed repositories tag and keep that : distributionManagement !-- use the following if you're not using a snapshot version. -- repository idrepository-releases/id nameRepository Name/name urlhttp://nexus/content/repositories/Releases//url /repository !-- use the following if you ARE using a snapshot version. -- snapshotRepository idrepository-snapshots/id nameSnapshots Repository/name urlhttp://nexus/content/repositories/Snapshots//url /snapshotRepository /distributionManagement I'm still having that error :-( : [INFO] [INFO] Failed to configure plugin parameters for: org.apache.maven.plugins:maven-deploy-plugin:2.4 [INFO] [INFO] check that the following section of the pom.xml is present and correct: [INFO] [INFO] distributionManagement [INFO] !-- use the following if you're not using a snapshot version. -- [INFO] repository [INFO] idrepo/id [INFO] nameRepository Name/name [INFO] urlscp://host/path/to/repo/url [INFO] /repository [INFO] !-- use the following if you ARE using a snapshot version. -- [INFO] snapshotRepository [INFO] idrepo/id [INFO] nameRepository Name/name [INFO] urlscp://host/path/to/repo/url [INFO] /snapshotRepository [INFO] /distributionManagement [INFO] [INFO] Cause: Class 'org.apache.maven.artifact.repository.ArtifactRepository' cannot be instantiated ... -- View this message in context: http://maven.40175.n5.nabble.com/Maven-release-perform-deploy-failed-access-denied-tp3339497p3345882.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven release:perform deploy failed access denied
Hum.. I tried something else, I launched the mvn:deploy task, and it works !! ... I jus't don't understand... any idea ? -- View this message in context: http://maven.40175.n5.nabble.com/Maven-release-perform-deploy-failed-access-denied-tp3339497p3346122.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: Problem with the release:perform
I've got exactly the same issue... Mvn:deploy works, but, deploy goal fails in release:perform goal... -- View this message in context: http://maven.40175.n5.nabble.com/Problem-with-the-release-perform-tp44484p3346125.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: Maven release:perform deploy failed access denied
hi! Please look at the file permissions on your server, maybe the file got uploaded by someone else and you have no right to write to this directory. To prevent such situations, one usually uses the following settings.xml configuration: server idyourServerId/id usernameyourusername/username passwordyourpassword/password directoryPermissions0775/directoryPermissions filePermissions0664/filePermissions /server Rerun the release with the -X option and use | tee mvn.log to catch the full output of the maven run. LieGrue, strub PS: I assume you substituted your servername in Uploading: http://serverIp/nexus/content/groups/MyRepositories//com/project/Parent/0.0.5/Parent-0.0.5.pom , right? --- On Tue, 1/18/11, jeb001 jeremy.jar...@gmail.com wrote: From: jeb001 jeremy.jar...@gmail.com Subject: Re: Maven release:perform deploy failed access denied To: users@maven.apache.org Date: Tuesday, January 18, 2011, 12:48 PM Hum.. I tried something else, I launched the mvn:deploy task, and it works !! ... I jus't don't understand... any idea ? -- View this message in context: http://maven.40175.n5.nabble.com/Maven-release-perform-deploy-failed-access-denied-tp3339497p3346122.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven release:perform deploy failed access denied
I tried that, still the same result... I begin to think that a single module project should be more easy to work with... -- View this message in context: http://maven.40175.n5.nabble.com/Maven-release-perform-deploy-failed-access-denied-tp3339497p3346186.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: problem when upgrading from maven2 to maven3
I encountered similar problem when upgrading from M2 to M3. The cause was 2 different versions of Hibernate jars on the classpath. It seems M3's transitive dependency resolution is more inclusive (more accurate?!). You may need to exclude a transitive dep (or drop use of an unnecessary dep). For conflicts like that, the offending dep's POM config sometimes benefit from scope adjusting, perhaps to optional, to prevent same problem for others. On Tue, Jan 18, 2011 at 3:07 AM, Marc Rohlfs pomar...@googlemail.com wrote: See the Maven 3 compatibility note on dependency resolution: https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-DependencyResolution. It suggests to inspect the dependency tree that is printed when running Maven in debug mode. On 18/01/11 04:17, 刘勇坡 wrote: Can you tell me what I can do? and why a project work with maven2 well can't not be build with maven3? - 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
org.codehaus.modello.ModelloCli fails parsing maven.mdo on OpenVMS
I am about to build apache-maven-2.2.1 on OpenVMS using either ant 1.7
or ant 1.6.5 from the NetBeans IDE 6.5.1
Just substituted M2_HOME by MVN_HOME for convenient.
I managed that ant get could download the artifacts from central
repository straigth into OpenVMS; for that to work, for that to pass my
firewall, I added the follwing logical to OpenVMS.
$ define/process -Dhttp.authpreference=Basic
-Dhttp.proxyhost=myprocx.com -Dhttp.proxyport=8080
-Dhttp.proxyuser=mydomainusername -Dhttp.proxypassword=mydoaminpassword
So the only thing one can not do with setproxy in ant is to give a
AuthenticationSchema preference, but as we access via http we can use it
like from maven, and since there is no more needs for any setproxy in
the build.xml file.
After doing so the pull target of the bootstrap-build.xml was working
properly and all dependent artifacts are now downloaded straigth into
the OpenVMS maven repository;
hence I did the next command line
$ ant -v -Dmaven.home=/dkb3/stadelma/apache-maven-2_2_1 -f
bootstrap-build.xml generate-sources
And that gives me an error which you migth be able to give me a bit
advise. See to verbos output (few overides deleted)
I toke out java fork=fork from bootstratp-build.xml setting up the
macrodef for modello, but no effect; so I changed this back.
I checked out by an editor that maven.mdo file for proper formats; BUT
I can't see anything wrong with it; also the same files build perfect on
the windows system, just not on openVMS.
Could it be a parser problem?
If yes is there a way to exchange the parser for the source generating
step ?
Josef
Apache Ant version 1.6.5 compiled on July 14 2006
Buildfile:
/INTEG1$DKB3/stadelma/sw-projekte/asf/maven/maven-2/tags/maven-2_2_1/boo
tstrap-build.xml
Detected Java version: 1.5 in: /ide$java_root/jre
Detected OS: OpenVMS
parsing buildfile
/INTEG1$DKB3/stadelma/sw-projekte/asf/maven/maven-2/tags/maven-2_2_1/boo
tstrap-build.xml with URI =
file:///INTEG1$DKB3/stadelma/sw-projekte/asf/maven/maven-2/tags/maven-2_
2_1/bootstrap-build.xml
Project base dir set to:
/INTEG1$DKB3/stadelma/sw-projekte/asf/maven/maven-2/tags/maven-2_2_1
Build sequence for target(s) `generate-sources' is [initTaskDefs,
isMavenHomeSet, initLocalRepo, init, read-poms, pull, generate-sources]
Complete build sequence is [initTaskDefs, isMavenHomeSet, initLocalRepo,
init, read-poms, pull, generate-sources, clean-bootstrap, compile-boot,
maven-compile, maven-assembly, extract-assembly, all, its-setup,
its-win32, its-unix, run-its, with-its, set-temp-maven-home, ]
initTaskDefs:
Loading
/INTEG1$DKB3/stadelma/sw-projekte/asf/maven/maven-2/tags/maven-2_2_1/pom
.xml
parsing buildfile
jar:file:/INTEG1$DKB3/stadelma/sw-projekte/asf/maven/maven-2/tags/maven-
2_2_1/maven-ant-tasks-2.0.8.jar!/org/apache/maven/artifact/ant/antlib.xm
l with URI =
jar:file:/INTEG1$DKB3/stadelma/sw-projekte/asf/maven/maven-2/tags/maven-
2_2_1/maven-ant-tasks-2.0.8.jar!/org/apache/maven/artifact/ant/antlib.xm
l
isMavenHomeSet:
Loading Environment env.
Property ${env.MVN_HOME} has not been set
Using Maven home at: /dkb3/stadelma/apache-maven-2_2_1
initLocalRepo:
Using the local repository at: /dkb3/stadelma/.m2/repository
init:
Loading
/INTEG1$DKB3/stadelma/sw-projekte/asf/maven/maven-2/tags/maven-2_2_1/pom
.xml
maven.home = /dkb3/stadelma/apache-maven-2_2_1
maven.assembly =
/INTEG1$DKB3/stadelma/sw-projekte/asf/maven/maven-2/tags/maven-2_2_1/apa
che-maven/target/apache-maven-2.2.1-bin.zip
read-poms:
Copying 1 file to
/INTEG1$DKB3/stadelma/sw-projekte/asf/maven/maven-2/tags/maven-2_2_1
Copying
/INTEG1$DKB3/stadelma/sw-projekte/asf/maven/maven-2/tags/maven-2_2_1/pom
.xml to
/INTEG1$DKB3/stadelma/sw-projekte/asf/maven/maven-2/tags/maven-2_2_1/dep
endencies.xml
Replacing in
/INTEG1$DKB3/stadelma/sw-projekte/asf/maven/maven-2/tags/maven-2_2_1/dep
endencies.xml: !--start-- -- !--
Replacing in
/INTEG1$DKB3/stadelma/sw-projekte/asf/maven/maven-2/tags/maven-2_2_1/dep
endencies.xml: !--end-- -- --
Loading Maven settings file: /dkb3/stadelma/.m2/settings.xml
Using remote repositories:
- id=central, url=http://repo.exist.com/maven2, releases=enabled,
snapshots=disabled, proxy=bcproxyserver.ch.winterthur.com
Deleting:
/INTEG1$DKB3/stadelma/sw-projekte/asf/maven/maven-2/tags/maven-2_2_1/dep
endencies.xml
Loading Maven settings file: /dkb3/stadelma/.m2/settings.xml
pull:
Loading Maven settings file: /dkb3/stadelma/.m2/settings.xml
Maven Ant Tasks version: 2.0.8
Using local repository: /dkb3/stadelma/.m2/repository
Resolving dependencies...
Using remote repositories:
- id=apache.snapshots, url=http://repository.apache.org/snapshots,
releases=disabled, snapshots=enabled,
proxy=bcproxyserver.ch.winterthur.com
- id=central, url=http://repo.exist.com/maven2, releases=enabled,
snapshots=disabled, proxy=bcproxyserver.ch.winterthur.com
org.apache.maven:maven:pom:2.2.1 (selected)
commons-cli:commons-cli:jar:1.2:compile (selected)
org.apache.maven.doxia:doxia-sink-api:jar:1.1:compile (selected)
site.xml: property interpolation and inheritance
Hi all,
I have a question regarding property interpolation and inheritance in
the case of site descriptors. I looks to my like these behave
differently than property interpolation and inheritance in the case of
the POM.
Suppose I have the following element within my parent project's site.xml
bannerRight
name${project.description}/name
/bannerRight
Now a child project's site:effective-site contains the following:
bannerRight
nameDescription of the *parent* project/name
/bannerRight
Why is that? Inherited elements in the POM (e.g., url) are subject to
property interpolation in the context of the child project rather than
the parent project. Why is this different for site descriptors? And is
there a workaround other than copy-and-pasting the site.xml into the
child project.
FWIW, I am using Maven 3.0.2, the maven-site-plugin version 3.0-beta-3,
and have attached my descriptor to the parent project; the attached
descriptor is already fully interpolated. :-(
Best wishes,
Andreas
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: org.codehaus.modello.ModelloCli fails parsing maven.mdo on OpenVMS
Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException: end tag name /field must match start tag name fields from line 79 (position: TEXT seen .../field /field... @103:33) Did you check around line 79, the /field and /fields etc? Are you certain this is exactly the same file that is processed with no errors on Windows with zero edits or modifications, the same revision number, etc? Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: org.codehaus.modello.ModelloCli fails parsing maven.mdo on OpenVMS
I am using NetBeans IDE with distributed NetBeans Plugin from HP to connect to OpenVMS That way I can say that any .mdo file is an ASCII file to be sent/received by the FTP File cabinet to/from openVMS. So over all I have avery convenient way to put or get files to from my OpenVMS FTP File cabinet. And I just did a get from server and then applied a local PC based Build of the target generate-sources and all went OK. I doubble checkk with the EDT on OpenVMS and it seams a plain vanilla XML file. Because NetBeans said the file type is unknown I assigned it a Mime type of (application/xml) I took NetBeans and I applied an xml check and an xml validation and all went Ok. I went online to connect via FTP to my OpenVMS system and I did put file to server I toke my plain old OpenVMS EDT and I could edit it without any troubles. and I marked line 79 with EDT and went down to line 103 with EDT and the look all the same in OpenVMS EDIT EDT and in NetBeans, guess there is a parser problem maybe with encoding as in OpenVMS we normally use ISO-8895-1 not UTF-8. We can say it is the same content. And you want beleave it ... after I toke out the content of the first 4 description /description In particular the CDATA sections but left descriptionTest /description the parsing went well over maven.mdo (all 3 gen-sets), lifecycle.mdo (all 3 gen sets), but failed again for the plugin-registry.mdo with the java gen set. Maybe you have another advise for me. Josef ... classes class rootElement=true xml.tagName=project nameModel/name superClassModelBase/superClass description ![CDATA[ The codelt;projectgt;/code element is the root of the descriptor. The following table lists all of the possible child elements. ]] /description version3.0.0+/version fields . this is line 79 in OpenVMS EDT !-- == -- !-- Model Version -- !-- == -- field namepomVersion/name version3.0.0/version requiredtrue/required typeString/type description ![CDATA[ Declares to which version of project descriptor this POM conforms. The only valid value is code3/code. ]] /description /field field namemodelVersion/name version4.0.0/version requiredtrue/required descriptionDeclares to which version of project descriptor this POM conforms./description typeString/type /field .and this is line 103 in openVMS EDT and the same is shown in NetBeans IDE Editor !-- == -- !-- Parent Model -- !-- == -- -Ursprüngliche Nachricht- Von: Wayne Fay [mailto:wayne...@gmail.com] Gesendet: Dienstag, 18. Januar 2011 16:10 An: Maven Users List Betreff: Re: org.codehaus.modello.ModelloCli fails parsing maven.mdo on OpenVMS Caused by: org.codehaus.plexus.util.xml.pull.XmlPullParserException: end tag name /field must match start tag name fields from line 79 (position: TEXT seen .../field /field... @103:33) Did you check around line 79, the /field and /fields etc? Are you certain this is exactly the same file that is processed with no errors on Windows with zero edits or modifications, the same revision number, etc? Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven release:perform deploy failed access denied
Stephen is right about how to set up Nexus. You probably should have got all this advice from the Nexus installation docs. Read them and direct some/most of these questions to the Nexus forum. Ron On 18/01/2011 4:25 AM, Stephen Connolly wrote: On 18 January 2011 09:08, jeb001jeremy.jar...@gmail.com wrote: ok... If I try to sum up... First issue was to use a groups URL of nexus.. ok, it's correct now. Correct Then, both of the distMgt tag and repository set the same URL.. Incorrect... distMgt should point to the repo. repositories should point to the group that aggregates the repo and central and whatever other repos you want. but repositories tag have to be moved in the settings.xml. It's optional to move it, but its best practice... in fact better practice is just to use amirrorOf*/mirrorOf and not have any repositories in your settings.xml Am I right now ? -- View this message in context: http://maven.40175.n5.nabble.com/Maven-release-perform-deploy-failed-access-denied-tp3339497p3345851.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: site.xml: property interpolation and inheritance
That's an old bug: http://jira.codehaus.org/browse/MSITE-135
I am currently looking at site inheritance issues, maybe I'll get to it...
-Lukas
Andreas Sewe wrote:
Hi all,
I have a question regarding property interpolation and inheritance in
the case of site descriptors. I looks to my like these behave
differently than property interpolation and inheritance in the case of
the POM.
Suppose I have the following element within my parent project's site.xml
bannerRight
name${project.description}/name
/bannerRight
Now a child project's site:effective-site contains the following:
bannerRight
nameDescription of the *parent* project/name
/bannerRight
Why is that? Inherited elements in the POM (e.g., url) are subject to
property interpolation in the context of the child project rather than
the parent project. Why is this different for site descriptors? And is
there a workaround other than copy-and-pasting the site.xml into the
child project.
FWIW, I am using Maven 3.0.2, the maven-site-plugin version 3.0-beta-3,
and have attached my descriptor to the parent project; the attached
descriptor is already fully interpolated. :-(
Best wishes,
Andreas
-
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
Hibernate 3.6.0 and Maven
Does anyone have a working pom file for Hibernate 3.5.x or 3.6.x? This is what I have now: dependency groupIdorg.hibernate/groupId artifactIdhibernate/artifactId version3.5.3-Final/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-entitymanager/artifactId version3.5.3-Final/version /dependency [ERROR] Failed to execute goal on project ctjava: Could not resolve dependencies for project net.cuprak.web:ctjava:war:1.0-SNAPSHOT: Could not find artifact org.hibernate:hibernate:jar:3.5.3-Final in jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public-jboss/) - [Help 1] I look at the repository and it looks to me like that dependency exists. I am trying to get off of Hibernate 3.2.5. Thanks, -Ryan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Create a common/shared task for the maven-antrun-plugin ?
In a parent I define some properties that are used in a lot of sub
modules in the maven-antrun-plugin. All these sub modules needs to
execute the exact same tasks so it could be nice to define this task
once in the parent.
But is it possible to define a global maven-antrun task in a parent
that can be optionally used in a sub module?
I have tried to move the maven-antrun-plugin to the parent's
pluginManagement and then define the tasks there. But I have another
sub module that don't need to to run this global task. But since its
inherited from the parent I am a bit stuck here.
Is it possible to define only a a task that can be inserted without
having to modify the maven-antrun-plugin for all sub modules??
Here is how its used in a sub module:
plugin
artifactIdmaven-antrun-plugin/artifactId
version1.6/version
executions
execution
idtest/id
phasedeploy/phase
goals
goalrun/goal
/goals
configuration
tasks
!-- run a bunch of sshexec and scp tasks.
Could be
nice if we could do the following: --
my.task run special task defined in parent /my.task
/tasks
/configuration
/execution
/executions
dependencies
dependency
groupIdorg.apache.ant/groupId
artifactIdant-jsch/artifactId
version${ant.jsch.version}/version
/dependency
/dependencies
/plugin
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: site.xml: property interpolation and inheritance
Hi Lukas, That's an old bug: http://jira.codehaus.org/browse/MSITE-135 *sigh* I should really check the issue tracker first. :-( I am currently looking at site inheritance issues, maybe I'll get to it... That would be great. Thanks. Andreas - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Changing the groupId/artifactId of an artifact in the next version but keep maven conflict detection
There should be some support for changing the GA. Getting it right immediately, forever in the beginning is not realistic. Projects names change (hudson - jenkins, drools-solver - drools-planner), and subprojects graduate away from their parent project (turbine-maven - maven). There are plenty of big projects that changed their GA's. Even though we will boradcast it to our users (and hopefully a good percentage will hear it), it will not prevent this scenario for the developers on foo, which are not the developers or bar or drools: - foo -- foo depends on bar --- bar depends on org.drools:drools-repository:5.1.0 -- foo depends on org.drools.guvnor:guvnor-repository:5.2.0 Op 18-01-11 10:29, Anders Hammar schreef: All this emphasizes how important it is to get the GA right in the beginning. As long as no one depends on your artifacts it's not a big deal, but when you have lots of users you will cause issues. If you absolutely do need to change GA, you must broadcast this to your users very clearly! The issues that could arise are not easily understandable, IMHO, to the normal devs just using Maven as a magic dependency management tool. /Anders On Tue, Jan 18, 2011 at 09:04, Stephen Connolly stephen.alan.conno...@gmail.com wrote: The closest you will get is to deploy a relocation pom at the old GA with the new V., e.g. at groupIdorg.drools/groupId artifactIddrools-repository/artifactId version5.2.0/version it's not perfect (i.e. it will only notify people using ranges and only fools use ranges!) and it does not do exactly what you want, but it will at least give a bit more of a hint. I should probably add some goals to v-m-p to help trace relocation poms and add exclusions for the old locations to the tree -Stephen On 18 January 2011 07:58, Geoffrey De Smetge0ffrey.s...@gmail.com wrote: Hi, We have a pom.xml for the drools guvnor repository jar, with this identification: groupIdorg.drools/groupId artifactIddrools-repository/artifactId version5.1.0/version Now, for the next version of that jar, we need to change the identification to: groupIdorg.drools.guvnor/groupId artifactIdguvnor-repository/artifactId version5.2.0/version It's the same code in the jar, but the original identification was wrong and we're fixing that now. The problem is, what happens if one of our users has this dependency tree? - foo -- foo depends on bar --- bar depends on org.drools:drools-repository:5.1.0 -- foo depends on org.drools.guvnor:guvnor-repository:5.2.0 Maven will not detect the dependency conflict between - org.drools:drools-repository:5.1.0 - org.drools.guvnor:guvnor-repository:5.2.0 and it will put both of them in the classpath, instead of just 5.2.0. Is there any way to tell maven in the 5.2.0 pom.xml, something like this: groupIdorg.drools.guvnor/groupId artifactIdguvnor-repository/artifactId version5.2.0/version legacy-identifications legacy-identification groupIdorg.drools/groupId artifactIddrools-repository/artifactId legacy-identification /legacy-identifications So it does detect the dependency conflict and lets just 5.2.0 survive? -- With kind regards, Geoffrey De Smet - 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 -- With kind regards, Geoffrey De Smet - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Create a common/shared task for the maven-antrun-plugin ?
you might consider throwing it in a maven plugin (sounds scary, it isn't) use groovy's ant dsl to slap it together http://groovy.codehaus.org/Using+Ant+from+Groovy i'm using that pattern now to wrap around an ant task, you can take a look at it if you want: http://code.google.com/p/indoorsdog/source/browse/jacoco/trunk/jacoco-maven-plugin/src/main/groovy/org/indoorsdog/jacoco/maven/plugin/internal/AgentMojo.groovy -- View this message in context: http://maven.40175.n5.nabble.com/Create-a-common-shared-task-for-the-maven-antrun-plugin-tp3346449p3346458.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
surefire classpath problems with maven 3 parallel
Hi, while migrating to maven 3 (a large multi module project with 200 maven projects) I ran into a lot of surefire JUnit problems. The whole project builds correct with maven 3 serial build (without -T option). I've isolated problematic tests and for them I use the surefire configuration forkModealways/forkMode. This solved my System-property based parts of my projects so I'm generally able to build/test in parallel. But I still have some strange ClassNotFound exceptions in parallel mode for my JUnit tests. There are two different problems: a) While the JUnit tests are running it can't find any of the org.junit classes (e.g. After, Befor, TestCase,...) and complains with a ClassNotFound for them. I think I use the right dependencies in my projects root pom, specified in the dependencyManagement section: dependencyManagement dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId scopetest/scope version4.8.2/version /dependency /dependencies /dependencyManagement The errors looks like this: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:testCompile (default-testCompile) on project qm-server: Compilation failure: Compilation failure: [ERROR] /Daten/projects/qq/server/src/test/java/aaa/bbb/TestXYBean.java:[11,23] package org.junit does not exist [ERROR] /Daten/projects/q/server/src/test/java/aaa/bbb//TestXYConfigBean.java:[15,3] cannot find symbol [ERROR] symbol : class Test ... b) The other problem occures for projects which doesn't have test classes until yet (no JUnit tests in the src folder). But the surefire plugin try to execute this (none existing tests) and this results in the following error: --- T E S T S--- Concurrency config is parallel='none', perCoreThreadCount=true, threadCount=2, useUnlimitedThreads=false java.lang.reflect.UndeclaredThrowableException at $Proxy0.invoke(Unknown Source) at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:145) at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:87) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103) ... 4 more Caused by: java.lang.NoClassDefFoundError: org/junit/runner/notification/RunListener at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClassCond(ClassLoader.java:632) at java.lang.ClassLoader.defineClass(ClassLoader.java:616) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) at java.net.URLClassLoader.defineClass(URLClassLoader.java:283) at java.net.URLClassLoader.access$000(URLClassLoader.java:58) at java.net.URLClassLoader$1.run(URLClassLoader.java:197) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at java.lang.ClassLoader.loadClass(ClassLoader.java:248) at org.apache.maven.surefire.booter.IsolatedClassLoader.loadClass(IsolatedClassLoader.java:93) at org.apache.maven.surefire.junitcore.JUnitCoreProvider.invoke(JUnitCoreProvider.java:97) ... 9 more Caused by: java.lang.ClassNotFoundException: org.junit.runner.notification.RunListener at java.net.URLClassLoader$1.run(URLClassLoader.java:202) at java.security.AccessController.doPrivileged(Native Method) at java.net.URLClassLoader.findClass(URLClassLoader.java:190) at java.lang.ClassLoader.loadClass(ClassLoader.java:307) at java.lang.ClassLoader.loadClass(ClassLoader.java:248) at org.apache.maven.surefire.booter.IsolatedClassLoader.loadClass(IsolatedClassLoader.java:93) [ERROR] Failed to execute goal org.apache.maven.plugins:maven-surefire-plugin:2.7.1:test (default-test) on project xy-server: There are test failures. [ERROR] [ERROR] Please refer to/Daten/projects/xy/server/target/surefire-reports for the individual test results. [ERROR] - [Help 1] This message indicates that a /surefile-reports directory exists, but it doesn't exist because there are no tests. But the surefire plugin created a directory /surefire with some tmp-files. All my projects (also the projects which don't have unit tests until now)
Re: Hibernate 3.6.0 and Maven
Hello Ryan You just need this: dependency groupIdorg.hibernate/groupId artifactIdhibernate-entitymanager/artifactId version3.6.0.Final/version /dependency Johann On Tue, Jan 18, 2011 at 11:25 AM, Ryan Cuprak rcup...@me.com wrote: Does anyone have a working pom file for Hibernate 3.5.x or 3.6.x? This is what I have now: dependency groupIdorg.hibernate/groupId artifactIdhibernate/artifactId version3.5.3-Final/version /dependency dependency groupIdorg.hibernate/groupId artifactIdhibernate-entitymanager/artifactId version3.5.3-Final/version /dependency [ERROR] Failed to execute goal on project ctjava: Could not resolve dependencies for project net.cuprak.web:ctjava:war:1.0-SNAPSHOT: Could not find artifact org.hibernate:hibernate:jar:3.5.3-Final in jboss-public-repository-group ( https://repository.jboss.org/nexus/content/groups/public-jboss/) - [Help 1] I look at the repository and it looks to me like that dependency exists. I am trying to get off of Hibernate 3.2.5. Thanks, -Ryan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Changing the groupId/artifactId of an artifact in the next version but keep maven conflict detection
There should be some support for changing the GA. Getting it right immediately, forever in the beginning is not realistic. But how would you implement this? The only way I can think off the top of my head is a global relocations.xml that is stored in Central and is somehow used to manage these moves. But that gets ugly very quickly. And no one really wants to manage that file. No, I think the current approach is the most sane one. People using Maven for their builds should be expected to know what their dependencies (including transitives) are, and manage these kinds of changes with exclusions etc. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Hibernate 3.6.0 and Maven
version3.5.3-Final/version 3.5.3-Final is really terrible name for a version. [ERROR] Failed to execute goal on project ctjava: Could not resolve dependencies for project net.cuprak.web:ctjava:war:1.0-SNAPSHOT: Could not find artifact org.hibernate:hibernate:jar:3.5.3-Final in jboss-public-repository-group (https://repository.jboss.org/nexus/content/groups/public-jboss/) - [Help 1] Pay special attention to the error -- could not find find artifact ...:jar:... And sure enough, the jar file for this version does not exist in that repo -- they just have a pom and signature files. Look for yourself: https://repository.jboss.org/nexus/content/groups/public-jboss/org/hibernate/hibernate/3.5.3-Final/ That appears to simply be an aggregator pom used for the build. I think you probably want to have a dependency on org.hibernate/hibernate-core or something. That has a jar for version 3.5.3-Final, and a pom with proper dependencies etc. But I'm not an expert on Hibernate so I can't be certain. PS- Probably these questions should be directed to the Hibernate Users list in the future. They ARE experts on Hibernate, and I bet a bunch of them are also using Maven. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Skipping rpm build under windows
-Original Message- From: Wayne Fay [mailto:wayne...@gmail.com] Sent: 17 January 2011 16:49 To: Maven Users List Subject: Re: Skipping rpm build under windows You can use a profile to build your rpm project. This would normally be my response too... but I personally dislike profiles for things if there is another way to handle it. Profiles can make builds more complicated than absolutely necessary. Surely the rpmbuild plugin could be adjusted to check the OS, or check for the existence of the rpmbuild executable or something, and then ignore with a warning (or fail, configurable in the plugin config) if it wasn't found, or something...? This just seems like a common use case and maybe the rpmbuild plugin devs should find a little bit smarter way to handle it. [JN] But then you run the release on a unix box that hasn't had RPMBuild installed and it completes (no one ever checks the warnings right yet there is no rpm!) But it's ok as you can then have a profile to enable the doNotFailIfRPMBuildIsNotFound - but then you don't like profiles and you are back where you started... IIRC the rpm plugin works on windows if you have Cygwin installed and the rpmbuild package for the anti-profile people out there. /James ** This message is confidential and intended only for the addressee. If you have received this message in error, please immediately notify the postmas...@nds.com and delete it from your system as well as any copies. The content of e-mails as well as traffic data may be monitored by NDS for employment and security purposes. To protect the environment please do not print this e-mail unless necessary. NDS Limited. Registered Office: One London Road, Staines, Middlesex, TW18 4EX, United Kingdom. A company registered in England and Wales. Registered no. 3080780. VAT no. GB 603 8808 40-00 **
How to get the configuration properties of a plugin execution without an execution plan
Consider a project with an arbitrary structure of parent that might contain plugins and plugin management. In an M2Eclipse plugin I'm maintain, I am asking the question: Is there an execution of GROUP:ARTIFACT:GOAL, and, if so, what is the contents of the configuration/ element? I currently do this by walking an execution plan. This depends on the plugin being bound to a phase in the lifecycle used to build the execution plan. users have asked me if I can't come up with some other scheme that does not require the lifecycle binding. Is there a way to navigate the plugins of the 'effective pom' to this effect using the API? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Skipping rpm build under windows
[JN] But then you run the release on a unix box that hasn't had RPMBuild installed and it completes (no one ever checks the warnings right yet there is no rpm!) But it's ok as you can then have a profile to enable the doNotFailIfRPMBuildIsNotFound - but then you don't like profiles and you Nah... the configuration would look like: ignoreRpmbuildFailureOses ignoreRpmbuildFailureOswin32/ignoreRpmbuildFailureOs ignoreRpmbuildFailureOsmacosx/ignoreRpmbuildFailureOs /ignoreRpmbuildFailureOses Or the opposite: rpmbuildOses rpmbuildOsunix/rpmbuildOs rpmbuildOslinux/rpmbuildOs rpmbuildOscygwin/rpmbuildOs /rpmbuildOses And the plugin would automatically skip if the OS does not match, like having a skiptrue config that some plugins offer. Just thinking out loud here... feel free to ignore me. ;-) Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Create a common/shared task for the maven-antrun-plugin ?
if one of your modules _is_ the custom ant task (one of the modules is a maven project that codes to ant api and contains the ant task), then you can do this: plugin artifactIdmaven-antrun-plugin/artifactId executions execution ... configuration tasks my.task run special task defined in another module/my.task /tasks /configuration /execution /executions dependencies dependency groupIdmy.groupId/groupId artifactIdmy-ant-task-project/artifactId /dependency /dependencies /plugin the only thing I would wonder about is if the reactor inter-dependency logic can correctly see that the my-ant-task-project needs to be built before its consumers -- View this message in context: http://maven.40175.n5.nabble.com/Create-a-common-shared-task-for-the-maven-antrun-plugin-tp3346449p3346860.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: use of plugin and pluginmanagement
Hi Wayne, Here are my suggestions so far: Descriptions of what the various elements in a pom do (similar to the Ant documentation). Sequence diagrams for maven execution (typical cases) to show how POM elements affect the build. How do phases and goals relate to POM elements? Changes from Maven 2 to Maven 3. Thanks. --- On Sun, 1/16/11, Wayne Fay wayne...@gmail.com wrote: From: Wayne Fay wayne...@gmail.com Subject: Re: use of plugin and pluginmanagement To: Maven Users List users@maven.apache.org Date: Sunday, January 16, 2011, 8:27 PM Maven documentation authors - please study Wayne's concise statement below. That is what we need in the Maven documentation. Not the long-winded, stream-of-consciousness that the existing maven docs currently are. Thanks Dean. I was just recently invited to join Maven dev team and I do plan to make some improvements to the documentation. ;-) It won't happen overnight, but hopefully we can make things easier for everyone. Along those lines... any suggestions you may have would be greatly appreciated!! Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Using release plugin with multi-module project
I'm trying to use the release plugin for the first time on a multi-module project. Given that my project looks like this: /Parent /Project-A /Project-B (had a dependency on Project-A) the problem I'm having is when the release plugin goes to build Project-B it fails with an error saying it can't find Project-A. The release plugin will successfully take the version of Project-A and remove the -SNAPSHOT so that's OK. Also, the release plugin will successfully alter the pom of Project-B and remove the -SNAPSHOT on the dependency to Project-A. However Project-B still can't find Project-A when it the release plugin tries to build it. Suggestions?
Re: Using release plugin with multi-module project
plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId configuration preparationGoalsclean install/preparationGoals /configuration /plugin Search the list for explanation. Kalle On Tue, Jan 18, 2011 at 1:54 PM, Michael Remijan mjremi...@yahoo.com wrote: I'm trying to use the release plugin for the first time on a multi-module project. Given that my project looks like this: /Parent /Project-A /Project-B (had a dependency on Project-A) the problem I'm having is when the release plugin goes to build Project-B it fails with an error saying it can't find Project-A. The release plugin will successfully take the version of Project-A and remove the -SNAPSHOT so that's OK. Also, the release plugin will successfully alter the pom of Project-B and remove the -SNAPSHOT on the dependency to Project-A. However Project-B still can't find Project-A when it the release plugin tries to build it. Suggestions? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Create a common/shared task for the maven-antrun-plugin ?
But I need to use this custom task across different projects. Do you suggest that I create a full separate native maven project where one of the sub modules specifies the custom task and then use this module as a dependency in the other projects? On Tue, Jan 18, 2011 at 10:36 PM, lukewpatterson lukewpatter...@gmail.com wrote: if one of your modules _is_ the custom ant task (one of the modules is a maven project that codes to ant api and contains the ant task), then you can do this: plugin artifactIdmaven-antrun-plugin/artifactId executions execution ... configuration tasks my.task run special task defined in another module/my.task /tasks /configuration /execution /executions dependencies dependency groupIdmy.groupId/groupId artifactIdmy-ant-task-project/artifactId /dependency /dependencies /plugin the only thing I would wonder about is if the reactor inter-dependency logic can correctly see that the my-ant-task-project needs to be built before its consumers -- View this message in context: http://maven.40175.n5.nabble.com/Create-a-common-shared-task-for-the-maven-antrun-plugin-tp3346449p3346860.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: Create a common/shared task for the maven-antrun-plugin ?
morty wrote: ... I need to use this custom task across different projects. Do you suggest that I create a full separate native maven project... If you want to share build logic across different projects, and especially if you code to (via Ant task markup in your case) the custom logic, the logic needs to have coordinates (groupId, artifactId, version) so you can reference it. Yes, the custom plugin/task would be a full-blown Maven project. It would have its own POM, its own coordinates (groupId, artifactId, version), you would install/deploy it just like library/consumer jars. You could make it a Maven plugin (probably the better choice) or an Ant task. If you make it an Ant task, then your consumers would need to route through antrun to use it. From my experience (others may have better ideas), that is really the only way to go in a case like this. If the custom logic codes to you (put gmaven or antrun configuration in a parent pom with a bunch of conditionals to decide what to do), then you can probably get away with not writing a custom plugin. -- View this message in context: http://maven.40175.n5.nabble.com/Create-a-common-shared-task-for-the-maven-antrun-plugin-tp3346449p3346983.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: Create a common/shared task for the maven-antrun-plugin ?
But I need to use this custom task across different projects. Do you suggest that I create a full separate native maven project where one In that case... I like Luke's initial suggestion of turning this into a plugin even more. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: AW: org.codehaus.modello.ModelloCli fails parsing maven.mdo on OpenVMS
Den 18.01.2011 17:16, skrev Stadelmann Josef: Maybe you have another advise for me. From the general smell of it I would suspect this is somehow related to your xml parsers/versions or some kind of inappropriate version mix. I know this is probably not too helpful Kristian - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: surefire classpath problems with maven 3 parallel
Den 18.01.2011 18:03, skrev fmeili: a) The symptoms you are encountering seem to indicate that you're getting testng or junit3 in somewhere on your classpath. As to why this is happening, we'll have to try some detective work: The most significant difference between serial and parallel maven run-mode is that in serial, the entire run-order of the reactor is defined up-front. In parallel, it isn't. Technically parallel mode knows a range of *possible* run-orders that are described by the dependencies in the poms of your individual modules. So from build to build the run-order of your modules can change somewhat. If module number 36 for some reason decides to spend twice as much time as usual, it could change the build order of the remaining build more or less completely (although it'll normally not be *that* bad). So mvn dependency:analyze is your friend here. Especially the used, undeclared dependencies might be able to introduce non-determinisms into your parallel build. A few more questions to ask: - Although it fails intermittently, does it always fail on the same set of modules ? - Does supressing transitive junit3/testng inclusions help ? Surefire stores the fork-configuration for the test run in the target/surefire folder, and if you grep for the correct files you should also be able to compare the values used for a successful/failing run. This would be really valuable. (/me kicks myself in the leg for not making those property files alphabetical for the 100th time. Create an issue if you feel the same ;) b) This may actually be caused by somehow picking up testng/junit3 (ref problem A), especially if you're forcing surefire to use the 4.7 provider. It's probably some behavioural change related to http://jira.codehaus.org/browse/SUREFIRE-663, although I am not entirely sure of what would cause it. Kristian Hi, while migrating to maven 3 (a large multi module project with200 maven projects) I ran into a lot of surefire JUnit problems. The whole project builds correct with maven 3 serial build (without -T option). I've isolated problematic tests and for them I use the surefire configurationforkModealways/forkMode. This solved my System-property based parts of my projects so I'm generally able to build/test in parallel. But I still have some strange ClassNotFound exceptions in parallel mode for my JUnit tests. There are two different problems: a) While the JUnit tests are running it can't find any of the org.junit classes (e.g. After, Befor, TestCase,...) and complains with a ClassNotFound for them. I think I use the right dependencies in my projects root pom, specified in thedependencyManagement section: dependencyManagement dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId scopetest/scope version4.8.2/version /dependency /dependencies /dependencyManagement The errors looks like this: [ERROR] Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:testCompile (default-testCompile) on project qm-server: Compilation failure: Compilation failure: [ERROR] /Daten/projects/qq/server/src/test/java/aaa/bbb/TestXYBean.java:[11,23] package org.junit does not exist [ERROR] /Daten/projects/q/server/src/test/java/aaa/bbb//TestXYConfigBean.java:[15,3] cannot find symbol [ERROR] symbol : class Test ... b) The other problem occures for projects which doesn't have test classes until yet (no JUnit tests in the src folder). But the surefire plugin try to execute this (none existing tests) and this results in the following error: --- T E S T S--- Concurrency config is parallel='none', perCoreThreadCount=true, threadCount=2, useUnlimitedThreads=false java.lang.reflect.UndeclaredThrowableException at $Proxy0.invoke(Unknown Source) at org.apache.maven.surefire.booter.SurefireStarter.invokeProvider(SurefireStarter.java:145) at org.apache.maven.surefire.booter.SurefireStarter.runSuitesInProcess(SurefireStarter.java:87) at org.apache.maven.surefire.booter.ForkedBooter.main(ForkedBooter.java:69) Caused by: java.lang.reflect.InvocationTargetException at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.maven.surefire.booter.ProviderFactory$ClassLoaderProxy.invoke(ProviderFactory.java:103) ... 4 more Caused by: java.lang.NoClassDefFoundError: org/junit/runner/notification/RunListener at java.lang.ClassLoader.defineClass1(Native Method) at java.lang.ClassLoader.defineClassCond(ClassLoader.java:632) at java.lang.ClassLoader.defineClass(ClassLoader.java:616) at java.security.SecureClassLoader.defineClass(SecureClassLoader.java:141) at
