Re: If its' not one thing it's another
Am 04.08.2011 06:53 schrieb Eric Kolotyluk eric.koloty...@gmail.com: OK, I almost had everything working with maven and m2e and nexus, and now it's all broken again. It seems every time I change anything to do with maven configuration, it all falls apart again. It is all unbelievably fragile. I keep trying to do a mvn install on my color-repository module, which depends on intersystem-common. I am able to do an mvn install on intersystem-common, it all succeeds, but fails on color-repository. Last week this was all working fine, until I brought Nexus into the picture. Yesterday it was mostly working with nexus, and now it's all broken again. The diagnostics do not help at all to illuminate what the problem is. Does anyone have any advice (or even just a little sympathy)? Cheers, Eric [ERROR] Failed to execute goal on project color-repository: Could not resolve dependencies for project com.kodak.intersystem.color.repository:color-repository:jar:0.0.1-SNAPSHOT: Failed to collect dependencies for [com.kodak.intersystem:intersystem-common:jar:0.0.1-SNAPSHOT (compile), org.hibernate:hibernate-core:jar:3.6.1.Final (compile), org.eclipse.jetty:example-jetty-embedded:jar:8.0.0.M2 (compile), org.jboss.logging:jboss-logging-log4j:jar:2.1.2.GA (compile), org.slf4j:slf4j-log4j12:jar:1.6.1 (compile), net.jcip:jcip-annotations:jar:1.0 (compile), postgresql:postgresql:jar:9.0-801.jdbc4 (compile), org.javassist:javassist:jar:3.14.0-GA (compile), com.sun.org.apache:jaxp-ri:jar:1.4 (compile), com.miglayout:miglayout:jar:3.7.4 (compile), com.jidesoft:jide-oss:jar:2.4.8 (compile), com.apple:dnssd:jar:2.0.4.0 (compile), org.apache.servicemix.bundles:org.apache.servicemix.bundles.commons-io:jar:1.4_2 (compile), com.threerings:getdown:jar:1.0 (compile), net.sf:jRegistryKey:jar:1.4.5 (compile), jnotify:jnotify:jar:0.93 (compile)]: This looks interesting: Failed to read artifact descriptor for com.kodak.intersystem:intersystem-common:jar:0.0.1-SNAPSHOT: Failure to find com.kodak.intersystem:Kodak-Intersystem:pom:0.0.1-SNAPSHOT in http://nexus:8081/nexus/content/repositories/org.jboss.repositor/ was cached in the local repository, resolution will not be reattempted until the update interval of org.jboss.repository has elapsed or updates are forced - [Help 1] Try command line option -U to force updates. If problem persists, make sure the intersystem pom is actually contained in repository named org.jboss.repository. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: If its' not one thing it's another
This is the JBoss repository, it is very unreliable. If you don't need to resolve dependencies, try building offline. -dirk - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: mvn release is failing with git
release activates some profiles which will result in the active by default
profiles no longer being so
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random nonsense
words and other nonsense are a direct result of using swype to type on the
screen
On 4 Aug 2011 03:10, erwin.muel...@deventm.org wrote:
Hallo,
I have an error in maven release plugin (mvn release:prepare):
[ERROR] The git-push command failed.
[ERROR] Command output:
[ERROR] fatal: The remote end hung up unexpectedly
But I'm sure that the remote repository works just fine. Is there
difficulties with the git protocol? I post my settings.xml and pom.xml:
@- settings.xml
settings
profiles
profile
idRepository Root Locations Local/id
activation
activeByDefaulttrue/activeByDefault
/activation
properties
archiva.repository.roothttp://localhost:8080/archiva
/archiva.repository.root
git.repository.rootgit://localhost/~devent/git.repository.root
/properties
/profile
...
-@
@- pom.xml
scm
connectionscm:git:${git.repository.root}/xmlstorage.git /connection
developerConnectionscm:git:${git.repository.root}/xmlstorage.git
/developerConnection
urlscm:git:scm:git:${git.repository.root}/xmlstorage.git /url
/scm
distributionManagement
repository
idglobalscaling.com-public/id
url${archiva.repository.root}/repository/globalscaling.com-public//url
/repository
snapshotRepository
idglobalscaling.com-public-snapshots/id
url${archiva.repository.root}/repository/globalscaling.com-public-snapshots//url
/snapshotRepository
/distributionManagement
-@
I have them in properties because I like to change them without to touch
the pom.xml. Sometimes I work at home, there I have a good internet
connection, but sometimes I work with my laptop with no/bad connection. So I
setup a git repository and Archiva on localhost.
git pull and git push works, and mvn deploy works, too. mvn scm update
works, too. So I don't understand, if I use the ssh protocol in the URLs,
mvn release works just fine. Is it an issue with the git protocol?
Kind regards, Erwin.
--
Erwin Mueller, erwin.muel...@deventm.org
http://www.global-scaling-institute.de/
http://www.deventm.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: mvn release is failing with git
Erwin,
do you have a log of the git push command which fails? We log it to the console
in case of an error.
Please try to execute this command manually and check if there are any errors
too.
LieGrue,
strub
--- On Thu, 8/4/11, Stephen Connolly stephen.alan.conno...@gmail.com wrote:
From: Stephen Connolly stephen.alan.conno...@gmail.com
Subject: Re: mvn release is failing with git
To: Maven Users List users@maven.apache.org
Date: Thursday, August 4, 2011, 6:43 AM
release activates some profiles which
will result in the active by default
profiles no longer being so
- Stephen
---
Sent from my Android phone, so random spelling mistakes,
random nonsense
words and other nonsense are a direct result of using swype
to type on the
screen
On 4 Aug 2011 03:10, erwin.muel...@deventm.org
wrote:
Hallo,
I have an error in maven release plugin (mvn
release:prepare):
[ERROR] The git-push command failed.
[ERROR] Command output:
[ERROR] fatal: The remote end hung up unexpectedly
But I'm sure that the remote repository works just
fine. Is there
difficulties with the git protocol? I post my settings.xml
and pom.xml:
@- settings.xml
settings
profiles
profile
idRepository Root Locations Local/id
activation
activeByDefaulttrue/activeByDefault
/activation
properties
archiva.repository.roothttp://localhost:8080/archiva
/archiva.repository.root
git.repository.rootgit://localhost/~devent/git.repository.root
/properties
/profile
...
-@
@- pom.xml
scm
connectionscm:git:${git.repository.root}/xmlstorage.git
/connection
developerConnectionscm:git:${git.repository.root}/xmlstorage.git
/developerConnection
urlscm:git:scm:git:${git.repository.root}/xmlstorage.git
/url
/scm
distributionManagement
repository
idglobalscaling.com-public/id
url${archiva.repository.root}/repository/globalscaling.com-public//url
/repository
snapshotRepository
idglobalscaling.com-public-snapshots/id
url${archiva.repository.root}/repository/globalscaling.com-public-snapshots//url
/snapshotRepository
/distributionManagement
-@
I have them in properties because I like to change
them without to touch
the pom.xml. Sometimes I work at home, there I have a good
internet
connection, but sometimes I work with my laptop with no/bad
connection. So I
setup a git repository and Archiva on localhost.
git pull and git push works, and mvn deploy works,
too. mvn scm update
works, too. So I don't understand, if I use the ssh
protocol in the URLs,
mvn release works just fine. Is it an issue with the git
protocol?
Kind regards, Erwin.
--
Erwin Mueller, erwin.muel...@deventm.org
http://www.global-scaling-institute.de/
http://www.deventm.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
[ANN] Selenium Maven Plugin 2.0 Released
Hi, The Mojo team is pleased to announce the release of the Selenium Maven Plugin version 2.0. Site : http://mojo.codehaus.org/selenium-maven-plugin/ To get this update, simply specify the version in your project's plugin configuration: plugin groupIdorg.codehaus.mojo/groupId artifactIdselenium-maven-plugin/artifactId version2.0/version /plugin Release Notes - Maven 2.x Selenium Plugin - Version 2.0 ** Bug * [MSELENIUM-63] - Add support for passing in system properties when starting the selenium server. ** New Feature * [MSELENIUM-70] - upgrade to selenium server 2.2.0 Have Fun, -- The Mojo team. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Execution of plugin in child poms and not in current pom
Hello, i try to create a company parent pom that defines the usage of the enforcer plugin with some handmade enforcer rules. This rules validates the project settings for all our applications we build with maven. My problem is that the enforcer plugin (and the defined rules) are called in the run of the company parent pom build and fail the build because he use the rules that should only be used in application projects. Do anyone know how if i can fix this? The enforcer plugin should only called in all projects based on company parent pom as parent. Thanks. Conny - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Packaging binaries
Hi, What is the best way to package precompiled binaries in Maven Central? I've cross-posted this question (with more information) to http://stackoverflow.com/questions/6942721/packaging-precompiled-binaries-for-maven Thank you, Gili -- View this message in context: http://maven.40175.n5.nabble.com/Packaging-binaries-tp4666401p4666401.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
Filtering using properties in jar?
I have some properties I'd like to use in multiple projects for filtering, how can I specify that the xxx.properties file I want to use is in a jar? Typically I do the following when filtering but that assumes I have that file locally, how can I do this if the file is in a jar/zip? I know I could unpack the jar locally but I'm hoping there is a more elegant solution. filters filter [a filter property file] /filter /filters -Dave - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [ANN] Selenium Maven Plugin 2.0 Released
Hi, just saw that the link to Selenium Java Client Driver on the index.html page is not correct... Thanks for that good work... Kind regards Karl Heinz Marbaise - Kind regards Karl Heinz Marbaise http://www.soebes.de http://www.skmwiki.de http://supose.org/wiki/supose -- View this message in context: http://maven.40175.n5.nabble.com/ANN-Selenium-Maven-Plugin-2-0-Released-tp4666252p4666493.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: Filtering using properties in jar?
Hello, Remote Resources Plugin [1] will be probably your friend HTH, -- Olivier Lamy Talend : http://talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy [1] http://maven.apache.org/plugins/maven-remote-resources-plugin/ 2011/8/4 David Hoffer dhoff...@gmail.com: I have some properties I'd like to use in multiple projects for filtering, how can I specify that the xxx.properties file I want to use is in a jar? Typically I do the following when filtering but that assumes I have that file locally, how can I do this if the file is in a jar/zip? I know I could unpack the jar locally but I'm hoping there is a more elegant solution. filters filter [a filter property file] /filter /filters -Dave - 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
Custom lifecycle using Maven plugin
Hello everyone, I'd like to accomplish defining a custom lifecycle for my plugin that invokes a set of goals (including some goals implemented by a Mojo in the plugin) in a custom lifecycle phase. Unfortunately, my progress implementing this is still somewhat limited. ;-) I have a META-INF/maven/lifecycles.xml: -- 8 -- lifecycles lifecycle idhsqldb/id phases phase idhsql-start/id executions execution goals goalhsql-start/goal /goals /execution /executions /phase /phases /lifecycle /lifecycles -- 8 -- and a META-INF/plexus/components.xml: -- 8 -- component-set components component roleorg.apache.maven.lifecycle.mapping.LifecycleMapping/role role-hinthsql-start/role-hint implementationorg.apache.maven.lifecycle.mapping.DefaultLifecycleMapping/implementation configuration phases hsql-startcom.example.plugins:maven-example-hsqldb-plugin:hsql-start/hsql-start /phases /configuration /component /components /component-set -- 8 -- What is currently not clear to me: How do I reference this lifecycle from my project's pom so that I can ideally invoke it using mvn hsql-start Any hints (including documentation pointers that I may have missed so far) are much appreciated! Thanks, Thilo - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: If its' not one thing it's another
The intersystem pom is not supposed to be in org.jboss.repository. I do not know why it expects to find it there. Cheers, Eric On Wed, Aug 3, 2011 at 11:03 PM, Ansgar Konermann ansgar.konerm...@googlemail.com wrote: Am 04.08.2011 06:53 schrieb Eric Kolotyluk eric.koloty...@gmail.com: OK, I almost had everything working with maven and m2e and nexus, and now it's all broken again. It seems every time I change anything to do with maven configuration, it all falls apart again. It is all unbelievably fragile. I keep trying to do a mvn install on my color-repository module, which depends on intersystem-common. I am able to do an mvn install on intersystem-common, it all succeeds, but fails on color-repository. Last week this was all working fine, until I brought Nexus into the picture. Yesterday it was mostly working with nexus, and now it's all broken again. The diagnostics do not help at all to illuminate what the problem is. Does anyone have any advice (or even just a little sympathy)? Cheers, Eric [ERROR] Failed to execute goal on project color-repository: Could not resolve dependencies for project com.kodak.intersystem.color.repository:color-repository:jar:0.0.1-SNAPSHOT: Failed to collect dependencies for [com.kodak.intersystem:intersystem-common:jar:0.0.1-SNAPSHOT (compile), org.hibernate:hibernate-core:jar:3.6.1.Final (compile), org.eclipse.jetty:example-jetty-embedded:jar:8.0.0.M2 (compile), org.jboss.logging:jboss-logging-log4j:jar:2.1.2.GA (compile), org.slf4j:slf4j-log4j12:jar:1.6.1 (compile), net.jcip:jcip-annotations:jar:1.0 (compile), postgresql:postgresql:jar:9.0-801.jdbc4 (compile), org.javassist:javassist:jar:3.14.0-GA (compile), com.sun.org.apache:jaxp-ri:jar:1.4 (compile), com.miglayout:miglayout:jar:3.7.4 (compile), com.jidesoft:jide-oss:jar:2.4.8 (compile), com.apple:dnssd:jar:2.0.4.0 (compile), org.apache.servicemix.bundles:org.apache.servicemix.bundles.commons-io:jar:1.4_2 (compile), com.threerings:getdown:jar:1.0 (compile), net.sf:jRegistryKey:jar:1.4.5 (compile), jnotify:jnotify:jar:0.93 (compile)]: This looks interesting: Failed to read artifact descriptor for com.kodak.intersystem:intersystem-common:jar:0.0.1-SNAPSHOT: Failure to find com.kodak.intersystem:Kodak-Intersystem:pom:0.0.1-SNAPSHOT in http://nexus:8081/nexus/content/repositories/org.jboss.repositor/ was cached in the local repository, resolution will not be reattempted until the update interval of org.jboss.repository has elapsed or updates are forced - [Help 1] Try command line option -U to force updates. If problem persists, make sure the intersystem pom is actually contained in repository named org.jboss.repository. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: If its' not one thing it's another
When I set up Nexus I set it up to mirror the JBoss repository. It synced up with JBoss last week and everything was working fine. Isn't the idea of having a central repository manager like Nexus that you are isolated against problems with the real repositories? Cheers, Eric On Wed, Aug 3, 2011 at 11:07 PM, d...@xanthippe.ping.de d...@xanthippe.ping.de wrote: This is the JBoss repository, it is very unreliable. If you don't need to resolve dependencies, try building offline. -dirk - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
What does this mean?
I keep seeing the following almost every time something fails, but I have no idea what it means, or how to resolve it. ...was cached in the local repository, resolution will not be reattempted until the update interval of info.collide.mvn has elapsed or updates are forced Could someone please explain what this means and what I have to do to stop it from happening. I'm tired of seeing it all the time. Cheers, Eric [ERROR] Failed to execute goal on project color-repository: Could not resolve dependencies for project com.kodak.intersystem:color-repository:jar:0.0.1-SNAPSHOT: Failed to collect dependencies for [com.kodak.intersystem:intersystem-common:jar:0.0.1-SNAPSHOT (compile), org.hibernate:hibernate-core:jar:3.6.1.Final (compile), org.eclipse.jetty:example-jetty-embedded:jar:8.0.0.M2 (compile), org.jboss.logging:jboss-logging-log4j:jar:2.1.2.GA (compile), org.slf4j:slf4j-log4j12:jar:1.6.1 (compile), net.jcip:jcip-annotations:jar:1.0 (compile), postgresql:postgresql:jar:9.0-801.jdbc4 (compile), org.javassist:javassist:jar:3.14.0-GA (compile), com.sun.org.apache:jaxp-ri:jar:1.4 (compile), com.miglayout:miglayout:jar:3.7.4 (compile), com.jidesoft:jide-oss:jar:2.4.8 (compile), com.apple:dnssd:jar:2.0.4.0 (compile), org.apache.servicemix.bundles:org.apache.servicemix.bundles.commons-io:jar:1.4_2 (compile), com.threerings:getdown:jar:1.0 (compile), net.sf:jRegistryKey:jar:1.4.5 (compile), jnotify:jnotify:jar:0.93 (compile)]: Failed to read artifact descriptor for com.kodak.intersystem:intersystem-common:jar:0.0.1-SNAPSHOT: Failure to find com.kodak.intersystem:Kodak-Intersystem:pom:0.0.1-SNAPSHOT in http://nexus:8081/nexus/content/repositories/info.collide.mvn/ was cached in the local repository, resolution will not be reattempted until the update interval of info.collide.mvn has elapsed or updates are forced - [Help 1]
Re: What does this mean?
Hello, The logs says : Failure to find com.kodak.intersystem:Kodak-Intersystem:pom:0.0.1-SNAPSHOT in http://nexus:8081/nexus/content/repositories/info.collide.mvn/ was cached in the local repository, resolution will not be reattempted until the update interval of info.collide.mvn has elapsed or updates are forced So try again mvn with adding -U. if doesn't work ensure this artifact is available in this repository. -- Olivier Lamy Talend : http://talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy 2011/8/4 Eric Kolotyluk eric.koloty...@gmail.com: I keep seeing the following almost every time something fails, but I have no idea what it means, or how to resolve it. ...was cached in the local repository, resolution will not be reattempted until the update interval of info.collide.mvn has elapsed or updates are forced Could someone please explain what this means and what I have to do to stop it from happening. I'm tired of seeing it all the time. Cheers, Eric [ERROR] Failed to execute goal on project color-repository: Could not resolve dependencies for project com.kodak.intersystem:color-repository:jar:0.0.1-SNAPSHOT: Failed to collect dependencies for [com.kodak.intersystem:intersystem-common:jar:0.0.1-SNAPSHOT (compile), org.hibernate:hibernate-core:jar:3.6.1.Final (compile), org.eclipse.jetty:example-jetty-embedded:jar:8.0.0.M2 (compile), org.jboss.logging:jboss-logging-log4j:jar:2.1.2.GA (compile), org.slf4j:slf4j-log4j12:jar:1.6.1 (compile), net.jcip:jcip-annotations:jar:1.0 (compile), postgresql:postgresql:jar:9.0-801.jdbc4 (compile), org.javassist:javassist:jar:3.14.0-GA (compile), com.sun.org.apache:jaxp-ri:jar:1.4 (compile), com.miglayout:miglayout:jar:3.7.4 (compile), com.jidesoft:jide-oss:jar:2.4.8 (compile), com.apple:dnssd:jar:2.0.4.0 (compile), org.apache.servicemix.bundles:org.apache.servicemix.bundles.commons-io:jar:1.4_2 (compile), com.threerings:getdown:jar:1.0 (compile), net.sf:jRegistryKey:jar:1.4.5 (compile), jnotify:jnotify:jar:0.93 (compile)]: Failed to read artifact descriptor for com.kodak.intersystem:intersystem-common:jar:0.0.1-SNAPSHOT: Failure to find com.kodak.intersystem:Kodak-Intersystem:pom:0.0.1-SNAPSHOT in http://nexus:8081/nexus/content/repositories/info.collide.mvn/ was cached in the local repository, resolution will not be reattempted until the update interval of info.collide.mvn has elapsed or updates are forced - [Help 1] - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: If its' not one thing it's another
It appears like you aren't using groups in Nexus. Your maven shouldn't be telling you it's looking in the jboss repo, it should be looking in your nexus group and nexus deals with the other repos. You would normally do this in your settings with a mirrorOf * - nexus/content/groups/public for example On Thu, Aug 4, 2011 at 11:32 AM, Eric Kolotyluk eric.koloty...@gmail.com wrote: When I set up Nexus I set it up to mirror the JBoss repository. It synced up with JBoss last week and everything was working fine. Isn't the idea of having a central repository manager like Nexus that you are isolated against problems with the real repositories? Cheers, Eric On Wed, Aug 3, 2011 at 11:07 PM, d...@xanthippe.ping.de d...@xanthippe.ping.de wrote: This is the JBoss repository, it is very unreliable. If you don't need to resolve dependencies, try building offline. -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: What does this mean?
-U does nothing, I have tried that over a dozen times now. com.kodak.intersystem:Kodak-Intersystem:pom:0.0.1-SNAPSHOT is not supposed to be in the nexus repository, it is supposed to be in the local repository What I want to know is what resolution will not be reattempted until the update interval of info.collide.mvn has elapsed or updates are forced means. I see it all the time, it always causes problems, but the message is meaningless to me. How do I make it stop happening? When I run from the command line I get: [ERROR] Failed to execute goal on project color-repository: Could not resolve dependencies for project com.kodak.intersystem:color-repository:jar:0.0.1-SNAPSHOT: Failed to collect dependencies for [com.kodak.intersystem:intersystem-common:jar:0.0.1-SNAPSHOT (compile), org.hibernate:hibernate-core:jar:3.6.1.Final (compile), org.eclipse.jetty:example-jetty-embedded:jar:8.0.0.M2 (compile), org.slf4j:slf4j-log4j12:jar:1.6.1 (compile), net.jcip:jcip-annotations:jar:1.0 (compile), postgresql:postgresql:jar:9.0-801.jdbc4 (compile), org.javassist:javassist:jar:3.14.0-GA (compile), com.sun.org.apache:jaxp-ri:jar:1.4 (compile), com.miglayout:miglayout:jar:3.7.4 (compile), com.jidesoft:jide-oss:jar:2.4.8 (compile), com.apple:dnssd:jar:2.0.4.0 (compile), org.apache.servicemix.bundles:org.apache.servicemix.bundles.commons-io:jar:1.4_2 (compile), com.threerings:getdown:jar:1.0 (compile), net.sf:jRegistryKey:jar:1.4.5 (compile), jnotify:jnotify:jar:0.93 (compile), ant:ant-apache-log4j:jar:1.6.5 (compile)]: Failed to read artifact descriptor for com.kodak.intersystem:intersystem-common:jar:0.0.1-SNAPSHOT: Could not find artifact com.kodak.intersystem:Kodak-Intersystem:pom:0.0.1-SNAPSHOT in nexus ( http://nexus:8081/nexus/content/groups/public) - [Help 1] So, the resolution will not be reattempted until the update interval of info.collide.mvn has elapsed or updates are forced seems to be something that is upsetting m2e. There seems to be a catch 22 situation. I cannot install Kodak-Intersystem because it fails to build because intersystem-service fails to build because color-repository fails to build. So, color-repository fails to build because color-repository fails to build. Is there any way to break the cycle? Cheers, Eric On Thu, Aug 4, 2011 at 9:54 AM, Olivier Lamy ol...@apache.org wrote: Hello, The logs says : Failure to find com.kodak.intersystem:Kodak-Intersystem:pom:0.0.1-SNAPSHOT in http://nexus:8081/nexus/content/repositories/info.collide.mvn/ was cached in the local repository, resolution will not be reattempted until the update interval of info.collide.mvn has elapsed or updates are forced So try again mvn with adding -U. if doesn't work ensure this artifact is available in this repository. -- Olivier Lamy Talend : http://talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy 2011/8/4 Eric Kolotyluk eric.koloty...@gmail.com: I keep seeing the following almost every time something fails, but I have no idea what it means, or how to resolve it. ...was cached in the local repository, resolution will not be reattempted until the update interval of info.collide.mvn has elapsed or updates are forced Could someone please explain what this means and what I have to do to stop it from happening. I'm tired of seeing it all the time. Cheers, Eric [ERROR] Failed to execute goal on project color-repository: Could not resolve dependencies for project com.kodak.intersystem:color-repository:jar:0.0.1-SNAPSHOT: Failed to collect dependencies for [com.kodak.intersystem:intersystem-common:jar:0.0.1-SNAPSHOT (compile), org.hibernate:hibernate-core:jar:3.6.1.Final (compile), org.eclipse.jetty:example-jetty-embedded:jar:8.0.0.M2 (compile), org.jboss.logging:jboss-logging-log4j:jar:2.1.2.GA (compile), org.slf4j:slf4j-log4j12:jar:1.6.1 (compile), net.jcip:jcip-annotations:jar:1.0 (compile), postgresql:postgresql:jar:9.0-801.jdbc4 (compile), org.javassist:javassist:jar:3.14.0-GA (compile), com.sun.org.apache:jaxp-ri:jar:1.4 (compile), com.miglayout:miglayout:jar:3.7.4 (compile), com.jidesoft:jide-oss:jar:2.4.8 (compile), com.apple:dnssd:jar:2.0.4.0 (compile), org.apache.servicemix.bundles:org.apache.servicemix.bundles.commons-io:jar:1.4_2 (compile), com.threerings:getdown:jar:1.0 (compile), net.sf:jRegistryKey:jar:1.4.5 (compile), jnotify:jnotify:jar:0.93 (compile)]: Failed to read artifact descriptor for com.kodak.intersystem:intersystem-common:jar:0.0.1-SNAPSHOT: Failure to find com.kodak.intersystem:Kodak-Intersystem:pom:0.0.1-SNAPSHOT in http://nexus:8081/nexus/content/repositories/info.collide.mvn/ was cached in the local repository, resolution will not be reattempted until the update interval of info.collide.mvn has elapsed or updates are forced - [Help 1]
Re: Automatic Update of Build Plugin Versions?
On 29 July 2011 22:02, Wayne Fay wayne...@gmail.com wrote:
When I decide I want the new version of a plugin I want to update all
projects
at once instead of having to open each pom and change it by hand. From
your response I am guessing it is expected to use properties to control
this.
Or use pluginManagement in a shared parent...
Definitely, the shared parent is your friend if you want manage plugin
versions in one central place. The shared parent is often called
corporate pom. Define all plugins in the pluginManagement section in
the corporate pom. You can also specify plugin versions as properties,
then you can easily overwrite version in the specific project:
properties
acme-corporate-pom.cleanVersion2.4.1/acme-corporate-pom.cleanVersion
/properties
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-clean-plugin/artifactId
version${acme-corporate-pom.cleanVersion}/version
/plugin
The same concept can be used to customize plugins configuration (can
be easily overwritten):
properties
!-- Automatically assign submodules the parent version (m-release-p) --
autoVersionSubmodulestrue/autoVersionSubmodules
/properties
--
Marcin Kuthan
Maven For Enterprise - http://code.google.com/p/m4enterprise/
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: Execution of plugin in child poms and not in current pom
Hi Conny Define enforcer rules in the profile, e.g: profile idenforcer-rules/id activation !-- To disable profile, define property -Dacme-corporate-pom.enforcerRulesDisabled=true -- property name!acme-corporate-pom.enforcerRulesDisabled/name /property /activation ... /profile When you build corporate pom, disable the profile with: mvn -Dacme-corporate-pom.enforcerRulesDisabled=true For all other projects the profile is enabled by default. -- Marcin Kuthan Maven For Enterprise - http://code.google.com/p/m4enterprise/ On 4 August 2011 15:47, Kreyßel, Conny conny.kreys...@inter-forum.de wrote: Hello, i try to create a company parent pom that defines the usage of the enforcer plugin with some handmade enforcer rules. This rules validates the project settings for all our applications we build with maven. My problem is that the enforcer plugin (and the defined rules) are called in the run of the company parent pom build and fail the build because he use the rules that should only be used in application projects. Do anyone know how if i can fix this? The enforcer plugin should only called in all projects based on company parent pom as parent. Thanks. Conny - 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: Execution of plugin in child poms and not in current pom
you could place the enforcer plugin definition in pluginManagement section of the parent pom and then in each of the child poms you want to execute the plugin, you would include it in the plugins section Milos On Thu, Aug 4, 2011 at 3:47 PM, Kreyßel, Conny conny.kreys...@inter-forum.de wrote: Hello, i try to create a company parent pom that defines the usage of the enforcer plugin with some handmade enforcer rules. This rules validates the project settings for all our applications we build with maven. My problem is that the enforcer plugin (and the defined rules) are called in the run of the company parent pom build and fail the build because he use the rules that should only be used in application projects. Do anyone know how if i can fix this? The enforcer plugin should only called in all projects based on company parent pom as parent. Thanks. Conny - 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: Should I use classifiers to differentiate between devel and production builds?
You are right, not everything could be configured in JNDI. The logger
is a good example. For web application packaged as WAR, you can define
separate project module, and apply the overlay with logger
configuration.
!-- Customize artifact before deployment --
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
configuration
overlays
overlay
groupId${project.groupId}/groupId
artifactIdmodular-war-webapp/artifactId
/overlay
/overlays
/configuration
/plugin
For more complete example, please look into
http://code.google.com/p/m4enterprise/source/browse/trunk/modular-war/modular-war-deploy/pom.xml
Not ideal, but much better than profiles in the web application
module. The deployment specific configuration is located in separate
deploy module.
--
Marcin Kuthan
Maven For Enterprise - http://code.google.com/p/m4enterprise/
On 27 July 2011 15:43, Daniel Serodio (lists) daniel.lis...@xxx.com.br wrote:
Ansgar Konermann wrote:
Am 25.07.2011 22:13, schrieb Daniel Serodio (lists):
Do you think using a classifier to differentiate artifacts built for
development and production is hacky, is is this an appropriate
solution?
Use the same *artifacts* for all stages and allow for *configuring* the
relevant properties of your application at runtime/startup time, as much
as possible.
A common mechanism to configure things at runtime is using JNDI
parameters.
I'mconsidering changing our build process. Setting up the DB using JNDI is
easy enough, but how do you suggest we deal with different logging
configurations, which differ not only on some values, but structure (ie
log4j Loggers and Appenders with different classes, file paths and severity
thresholds) ?
Regards,
Daniel Serodio
-
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: What does this mean?
OK, some progress. I was able to break the cycle... Kodak-Intersystem (the parent project) was failing on javadoc running during package, so I changed it to run during deploy. Once Kodak Intersystem was able to install, then color-repository was able to install, then intersystem-service was able to install. So I guess this was basically a life cycle problem - does that make sense? Cheers, Eric On Thu, Aug 4, 2011 at 10:44 AM, Eric Kolotyluk eric.koloty...@gmail.comwrote: -U does nothing, I have tried that over a dozen times now. com.kodak.intersystem:Kodak-Intersystem:pom:0.0.1-SNAPSHOT is not supposed to be in the nexus repository, it is supposed to be in the local repository What I want to know is what resolution will not be reattempted until the update interval of info.collide.mvn has elapsed or updates are forced means. I see it all the time, it always causes problems, but the message is meaningless to me. How do I make it stop happening? When I run from the command line I get: [ERROR] Failed to execute goal on project color-repository: Could not resolve dependencies for project com.kodak.intersystem:color-repository:jar:0.0.1-SNAPSHOT: Failed to collect dependencies for [com.kodak.intersystem:intersystem-common:jar:0.0.1-SNAPSHOT (compile), org.hibernate:hibernate-core:jar:3.6.1.Final (compile), org.eclipse.jetty:example-jetty-embedded:jar:8.0.0.M2 (compile), org.slf4j:slf4j-log4j12:jar:1.6.1 (compile), net.jcip:jcip-annotations:jar:1.0 (compile), postgresql:postgresql:jar:9.0-801.jdbc4 (compile), org.javassist:javassist:jar:3.14.0-GA (compile), com.sun.org.apache:jaxp-ri:jar:1.4 (compile), com.miglayout:miglayout:jar:3.7.4 (compile), com.jidesoft:jide-oss:jar:2.4.8 (compile), com.apple:dnssd:jar:2.0.4.0 (compile), org.apache.servicemix.bundles:org.apache.servicemix.bundles.commons-io:jar:1.4_2 (compile), com.threerings:getdown:jar:1.0 (compile), net.sf:jRegistryKey:jar:1.4.5 (compile), jnotify:jnotify:jar:0.93 (compile), ant:ant-apache-log4j:jar:1.6.5 (compile)]: Failed to read artifact descriptor for com.kodak.intersystem:intersystem-common:jar:0.0.1-SNAPSHOT: Could not find artifact com.kodak.intersystem:Kodak-Intersystem:pom:0.0.1-SNAPSHOT in nexus ( http://nexus:8081/nexus/content/groups/public) - [Help 1] So, the resolution will not be reattempted until the update interval of info.collide.mvn has elapsed or updates are forced seems to be something that is upsetting m2e. There seems to be a catch 22 situation. I cannot install Kodak-Intersystem because it fails to build because intersystem-service fails to build because color-repository fails to build. So, color-repository fails to build because color-repository fails to build. Is there any way to break the cycle? Cheers, Eric On Thu, Aug 4, 2011 at 9:54 AM, Olivier Lamy ol...@apache.org wrote: Hello, The logs says : Failure to find com.kodak.intersystem:Kodak-Intersystem:pom:0.0.1-SNAPSHOT in http://nexus:8081/nexus/content/repositories/info.collide.mvn/ was cached in the local repository, resolution will not be reattempted until the update interval of info.collide.mvn has elapsed or updates are forced So try again mvn with adding -U. if doesn't work ensure this artifact is available in this repository. -- Olivier Lamy Talend : http://talend.com http://twitter.com/olamy | http://linkedin.com/in/olamy 2011/8/4 Eric Kolotyluk eric.koloty...@gmail.com: I keep seeing the following almost every time something fails, but I have no idea what it means, or how to resolve it. ...was cached in the local repository, resolution will not be reattempted until the update interval of info.collide.mvn has elapsed or updates are forced Could someone please explain what this means and what I have to do to stop it from happening. I'm tired of seeing it all the time. Cheers, Eric [ERROR] Failed to execute goal on project color-repository: Could not resolve dependencies for project com.kodak.intersystem:color-repository:jar:0.0.1-SNAPSHOT: Failed to collect dependencies for [com.kodak.intersystem:intersystem-common:jar:0.0.1-SNAPSHOT (compile), org.hibernate:hibernate-core:jar:3.6.1.Final (compile), org.eclipse.jetty:example-jetty-embedded:jar:8.0.0.M2 (compile), org.jboss.logging:jboss-logging-log4j:jar:2.1.2.GA (compile), org.slf4j:slf4j-log4j12:jar:1.6.1 (compile), net.jcip:jcip-annotations:jar:1.0 (compile), postgresql:postgresql:jar:9.0-801.jdbc4 (compile), org.javassist:javassist:jar:3.14.0-GA (compile), com.sun.org.apache:jaxp-ri:jar:1.4 (compile), com.miglayout:miglayout:jar:3.7.4 (compile), com.jidesoft:jide-oss:jar:2.4.8 (compile), com.apple:dnssd:jar:2.0.4.0 (compile), org.apache.servicemix.bundles:org.apache.servicemix.bundles.commons-io:jar:1.4_2 (compile), com.threerings:getdown:jar:1.0 (compile), net.sf:jRegistryKey:jar:1.4.5 (compile), jnotify:jnotify:jar:0.93 (compile)]: Failed to read artifact descriptor for
Re: If its' not one thing it's another
OK, things seem to have been sorted out now. It seems the underlying problem was my parent pom Kodak-Intersystem was failing to to generate javadoc in the package phase, this was failing because intersystem-service was failing in build, which was failing because color-repository was failing in build and had not been installed, which was failing because Kodak-Intersystem had not been installed - so I had a cycle of dependencies Changing Kodak-Intersystem to generate javadoc in the deploy phase broke the cycle by allowing Kodak-Intersystem to be installed, and all the other dependencies to be resolved. For the most part the diagnostics were not at all useful in helping, I had to reason through all the mechanics of what was going on. The behavior of Nexus and m2e, while annoying and distracting, were not the direct cause. Nexus was an indirect cause because I was reorganizing things, which finally caused the dependency/life-cycle circle to manifest. Cheers, Eric On Thu, Aug 4, 2011 at 10:31 AM, Brian Fox bri...@infinity.nu wrote: It appears like you aren't using groups in Nexus. Your maven shouldn't be telling you it's looking in the jboss repo, it should be looking in your nexus group and nexus deals with the other repos. You would normally do this in your settings with a mirrorOf * - nexus/content/groups/public for example On Thu, Aug 4, 2011 at 11:32 AM, Eric Kolotyluk eric.koloty...@gmail.com wrote: When I set up Nexus I set it up to mirror the JBoss repository. It synced up with JBoss last week and everything was working fine. Isn't the idea of having a central repository manager like Nexus that you are isolated against problems with the real repositories? Cheers, Eric On Wed, Aug 3, 2011 at 11:07 PM, d...@xanthippe.ping.de d...@xanthippe.ping.de wrote: This is the JBoss repository, it is very unreliable. If you don't need to resolve dependencies, try building offline. -dirk - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How can a plugin become aware of its environment (e.g. properties)?
First: if I'm writing a plugin for my own use, am I a user or a developer? I'm not developing Maven itself and the Developer Centre page admits of nothing in between. Back to topic: I'm writing a plugin that needs access to the project's properties. Nothing environmental is passed to a mojo, and fishing through the Javadocs for static methods that look promising has turned up nothing so far. What *should* I be reading? Lots of other questions about plugin development, that the Plugin Developer Centre doesn't address -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Asking whether markets are efficient is like asking whether people are smart. pgp1h9RflW4e2.pgp Description: PGP signature
Re: [nexus-user] What does this mean?
On 04/08/2011 12:42 PM, Eric Kolotyluk wrote: Failure to find com.kodak.intersystem:Kodak-Intersystem:pom:0.0.1-SNAPSHOT This is pretty clear. It does not exist. Do you see it in your repo? Does a POM exist or is it supposed to be a JAR. com.kodak.intersystem:Kodak-Intersystem:jar:0.0.1-SNAPSHOT - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How to force eager resolution of inherited properties?
Hi,
in one of my parent poms, i have a property like this:
repository.integrationtests${project.basedir}/../../target/it-repository/repository.integrationtests
This property is then inherited to various child modules which live at
different depths in the inheritance tree.
As far as I understand the maven property inheritance mechanism,
${project.basedir} gets inherited as a *variable* and resolved in the
context of each child project referencing this variable. As the child
projects live at different levels of the inheritance tree, they will
also use it-repository directories at different levels of the tree, so
there are multiple repo directories, and none contains all the required
artifacts :-(
I'd like to *prevent* this context-dependent resolution behaviour and
tell all my child projects, wherever they might live in the tree, where
to find *the one* repository which should be used for integration
testing (a plugin, that is).
How could I achieve this?
Thanks in advance
Ansgar
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: [nexus-user] What does this mean?
Yes, Kodak-Intersystem is a POM, the parent of all my JAR modules. I don't know why it was looking for a jar, there is no jar. Cheers, Eric On Thu, Aug 4, 2011 at 1:10 PM, Ron Wheeler rwhee...@artifact-software.comwrote: On 04/08/2011 12:42 PM, Eric Kolotyluk wrote: Failure to find com.kodak.intersystem:Kodak-** Intersystem:pom:0.0.1-SNAPSHOT This is pretty clear. It does not exist. Do you see it in your repo? Does a POM exist or is it supposed to be a JAR. com.kodak.intersystem:Kodak-**Intersystem:jar:0.0.1-SNAPSHOT --**--**- To unsubscribe, e-mail: nexus-user-unsubscribe@**sonatype.orgnexus-user-unsubscr...@sonatype.org For additional commands, e-mail: nexus-user-h...@sonatype.org
Re: cargo tomcat configurations in settings.xml
Hi there, I have the same problem and followed this thread, however the solution ist not working for me. I have added the caro line in my settings.xml and copied it also to my users .m2 directory (though before a mvn help:effective-settings showed that the line was already active). My result ist still; No plugin found for prefix 'cargo'. I'm a bit clueless. Any ideas? Cheers Stefan C:\Users\Stefan\.m2mvn cargo:help [INFO] Scanning for projects... Downloading: http://repo1.maven.org/maven2/org/codehaus/mojo/maven-metadata.xml Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-metada ta.xml Downloading: http://repo1.maven.org/maven2/org/codehaus/cargo/maven-metadata.xml Downloaded: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-metadat a.xml (11 KB at 10.1 KB/sec) Downloaded: http://repo1.maven.org/maven2/org/codehaus/mojo/maven-metadata.xml ( 18 KB at 13.7 KB/sec) Downloaded: http://repo1.maven.org/maven2/org/codehaus/cargo/maven-metadata.xml (703 B at 0.5 KB/sec) [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 2.043s [INFO] Finished at: Thu Aug 04 23:11:04 CEST 2011 [INFO] Final Memory: 3M/90M [INFO] [ERROR] No plugin found for prefix 'cargo' in the current project and in the plu gin groups [org.codehaus.cargo, org.apache.maven.plugins, org.codehaus.mojo] ava ilable from the repositories [local (d:\dev\maven-3.0.3\repository), central (ht tp://repo1.maven.org/maven2)] - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit ch. [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 rea d the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/NoPluginFoundF orPrefixException C:\Users\Stefan\.m2 -- View this message in context: http://maven-users.828.n2.nabble.com/cargo-tomcat-configurations-in-settings-xml-tp6338184p6654300.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 3 and cargo plugin
Hi there, I have the same problem and followed this thread, however the solution ist not working for me. My result ist still; No plugin found for prefix 'cargo'. I'm a bit clueless. Have you solved your problem in between? Cheers Stefan C:\Users\Stefan\.m2mvn cargo:help [INFO] Scanning for projects... Downloading: http://repo1.maven.org/maven2/org/codehaus/mojo/maven-metadata.xml Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-metada ta.xml Downloading: http://repo1.maven.org/maven2/org/codehaus/cargo/maven-metadata.xml Downloaded: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-metadat a.xml (11 KB at 10.1 KB/sec) Downloaded: http://repo1.maven.org/maven2/org/codehaus/mojo/maven-metadata.xml ( 18 KB at 13.7 KB/sec) Downloaded: http://repo1.maven.org/maven2/org/codehaus/cargo/maven-metadata.xml (703 B at 0.5 KB/sec) [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Total time: 2.043s [INFO] Finished at: Thu Aug 04 23:11:04 CEST 2011 [INFO] Final Memory: 3M/90M [INFO] [ERROR] No plugin found for prefix 'cargo' in the current project and in the plu gin groups [org.codehaus.cargo, org.apache.maven.plugins, org.codehaus.mojo] ava ilable from the repositories [local (d:\dev\maven-3.0.3\repository), central (ht tp://repo1.maven.org/maven2)] - [Help 1] [ERROR] [ERROR] To see the full stack trace of the errors, re-run Maven with the -e swit ch. [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 rea d the following articles: [ERROR] [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/NoPluginFoundF orPrefixException C:\Users\Stefan\.m2 -- View this message in context: http://maven-users.828.n2.nabble.com/Maven-3-and-cargo-plugin-tp6007841p6654316.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 3 and cargo plugin
Hm I think i have found something. It looks like if my local repository is beeing ignored. Instead of downloading the plugin in the specified directory from the settings.xml my maven3 is creating a repository for the plugin in my users .m2 dir? Why, all other dependencies are going in the specified local repository. Does anyone now why? Here is my effective-settings: ?xml version=1.0 encoding=UTF-8? settings xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org /2001/XMLSchema-instance xsi:schemaLocation=http://maven.apache.org/SETTINGS/1 .1.0 http://maven.apache.org/xsd/settings-1.1.0.xsd; localRepository xmlns=http://maven.apache.org/SETTINGS/1.1.0;d:\dev\maven-3 .0.3\repository/localRepository pluginGroups xmlns=http://maven.apache.org/SETTINGS/1.1.0; pluginGrouporg.codehaus.cargo/pluginGroup pluginGrouporg.apache.maven.plugins/pluginGroup pluginGrouporg.codehaus.mojo/pluginGroup /pluginGroups /settings [INFO] [INFO] BUILD SUCCESS [INFO] [INFO] Total time: 1.162s [INFO] Finished at: Thu Aug 04 23:27:19 CEST 2011 [INFO] Final Memory: 4M/90M [INFO] C:\Users\Stefan\.m2 -- View this message in context: http://maven-users.828.n2.nabble.com/Maven-3-and-cargo-plugin-tp6007841p6654331.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 3 and cargo plugin
bluewhale wrote: Downloaded: http://repo1.maven.org/maven2/org/codehaus/cargo/maven-metadata.xml [...] [ERROR] No plugin found for prefix 'cargo' It appears something went wrong during the last release of Cargo, the mentioned metadata file lists cargo2 as the plugin prefix which however contradicts the prefix stored in the cargo-maven2-plugin-1.1.1.jar/META-INF/maven/plugin.xml. So for now, mvn cargo2:goal should work. I already brought this up on the Cargo developer list, the release of 1.1.2 is currently open for voting, providing a good chance to see what happens with the metadata upon release. Benjamin - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How to Convert Ant Project to MAVEN
Hi, I have some questions for your guys. As i am starting converting projects from ANT to MAVEN. 1). How can i create EAR file by using multiple Modules in One Project. Example : MainProject ModuleJava ModuleEJB ModuleWeb ModuleWebservice ModuleSchema So my existing ANT project is first Creating JAR file for each modules and i am adding those JAR files in my EAR file. How can i do same things by using POM. Please give me guide me with some Example... 2) ModuleJava has directory structure something like this. com.companyname.service.core.* Now if i have to create ModuleJava's POM.XML to create JAR file.. I think MAVEN expects some specific source directory folder *src/main/java *and then source code.. But my existing coding standard for all project doesn't have something like this. So is there any work around to deal with this so don't need to recreate my directory structure and still i can compile my classes by giving dependencies. And it can create JAR file. 3) ModuleEJB has sample.ejb file and which is following 2.0 EJB standard how can i compile those classes and create JAR fiile for ModuleEJB ? Please share me some guidelines to convert my all projects from ANT to MAVEN. Please help me out. Thanks, Daivish.
Switching Mojos on Goal Results
Here is a sincere doubt I've been thinking and I'd like to ask your advice. I do have a war project which, when deployed, should be run a couple of IT targets. If tests are ok, then the build should be promoted to production. Otherwise, the server must be discarded. How could you switch among different mojos to be called based on test results from either Shitty and/or Failsafe? Examples are welcome Thank you -- -- Aldrin Leal, ald...@leal.eng.br
Re: mvn release is failing with git
Hi,
I don't know how to get the log, because that is all what maven will print
in the console. Even with mvn -X I get the same print out (plus some
exceptions).
- Mark Struberg strub...@yahoo.de wrote:
Erwin,
do you have a log of the git push command which fails? We log it to
the console in case of an error.
Please try to execute this command manually and check if there are any
errors too.
LieGrue,
strub
--- On Thu, 8/4/11, Stephen Connolly stephen.alan.conno...@gmail.com
wrote:
From: Stephen Connolly stephen.alan.conno...@gmail.com
Subject: Re: mvn release is failing with git
To: Maven Users List users@maven.apache.org
Date: Thursday, August 4, 2011, 6:43 AM
release activates some profiles which
will result in the active by default
profiles no longer being so
- Stephen
---
Sent from my Android phone, so random spelling mistakes,
random nonsense
words and other nonsense are a direct result of using swype
to type on the
screen
On 4 Aug 2011 03:10, erwin.muel...@deventm.org
wrote:
Hallo,
I have an error in maven release plugin (mvn
release:prepare):
[ERROR] The git-push command failed.
[ERROR] Command output:
[ERROR] fatal: The remote end hung up unexpectedly
But I'm sure that the remote repository works just
fine. Is there
difficulties with the git protocol? I post my settings.xml
and pom.xml:
@- settings.xml
settings
profiles
profile
idRepository Root Locations Local/id
activation
activeByDefaulttrue/activeByDefault
/activation
properties
archiva.repository.roothttp://localhost:8080/archiva
/archiva.repository.root
git.repository.rootgit://localhost/~devent/git.repository.root
/properties
/profile
...
-@
@- pom.xml
scm
connectionscm:git:${git.repository.root}/xmlstorage.git
/connection
developerConnectionscm:git:${git.repository.root}/xmlstorage.git
/developerConnection
urlscm:git:scm:git:${git.repository.root}/xmlstorage.git
/url
/scm
distributionManagement
repository
idglobalscaling.com-public/id
url${archiva.repository.root}/repository/globalscaling.com-public//url
/repository
snapshotRepository
idglobalscaling.com-public-snapshots/id
url${archiva.repository.root}/repository/globalscaling.com-public-snapshots//url
/snapshotRepository
/distributionManagement
-@
I have them in properties because I like to change
them without to touch
the pom.xml. Sometimes I work at home, there I have a good
internet
connection, but sometimes I work with my laptop with no/bad
connection. So I
setup a git repository and Archiva on localhost.
git pull and git push works, and mvn deploy works,
too. mvn scm update
works, too. So I don't understand, if I use the ssh
protocol in the URLs,
mvn release works just fine. Is it an issue with the git
protocol?
Kind regards, Erwin.
--
Erwin Mueller, erwin.muel...@deventm.org
http://www.global-scaling-institute.de/
http://www.deventm.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
--
Erwin Mueller, erwin.muel...@deventm.org
http://www.global-scaling-institute.de/
http://www.deventm.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: mvn release is failing with git
Hi,
you are saying because of mvn release plugin I can't use any of my own
profiles in settings.xml? That sounds to me like a bug, why would you ever want
that? Do you have a workaround for it? Maybe I need to activate the profile
from the command line?
- Stephen Connolly stephen.alan.conno...@gmail.com wrote:
release activates some profiles which will result in the active by
default
profiles no longer being so
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random
nonsense
words and other nonsense are a direct result of using swype to type on
the
screen
On 4 Aug 2011 03:10, erwin.muel...@deventm.org wrote:
Hallo,
I have an error in maven release plugin (mvn release:prepare):
[ERROR] The git-push command failed.
[ERROR] Command output:
[ERROR] fatal: The remote end hung up unexpectedly
But I'm sure that the remote repository works just fine. Is there
difficulties with the git protocol? I post my settings.xml and
pom.xml:
@- settings.xml
settings
profiles
profile
idRepository Root Locations Local/id
activation
activeByDefaulttrue/activeByDefault
/activation
properties
archiva.repository.roothttp://localhost:8080/archiva
/archiva.repository.root
git.repository.rootgit://localhost/~devent/git.repository.root
/properties
/profile
...
-@
@- pom.xml
scm
connectionscm:git:${git.repository.root}/xmlstorage.git
/connection
developerConnectionscm:git:${git.repository.root}/xmlstorage.git
/developerConnection
urlscm:git:scm:git:${git.repository.root}/xmlstorage.git /url
/scm
distributionManagement
repository
idglobalscaling.com-public/id
url${archiva.repository.root}/repository/globalscaling.com-public//url
/repository
snapshotRepository
idglobalscaling.com-public-snapshots/id
url${archiva.repository.root}/repository/globalscaling.com-public-snapshots//url
/snapshotRepository
/distributionManagement
-@
I have them in properties because I like to change them without to
touch
the pom.xml. Sometimes I work at home, there I have a good internet
connection, but sometimes I work with my laptop with no/bad
connection. So I
setup a git repository and Archiva on localhost.
git pull and git push works, and mvn deploy works, too. mvn scm
update
works, too. So I don't understand, if I use the ssh protocol in the
URLs,
mvn release works just fine. Is it an issue with the git protocol?
Kind regards, Erwin.
--
Erwin Mueller, erwin.muel...@deventm.org
http://www.global-scaling-institute.de/
http://www.deventm.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Erwin Mueller, erwin.muel...@deventm.org
http://www.global-scaling-institute.de/
http://www.deventm.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Trouble configuring an additional context path for embedded Tomcat
Hi, I'm using Maven 3.0.3 with the Tomcat plugin. I have a directory outside of my war that contains static assets. It will have a different context path than the default war. How do I configure my plugin to associate the additional context path for the other resources? Thanks for your help, - Dave -- View this message in context: http://maven.40175.n5.nabble.com/Trouble-configuring-an-additional-context-path-for-embedded-Tomcat-tp4668005p4668005.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: mvn release is failing with git
Am 05.08.2011 03:05, schrieb Erwin Mueller:
Hi,
Maybe I need to activate the profile from the command line?
Either that or use activeProfiles in your settings.xml instead of
activeByDefault. The latter is is *only* relevant if no other profiles
are activated (as the release plugin does). This is documented behaviour
according to [1].
Best regards,
Ansgar
[1]
http://maven.apache.org/guides/introduction/introduction-to-profiles.html
- Stephen Connolly stephen.alan.conno...@gmail.com wrote:
release activates some profiles which will result in the active by
default
profiles no longer being so
- Stephen
---
Sent from my Android phone, so random spelling mistakes, random
nonsense
words and other nonsense are a direct result of using swype to type on
the
screen
On 4 Aug 2011 03:10, erwin.muel...@deventm.org wrote:
Hallo,
I have an error in maven release plugin (mvn release:prepare):
[ERROR] The git-push command failed.
[ERROR] Command output:
[ERROR] fatal: The remote end hung up unexpectedly
But I'm sure that the remote repository works just fine. Is there
difficulties with the git protocol? I post my settings.xml and
pom.xml:
@- settings.xml
settings
profiles
profile
idRepository Root Locations Local/id
activation
activeByDefaulttrue/activeByDefault
/activation
properties
archiva.repository.roothttp://localhost:8080/archiva
/archiva.repository.root
git.repository.rootgit://localhost/~devent/git.repository.root
/properties
/profile
...
-@
@- pom.xml
scm
connectionscm:git:${git.repository.root}/xmlstorage.git
/connection
developerConnectionscm:git:${git.repository.root}/xmlstorage.git
/developerConnection
urlscm:git:scm:git:${git.repository.root}/xmlstorage.git /url
/scm
distributionManagement
repository
idglobalscaling.com-public/id
url${archiva.repository.root}/repository/globalscaling.com-public//url
/repository
snapshotRepository
idglobalscaling.com-public-snapshots/id
url${archiva.repository.root}/repository/globalscaling.com-public-snapshots//url
/snapshotRepository
/distributionManagement
-@
I have them in properties because I like to change them without to
touch
the pom.xml. Sometimes I work at home, there I have a good internet
connection, but sometimes I work with my laptop with no/bad
connection. So I
setup a git repository and Archiva on localhost.
git pull and git push works, and mvn deploy works, too. mvn scm
update
works, too. So I don't understand, if I use the ssh protocol in the
URLs,
mvn release works just fine. Is it an issue with the git protocol?
Kind regards, Erwin.
--
Erwin Mueller, erwin.muel...@deventm.org
http://www.global-scaling-institute.de/
http://www.deventm.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Maven, Eclipse, Nexus, Perforce, Team City, Oh My!
OK, this is my meager first attempt to give something back to the community... http://docs.codehaus.org/display/MAVENUSER/Maven%2C+Eclipse%2C+Nexus%2C+Perforce%2C+Team+City%2C+Oh+My! http://docs.codehaus.org/display/MAVENUSER/Maven%2C+Eclipse%2C+Nexus%2C+Perforce%2C+Team+City%2C+Oh+My%21 Send e-mail to my personal address, or flame/commend me in the mailing lists - I'm thick skinned, but receptive of praise. The point is, I really love Maven, but I want to see it improve, and this is my way of going about it. I hope hope to add more experience to this in the future, so comments and criticism are appreciated. Cheers, Eric - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
