Re: Maven in 5 minutes doesn't work

I have attached the settings.xml I was getting following error while I was creating a project before I downloaded the plugin jars manually. Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-install-plugin/2.3.1/maven-install-plugin-2.3.1.jar [WARNING] Failed to retrieve

Re: Maven Ant Demo

Ahh, now I get it. You are running Maven 3. I hadn't tested Ant based plugins in Maven 3 until now, and apparently it doesn't work as it did in Maven 2. On Thu, Dec 16, 2010 at 6:28 PM, dan.old...@emc.com wrote: I'm just learning Maven and trying this demo:

Re: Maven in 5 minutes doesn't work

Google is your friend: http://maven.apache.org/guides/mini/guide-proxies.html /Anders On Fri, Dec 17, 2010 at 09:52, biswamohan.padhy biswamohan.pa...@bt.comwrote: I have attached the settings.xml I was getting following error while I was creating a project before I downloaded the plugin

Dependency on pom-project not resolved in reactor on multi-module build

Hello, I am having the following issue with artifact resolution in the Maven reactor. My project layout resembles the following: -- Parent POM -- POM A (packaging: pom) -- POM B (packaging: jar) POM A and POM B have Parent POM as parent. Parent POM has POM A and POM B as submodules.

Maven and environment Properties - Feature or bug ??

In windows: set test=dev and using ${env.test} in the pom for example in name myArtifact _${env.test}/name Results in: Building myArtifact_${env.test} 00.01-SNAPSHOT set TEST=dev and using ${env.TEST} in the pom for example in name myArtifact _${env.TEST}/name Results in: Building

AW: Dependency on pom-project not resolved in reactor on multi-module build

What happens, if you use mvn install? Fredy -Ursprüngliche Nachricht- Von: Florian Rampp [mailto:florian.ra...@jambit.com] Gesendet: Freitag, 17. Dezember 2010 10:51 An: users@maven.apache.org Betreff: Dependency on pom-project not resolved in reactor on multi-module build Hello, I

AW: Dependency on pom-project not resolved in reactor on multi-module build

How is the reactor solving the order of your modules? How is the order in your parent pom? Fredy -Ursprüngliche Nachricht- Von: Florian Rampp [mailto:florian.ra...@jambit.com] Gesendet: Freitag, 17. Dezember 2010 10:51 An: users@maven.apache.org Betreff: Dependency on pom-project not

ant task runs twice

Hello, I've got an Ant task which is bound to 'generate-resources' phase. If I try to deploy the project, the task gets executed twice (before and after the tests). Any ideas about how could I prevent that? # 'release' and 'local' are my own profiles. (~/)\mvn -P release,-local clean deploy

Re: ant task runs twice

It also seems that this has nothing to do with whatever lifecycle is the task bound to. Even if the POM looks like below, it runs twice: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-antrun-plugin/artifactId version1.6/version executions

activating a profile by two environment variables/values

Hi, I have four profiles prodDeps, prodResources, devDeps, devResources. If I set ENVIRONMENT=devContainer - prodDeps and devResources should be activated If I set ENVIRONMENT=prodContainer - prodDeps and prodResources should be activated If I set ENVIRONMENT=eclipse - devDeps and devResources

Re: ant task runs twice

Never mind, I've spend half day with this and it was my fault. :( ( mvn -Drelease-version=43 -P release,-local clean test deploy ) test / deploy both run tests. On Fri, Dec 17, 2010 at 10:35 AM, Mate Varga mate.va...@gmail.com wrote: It also seems that this has nothing to do with whatever

Re: Maven and environment Properties - Feature or bug ??

Hauschel Fred Robert wrote: Or did I have problems understanding the environment variables? Is there a case sensitivity in general ?? http://maven.apache.org/pom.html#Properties Benjamin - To unsubscribe, e-mail:

AW: Maven and environment Properties - Feature or bug ??

Rtfm ;-) Thanks!!! Fredy -Ursprüngliche Nachricht- Von: Benjamin Bentmann [mailto:benjamin.bentm...@udo.edu] Gesendet: Freitag, 17. Dezember 2010 12:18 An: Maven Users List Betreff: Re: Maven and environment Properties - Feature or bug ?? Hauschel Fred Robert wrote: Or did I have

Re: Handling native dependencies via classifier(s)

Thanks for that. re: jar. Is there an advantage building a jar for natives rather than a zip? re: single jar natives. makes sense, and saves a lot of manual config in eclipse to add each native path later (I often need to switch versions). Although I wonder how this will affect my final

Re: AW: Dependency on pom-project not resolved in reactor on multi-module build

Hello Freddy, Thanks for your quick reply. I should have mentioned that mvn installs solves the problem. So Maven resolves the dependency from the local repository. But this is just a workaround since I expect the dependency to be resolved from the reactor. I think the order in which the

Re: Chicken-and-egg problem: plugin dependencies as modules

Hi Wayne, thanks for the advice. What's the best way to resolve this kind of chicken-and-egg problem without introducing too many extra projects just to break the cycle? Any This is exactly what you have to do. The rulesets should be packaged and versioned independent of the project. Ideally

AW: AW: Dependency on pom-project not resolved in reactor on multi-module build

Hello Florian, have you defined the typepom/type ?? dependencies dependency groupIdmygroup/groupId artifactIdA/artifactId version${parent.version}/version typepom/type /dependency Fredy -Ursprüngliche Nachricht- Von: Florian Rampp

Re: Chicken-and-egg problem: plugin dependencies as modules

