How to declare that my plugin doesn't work with Maven 3?
Is there a way to declare that my plugin doesn't work with Maven 3? If not, how can I handle this programmatically? In other words, how can I find out which version of Maven my plugin gets run with, so that I can throw an exception? Cheers, Peter - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 3 no longer supporting dynamic configuration of plugins?
No Maven committers reading this list? Even a No would help. Cheers, Peter -- View this message in context: http://maven.40175.n5.nabble.com/Maven-3-no-longer-supporting-dynamic-configuration-of-plugins-tp3279670p3292542.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 build fails because of empty maven-metadata-central.xml under hudson
Hi,
To whom it may concern I would like to update that I seem to be able to work
around this issue:
In the super pom for all of our projects I've defined the following:
dependencyManagement
dependencies
...
dependency
groupIdcom.amazonaws/groupId
artifactIdaws-java-sdk/artifactId
version1.1.0/version
/dependency
dependency
groupIdcommons-httpclient/groupId
artifactIdcommons-httpclient/artifactId
version3.1/version
/dependency
dependency
groupIdcommons-logging/groupId
artifactIdcommons-logging/artifactId
version1.1/version
/dependency
/dependencies
...
/dependencyManagement
This causes maven to pick version 1.1 of commons-logging even without
consulting the metadata file :).
I would like to mention that this is a hack to get this thing to work but I
would obviously like to work for a proper solution on this problem.
Thanks,
Maxim.
On Thu, Dec 2, 2010 at 8:29 PM, Maxim Veksler ma...@vekslers.org wrote:
Hi,
// This email is cross posted to maven-users hudson-users, Maven seems to
be the issue, but it only reproduces under Hudson environment.
First, a quick description of the problem before I drill down into the
details: Our maven projects that depend on
com.amazonaws:aws-java-sdk:jar:1.1.0 fail to build on our linux based Hudson
installation (server is sitting on EC2) because of unsatisfied range
dependency coming from aws-java-sdk - commons-logging [1.1,2.0). This
happens only on the build server, and reproduces after
several successful builds. On the develop machines this does not happen.
The full behavior, and debugging steps are as following.
We have a super pom that defines:
dependencyManagement
dependencies
dependency
groupIdcom.amazonaws/groupId
artifactIdaws-java-sdk/artifactId
version1.1.0/version
/dependency
/dependencies
/dependencyManagement
Then projects (that define the super pom as their parent) define the
dependency on aws-java-sdk in their own pom:
dependencies
dependency
groupIdcom.amazonaws/groupId
artifactIdaws-java-sdk/artifactId
/dependency
/dependencies
This setup works great and compiles on the development Ubuntu machines.
On Hudson OTOH the same setup yields different results, once in a while the
build fails with the following error:
$ mvn install
[INFO] Scanning for projects...
[INFO]
[INFO] Building mad service online updater
[INFO]task-segment: [install]
[INFO]
[INFO] [resources:resources {execution: default-resources}]
[INFO] Using 'UTF-8' encoding to copy filtered resources.
[INFO] Copying 6 resources
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
No versions are present in the repository for the artifact with a range
[1.1,2.0)
commons-logging:commons-logging:jar:null
from the specified remote repositories:
Everything (http://artifactory.eyeviewdigital.com/artifactory/repo),
central (http://repo1.maven.org/maven2)
Path to dependency:
1) com.eyeview:mad-updater:jar:1.0.0-SNAPSHOT
2) com.amazonaws:aws-java-sdk:jar:1.1.0
After debugging this I came to the conclusion that the reason it fails on
the production build server is because the maven-metadata
for commons-logging get's emptied on the build server.
Here is how the file looks on the build server (I've download it to my
local PC, and was able to successfully reproduce the bug using the .m2
coming from Hudson):
ma...@maxim-desktop:~/workspace$ cat
~/.m2/repository/commons-logging/commons-logging/maven-metadata-Everything.xml
?xml version=1.0 encoding=UTF-8?
metadata
groupIdcommons-logging/groupId
artifactIdcommons-logging/artifactId
/metadata
Here is how it looks on my machine (I've renamed my local .m2 to a
.m2-mine)
ma...@maxim-desktop:~/workspace$ cat
~/.m2-mine/repository/commons-logging/commons-logging/maven-metadata-Everything.xml
?xml version=1.0 encoding=UTF-8?
metadata
groupIdcommons-logging/groupId
artifactIdcommons-logging/artifactId
version1.1.1/version
versioning
release1.1.1/release
versions
version1.0/version
version1.0.1/version
version1.0.2/version
version1.0.3/version
version1.0.4/version
version1.1/version
version1.1.1/version
/versions
lastUpdated20071128191817/lastUpdated
/versioning
/metadata
You can see that the metadata
file exists activation
I'm a new to maven. I've recently tried unsuccessfully to get
activationfileexists to work unless the absolute file path was given.
I'm running on windows XP, with netbeans IDE 6.8 supposedly using maven
3.0-SNAPSHOT.
I've tried:
existsC:/Documents and Settings/xname/My
Documents/maven/mrt/storage/store-conf/mrt.local.properties/exists ---
works
exists${basedir}/mrt.local.properties/exists --- does NOT work
exists./mrt.local.properties/exists --- does NOT work
existsmrt.local.properties/exists --- does NOT work
Any suggestions for getting activationfileexists to work without
using an absolute filepath.
Thanks
David
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: assembly strange result
Thanks Kristian, i will try this on monday :-) S. Somehow this sounds like the notorious http://jira.codehaus.org/browse/PLXCOMP-149 and the attached http://jira.codehaus.org/browse/MSHARED-148 Upgrade all your plugins to the latest version. Kristian Make sure fr., 03.12.2010 kl. 20.47 +0100, skrev reno: hi, today, we encountered a strange result with the assembly plugin: we had a jar inside a project which is a part of the project. We write an assembly file to create a tar file. No problem for the part :-) the problem is: the size of the library is about 2.7 Mo. when we untar the package, the size of the library is 4.6 Mo !! Is anybody see this strange behavior ? I know that we could use deploy the library on a maven repository (we will do it next week) but i would like to know why after packaging and untaring, the size of the library increases.. (maven 2.1, jdk 5, RHEL5) Regards S. - 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: file exists activation
where is your pom.xml?
C:/Documents and Settings/xname/My Documents/maven/mrt/storage ?
regards,
Hervé
Le samedi 4 décembre 2010, dloy a écrit :
I'm a new to maven. I've recently tried unsuccessfully to get
activationfileexists to work unless the absolute file path was given.
I'm running on windows XP, with netbeans IDE 6.8 supposedly using maven
3.0-SNAPSHOT.
I've tried:
existsC:/Documents and Settings/xname/My
Documents/maven/mrt/storage/store-conf/mrt.local.properties/exists ---
works
exists${basedir}/mrt.local.properties/exists --- does NOT work
exists./mrt.local.properties/exists --- does NOT work
existsmrt.local.properties/exists --- does NOT work
Any suggestions for getting activationfileexists to work without
using an absolute filepath.
Thanks
David
-
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 3 no longer supporting dynamic configuration of plugins?
I can't answer your question, sorry. Maybe you should post this at the dev list. There resides the most people with intimate knowledge about Maven's plugin setup. With regards, Nick Stolwijk ~Java Developer~ IPROFS BV. Claus Sluterweg 125 2012 WS Haarlem http://www.iprofs.nl On Sat, Dec 4, 2010 at 11:08 PM, Peter Niederwieser pnied...@gmail.com wrote: No Maven committers reading this list? Even a No would help. Cheers, Peter -- View this message in context: http://maven.40175.n5.nabble.com/Maven-3-no-longer-supporting-dynamic-configuration-of-plugins-tp3279670p3292542.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
maven-eclipse-plugin
Hi all, Does anybody know in which version the support for wtp 2.x was added? And when will support for wtp 3.x be added? Thanks! -- Roland Asmann Senior Software Engineer adesso Austria GmbH Floridotower 26. Stock T +43 1 2198790-27 Floridsdorfer Hauptstr. 1 F +43 1 2198790-927 A-1210 Wien M +43 664 88657566 E roland.asm...@adesso.at W www.adesso.at - business. people. technology. - - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 3 no longer supporting dynamic configuration of plugins?
I only look at user list infrequently. This question would have likely been answered faster on the dev list. You might want to look at the new maven-site-plugin and ask Olivier Lamy specifically how he's manipulating configuration before the execution of a plugin. We also use this technique in M2Eclipse. So it is possible, is it documented? No. This I consider part of the embedding API which will resurface in documented, supported form in Maven 3.1. You're free to use the internal APIs but they may change. On Dec 4, 2010, at 5:08 PM, Peter Niederwieser wrote: No Maven committers reading this list? Even a No would help. Cheers, Peter -- View this message in context: http://maven.40175.n5.nabble.com/Maven-3-no-longer-supporting-dynamic-configuration-of-plugins-tp3279670p3292542.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 Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl - A party which is not afraid of letting culture, business, and welfare go to ruin completely can be omnipotent for a while. -- Jakob Burckhardt
classes complied by plexus-compiler-plugin get 'source not found' problem in eclipse class file editor
Hi, I just find a bug in plexus-compiler-plugin. All classes complied by plexus-compiler-plugin will get 'source not found' problem in eclipse class file editor which is opened when you access the jar file containing the compiled classes even though you have source jar associated with the jar file. I do not know where to report this bug. This bug has been around and bothered me for many years. Today, I finally find out why I always get the 'source not found' for all jars genered by me. Some guy met the same probem as mine, see http://www.mail-archive.com/users@maven.apache.org/msg80120.html for his observation on this problem. Regards, Rice
Re: maven-eclipse-plugin
On Mon, Dec 6, 2010 at 12:51 AM, Asmann, Roland roland.asm...@adesso.at wrote: Hi all, Does anybody know in which version the support for wtp 2.x was added? Not really, you'd have to trawl through the code base to see for sure. http://maven.apache.org/plugins/maven-eclipse-plugin/wtp.html lists the versions available And when will support for wtp 3.x be added? There is no active development for adding wtp 3.x support. Feel free to create a jira, integration tests and patches. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-eclipse-plugin
On a related note, can anyone summarize what the best way of maintaining eclipse projects from Maven is? I use IDEA, and the best way from there is IDEA itself, not with the IDEA plugin for Maven. Is the same true for Eclipse that the IDE plugin for Maven is better than the Maven plugin for the IDE? If so, what is the best plugin for Eclipse (there seems to be more than one). Thanks, Brian On Dec 5, 2010, at 6:41 PM, Barrie Treloar wrote: On Mon, Dec 6, 2010 at 12:51 AM, Asmann, Roland roland.asm...@adesso.at wrote: Hi all, Does anybody know in which version the support for wtp 2.x was added? Not really, you'd have to trawl through the code base to see for sure. http://maven.apache.org/plugins/maven-eclipse-plugin/wtp.html lists the versions available And when will support for wtp 3.x be added? There is no active development for adding wtp 3.x support. Feel free to create a jira, integration tests and patches. - 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: classes complied by plexus-compiler-plugin get 'source not found' problem in eclipse class file editor
Some typo on my last message. The plugin causing problem is plexus-compiler-eclipse. On Mon, Dec 6, 2010 at 1:12 AM, Rice Yeh rice...@gmail.com wrote: Hi, I just find a bug in plexus-compiler-plugin. All classes complied by plexus-compiler-plugin will get 'source not found' problem in eclipse class file editor which is opened when you access the jar file containing the compiled classes even though you have source jar associated with the jar file. I do not know where to report this bug. This bug has been around and bothered me for many years. Today, I finally find out why I always get the 'source not found' for all jars genered by me. Some guy met the same probem as mine, see http://www.mail-archive.com/users@maven.apache.org/msg80120.html for his observation on this problem. Regards, Rice
Re: maven-eclipse-plugin
On 05/12/2010 7:09 PM, Brian Topping wrote: On a related note, can anyone summarize what the best way of maintaining eclipse projects from Maven is? I use IDEA, and the best way from there is IDEA itself, not with the IDEA plugin for Maven. Is the same true for Eclipse that the IDE plugin for Maven is better than the Maven plugin for the IDE? If so, what is the best plugin for Eclipse (there seems to be more than one). The Eclipse/STS from Springsource is the easiest way to get Eclipse integrated with Maven. Thanks, Brian On Dec 5, 2010, at 6:41 PM, Barrie Treloar wrote: On Mon, Dec 6, 2010 at 12:51 AM, Asmann, Rolandroland.asm...@adesso.at wrote: Hi all, Does anybody know in which version the support for wtp 2.x was added? Not really, you'd have to trawl through the code base to see for sure. http://maven.apache.org/plugins/maven-eclipse-plugin/wtp.html lists the versions available And when will support for wtp 3.x be added? There is no active development for adding wtp 3.x support. Feel free to create a jira, integration tests and patches. - 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: Maven Transitive dependency for woven jar
I don't have a solution for you, but as you've not received an answer from anyone else I wanted to reply. I have run into a similar situation with aop, but haven't really come up with a good solution. In my case, the aop weaving was just used for testing, so the dependency tree wasn't an issue for anyone else. /Anders On Fri, Nov 26, 2010 at 12:09, Akhilesh Singh akhil...@zinniasystems.comwrote: Hi, I am currently facing an issue in our project setup. The scenario is something like this: 1) Project A - Project B - Project C 2) Project A-web - Project A Project D This works all fine as generated was for Project A-web conains all the required jars. ( A, B, C,D) 3) Project A-woven - Project A Aspect-jar Now, we are creating a aspectj woven jar pf Project A using aspectj mojo. The name of this module is Project A-woven. We want to include this jar in the Project A-web instead of Project A. However, if I add Project A-woven as dependency and add Project A as exclusion in Project A-web( otherwise both A and A-woven will be present) , Project B and Proejct-C will also not be included in the resulting war. Project A is a typical enterprise application and has more than 20 jars as dependency which I don't want to add again in Project A-web or Project A-woven. My idea is to add Project A-woven with Project-A as exclusion in Project A-web while keeping the dependencies of A intact. Is this possible? Can anybody please help with suggestions on this? Regards, *Akhilesh Singh* *Chief Software Architect, * *Zinnia Systems,* *Mobile: +91 9742306306* *http://www.zinniasystems.com* http://www.zinniasystems.com/
