Re: pde-maven-plugin calls wrong ant target
Hi Jeroren, I spent almost a week on avoiding that src.zip in the plugin.zip. I did not find any help on that and ultimately I had to resolve to a workaround which is that I now build a feature(dummy) which includes the plug in I actually want to build. When I get the feature.zip, I find my plug in inside that without src.zip. I know its not something I should have resolved to, but that was the only thing that I could find to fix the src.zip problem. If you find something on how to correct the ant calls, please let me know as well. Thanks and regards, Amit Kumar On Mon, Mar 17, 2008 at 6:40 PM, JeroenL [EMAIL PROTECTED] wrote: Hi all, I'm trying to build an Eclipse plugin with maven. Problems are that 1) the archive is zipped and 2) a directory is added and 3) a sr.zip is added. After investigating the calls to Ant I discovered that maven calls the targets clean build.jars zip.plugin. According my belief this should be clean build.update.jar Does anyone have an idea how to call the proper targets? Regards, Jeroen -- View this message in context: http://www.nabble.com/pde-maven-plugin-calls-wrong-ant-target-tp16092576s177p16092576.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
NoClassDefFoundError when running maven-exec-plugin and Cobertura
Hi,
I have configured my reporting section with the cobertura plugin, version
2.0.
I also have a maven-exec-plugin defined to setup my testdatabase during the
test-compile phase as shown below:
(notice the classpath definition. If I understand this correctly, this
configuration should make all project dependencies appear on the classpath
during the maven execution, hmm, might be on to something here. anyway...)
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdexec-maven-plugin/artifactId
executions
!-- Test for the existence of the database --
execution
idtest-db-exists/id
phasetest-compile/phase
goals
goalexec/goal
/goals
configuration
executablejava/executable
arguments
argument-classpath/argument
classpath /
argument
blabla.blabla.blala.DatabaseAccessVerifier
/argument
/arguments
/configuration
/execution
/executions
/plugin
Now when I run mvn site, I get the following stacktrace (not complete
stacktrace)
[INFO] Instrumentation was successful.
[INFO] [resources:testResources]
[INFO] Using default encoding to copy filtered resources.
[INFO] [compiler:testCompile]
[INFO] Nothing to compile - all classes are up to date
[INFO] [exec:exec {execution: test-db-exists}]
[INFO] java.lang.NoClassDefFoundError:
net/sourceforge/cobertura/coveragedata/HasBeenInstrumented
[INFO] at java.lang.ClassLoader.defineClass1(Native Method)
[INFO] at java.lang.ClassLoader.defineClass(Unknown Source)
[INFO] at java.security.SecureClassLoader.defineClass(Unknown Source)
[INFO] at java.net.URLClassLoader.defineClass(Unknown Source)
[INFO] at java.net.URLClassLoader.access$000(Unknown Source)
[INFO] at java.net.URLClassLoader$1.run(Unknown Source)
[INFO] at java.security.AccessController.doPrivileged(Native Method)
[INFO] at java.net.URLClassLoader.findClass(Unknown Source)
[INFO] at java.lang.ClassLoader.loadClass(Unknown Source)
[INFO] at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
[INFO] at java.lang.ClassLoader.loadClass(Unknown Source)
[INFO] at java.lang.ClassLoader.loadClassInternal(Unknown Source)
[INFO] Caused by: java.lang.ClassNotFoundException:
net.sourceforge.cobertura.coveragedata.HasBeenInstrumented
[INFO] at java.net.URLClassLoader$1.run(Unknown Source)
[INFO] at java.security.AccessController.doPrivileged(Native Method)
[INFO] at java.net.URLClassLoader.findClass(Unknown Source)
[INFO] at java.lang.ClassLoader.loadClass(Unknown Source)
[INFO] at sun.misc.Launcher$AppClassLoader.loadClass(Unknown Source)
[INFO] at java.lang.ClassLoader.loadClass(Unknown Source)
[INFO] at java.lang.ClassLoader.loadClassInternal(Unknown Source)
[INFO] ... 12 more
[INFO] Exception in thread main
[INFO]
[ERROR] BUILD ERROR
[INFO]
Does anyone know how I can get the exec plugin to find the cobertura
classes?
Best Regards
Customizing Build order
Hi, I have a multi-module project with the following structure. Root -A -A1 -A2 -A3 -B -B1 -B2 -B3 -B4 In the Root's pom i have mentioned my modules as: moduleA/module moduleB/module Now is there a way that I can change the normal build order(which is) -Root -A -A1 -A2 -A3 -B -B1 -B2 -B3 -B4 to something like -Root -A -A1 -A2 -B -B1 -B2 -A3 -B4 It is actually a requirement. But I doubt that there is a possibility that the CVS structure itself is not competent enough then to handle inter-module dependencies. Any inputs? Thanks and regards, Amit Kumar
release plugin and modules tagging does not work?
Hello, I have the following structure locally: releases - pom.xml - module1 - pom.xml - module2 - pom.xml The release is a pom.xml that mainly contains a version number (SNAPSHOT), module tags and scm informations All poms have correct information tags. Individually, i can perform a release on each submodule without trouble (tagging work, so scm is set correctly to pom). However, if i try to release all modules at once using toplevel pom, maven release plugin only tags the parent poms instead of tagging each submodule. It doesn't seem to respect scm informations present in submodules My svn structure is as follow http://svn/path - releases -trunk -tags -branches - module1 -trunk -tags -branches - module2 -trunk -tags -branches I use property svn:externals to collect modules as subfolders of releases. Is it a known limitation of maven release plugin? Are there any work-around for this? Thanks for informations -- David Delbecq Institut Royal Météorologique Ext:557 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Customizing Build order
amit kumar wrote: to something like -Root -A -A1 -A2 -B -B1 -B2 -A3 -B4 It is actually a requirement. But I doubt that there is a possibility that the CVS structure itself is not competent enough then to handle inter-module dependencies. This looks suspiciously like a circular dependency? If so, circular dependencies are broken regardless of your build tool. Regards, Graham -- smime.p7s Description: S/MIME Cryptographic Signature
Re: Customizing Build order
amit kumar schrieb: Hi, I have a multi-module project with the following structure. Root -A -A1 -A2 -A3 -B -B1 -B2 -B3 -B4 In the Root's pom i have mentioned my modules as: moduleA/module moduleB/module Now is there a way that I can change the normal build order(which is) -Root -A -A1 -A2 -A3 -B -B1 -B2 -B3 -B4 to something like -Root -A -A1 -A2 -B -B1 -B2 -A3 -B4 It is actually a requirement. But I doubt that there is a possibility that the CVS structure itself is not competent enough then to handle inter-module dependencies. Any inputs? Man, that is a seriously weird and twisted requirement. I know of no way to get maven to do this, and see no reason why such a feature should exist in maven. It looks to me like you should fix whatever problem exists in your source code that requires this weird build setup rather than distorting your build system to handle it. Regards, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Customizing Build order
En l'instant précis du 18/03/08 09:42, amit kumar s'exprimait en ces termes: Hi, I have a multi-module project with the following structure. Root -A -A1 -A2 -A3 -B -B1 -B2 -B3 -B4 In the Root's pom i have mentioned my modules as: moduleA/module moduleB/module Now is there a way that I can change the normal build order(which is) -Root -A -A1 -A2 -A3 -B -B1 -B2 -B3 -B4 to something like -Root -A -A1 -A2 -B -B1 -B2 -A3 -B4 It is actually a requirement. But I doubt that there is a possibility that the CVS structure itself is not competent enough then to handle inter-module dependencies. Any inputs? Thanks and regards, Amit Kumar In the A3 project, add dependencies that point to all other projects you need to have compiled before (i suspect you need B2 resources for A3?), maven should order them properly. -- David Delbecq Institut Royal Météorologique Ext:557 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Integrating existing project
I am a newbie with Maven. My problem: I want to integrate an already existing project (Webapp) into Maven (schould I create the pom.xml manually into the root folder of the project?). I'm not sure how this works. The Getting started section couldnt help me. As a result must be delivered a war-file. I want to run this war-file into Tomcat. In the project I have several source folders. It should be inserted jsp-, jspx-, jar-and xml files from several folders into the war-file. Can someone help me? Best regards, buFka -- View this message in context: http://www.nabble.com/Integrating-existing-project-tp16117612s177p16117612.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[surefire] problem with xml
Hi all, I encounter problem with my junit tests when I try to update version of surefire plugin. Actually all my tests that need to read xml files failed with the following error : org.apache.xml.utils.WrappedRuntimeException: Output method is xml could not load output_xml.properties (check CLASSPATH) at org.apache.xalan.templates.OutputProperties.getDefaultMethodProperties( OutputProperties.java:394) at org.apache.xalan.templates.OutputProperties.init( OutputProperties.java:132) at org.apache.xalan.transformer.TransformerIdentityImpl.init( TransformerIdentityImpl.java:104) at org.apache.xalan.processor.TransformerFactoryImpl.newTransformer( TransformerFactoryImpl.java:842) at com.ideo.sweetdev.data.service.configxml.digester.ConfigXml$ConfigXmlUtil.documentToBytes (ConfigXml.java:506) at com.ideo.sweetdev.data.service.configxml.digester.ConfigXml.unmarshall( ConfigXml.java:355) at com.ideo.sweetdev.data.service.configxml.digester.ConfigXml.init( ConfigXml.java:253) at com.ideo.sweetdev.data.service.configxml.digester.ConfigXml .init(ConfigXml.java:133) at com.ideo.sweetdev.data.service.configxml.digester.ConfigXmlService.getConfigXml (ConfigXmlService.java:138) at com.ideo.sweetdev.data.service.configxml.digester.ConfigXmlService.getConfigXml (ConfigXmlService.java:115) at com.ideo.sweetdev.data.service.configxml.digester.ConfigXmlHelper.getConfigXml (ConfigXmlHelper.java:73) at com.ideo.sweetdev.core.service.ServiceManager.loadServicesDefinition( ServiceManager.java:470) at com.ideo.sweetdev.core.service.ServiceManager.initialize( ServiceManager.java:266) at com.ideo.sweetdev.core.service.ServiceManager.clinit( ServiceManager.java:153) at com.ideo.sweetdev.core.service.broker.BrokerHelper.getBrokerService( BrokerHelper.java:51) at com.ideo.sweetdev.core.service.broker.BrokerHelper.getBroker( BrokerHelper.java:78) at com.ideo.sweetdev.core.service.broker.TestBroker.testServiceCallOk( TestBroker.java:40) 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:324) at junit.framework.TestCase.runTest(TestCase.java:154) at junit.framework.TestCase.runBare(TestCase.java:127) at junit.framework.TestResult$1.protect(TestResult.java:106) at junit.framework.TestResult.runProtected(TestResult.java:124) at junit.framework.TestResult.run(TestResult.java:109) at junit.framework.TestCase.run(TestCase.java:118) at junit.framework.TestSuite.runTest(TestSuite.java:208) at junit.framework.TestSuite.run(TestSuite.java:203) 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:324) at org.apache.maven.surefire.junit.JUnitTestSet.execute( JUnitTestSet.java:213) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.executeTestSet( AbstractDirectoryTestSuite.java:140) at org.apache.maven.surefire.suite.AbstractDirectoryTestSuite.execute( AbstractDirectoryTestSuite.java:165) at org.apache.maven.surefire.Surefire.run(Surefire.java:107) 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:324) at org.apache.maven.surefire.booter.SurefireBooter.runSuitesInProcess( SurefireBooter.java:289) I have the problem with surefire 2.4.2 but it works for 2.3.1 !! Any help are welcome. Thanks Guillaume Boucherie
[ANN] Maven Eclipse Plugin 2.5 Released
The Maven team is pleased to announce the release of the Maven Eclipse
Plugin, version 2.5
This plugin is used to generate Eclipse IDE files (*.classpath,
*.wtpmodules and the .settings folder) for use with a project.
http://maven.apache.org/plugins/maven-eclipse-plugin/
You can run mvn -up to get the latest version of the plugin, or specify
the version in your project's plugin configuration:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-eclipse-plugin/artifactId
version2.5/version
/plugin
In this release we added the support for myeclipse, WTP 2.0 and the
possibility to connect your projects with existing ones in your
workspace.
We also improved the support for rad 6 7 and fixed many bugs.
Thanks a lot for those who helped us by providing patches and/or by
testing our snapshots.
Release Notes - Maven 2.x Eclipse Plugin - Version 2.5
** Bug
* [MECLIPSE-56] - Generated .project-file misses encoding declaration
* [MECLIPSE-102] - sar projects conflict with maven-eclipse-plugin
* [MECLIPSE-107] - Dependency Version Incorrectly Taken from
DependencyManagement
* [MECLIPSE-160] - Wrong description with the goal
add-maven-repo documentation
* [MECLIPSE-172] - Don't add Default ClasspathContainer if a
alternate JRE or a Execution Environment is configured as
ClasspathContainer.
* [MECLIPSE-291] - tests fail with spaces in the path name
* [MECLIPSE-296] - Wrong generated source-path when
warSourceDirectory is set
* [MECLIPSE-297] - eclipse:clean deletes files from pom projects
* [MECLIPSE-301] - eclipse:clean doesn't respect packaging 'pom'
* [MECLIPSE-305] - souce-path is absolute versus relative with WAR
* [MECLIPSE-309] - warSourceDirectory incorrectly resolved inside
a reactor (with a relative path)
* [MECLIPSE-315] - RadWebSettingsWriter uses hardcoded webcontent
path and ignores warSourceDirectory
* [MECLIPSE-316] - RadCleanMojo does not clean .war files
* [MECLIPSE-323] - eclipse:clean does NOT delete 'additionalConfig' files
* [MECLIPSE-332] - mvn-eclipse-cache.properties is never filled
* [MECLIPSE-342] - Found an equals call to check unrelated types
* [MECLIPSE-346] - Transitive dependencies aren't used to resolve
JEE/JSP/EJB/Servlet versions
* [MECLIPSE-352] - RAD application.xml is not generated with good parameters
* [MECLIPSE-356] - RadLibCopier does not respect
warSourceDirectory setting of maven-war-plugin when copying
dependencies
* [MECLIPSE-357] - RadManifestWriter uses hardcoded web
application source directory
* [MECLIPSE-358] - plugin installed via eclipse:install-plugins
have the wrong name
* [MECLIPSE-366] - Test file(s) for Multi-project sample is missing
* [MECLIPSE-367] - Dependency to artifact with classifier tests
not distinguished from the regular artifact
* [MECLIPSE-369] - source status cache not maintained.
* [MECLIPSE-374] - Rename the expression ${eclipse.workspace} to
${eclipse.projectDir} for the parameter eclipseProjectDir in the goal
eclipse:eclipse
* [MECLIPSE-378] - Projects with customized warSourceDirectory
still creates empty directories of the default path
* [MECLIPSE-379] - When downloading sources and javadocs
dependency classifier is not respected.
* [MECLIPSE-390] - myeclipse goal ignores additionalConfig
* [MECLIPSE-399] - URL for javadoc attachments on Unix is invalid
** Improvement
* [MECLIPSE-32] - Allow for forcing the creation of direct project
references for dependencies
* [MECLIPSE-79] - exclude dependencies from the Classpath Container
* [MECLIPSE-120] - Force inter-project dependencies
* [MECLIPSE-152] - Write .classpath with ordered dependencies [incl. Patch]
* [MECLIPSE-163] - eclipe:eclipse 2.3-SNAPSHOT with wtp-1.5 fixes
* [MECLIPSE-213] - more jee support for wtp
* [MECLIPSE-219] - Allow file contents to be obtained from url or location
* [MECLIPSE-256] - [PATCH]Flat Maven2 Multiproject Structures and
Classpath Resolution as Projects (not binaries)
* [MECLIPSE-264] - Support for WTP2.0
* [MECLIPSE-281] - Documentation patch for PDE support
* [MECLIPSE-292] - Behaviour for sources and Javadoc attachement
for dependencies should be consistent
* [MECLIPSE-294] - Sort items in the generated .classpath
* [MECLIPSE-331] - Allow to use a packaging model to override the
packaging defined in the pom
* [MECLIPSE-333] - WTP-2.0 support with howto apt, refactoring and
contextroot handling
* [MECLIPSE-392] - Output is written to src/main/webapp instead of target
** New Feature
* [MECLIPSE-74] - Workspace inspection when adding a project
* [MECLIPSE-127] - Ability to add other workspace configuration
similar to add-maven-repo goal
* [MECLIPSE-158] - Add the ability to selectively treat a
referenced project as a local repository file
* [MECLIPSE-197] - Automatic reference of dependee projects
* [MECLIPSE-260] - Ignore artifact version
Re: Reporting of multi-module project
Martin Höller schrieb: On Saturday 08 March 2008 Ingo Düppe wrote: I like to exclude some of my modules within my multi-module projects from beeing considered by report generating. For instance, I do like to generate a aggregated javadoc report for all jar modules but not of the model - module of andromda. What about using profiles? You can define the modules that shouldn't be considered during site generation in a profile which is only activated when you are not running site generation. hth, - martin thank you martin for the hint. A speciale profile for generating the sites work fine for me. Regards - Ingo - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
enforcer-plugin causes multimodule project to fail
Hi all! I stumbled over a problem with the maven-enforcer-plugin (tested with 1.0-alpha-3 and 1.0-SNAPSHOT): when a new multi-module project is created and the m-enforcer-p is used, maven fails with a Failed to resolve artifact error. This only happens when the new artifacts are not already in any configured repository. I already created a Jira issue for this with a test project attached: http://jira.codehaus.org/browse/MENFORCER-42 Anybody else who has similar problems with the enforcer? btw: according to the SVN repository some people are working on the plugin. Are there any plans to release a new version in the near future? regards, - martin signature.asc Description: This is a digitally signed message part.
Re: [ANN] Maven Eclipse Plugin 2.5 Released
On Tuesday 18 March 2008 Arnaud HERITIER wrote: The Maven team is pleased to announce the release of the Maven Eclipse Plugin, version 2.5 Glad to hear this! I've already been using the latest snapshots, so I don't expect much problems upgrading to 2.5. Anyway, good work so far! Thanks! - martin signature.asc Description: This is a digitally signed message part.
Re: [surefire] problem with xml
On Tuesday 18 March 2008 Guillaume Boucherie wrote: I have the problem with surefire 2.4.2 but it works for 2.3.1 !! Which maven versions? There were some issues with combinations of surefire 2.4.x and maven prior to 2.0.8 as well as with maven 2.0.8 and surefire 2.3.x. Try searching the archive for surefire to get more details. hth, - martin signature.asc Description: This is a digitally signed message part.
Re: Integrating existing project
On Tuesday 18 March 2008 buFka wrote: I am a newbie with Maven. My problem: I want to integrate an already existing project (Webapp) into Maven For general maven questions read one of [0] or [1]. For maven webapp specific questions see the maven-war-plugin [2]. hth, - martin [0] http://www.sonatype.com/book/ [1] http://www.devzuz.com/web/guest/products/resources#BBWM [2] http://maven.apache.org/plugins/maven-war-plugin/ signature.asc Description: This is a digitally signed message part.
Re: pde-maven-plugin calls wrong ant target
Hi Amit, The problem was detected reviously and filed under http://jira.codehaus.org/browse/MOJO-738 I solved the problem as follows: 1. I checked out version 6085 of the trunk of the pde-maven-plugin. I used this specific version because I'm using Eclipse 3.3 with maven 2.0.8 on Windows. 2. I changed zip in EclipsePDEAttachMojo.java to jar 3. I changed the .zip in line 226 of EclipsePDEMojo.java to .jar and line 236 to clean build.update.jar 4. I built the 'damn' thing: mvn clean install 5. I ignored the build error because of test failures 6. I grabbed the class files and updated the pde-maven-plugin jar with these class files. When I build my Eclipse plugin I now have a jar archive installed in my project directory and in the local repository. This is not a proper way of working. To my opinion, building the type of archive should be configurable in the POM, and not fixed in the code as it is now, but at least it's working for me now. One more thing. The PDE plugin may also be used to build an RCP application. The fix I mention here will not work for RCP, but the alpha-2-SNAPSHOT version will. Regards, Jeroen amit kumar-18 wrote: Hi Jeroren, I spent almost a week on avoiding that src.zip in the plugin.zip. I did not find any help on that and ultimately I had to resolve to a workaround which is that I now build a feature(dummy) which includes the plug in I actually want to build. When I get the feature.zip, I find my plug in inside that without src.zip. I know its not something I should have resolved to, but that was the only thing that I could find to fix the src.zip problem. If you find something on how to correct the ant calls, please let me know as well. Thanks and regards, Amit Kumar On Mon, Mar 17, 2008 at 6:40 PM, JeroenL [EMAIL PROTECTED] wrote: Hi all, I'm trying to build an Eclipse plugin with maven. Problems are that 1) the archive is zipped and 2) a directory is added and 3) a sr.zip is added. After investigating the calls to Ant I discovered that maven calls the targets clean build.jars zip.plugin. According my belief this should be clean build.update.jar Does anyone have an idea how to call the proper targets? Regards, Jeroen -- View this message in context: http://www.nabble.com/pde-maven-plugin-calls-wrong-ant-target-tp16092576s177p16092576.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/pde-maven-plugin-calls-wrong-ant-target-tp16092576s177p16119229.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
overwriting external resources
Hi i am pretty new to maven and encountered a problem by overwriting some external resources. I am using maven 2.0.7 and the maven-war-plugin 2.0.2. What I want to do is to overwrite a folder config in the WEB-INF containing some files with an other folder config which is stored in an external resource folder until I build the project. In the end it looks pretty much like this: -src/main/ -Customer/config -web.xml -config.xml -... -webapp/WEB-INF -config/... -web.xml when building the project i want to use profiles to replace the web.xml and the config foilder in the WEB-INF. For replacing the web.xml I am using the webXml property but so far I didn't find a way to overwrite the config folder in the WEB-INF. Any ideas someone?? thx in advance -- Ist Ihr Browser Vista-kompatibel? Jetzt die neuesten Browser-Versionen downloaden: http://www.gmx.net/de/go/browser - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Convert SNAPSHOT timestamps from utc to local time
Hi all, We're having a small problem with deployment: UTC is being used for replacing SNAPSHOT with timestamp. For us, UTC is one hour behind local time. In some days, it will be 2 hours. It's a bit annoying because people are sometimes wondering which snapshot is corresponding to their commit. We'd prefer being able to deploy using local time (at the moment, for example utc is something like 11h47, and our local time is 12h47). I looked at the code and found that the code is in the org.apache.maven.artifact.transform.SnapshotTransformation class. Is there a way to define some global variable (used by the timezone or something like that) to shift generated timestamps? Thanks in advance. Cheers.
Regarding Queries
Hi, how can I send my queries to get it resoved .please provide me the details. -- Regads, Sowmya.R - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Integrating existing project
maybe was the description of my problem not correct (sorry, my english not the best). I'm looking for an HOWTO like this one: http://maven.apache.org/maven-1.x/start/adapting.html but i want to use Maven2 and not the 1.x. the structure of the project should remain exactly as it is now (not definited from Maven). -- View this message in context: http://www.nabble.com/Integrating-existing-project-tp16117612s177p16119610.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [ANN] Maven Eclipse Plugin 2.5 Released
Using mvn eclipse:clean eclipse:eclipse with version 2.5. For example, if
M2_REPO = /path/to/repo executing the command renders build paths for
dependencies for project as
M2_REPO/path/to/repo/commons-collections/commons-collections/3.2/commons-collections-3.2.jar
If I use version 2.4 M2_REPO is referenced properly (i.e.
M2_REPO/commons-collections/commons-collections/3.2/commons-collections-3.2.jar):
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-eclipse-plugin/artifactId
version2.4/version
/plugin
/plugins
/build
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of
Arnaud HERITIER
Sent: Tuesday, March 18, 2008 6:33 AM
To: [EMAIL PROTECTED]; Maven Users List
Cc: Maven Developers List
Subject: [ANN] Maven Eclipse Plugin 2.5 Released
The Maven team is pleased to announce the release of the Maven Eclipse
Plugin, version 2.5
This plugin is used to generate Eclipse IDE files (*.classpath,
*.wtpmodules and the .settings folder) for use with a project.
http://maven.apache.org/plugins/maven-eclipse-plugin/
You can run mvn -up to get the latest version of the plugin, or specify
the version in your project's plugin configuration:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-eclipse-plugin/artifactId
version2.5/version
/plugin
In this release we added the support for myeclipse, WTP 2.0 and the
possibility to connect your projects with existing ones in your
workspace.
We also improved the support for rad 6 7 and fixed many bugs.
Thanks a lot for those who helped us by providing patches and/or by
testing our snapshots.
Release Notes - Maven 2.x Eclipse Plugin - Version 2.5
** Bug
* [MECLIPSE-56] - Generated .project-file misses encoding declaration
* [MECLIPSE-102] - sar projects conflict with maven-eclipse-plugin
* [MECLIPSE-107] - Dependency Version Incorrectly Taken from
DependencyManagement
* [MECLIPSE-160] - Wrong description with the goal
add-maven-repo documentation
* [MECLIPSE-172] - Don't add Default ClasspathContainer if a
alternate JRE or a Execution Environment is configured as
ClasspathContainer.
* [MECLIPSE-291] - tests fail with spaces in the path name
* [MECLIPSE-296] - Wrong generated source-path when
warSourceDirectory is set
* [MECLIPSE-297] - eclipse:clean deletes files from pom projects
* [MECLIPSE-301] - eclipse:clean doesn't respect packaging 'pom'
* [MECLIPSE-305] - souce-path is absolute versus relative with WAR
* [MECLIPSE-309] - warSourceDirectory incorrectly resolved inside
a reactor (with a relative path)
* [MECLIPSE-315] - RadWebSettingsWriter uses hardcoded webcontent
path and ignores warSourceDirectory
* [MECLIPSE-316] - RadCleanMojo does not clean .war files
* [MECLIPSE-323] - eclipse:clean does NOT delete 'additionalConfig' files
* [MECLIPSE-332] - mvn-eclipse-cache.properties is never filled
* [MECLIPSE-342] - Found an equals call to check unrelated types
* [MECLIPSE-346] - Transitive dependencies aren't used to resolve
JEE/JSP/EJB/Servlet versions
* [MECLIPSE-352] - RAD application.xml is not generated with good parameters
* [MECLIPSE-356] - RadLibCopier does not respect
warSourceDirectory setting of maven-war-plugin when copying
dependencies
* [MECLIPSE-357] - RadManifestWriter uses hardcoded web
application source directory
* [MECLIPSE-358] - plugin installed via eclipse:install-plugins
have the wrong name
* [MECLIPSE-366] - Test file(s) for Multi-project sample is missing
* [MECLIPSE-367] - Dependency to artifact with classifier tests
not distinguished from the regular artifact
* [MECLIPSE-369] - source status cache not maintained.
* [MECLIPSE-374] - Rename the expression ${eclipse.workspace} to
${eclipse.projectDir} for the parameter eclipseProjectDir in the goal
eclipse:eclipse
* [MECLIPSE-378] - Projects with customized warSourceDirectory
still creates empty directories of the default path
* [MECLIPSE-379] - When downloading sources and javadocs
dependency classifier is not respected.
* [MECLIPSE-390] - myeclipse goal ignores additionalConfig
* [MECLIPSE-399] - URL for javadoc attachments on Unix is invalid
** Improvement
* [MECLIPSE-32] - Allow for forcing the creation of direct project
references for dependencies
* [MECLIPSE-79] - exclude dependencies from the Classpath Container
* [MECLIPSE-120] - Force inter-project dependencies
* [MECLIPSE-152] - Write .classpath with ordered dependencies [incl. Patch]
* [MECLIPSE-163] - eclipe:eclipse 2.3-SNAPSHOT with wtp-1.5 fixes
* [MECLIPSE-213] - more jee support for wtp
* [MECLIPSE-219] - Allow file contents to be obtained from url or location
* [MECLIPSE-256] - [PATCH]Flat Maven2 Multiproject
Re: Integrating existing project
On Tuesday 18 March 2008 buFka wrote: maybe was the description of my problem not correct (sorry, my english not the best). I'm looking for an HOWTO like this one: http://maven.apache.org/maven-1.x/start/adapting.html but i want to use Maven2 and not the 1.x. the structure of the project should remain exactly as it is now (not definited from Maven). I don't know of a step-by-step howto for migrating an existing webapplication to a maven2 project, but did you even have a look at the links Iprovided? Following the first one brings me to http://www.sonatype.com/book/reference/web.html which explains webapplications and maven pretty good. - martin signature.asc Description: This is a digitally signed message part.
RE: [ANN] Maven Eclipse Plugin 2.5 Released
+1. Same problem here. Just saw the behaviour some minutes ago.
Precision: I'm not using the default repository location, this might a cause of
this problem.
Do you want someone to log a bug in the tracker, Arnaud?
Cheers.
-Message d'origine-
De : Hoover, William [mailto:[EMAIL PROTECTED]
Envoyé : mardi 18 mars 2008 13:11
À : Maven Users List
Cc : Maven Developers List
Objet : RE: [ANN] Maven Eclipse Plugin 2.5 Released
Using mvn eclipse:clean eclipse:eclipse with version 2.5. For example, if
M2_REPO = /path/to/repo executing the command renders build paths for
dependencies for project as
M2_REPO/path/to/repo/commons-collections/commons-collections/3.2/commons-collections-3.2.jar
If I use version 2.4 M2_REPO is referenced properly (i.e.
M2_REPO/commons-collections/commons-collections/3.2/commons-collections-3.2.jar):
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-eclipse-plugin/artifactId
version2.4/version
/plugin
/plugins
/build
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Arnaud HERITIER
Sent: Tuesday, March 18, 2008 6:33 AM
To: [EMAIL PROTECTED]; Maven Users List
Cc: Maven Developers List
Subject: [ANN] Maven Eclipse Plugin 2.5 Released
The Maven team is pleased to announce the release of the Maven Eclipse Plugin,
version 2.5
This plugin is used to generate Eclipse IDE files (*.classpath, *.wtpmodules
and the .settings folder) for use with a project.
http://maven.apache.org/plugins/maven-eclipse-plugin/
You can run mvn -up to get the latest version of the plugin, or specify the
version in your project's plugin configuration:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-eclipse-plugin/artifactId
version2.5/version
/plugin
In this release we added the support for myeclipse, WTP 2.0 and the possibility
to connect your projects with existing ones in your workspace.
We also improved the support for rad 6 7 and fixed many bugs.
Thanks a lot for those who helped us by providing patches and/or by testing our
snapshots.
Release Notes - Maven 2.x Eclipse Plugin - Version 2.5
** Bug
* [MECLIPSE-56] - Generated .project-file misses encoding declaration
* [MECLIPSE-102] - sar projects conflict with maven-eclipse-plugin
* [MECLIPSE-107] - Dependency Version Incorrectly Taken from
DependencyManagement
* [MECLIPSE-160] - Wrong description with the goal add-maven-repo
documentation
* [MECLIPSE-172] - Don't add Default ClasspathContainer if a alternate JRE
or a Execution Environment is configured as ClasspathContainer.
* [MECLIPSE-291] - tests fail with spaces in the path name
* [MECLIPSE-296] - Wrong generated source-path when warSourceDirectory is
set
* [MECLIPSE-297] - eclipse:clean deletes files from pom projects
* [MECLIPSE-301] - eclipse:clean doesn't respect packaging 'pom'
* [MECLIPSE-305] - souce-path is absolute versus relative with WAR
* [MECLIPSE-309] - warSourceDirectory incorrectly resolved inside a reactor
(with a relative path)
* [MECLIPSE-315] - RadWebSettingsWriter uses hardcoded webcontent path and
ignores warSourceDirectory
* [MECLIPSE-316] - RadCleanMojo does not clean .war files
* [MECLIPSE-323] - eclipse:clean does NOT delete 'additionalConfig' files
* [MECLIPSE-332] - mvn-eclipse-cache.properties is never filled
* [MECLIPSE-342] - Found an equals call to check unrelated types
* [MECLIPSE-346] - Transitive dependencies aren't used to resolve
JEE/JSP/EJB/Servlet versions
* [MECLIPSE-352] - RAD application.xml is not generated with good parameters
* [MECLIPSE-356] - RadLibCopier does not respect warSourceDirectory setting
of maven-war-plugin when copying dependencies
* [MECLIPSE-357] - RadManifestWriter uses hardcoded web application source
directory
* [MECLIPSE-358] - plugin installed via eclipse:install-plugins have the
wrong name
* [MECLIPSE-366] - Test file(s) for Multi-project sample is missing
* [MECLIPSE-367] - Dependency to artifact with classifier tests not
distinguished from the regular artifact
* [MECLIPSE-369] - source status cache not maintained.
* [MECLIPSE-374] - Rename the expression ${eclipse.workspace} to
${eclipse.projectDir} for the parameter eclipseProjectDir in the goal
eclipse:eclipse
* [MECLIPSE-378] - Projects with customized warSourceDirectory still
creates empty directories of the default path
* [MECLIPSE-379] - When downloading sources and javadocs dependency
classifier is not respected.
* [MECLIPSE-390] - myeclipse goal ignores additionalConfig
* [MECLIPSE-399] - URL for javadoc attachments on Unix is invalid
** Improvement
* [MECLIPSE-32] - Allow for forcing the creation of direct project
references for dependencies
Binding goals to POM's default life cycle
Hi, I developed a plugin with a Mojo that is being executed manually. mvn myPlugin:my-goal The Mojo has the following annotation: @execute phase=compile The Mojo is invoked from the directory of the master project in a multi module project. According to the documentation I expect that before the Mojo is invoked the project will compile. But instead I get the message: No goals needed for project - skipping I guess it's because by default no goals are bound to the lifecycle of the pom project. How can I bind goals to the default lifecycle of pom? In other words, I want the multi module project to compile the submodules before invoking the Mojo. Can I define a different lifecycle for pom (using plexus for example)? Thanks, Shai -- View this message in context: http://www.nabble.com/Binding-goals-to-POM%27s-default-life-cycle-tp16119966s177p16119966.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
how to checkout the Project from cvs using Maven2.0.7
Hi, I am using maven to checkout the project from cvs.I want to checkout from CVS, for that i want it should ask for CVS user id and password from the user in command line to connect to cvs for checkout. And I also want to do the checkout for the different projects module that are present in cvs just by giving the name of the module. Provide me the commands to do these tasks. Please solve these issues and provide me the details for how to do this. Thanks in advance :) Regards, sowmya - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [ANN] Maven Eclipse Plugin 2.5 Released
I'm not using the default repository location either. I think you may be right-
it may have something to do with that.
-Original Message-
From: MATHUS Baptiste [mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 18, 2008 8:29 AM
To: Maven Users List
Subject: RE: [ANN] Maven Eclipse Plugin 2.5 Released
+1. Same problem here. Just saw the behaviour some minutes ago.
Precision: I'm not using the default repository location, this might a cause of
this problem.
Do you want someone to log a bug in the tracker, Arnaud?
Cheers.
-Message d'origine-
De : Hoover, William [mailto:[EMAIL PROTECTED]
Envoyé : mardi 18 mars 2008 13:11
À : Maven Users List
Cc : Maven Developers List
Objet : RE: [ANN] Maven Eclipse Plugin 2.5 Released
Using mvn eclipse:clean eclipse:eclipse with version 2.5. For example, if
M2_REPO = /path/to/repo executing the command renders build paths for
dependencies for project as
M2_REPO/path/to/repo/commons-collections/commons-collections/3.2/commons-collections-3.2.jar
If I use version 2.4 M2_REPO is referenced properly (i.e.
M2_REPO/commons-collections/commons-collections/3.2/commons-collections-3.2.jar):
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-eclipse-plugin/artifactId
version2.4/version
/plugin
/plugins
/build
-Original Message-
From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Arnaud HERITIER
Sent: Tuesday, March 18, 2008 6:33 AM
To: [EMAIL PROTECTED]; Maven Users List
Cc: Maven Developers List
Subject: [ANN] Maven Eclipse Plugin 2.5 Released
The Maven team is pleased to announce the release of the Maven Eclipse Plugin,
version 2.5
This plugin is used to generate Eclipse IDE files (*.classpath, *.wtpmodules
and the .settings folder) for use with a project.
http://maven.apache.org/plugins/maven-eclipse-plugin/
You can run mvn -up to get the latest version of the plugin, or specify the
version in your project's plugin configuration:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-eclipse-plugin/artifactId
version2.5/version
/plugin
In this release we added the support for myeclipse, WTP 2.0 and the possibility
to connect your projects with existing ones in your workspace.
We also improved the support for rad 6 7 and fixed many bugs.
Thanks a lot for those who helped us by providing patches and/or by testing our
snapshots.
Release Notes - Maven 2.x Eclipse Plugin - Version 2.5
** Bug
* [MECLIPSE-56] - Generated .project-file misses encoding declaration
* [MECLIPSE-102] - sar projects conflict with maven-eclipse-plugin
* [MECLIPSE-107] - Dependency Version Incorrectly Taken from
DependencyManagement
* [MECLIPSE-160] - Wrong description with the goal add-maven-repo
documentation
* [MECLIPSE-172] - Don't add Default ClasspathContainer if a alternate JRE
or a Execution Environment is configured as ClasspathContainer.
* [MECLIPSE-291] - tests fail with spaces in the path name
* [MECLIPSE-296] - Wrong generated source-path when warSourceDirectory is
set
* [MECLIPSE-297] - eclipse:clean deletes files from pom projects
* [MECLIPSE-301] - eclipse:clean doesn't respect packaging 'pom'
* [MECLIPSE-305] - souce-path is absolute versus relative with WAR
* [MECLIPSE-309] - warSourceDirectory incorrectly resolved inside a reactor
(with a relative path)
* [MECLIPSE-315] - RadWebSettingsWriter uses hardcoded webcontent path and
ignores warSourceDirectory
* [MECLIPSE-316] - RadCleanMojo does not clean .war files
* [MECLIPSE-323] - eclipse:clean does NOT delete 'additionalConfig' files
* [MECLIPSE-332] - mvn-eclipse-cache.properties is never filled
* [MECLIPSE-342] - Found an equals call to check unrelated types
* [MECLIPSE-346] - Transitive dependencies aren't used to resolve
JEE/JSP/EJB/Servlet versions
* [MECLIPSE-352] - RAD application.xml is not generated with good parameters
* [MECLIPSE-356] - RadLibCopier does not respect warSourceDirectory setting
of maven-war-plugin when copying dependencies
* [MECLIPSE-357] - RadManifestWriter uses hardcoded web application source
directory
* [MECLIPSE-358] - plugin installed via eclipse:install-plugins have the
wrong name
* [MECLIPSE-366] - Test file(s) for Multi-project sample is missing
* [MECLIPSE-367] - Dependency to artifact with classifier tests not
distinguished from the regular artifact
* [MECLIPSE-369] - source status cache not maintained.
* [MECLIPSE-374] - Rename the expression ${eclipse.workspace} to
${eclipse.projectDir} for the parameter eclipseProjectDir in the goal
eclipse:eclipse
* [MECLIPSE-378] - Projects with customized warSourceDirectory still
creates empty directories of the default path
* [MECLIPSE-379] - When downloading
Re: overwriting external resources
En l'instant précis du 18/03/08 12:43, Dominik Heller s'exprimait en ces
termes:
Hi i am pretty new to maven and encountered a problem by overwriting some
external resources. I am using maven 2.0.7 and the maven-war-plugin 2.0.2. What
I want to do is to overwrite a folder config in the WEB-INF containing some
files with an other folder config which is stored in an external resource
folder until I build the project.
In the end it looks pretty much like this:
-src/main/
-Customer/config
-web.xml
-config.xml
-...
-webapp/WEB-INF
-config/...
-web.xml
when building the project i want to use profiles to replace the web.xml and the
config foilder in the WEB-INF. For replacing the web.xml I am using the
webXml property but so far I didn't find a way to overwrite the config folder
in the WEB-INF.
Any ideas someone??
thx in advance
Hi, we had similar requirement here. Here is our solution:
in build plugins:
plugin
artifactIdmaven-war-plugin/artifactId
configuration
warSourceDirectorywebapp/warSourceDirectory
webResources
resource
!-- this is relative to the pom.xml directory --
directoryconfigSets/${config.configSet}/directory
/resource
/webResources
/configuration
/plugin
in profiles:
profile
iduser-x/id
activation
property
nameuser/name
valuex/value
/property
/activation
properties
config.configSetuserX/config.configSet
/properties
/profile
We make our package using
mvn package -Duser=x
and it will override, in war, existing files with those found in
configSets/userX/
--
David Delbecq
Institut Royal Météorologique
Ext:557
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [surefire] problem with xml
I try with version 2.0.7 and 2.0.8. I have the same error. I'm on windows with jdk1.6.0. My project is compiled with a jdk1.4.2 and my test is run with the same jdk. Guillaume Boucherie 2008/3/18, Martin Höller [EMAIL PROTECTED]: On Tuesday 18 March 2008 Guillaume Boucherie wrote: I have the problem with surefire 2.4.2 but it works for 2.3.1 !! Which maven versions? There were some issues with combinations of surefire 2.4.x and maven prior to 2.0.8 as well as with maven 2.0.8 and surefire 2.3.x. Try searching the archive for surefire to get more details. hth, - martin
Re: [ANN] Maven Eclipse Plugin 2.5 Released
yes please open a bug. I don't use the standard location and didn't notice it. If I can reproduce it, I'll publish a version 2.5.1 in few days. cheers. On Tue, Mar 18, 2008 at 1:56 PM, Hoover, William [EMAIL PROTECTED] wrote: I'm not using the default repository location either. I think you may be right- it may have something to do with that. -Original Message- From: MATHUS Baptiste [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2008 8:29 AM To: Maven Users List Subject: RE: [ANN] Maven Eclipse Plugin 2.5 Released +1. Same problem here. Just saw the behaviour some minutes ago. Precision: I'm not using the default repository location, this might a cause of this problem. Do you want someone to log a bug in the tracker, Arnaud? Cheers. -Message d'origine- De : Hoover, William [mailto:[EMAIL PROTECTED] Envoyé : mardi 18 mars 2008 13:11 À : Maven Users List Cc : Maven Developers List Objet : RE: [ANN] Maven Eclipse Plugin 2.5 Released Using mvn eclipse:clean eclipse:eclipse with version 2.5. For example, if M2_REPO = /path/to/repo executing the command renders build paths for dependencies for project as M2_REPO/path/to/repo/commons-collections/commons-collections/3.2/commons-collections-3.2.jar If I use version 2.4 M2_REPO is referenced properly (i.e. M2_REPO/commons-collections/commons-collections/3.2/commons-collections-3.2.jar): build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-eclipse-plugin/artifactId version2.4/version /plugin /plugins /build -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Arnaud HERITIER Sent: Tuesday, March 18, 2008 6:33 AM To: [EMAIL PROTECTED]; Maven Users List Cc: Maven Developers List Subject: [ANN] Maven Eclipse Plugin 2.5 Released The Maven team is pleased to announce the release of the Maven Eclipse Plugin, version 2.5 This plugin is used to generate Eclipse IDE files (*.classpath, *.wtpmodules and the .settings folder) for use with a project. http://maven.apache.org/plugins/maven-eclipse-plugin/ You can run mvn -up to get the latest version of the plugin, or specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-eclipse-plugin/artifactId version2.5/version /plugin In this release we added the support for myeclipse, WTP 2.0 and the possibility to connect your projects with existing ones in your workspace. We also improved the support for rad 6 7 and fixed many bugs. Thanks a lot for those who helped us by providing patches and/or by testing our snapshots. Release Notes - Maven 2.x Eclipse Plugin - Version 2.5 ** Bug * [MECLIPSE-56] - Generated .project-file misses encoding declaration * [MECLIPSE-102] - sar projects conflict with maven-eclipse-plugin * [MECLIPSE-107] - Dependency Version Incorrectly Taken from DependencyManagement * [MECLIPSE-160] - Wrong description with the goal add-maven-repo documentation * [MECLIPSE-172] - Don't add Default ClasspathContainer if a alternate JRE or a Execution Environment is configured as ClasspathContainer. * [MECLIPSE-291] - tests fail with spaces in the path name * [MECLIPSE-296] - Wrong generated source-path when warSourceDirectory is set * [MECLIPSE-297] - eclipse:clean deletes files from pom projects * [MECLIPSE-301] - eclipse:clean doesn't respect packaging 'pom' * [MECLIPSE-305] - souce-path is absolute versus relative with WAR * [MECLIPSE-309] - warSourceDirectory incorrectly resolved inside a reactor (with a relative path) * [MECLIPSE-315] - RadWebSettingsWriter uses hardcoded webcontent path and ignores warSourceDirectory * [MECLIPSE-316] - RadCleanMojo does not clean .war files * [MECLIPSE-323] - eclipse:clean does NOT delete 'additionalConfig' files * [MECLIPSE-332] - mvn-eclipse-cache.properties is never filled * [MECLIPSE-342] - Found an equals call to check unrelated types * [MECLIPSE-346] - Transitive dependencies aren't used to resolve JEE/JSP/EJB/Servlet versions * [MECLIPSE-352] - RAD application.xml is not generated with good parameters * [MECLIPSE-356] - RadLibCopier does not respect warSourceDirectory setting of maven-war-plugin when copying dependencies * [MECLIPSE-357] - RadManifestWriter uses hardcoded web application source directory * [MECLIPSE-358] - plugin installed via eclipse:install-plugins have the wrong name * [MECLIPSE-366] - Test file(s) for Multi-project sample is missing * [MECLIPSE-367] - Dependency to artifact with classifier tests not distinguished from the regular artifact * [MECLIPSE-369]
Re: overwriting external resources
Hi David,
well first of all thanks so much for yours quick response. I have tried your
code and it works fine for me. it seems that the
warSourceDirectorywebapp/warSourceDirectory is dealing with the timestamps
of the files correctly although I thought that the webapp would be the default
webSourceDirectory. If the webSourceDirectory is not explicitly specified the
file in the config folder of the WEb-Inf folder won't be overwriten if it has a
newer timestamp than the file it should be overwritten with. Anyways thanks for
your help I really appreciate it.
Original-Nachricht
Datum: Tue, 18 Mar 2008 13:53:47 +0100
Von: David Delbecq [EMAIL PROTECTED]
An: Maven Users List users@maven.apache.org
Betreff: Re: overwriting external resources
En l'instant précis du 18/03/08 12:43, Dominik Heller s'exprimait en ces
termes:
Hi i am pretty new to maven and encountered a problem by overwriting
some external resources. I am using maven 2.0.7 and the maven-war-plugin
2.0.2. What I want to do is to overwrite a folder config in the WEB-INF
containing some files with an other folder config which is stored in an
external
resource folder until I build the project.
In the end it looks pretty much like this:
-src/main/
-Customer/config
-web.xml
-config.xml
-...
-webapp/WEB-INF
-config/...
-web.xml
when building the project i want to use profiles to replace the web.xml
and the config foilder in the WEB-INF. For replacing the web.xml I am using
the webXml property but so far I didn't find a way to overwrite the
config folder in the WEB-INF.
Any ideas someone??
thx in advance
Hi, we had similar requirement here. Here is our solution:
in build plugins:
plugin
artifactIdmaven-war-plugin/artifactId
configuration
warSourceDirectorywebapp/warSourceDirectory
webResources
resource
!-- this is relative to the pom.xml directory --
directoryconfigSets/${config.configSet}/directory
/resource
/webResources
/configuration
/plugin
in profiles:
profile
iduser-x/id
activation
property
nameuser/name
valuex/value
/property
/activation
properties
config.configSetuserX/config.configSet
/properties
/profile
We make our package using
mvn package -Duser=x
and it will override, in war, existing files with those found in
configSets/userX/
--
David Delbecq
Institut Royal Météorologique
Ext:557
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Pt! Schon vom neuen GMX MultiMessenger gehört?
Der kann`s mit allen: http://www.gmx.net/de/go/multimessenger
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Customizing Build order
Oh Okay. Yes simon you are right. Thanks for the advise. Regards, Amit On Tue, Mar 18, 2008 at 3:46 PM, David Delbecq [EMAIL PROTECTED] wrote: En l'instant précis du 18/03/08 09:42, amit kumar s'exprimait en ces termes: Hi, I have a multi-module project with the following structure. Root -A -A1 -A2 -A3 -B -B1 -B2 -B3 -B4 In the Root's pom i have mentioned my modules as: moduleA/module moduleB/module Now is there a way that I can change the normal build order(which is) -Root -A -A1 -A2 -A3 -B -B1 -B2 -B3 -B4 to something like -Root -A -A1 -A2 -B -B1 -B2 -A3 -B4 It is actually a requirement. But I doubt that there is a possibility that the CVS structure itself is not competent enough then to handle inter-module dependencies. Any inputs? Thanks and regards, Amit Kumar In the A3 project, add dependencies that point to all other projects you need to have compiled before (i suspect you need B2 resources for A3?), maven should order them properly. -- David Delbecq Institut Royal Météorologique Ext:557 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Maven Eclipse Plugin 2.5 Released
I also use a custom local repository location and get the expected M2_REPO/commons-logging in my .classpath. Nico 2008/3/18, Arnaud HERITIER [EMAIL PROTECTED]: yes please open a bug. I don't use the standard location and didn't notice it. If I can reproduce it, I'll publish a version 2.5.1 in few days. cheers. On Tue, Mar 18, 2008 at 1:56 PM, Hoover, William [EMAIL PROTECTED] wrote: I'm not using the default repository location either. I think you may be right- it may have something to do with that. -Original Message- From: MATHUS Baptiste [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2008 8:29 AM To: Maven Users List Subject: RE: [ANN] Maven Eclipse Plugin 2.5 Released +1. Same problem here. Just saw the behaviour some minutes ago. Precision: I'm not using the default repository location, this might a cause of this problem. Do you want someone to log a bug in the tracker, Arnaud? Cheers. -Message d'origine- De : Hoover, William [mailto:[EMAIL PROTECTED] Envoyé : mardi 18 mars 2008 13:11 À : Maven Users List Cc : Maven Developers List Objet : RE: [ANN] Maven Eclipse Plugin 2.5 Released Using mvn eclipse:clean eclipse:eclipse with version 2.5. For example, if M2_REPO = /path/to/repo executing the command renders build paths for dependencies for project as M2_REPO/path/to/repo/commons-collections/commons-collections/3.2/commons- collections-3.2.jar If I use version 2.4 M2_REPO is referenced properly (i.e. M2_REPO/commons-collections/commons-collections/3.2/commons- collections-3.2.jar): build plugins plugin groupIdorg.apache.maven.plugins /groupId artifactIdmaven-eclipse-plugin/artifactId version2.4/version /plugin /plugins /build -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Arnaud HERITIER Sent: Tuesday, March 18, 2008 6:33 AM To: [EMAIL PROTECTED]; Maven Users List Cc: Maven Developers List Subject: [ANN] Maven Eclipse Plugin 2.5 Released The Maven team is pleased to announce the release of the Maven Eclipse Plugin, version 2.5 This plugin is used to generate Eclipse IDE files (*.classpath, *.wtpmodules and the .settings folder) for use with a project. http://maven.apache.org/plugins/maven-eclipse-plugin/ You can run mvn -up to get the latest version of the plugin, or specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-eclipse-plugin/artifactId version2.5/version /plugin In this release we added the support for myeclipse, WTP 2.0 and the possibility to connect your projects with existing ones in your workspace. We also improved the support for rad 6 7 and fixed many bugs. Thanks a lot for those who helped us by providing patches and/or by testing our snapshots. Release Notes - Maven 2.x Eclipse Plugin - Version 2.5 ** Bug * [MECLIPSE-56] - Generated .project-file misses encoding declaration * [MECLIPSE-102] - sar projects conflict with maven-eclipse-plugin * [MECLIPSE-107] - Dependency Version Incorrectly Taken from DependencyManagement * [MECLIPSE-160] - Wrong description with the goal add-maven-repo documentation * [MECLIPSE-172] - Don't add Default ClasspathContainer if a alternate JRE or a Execution Environment is configured as ClasspathContainer. * [MECLIPSE-291] - tests fail with spaces in the path name * [MECLIPSE-296] - Wrong generated source-path when warSourceDirectory is set * [MECLIPSE-297] - eclipse:clean deletes files from pom projects * [MECLIPSE-301] - eclipse:clean doesn't respect packaging 'pom' * [MECLIPSE-305] - souce-path is absolute versus relative with WAR * [MECLIPSE-309] - warSourceDirectory incorrectly resolved inside a reactor (with a relative path) * [MECLIPSE-315] - RadWebSettingsWriter uses hardcoded webcontent path and ignores warSourceDirectory * [MECLIPSE-316] - RadCleanMojo does not clean .war files * [MECLIPSE-323] - eclipse:clean does NOT delete 'additionalConfig' files * [MECLIPSE-332] - mvn-eclipse-cache.properties is never filled * [MECLIPSE-342] - Found an equals call to check unrelated types * [MECLIPSE-346] - Transitive dependencies aren't used to resolve JEE/JSP/EJB/Servlet versions * [MECLIPSE-352] - RAD application.xml is not generated with good parameters * [MECLIPSE-356] - RadLibCopier does not respect warSourceDirectory setting of maven-war-plugin when copying dependencies * [MECLIPSE-357] - RadManifestWriter uses hardcoded web application source directory * [MECLIPSE-358] - plugin installed via eclipse:install-plugins have the wrong
Re: Regarding Queries
What exactly is your question? Just go ahead and ask it, and if someone knows the answer or wants to help, they will reply. It is better to include MORE information than LESS. Wayne On 3/18/08, Sowmya. R [EMAIL PROTECTED] wrote: Hi, how can I send my queries to get it resoved .please provide me the details. -- Regads, Sowmya.R - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: AspectJ and M2Eclipse
This is a general problem with any eclipse integration that manages its own classpath container. This is something we're trying to work on with other groups at Eclipse. We're at EclipseCon this week and so we're trying to figure out how this might best work. On 17-Mar-08, at 6:23 AM, Felipe Kamakura wrote: Greetings! I have a problem concerning AJDT and the M2Eclipse plugin I hope someone can help me with that. I have to include a .JAR in my AspectJ Build Path, but M2Eclipse won't let me. Everytime I include a library in the AspectJ Build Path it is automatically excluded. I think that's because M2Eclipse groups all libraries in a Container: classpathentry kind=con path= org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER/ I've tried changing manually the .classpath file, including the dependency like this: classpathentry kind=var path=M2_REPO/br/com/touchtec/version/version/1.0/version-1.0.jar attributes attribute name=org.eclipse.ajdt.aspectpath value=true/ /attributes /classpathenty But Eclipse will give me an error for duplicated build path entry, because the version-1.0.jar already exists in the M2Eclipse Container. Is there a way to suppress this error? Or better, is there a way to include a Maven dependency in the AspectJ Build Path?? Thanks! Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- What matters is not ideas, but the people who have them. Good people can fix bad ideas, but good ideas can't save bad people. -- Paul Graham - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Convert SNAPSHOT timestamps from utc to local time
Not that I'm aware of, at least, not today. If you really must have this feature, you could add a configuration and hack the code, but as with any user-provided patch, there's no guarantee it would be accepted into the core if you contributed it via Jira. Maven uses UTC on purpose so that timestamps are gloabally unique and incrementing. Then when I'm working in CA and the rest of my team is in NJ, and we're both deploying to the same corporate repo, my 11am (PT) builds are properly considered newer than your 1pm (ET) builds. If you're all in the same timezone, this seems like less of a problem, but how common is that in today's corporate climate? I know my small team of 5 people is in 3 timezones. Wayne On 3/18/08, MATHUS Baptiste [EMAIL PROTECTED] wrote: Hi all, We're having a small problem with deployment: UTC is being used for replacing SNAPSHOT with timestamp. For us, UTC is one hour behind local time. In some days, it will be 2 hours. It's a bit annoying because people are sometimes wondering which snapshot is corresponding to their commit. We'd prefer being able to deploy using local time (at the moment, for example utc is something like 11h47, and our local time is 12h47). I looked at the code and found that the code is in the org.apache.maven.artifact.transform.SnapshotTransformation class. Is there a way to define some global variable (used by the timezone or something like that) to shift generated timestamps? Thanks in advance. Cheers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Archetype using artifactId for package name
I would like to create an archetype of a Java project where the package name
of the Java files is predicated on the artifactId specified when
archetype:create is invoked.
IOW, the archetype-resources directory needs to look something like this:
archetype-resources
|
`--src
|
`--main
|
`--java
|
`--com
|
`--acme
|
`--${artifactId}
Needless to say, this does not work. I have even tried ${packageName}. The
attendant question is, how do I refer to these files in the archetype.xml
file?
Thanks
Sri
--
View this message in context:
http://www.nabble.com/Archetype-using-artifactId-for-package-name-tp16124185s177p16124185.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [surefire] problem with xml
I'm find that the error only appends with jdk1.4 But my project must be compiled and test with jdk1.4 So I can I use the latest version of surefire plugin without problem. I'm trying to search surefire related thread in archive but I don't see interesting thing. Can anyone help me ? Guillaume Boucherie 2008/3/18, Guillaume Boucherie [EMAIL PROTECTED]: I try with version 2.0.7 and 2.0.8. I have the same error. I'm on windows with jdk1.6.0. My project is compiled with a jdk1.4.2 and my test is run with the same jdk. Guillaume Boucherie 2008/3/18, Martin Höller [EMAIL PROTECTED]: On Tuesday 18 March 2008 Guillaume Boucherie wrote: I have the problem with surefire 2.4.2 but it works for 2.3.1 !! Which maven versions? There were some issues with combinations of surefire 2.4.x and maven prior to 2.0.8 as well as with maven 2.0.8 and surefire 2.3.x. Try searching the archive for surefire to get more details. hth, - martin
Problems to include test-jar in the classpath
Hello, When I try to create a test-jar that depends of another test-jar I cant include this second test-jar in the first. I put the second test-jar in the pom.xml of the first as typetest-jar/typescopetest/scope but the manifest built by maven do not include this jar (of course in the manifest appear all the others ¡ars needed). Im starting to work with maven, I appreciate your help and your time. Regards,
RE: Convert SNAPSHOT timestamps from utc to local time
My company is french, we sell to frenchies and have almost no chance to ever sell to another country ;). In fact, we work in the healthcare area and there's lots and lots of administrative rules that even make it difficult to follow only for the french market :-). So, I'll hack the code and propose a patch with some additional parameter to tune this behaviour, hoping it finds a way into the trunk one day. Cheers. -Message d'origine- De : Wayne Fay [mailto:[EMAIL PROTECTED] Envoyé : mardi 18 mars 2008 16:32 À : Maven Users List Objet : Re: Convert SNAPSHOT timestamps from utc to local time Not that I'm aware of, at least, not today. If you really must have this feature, you could add a configuration and hack the code, but as with any user-provided patch, there's no guarantee it would be accepted into the core if you contributed it via Jira. Maven uses UTC on purpose so that timestamps are gloabally unique and incrementing. Then when I'm working in CA and the rest of my team is in NJ, and we're both deploying to the same corporate repo, my 11am (PT) builds are properly considered newer than your 1pm (ET) builds. If you're all in the same timezone, this seems like less of a problem, but how common is that in today's corporate climate? I know my small team of 5 people is in 3 timezones. Wayne On 3/18/08, MATHUS Baptiste [EMAIL PROTECTED] wrote: Hi all, We're having a small problem with deployment: UTC is being used for replacing SNAPSHOT with timestamp. For us, UTC is one hour behind local time. In some days, it will be 2 hours. It's a bit annoying because people are sometimes wondering which snapshot is corresponding to their commit. We'd prefer being able to deploy using local time (at the moment, for example utc is something like 11h47, and our local time is 12h47). I looked at the code and found that the code is in the org.apache.maven.artifact.transform.SnapshotTransformation class. Is there a way to define some global variable (used by the timezone or something like that) to shift generated timestamps? Thanks in advance. Cheers. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Copy:unpack
This plugin should either be altered to process other files OR be
renamed to velocity-file-processor.
It's very confusing and in this case a massive time sink, trying to
learn the particulars of a plugin that in the end didn't suit our
purposes.
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Sunday, March 16, 2008 1:10 PM
To: users@maven.apache.org
Cc: EJ Ciramella
Subject: Re: Copy:unpack
On Sunday 16 March 2008, EJ Ciramella wrote:
Hmmm - maybe there's a disconnect then. I think this plugin
perfectly suits my needs (if it worked or was better documented).
What I need:
1 - pull down a dependency
2 - extract said dependency outside of the target directory (or to
some other settings.xml specified location).
Right. But remote-resources will then add that directory to the build
such that any subsequent jar call will pick them up anyway.
remote-resources is designed to make everything it outputs get sucked
into the jars. The jar jar, the sources jar, the test jar, the
javadoc jar, etc Thus, you might as well just use
dependency:unpack to unpack to a resources dir that then gets filtered.
3 - process a list of files on the way out.
remote-resources only processes files ending in .vm (and it strips
the .vm off). Basically, they are just treated as velocity templates
and fed into velocity. Anything else is just copied directly, no
processing.
Also, the properties that are fed into the velocity context are NOT
the
entire list of of project properties. (although you might be able to
do ${project.properties.get('...')} or similar) Generally, the stuff
that is filtered in is configured on the plugin itself.This is
pretty much as designed cause when you are dealing with legal junk like
the NOTICE files and stuff, you REALLY need complete control over what
is happening.
Dan
-Original Message-
From: Daniel Kulp [mailto:[EMAIL PROTECTED]
Sent: Sat 3/15/2008 1:01 PM
To: users@maven.apache.org
Cc: EJ Ciramella
Subject: Re: Copy:unpack
My gut feeling is that remote-resources is NOT the plugin to be used
for this. remote-resources will only process specific files in the
bundle and only if the bundle is properly created with the
remote-resources:bundle goal. It also only fills in
properties/values that are specifically set in the plugins
configuration, not everything in the pom. remote-resources targets a
specific need, and this really doesn't sound like it.
Most likely, you should add a feature request to the dependency plugin
to allow filtering of stuff that is unpacked. I think a new filtering
component was created recently that could make it pretty easy to do.
Not really sure though.
Dan
On Saturday 15 March 2008, EJ Ciramella wrote:
Well these questions are directed at the entire mailing list.
I do appreciate all the energy you've put into this.
We started work on a series of plugins because of how little is
known about this particular one (can I submit changes to the
documentation that helped me?), but I'd hate to manage a plugin that
is pretty much a duplicate of what is offered out of the box (but we
just can't figure out how to use it).
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Fri 3/14/2008 8:54 PM
To: Maven Users List
Subject: RE: Copy:unpack
The maven build is using it, as are lots of other builds at apache
to handle the NOTICE and LICENSE files, so I know it works a little
bit...but alas I haven't actually used it to filter anything myself.
-Original Message-
From: EJ Ciramella [mailto:[EMAIL PROTECTED]
Sent: Friday, March 14, 2008 8:41 PM
To: Maven Users List
Subject: RE: Copy:unpack
Done:
http://jira.codehaus.org/browse/MRRESOURCES-33
No suggestions or pointers on getting this bugger working? I could
live with the duplicated version number. What I can't deal with is
this NOT processing resources like it says it's supposed to.
When run with -X -e, btw, the output shows the resources like this:
(f) resources = [EMAIL PROTECTED],
[EMAIL PROTECTED]
I'm guessing this could have been something more like
resources.getName() or getPath() or something. Not the memory
address or w/e...
-Original Message-
From: Brian E. Fox [mailto:[EMAIL PROTECTED]
Sent: Friday, March 14, 2008 8:17 PM
To: Maven Users List
Subject: RE: Copy:unpack
2 - verified that I can pull it down (still not thrilled about
listing version twice in the same pom). The plugin should look up
the version like dependency:unpack
Can you file a jira?
- To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
- To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional
Profiles and Dependencies in Maven ANT Task
Hi! I know that the attribute profiles in task artifact:dependencies is not yet supported. I was though wondering is there a mechanism to specify the correct property/ies in the rest of the ant file so that the correct profile would be picked up by the dependency task. In other words I'd like to have in my build.xml property name=myprop value=true/ and in pom.xml . profile idadditional_dependency_profile/id activation property namemyprop/name valuetrue/value /property /activation dependencies extra dependencies here /dependencies /profile I noticed that setting a profile to activeByDefault works, i.e. the dependency task picks up the extra dependencies defined in the profile, but, as said, I could not make the property-activated profile do my bidding. Thanks in advance for your help, regards, Marco Sandrini -- View this message in context: http://www.nabble.com/Profiles-and-Dependencies-in-Maven-ANT-Task-tp16125102s177p16125102.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [ANN] Maven Eclipse Plugin 2.5 Released
What OS and Maven version are you using? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of nicolas de loof Sent: Tuesday, March 18, 2008 10:10 AM To: Maven Users List Subject: Re: [ANN] Maven Eclipse Plugin 2.5 Released I also use a custom local repository location and get the expected M2_REPO/commons-logging in my .classpath. Nico 2008/3/18, Arnaud HERITIER [EMAIL PROTECTED]: yes please open a bug. I don't use the standard location and didn't notice it. If I can reproduce it, I'll publish a version 2.5.1 in few days. cheers. On Tue, Mar 18, 2008 at 1:56 PM, Hoover, William [EMAIL PROTECTED] wrote: I'm not using the default repository location either. I think you may be right- it may have something to do with that. -Original Message- From: MATHUS Baptiste [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2008 8:29 AM To: Maven Users List Subject: RE: [ANN] Maven Eclipse Plugin 2.5 Released +1. Same problem here. Just saw the behaviour some minutes ago. Precision: I'm not using the default repository location, this might a cause of this problem. Do you want someone to log a bug in the tracker, Arnaud? Cheers. -Message d'origine- De : Hoover, William [mailto:[EMAIL PROTECTED] Envoyé : mardi 18 mars 2008 13:11 À : Maven Users List Cc : Maven Developers List Objet : RE: [ANN] Maven Eclipse Plugin 2.5 Released Using mvn eclipse:clean eclipse:eclipse with version 2.5. For example, if M2_REPO = /path/to/repo executing the command renders build paths for dependencies for project as M2_REPO/path/to/repo/commons-collections/commons-collections/3.2/commons- collections-3.2.jar If I use version 2.4 M2_REPO is referenced properly (i.e. M2_REPO/commons-collections/commons-collections/3.2/commons- collections-3.2.jar): build plugins plugin groupIdorg.apache.maven.plugins /groupId artifactIdmaven-eclipse-plugin/artifactId version2.4/version /plugin /plugins /build -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Arnaud HERITIER Sent: Tuesday, March 18, 2008 6:33 AM To: [EMAIL PROTECTED]; Maven Users List Cc: Maven Developers List Subject: [ANN] Maven Eclipse Plugin 2.5 Released The Maven team is pleased to announce the release of the Maven Eclipse Plugin, version 2.5 This plugin is used to generate Eclipse IDE files (*.classpath, *.wtpmodules and the .settings folder) for use with a project. http://maven.apache.org/plugins/maven-eclipse-plugin/ You can run mvn -up to get the latest version of the plugin, or specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-eclipse-plugin/artifactId version2.5/version /plugin In this release we added the support for myeclipse, WTP 2.0 and the possibility to connect your projects with existing ones in your workspace. We also improved the support for rad 6 7 and fixed many bugs. Thanks a lot for those who helped us by providing patches and/or by testing our snapshots. Release Notes - Maven 2.x Eclipse Plugin - Version 2.5 ** Bug * [MECLIPSE-56] - Generated .project-file misses encoding declaration * [MECLIPSE-102] - sar projects conflict with maven-eclipse-plugin * [MECLIPSE-107] - Dependency Version Incorrectly Taken from DependencyManagement * [MECLIPSE-160] - Wrong description with the goal add-maven-repo documentation * [MECLIPSE-172] - Don't add Default ClasspathContainer if a alternate JRE or a Execution Environment is configured as ClasspathContainer. * [MECLIPSE-291] - tests fail with spaces in the path name * [MECLIPSE-296] - Wrong generated source-path when warSourceDirectory is set * [MECLIPSE-297] - eclipse:clean deletes files from pom projects * [MECLIPSE-301] - eclipse:clean doesn't respect packaging 'pom' * [MECLIPSE-305] - souce-path is absolute versus relative with WAR * [MECLIPSE-309] - warSourceDirectory incorrectly resolved inside a reactor (with a relative path) * [MECLIPSE-315] - RadWebSettingsWriter uses hardcoded webcontent path and ignores warSourceDirectory * [MECLIPSE-316] - RadCleanMojo does not clean .war files * [MECLIPSE-323] - eclipse:clean does NOT delete 'additionalConfig' files * [MECLIPSE-332] - mvn-eclipse-cache.properties is never filled * [MECLIPSE-342] - Found an equals call to check unrelated types * [MECLIPSE-346] - Transitive dependencies aren't used to resolve JEE/JSP/EJB/Servlet versions * [MECLIPSE-352] - RAD application.xml is not generated with good parameters * [MECLIPSE-356] - RadLibCopier does not
Re: [ANN] Maven Eclipse Plugin 2.5 Released
Maven 2.0.8 running on Windows XP, Jrockit 6.0 maven-eclipse-plugin 2.5 (final) localrepository set to custom path from my settings.xml All works fine for me. 2008/3/18, Hoover, William [EMAIL PROTECTED]: What OS and Maven version are you using? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of nicolas de loof Sent: Tuesday, March 18, 2008 10:10 AM To: Maven Users List Subject: Re: [ANN] Maven Eclipse Plugin 2.5 Released I also use a custom local repository location and get the expected M2_REPO/commons-logging in my .classpath. Nico 2008/3/18, Arnaud HERITIER [EMAIL PROTECTED]: yes please open a bug. I don't use the standard location and didn't notice it. If I can reproduce it, I'll publish a version 2.5.1 in few days. cheers. On Tue, Mar 18, 2008 at 1:56 PM, Hoover, William [EMAIL PROTECTED] wrote: I'm not using the default repository location either. I think you may be right- it may have something to do with that. -Original Message- From: MATHUS Baptiste [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2008 8:29 AM To: Maven Users List Subject: RE: [ANN] Maven Eclipse Plugin 2.5 Released +1. Same problem here. Just saw the behaviour some minutes ago. Precision: I'm not using the default repository location, this might a cause of this problem. Do you want someone to log a bug in the tracker, Arnaud? Cheers. -Message d'origine- De : Hoover, William [mailto:[EMAIL PROTECTED] Envoyé : mardi 18 mars 2008 13:11 À : Maven Users List Cc : Maven Developers List Objet : RE: [ANN] Maven Eclipse Plugin 2.5 Released Using mvn eclipse:clean eclipse:eclipse with version 2.5. For example, if M2_REPO = /path/to/repo executing the command renders build paths for dependencies for project as M2_REPO/path/to/repo/commons-collections/commons-collections/3.2/commons- collections-3.2.jar If I use version 2.4 M2_REPO is referenced properly (i.e. M2_REPO/commons-collections/commons-collections/3.2/commons- collections-3.2.jar): build plugins plugin groupIdorg.apache.maven.plugins /groupId artifactIdmaven-eclipse-plugin/artifactId version2.4/version /plugin /plugins /build -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Arnaud HERITIER Sent: Tuesday, March 18, 2008 6:33 AM To: [EMAIL PROTECTED]; Maven Users List Cc: Maven Developers List Subject: [ANN] Maven Eclipse Plugin 2.5 Released The Maven team is pleased to announce the release of the Maven Eclipse Plugin, version 2.5 This plugin is used to generate Eclipse IDE files (*.classpath, *.wtpmodules and the .settings folder) for use with a project. http://maven.apache.org/plugins/maven-eclipse-plugin/ You can run mvn -up to get the latest version of the plugin, or specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-eclipse-plugin/artifactId version2.5/version /plugin In this release we added the support for myeclipse, WTP 2.0 and the possibility to connect your projects with existing ones in your workspace. We also improved the support for rad 6 7 and fixed many bugs. Thanks a lot for those who helped us by providing patches and/or by testing our snapshots. Release Notes - Maven 2.x Eclipse Plugin - Version 2.5 ** Bug * [MECLIPSE-56] - Generated .project-file misses encoding declaration * [MECLIPSE-102] - sar projects conflict with maven-eclipse-plugin * [MECLIPSE-107] - Dependency Version Incorrectly Taken from DependencyManagement * [MECLIPSE-160] - Wrong description with the goal add-maven-repo documentation * [MECLIPSE-172] - Don't add Default ClasspathContainer if a alternate JRE or a Execution Environment is configured as ClasspathContainer. * [MECLIPSE-291] - tests fail with spaces in the path name * [MECLIPSE-296] - Wrong generated source-path when warSourceDirectory is set * [MECLIPSE-297] - eclipse:clean deletes files from pom projects * [MECLIPSE-301] - eclipse:clean doesn't respect packaging 'pom' * [MECLIPSE-305] - souce-path is absolute versus relative with WAR * [MECLIPSE-309] - warSourceDirectory incorrectly resolved inside a reactor (with a relative path) * [MECLIPSE-315] - RadWebSettingsWriter uses hardcoded webcontent path and ignores warSourceDirectory * [MECLIPSE-316] - RadCleanMojo does not clean .war files * [MECLIPSE-323] - eclipse:clean does NOT delete 'additionalConfig' files * [MECLIPSE-332] -
SV: [ANN] Maven Eclipse Plugin 2.5 Released
This error occurs in my projects to after switching to 2.5, but so far only in when packaging are war, not jar or ejb. I'm using wtpversion 2.0. I'm using windows XP, Maven 2.0.8 Arne. -Opprinnelig melding- Fra: Hoover, William [mailto:[EMAIL PROTECTED] Sendt: 18. mars 2008 17:36 Til: Maven Users List Emne: RE: [ANN] Maven Eclipse Plugin 2.5 Released What OS and Maven version are you using? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of nicolas de loof Sent: Tuesday, March 18, 2008 10:10 AM To: Maven Users List Subject: Re: [ANN] Maven Eclipse Plugin 2.5 Released I also use a custom local repository location and get the expected M2_REPO/commons-logging in my .classpath. Nico 2008/3/18, Arnaud HERITIER [EMAIL PROTECTED]: yes please open a bug. I don't use the standard location and didn't notice it. If I can reproduce it, I'll publish a version 2.5.1 in few days. cheers. On Tue, Mar 18, 2008 at 1:56 PM, Hoover, William [EMAIL PROTECTED] wrote: I'm not using the default repository location either. I think you may be right- it may have something to do with that. -Original Message- From: MATHUS Baptiste [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2008 8:29 AM To: Maven Users List Subject: RE: [ANN] Maven Eclipse Plugin 2.5 Released +1. Same problem here. Just saw the behaviour some minutes ago. Precision: I'm not using the default repository location, this might a cause of this problem. Do you want someone to log a bug in the tracker, Arnaud? Cheers. -Message d'origine- De : Hoover, William [mailto:[EMAIL PROTECTED] Envoyé : mardi 18 mars 2008 13:11 À : Maven Users List Cc : Maven Developers List Objet : RE: [ANN] Maven Eclipse Plugin 2.5 Released Using mvn eclipse:clean eclipse:eclipse with version 2.5. For example, if M2_REPO = /path/to/repo executing the command renders build paths for dependencies for project as M2_REPO/path/to/repo/commons-collections/commons-collections/3.2/commons- collections-3.2.jar If I use version 2.4 M2_REPO is referenced properly (i.e. M2_REPO/commons-collections/commons-collections/3.2/commons- collections-3.2.jar): build plugins plugin groupIdorg.apache.maven.plugins /groupId artifactIdmaven-eclipse-plugin/artifactId version2.4/version /plugin /plugins /build -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Arnaud HERITIER Sent: Tuesday, March 18, 2008 6:33 AM To: [EMAIL PROTECTED]; Maven Users List Cc: Maven Developers List Subject: [ANN] Maven Eclipse Plugin 2.5 Released The Maven team is pleased to announce the release of the Maven Eclipse Plugin, version 2.5 This plugin is used to generate Eclipse IDE files (*.classpath, *.wtpmodules and the .settings folder) for use with a project. http://maven.apache.org/plugins/maven-eclipse-plugin/ You can run mvn -up to get the latest version of the plugin, or specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-eclipse-plugin/artifactId version2.5/version /plugin In this release we added the support for myeclipse, WTP 2.0 and the possibility to connect your projects with existing ones in your workspace. We also improved the support for rad 6 7 and fixed many bugs. Thanks a lot for those who helped us by providing patches and/or by testing our snapshots. Release Notes - Maven 2.x Eclipse Plugin - Version 2.5 ** Bug * [MECLIPSE-56] - Generated .project-file misses encoding declaration * [MECLIPSE-102] - sar projects conflict with maven-eclipse-plugin * [MECLIPSE-107] - Dependency Version Incorrectly Taken from DependencyManagement * [MECLIPSE-160] - Wrong description with the goal add-maven-repo documentation * [MECLIPSE-172] - Don't add Default ClasspathContainer if a alternate JRE or a Execution Environment is configured as ClasspathContainer. * [MECLIPSE-291] - tests fail with spaces in the path name * [MECLIPSE-296] - Wrong generated source-path when warSourceDirectory is set * [MECLIPSE-297] - eclipse:clean deletes files from pom projects * [MECLIPSE-301] - eclipse:clean doesn't respect packaging 'pom' * [MECLIPSE-305] - souce-path is absolute versus relative with WAR * [MECLIPSE-309] - warSourceDirectory incorrectly resolved inside a reactor (with a relative path) * [MECLIPSE-315] - RadWebSettingsWriter uses hardcoded webcontent path and ignores warSourceDirectory * [MECLIPSE-316] - RadCleanMojo does not clean .war files * [MECLIPSE-323] - eclipse:clean does NOT delete 'additionalConfig' files
RE: [ANN] Maven Eclipse Plugin 2.5 Released
I tested with packaging as jar or war and still have the issue -Original Message- From: Arne Rivenes [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2008 12:49 PM To: Maven Users List Subject: SV: [ANN] Maven Eclipse Plugin 2.5 Released This error occurs in my projects to after switching to 2.5, but so far only in when packaging are war, not jar or ejb. I'm using wtpversion 2.0. I'm using windows XP, Maven 2.0.8 Arne. -Opprinnelig melding- Fra: Hoover, William [mailto:[EMAIL PROTECTED] Sendt: 18. mars 2008 17:36 Til: Maven Users List Emne: RE: [ANN] Maven Eclipse Plugin 2.5 Released What OS and Maven version are you using? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of nicolas de loof Sent: Tuesday, March 18, 2008 10:10 AM To: Maven Users List Subject: Re: [ANN] Maven Eclipse Plugin 2.5 Released I also use a custom local repository location and get the expected M2_REPO/commons-logging in my .classpath. Nico 2008/3/18, Arnaud HERITIER [EMAIL PROTECTED]: yes please open a bug. I don't use the standard location and didn't notice it. If I can reproduce it, I'll publish a version 2.5.1 in few days. cheers. On Tue, Mar 18, 2008 at 1:56 PM, Hoover, William [EMAIL PROTECTED] wrote: I'm not using the default repository location either. I think you may be right- it may have something to do with that. -Original Message- From: MATHUS Baptiste [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2008 8:29 AM To: Maven Users List Subject: RE: [ANN] Maven Eclipse Plugin 2.5 Released +1. Same problem here. Just saw the behaviour some minutes ago. Precision: I'm not using the default repository location, this might a cause of this problem. Do you want someone to log a bug in the tracker, Arnaud? Cheers. -Message d'origine- De : Hoover, William [mailto:[EMAIL PROTECTED] Envoyé : mardi 18 mars 2008 13:11 À : Maven Users List Cc : Maven Developers List Objet : RE: [ANN] Maven Eclipse Plugin 2.5 Released Using mvn eclipse:clean eclipse:eclipse with version 2.5. For example, if M2_REPO = /path/to/repo executing the command renders build paths for dependencies for project as M2_REPO/path/to/repo/commons-collections/commons-collections/3.2/commons- collections-3.2.jar If I use version 2.4 M2_REPO is referenced properly (i.e. M2_REPO/commons-collections/commons-collections/3.2/commons- collections-3.2.jar): build plugins plugin groupIdorg.apache.maven.plugins /groupId artifactIdmaven-eclipse-plugin/artifactId version2.4/version /plugin /plugins /build -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Arnaud HERITIER Sent: Tuesday, March 18, 2008 6:33 AM To: [EMAIL PROTECTED]; Maven Users List Cc: Maven Developers List Subject: [ANN] Maven Eclipse Plugin 2.5 Released The Maven team is pleased to announce the release of the Maven Eclipse Plugin, version 2.5 This plugin is used to generate Eclipse IDE files (*.classpath, *.wtpmodules and the .settings folder) for use with a project. http://maven.apache.org/plugins/maven-eclipse-plugin/ You can run mvn -up to get the latest version of the plugin, or specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-eclipse-plugin/artifactId version2.5/version /plugin In this release we added the support for myeclipse, WTP 2.0 and the possibility to connect your projects with existing ones in your workspace. We also improved the support for rad 6 7 and fixed many bugs. Thanks a lot for those who helped us by providing patches and/or by testing our snapshots. Release Notes - Maven 2.x Eclipse Plugin - Version 2.5 ** Bug * [MECLIPSE-56] - Generated .project-file misses encoding declaration * [MECLIPSE-102] - sar projects conflict with maven-eclipse-plugin * [MECLIPSE-107] - Dependency Version Incorrectly Taken from DependencyManagement * [MECLIPSE-160] - Wrong description with the goal add-maven-repo documentation * [MECLIPSE-172] - Don't add Default ClasspathContainer if a alternate JRE or a Execution Environment is configured as ClasspathContainer. * [MECLIPSE-291] - tests fail with spaces in the path name * [MECLIPSE-296] - Wrong generated source-path when warSourceDirectory is set * [MECLIPSE-297] - eclipse:clean deletes files from pom projects * [MECLIPSE-301] - eclipse:clean doesn't respect packaging 'pom' * [MECLIPSE-305] - souce-path is absolute versus relative with WAR * [MECLIPSE-309] - warSourceDirectory incorrectly resolved inside a reactor (with a relative path) *
RE: [ANN] Maven Eclipse Plugin 2.5 Released
We are also getting this behavior maven 2.0.8 windows XP. Liz Sommers [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Versioning conflict in mvn and eclipse:to-maven plugin
Hey guys, i believe there is a bug in either the way versions for dependencies are matched or in the way the eclipse:to-maven plugin works. When I run the eclipse:to-maven target, my brand new repository is populated with eclipse plugins and nothing else. I attempt to build a project which depends on these dependencies, but the dependencies do not resolve. One of the eclipse plugins depends on another one that is within version range [3.3.0,4.00). The dependecny i have to satisfy this version is 3.3.0-3.3.0-I20070605-0010. But this is not acceptable, yielding this error: org.apache.maven.lifecycle.LifecycleExecutionException: Couldn't find a version in [3.3.0-I20070605-0010, 3.2.0-I20060605-1400] to match range [3.3.0,4.0.0) I understand that maven might desire some sort of special versioning in the form of x.y.z, in which case the eclipse:to-maven plugin should setup the pom's correctly (set the versions in an acceptable manner.) If maven does not have this hard and fast version requirement, shouldn't it accept the version 3.3.0-I20070605-0010, 3.2.0-I20060605-1400 to be within 3.3.0-4.0.0? Thank you Apaar Trivedi Consultant Blue Fish Development Group http://www.bluefishgroup.com http://www.bluefishgroup.com/ Blue Fish is Hiring! Check out www.bluefishgroup.com/careers http://www.bluefishgroup.com/careers
RE: [ANN] Maven Eclipse Plugin 2.5 Released
I found that replacing... localRepository/path/to/repo/localRepository with... localRepositoryC:\path\to\repo/localRepository ... in settings.xml fixes the problem in XP. In 2.4 /path/to/repo worked properly and is more portable than specifying a drive and corresponding backslashes. Can anyone else verify that this fixes their issues as well? -Original Message- From: Hoover, William [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2008 12:57 PM To: Maven Users List Subject: RE: [ANN] Maven Eclipse Plugin 2.5 Released I tested with packaging as jar or war and still have the issue -Original Message- From: Arne Rivenes [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2008 12:49 PM To: Maven Users List Subject: SV: [ANN] Maven Eclipse Plugin 2.5 Released This error occurs in my projects to after switching to 2.5, but so far only in when packaging are war, not jar or ejb. I'm using wtpversion 2.0. I'm using windows XP, Maven 2.0.8 Arne. -Opprinnelig melding- Fra: Hoover, William [mailto:[EMAIL PROTECTED] Sendt: 18. mars 2008 17:36 Til: Maven Users List Emne: RE: [ANN] Maven Eclipse Plugin 2.5 Released What OS and Maven version are you using? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of nicolas de loof Sent: Tuesday, March 18, 2008 10:10 AM To: Maven Users List Subject: Re: [ANN] Maven Eclipse Plugin 2.5 Released I also use a custom local repository location and get the expected M2_REPO/commons-logging in my .classpath. Nico 2008/3/18, Arnaud HERITIER [EMAIL PROTECTED]: yes please open a bug. I don't use the standard location and didn't notice it. If I can reproduce it, I'll publish a version 2.5.1 in few days. cheers. On Tue, Mar 18, 2008 at 1:56 PM, Hoover, William [EMAIL PROTECTED] wrote: I'm not using the default repository location either. I think you may be right- it may have something to do with that. -Original Message- From: MATHUS Baptiste [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2008 8:29 AM To: Maven Users List Subject: RE: [ANN] Maven Eclipse Plugin 2.5 Released +1. Same problem here. Just saw the behaviour some minutes ago. Precision: I'm not using the default repository location, this might a cause of this problem. Do you want someone to log a bug in the tracker, Arnaud? Cheers. -Message d'origine- De : Hoover, William [mailto:[EMAIL PROTECTED] Envoyé : mardi 18 mars 2008 13:11 À : Maven Users List Cc : Maven Developers List Objet : RE: [ANN] Maven Eclipse Plugin 2.5 Released Using mvn eclipse:clean eclipse:eclipse with version 2.5. For example, if M2_REPO = /path/to/repo executing the command renders build paths for dependencies for project as M2_REPO/path/to/repo/commons-collections/commons-collections/3.2/commons- collections-3.2.jar If I use version 2.4 M2_REPO is referenced properly (i.e. M2_REPO/commons-collections/commons-collections/3.2/commons- collections-3.2.jar): build plugins plugin groupIdorg.apache.maven.plugins /groupId artifactIdmaven-eclipse-plugin/artifactId version2.4/version /plugin /plugins /build -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Behalf Of Arnaud HERITIER Sent: Tuesday, March 18, 2008 6:33 AM To: [EMAIL PROTECTED]; Maven Users List Cc: Maven Developers List Subject: [ANN] Maven Eclipse Plugin 2.5 Released The Maven team is pleased to announce the release of the Maven Eclipse Plugin, version 2.5 This plugin is used to generate Eclipse IDE files (*.classpath, *.wtpmodules and the .settings folder) for use with a project. http://maven.apache.org/plugins/maven-eclipse-plugin/ You can run mvn -up to get the latest version of the plugin, or specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-eclipse-plugin/artifactId version2.5/version /plugin In this release we added the support for myeclipse, WTP 2.0 and the possibility to connect your projects with existing ones in your workspace. We also improved the support for rad 6 7 and fixed many bugs. Thanks a lot for those who helped us by providing patches and/or by testing our snapshots. Release Notes - Maven 2.x Eclipse Plugin - Version 2.5 ** Bug * [MECLIPSE-56] - Generated .project-file misses encoding declaration * [MECLIPSE-102] - sar projects conflict with maven-eclipse-plugin * [MECLIPSE-107] - Dependency Version Incorrectly Taken from DependencyManagement * [MECLIPSE-160] - Wrong description with the goal add-maven-repo documentation * [MECLIPSE-172] - Don't add Default ClasspathContainer if a alternate JRE or
Using the maven-dependency-plugin
Hi, I am using the maven-dependency-plugin unpack-dependencies to unpack the dependencies into some directory in my target directory. When i have multiple executions, the first unpack-dependencies execution unpacks the junit jar by default into my output directory. This does not happen for the subsequent executions. Any ideas why this happens? I have enabled the excludeTrasitive flag. Thanks, Shalini. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Versioning conflict in mvn and eclipse:to-maven plugin
I have looked into this a bit more and it appears that the problem is with the qualifiers getting added to the versions of the artifacts deployed by the eclipse:to-maven target. The solution involves allowing the 'stripQualifier' parameter to be exposed in the plugin, here is a note I sent to the dev list: We need one thing parameterized on the EclipseToMavenMojo.java in the maven-eclipse-plugin which should be parameterized anyway. In the call to osgiVersionToMavenVersion, it only allows 'false' to be passed in for the 'strip qualifier' parameter. While the make-artifacts (which extends to-maven) target allows you to strip the qualifier, this is not a parameter that can be used in the to-maven target. This is a problem because using 'to-maven' provides artifacts with the proper names but the dependecies do not resolve due to the qualifiers on the versions. While make-artifacts provides dependecies that resolve but the naming convention of the groupId's and artifactId's is incorrect. Just a parameter -DstripQualifer that gets passed in to the call to osgiVersionToMavenVersion( String version, String forcedQualifier, boolean stripQualifier ) would be perfect. Thank you Apaar -Original Message- From: Apaar Trivedi [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2008 1:28 PM To: users@maven.apache.org Subject: Versioning conflict in mvn and eclipse:to-maven plugin Hey guys, i believe there is a bug in either the way versions for dependencies are matched or in the way the eclipse:to-maven plugin works. When I run the eclipse:to-maven target, my brand new repository is populated with eclipse plugins and nothing else. I attempt to build a project which depends on these dependencies, but the dependencies do not resolve. One of the eclipse plugins depends on another one that is within version range [3.3.0,4.00). The dependecny i have to satisfy this version is 3.3.0-3.3.0-I20070605-0010. But this is not acceptable, yielding this error: org.apache.maven.lifecycle.LifecycleExecutionException: Couldn't find a version in [3.3.0-I20070605-0010, 3.2.0-I20060605-1400] to match range [3.3.0,4.0.0) I understand that maven might desire some sort of special versioning in the form of x.y.z, in which case the eclipse:to-maven plugin should setup the pom's correctly (set the versions in an acceptable manner.) If maven does not have this hard and fast version requirement, shouldn't it accept the version 3.3.0-I20070605-0010, 3.2.0-I20060605-1400 to be within 3.3.0-4.0.0? Thank you Apaar Trivedi Consultant Blue Fish Development Group http://www.bluefishgroup.com http://www.bluefishgroup.com/ Blue Fish is Hiring! Check out www.bluefishgroup.com/careers http://www.bluefishgroup.com/careers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
mvn 2.0.8
Hi, I have been using 2,.0.7 for some time and I'm very happy I just tried a quick update to 2.0.8 and am having no luck. Any suggestions? I keep getting [EMAIL PROTECTED]:~/cc/maven-2.0.8 mvn --version Exception in thread main java.lang.IllegalAccessError: tried to access field hidden.org.codehaus.plexus.util.Os.OS_NAME from class org.apache.maven.cli.MavenCli at org.apache.maven.cli.MavenCli.clinit(MavenCli.java:76) 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:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mvn 2.0.8
Are you sure you're running the mvn binary you think you're running? Try ./mvn --version instead. I'd assume you failed to update your PATH etc as required. Wayne On 3/18/08, Michael Clark [EMAIL PROTECTED] wrote: Hi, I have been using 2,.0.7 for some time and I'm very happy I just tried a quick update to 2.0.8 and am having no luck. Any suggestions? I keep getting [EMAIL PROTECTED]:~/cc/maven-2.0.8 mvn --version Exception in thread main java.lang.IllegalAccessError: tried to access field hidden.org.codehaus.plexus.util.Os.OS_NAME from class org.apache.maven.cli.MavenCli at org.apache.maven.cli.MavenCli.clinit(MavenCli.java:76) 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:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
mvn -Dplugin=install help:describe
Hi - I just installed Maven 2.0.8 as per instructions. Running mvn --version yields Maven version: 2.0.8 Java version: 1.6.0_03 OS name: linux version: 2.6.17.13 arch: i386 Family: unix The FAQ indicates that to check the installed plugins I need execute mvn -Dplugin=install help:describe But when I run this command it fails with a build failure Plugin could not be found. I also tried mvn -U -Dplugin=install help:describe but the same result - can't find the plugin. The output is enclosed. There doesn't appear to be a FAQ entry indicating how to upgrade or install a plugin. Any help would be appreciated. [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'help'. [INFO] org.apache.maven.plugins: checking for updates from central [INFO] org.codehaus.mojo: checking for updates from central [INFO] artifact org.apache.maven.plugins:maven-help-plugin: checking for updates from central Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-help-p lugin/2.0.2/maven-help-plugin-2.0.2.pom 3K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-plugin s/10/maven-plugins-10.pom 7K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven-parent/7/maven -parent-7.pom 20K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/apache/4/apache-4.pom 4K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-help-p lugin/2.0.2/maven-help-plugin-2.0.2.jar 23K downloaded [INFO] [INFO] Building Maven Default Project [INFO]task-segment: [help:describe] (aggregator-style) [INFO] Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven-project/2.0/ma ven-project-2.0.pom 1K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven/2.0/maven-2.0. pom 8K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven-profile/2.0/ma ven-profile-2.0.pom 1K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven-model/2.0/mave n-model-2.0.pom 2K downloaded Downloading: http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.0. 4/plexus-utils-1.0.4.pom 6K downloaded Downloading: http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-container- /1.0.3/plexus-containers-1.0.3.pom 492b downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven-settings/2.0/m aven-settings-2.0.pom 1K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven-core/2.0/maven -core-2.0.pom 5K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/wagon/wagon-file/1.0 -alpha-5/wagon-file-1.0-alpha-5.pom 5K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven-plugin-paramet er-documenter/2.0/maven-plugin-parameter-documenter-2.0.pom 1K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/wagon/wagon-http-lig htweight/1.0-alpha-5/wagon-http-lightweight-1.0-alpha-5.pom 5K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/reporting/maven-repo rting-api/2.0/maven-reporting-api-2.0.pom 1K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/reporting/maven-repo rting/2.0/maven-reporting-2.0.pom 504b downloaded Downloading: http://repo1.maven.org/maven2/doxia/doxia-sink-api/1.0-alpha-4/doxi a-sink-api-1.0-alpha-4.pom 1K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven-error-diagnost ics/2.0/maven-error-diagnostics-2.0.pom 812b downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven-plugin-registr y/2.0/maven-plugin-registry-2.0.pom 1K downloaded Downloading: http://repo1.maven.org/maven2/commons-cli/commons-cli/1.0/commons-c li-1.0.pom 2K downloaded Downloading: http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-interactiv ity-api/1.0-alpha-4/plexus-interactivity-api-1.0-alpha-4.pom 6K downloadedDownloading: http://repo1.maven.org/maven2/org/apache/maven/maven-monitor/2.0/ma ven-monitor-2.0.pom 400b downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/wagon/wagon-ssh/1.0- alpha-5/wagon-ssh-1.0-alpha-5.pom 6K downloaded Downloading: http://repo1.maven.org/maven2/com/jcraft/jsch/0.1.23/jsch-0.1.23.po m 485b downloaded Downloading: http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.1/ plexus-utils-1.1.jar 164K downloaded [INFO] [help:describe] [INFO] Searching repository for plugin with prefix: 'install'. [INFO] [ERROR] BUILD FAILURE [INFO]
Re: mvn -Dplugin=install help:describe
Plugins are automatically downloaded and installed on an as-needed basis. You don't need to do anything manually to make it happen. Just build up a pom and type mvn install and it will be downloaded and used. Wayne On 3/18/08, Agile Aspect [EMAIL PROTECTED] wrote: Hi - I just installed Maven 2.0.8 as per instructions. Running mvn --version yields Maven version: 2.0.8 Java version: 1.6.0_03 OS name: linux version: 2.6.17.13 arch: i386 Family: unix The FAQ indicates that to check the installed plugins I need execute mvn -Dplugin=install help:describe But when I run this command it fails with a build failure Plugin could not be found. I also tried mvn -U -Dplugin=install help:describe but the same result - can't find the plugin. The output is enclosed. There doesn't appear to be a FAQ entry indicating how to upgrade or install a plugin. Any help would be appreciated. [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'help'. [INFO] org.apache.maven.plugins: checking for updates from central [INFO] org.codehaus.mojo: checking for updates from central [INFO] artifact org.apache.maven.plugins:maven-help-plugin: checking for updates from central Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-help-p lugin/2.0.2/maven-help-plugin-2.0.2.pom 3K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-plugin s/10/maven-plugins-10.pom 7K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven-parent/7/maven -parent-7.pom 20K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/apache/4/apache-4.pom 4K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-help-p lugin/2.0.2/maven-help-plugin-2.0.2.jar 23K downloaded [INFO] [INFO] Building Maven Default Project [INFO]task-segment: [help:describe] (aggregator-style) [INFO] Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven-project/2.0/ma ven-project-2.0.pom 1K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven/2.0/maven-2.0. pom 8K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven-profile/2.0/ma ven-profile-2.0.pom 1K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven-model/2.0/mave n-model-2.0.pom 2K downloaded Downloading: http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.0. 4/plexus-utils-1.0.4.pom 6K downloaded Downloading: http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-container- /1.0.3/plexus-containers-1.0.3.pom 492b downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven-settings/2.0/m aven-settings-2.0.pom 1K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven-core/2.0/maven -core-2.0.pom 5K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/wagon/wagon-file/1.0 -alpha-5/wagon-file-1.0-alpha-5.pom 5K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven-plugin-paramet er-documenter/2.0/maven-plugin-parameter-documenter-2.0.pom 1K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/wagon/wagon-http-lig htweight/1.0-alpha-5/wagon-http-lightweight-1.0-alpha-5.pom 5K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/reporting/maven-repo rting-api/2.0/maven-reporting-api-2.0.pom 1K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/reporting/maven-repo rting/2.0/maven-reporting-2.0.pom 504b downloaded Downloading: http://repo1.maven.org/maven2/doxia/doxia-sink-api/1.0-alpha-4/doxi a-sink-api-1.0-alpha-4.pom 1K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven-error-diagnost ics/2.0/maven-error-diagnostics-2.0.pom 812b downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven-plugin-registr y/2.0/maven-plugin-registry-2.0.pom 1K downloaded Downloading: http://repo1.maven.org/maven2/commons-cli/commons-cli/1.0/commons-c li-1.0.pom 2K downloaded Downloading: http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-interactiv ity-api/1.0-alpha-4/plexus-interactivity-api-1.0-alpha-4.pom 6K downloadedDownloading: http://repo1.maven.org/maven2/org/apache/maven/maven-monitor/2.0/ma ven-monitor-2.0.pom 400b downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/wagon/wagon-ssh/1.0- alpha-5/wagon-ssh-1.0-alpha-5.pom 6K downloaded Downloading: http://repo1.maven.org/maven2/com/jcraft/jsch/0.1.23/jsch-0.1.23.po m 485b downloaded Downloading: http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.1/ plexus-utils-1.1.jar 164K
Re: mvn 2.0.8
Yup same results [EMAIL PROTECTED]:~/cc/maven-2.0.8/bin ./mvn --version Exception in thread main java.lang.IllegalAccessError: tried to access field hidden.org.codehaus.plexus.util.Os.OS_NAME from class org.apache.maven.cli.MavenCli at org.apache.maven.cli.MavenCli.clinit(MavenCli.java:76) 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:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) On Tue, 2008-03-18 at 15:22 -0500, Wayne Fay wrote: Are you sure you're running the mvn binary you think you're running? Try ./mvn --version instead. I'd assume you failed to update your PATH etc as required. Wayne On 3/18/08, Michael Clark [EMAIL PROTECTED] wrote: Hi, I have been using 2,.0.7 for some time and I'm very happy I just tried a quick update to 2.0.8 and am having no luck. Any suggestions? I keep getting [EMAIL PROTECTED]:~/cc/maven-2.0.8 mvn --version Exception in thread main java.lang.IllegalAccessError: tried to access field hidden.org.codehaus.plexus.util.Os.OS_NAME from class org.apache.maven.cli.MavenCli at org.apache.maven.cli.MavenCli.clinit(MavenCli.java:76) 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:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mvn 2.0.8
What kind of system are you on? For all I know, you've stumbled across an obscure bug related to your specific environment. Also try mvn -U to force it to find updates, perhaps you've got a buggy Plexus-Util. Wayne On 3/18/08, Michael Clark [EMAIL PROTECTED] wrote: Yup same results [EMAIL PROTECTED]:~/cc/maven-2.0.8/bin ./mvn --version Exception in thread main java.lang.IllegalAccessError: tried to access field hidden.org.codehaus.plexus.util.Os.OS_NAME from class org.apache.maven.cli.MavenCli at org.apache.maven.cli.MavenCli.clinit(MavenCli.java:76) 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:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) On Tue, 2008-03-18 at 15:22 -0500, Wayne Fay wrote: Are you sure you're running the mvn binary you think you're running? Try ./mvn --version instead. I'd assume you failed to update your PATH etc as required. Wayne On 3/18/08, Michael Clark [EMAIL PROTECTED] wrote: Hi, I have been using 2,.0.7 for some time and I'm very happy I just tried a quick update to 2.0.8 and am having no luck. Any suggestions? I keep getting [EMAIL PROTECTED]:~/cc/maven-2.0.8 mvn --version Exception in thread main java.lang.IllegalAccessError: tried to access field hidden.org.codehaus.plexus.util.Os.OS_NAME from class org.apache.maven.cli.MavenCli at org.apache.maven.cli.MavenCli.clinit(MavenCli.java:76) 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:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mvn -Dplugin=install help:describe
Great - thank you - I'll give it try! Wayne Fay wrote: Plugins are automatically downloaded and installed on an as-needed basis. You don't need to do anything manually to make it happen. Just build up a pom and type mvn install and it will be downloaded and used. Wayne On 3/18/08, Agile Aspect [EMAIL PROTECTED] wrote: Hi - I just installed Maven 2.0.8 as per instructions. Running mvn --version yields Maven version: 2.0.8 Java version: 1.6.0_03 OS name: linux version: 2.6.17.13 arch: i386 Family: unix The FAQ indicates that to check the installed plugins I need execute mvn -Dplugin=install help:describe But when I run this command it fails with a build failure Plugin could not be found. I also tried mvn -U -Dplugin=install help:describe but the same result - can't find the plugin. The output is enclosed. There doesn't appear to be a FAQ entry indicating how to upgrade or install a plugin. Any help would be appreciated. [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'help'. [INFO] org.apache.maven.plugins: checking for updates from central [INFO] org.codehaus.mojo: checking for updates from central [INFO] artifact org.apache.maven.plugins:maven-help-plugin: checking for updates from central Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-help-p lugin/2.0.2/maven-help-plugin-2.0.2.pom 3K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-plugin s/10/maven-plugins-10.pom 7K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven-parent/7/maven -parent-7.pom 20K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/apache/4/apache-4.pom 4K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-help-p lugin/2.0.2/maven-help-plugin-2.0.2.jar 23K downloaded [INFO] [INFO] Building Maven Default Project [INFO]task-segment: [help:describe] (aggregator-style) [INFO] Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven-project/2.0/ma ven-project-2.0.pom 1K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven/2.0/maven-2.0. pom 8K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven-profile/2.0/ma ven-profile-2.0.pom 1K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven-model/2.0/mave n-model-2.0.pom 2K downloaded Downloading: http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.0. 4/plexus-utils-1.0.4.pom 6K downloaded Downloading: http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-container- /1.0.3/plexus-containers-1.0.3.pom 492b downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven-settings/2.0/m aven-settings-2.0.pom 1K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven-core/2.0/maven -core-2.0.pom 5K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/wagon/wagon-file/1.0 -alpha-5/wagon-file-1.0-alpha-5.pom 5K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven-plugin-paramet er-documenter/2.0/maven-plugin-parameter-documenter-2.0.pom 1K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/wagon/wagon-http-lig htweight/1.0-alpha-5/wagon-http-lightweight-1.0-alpha-5.pom 5K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/reporting/maven-repo rting-api/2.0/maven-reporting-api-2.0.pom 1K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/reporting/maven-repo rting/2.0/maven-reporting-2.0.pom 504b downloaded Downloading: http://repo1.maven.org/maven2/doxia/doxia-sink-api/1.0-alpha-4/doxi a-sink-api-1.0-alpha-4.pom 1K downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven-error-diagnost ics/2.0/maven-error-diagnostics-2.0.pom 812b downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/maven-plugin-registr y/2.0/maven-plugin-registry-2.0.pom 1K downloaded Downloading: http://repo1.maven.org/maven2/commons-cli/commons-cli/1.0/commons-c li-1.0.pom 2K downloaded Downloading: http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-interactiv ity-api/1.0-alpha-4/plexus-interactivity-api-1.0-alpha-4.pom 6K downloadedDownloading: http://repo1.maven.org/maven2/org/apache/maven/maven-monitor/2.0/ma ven-monitor-2.0.pom 400b downloaded Downloading: http://repo1.maven.org/maven2/org/apache/maven/wagon/wagon-ssh/1.0- alpha-5/wagon-ssh-1.0-alpha-5.pom 6K downloaded Downloading: http://repo1.maven.org/maven2/com/jcraft/jsch/0.1.23/jsch-0.1.23.po m 485b downloaded Downloading: http://repo1.maven.org/maven2/org/codehaus/plexus/plexus-utils/1.1/ plexus-utils-1.1.jar 164K downloaded [INFO] [help:describe] [INFO] Searching repository for plugin with
Plugin or not plugin : maven-artifact-manager
Hi all, (I hesitated on posting this on the developer list) So, I tried hacking the SnapshotTransformation class to be able to configure the use of the local time instead of UTC if wanted. After some times trying to install the jar (mvn install) and test it with a mvn deploy on some other project, without any changes. I finally realized the class that was used was the one in the jar in $M2_HOME/lib. So, for my knowlegde: actually code the one from the maven-artifact-manager project are no use from the local repository, right? Is it the very same code, just packaged differently? Thanks a lot. Cheers.
Re: maven2 jira plugin?
Rémy Sanlaville wrote: Because we already have a plugin that generates a report from an SCM system, namely maven-changelog-plugin. Yes but the reports are completely different : - maven-changes-plugin : http://maven.apache.org/plugins/maven-changes-plugin/changes-report.html - maven-changelog-plugin : http://maven.apache.org/plugins/maven-changelog-plugin/changelog.html This improvement generate the same report as maven-changes-plugin not maven-changelog-plugin. I'm sorry but I still don't understand the problem and what maven community can proposed for user who want this feature (changes-report generated from SCM comments). Rémy The proposed plugin did not fit well into either maven-changes-plugin or maven-changelog-plugin. The author of the plugin has since approached the Mojo project at codehaus. The plugin is currently an enhancement request there: http://jira.codehaus.org/browse/MOJO-1026 -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[ANN] Maven Plugin Tools 2.4 Released
The Maven team is pleased to announce the release of the Maven Plugin Tools, version 2.4 The Maven Plugin Tools contains the necessary tools to be able to produce Maven Plugins in a variety of languages. Maven Plugin: http://maven.apache.org/plugins/maven-plugin-plugin/ Maven Plugin Tools: http://maven.apache.org/plugin-tools/maven-plugin-tools-ant/ http://maven.apache.org/plugin-tools/maven-plugin-tools-api/ http://maven.apache.org/plugin-tools/maven-plugin-tools-beanshell/ http://maven.apache.org/plugin-tools/maven-plugin-tools-java/ http://maven.apache.org/plugin-tools/maven-plugin-tools-javadoc/ http://maven.apache.org/plugin-tools/maven-plugin-tools-model/ Note: the groupId of tools becomes org.apache.maven.plugin-tools. You can run mvn -up to get the latest version of the plugin, or specify the version in your project's plugin configuration: http://maven.apache.org/plugins/maven-plugin-plugin/plugin-info.html Release Notes - Maven 2.x Plugin Tools - Version 2.4 ** Sub-task * [MPLUGIN-66] - Add unit test ** Bug * [MPLUGIN-28] - Error of goal value in Plugin documentation generation * [MPLUGIN-30] - dependency:analyze shows errors * [MPLUGIN-35] - Generated documentation for @phase is misleading * [MPLUGIN-43] - Adding validation in PluginXdocGenerator class? * [MPLUGIN-45] - Plugin dependencies are not put in generated plugin.xml * [MPLUGIN-46] - [maven-plugin-testing-harness-1.0-beta-1] AbstractMojoTestCase.extractPluginConfiguration expects plugin configuration directly under plugin (configuration under executions/execution doesn't work) * [MPLUGIN-58] - File Parameter Evaluation * [MPLUGIN-59] - [maven-plugin-testing-harness] Clean the code * [MPLUGIN-60] - MavenProjectStub uses immutable collections for modifiable data * [MPLUGIN-62] - Exclude read-only components from plugin goal documentation * [MPLUGIN-65] - [PATCH] NPE in PluginXDocGenerator while creating plugin site * [MPLUGIN-71] - Make JavaMojoDescriptorExtractor extract class-level deprecated tag * [MPLUGIN-73] - PluginXdocGenerator fails to decode javadoc inline tags * [MPLUGIN-76] - Fixed file encoding employed by PluginXDocGenerator * [MPLUGIN-78] - Fix german localization * [MPLUGIN-79] - Fix detection of JDK requirement * [MPLUGIN-80] - Detection of report goals always fails due to class loader separation * [MPLUGIN-83] - POM snippet for plugin usage via pluginManagement is missing plugins container * [MPLUGIN-85] - Add missing whitespace between words on mojo description page * [MPLUGIN-86] - Test for empty mojo description in XDoc generator does not cover empty string * [MPLUGIN-88] - Fix punctuation for description of mojo attributes * [MPLUGIN-91] - misleading icon on list of goals ** Improvement * [MPLUGIN-11] - add an introduction to plugin configuration in plugin report * [MPLUGIN-13] - Provide Automated Documentation for a Plugin That Provides a Report * [MPLUGIN-38] - Upgrade to doxia 1.0-alpha-9 * [MPLUGIN-53] - Plugin descriptor extractor crashes on certain types of Java source files * [MPLUGIN-63] - Add since column in the parameters table * [MPLUGIN-64] - Beanshell extractor does not handle parameter default value * [MPLUGIN-67] - Document somewhere the minimum version of maven required by the plugin * [MPLUGIN-68] - Make generated mojo description valid XHTML * [MPLUGIN-70] - Make plugin highlight deprecated goals in the plugin overview * [MPLUGIN-72] - Add german translation * [MPLUGIN-75] - Internationalize PluginXdocGenerator * [MPLUGIN-77] - Add german translation * [MPLUGIN-87] - Replace None with something that is better understandable without context * [MPLUGIN-90] - Refactor makeValidHtml into PluginUtils for better reusage ** New Feature * [MPLUGIN-40] - All plugins should by default have an auto-generated goal 'help' * [MPLUGIN-81] - Handle Mojo annotations as Javadoc taglets to make better javadoc ** Task * [MPLUGIN-69] - Be consistent about physical/logical formatting tags * [MPLUGIN-74] - Explicitly control layout of tables generated for parameters of mojo description * [MPLUGIN-82] - Fix test for javadoc tools * [MPLUGIN-84] - Update to Plexus Utils 1.5+ * [MPLUGIN-89] - Restore compat with Java 1.4 Enjoy, -The Maven team - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Versioning conflict in mvn and eclipse:to-maven plugin
answered to your other thread about it. You need to use dependencyManagement in maven 2.0.9+ to force the versions when Maven doesnt resolve the ranges as Eclipse expects I will post soon the material from the tutorial I gave at EclipseCON covering that and other issues with Maven and OSGi http://www.jroller.com/carlossg/entry/letters_from_eclipsecon On Tue, Mar 18, 2008 at 1:13 PM, Apaar Trivedi [EMAIL PROTECTED] wrote: I have looked into this a bit more and it appears that the problem is with the qualifiers getting added to the versions of the artifacts deployed by the eclipse:to-maven target. The solution involves allowing the 'stripQualifier' parameter to be exposed in the plugin, here is a note I sent to the dev list: We need one thing parameterized on the EclipseToMavenMojo.java in the maven-eclipse-plugin which should be parameterized anyway. In the call to osgiVersionToMavenVersion, it only allows 'false' to be passed in for the 'strip qualifier' parameter. While the make-artifacts (which extends to-maven) target allows you to strip the qualifier, this is not a parameter that can be used in the to-maven target. This is a problem because using 'to-maven' provides artifacts with the proper names but the dependecies do not resolve due to the qualifiers on the versions. While make-artifacts provides dependecies that resolve but the naming convention of the groupId's and artifactId's is incorrect. Just a parameter -DstripQualifer that gets passed in to the call to osgiVersionToMavenVersion( String version, String forcedQualifier, boolean stripQualifier ) would be perfect. Thank you Apaar -Original Message- From: Apaar Trivedi [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2008 1:28 PM To: users@maven.apache.org Subject: Versioning conflict in mvn and eclipse:to-maven plugin Hey guys, i believe there is a bug in either the way versions for dependencies are matched or in the way the eclipse:to-maven plugin works. When I run the eclipse:to-maven target, my brand new repository is populated with eclipse plugins and nothing else. I attempt to build a project which depends on these dependencies, but the dependencies do not resolve. One of the eclipse plugins depends on another one that is within version range [3.3.0,4.00). The dependecny i have to satisfy this version is 3.3.0-3.3.0-I20070605-0010. But this is not acceptable, yielding this error: org.apache.maven.lifecycle.LifecycleExecutionException: Couldn't find a version in [3.3.0-I20070605-0010, 3.2.0-I20060605-1400] to match range [3.3.0,4.0.0) I understand that maven might desire some sort of special versioning in the form of x.y.z, in which case the eclipse:to-maven plugin should setup the pom's correctly (set the versions in an acceptable manner.) If maven does not have this hard and fast version requirement, shouldn't it accept the version 3.3.0-I20070605-0010, 3.2.0-I20060605-1400 to be within 3.3.0-4.0.0? Thank you Apaar Trivedi Consultant Blue Fish Development Group http://www.bluefishgroup.com http://www.bluefishgroup.com/ Blue Fish is Hiring! Check out www.bluefishgroup.com/careers http://www.bluefishgroup.com/careers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2]dbunit and hmb2ddl errors trying to unit test.
I want to create a core.jar that I can put all my model and DAO object that
I can use dbunit to test during my build. I have been combing through the
net all day trying examples that say they work but have no luck getting this
to function.
*I have a test persistance.xml in /src/test/resources/*
*?xml version=1.0 encoding=UTF-8?
persistence xmlns=http://java.sun.com/xml/ns/persistence;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://java.sun.com/xml/ns/persistence
http://java.sun.com/xml/ns/persistence/persistence_1_0.xsd;
version=1.0
persistence-unit name=hibernate-hsqldb
providerorg.hibernate.ejb.HibernatePersistence/provider
jar-file${project.build.directory}/classes/jar-file
properties
property name=hibernate.dialect value=
org.hibernate.dialect.HSQLDialect/
property name=hibernate.connection.driver_class value=
org.hsqldb.jdbcDriver/
property name=hibernate.connection.url
value=jdbc:hsqldb:./
property name=hibernate.connection.username value=sa/
property name=hibernate.connection.password value=/
property name=hibernate.hbm2ddl.auto value=create-drop/
property name=hibernate.show_sql value=true/
property name=hibernate.format_sql value=true/
property name=use_sql_comments value=true/
/properties
/persistence-unit
/persistence
*
*Then I also have my dbunit and hibernate3-maven plugins:*
*plugin
groupIdorg.codehaus.mojo/groupId
artifactIdhibernate3-maven-plugin/artifactId
version2.0-alpha-2/version
configuration
components
component
namehbm2ddl/name
implementationannotationconfiguration/implementation
/component
/components
componentProperties
droptrue/drop
jdk5true/jdk5
ejb3true/ejb3
propertyfiletarget/test-classes/jdbc.properties/propertyfile
outputfilenameschema.sql/outputfilename
outputDirectory
hbm2javatarget/test-classes/hbm2java
hbm2ddltarget/test-classes/hbm2ddl
/outputDirectory
skip${maven.test.skip}/skip
/componentProperties
/configuration
executions
execution
phaseprocess-test-resources/phase
goals
goalhbm2ddl/goal
/goals
/execution
/executions
dependencies
dependency
groupId${jdbc.groupId}/groupId
artifactId${jdbc.artifactId}/artifactId
version${jdbc.version}/version
/dependency
/dependencies
/plugin
plugin
groupIdorg.codehaus.mojo/groupId
artifactIddbunit-maven-plugin/artifactId
version1.0-beta-1/version
configuration
dataTypeFactoryName${dbunit.dataTypeFactoryName
}/dataTypeFactoryName
driver${jdbc.driverClassName}/driver
username${jdbc.username}/username
password${jdbc.password}/password
url${jdbc.url}/url
src${basedir}/src/test/resources/sample-data.xml/src
type${dbunit.operation.type}/type
schema${dbunit.schema}/schema
skip${maven.test.skip}/skip
verbose2/verbose
/configuration
executions
execution
phasetest-compile/phase
goals
goaloperation/goal
/goals
/execution
/executions
dependencies
dependency
groupId${jdbc.groupId}/groupId
artifactId${jdbc.artifactId}/artifactId
version${jdbc.version}/version
/dependency
/dependencies
/plugin
*
*when I run mvn hibernate3:hbm2ddl -P hsqldb -e -X, I get the following
trace:*
*[DEBUG] org.hibernate:jtidy:jar:r8-20060801:runtime (selected for
runtime)
[DEBUG] hsqldb:hsqldb:jar:1.8.0.7:compile (selected for compile)
[DEBUG] log4j:log4j:jar:1.2.14:runtime (selected for runtime)
[DEBUG] Configuring mojo '
org.codehaus.mojo:hibernate3-maven-plugin:2.0-alpha-2:hbm2ddl' --
[DEBUG] (f) componentProperties =
RE: enforcer-plugin causes multimodule project to fail
I haven't tried the test yet, but I'd be willing to bet this is a maven core issue and not the plugin itself. Either way, I intend to resume working on the enforcer ASAP. I've been working on 2.0.9 and staged a release candidate today, so I should have time to finish the enforcer. -Original Message- From: Martin Höller [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2008 7:09 AM To: Maven Users List Subject: enforcer-plugin causes multimodule project to fail Hi all! I stumbled over a problem with the maven-enforcer-plugin (tested with 1.0-alpha-3 and 1.0-SNAPSHOT): when a new multi-module project is created and the m-enforcer-p is used, maven fails with a Failed to resolve artifact error. This only happens when the new artifacts are not already in any configured repository. I already created a Jira issue for this with a test project attached: http://jira.codehaus.org/browse/MENFORCER-42 Anybody else who has similar problems with the enforcer? btw: according to the SVN repository some people are working on the plugin. Are there any plans to release a new version in the near future? regards, - martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Using the maven-dependency-plugin
What happens for the subsequent executions? Can you paste your pom? Why do you have multiple executions? The unpack-dependencies can take a list of dependencies and each one can be unpacked into different folders (the output directory is configurable at the artifactItem level too) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2008 3:10 PM To: users@maven.apache.org Subject: Using the maven-dependency-plugin Hi, I am using the maven-dependency-plugin unpack-dependencies to unpack the dependencies into some directory in my target directory. When i have multiple executions, the first unpack-dependencies execution unpacks the junit jar by default into my output directory. This does not happen for the subsequent executions. Any ideas why this happens? I have enabled the excludeTrasitive flag. Thanks, Shalini. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using the maven-dependency-plugin
I have multiple executions because i want 2 different archives to be
created with the same dependencies, but with different set of files. As
in, i exclude some in one and include some in the other.
I have attached my pom.xml herewith.
Thanks,
Shalini.
Brian E. Fox wrote:
What happens for the subsequent executions? Can you paste your pom? Why
do you have multiple executions? The unpack-dependencies can take a list
of dependencies and each one can be unpacked into different folders (the
output directory is configurable at the artifactItem level too)
-Original Message-
From: [EMAIL PROTECTED]
[mailto:[EMAIL PROTECTED]
Sent: Tuesday, March 18, 2008 3:10 PM
To: users@maven.apache.org
Subject: Using the maven-dependency-plugin
Hi,
I am using the maven-dependency-plugin unpack-dependencies to unpack
the dependencies into some directory in my target directory. When i have
multiple executions, the first unpack-dependencies execution unpacks the
junit jar by default into my output directory. This does not happen for
the subsequent executions. Any ideas why this happens?
I have enabled the excludeTrasitive flag.
Thanks,
Shalini.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
?xml version=1.0?
project
parent
artifactIdmyProj/artifactId
groupIdorg.modules.myProj/groupId
version10.0-SNAPSHOT/version
/parent
modelVersion4.0.0/modelVersion
groupIdorg.modules.myProj.module1/groupId
artifactIdmodule1/artifactId
nameModule 1 - blah blah/name
build
plugins
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-dependency-plugin/artifactId
executions
execution
idds_unpack-dependencies/id
phasepackage/phase
goals
goalunpack-dependencies/goal
/goals
configuration
includes**/*.class,**/*.properties/includes
excludes**/XA.class,**/CP.class,**/DM.class/excludes
outputDirectorysrc/main/java/__ds_archive/outputDirectory
overWriteSnapshotstrue/overWriteSnapshots
excludeTransitivetrue/excludeTransitive
/configuration
/execution
execution
idcp_unpack-dependencies/id
phasepackage/phase
goals
goalunpack-dependencies/goal
/goals
configuration
includes**/*.class,**/*.properties/includes
excludes**/XA.class,**/DM.class,**/DS.class/excludes
outputDirectorysrc/main/java/__cp_archive/outputDirectory
overWriteSnapshotstrue/overWriteSnapshots
excludeTransitivetrue/excludeTransitive
/configuration
/execution
/executions
/plugin
/plugins
/build
dependencies
dependency
groupIdorg.modules.myProj.module2/groupId
artifactIdmodule2/artifactId
version${project.parent.version}/version
/dependency
dependency
groupIdorg.modules.myProj.module3/groupId
artifactIdmodule3/artifactId
version${project.parent.version}/version
/dependency
/dependencies
/project
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using the maven-dependency-plugin
The outcome of a mvn install is the following: $ ls src/main/java/__ds_archive com junit META-INF org $ ls src/main/java/__cp_archive com META-INF As you can see from above, the 2 extra junit packages have been unpacked in the case of __ds_archive from nowhere. The dependencies mentioned in the dependencies list does not have a transitive dependency on junit also. Even then, it has been unpacked. Brian E. Fox wrote: What happens for the subsequent executions? Can you paste your pom? Why do you have multiple executions? The unpack-dependencies can take a list of dependencies and each one can be unpacked into different folders (the output directory is configurable at the artifactItem level too) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2008 3:10 PM To: users@maven.apache.org Subject: Using the maven-dependency-plugin Hi, I am using the maven-dependency-plugin unpack-dependencies to unpack the dependencies into some directory in my target directory. When i have multiple executions, the first unpack-dependencies execution unpacks the junit jar by default into my output directory. This does not happen for the subsequent executions. Any ideas why this happens? I have enabled the excludeTrasitive flag. Thanks, Shalini. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Profiles and Dependencies in Maven ANT Task
you can try the example:
plugin
artifactIdmaven-antrun-plugin/artifactId
executions
execution
idstart-hsqldb/id
phasesite/phase
goals
goalrun/goal
/goals
/execution
/executions
configuration
tasks
taskdef
resource=net/sf/antcontrib/antcontrib.properties/
if
equals
arg1=${unit-test} arg2=0 /
then
delete
fileset dir=${basedir}/target/test-classes
include name=**/*.class/
exclude name=**/SignonFunTest.class/
/fileset
/delete
/then
/if
java
classname=org.hsqldb.Server fork=false
arg line=-database.0
signon -dbname.0 signon/
!--classpath
pathelement
path=D:\Workspace\signon-frank-google\src\main\hsqldb\hsqldb.jar/
/classpath--
/java
/tasks
/configuration
dependencies
dependency
groupIdant-contrib/groupId
artifactIdant-contrib/artifactId
version1.0b2/version
/dependency
dependency
groupIdhsqldb/groupId
artifactIdhsqldb/artifactId
version1.8.0.7/version
/dependency
/dependencies
/plugin
2008/3/19, Marco Sandrini [EMAIL PROTECTED]:
Hi!
I know that the attribute profiles in task artifact:dependencies is not yet
supported. I was though wondering is there a mechanism to specify the
correct property/ies in the rest of the ant file so that the correct profile
would be picked up by the dependency task.
In other words I'd like to have in my build.xml
property name=myprop value=true/
and in pom.xml
.
profile
idadditional_dependency_profile/id
activation
property
namemyprop/name
valuetrue/value
/property
/activation
dependencies
extra dependencies here
/dependencies
/profile
I noticed that setting a profile to activeByDefault works, i.e. the
dependency task picks up the extra dependencies defined in the profile, but,
as said, I could not make the property-activated profile do my bidding.
Thanks in advance for your help,
regards,
Marco Sandrini
--
View this message in context:
http://www.nabble.com/Profiles-and-Dependencies-in-Maven-ANT-Task-tp16125102s177p16125102.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Using the maven-dependency-plugin
Are there any dependencies listed in the parent of the attached pom? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2008 8:24 PM To: Maven Users List Subject: Re: Using the maven-dependency-plugin The outcome of a mvn install is the following: $ ls src/main/java/__ds_archive com junit META-INF org $ ls src/main/java/__cp_archive com META-INF As you can see from above, the 2 extra junit packages have been unpacked in the case of __ds_archive from nowhere. The dependencies mentioned in the dependencies list does not have a transitive dependency on junit also. Even then, it has been unpacked. Brian E. Fox wrote: What happens for the subsequent executions? Can you paste your pom? Why do you have multiple executions? The unpack-dependencies can take a list of dependencies and each one can be unpacked into different folders (the output directory is configurable at the artifactItem level too) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2008 3:10 PM To: users@maven.apache.org Subject: Using the maven-dependency-plugin Hi, I am using the maven-dependency-plugin unpack-dependencies to unpack the dependencies into some directory in my target directory. When i have multiple executions, the first unpack-dependencies execution unpacks the junit jar by default into my output directory. This does not happen for the subsequent executions. Any ideas why this happens? I have enabled the excludeTrasitive flag. Thanks, Shalini. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Customizing Build order
Maven starts with the ordering listed in the poms (A and its children, then B and its children, etc) unless there is a dependency. If it sees a dependency, then it will automatically reorder by pushing down modules that have a dependency so they build after their dep. I'm wondering why the order matters if you don't have a dependency listed (I'm assuming you don't or it would be ordered already). -Original Message- From: amit kumar [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2008 4:42 AM To: Maven Users List Subject: Customizing Build order Hi, I have a multi-module project with the following structure. Root -A -A1 -A2 -A3 -B -B1 -B2 -B3 -B4 In the Root's pom i have mentioned my modules as: moduleA/module moduleB/module Now is there a way that I can change the normal build order(which is) -Root -A -A1 -A2 -A3 -B -B1 -B2 -B3 -B4 to something like -Root -A -A1 -A2 -B -B1 -B2 -A3 -B4 It is actually a requirement. But I doubt that there is a possibility that the CVS structure itself is not competent enough then to handle inter-module dependencies. Any inputs? Thanks and regards, Amit Kumar - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: mvn 2.0.8
It seems to me like the paths or m2_home env vars are wrong. It looks like it's executing a class from 2.0.8 against the 2.0.7 uber.jar. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2008 4:23 PM To: Maven Users List Subject: Re: mvn 2.0.8 Are you sure you're running the mvn binary you think you're running? Try ./mvn --version instead. I'd assume you failed to update your PATH etc as required. Wayne On 3/18/08, Michael Clark [EMAIL PROTECTED] wrote: Hi, I have been using 2,.0.7 for some time and I'm very happy I just tried a quick update to 2.0.8 and am having no luck. Any suggestions? I keep getting [EMAIL PROTECTED]:~/cc/maven-2.0.8 mvn --version Exception in thread main java.lang.IllegalAccessError: tried to access field hidden.org.codehaus.plexus.util.Os.OS_NAME from class org.apache.maven.cli.MavenCli at org.apache.maven.cli.MavenCli.clinit(MavenCli.java:76) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Using the maven-dependency-plugin
The top level parent's pom has a dependency listed on junit. Does this affect? Brian E. Fox wrote: Are there any dependencies listed in the parent of the attached pom? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2008 8:24 PM To: Maven Users List Subject: Re: Using the maven-dependency-plugin The outcome of a mvn install is the following: $ ls src/main/java/__ds_archive com junit META-INF org $ ls src/main/java/__cp_archive com META-INF As you can see from above, the 2 extra junit packages have been unpacked in the case of __ds_archive from nowhere. The dependencies mentioned in the dependencies list does not have a transitive dependency on junit also. Even then, it has been unpacked. Brian E. Fox wrote: What happens for the subsequent executions? Can you paste your pom? Why do you have multiple executions? The unpack-dependencies can take a list of dependencies and each one can be unpacked into different folders (the output directory is configurable at the artifactItem level too) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2008 3:10 PM To: users@maven.apache.org Subject: Using the maven-dependency-plugin Hi, I am using the maven-dependency-plugin unpack-dependencies to unpack the dependencies into some directory in my target directory. When i have multiple executions, the first unpack-dependencies execution unpacks the junit jar by default into my output directory. This does not happen for the subsequent executions. Any ideas why this happens? I have enabled the excludeTrasitive flag. Thanks, Shalini. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Question on using maven-jar-plugin
I use the maven-jar-plugin in my module, as follows:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-jar-plugin/artifactId
executions
execution
idds_build-jar/id
phasepackage/phase
goals
goaljar/goal
/goals
configuration
finalNameds/finalName
outputDirectory${project.build.directory}/outputDirectory
includes
includesrc/main/java/__ds_archive/com/**/*.class/include
includesrc/main/java/__ds_archive/**/*.properties/include
/includes
excludes
excludesrc/main/java/__ds_archive/junit/**/*.*/exclude
exclude${project.build.directory}/__ds_archive/org/**/*.*/exclude
/excludes
/configuration
/execution
/executions
/plugin
When i do a mvn install, the ds.jar built out of this does not include
any of the classes specified in the includes clause nor does it
exclude any. I get a warning message :
[INFO] [jar:jar {execution: __ds}]
[WARNING] JAR will be empty - no content was marked for inclusion!
[INFO] [jar:jar {execution: ds_build-jar}]
Am i missing something here?
Please let me know.
Thanks in advance,
Shalini.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Using the maven-dependency-plugin
Absolutely. That dependency is inherited by this module and you are asking the plugin to unpack all dependencies. You can exclude artifacts by name or group (among other things) to get down to the list you want. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2008 9:36 PM To: Maven Users List Subject: Re: Using the maven-dependency-plugin The top level parent's pom has a dependency listed on junit. Does this affect? Brian E. Fox wrote: Are there any dependencies listed in the parent of the attached pom? -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2008 8:24 PM To: Maven Users List Subject: Re: Using the maven-dependency-plugin The outcome of a mvn install is the following: $ ls src/main/java/__ds_archive com junit META-INF org $ ls src/main/java/__cp_archive com META-INF As you can see from above, the 2 extra junit packages have been unpacked in the case of __ds_archive from nowhere. The dependencies mentioned in the dependencies list does not have a transitive dependency on junit also. Even then, it has been unpacked. Brian E. Fox wrote: What happens for the subsequent executions? Can you paste your pom? Why do you have multiple executions? The unpack-dependencies can take a list of dependencies and each one can be unpacked into different folders (the output directory is configurable at the artifactItem level too) -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2008 3:10 PM To: users@maven.apache.org Subject: Using the maven-dependency-plugin Hi, I am using the maven-dependency-plugin unpack-dependencies to unpack the dependencies into some directory in my target directory. When i have multiple executions, the first unpack-dependencies execution unpacks the junit jar by default into my output directory. This does not happen for the subsequent executions. Any ideas why this happens? I have enabled the excludeTrasitive flag. Thanks, Shalini. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
how to generate report of cobertura in integration-test
cobertura:cobertura report when package war deploy to jetty - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Customizing Build order
I've never tried this exact scenario, but couldn't you also do this in the root pom and remove A3 and B4 from the A and B poms respectively? moduleA/module moduleB/module moduleA/A3/module moduleB/B4/module Of course this assumes that previous modules don't depend on A3 or B4. Chris On Tue, Mar 18, 2008 at 7:19 PM, Brian E. Fox [EMAIL PROTECTED] wrote: Maven starts with the ordering listed in the poms (A and its children, then B and its children, etc) unless there is a dependency. If it sees a dependency, then it will automatically reorder by pushing down modules that have a dependency so they build after their dep. I'm wondering why the order matters if you don't have a dependency listed (I'm assuming you don't or it would be ordered already). -Original Message- From: amit kumar [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 18, 2008 4:42 AM To: Maven Users List Subject: Customizing Build order Hi, I have a multi-module project with the following structure. Root -A -A1 -A2 -A3 -B -B1 -B2 -B3 -B4 In the Root's pom i have mentioned my modules as: moduleA/module moduleB/module Now is there a way that I can change the normal build order(which is) -Root -A -A1 -A2 -A3 -B -B1 -B2 -B3 -B4 to something like -Root -A -A1 -A2 -B -B1 -B2 -A3 -B4 It is actually a requirement. But I doubt that there is a possibility that the CVS structure itself is not competent enough then to handle inter-module dependencies. Any inputs? Thanks and regards, Amit Kumar - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Adding Resources to Jar
I tried to create sample project and added an external resource (xml file) to test what you said. mvn archetype:create \ -DarchetypeGroupId=org.apache.maven.archetypes \ -DgroupId=com.mycompany.app \ -DartifactId=my-app Result : The xml is not copied in the same directory in the Jar (src/ main/java/com/mycompany/app/) , but is instead copied in the base directory. Here is my pom.xml: == project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http:// www.w3.org/2001/XMLSchema-instance xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http:// maven.apache.org/maven-v4_0_0.xsd modelVersion4.0.0/modelVersion groupIdcom.mycompany.app/groupId artifactIdmy-app/artifactId packagingjar/packaging version1.0-SNAPSHOT/version namemy-app/name urlhttp://maven.apache.org/url build resources resource directorysrc/main/java/com/mycompany/app//directory filteringfalse/filtering includes include**/*.xml/include /includes /resource /resources /build dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version scopetest/scope /dependency /dependencies /project === Please help :/ Pierre On 17-Mar-08, at 6:47 PM, Jeff MAURY wrote: You must not define an outputdirectory but multiple resource directories. As soon as you declare resource directories in your pom, the files stored in thoses directories will be included verbatim (or filtered if you want) in your outputdirectory and jar file. Jeff MAURY 2008/3/17 Pierre-Alexandre Lacerte [EMAIL PROTECTED]: The problem is that I can't define multiple outputDirectory in my pom, corresponding to the location of my different files. Ex: With this in my pom : resource directorysrc/dats/common/businessobjects//directory filteringtrue/filtering includes include**/*.xml/include /includes /resource The files are copied in the base directory of my Jar, and not in the dats/common/businessobjects/ directory. I already have 1 value of outputDirectory corresponding to the directory where I want to send my compiled classes. On 17-Mar-08, at 6:22 PM, Jeff MAURY wrote: You must define multiple resource directories in your pom. Jeff MAURY On Mon, Mar 17, 2008 at 10:40 PM, Pierre-Alexandre Lacerte [EMAIL PROTECTED] wrote: Hi, I have many resources (log4j properties, hibernate hbm.xml files, etc.) in different directories in my project. I would like to copy them in the same path in my packaged Jar file. Is it possible? I can't find a way to define multiple outputDirectory values. Thanks Pierre --- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- La mélancolie c'est communiste Tout le monde y a droit de temps en temps La mélancolie n'est pas capitaliste C'est même gratuit pour les perdants La mélancolie c'est pacifiste On ne lui rentre jamais dedans La mélancolie oh tu sais ça existe Elle se prend même avec des gants La mélancolie c'est pour les syndicalistes Il faut juste sa carte de permanent Miossec (2006) http://www.jeffmaury.com http://riadiscuss.jeffmaury.com -- La mélancolie c'est communiste Tout le monde y a droit de temps en temps La mélancolie n'est pas capitaliste C'est même gratuit pour les perdants La mélancolie c'est pacifiste On ne lui rentre jamais dedans La mélancolie oh tu sais ça existe Elle se prend même avec des gants La mélancolie c'est pour les syndicalistes Il faut juste sa carte de permanent Miossec (2006) http://www.jeffmaury.com http://riadiscuss.jeffmaury.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to checkout the Project from cvs in Maven2.0.7 without using eclipse.
Hi, I am working on the maven tool for my project ,where I have to checkout from CVS and I want to ask for CVS user id and password from the user while checkingout the project.This process I want to do dynamically to checkout multiple projects. I am new user of maven ,Pleases help me out to resove this issue. -- Regads, Sowmya.R - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to checkout the Project from cvs in Maven2.0.7 without using eclipse.
Take a look at the SCM plugin: http://maven.apache.org/scm/plugins/examples/bootstrapping-with-pom.html Wayne On 3/18/08, Sowmya. R [EMAIL PROTECTED] wrote: Hi, I am working on the maven tool for my project ,where I have to checkout from CVS and I want to ask for CVS user id and password from the user while checkingout the project.This process I want to do dynamically to checkout multiple projects. I am new user of maven ,Pleases help me out to resove this issue. -- Regads, Sowmya.R - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
