[ANN] Maven Archetype version 2.0-alpha-5 Released
The Maven team is pleased to announce the release of the Maven Archetype components version 2.0-alpha-5. Archetype is a Maven project templating toolkit. http://maven.apache.org/archetype/ Release Notes - Maven Archetype - Version 2.0-alpha-5 ** Bug * [ARCHETYPE-81] - Archetype not downloaded until pom is placed in working dir * [ARCHETYPE-89] - archetypeng:create doesn't use configured repos to find artifacts * [ARCHETYPE-110] - Maven archetype overwrites parent information * [ARCHETYPE-142] - catalog default location problem in CrawlRepositoryMojo * [ARCHETYPE-234] - archetype:crawl fails on large repositories (Too many open files) * [ARCHETYPE-235] - DefaultPomManager.mergePoms ignores ordering of plugins * [ARCHETYPE-243] - archetype:create-from-project generates xnl file, not xml * [ARCHETYPE-262] - Allow empty properties in generated pom.xml * [ARCHETYPE-270] - RemoteCatalogArchetypeDataSource leaves open wagon connection when archetype catalog retrieval fails * [ARCHETYPE-292] - both 1.0.X archetype.xml and 2.0.x archetype- metadata.xml descriptors are generated: only one is needed ** Improvement * [ARCHETYPE-61] - Configure distributionManagement for archetype * [ARCHETYPE-158] - Create a directory with name artiactId * [ARCHETYPE-162] - Prepend java package declaration to the java file path * [ARCHETYPE-192] - Property replacement for required properties * [ARCHETYPE-217] - mvn archetype:help should not require a pom * [ARCHETYPE-224] - Add Tapestry 5 Quickstart archetype to the list of internal archectypes * [ARCHETYPE-229] - Do not use hardcoded path to the build directory in create-from-project goal * [ARCHETYPE-237] - Provide schema for archetype descriptor * [ARCHETYPE-249] - Add Apache Camel WAR archetype to internal catalog * [ARCHETYPE-259] - Provide XSD schema for archetype-catalog.xml * [ARCHETYPE-272] - Change GMaven archetype to newer package name * [ARCHETYPE-281] - Update to plexus-velocity 1.1.8 and Velocity 1.5 * [ARCHETYPE-290] - recreate the internal catalogue to include new wiki page changes (the scalate archetypes) * [ARCHETYPE-291] - add old archetype support for integration-test * [ARCHETYPE-293] - generated archetype pom.xml should reference POM XML Schema * [ARCHETYPE-294] - provide a basic it in created archetype ** New Feature * [ARCHETYPE-47] - use an xml schema for archetype.xml Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: integration problem
i did it as you said but now it showing me following errors
C:\projectmvn archetype:generate -DarchetypeGroupId=org.richfaces.cdk
-Darchetyp
eArtifactId=maven-archetype-jsfwebapp -DarchetypeVersion=3.3.2-GA
-DgroupId=org.
docs.richfaces -DartifactId=jsf-app
-DarchetypeRepository=http://repository.jbos
s.org/maven2
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'archetype'.
[INFO]
[INFO] Building Maven Default Project
[INFO]task-segment: [archetype:generate] (aggregator-style)
[INFO]
[INFO] Preparing archetype:generate
[INFO] No goals needed for project - skipping
[INFO] Setting property: classpath.resource.loader.class =
'org.codehaus.plexus
.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on = 'false'.
[INFO] Setting property: resource.loader = 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound = 'false'.
[INFO] [archetype:generate {execution: default-cli}]
[INFO] Generating project in Interactive mode
[INFO] Archetype defined by properties
Downloading:
http://repository.jboss.org/maven2/org/richfaces/cdk/maven-archetyp
e-jsfwebapp/3.3.2-GA/maven-archetype-jsfwebapp-3.3.2-GA.jar
[INFO] Unable to find resource
'org.richfaces.cdk:maven-archetype-jsfwebapp:jar:
3.3.2-GA' in repository maven-archetype-jsfwebapp-repo
(http://repository.jboss.
org/maven2)
Downloading:
http://repo1.maven.org/maven2/org/richfaces/cdk/maven-archetype-jsf
webapp/3.3.2-GA/maven-archetype-jsfwebapp-3.3.2-GA.jar
[INFO] Unable to find resource
'org.richfaces.cdk:maven-archetype-jsfwebapp:jar:
3.3.2-GA' in repository central (http://repo1.maven.org/maven2)
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] The desired archetype does not exist
(org.richfaces.cdk:maven-archetype-j
sfwebapp:3.3.2-GA)
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 6 seconds
[INFO] Finished at: Fri Apr 23 11:47:50 IST 2010
[INFO] Final Memory: 8M/21M
[INFO]
C:\project
--
View this message in context:
http://old.nabble.com/integration-problem-tp28337509p28337627.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: integration problem
Ah, my fault.
Try to use.
mvn archetype:generate -DarchetypeGroupId=org.richfaces.cdk
-DarchetypeArtifactId=maven-archetype-jsfwebapp
-DarchetypeVersion=3.3.2.GA -DgroupId=org.docs.richfaces
-DartifactId=jsf-app
-DarchetypeRepository=http://repository.jboss.org/maven2
Aleksey.
23.04.2010 10:21, pankjajain15 пишет:
i did it as you said but now it showing me following errors
C:\projectmvn archetype:generate -DarchetypeGroupId=org.richfaces.cdk
-Darchetyp
eArtifactId=maven-archetype-jsfwebapp -DarchetypeVersion=3.3.2-GA
-DgroupId=org.
docs.richfaces -DartifactId=jsf-app
-DarchetypeRepository=http://repository.jbos
s.org/maven2
[INFO] Scanning for projects...
[INFO] Searching repository for plugin with prefix: 'archetype'.
[INFO]
[INFO] Building Maven Default Project
[INFO]task-segment: [archetype:generate] (aggregator-style)
[INFO]
[INFO] Preparing archetype:generate
[INFO] No goals needed for project - skipping
[INFO] Setting property: classpath.resource.loader.class =
'org.codehaus.plexus
.velocity.ContextClassLoaderResourceLoader'.
[INFO] Setting property: velocimacro.messages.on = 'false'.
[INFO] Setting property: resource.loader = 'classpath'.
[INFO] Setting property: resource.manager.logwhenfound = 'false'.
[INFO] [archetype:generate {execution: default-cli}]
[INFO] Generating project in Interactive mode
[INFO] Archetype defined by properties
Downloading:
http://repository.jboss.org/maven2/org/richfaces/cdk/maven-archetyp
e-jsfwebapp/3.3.2-GA/maven-archetype-jsfwebapp-3.3.2-GA.jar
[INFO] Unable to find resource
'org.richfaces.cdk:maven-archetype-jsfwebapp:jar:
3.3.2-GA' in repository maven-archetype-jsfwebapp-repo
(http://repository.jboss.
org/maven2)
Downloading:
http://repo1.maven.org/maven2/org/richfaces/cdk/maven-archetype-jsf
webapp/3.3.2-GA/maven-archetype-jsfwebapp-3.3.2-GA.jar
[INFO] Unable to find resource
'org.richfaces.cdk:maven-archetype-jsfwebapp:jar:
3.3.2-GA' in repository central (http://repo1.maven.org/maven2)
[INFO]
[ERROR] BUILD FAILURE
[INFO]
[INFO] The desired archetype does not exist
(org.richfaces.cdk:maven-archetype-j
sfwebapp:3.3.2-GA)
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 6 seconds
[INFO] Finished at: Fri Apr 23 11:47:50 IST 2010
[INFO] Final Memory: 8M/21M
[INFO]
C:\project
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Eclipse plug-in as artifact
Hello! We are using Maven in the company and we are often heading issue how to put eclipse plug-in into Maven's repository. For example how to store org.mozilla.xulrunner.win32.win32.x86_1.9.2.0_201004211457.jar . We like the artifact, group ids and clasifiers. Eclipse doesn't use the '-' for separating such elements and we don't want to rename the file, because of further assembly process. We can't find the way how to change maven behaviour e.g. via configuration tag. Has the problem solution without renamig file? Thank you in advance for answer. Best Regards! Ivo Odchozí zpráva neobsahuje viry. Zkontrolováno AVG - www.avg.cz Verze: 9.0.814 / Virová báze: 271.1.1/2828 - Datum vydání: 04/22/10 08:31:00 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven project organization
Hey, I 'm thinking about the appropriate project structure for a coming multi module web application project. I would like to have it separated something like that: root-application webapp module1-web module1 module2-web module2 The root-application is the root-project (Surprise!!!), the webapp contains any web application wide source files, like the web.xml for example. Most of the source files are contained by the module projects. Any module has a web-project and the module project itself. Now I would like to have the webapp source files of the modules' web projects copied into the single destination WAR. Is there something like a best practice? What kind of packaging do I have to choose for the module-web projects? Thanks, Stephan
Re: [ANN] Maven Compiler Plugin 2.3 Released
The checksums on central shall be fixed now. My apologies to everyone. Milos On Wed, Apr 21, 2010 at 10:22 PM, Brett Porter br...@apache.org wrote: On 21/04/2010, at 11:13 PM, John Singleton wrote: Thanks, Brett. FWIW, I also noticed this problem with the 2.2 version of Compiler plugin, which was released a couple of weeks ago. Yes, they both use the same version of the shared component. It's being taken care of. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [ANN] Maven Compiler Plugin 2.3 Released
Hi! I just upgraded the project I'm working on and it worked fine. /Thomas On Fri, Apr 23, 2010 at 09:54, Milos Kleint mkle...@gmail.com wrote: The checksums on central shall be fixed now. My apologies to everyone. Milos On Wed, Apr 21, 2010 at 10:22 PM, Brett Porter br...@apache.org wrote: On 21/04/2010, at 11:13 PM, John Singleton wrote: Thanks, Brett. FWIW, I also noticed this problem with the 2.2 version of Compiler plugin, which was released a couple of weeks ago. Yes, they both use the same version of the shared component. It's being taken care of. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Thomas Sundberg M. Sc. in Computer Science Mobile: +46 70 767 33 15 Blog: http://thomassundberg.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven scm plugin: accurev scm provider
If you want to use the new version, take the code attached to issue, bump parent version to 1.3 and change the artifact version to 1.4-SNAPSHOT then build and install to your local repository. Then in your project pom add this as a dependency to the maven-scm-plugin as follows. build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-scm-plugin/artifactId version1.3/version dependencies dependency groupIdorg.apache.maven.scm/groupId artifactIdmaven-scm-provider-accurev/artifactId version1.4-SNAPSHOT/version /dependency /dependencies /plugin plugins /build On Wed, 21 Apr 2010 15:56:50 +0300, eyal edri eyal.e...@gmail.com wrote: Anyone has used accurev + scm plugin yet? i know issue 445 on the scm-accurev-provider should fix most problems once ver 1.4 is due, is there any way i can use the plugin in the meantime and test connection to the accurev server? thanks. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-metadata-central.xml is missing versions in local repo
Markku Saarela wrote: This can be caused by Artifactory if checksums does not match and you Artifactory is configured to fail if checksums doesn't match. Markku Hi, thank you for the suggestion, but our artifactory is configured to ignore and return generated checksums. Florian -- View this message in context: http://old.nabble.com/maven-metadata-central.xml-is-missing-versions-in-local-repo-tp28288000p28337643.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Thoughts on profiles [Virus checked]
Hi everybody! Just imagine we had a profiles definition in a pom.xml such as profile group=database type=manditory idMySQL/id ... as we know it ... /profile profile group=database type=manditory idOracle/id ... as we know it ... /profile profile group=implementation idmock/mock ... as we know it ... /profile profile group=environment idqualitycontrol23/id ... as we know it ... /profile with (obvious?) semantics, if a profile group is manditory and none is active, the build fails ... if more than one profile in a group is active, the build fails ... in project builds, where maven profiles are the main thing understood, selection of the 'right' profiles is crucial to project builds, but not really contained the project description. Command line selection of profiles, such as in hudson or aquivalent, is important project build knowledge, but so far not contained in the pom.xml Any comments, corrections, refusals, improvements, bashing, ... ? mit freundlichen Grüßen/best regards Wolfgang Schrecker ... it is difficult in practice to keep track of which variables in a program are allowed to be null. from Odersky,Spoon, Venners: Programming in Scala p. 283 -- -- Atos Worldline Processing GmbH Hahnstrasse 25 60528 Frankfurt/Main Germany Phone: +49 69/6657-1176 mailto:wolfgang.schrec...@atosorigin.com http://www.atosworldline.com Geschäftsführer: Erik Munk Koefoed Aufsichtsratsvorsitzender: Didier Dhennin Sitz der Gesellschaft: Frankfurt/Main Handelsregister: Frankfurt/Main HRB 40 417 -- Atos Worldline Processing GmbH Hahnstrasse 25 60528 Frankfurt/Main Germany Phone: +49 69/6657-1176 Fax : mailto: wolfgang.schrec...@atosorigin.com http://www.atosworldline.com Geschäftsführer: Erik Munk Koefoed Aufsichtsratsvorsitzender: Didier Dhennin Sitz der Gesellschaft: Frankfurt/Main Handelsregister: Frankfurt/Main HRB 40 417 * * * * * * * * L E G A LD I S C L A I M E R * * * * * * * * This e-mail is destined for the above mentioned recipient. In case you received this e-mail by accident, we would appreciate it if you could contact the sender and delete all copies stored on your computer. Please be aware that the security and confidentiality of electronic data transmitted by e-mail is not completely guaranteed and that data may be seen, copied, downloaded or changed by third persons during transmission. Atos Origin accepts no liability for the security and confidentiality of data and documents sent by e-mail. Please make sure that all important messages will be confirmed in writing by means of a telefax or a letter. * * * * * * * * L E G A LD I S C L A I M E R * * * * * * * *
AW: Maven Compiler Plugin - Excludes
Nothing special really... as you see no src/test/aspect in testSourceDirectory I only have, aspectj-maven-plugin in the build configuration but how it can only affect the testSourceDirectory, I don't know.while as I said for sourceDirectoy, sec/main/aspect is not in it and compiler plugin doesn't care about it... build sourceDirectoryC:\DEV\tmp\glassbox\glassbox\monitor\src\main\java/sourceDirectory scriptSourceDirectorysrc/main/scripts/scriptSourceDirectory testSourceDirectoryC:\DEV\tmp\glassbox\glassbox\monitor\src\test\java/testSourceDirectory outputDirectoryC:\DEV\tmp\glassbox\glassbox\monitor\target\classes/outputDirectory testOutputDirectoryC:\DEV\tmp\glassbox\glassbox\monitor\target\test-classes/testOutputDirectory resources resource mergeIdresource-2/mergeId directoryC:\DEV\tmp\glassbox\glassbox\monitor\src\main\resources/directory /resource /resources testResources testResource mergeIdresource-3/mergeId directoryC:\DEV\tmp\glassbox\glassbox\monitor\src\test\resources/directory /testResource /testResources directoryC:\DEV\tmp\glassbox\glassbox\monitor\target/directory finalNamemonitor-1.0.0-SNAPSHOT/finalName plugin groupIdorg.codehaus.mojo/groupId artifactIdaspectj-maven-plugin/artifactId executions execution goals goalcompile/goal goaltest-compile/goal /goals /execution /executions configuration source1.5/source target1.5/target encodingUTF-8/encoding /configuration dependencies dependency groupIdorg.aspectj/groupId artifactIdaspectjrt/artifactId version1.6.8/version /dependency dependency groupIdorg.aspectj/groupId artifactIdaspectjtools/artifactId version1.6.8/version /dependency /dependencies /plugin Telekom Deutschland GmbH Aufsichtsrat: Timotheus Höttges (Vorsitzender) Geschäftsführung: Niek Jan van Damme (Sprecher), Thomas Berlemann, Thomas Dannenfeldt, Albert Henn, Dr. Christian P. Illek, Dr. Bruno Jacobfeuerborn Handelsregister: Amtsgericht Bonn, HRB 59 19 Sitz der Gesellschaft: Bonn WEEE-Reg.-Nr.: DE60800328 -Ursprüngliche Nachricht- Von: Wayne Fay [mailto:wayne...@gmail.com] Gesendet: Mittwoch, 21. April 2010 22:43 An: Maven Users List Betreff: Re: Maven Compiler Plugin - Excludes Now in test-compile phase, compiler plugin discovers the src/test/aspect and wants to compile that also. This is a feature or bug I don't know What does mvn help:effective-pom reveal? You must be configuring something somewhere that is telling Maven to compile files in src/test/aspect. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: integration problem
ya i tried your command, but again foung following error -- 1) org.richfaces.framework:richfaces-api:jar:3.3.3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.richfaces.framework -DartifactId=ri chfaces-api -Dversion=3.3.3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.richfaces.framework -DartifactId=rich faces-api -Dversion=3.3.3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[u rl] -DrepositoryId=[id] Path to dependency: 1) org.docs.richfaces:jsf-app:war:3.3.3 2) org.richfaces.framework:richfaces-api:jar:3.3.3-SNAPSHOT 2) org.richfaces.framework:richfaces-impl:jar:3.3.3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.richfaces.framework -DartifactId=ri chfaces-impl -Dversion=3.3.3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.richfaces.framework -DartifactId=rich faces-impl -Dversion=3.3.3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[ url] -DrepositoryId=[id] Path to dependency: 1) org.docs.richfaces:jsf-app:war:3.3.3 2) org.richfaces.framework:richfaces-impl:jar:3.3.3-SNAPSHOT 3) org.richfaces.ui:richfaces-ui:jar:3.3.2.GA Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.richfaces.ui -DartifactId=richfaces -ui -Dversion=3.3.2.GA -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.richfaces.ui -DartifactId=richfaces-u i -Dversion=3.3.2.GA -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -Dreposito ryId=[id] Path to dependency: 1) org.docs.richfaces:jsf-app:war:3.3.3 2) org.richfaces.ui:richfaces-ui:jar:3.3.2.GA 4) el-impl:el-impl:jar:1.0 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=el-impl -DartifactId=el-impl -Dversion= 1.0 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=el-impl -DartifactId=el-impl -Dversion=1. 0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.docs.richfaces:jsf-app:war:3.3.3 2) el-impl:el-impl:jar:1.0 5) javax.faces:jsf-api:jar:1.2_12 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=javax.faces -DartifactId=jsf-api -Dvers ion=1.2_12 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=javax.faces -DartifactId=jsf-api -Dversio n=1.2_12 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.docs.richfaces:jsf-app:war:3.3.3 2) javax.faces:jsf-api:jar:1.2_12 6) javax.faces:jsf-impl:jar:1.2_12 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=javax.faces -DartifactId=jsf-impl -Dver sion=1.2_12 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=javax.faces -DartifactId=jsf-impl -Dversi on=1.2_12 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.docs.richfaces:jsf-app:war:3.3.3 2) javax.faces:jsf-impl:jar:1.2_12 -- 6 required artifacts are missing. for artifact: org.docs.richfaces:jsf-app:war:3.3.3 from the specified remote repositories: central (http://repo1.maven.org/maven2) [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 12 seconds [INFO] Finished at: Fri Apr 23 16:39:44 IST 2010 [INFO] Final Memory: 7M/18M [INFO] C:\sample\jsf-app -- View this message in context: http://old.nabble.com/integration-problem-tp28337509p28340212.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: integration problem
Please, send to me a command from console? Maven try to use SNAPSHOT versions. It's strange. 23.04.2010 15:39, pankjajain15 пишет: ya i tried your command, but again foung following error -- 1) org.richfaces.framework:richfaces-api:jar:3.3.3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.richfaces.framework -DartifactId=ri chfaces-api -Dversion=3.3.3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.richfaces.framework -DartifactId=rich faces-api -Dversion=3.3.3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[u rl] -DrepositoryId=[id] Path to dependency: 1) org.docs.richfaces:jsf-app:war:3.3.3 2) org.richfaces.framework:richfaces-api:jar:3.3.3-SNAPSHOT 2) org.richfaces.framework:richfaces-impl:jar:3.3.3-SNAPSHOT Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.richfaces.framework -DartifactId=ri chfaces-impl -Dversion=3.3.3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.richfaces.framework -DartifactId=rich faces-impl -Dversion=3.3.3-SNAPSHOT -Dpackaging=jar -Dfile=/path/to/file -Durl=[ url] -DrepositoryId=[id] Path to dependency: 1) org.docs.richfaces:jsf-app:war:3.3.3 2) org.richfaces.framework:richfaces-impl:jar:3.3.3-SNAPSHOT 3) org.richfaces.ui:richfaces-ui:jar:3.3.2.GA Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.richfaces.ui -DartifactId=richfaces -ui -Dversion=3.3.2.GA -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.richfaces.ui -DartifactId=richfaces-u i -Dversion=3.3.2.GA -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -Dreposito ryId=[id] Path to dependency: 1) org.docs.richfaces:jsf-app:war:3.3.3 2) org.richfaces.ui:richfaces-ui:jar:3.3.2.GA 4) el-impl:el-impl:jar:1.0 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=el-impl -DartifactId=el-impl -Dversion= 1.0 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=el-impl -DartifactId=el-impl -Dversion=1. 0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.docs.richfaces:jsf-app:war:3.3.3 2) el-impl:el-impl:jar:1.0 5) javax.faces:jsf-api:jar:1.2_12 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=javax.faces -DartifactId=jsf-api -Dvers ion=1.2_12 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=javax.faces -DartifactId=jsf-api -Dversio n=1.2_12 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.docs.richfaces:jsf-app:war:3.3.3 2) javax.faces:jsf-api:jar:1.2_12 6) javax.faces:jsf-impl:jar:1.2_12 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=javax.faces -DartifactId=jsf-impl -Dver sion=1.2_12 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=javax.faces -DartifactId=jsf-impl -Dversi on=1.2_12 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) org.docs.richfaces:jsf-app:war:3.3.3 2) javax.faces:jsf-impl:jar:1.2_12 -- 6 required artifacts are missing. for artifact: org.docs.richfaces:jsf-app:war:3.3.3 from the specified remote repositories: central (http://repo1.maven.org/maven2) [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 12 seconds [INFO] Finished at: Fri Apr 23 16:39:44 IST 2010 [INFO] Final Memory: 7M/18M [INFO] C:\sample\jsf-app - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail:
Re: integration problem
i used same command as u told me the command is as follow C:\sample2mvn archetype:generate -DarchetypeGroupId=org.richfaces.cdk -Darchety peArtifactId=maven-archetype-jsfwebapp -DarchetypeVersion=3.3.2.GA -DgroupId=org .docs.richfaces -DartifactId=jsf-app -DarchetypeRepository=http://repository.jbo ss.org/maven2 -- View this message in context: http://old.nabble.com/integration-problem-tp28337509p28340531.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: integration problem
Ok, I undertsand. Looks like this archetype is quite difficult as I think before. You need to add JBoss Snapshot repo to you maven settings.xml. Try to change previously added profiles section to listed below and try again with command. profiles profile idjboss-repo/id repositories repository idjboss/id urlhttp://repository.jboss.org/maven2/url releasesenabledtrue/enabled/releases snapshotsenabledfalse/enabled/snapshots /repository /repositories /profile profile idjboss-repo-snapshots/id repositories repository idjboss-snapshots/id urlhttp://snapshots.jboss.org/maven2//url releasesenabledfalse/enabled/releases snapshotsenabledtrue/enabled/snapshots /repository /repositories /profile /profiles activeProfiles activeProfilejboss-repo/activeProfile activeProfilejboss-repo-snapshots/activeProfile /activeProfiles 23.04.2010 16:11, pankjajain15 пишет: i used same command as u told me the command is as follow C:\sample2mvn archetype:generate -DarchetypeGroupId=org.richfaces.cdk -Darchety peArtifactId=maven-archetype-jsfwebapp -DarchetypeVersion=3.3.2.GA -DgroupId=org .docs.richfaces -DartifactId=jsf-app -DarchetypeRepository=http://repository.jbo ss.org/maven2 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: integration problem
till it is asking for snapshot version Aleksey Didik wrote: Ok, I undertsand. Looks like this archetype is quite difficult as I think before. You need to add JBoss Snapshot repo to you maven settings.xml. Try to change previously added profiles section to listed below and try again with command. profiles profile idjboss-repo/id repositories repository idjboss/id urlhttp://repository.jboss.org/maven2/url releasesenabledtrue/enabled/releases snapshotsenabledfalse/enabled/snapshots /repository /repositories /profile profile idjboss-repo-snapshots/id repositories repository idjboss-snapshots/id urlhttp://snapshots.jboss.org/maven2//url releasesenabledfalse/enabled/releases snapshotsenabledtrue/enabled/snapshots /repository /repositories /profile /profiles activeProfiles activeProfilejboss-repo/activeProfile activeProfilejboss-repo-snapshots/activeProfile /activeProfiles 23.04.2010 16:11, pankjajain15 пишет: i used same command as u told me the command is as follow C:\sample2mvn archetype:generate -DarchetypeGroupId=org.richfaces.cdk -Darchety peArtifactId=maven-archetype-jsfwebapp -DarchetypeVersion=3.3.2.GA -DgroupId=org .docs.richfaces -DartifactId=jsf-app -DarchetypeRepository=http://repository.jbo ss.org/maven2 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://old.nabble.com/integration-problem-tp28337509p28340758.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: integration problem
Ok, I have capitulated. Sorry pankjajain, but it's much difficult to start maven project then 5 minute install. Maven environment need to be configured. Different repositories must be added to your configuration. Try to read what Maven is. It will lead your to the right way. By the way, try to change archetype version in command to earlier, like 3.3.1.GA 3.3.0.GA 3.2.2.GA 3.3.1.GA May be the luck will be with you in one moment and this version of archetype will use only releases... Aleksey. 23.04.2010 16:34, pankjajain15 пишет: till it is asking for snapshot version Aleksey Didik wrote: Ok, I undertsand. Looks like this archetype is quite difficult as I think before. You need to add JBoss Snapshot repo to you maven settings.xml. Try to change previously addedprofiles section to listed below and try again with command. profiles profile idjboss-repo/id repositories repository idjboss/id urlhttp://repository.jboss.org/maven2/url releasesenabledtrue/enabled/releases snapshotsenabledfalse/enabled/snapshots /repository /repositories /profile profile idjboss-repo-snapshots/id repositories repository idjboss-snapshots/id urlhttp://snapshots.jboss.org/maven2//url releasesenabledfalse/enabled/releases snapshotsenabledtrue/enabled/snapshots /repository /repositories /profile /profiles activeProfiles activeProfilejboss-repo/activeProfile activeProfilejboss-repo-snapshots/activeProfile /activeProfiles 23.04.2010 16:11, pankjajain15 пишет: i used same command as u told me the command is as follow C:\sample2mvn archetype:generate -DarchetypeGroupId=org.richfaces.cdk -Darchety peArtifactId=maven-archetype-jsfwebapp -DarchetypeVersion=3.3.2.GA -DgroupId=org .docs.richfaces -DartifactId=jsf-app -DarchetypeRepository=http://repository.jbo ss.org/maven2 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Apache Maven 3.0-beta-1 Released
The Maven team is pleased to announce the release of Apache Maven 3.0-beta-1. Maven is a project comprehension and build tool, designed to simplify the process of maintaining a healthy development lifecycle for your project. You can read more here: http://maven.apache.org/ Downloads of source and binary distributions are listed in our download section: http://maven.apache.org/download.html A major goal of Maven 3.0 is to be compatible, to the extent possible, with existing plugins and projects designed for Maven 2.x. Users interested in testing this beta release should have a glance at the compatibility notes for known differences between Maven 3.0 and Maven 2.x: http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html If you encounter unexpected problems while using Maven 3.0-beta-1, please feel free to contact us via the Maven developer list: http://maven.apache.org/mail-lists.html Release Notes - Maven 2 3 - Version 3.0-beta-1 ** Bug * [MNG-1751] - merging metadata doesn't fail when timestamp is in the future * [MNG-2103] - Inheritance of plugin overrides that of execution * [MNG-] - dependency to dependency without source code fails * [MNG-2276] - profile activation by property doesn't work with properties defined in settings. * [MNG-2994] - Snapshot repositories are not checked when using ranges * [MNG-3092] - Version ranges with non-snapshot bounds can contain snapshot versions * [MNG-3133] - DefaultModelInheritence::appendPath assumes it is operating on interpolated/literal paths * [MNG-3470] - Build does not fail on corrupted POM even with checksumPolicy=fail * [MNG-3477] - Authentication failures on dependency download aren't reported * [MNG-3529] - mvn -Da= throws an excepltion * [MNG-3616] - Null Pointer Exception when mirrorOf missing from mirror in settings.xml * [MNG-3700] - ModelUtils.clone doesn't clone plugin entries where inherited == false * [MNG-4022] - Incorrect merge behavior using profile driven plugin configuration * [MNG-4326] - Maven should not check snapshot repositories for dependencies in the reactor * [MNG-4418] - Dependency resolution appears to misbehave if a remote repository uses the id local * [MNG-4453] - [regression] Plugin versions defined in a lifecycle mapping are not respected * [MNG-4555] - mvn archetype:generate -o (offline) still results in a checking updates from central * [MNG-4580] - Plugin dependencies for module ignored when building from aggregator project using direct plugin invocation * [MNG-4586] - Plugin prefix can't be resolved from plugin management if management entry is missing plugin version * [MNG-4590] - [regression] System properties are no longer interpolated in imported POMs * [MNG-4600] - [regression] Optional flag from dependency management applied to dependencies * [MNG-4618] - maven-javadoc-plugin aggregate-jar fails with maven3 and multiple modules * [MNG-4625] - Interpolation of settings.xml fails if an expression's value contains XML markup * [MNG-4629] - [regression] POM validation fails upon non-existing system-scope dependency * [MNG-4632] - Class loading is not thread-safe ** Improvement * [MNG-1701] - Validate that a plugin is not configured twice in the pom * [MNG-2187] - Improve error message when the pom is encoded in the wrong charset * [MNG-2741] - [regression] Meaningless error message: Error transferring file * [MNG-3004] - Allow build lifecycle to execute projects in parallel * [MNG-3779] - Improve error message when trying to execute mojo with no pom.xml * [MNG-4162] - Removal of all reporting logic from the core of Maven * [MNG-4194] - API to safely release of plugin realms * [MNG-4591] - Enhance the download rate output to include downloaded file name * [MNG-4610] - Bump maven-release-plugin to v2.0 in super POM * [MNG-4619] - Issue warning in case parent.relativePath points at POM with different groupId/artifactId * [MNG-4623] - model parsing errors can be less helpful in Maven 3 * [MNG-4628] - ReactorArtifactRepository is not setup soon enough for AbstractMavenLifecycleParticipant#afterProjectsRead * [MNG-4634] - Allow custom lifecycles ** Task * [MNG-3917] - Complete the POM construction tests which will be the validation for the specification Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
missing artifact
while creating a maven project in eclipse, it creates project successfully but showing following errors after building a project 4/23/10 4:55:53 PM IST: Missing artifact javax.faces:jsf-api:jar:1.2_12:compile 4/23/10 4:55:53 PM IST: Missing artifact javax.faces:jsf-impl:jar:1.2_12:compile 4/23/10 4:55:53 PM IST: Missing artifact el-impl:el-impl:jar:1.0:provided 4/23/10 4:55:53 PM IST: Missing artifact org.richfaces.framework:richfaces-api:jar:3.3.3-SNAPSHOT:compile 4/23/10 4:55:53 PM IST: Missing artifact org.richfaces.framework:richfaces-impl:jar:3.3.3-SNAPSHOT:compile 4/23/10 4:55:53 PM IST: Missing artifact org.richfaces.ui:richfaces-ui:jar:3.3.3-SNAPSHOT:compile 4/23/10 4:55:53 PM IST: Missing artifact org.richfaces.ui:richfaces-ui:jar:3.3.3-SNAPSHOT:compile 4/23/10 4:55:53 PM IST: Missing artifact org.richfaces.framework:richfaces-impl:jar:3.3.3-SNAPSHOT:provided please help me out -- View this message in context: http://old.nabble.com/missing-artifact-tp28341290p28341290.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: integration problem
Please ask the Richfaces people who created this archetype. Or the Jboss folks who are hosting it. This list can't help with bad/broken archetypes. Wayne On Fri, Apr 23, 2010 at 8:12 AM, pankjajain15 pankajjai...@gmail.com wrote: hey Aleksey tried following command C:\sample2\jsf-appmvn archetype:generate -DarchetypeGroupId=org.richfaces.cdk - DarchetypeArtifactId=maven-archetype-jsfwebapp -DarchetypeVersion=3.3.3-SNAPSHOT -DgroupId=org.docs.richfaces -DartifactId=jsf-app please tell me what would be the problem for above - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: passing parameters to plugin Archetype
I'm trying to do the same thing - can someone post instructions, I've
searched everywhere. I can see it's possible as when I use m2eclipse it
allows me to specify custom properties that are picked up, I just can't
figure out how to do it from the command line.
Thanks,
Steve.
iiggzz wrote:
I found it out! So if anybody has the same problem go ahead and ask me.
Now I have another problem. I need to specify the path to my files like
this: ${projectName}-mymodule/myfile.txt so after creation it should look
like this: helloworld-mymodule.
--
View this message in context:
http://old.nabble.com/passing-parameters-to-plugin-Archetype-tp16807963p28341796.html
Sent from the Maven - Users mailing list archive at Nabble.com.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Could we configure mapper in maven-resources-plugin?
Hello
Could we configure mapper in maven-resources-plugin?
I try without success the following:
plugin
artifactIdmaven-resources-plugin/artifactId
version2.4.2/version
executions
execution
idcopy-with-mapper/id
phasepre-integration-test/phase
configuration
outputDirectory${project.build.directory}/outputDirectory
resources
resource
directorysrc/test/config/directory
mapper type=glob from=*.cdf-test to=*.cfg/
/resource
/resources
/configuration
goals
goalcopy-resources/goal
/goals
/execution
/executions
/plugin
Regards,
Arnaud.
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: [ANN] Apache Maven 3.0-beta-1 Released
I know Jason says he won't give ETAs, but is there any ETA on the site reporting? I make a lot of use of it, and I doubt I'm alone. My personal preference is to find some way to integrate the docbkx plugin with the site framework. I've got some code that does this for Maven 2, and it works for Maven 3, but the reports aren't generated. -K On Apr 23, 2010, at 8:05 AM, Benjamin Bentmann wrote: The Maven team is pleased to announce the release of Apache Maven 3.0-beta-1. Maven is a project comprehension and build tool, designed to simplify the process of maintaining a healthy development lifecycle for your project. You can read more here: http://maven.apache.org/ Downloads of source and binary distributions are listed in our download section: http://maven.apache.org/download.html A major goal of Maven 3.0 is to be compatible, to the extent possible, with existing plugins and projects designed for Maven 2.x. Users interested in testing this beta release should have a glance at the compatibility notes for known differences between Maven 3.0 and Maven 2.x: http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html If you encounter unexpected problems while using Maven 3.0-beta-1, please feel free to contact us via the Maven developer list: http://maven.apache.org/mail-lists.html Release Notes - Maven 2 3 - Version 3.0-beta-1 ** Bug * [MNG-1751] - merging metadata doesn't fail when timestamp is in the future * [MNG-2103] - Inheritance of plugin overrides that of execution * [MNG-] - dependency to dependency without source code fails * [MNG-2276] - profile activation by property doesn't work with properties defined in settings. * [MNG-2994] - Snapshot repositories are not checked when using ranges * [MNG-3092] - Version ranges with non-snapshot bounds can contain snapshot versions * [MNG-3133] - DefaultModelInheritence::appendPath assumes it is operating on interpolated/literal paths * [MNG-3470] - Build does not fail on corrupted POM even with checksumPolicy=fail * [MNG-3477] - Authentication failures on dependency download aren't reported * [MNG-3529] - mvn -Da= throws an excepltion * [MNG-3616] - Null Pointer Exception when mirrorOf missing from mirror in settings.xml * [MNG-3700] - ModelUtils.clone doesn't clone plugin entries where inherited == false * [MNG-4022] - Incorrect merge behavior using profile driven plugin configuration * [MNG-4326] - Maven should not check snapshot repositories for dependencies in the reactor * [MNG-4418] - Dependency resolution appears to misbehave if a remote repository uses the id local * [MNG-4453] - [regression] Plugin versions defined in a lifecycle mapping are not respected * [MNG-4555] - mvn archetype:generate -o (offline) still results in a checking updates from central * [MNG-4580] - Plugin dependencies for module ignored when building from aggregator project using direct plugin invocation * [MNG-4586] - Plugin prefix can't be resolved from plugin management if management entry is missing plugin version * [MNG-4590] - [regression] System properties are no longer interpolated in imported POMs * [MNG-4600] - [regression] Optional flag from dependency management applied to dependencies * [MNG-4618] - maven-javadoc-plugin aggregate-jar fails with maven3 and multiple modules * [MNG-4625] - Interpolation of settings.xml fails if an expression's value contains XML markup * [MNG-4629] - [regression] POM validation fails upon non-existing system-scope dependency * [MNG-4632] - Class loading is not thread-safe ** Improvement * [MNG-1701] - Validate that a plugin is not configured twice in the pom * [MNG-2187] - Improve error message when the pom is encoded in the wrong charset * [MNG-2741] - [regression] Meaningless error message: Error transferring file * [MNG-3004] - Allow build lifecycle to execute projects in parallel * [MNG-3779] - Improve error message when trying to execute mojo with no pom.xml * [MNG-4162] - Removal of all reporting logic from the core of Maven * [MNG-4194] - API to safely release of plugin realms * [MNG-4591] - Enhance the download rate output to include downloaded file name * [MNG-4610] - Bump maven-release-plugin to v2.0 in super POM * [MNG-4619] - Issue warning in case parent.relativePath points at POM with different groupId/artifactId * [MNG-4623] - model parsing errors can be less helpful in Maven 3 * [MNG-4628] - ReactorArtifactRepository is not setup soon enough for AbstractMavenLifecycleParticipant#afterProjectsRead * [MNG-4634] - Allow custom lifecycles ** Task * [MNG-3917] - Complete the POM construction tests which will be the validation for the specification Enjoy, -The Maven team - To
Re: [ANN] Maven Compiler Plugin 2.3 Released
It works for me, too - Thanks! John Singleton On Fri, Apr 23, 2010 at 4:04 AM, Thomas Sundberg thomas.k.sundb...@gmail.com wrote: Hi! I just upgraded the project I'm working on and it worked fine. /Thomas On Fri, Apr 23, 2010 at 09:54, Milos Kleint mkle...@gmail.com wrote: The checksums on central shall be fixed now. My apologies to everyone. Milos On Wed, Apr 21, 2010 at 10:22 PM, Brett Porter br...@apache.org wrote: On 21/04/2010, at 11:13 PM, John Singleton wrote: Thanks, Brett. FWIW, I also noticed this problem with the 2.2 version of Compiler plugin, which was released a couple of weeks ago. Yes, they both use the same version of the shared component. It's being taken care of. - Brett -- Brett Porter br...@apache.org http://brettporter.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Thomas Sundberg M. Sc. in Computer Science Mobile: +46 70 767 33 15 Blog: http://thomassundberg.wordpress.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to add jar file into a Maven 2 environment?
I follow the step 3 and add a PayPal jar file in addition of placing the settings.xml under the Maven installation directory (apache-maven-2.2.1\conf). I can see the PayPal under 3re party at Nexus. When I try the PayAl group name I given during the step stated above in Eclipse of the project pom file, nothing shows up. How shall I resolve this problem? Also, I have tried to Artifact Upload from our project POM file on Nexus. Only the project artifact is uploaded, but not those its dependences. I don't know whether it is right or not. quote who=Tim O'Brien 1. Install Nexus like this: http://www.youtube.com/watch?v=bLskAeXivPg 2. Drop this into your ~/.m2/settings.xml http://www.sonatype.com/books/nexus-book/reference/maven-sect-single-group.html 3. Login into Nexus with admin/admin123, click on the 3rd party repository and upload your artifacts, here's the relevant section: http://www.sonatype.com/books/nexus-book/reference/using-sect-uploading-artifacts.html - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to add jar file into a Maven 2 environment?
Thanks Yoav. Based on my reading (a quick scanning), JFrog does the same thing as Nexus. I will use Nexus for now. quote who=Yoav Landman This article is pretty old. You may can follow the new Artifactory install instructions here: http://wiki.jfrog.org/confluence/display/RTF/Installing+Artifactory http://wiki.jfrog.org/confluence/display/RTF/Installing+ArtifactoryA quick 1 minute setup demo is available here: http://www.youtube.com/watch?v=2FGHwZSAqog http://www.youtube.com/watch?v=2FGHwZSAqogHTH, Yoav 2010/4/22 Vernon vernon...@pu-gong-ying.info I find an article on the subject: http://www.theserverside.com/news/1364121/Setting-Up-a-Maven-Repository . Does the procedures described in the article good enough for our need? quote who=Vernon Thanks for the information. How long it will take me to read through the book and set up an internal Maven proxy server? In a non-Maven environment, we can add those jar files in a minutes. Of course, the downside will be a potential version issues. quote who=Tim O'Brien Here's a good book on the topic: http://www.sonatype.com/books/nexus-book/reference/ 2010/4/22 Vernon vernon...@pu-gong-ying.info: Thanks a lot for your information. Where I can find a documentation on the subject (an internal Maven proxy server)? I have a look at the maven documentation under the user center and haven't find any useful information yet. quote who=David Hoffer Right if its not in a public Maven repository you have to add it to yours. Ideally you will have an internal Maven proxy server such as Artifactory/Nexus where you can deploy it once and all can get it from there. (Regarding iText 5.x the reason that's not in a public maven is the license has changed greatly starting with this version.) -Dave 2010/4/20 Vernon vernon...@pu-gong-ying.info: We need to add PayPal Java library files into our Maven development environment. PayPal doesn't make any Maven artifact ID. What is a right way of adding a jar file? And one more related question: shall we add jar file by ourselves for a new version of jar file? For example, the current version of iText is 5.0.x and the highest version with Maven artifact ID is 2.7.x. Thanks very much in advance. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org Spam/Virus scanning by CanIt Pro For more information see http://www.kgbinternet.com/SpamFilter.htm To control your spam filter, log in at http://filter.kgbinternet.com -- ��插� http://www.pu-gong-ying.info - ��ㄧ��绀惧�轰俊＄��绔� ��伴�婚�ㄦ�� - 瀹规�蹇��版��瑙���ヨ��涓�颁富瑕���伴�绘�烘�瓒�杩�0涓���伴�绘�＄���#8364;� 绀句伴�� - 涓�浠�浜哄��浜���ㄧ�浜��#8364;� �℃� - 瀵绘�炬��璇�璁虹���璐���┿#8364;�娓哥�╁�版�广#8364;� ���绫诲箍��� - 寮�璐村��娴�瑙�褰���扮�绫诲箍�� - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org Spam/Virus scanning by CanIt Pro For more information see http://www.kgbinternet.com/SpamFilter.htm To control your spam filter, log in at http://filter.kgbinternet.com -- ��插� http://www.pu-gong-ying.info - ��ㄧ��绀惧�轰俊＄��绔� ��伴�婚�ㄦ�� - 瀹规�蹇��版��瑙���ヨ��涓�颁富瑕���伴�绘�烘�瓒�杩�0涓���伴�绘�＄���#8364;� 绀句伴�� - 涓�浠�浜哄��浜���ㄧ�浜��#8364;� �℃� - 瀵绘�炬��璇�璁虹���璐���┿#8364;�娓哥�╁�版�广#8364;� ���绫诲箍��� - 寮�璐村��娴�瑙�褰���扮�绫诲箍�� - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org Spam/Virus scanning by CanIt Pro For more information see http://www.kgbinternet.com/SpamFilter.htm To control your spam filter, log in at http://filter.kgbinternet.com -- ��插� http://www.pu-gong-ying.info - ��ㄧ��绀惧�轰俊＄��绔� ��伴�婚�ㄦ�� - 瀹规�蹇��版��瑙���ヨ��涓�颁富瑕���伴�绘�烘�瓒�杩�0涓���伴�绘�＄���#8364;� 绀句伴�� - 涓�浠�浜哄��浜���ㄧ�浜��#8364;� �℃� - 瀵绘�炬��璇�璁虹���璐���┿#8364;�娓哥�╁�版�广#8364;� ���绫诲箍��� - 寮�璐村��娴�瑙�褰���扮�绫诲箍��
How do I use my own AnnotationProcessor with maven-annotation-plugin
Hi,
I am trying to get the maven-annotation-plugin working for me. I have
created an AnnotationProcessor, which in located in
dk.danlon.ewp.common.annotations.AnnotationProcessor which is in a seperate
maven project and installed in local repository.
I have tried to add my annotation processor as a PluginDependecy, but it
seems to be ignored.
Any help appreciated.
The pom.xml comes after the output below:
When I run 'mvn compile' I get the following:
ste...@stefan-vaio:~/trifork/workspace/ewp$ mvn compile
[INFO] Scanning for projects...
[INFO]
[INFO] Building ewp
[INFO]task-segment: [compile]
[INFO]
[INFO] snapshot org.bsc.maven:maven-processor-plugin:1.3.3-SNAPSHOT:
checking for updates from maven-annotation-plugin
Downloading:
http://maven-annotation-plugin.googlecode.com/svn/trunk/mavenrepo/org/bsc/maven/maven-processor-plugin/1.3.3-SNAPSHOT/maven-processor-plugin-1.3.3-SNAPSHOT.pom
Downloading:
http://maven-annotation-plugin.googlecode.com/svn/trunk/mavenrepo/org/bsc/maven/maven-processor-plugin/1.3.3-SNAPSHOT/maven-processor-plugin-1.3.3-SNAPSHOT.jar
[INFO] snapshot dk.danlon:ewpap:0.0.1-SNAPSHOT: checking for updates from
maven-annotation-plugin
[INFO] [processor:process {execution: process}]
[INFO] Source directory:
/home/stefan/trifork/workspace/ewp/target/generated-sources/apt added
[INFO] javac option: -cp
[INFO] javac option:
/home/stefan/trifork/workspace/ewp/src/main/resources:/home/stefan/trifork/workspace/ewp/target/classes
[INFO] javac option: -proc:only
[INFO] javac option: -processor
[INFO] javac option: dk.danlon.ewp.common.annotations.AnnotationProcessor
[INFO] javac option: -s
[INFO] javac option:
/home/stefan/trifork/workspace/ewp/target/generated-sources/apt
[INFO] diagnostic error: Annotation processor
'dk.danlon.ewp.common.annotations.AnnotationProcessor' not found
[ERROR] execute error
java.lang.Exception: error during compilation
at
org.bsc.maven.plugin.processor.AbstractAnnotationProcessorMojo.executeWithExceptionsHandled(AbstractAnnotationProcessorMojo.java:188)
at
org.bsc.maven.plugin.processor.AbstractAnnotationProcessorMojo.execute(AbstractAnnotationProcessorMojo.java:101)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:490)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:694)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:556)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:535)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:387)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:348)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:180)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:328)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:138)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:362)
at
org.apache.maven.cli.compat.CompatibleMain.main(CompatibleMain.java:60)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at
sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
at
sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:597)
at org.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)
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] error during compilation
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 2 seconds
[INFO] Finished at: Fri Apr 23 21:32:11 CEST 2010
[INFO] Final Memory: 7M/109M
[INFO]
ste...@stefan-vaio:~/trifork/workspace/ewp$
My pom.xml looks like this:
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
groupIddk.danlon/groupId
artifactIdewp/artifactId
packagingjar/packaging
version0.0.1-SNAPSHOT/version
Re: [ANN] Apache Maven 3.0-beta-1 Released
this one isn't done by Jason, but this won't give you an ETA neither ;) maven-site-plugin 3.0-beta-1 shouldn't be far: see [1] you can install it for yourself and see if it works we will probably put the release out in the next weeks Regards, Hervé https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+and+site+plugin Le vendredi 23 avril 2010, Kathryn Huxtable a écrit : I know Jason says he won't give ETAs, but is there any ETA on the site reporting? I make a lot of use of it, and I doubt I'm alone. My personal preference is to find some way to integrate the docbkx plugin with the site framework. I've got some code that does this for Maven 2, and it works for Maven 3, but the reports aren't generated. -K On Apr 23, 2010, at 8:05 AM, Benjamin Bentmann wrote: The Maven team is pleased to announce the release of Apache Maven 3.0-beta-1. Maven is a project comprehension and build tool, designed to simplify the process of maintaining a healthy development lifecycle for your project. You can read more here: http://maven.apache.org/ Downloads of source and binary distributions are listed in our download section: http://maven.apache.org/download.html A major goal of Maven 3.0 is to be compatible, to the extent possible, with existing plugins and projects designed for Maven 2.x. Users interested in testing this beta release should have a glance at the compatibility notes for known differences between Maven 3.0 and Maven 2.x: http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html If you encounter unexpected problems while using Maven 3.0-beta-1, please feel free to contact us via the Maven developer list: http://maven.apache.org/mail-lists.html Release Notes - Maven 2 3 - Version 3.0-beta-1 ** Bug * [MNG-1751] - merging metadata doesn't fail when timestamp is in the future * [MNG-2103] - Inheritance of plugin overrides that of execution * [MNG-] - dependency to dependency without source code fails * [MNG-2276] - profile activation by property doesn't work with properties defined in settings. * [MNG-2994] - Snapshot repositories are not checked when using ranges * [MNG-3092] - Version ranges with non-snapshot bounds can contain snapshot versions * [MNG-3133] - DefaultModelInheritence::appendPath assumes it is operating on interpolated/literal paths * [MNG-3470] - Build does not fail on corrupted POM even with checksumPolicy=fail * [MNG-3477] - Authentication failures on dependency download aren't reported * [MNG-3529] - mvn -Da= throws an excepltion * [MNG-3616] - Null Pointer Exception when mirrorOf missing from mirror in settings.xml * [MNG-3700] - ModelUtils.clone doesn't clone plugin entries where inherited == false * [MNG-4022] - Incorrect merge behavior using profile driven plugin configuration * [MNG-4326] - Maven should not check snapshot repositories for dependencies in the reactor * [MNG-4418] - Dependency resolution appears to misbehave if a remote repository uses the id local * [MNG-4453] - [regression] Plugin versions defined in a lifecycle mapping are not respected * [MNG-4555] - mvn archetype:generate -o (offline) still results in a checking updates from central * [MNG-4580] - Plugin dependencies for module ignored when building from aggregator project using direct plugin invocation * [MNG-4586] - Plugin prefix can't be resolved from plugin management if management entry is missing plugin version * [MNG-4590] - [regression] System properties are no longer interpolated in imported POMs * [MNG-4600] - [regression] Optional flag from dependency management applied to dependencies * [MNG-4618] - maven-javadoc-plugin aggregate-jar fails with maven3 and multiple modules * [MNG-4625] - Interpolation of settings.xml fails if an expression's value contains XML markup * [MNG-4629] - [regression] POM validation fails upon non-existing system-scope dependency * [MNG-4632] - Class loading is not thread-safe ** Improvement * [MNG-1701] - Validate that a plugin is not configured twice in the pom * [MNG-2187] - Improve error message when the pom is encoded in the wrong charset * [MNG-2741] - [regression] Meaningless error message: Error transferring file * [MNG-3004] - Allow build lifecycle to execute projects in parallel * [MNG-3779] - Improve error message when trying to execute mojo with no pom.xml * [MNG-4162] - Removal of all reporting logic from the core of Maven * [MNG-4194] - API to safely release of plugin realms * [MNG-4591] - Enhance the download rate output to include downloaded file name * [MNG-4610] - Bump maven-release-plugin to v2.0 in super POM * [MNG-4619] - Issue warning in case parent.relativePath points at POM with different groupId/artifactId * [MNG-4623] - model parsing errors can be less helpful in Maven 3 * [MNG-4628] - ReactorArtifactRepository is not setup soon enough for
Re: [ANN] Apache Maven 3.0-beta-1 Released
Great! I'll try it out and let you know. You're probably already doing integration testing, so you probably already know anything I'll report. I'l check the JIRA before I complain... Thanks! -K On Apr 23, 2010, at 3:02 PM, Hervé BOUTEMY wrote: this one isn't done by Jason, but this won't give you an ETA neither ;) maven-site-plugin 3.0-beta-1 shouldn't be far: see [1] you can install it for yourself and see if it works we will probably put the release out in the next weeks Regards, Hervé https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+and+site+plugin Le vendredi 23 avril 2010, Kathryn Huxtable a écrit : I know Jason says he won't give ETAs, but is there any ETA on the site reporting? I make a lot of use of it, and I doubt I'm alone. My personal preference is to find some way to integrate the docbkx plugin with the site framework. I've got some code that does this for Maven 2, and it works for Maven 3, but the reports aren't generated. -K On Apr 23, 2010, at 8:05 AM, Benjamin Bentmann wrote: The Maven team is pleased to announce the release of Apache Maven 3.0-beta-1. Maven is a project comprehension and build tool, designed to simplify the process of maintaining a healthy development lifecycle for your project. You can read more here: http://maven.apache.org/ Downloads of source and binary distributions are listed in our download section: http://maven.apache.org/download.html A major goal of Maven 3.0 is to be compatible, to the extent possible, with existing plugins and projects designed for Maven 2.x. Users interested in testing this beta release should have a glance at the compatibility notes for known differences between Maven 3.0 and Maven 2.x: http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html If you encounter unexpected problems while using Maven 3.0-beta-1, please feel free to contact us via the Maven developer list: http://maven.apache.org/mail-lists.html Release Notes - Maven 2 3 - Version 3.0-beta-1 ** Bug * [MNG-1751] - merging metadata doesn't fail when timestamp is in the future * [MNG-2103] - Inheritance of plugin overrides that of execution * [MNG-] - dependency to dependency without source code fails * [MNG-2276] - profile activation by property doesn't work with properties defined in settings. * [MNG-2994] - Snapshot repositories are not checked when using ranges * [MNG-3092] - Version ranges with non-snapshot bounds can contain snapshot versions * [MNG-3133] - DefaultModelInheritence::appendPath assumes it is operating on interpolated/literal paths * [MNG-3470] - Build does not fail on corrupted POM even with checksumPolicy=fail * [MNG-3477] - Authentication failures on dependency download aren't reported * [MNG-3529] - mvn -Da= throws an excepltion * [MNG-3616] - Null Pointer Exception when mirrorOf missing from mirror in settings.xml * [MNG-3700] - ModelUtils.clone doesn't clone plugin entries where inherited == false * [MNG-4022] - Incorrect merge behavior using profile driven plugin configuration * [MNG-4326] - Maven should not check snapshot repositories for dependencies in the reactor * [MNG-4418] - Dependency resolution appears to misbehave if a remote repository uses the id local * [MNG-4453] - [regression] Plugin versions defined in a lifecycle mapping are not respected * [MNG-4555] - mvn archetype:generate -o (offline) still results in a checking updates from central * [MNG-4580] - Plugin dependencies for module ignored when building from aggregator project using direct plugin invocation * [MNG-4586] - Plugin prefix can't be resolved from plugin management if management entry is missing plugin version * [MNG-4590] - [regression] System properties are no longer interpolated in imported POMs * [MNG-4600] - [regression] Optional flag from dependency management applied to dependencies * [MNG-4618] - maven-javadoc-plugin aggregate-jar fails with maven3 and multiple modules * [MNG-4625] - Interpolation of settings.xml fails if an expression's value contains XML markup * [MNG-4629] - [regression] POM validation fails upon non-existing system-scope dependency * [MNG-4632] - Class loading is not thread-safe ** Improvement * [MNG-1701] - Validate that a plugin is not configured twice in the pom * [MNG-2187] - Improve error message when the pom is encoded in the wrong charset * [MNG-2741] - [regression] Meaningless error message: Error transferring file * [MNG-3004] - Allow build lifecycle to execute projects in parallel * [MNG-3779] - Improve error message when trying to execute mojo with no pom.xml * [MNG-4162] - Removal of all reporting logic from the core of Maven * [MNG-4194] - API to safely release of plugin realms * [MNG-4591] - Enhance the download rate output to include downloaded file name * [MNG-4610] - Bump maven-release-plugin to v2.0 in super POM * [MNG-4619] - Issue warning in case parent.relativePath points at
Re: [ANN] Apache Maven 3.0-beta-1 Released
Any reason why mvn clean package on the checked out source would yield: [INFO] --- maven-compiler-plugin:2.1:compile (default-compile) @ maven-site-plugin --- [INFO] Compiling 23 source files to /Users/huxtable/Documents/workspace/maven-site-plugin-3.0-beta-1-SNAPSHOT/target/classes [INFO] - [ERROR] COMPILATION ERROR : [INFO] - [ERROR] /Users/huxtable/Documents/workspace/maven-site-plugin-3.0-beta-1-SNAPSHOT/src/main/java/org/apache/maven/plugins/site/DefaultMavenReportExecutor.java:[209,41] cannot find symbol symbol : method calculateForkedExecutions(org.apache.maven.plugin.MojoExecution,org.apache.maven.execution.MavenSession) location: interface org.apache.maven.lifecycle.LifecycleExecutor [ERROR] /Users/huxtable/Documents/workspace/maven-site-plugin-3.0-beta-1-SNAPSHOT/src/main/java/org/apache/maven/plugins/site/DefaultMavenReportExecutor.java:[213,45] cannot find symbol symbol : method executeForkedExecutions(org.apache.maven.plugin.MojoExecution,org.apache.maven.execution.MavenSession) location: interface org.apache.maven.lifecycle.LifecycleExecutor [INFO] 2 errors [INFO] - [INFO] [INFO] BUILD FAILURE -K On Apr 23, 2010, at 3:42 PM, Kathryn Huxtable wrote: Great! I'll try it out and let you know. You're probably already doing integration testing, so you probably already know anything I'll report. I'l check the JIRA before I complain... Thanks! -K On Apr 23, 2010, at 3:02 PM, Hervé BOUTEMY wrote: this one isn't done by Jason, but this won't give you an ETA neither ;) maven-site-plugin 3.0-beta-1 shouldn't be far: see [1] you can install it for yourself and see if it works we will probably put the release out in the next weeks Regards, Hervé https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+and+site+plugin Le vendredi 23 avril 2010, Kathryn Huxtable a écrit : I know Jason says he won't give ETAs, but is there any ETA on the site reporting? I make a lot of use of it, and I doubt I'm alone. My personal preference is to find some way to integrate the docbkx plugin with the site framework. I've got some code that does this for Maven 2, and it works for Maven 3, but the reports aren't generated. -K On Apr 23, 2010, at 8:05 AM, Benjamin Bentmann wrote: The Maven team is pleased to announce the release of Apache Maven 3.0-beta-1. Maven is a project comprehension and build tool, designed to simplify the process of maintaining a healthy development lifecycle for your project. You can read more here: http://maven.apache.org/ Downloads of source and binary distributions are listed in our download section: http://maven.apache.org/download.html A major goal of Maven 3.0 is to be compatible, to the extent possible, with existing plugins and projects designed for Maven 2.x. Users interested in testing this beta release should have a glance at the compatibility notes for known differences between Maven 3.0 and Maven 2.x: http://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html If you encounter unexpected problems while using Maven 3.0-beta-1, please feel free to contact us via the Maven developer list: http://maven.apache.org/mail-lists.html Release Notes - Maven 2 3 - Version 3.0-beta-1 ** Bug * [MNG-1751] - merging metadata doesn't fail when timestamp is in the future * [MNG-2103] - Inheritance of plugin overrides that of execution * [MNG-] - dependency to dependency without source code fails * [MNG-2276] - profile activation by property doesn't work with properties defined in settings. * [MNG-2994] - Snapshot repositories are not checked when using ranges * [MNG-3092] - Version ranges with non-snapshot bounds can contain snapshot versions * [MNG-3133] - DefaultModelInheritence::appendPath assumes it is operating on interpolated/literal paths * [MNG-3470] - Build does not fail on corrupted POM even with checksumPolicy=fail * [MNG-3477] - Authentication failures on dependency download aren't reported * [MNG-3529] - mvn -Da= throws an excepltion * [MNG-3616] - Null Pointer Exception when mirrorOf missing from mirror in settings.xml * [MNG-3700] - ModelUtils.clone doesn't clone plugin entries where inherited == false * [MNG-4022] - Incorrect merge behavior using profile driven plugin configuration * [MNG-4326] - Maven should not check snapshot repositories for dependencies in the reactor * [MNG-4418] - Dependency resolution appears to misbehave if a remote repository uses the id local * [MNG-4453] - [regression] Plugin versions defined in a lifecycle mapping are not respected * [MNG-4555] - mvn archetype:generate -o (offline) still results in a checking updates from central * [MNG-4580] - Plugin dependencies for