The organizational pom can prescribe the use of the most recently released ruleset. The next version of the ruleset would technically be checked against the previous version, but as rulesets are not java code the check will not be applied on that artifact. -Stephen On 17 December 2010 11:55,

AW: AW: Dependency on pom-project not resolved in reactor on multi-module build

Yes, I have. See my first mail for the content of A/pom.xml and B/pom.xml Florian -- Florian Rampp, Software Architect Phone: +49.89.45 23 47-64 -Ursprüngliche Nachricht- Von: Hauschel Fred Robert [mailto:fredrobert.hausc...@cirquent.de] Gesendet: Freitag, 17. Dezember 2010 13:12

AW: AW: Dependency on pom-project not resolved in reactor on multi-module build

So I can't see a difference to my test, expecting version${project.version}/version I've used version${parent.version}/version Can't imagine, that that is a difference, but who knows! Fredy project xmlns=http://maven.apache.org/POM/4.0.0;

How to resolve 'LATEST'

Hi all, I'm writing an enforcer-rule, that should check if my parent is the LATEST version. How can I get the actual version for 'LATEST'? Thanks! -- Roland Asmann Senior Software Engineer adesso Austria GmbH Floridotower 26. Stock T +43 1 2198790-27 Floridsdorfer Hauptstr. 1

Re: Chicken-and-egg problem: plugin dependencies as modules

Hi Stephen, The organizational pom can prescribe the use of the most recently released ruleset. The next version of the ruleset would technically be checked against the previous version, but as rulesets are not java code the check will not be applied on that artifact. True. But its a little

Shade plugin dependency

I get an error when I build using shade plugin 1.4 that it is having trouble resolving a dependency on org.apache.commons:commons-io:1.3.2. The cause of the problem is my maven repo that doesn't have a good copy of that jar file. My questions for the forum are. 1. Can I configure my plugin to

Re: Maven 3 reports wrong version

Hm, this is still a mystery. I've run ./mvn.bat, and I get the same version reported (2.2.1) I downloaded a python script that simulates which ( http://nedbatchelder.com/code/utilities/wh_py.html) and the maven that is being run is indeed maven3.0.1bin\mvn.bat. Should I clear my local .m2

Re: Maven 3 reports wrong version

Andre M wrote: I just upgraded to Maven3 from Maven2 today, and when I run mvn.bat -version, this is what I see: [...] at org.apache.maven.cli.MavenCli.buildSettings(MavenCli.java:402) at org.apache.maven.cli.MavenCli.main(MavenCli.java:202) at

Re: POM inheritance breaks build

Jörg Schaible-3 wrote: The point is that it is platform dependent - the platform your developer is using. A profile should not be used to define dependencies - at least if those should be transitively inherited. It simply does not work in the way most people assume. It is not inherited

Re: Shade plugin dependency

Hi Paul, Paul Mendelson wrote: I get an error when I build using shade plugin 1.4 that it is having trouble resolving a dependency on org.apache.commons:commons-io:1.3.2. GroupId is wrong: http://mvnrepository.com/artifact/commons-io/commons-io The cause of the problem is my maven repo that

Re: POM inheritance breaks build

cowwoc wrote: Jörg Schaible-3 wrote: The point is that it is platform dependent - the platform your developer is using. A profile should not be used to define dependencies - at least if those should be transitively inherited. It simply does not work in the way most people assume.

Re: How to package a JAR file in an EAR file so that this can be accessed by all other modules (ex: EJB, WAR, etc)

I do not know if the error is because I lack some configuration setting or else because Geronimo does not realise that the ehb module needs the persistence module and therefore one should be deplpoyed before the other. The manual way to fix this: unpack the EAR that Maven produced, and unpack

Re: How to resolve 'LATEST'

Don't use RELEASE or LATEST. On Fri, Dec 17, 2010 at 7:43 AM, Asmann, Roland roland.asm...@adesso.at wrote: Hi all, I'm writing an enforcer-rule, that should check if my parent is the LATEST version. How can I get the actual version for 'LATEST'? Thanks! -- Roland Asmann Senior Software

maven-svn-revision-number-plugin Date Property

Hi, Well I have a question of the use of maven-svn-revision-number-plugin. I need to have in an output file the information of the svn. So, now I have this information in my file. repository = ${prefix.repository} path = ${prefix.path} revision = ${prefix.revision} mixedRevisions

Re: How to resolve 'LATEST'

Currently I am not using this, but I want the enforcer to check which version 'LATEST' is and tell the user he should update to that version! On 17-12-10 17:04, Brian Fox wrote: Don't use RELEASE or LATEST. On Fri, Dec 17, 2010 at 7:43 AM, Asmann, Roland roland.asm...@adesso.at wrote: Hi

Re: Maven 3 reports wrong version

On Fri, Dec 17, 2010 at 2:22 PM, Andre M mougeot.an...@gmail.com wrote: being run is indeed maven3.0.1bin\mvn.bat. Do you have M2_HOME in environment pointed to old version? -Guo - To unsubscribe, e-mail:

Re: Missing goal eclipse:m2eclipse in version 2.8 of the Maven Eclipse plugin

On Thu, Dec 16, 2010 at 9:39 PM, Stefan Eder stefan.e...@ebuconnect.de wrote:  Hi, since quite a while I am using Maven and Eclipse together with the Eclipse plugin for Maven and the Maven plugin for Eclipse. And it is just great. But in the version 2.8 of the Eclipse plugin for Maven I am