About Maven 1.0.2
I came across a problem when I run maven java:compile // unable to obtain the goal java:compile \hom.maven\cache\avalon-meta-plugin.jelly:12:83: ant:taskdef taskdef class org.apache.avalon.meta.info.ant.MetaTask cannnot be found // could you give you the reason? Thanks!!
About unittest run three times
Dear all, While I set the nightly build command for continum by clean install site-deploy, my unit tests all run for three times. And while I changed to clean install, the unit tests run for one time, and changed to clean site-deploy, my unit tests run for two times. Are there any to explain the behind mechanism? And my requirement is that to let all the unit tests run for only time, and I can also find the info from the deployed site, such as with PMD/FindBug related report. Thanks. Forest.
A problem of Maven 1.0.2
I came across a problem when I compile a project using maven 1.0.2. If I run maven -X java:compile, problems as follow: I don't know why? How to solve it? Thanks! __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0.2 Initializing Plugins! Set plugin source directory to C:\maven-1.0.2\plugins Set unpacked plugin directory to F:\home\.maven\cache Set user plugin directory to F:\home\.maven\plugins Loading plugin cache Now mapping cached plugins Loading plugin 'maven-cruisecontrol-plugin-1.6' Loading plugin 'maven-multichanges-plugin-1.1' Loading plugin 'maven-checkstyle-plugin-2.5' Loading plugin 'maven-file-activity-plugin-1.5.1' Loading plugin 'maven-jellydoc-plugin-1.3.1' Loading plugin 'maven-ear-plugin-1.6' Loading plugin 'maven-jdepend-plugin-1.5' Loading plugin 'maven-pom-plugin-1.4.1' Loading plugin 'maven-jira-plugin-1.1.2' Loading plugin 'maven-jar-plugin-1.6.1' Loading plugin 'maven-developer-activity-plugin-1.5.1' Loading plugin 'maven-jboss-plugin-1.5' Loading plugin 'maven-faq-plugin-1.4' Loading plugin 'maven-dist-plugin-1.6.1' Loading plugin 'maven-javadoc-plugin-1.7' Loading plugin 'maven-linkcheck-plugin-1.3.4' Loading plugin 'maven-tasklist-plugin-2.3' Loading plugin 'maven-idea-plugin-1.5' Loading plugin 'maven-jcoverage-plugin-1.0.9' Loading plugin 'maven-junit-report-plugin-1.5' Loading plugin 'maven-plugin-plugin-1.5.2' Loading plugin 'maven-changelog-plugin-1.7.1' Loading plugin 'maven-jxr-plugin-1.4.2' Loading plugin 'maven-ashkelon-plugin-1.2' Loading plugin 'maven-announcement-plugin-1.3' Loading plugin 'maven-xdoc-plugin-1.8' Loading plugin 'maven-eclipse-plugin-1.9' Loading plugin 'maven-shell-plugin-1.1' Loading plugin 'maven-rar-plugin-1.0' Loading plugin 'maven-dashboard-plugin-1.6' Loading plugin 'maven-scm-plugin-1.4.1' Loading plugin 'maven-clover-plugin-1.6' Loading plugin 'maven-uberjar-plugin-1.2' Loading plugin 'maven-war-plugin-1.6.1' Loading plugin 'maven-simian-plugin-1.4' Loading plugin 'maven-ant-plugin-1.8.1' Loading plugin 'maven-tjdo-plugin-1.0.0' Loading plugin 'maven-ejb-plugin-1.5' Loading plugin 'maven-changes-plugin-1.5.1' Loading plugin 'maven-j2ee-plugin-1.5.1' Loading plugin 'maven-release-plugin-1.4.1' Loading plugin 'maven-abbot-plugin-1.1' Loading plugin 'maven-multiproject-plugin-1.3.1' Loading plugin 'maven-nsis-plugin-1.1' Loading plugin 'maven-license-plugin-1.2' Loading plugin 'maven-jdiff-plugin-1.4' Loading plugin 'maven-pmd-plugin-1.6' Loading plugin 'maven-repository-plugin-1.2' Loading plugin 'maven-jbuilder-plugin-1.5' Loading plugin 'maven-console-plugin-1.1' Loading plugin 'maven-webserver-plugin-2.0' Loading plugin 'maven-aspectwerkz-plugin-1.2' Loading plugin 'maven-test-plugin-1.6.2' Loading plugin 'maven-jetty-plugin-1.1' Loading plugin 'maven-docbook-plugin-1.2' Loading plugin 'maven-latka-plugin-1.4.1' Loading plugin 'maven-aspectj-plugin-3.2' Loading plugin 'maven-hibernate-plugin-1.2' Loading plugin 'maven-native-plugin-1.1' Loading plugin 'maven-site-plugin-1.5.2' Loading plugin 'maven-gump-plugin-1.4' Loading plugin 'maven-appserver-plugin-2.0' Loading plugin 'maven-java-plugin-1.5' Loading plugin 'maven-pdf-plugin-2.2.1' Loading plugin 'maven-html2xdoc-plugin-1.3.1' Loading plugin 'maven-jdee-plugin-1.1' Loading plugin 'maven-jalopy-plugin-1.3.1' Loading plugin 'maven-jnlp-plugin-1.4.1' Loading plugin 'maven-jdeveloper-plugin-1.4' Loading plugin 'maven-junit-doclet-plugin-1.2' Loading plugin 'merlin-plugin-1.0' Loading plugin 'maven-wizard-plugin-1.1' Loading plugin 'maven-artifact-plugin-1.4.1' Loading plugin 'maven-javacc-plugin-1.1' Loading plugin 'maven-antlr-plugin-1.2.1' Loading plugin 'maven-struts-plugin-1.3' Loading plugin 'maven-clean-plugin-1.3' Loading plugin 'maven-castor-plugin-1.2' Loading plugin 'avalon-meta-plugin-1.1' Loading plugin 'maven-latex-plugin-1.4.1' Loading plugin 'maven-genapp-plugin-2.2' Loading plugin 'maven-caller-plugin-1.1' Loading plugin 'maven-vdoclet-plugin-1.2' Now loading uncached plugins Finished initializing Plugins! Using userBuildPropertiesFile: C:\Documents and Settings\Kerry Zhu\build.properties Using projectPropertiesFile: F:\xxx\project.properties Using projectBuildPropertiesFile: F:\xxx\build.properties pushing on org.apache.maven.jelly.mavenjellycont...@100363 over org.apache.maven.jelly.mavenjellycont...@14e8cee in emc:emc-dao [DEBUG] Adding reference: maven.dependency.classpath - running script null [available] [VERBOSE] Unable to find src\java to set property sourcesPresent [available] [VERBOSE] Unable to find src\test to set property unitTestSourcesPresent [DEBUG] Adding reference: maven-classpath - [DEBUG] Adding reference: maven.compile.src.set - Verifying dependencies for emc:emc-dao Processing dependencies for project xxx; classloader [ForeheadClassLoader: name=root.maven] running script F:\xxx\maven.xml preparing goal: build:start execution chain: [[Goal: name=build:start]; precursor=[]]]
maven deploy question
Hi Maven gurus, Looks like mvn deploy is deploying artifact from the target directory to remote maven repo. Is it possible to configure mvn deploy to deploy artifact from the local maven repo. Also, is it possible to skip all the lifecyle phases before deploy (validate, compile, test, package, integration-test, verify and install) and just deploy from local maven repo to remote maven repo? Thanks, Jane - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
checkstyle reports won't generate with a mvn clean install
Hi All I've configured checkstyle in my project and i can generate the Checkstyle reports when I issue a mvn checkstyle:checkstyle but my requirement is to generate the checkstyle reports once i do a clean build as well I've pasted the high level pom below. appreciate if you guys could point out what i'm doing wrong. I couldn't find a solution for this my searching the web. Thanks dependencyManagement dependencies dependency groupIdorg.hibernate/groupId artifactIdhibernate/artifactId version3.2.4.ga/version /dependency /dependencies /dependencyManagement build pluginManagement plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration source1.5/source target1.5/target /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId executions execution phaseverify/phase configuration consoleOutputtrue/consoleOutput configLocation checkstyle.xml /configLocation /configuration goals goalcheck/goal goalclean/goal /goals /execution /executions /plugin /plugins /pluginManagement /build reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId configuration configLocation checkstyle.xml /configLocation /configuration /plugin /plugins /reporting /project -- View this message in context: http://www.nabble.com/checkstyle-reports-won%27t-generate-with-a-mvn-clean-install-tp23632592p23632592.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven deploy question
Hi, See http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html Also note that modern MRM have a page that features this exact upload. Cheers. 2009/5/20 Jane Young jane.yo...@sun.com Hi Maven gurus, Looks like mvn deploy is deploying artifact from the target directory to remote maven repo. Is it possible to configure mvn deploy to deploy artifact from the local maven repo. Also, is it possible to skip all the lifecyle phases before deploy (validate, compile, test, package, integration-test, verify and install) and just deploy from local maven repo to remote maven repo? Thanks, Jane - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
Re: maven deploy question
Thanks for the link. I do not want to deploy individual artifacts. I want to deploy artifacts from a project. Is it possible to do this with deploy:deploy-file? Baptiste MATHUS wrote: Hi, See http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html Also note that modern MRM have a page that features this exact upload. Cheers. 2009/5/20 Jane Young jane.yo...@sun.com Hi Maven gurus, Looks like mvn deploy is deploying artifact from the target directory to remote maven repo. Is it possible to configure mvn deploy to deploy artifact from the local maven repo. Also, is it possible to skip all the lifecyle phases before deploy (validate, compile, test, package, integration-test, verify and install) and just deploy from local maven repo to remote maven repo? Thanks, Jane - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: About unittest run three times
Old story, and as far as I remember (please correct me if I'm wrong) the reason is: The site lifecycle and the default build lifecycle are isolated things. So if you run mvn install, the 'test' phase will be invoked - 1st run Your site has a test reporting section? - 2nd run I assume you have cobertura or another code coverage tool enabled? Because this runs all the tests in an instrumended form - 3nd run I'm not saying this situation is optimal though ;) This especially sucks while running releases, because prepare and perform will do all those steps a few times... LieGrue, strub --- forum geng gengfo.fo...@gmail.com schrieb am Mi, 20.5.2009: Von: forum geng gengfo.fo...@gmail.com Betreff: About unittest run three times An: users@maven.apache.org Datum: Mittwoch, 20. Mai 2009, 8:30 Dear all, While I set the nightly build command for continum by clean install site-deploy, my unit tests all run for three times. And while I changed to clean install, the unit tests run for one time, and changed to clean site-deploy, my unit tests run for two times. Are there any to explain the behind mechanism? And my requirement is that to let all the unit tests run for only time, and I can also find the info from the deployed site, such as with PMD/FindBug related report. Thanks. Forest. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven deploy question
Well, I'm finally not sure I understand what you want to do. Did you look at the provided link? Some goals (bound to the standard lifecycle that you should be aware of: http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#Build_Lifecycle_Basics ) * package will create the packaged version inside target directory (though this directory is customizable, but let's say you use the default values) * install will do all that package does + install the packaged artifact inside your local repository * deploy will do all that install does + deploy the artifact into your maven repository Deploy:deploy-file works at the file level. It takes many arguments, and you can use it to deploy any artifact in any repository, any groupId/artifactId/version. Really, I think this is what you need. If not, please rephrase your need more thoroughly. Cheers. 2009/5/20 Jane Young jane.yo...@sun.com Thanks for the link. I do not want to deploy individual artifacts. I want to deploy artifacts from a project. Is it possible to do this with deploy:deploy-file? Baptiste MATHUS wrote: Hi, See http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html Also note that modern MRM have a page that features this exact upload. Cheers. 2009/5/20 Jane Young jane.yo...@sun.com Hi Maven gurus, Looks like mvn deploy is deploying artifact from the target directory to remote maven repo. Is it possible to configure mvn deploy to deploy artifact from the local maven repo. Also, is it possible to skip all the lifecyle phases before deploy (validate, compile, test, package, integration-test, verify and install) and just deploy from local maven repo to remote maven repo? Thanks, Jane - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
how to patch existing (3rdparty) *.jar file with Maven
Hi, I´ve found a bug in an existing 3rdparty library that I can fix quickly by recompilation of the sourcefile and afterwards replace it in the *.jar. Is there a plugin to support that? The maven-patch-plugin only applies patches with the GNU patchtool, thats not what I´m looking for thanx, Torsten
Re: Maven: The Definitive Guide in French
What we're going to do is find a French publisher who is interested in printing the book. We want to have the same sort of deal we have with O'Reilly where we forfeit the royalties to get access to experienced editors. So I'll probably ask around to see if there are any interested publishers. Sonatype doesn't care about making money off the books we just want the book to be edited well. So the publisher can take all the proceeds from the printed book which I think works out for everyone. Editing and post production costs are very substantial for a book. It's great there are going to be volunteers to translate but someone needs to be responsible for the overall translation. I'll set up the standard mailing lists like we've done for the Chinese and German translations. Tim keeps an eye on these and keeps folks informed about new chapters that are in the works. If you need anything you just have to ask him in English :-) On 18-May-09, at 3:58 AM, Emmanuel Hugonnet wrote: Hi, I have started the French Translation for the Maven Guide here: http://github.com/ehsavoie/maven-guide/tree/master Feel free to contact me if you want to help :o) (reading, translating, ...). Emmanuel PS: I am currently translating the introduction chapter. -- Emmanuel Hugonnet Tel: +336.25.34.19.46 http://www.ehsavoie.com Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/SonatypeNexus http://twitter.com/SonatypeM2E -- Simplex sigillum veri. (Simplicity is the seal of truth.) - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven: The Definitive Guide in French
I'm in contact with Eyrolles as a JUG leader and can suggest them such a deal. As Pearson france is working with me and Arnaud on another Maven book I don't think they would like to have two, but can also suggest them Cheers, Nicolas 2009/5/20 Jason van Zyl jvan...@sonatype.com What we're going to do is find a French publisher who is interested in printing the book. We want to have the same sort of deal we have with O'Reilly where we forfeit the royalties to get access to experienced editors. So I'll probably ask around to see if there are any interested publishers. Sonatype doesn't care about making money off the books we just want the book to be edited well. So the publisher can take all the proceeds from the printed book which I think works out for everyone. Editing and post production costs are very substantial for a book. It's great there are going to be volunteers to translate but someone needs to be responsible for the overall translation. I'll set up the standard mailing lists like we've done for the Chinese and German translations. Tim keeps an eye on these and keeps folks informed about new chapters that are in the works. If you need anything you just have to ask him in English :-) On 18-May-09, at 3:58 AM, Emmanuel Hugonnet wrote: Hi, I have started the French Translation for the Maven Guide here: http://github.com/ehsavoie/maven-guide/tree/master Feel free to contact me if you want to help :o) (reading, translating, ...). Emmanuel PS: I am currently translating the introduction chapter. -- Emmanuel Hugonnet Tel: +336.25.34.19.46 http://www.ehsavoie.com Thanks, Jason -- Jason van Zyl Founder, Apache Maven http://twitter.com/jvanzyl http://twitter.com/SonatypeNexus http://twitter.com/SonatypeM2E -- Simplex sigillum veri. (Simplicity is the seal of truth.) - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-compiler-plugin unpacking dependencies into target/classes
I don't see anything in particular in your file listing nor in the effective pom that would make me instantly say oh that's it. Does this happen repeatedly? Can you replicate it on another computer, ideally with a completely different operating system and JDK version? If you had to, could you package it up and share it (and the parent poms etc) with someone to debug it? Perhaps try running mvn -X clean compile and post the output to Pastebin and send us the link. Wayne On Tue, May 19, 2009 at 3:48 AM, Michael Guyver michael.guy...@gmail.com wrote: bump? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-compiler-plugin unpacking dependencies into target/classes
Hi Wayne, Thanks for having a look for me. 2009/5/20 Wayne Fay wayne...@gmail.com: Does this happen repeatedly? It happens every time that Maven performs a compile of any of that project's source code. By that I mean that if I delete the javax directory from target/classes and run mvn compile, the compiler does not recreate the directory unless the up-to-date check fails. Delete one of the (expected) .class files and the javax branch is recreated. Can you replicate it on another computer, ideally with a completely different operating system and JDK version? Yes. I have a Linux workstation at work and suffer the same problem both there and at home, where I'm running OSX Leopard on Java 6. If you had to, could you package it up and share it (and the parent poms etc) with someone to debug it? I'm not sure I can share the code, and sadly, as with most WAR files, it's got plenty of dependencies. Perhaps try running mvn -X clean compile and post the output to Pastebin and send us the link. No problem: http://pastebin.com/f5722de1d Another thing that I find interesting is that it says it's Compiling 40 source files to /home/guyverm/projects/sr2/velocity-web/target/classes There are actually 57 class files in target/classes, of which 17 are under javax/servlet/. I've allowed for and subtracted the separate .class files for anonymous inner classes. Thanks very much for your time. Cheers Michael - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven deploy question
Hi, Thanks for responding. In our project, we first do mvn install to produce the artifact and then run QA tests to make sure the artifacts are good before deploying to the remote maven repository. When executing mvn deploy, it will go through preceding lifecycle phases (compile, package, test, install) before getting to deploy. We want to make sure the same artifacts that was tested in the local maven repository is getting published to the remote repository. But since deploy is executing compile, package and install again, it may possibly end up with different artifacts then the ones that was tested. Is there a workaround to this? Is it possible to skip the preceding lifecycle phases when executing mvn deploy. There are hundreds of artifacts in the project so deploying individual files with deploy:deploy-file will not work for us. Any suggestions? Thanks, Jane Baptiste MATHUS wrote: Well, I'm finally not sure I understand what you want to do. Did you look at the provided link? Some goals (bound to the standard lifecycle that you should be aware of: http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#Build_Lifecycle_Basics ) * package will create the packaged version inside target directory (though this directory is customizable, but let's say you use the default values) * install will do all that package does + install the packaged artifact inside your local repository * deploy will do all that install does + deploy the artifact into your maven repository Deploy:deploy-file works at the file level. It takes many arguments, and you can use it to deploy any artifact in any repository, any groupId/artifactId/version. Really, I think this is what you need. If not, please rephrase your need more thoroughly. Cheers. 2009/5/20 Jane Young jane.yo...@sun.com Thanks for the link. I do not want to deploy individual artifacts. I want to deploy artifacts from a project. Is it possible to do this with deploy:deploy-file? Baptiste MATHUS wrote: Hi, See http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html Also note that modern MRM have a page that features this exact upload. Cheers. 2009/5/20 Jane Young jane.yo...@sun.com Hi Maven gurus, Looks like mvn deploy is deploying artifact from the target directory to remote maven repo. Is it possible to configure mvn deploy to deploy artifact from the local maven repo. Also, is it possible to skip all the lifecyle phases before deploy (validate, compile, test, package, integration-test, verify and install) and just deploy from local maven repo to remote maven repo? Thanks, Jane - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: When using pom hierarchies where is the best place to add the distributionManagement bits?
What about report configuration, is that something you can add to your top parent pom? 2009/5/19 Baptiste MATHUS m...@batmat.net: Well, I'd say it totally depends on your organization. But I guess you could begin by putting the dependencies used very widely (e.g. commons-lang?) in your top pom. About your second sentence, well I'm not sure I understand what you mean. I guess you know that the parent pom will indeed be present locally, be it in the local maven repository or as a project you'll depend on. Cheers 2009/5/19 emerson cargnin echofloripa.y...@gmail.com Hi I have a few leves of hierarquies in our system. What is the suggested place to add the distributionManagement tag? For building I will use projects individually, so I will check out only the project without the parents. regards Emerson - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor ! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
m2 eclipse question
I know, I know, this may not be the list for that but the m2eclipse mailing list bot doesn't seem to be answering subscribe requests, so maybe I'll get lucky here. I created a new Maven project in Eclipse, using the maven-archetypes-quickstart archetype. I then added a dependency on commons-net-20030805.205232.jar which was duly processed and added to the pom file. However, eclipse tells me I have build errors. All of these errors have to do with unknown references to code in commons-net-20030805.205232.jar. If I invoke a build the pom.xml, it succeeds, but that's different than what eclipse does. In the .classpath file is the entry classpathentry kind=/con/ path=/org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER// In the Java build path, under Maven Dependencies I do see commons-net-20030805.205232.jar This would appear to be all that eclipse should need to be able to find this dependency in its build. What am I missing? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-compiler-plugin unpacking dependencies into target/classes
Michael Guyver wrote: Hi there, I'm experiencing some very very strange behaviour in my project. The mvn compile goal is somehow generating/unpacking the following files into my target/classes directory: javax/servlet/ServletRequest.class javax/servlet/RequestDispatcher.class javax/servlet/ServletContext.class javax/servlet/ServletResponse.class javax/servlet/ServletInputStream.class javax/servlet/ServletException.class javax/servlet/Servlet.class javax/servlet/ServletConfig.class javax/servlet/http/HttpServletRequest.class javax/servlet/http/Cookie.class javax/servlet/http/HttpSession.class javax/servlet/http/HttpSessionContext.class javax/servlet/http/HttpServletResponse.class javax/servlet/ServletOutputStream.class I'm at a loss as to how these are getting there. Hi Michael, Investigate the possibility that .java *source* files corresponding to those classes somehow exist in one of your dependency jar files. I've occasionally encountered weirdness where in such a circumstance, those .java files can get compiled into target/classes as well. Max. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven deploy question
You need to stage the deploy, i.e. deploy to an intermediate repository and then move them from there. I know that the pro version of Nexus has support built in for this, but given that we have not purchased it I cannot attest to it's workability. Alternatively there is a stage mojo on one of the plugins (might be wagon-maven-plugin) to help copying a staged repository to the final repository -Stephen 2009/5/20 Jane Young jane.yo...@sun.com Hi, Thanks for responding. In our project, we first do mvn install to produce the artifact and then run QA tests to make sure the artifacts are good before deploying to the remote maven repository. When executing mvn deploy, it will go through preceding lifecycle phases (compile, package, test, install) before getting to deploy. We want to make sure the same artifacts that was tested in the local maven repository is getting published to the remote repository. But since deploy is executing compile, package and install again, it may possibly end up with different artifacts then the ones that was tested. Is there a workaround to this? Is it possible to skip the preceding lifecycle phases when executing mvn deploy. There are hundreds of artifacts in the project so deploying individual files with deploy:deploy-file will not work for us. Any suggestions? Thanks, Jane Baptiste MATHUS wrote: Well, I'm finally not sure I understand what you want to do. Did you look at the provided link? Some goals (bound to the standard lifecycle that you should be aware of: http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#Build_Lifecycle_Basics ) * package will create the packaged version inside target directory (though this directory is customizable, but let's say you use the default values) * install will do all that package does + install the packaged artifact inside your local repository * deploy will do all that install does + deploy the artifact into your maven repository Deploy:deploy-file works at the file level. It takes many arguments, and you can use it to deploy any artifact in any repository, any groupId/artifactId/version. Really, I think this is what you need. If not, please rephrase your need more thoroughly. Cheers. 2009/5/20 Jane Young jane.yo...@sun.com Thanks for the link. I do not want to deploy individual artifacts. I want to deploy artifacts from a project. Is it possible to do this with deploy:deploy-file? Baptiste MATHUS wrote: Hi, See http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html Also note that modern MRM have a page that features this exact upload. Cheers. 2009/5/20 Jane Young jane.yo...@sun.com Hi Maven gurus, Looks like mvn deploy is deploying artifact from the target directory to remote maven repo. Is it possible to configure mvn deploy to deploy artifact from the local maven repo. Also, is it possible to skip all the lifecyle phases before deploy (validate, compile, test, package, integration-test, verify and install) and just deploy from local maven repo to remote maven repo? Thanks, Jane - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to reference a specific dependency in maven-antrun-plugin?
2009/5/17 Hilco Wijbenga hilco.wijbe...@gmail.com:
Hi all,
The documentation for maven-antrun-plugin lists at the very bottom of
Referencing the Maven Classpaths:
= Start snippet =
You can also use the path to each dependency artifact
property name=mvn.dependency.jar
refid=maven.dependency.my.group.id:my.artifact.id:classifier:jar.path/
echo message=My Dependency JAR-Path: ${mvn.dependency.jar}/
= End snippet =
I've tried several variations but I can't seem to find the right one.
If I have groupId org.example, artifactId xyz, and version 1.2,
then what is the magic incantation that uses the above snippet
properly?
I assume it's something like
property name=mvn.dependency.jar
refid=maven.dependency.org.example:xyz:classifier:jar.path/
but what do I do with classifier and jar.path?
Anyone? Is the question not clear? Or is this a dark and unexplored
area of maven-antrun-plugin? :-)
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: maven deploy question
mvn deploy -DaltDeploymentRepository=http://stage.repo.url/ mvn org.codehaus.mojo:wagon-maven-plugin:1.0-beta-1:merge-maven-repos \ -Dwagon.source=http://stage.repo.url \ -Dwagon.target=http://deploy.repo.url \ -Djava.io.tmpdir=target 2009/5/20 Stephen Connolly stephen.alan.conno...@gmail.com You need to stage the deploy, i.e. deploy to an intermediate repository and then move them from there. I know that the pro version of Nexus has support built in for this, but given that we have not purchased it I cannot attest to it's workability. Alternatively there is a stage mojo on one of the plugins (might be wagon-maven-plugin) to help copying a staged repository to the final repository -Stephen 2009/5/20 Jane Young jane.yo...@sun.com Hi, Thanks for responding. In our project, we first do mvn install to produce the artifact and then run QA tests to make sure the artifacts are good before deploying to the remote maven repository. When executing mvn deploy, it will go through preceding lifecycle phases (compile, package, test, install) before getting to deploy. We want to make sure the same artifacts that was tested in the local maven repository is getting published to the remote repository. But since deploy is executing compile, package and install again, it may possibly end up with different artifacts then the ones that was tested. Is there a workaround to this? Is it possible to skip the preceding lifecycle phases when executing mvn deploy. There are hundreds of artifacts in the project so deploying individual files with deploy:deploy-file will not work for us. Any suggestions? Thanks, Jane Baptiste MATHUS wrote: Well, I'm finally not sure I understand what you want to do. Did you look at the provided link? Some goals (bound to the standard lifecycle that you should be aware of: http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#Build_Lifecycle_Basics ) * package will create the packaged version inside target directory (though this directory is customizable, but let's say you use the default values) * install will do all that package does + install the packaged artifact inside your local repository * deploy will do all that install does + deploy the artifact into your maven repository Deploy:deploy-file works at the file level. It takes many arguments, and you can use it to deploy any artifact in any repository, any groupId/artifactId/version. Really, I think this is what you need. If not, please rephrase your need more thoroughly. Cheers. 2009/5/20 Jane Young jane.yo...@sun.com Thanks for the link. I do not want to deploy individual artifacts. I want to deploy artifacts from a project. Is it possible to do this with deploy:deploy-file? Baptiste MATHUS wrote: Hi, See http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html Also note that modern MRM have a page that features this exact upload. Cheers. 2009/5/20 Jane Young jane.yo...@sun.com Hi Maven gurus, Looks like mvn deploy is deploying artifact from the target directory to remote maven repo. Is it possible to configure mvn deploy to deploy artifact from the local maven repo. Also, is it possible to skip all the lifecyle phases before deploy (validate, compile, test, package, integration-test, verify and install) and just deploy from local maven repo to remote maven repo? Thanks, Jane - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven deploy question
sorry that should be mvn deploy -DaltDeploymentRepository=stage::default::http://stage.repo.url/ http://stage.repo.url/ mvn org.codehaus.mojo:wagon-maven-plugin:1.0-beta-1:merge-maven-repos \ -Dwagon.source=http://stage.repo.url \ -Dwagon.target=http://deploy.repo.url \ -Djava.io.tmpdir=target 2009/5/20 Stephen Connolly stephen.alan.conno...@gmail.com mvn deploy -DaltDeploymentRepository=http://stage.repo.url/ mvn org.codehaus.mojo:wagon-maven-plugin:1.0-beta-1:merge-maven-repos \ -Dwagon.source=http://stage.repo.url \ -Dwagon.target=http://deploy.repo.url \ -Djava.io.tmpdir=target 2009/5/20 Stephen Connolly stephen.alan.conno...@gmail.com You need to stage the deploy, i.e. deploy to an intermediate repository and then move them from there. I know that the pro version of Nexus has support built in for this, but given that we have not purchased it I cannot attest to it's workability. Alternatively there is a stage mojo on one of the plugins (might be wagon-maven-plugin) to help copying a staged repository to the final repository -Stephen 2009/5/20 Jane Young jane.yo...@sun.com Hi, Thanks for responding. In our project, we first do mvn install to produce the artifact and then run QA tests to make sure the artifacts are good before deploying to the remote maven repository. When executing mvn deploy, it will go through preceding lifecycle phases (compile, package, test, install) before getting to deploy. We want to make sure the same artifacts that was tested in the local maven repository is getting published to the remote repository. But since deploy is executing compile, package and install again, it may possibly end up with different artifacts then the ones that was tested. Is there a workaround to this? Is it possible to skip the preceding lifecycle phases when executing mvn deploy. There are hundreds of artifacts in the project so deploying individual files with deploy:deploy-file will not work for us. Any suggestions? Thanks, Jane Baptiste MATHUS wrote: Well, I'm finally not sure I understand what you want to do. Did you look at the provided link? Some goals (bound to the standard lifecycle that you should be aware of: http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#Build_Lifecycle_Basics ) * package will create the packaged version inside target directory (though this directory is customizable, but let's say you use the default values) * install will do all that package does + install the packaged artifact inside your local repository * deploy will do all that install does + deploy the artifact into your maven repository Deploy:deploy-file works at the file level. It takes many arguments, and you can use it to deploy any artifact in any repository, any groupId/artifactId/version. Really, I think this is what you need. If not, please rephrase your need more thoroughly. Cheers. 2009/5/20 Jane Young jane.yo...@sun.com Thanks for the link. I do not want to deploy individual artifacts. I want to deploy artifacts from a project. Is it possible to do this with deploy:deploy-file? Baptiste MATHUS wrote: Hi, See http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html Also note that modern MRM have a page that features this exact upload. Cheers. 2009/5/20 Jane Young jane.yo...@sun.com Hi Maven gurus, Looks like mvn deploy is deploying artifact from the target directory to remote maven repo. Is it possible to configure mvn deploy to deploy artifact from the local maven repo. Also, is it possible to skip all the lifecyle phases before deploy (validate, compile, test, package, integration-test, verify and install) and just deploy from local maven repo to remote maven repo? Thanks, Jane - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
FATAL ERROR: id can not be null
I apologize if this question has already been asked. I have searched the recent archives and did not find it. I have a project that compiled fine under Maven 2.0.6. I recently upgraded to Maven 2.1.0 and it returned this error when I tried to compile: [INFO] Copying 10 resources [INFO] [ERROR] FATAL ERROR [INFO] [INFO] id can not be null [INFO] [INFO] Trace java.lang.NullPointerException: id can not be null at org.apache.maven.wagon.repository.Repository.init(Repository.java:8 1) at org.apache.maven.artifact.repository.DefaultArtifactRepository.init (DefaultArtifactRepository.java:70) at org.apache.maven.artifact.repository.DefaultArtifactRepositoryFactory .createDeploymentArtifactRepository(DefaultArtifactRepositoryFactory.java:44) at org.apache.maven.project.ProjectUtils.buildDeploymentArtifactReposito ry(ProjectUtils.java:80) at org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLog ic(DefaultMavenProjectBuilder.java:1038) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(Def aultMavenProjectBuilder.java:880) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromReposito ry(DefaultMavenProjectBuilder.java:255) at org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocat edProject(MavenMetadataSource.java:163) at org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocat edArtifact(MavenMetadataSource.java:94) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(D efaultArtifactCollector.java:388) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(D efaultArtifactCollector.java:74) ... My POM file is: ?xml version=1.0?project modelVersion4.0.0/modelVersion groupIdorg.myorg/groupId artifactIdmy-main-project/artifactId namemy-main-project/name version1.1/version urlhttp://maven.apache.org/url build finalNamemy-main-project/finalName plugins plugin artifactIdmaven-compiler-plugin/artifactId configuration source1.5/source target1.5/target /configuration /plugin !--plugin groupIdorg.myorg/groupId artifactIdmaven-file-plugin/artifactId /plugin-- /plugins /build repositories repository idmaven2.org.myorg/id nameMy Maven2 Repository/name urlhttp://myorg.org/maven2/url /repository /repositories pluginRepositories pluginRepository idmaven2.myorg.org/id urlhttp://myorg.org/maven2/url /pluginRepository /pluginRepositories dependencies dependency groupIdjdbc/groupId artifactIdoracle/artifactId version1.4/version /dependency dependency groupIdorg.myorg/groupId artifactIdsome_service/artifactId version1.1/version /dependency dependency groupIdorg.json/groupId artifactIdjson/artifactId version1.0/version /dependency dependency groupIdorg.myorg/groupId artifactIdutils/artifactId version1.2/version /dependency dependency groupIdlog4j/groupId artifactIdlog4j/artifactId version1.2.15/version scopecompile/scope /dependency dependency groupIdjdom/groupId artifactIdjdom/artifactId version1.0/version /dependency dependency groupIdcommons-httpclient/groupId artifactIdcommons-httpclient/artifactId version3.1/version /dependency dependency groupIdorg.myorg/groupId artifactIdsome_java_service/artifactId version1.9/version /dependency /dependencies distributionManagement repository idorg.myorg/id urlscp://127.0.0.1/srv/www/htdocs/maven2/url !--urlscp://myorg.org/srv/www/htdocs/maven2/url-- /repository site idmyorg.org/id urlscp://myorg.org/home/public_html/my-main-project/url /site /distributionManagement /project I would appreciate any advice you can give with this problem. Algie Morgan Senior Software Developer Integrated Ocean Drilling Program Texas A M University Algie E. Morgan Software Developer Department: Tools and Analytical Services (TAS) morga...@iodp.tamu.edu Office: 979-845-1125 Cell: 979-571-7973 BEGIN:VCARD VERSION:2.1 X-GWTYPE:USER FN:Morgan, Algie EMAIL;WORK;PREF;NGW:morga...@iodp.tamu.edu N:Morgan;Algie ORG:;TAS TITLE:Application Developer II END:VCARD - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: FATAL ERROR: id can not be null
Hi, Maybe a repository/mirror declared in ~/.m2/settings.xml without any id. -- Olivier 2009/5/20 Algie Morgan morga...@iodp.tamu.edu: I apologize if this question has already been asked. I have searched the recent archives and did not find it. I have a project that compiled fine under Maven 2.0.6. I recently upgraded to Maven 2.1.0 and it returned this error when I tried to compile: [INFO] Copying 10 resources [INFO] [ERROR] FATAL ERROR [INFO] [INFO] id can not be null [INFO] [INFO] Trace java.lang.NullPointerException: id can not be null at org.apache.maven.wagon.repository.Repository.init(Repository.java:8 1) at org.apache.maven.artifact.repository.DefaultArtifactRepository.init (DefaultArtifactRepository.java:70) at org.apache.maven.artifact.repository.DefaultArtifactRepositoryFactory .createDeploymentArtifactRepository(DefaultArtifactRepositoryFactory.java:44) at org.apache.maven.project.ProjectUtils.buildDeploymentArtifactReposito ry(ProjectUtils.java:80) at org.apache.maven.project.DefaultMavenProjectBuilder.processProjectLog ic(DefaultMavenProjectBuilder.java:1038) at org.apache.maven.project.DefaultMavenProjectBuilder.buildInternal(Def aultMavenProjectBuilder.java:880) at org.apache.maven.project.DefaultMavenProjectBuilder.buildFromReposito ry(DefaultMavenProjectBuilder.java:255) at org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocat edProject(MavenMetadataSource.java:163) at org.apache.maven.project.artifact.MavenMetadataSource.retrieveRelocat edArtifact(MavenMetadataSource.java:94) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.recurse(D efaultArtifactCollector.java:388) at org.apache.maven.artifact.resolver.DefaultArtifactCollector.collect(D efaultArtifactCollector.java:74) ... My POM file is: ?xml version=1.0?project modelVersion4.0.0/modelVersion groupIdorg.myorg/groupId artifactIdmy-main-project/artifactId namemy-main-project/name version1.1/version urlhttp://maven.apache.org/url build finalNamemy-main-project/finalName plugins plugin artifactIdmaven-compiler-plugin/artifactId configuration source1.5/source target1.5/target /configuration /plugin !--plugin groupIdorg.myorg/groupId artifactIdmaven-file-plugin/artifactId /plugin-- /plugins /build repositories repository idmaven2.org.myorg/id nameMy Maven2 Repository/name urlhttp://myorg.org/maven2/url /repository /repositories pluginRepositories pluginRepository idmaven2.myorg.org/id urlhttp://myorg.org/maven2/url /pluginRepository /pluginRepositories dependencies dependency groupIdjdbc/groupId artifactIdoracle/artifactId version1.4/version /dependency dependency groupIdorg.myorg/groupId artifactIdsome_service/artifactId version1.1/version /dependency dependency groupIdorg.json/groupId artifactIdjson/artifactId version1.0/version /dependency dependency groupIdorg.myorg/groupId artifactIdutils/artifactId version1.2/version /dependency dependency groupIdlog4j/groupId artifactIdlog4j/artifactId version1.2.15/version scopecompile/scope /dependency dependency groupIdjdom/groupId artifactIdjdom/artifactId version1.0/version /dependency dependency groupIdcommons-httpclient/groupId artifactIdcommons-httpclient/artifactId version3.1/version /dependency dependency groupIdorg.myorg/groupId artifactIdsome_java_service/artifactId version1.9/version /dependency /dependencies distributionManagement repository idorg.myorg/id urlscp://127.0.0.1/srv/www/htdocs/maven2/url !--urlscp://myorg.org/srv/www/htdocs/maven2/url-- /repository site idmyorg.org/id urlscp://myorg.org/home/public_html/my-main-project/url /site /distributionManagement /project I would appreciate any advice you can give with this problem. Algie Morgan Senior Software Developer Integrated Ocean Drilling Program Texas A M University Algie E. Morgan Software Developer Department: Tools and Analytical Services (TAS) morga...@iodp.tamu.edu Office: 979-845-1125 Cell: 979-571-7973 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven jetty plugin does not rebuild war
maven plugin in my pom
plugin
groupIdorg.mortbay.jetty/groupId
artifactIdjetty-maven-plugin/artifactId
version7.0.0.pre5/version
configuration
contextPath/audit/contextPath
jettyEnvXml${basedir}/jetty-env.xml/jettyEnvXml
/configuration
dependencies
dependency
groupIdcommons-dbcp/groupId
artifactIdcommons-dbcp/artifactId
version1.2.2/version
scopecompile/scope
/dependency
dependency
groupIdcom.oracle/groupId
artifactIdojdbc/artifactId
version14/version
scopecompile/scope
/dependency
/dependencies
/plugin
/plugins
any time I make changes to java code and run jetty:run the changes are not
picked up , I have to do a clean and which deletes the war file , if there
is war file in target then this plugin does not rebuild the war , please
help me how to resolve this ?
Re: m2 eclipse question
Uh, never mind. I chose the wrong commons-net version from the repository. The repository and m2-eclipse were doing exactly what I told them to. I wanted commons-net-2.0.jar, not this old 20030805 thing which is obviously a very old date. Steve Cohen wrote: I know, I know, this may not be the list for that but the m2eclipse mailing list bot doesn't seem to be answering subscribe requests, so maybe I'll get lucky here. I created a new Maven project in Eclipse, using the maven-archetypes-quickstart archetype. I then added a dependency on commons-net-20030805.205232.jar which was duly processed and added to the pom file. However, eclipse tells me I have build errors. All of these errors have to do with unknown references to code in commons-net-20030805.205232.jar. If I invoke a build the pom.xml, it succeeds, but that's different than what eclipse does. In the .classpath file is the entry classpathentry kind=/con/ path=/org.maven.ide.eclipse.MAVEN2_CLASSPATH_CONTAINER// In the Java build path, under Maven Dependencies I do see commons-net-20030805.205232.jar This would appear to be all that eclipse should need to be able to find this dependency in its build. What am I missing? - 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
How to make a war file with all schema inside
it's possibile make, with eclipse/maven, a .war file (for tomcat) that include all necessary schemas? I want that my service working in local without internet. Unfortunately at the moment without internet tomcat tries to get external schema (es. spring schemas or cxf schemas) and doesn't start the service. It's possibile resolve the problem? Thanks - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: maven-compiler-plugin unpacking dependencies into target/classes
Hi Max, 2009/5/20 Max Bowsher m...@mxtelecom.com: Investigate the possibility that .java *source* files corresponding to those classes somehow exist in one of your dependency jar files. I've occasionally encountered weirdness where in such a circumstance, those .java files can get compiled into target/classes as well. And that seems to have been exactly it. The JAR gwt-user-1.6.4.jar contains a large number of source files and it's these that seem to have been compiled into the target/classes directory. I've fixed it by repacking that jar file and verified with a mvn clean compile that the javax/ directory has not been recreated. I would be interested to find out how it is that source files ostensibly on the classpath (and not the source-path) are being compiled into target/classes. Have I missed something here? Best wishes and thanks very much to you and Wayne for your help. Mike - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: FATAL ERROR: id can not be null
Olivier,
Thanks for your fast response, but that is not the problem. I checked the
~/.m2/settings.xml and that all checks out fine. There were only a few entries
there for a jetspeed project I am experimenting with. I tried commenting out
most of that file and I still get the error. But, just in case I overlooked
something, here is the settings.xml file:
?xml version=1.0 encoding=UTF-8?
!--
Licensed to the Apache Software Foundation (ASF) under one or more
contributor license agreements. See the NOTICE file distributed with
this work for additional information regarding copyright ownership.
The ASF licenses this file to You under the Apache License, Version 2.0
(the License); you may not use this file except in compliance with
the License. You may obtain a copy of the License at
http://www.apache.org/licenses/LICENSE-2.0
Unless required by applicable law or agreed to in writing, software
distributed under the License is distributed on an AS IS BASIS,
WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
See the License for the specific language governing permissions and
limitations under the License.
$Id:$
--
!--
settings.xml
This file is placed in ~/.m2 by convention. User defined
profiles must be defined or extended with these settings
to perform a complete J2 build and deployment.
--
settings xmlns=http://maven.apache.org/POM/4.0.0;
profiles
!-- Default Profile --
profile
idsettings/id
activation
activeByDefaulttrue/activeByDefault
/activation
properties
!-- Jetspeed-2 deployment properties --
org.apache.jetspeed.server.homeC:\Program Files\Apache
Software Foundation\Tomcat-5.5.27/org.apache.jetspeed.server.home
org.apache.jetspeed.catalina.version.major5.5/org.apache.jetspeed.catalina.version.major
org.apache.jetspeed.services.autodeployment.serverlocalhost/org.apache.jetspeed.services.autodeployment.server
org.apache.jetspeed.services.autodeployment.port8080/org.apache.jetspeed.services.autodeployment.port
org.apache.jetspeed.services.autodeployment.useruser/org.apache.jetspeed.services.autodeployment.user
org.apache.jetspeed.services.autodeployment.passwordpassword/org.apache.jetspeed.services.autodeployment.password
!-- Derby embedded database properties --
org.apache.jetspeed.production.jdbc.drivers.path/org.apache.jetspeed.production.jdbc.drivers.path
org.apache.jetspeed.production.database.default.namederby/org.apache.jetspeed.production.database.default.name
org.apache.jetspeed.production.database.urljdbc:derby:/tmp/j2/org.apache.jetspeed.production.database.url
org.apache.jetspeed.production.database.driverorg.apache.derby.jdbc.EmbeddedDriver/org.apache.jetspeed.production.database.driver
org.apache.jetspeed.production.database.user/org.apache.jetspeed.production.database.user
org.apache.jetspeed.production.database.password/org.apache.jetspeed.production.database.password
!-- MSSQL database properties --
!--
org.apache.jetspeed.production.jdbc.drivers.path${org.apache.jetspeed.server.home}/shared/lib/jtds-1.2.jar/org.apache.jetspeed.production.jdbc.drivers.path
org.apache.jetspeed.production.database.default.namemssql/org.apache.jetspeed.production.database.default.name
org.apache.jetspeed.production.database.urljdbc:jtds:sqlserver://localhost:1433/j2/org.apache.jetspeed.production.database.url
org.apache.jetspeed.production.database.drivernet.sourceforge.jtds.jdbc.Driver/org.apache.jetspeed.production.database.driver
org.apache.jetspeed.production.database.usersa/org.apache.jetspeed.production.database.user
org.apache.jetspeed.production.database.passwordsa/org.apache.jetspeed.production.database.password
--
!-- HSQLDB embedded database properties --
!--
org.apache.jetspeed.production.jdbc.drivers.path/org.apache.jetspeed.production.jdbc.drivers.path
org.apache.jetspeed.production.database.default.namehsql/org.apache.jetspeed.production.database.default.name
org.apache.jetspeed.production.database.urljdbc:hsqldb:file:/tmp/j2;shutdown=true/org.apache.jetspeed.production.database.url
org.apache.jetspeed.production.database.driverorg.hsqldb.jdbcDriver/org.apache.jetspeed.production.database.driver
org.apache.jetspeed.production.database.usersa/org.apache.jetspeed.production.database.user
org.apache.jetspeed.production.database.password/org.apache.jetspeed.production.database.password
--
Re: maven deploy question
Thanks, Stephen. This may work for us. Stephen Connolly wrote: sorry that should be mvn deploy -DaltDeploymentRepository=stage::default::http://stage.repo.url/ http://stage.repo.url/ mvn org.codehaus.mojo:wagon-maven-plugin:1.0-beta-1:merge-maven-repos \ -Dwagon.source=http://stage.repo.url \ -Dwagon.target=http://deploy.repo.url \ -Djava.io.tmpdir=target 2009/5/20 Stephen Connolly stephen.alan.conno...@gmail.com mvn deploy -DaltDeploymentRepository=http://stage.repo.url/ mvn org.codehaus.mojo:wagon-maven-plugin:1.0-beta-1:merge-maven-repos \ -Dwagon.source=http://stage.repo.url \ -Dwagon.target=http://deploy.repo.url \ -Djava.io.tmpdir=target 2009/5/20 Stephen Connolly stephen.alan.conno...@gmail.com You need to stage the deploy, i.e. deploy to an intermediate repository and then move them from there. I know that the pro version of Nexus has support built in for this, but given that we have not purchased it I cannot attest to it's workability. Alternatively there is a stage mojo on one of the plugins (might be wagon-maven-plugin) to help copying a staged repository to the final repository -Stephen 2009/5/20 Jane Young jane.yo...@sun.com Hi, Thanks for responding. In our project, we first do mvn install to produce the artifact and then run QA tests to make sure the artifacts are good before deploying to the remote maven repository. When executing mvn deploy, it will go through preceding lifecycle phases (compile, package, test, install) before getting to deploy. We want to make sure the same artifacts that was tested in the local maven repository is getting published to the remote repository. But since deploy is executing compile, package and install again, it may possibly end up with different artifacts then the ones that was tested. Is there a workaround to this? Is it possible to skip the preceding lifecycle phases when executing mvn deploy. There are hundreds of artifacts in the project so deploying individual files with deploy:deploy-file will not work for us. Any suggestions? Thanks, Jane Baptiste MATHUS wrote: Well, I'm finally not sure I understand what you want to do. Did you look at the provided link? Some goals (bound to the standard lifecycle that you should be aware of: http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html#Build_Lifecycle_Basics ) * package will create the packaged version inside target directory (though this directory is customizable, but let's say you use the default values) * install will do all that package does + install the packaged artifact inside your local repository * deploy will do all that install does + deploy the artifact into your maven repository Deploy:deploy-file works at the file level. It takes many arguments, and you can use it to deploy any artifact in any repository, any groupId/artifactId/version. Really, I think this is what you need. If not, please rephrase your need more thoroughly. Cheers. 2009/5/20 Jane Young jane.yo...@sun.com Thanks for the link. I do not want to deploy individual artifacts. I want to deploy artifacts from a project. Is it possible to do this with deploy:deploy-file? Baptiste MATHUS wrote: Hi, See http://maven.apache.org/plugins/maven-deploy-plugin/deploy-file-mojo.html Also note that modern MRM have a page that features this exact upload. Cheers. 2009/5/20 Jane Young jane.yo...@sun.com Hi Maven gurus, Looks like mvn deploy is deploying artifact from the target directory to remote maven repo. Is it possible to configure mvn deploy to deploy artifact from the local maven repo. Also, is it possible to skip all the lifecyle phases before deploy (validate, compile, test, package, integration-test, verify and install) and just deploy from local maven repo to remote maven repo? Thanks, Jane - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to make a war file with all schema inside
I want that my service working in local without internet. Unfortunately at the moment without internet tomcat tries to get external schema (es. spring schemas or cxf schemas) and doesn't start the service. Its probably a better use of your time to look into configuring Tomcat so it does not try to reach out and get external schemas (surely there's a configuration option for this) rather than trying to bundle the files in your War. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: FATAL ERROR: id can not be null
Here is a pom.xml which contains a mandatory id element /mailingList /mailingLists developers developer idmraible/id nameMatt Raible/name emailm...@raibledesigns.com/email organizationRaible Designs, Inc./organization timezone-7/timezone /developer if i left out idmraible/id maven execution would fail so examine all the elements in your pom.xml and determine which ones need id element and insert idSomeValidId/idaccordingly HTH Martin Gainty __ Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht dient lediglich dem Austausch von Informationen und entfaltet keine rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le destinataire prévu, nous te demandons avec bonté que pour satisfaire informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie de ceci est interdite. Ce message sert à l'information seulement et n'aura pas n'importe quel effet légalement obligatoire. Étant donné que les email peuvent facilement être sujets à la manipulation, nous ne pouvons accepter aucune responsabilité pour le contenu fourni. Date: Wed, 20 May 2009 16:27:39 -0500 From: morga...@iodp.tamu.edu To: users@maven.apache.org Subject: Re: FATAL ERROR: id can not be null Olivier, Thanks for your fast response, but that is not the problem. I checked the ~/.m2/settings.xml and that all checks out fine. There were only a few entries there for a jetspeed project I am experimenting with. I tried commenting out most of that file and I still get the error. But, just in case I overlooked something, here is the settings.xml file: ?xml version=1.0 encoding=UTF-8? !-- Licensed to the Apache Software Foundation (ASF) under one or more contributor license agreements. See the NOTICE file distributed with this work for additional information regarding copyright ownership. The ASF licenses this file to You under the Apache License, Version 2.0 (the License); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. $Id:$ -- !-- settings.xml This file is placed in ~/.m2 by convention. User defined profiles must be defined or extended with these settings to perform a complete J2 build and deployment. -- settings xmlns=http://maven.apache.org/POM/4.0.0; profiles !-- Default Profile -- profile idsettings/id activation activeByDefaulttrue/activeByDefault /activation properties !-- Jetspeed-2 deployment properties -- org.apache.jetspeed.server.homeC:\Program Files\Apache Software Foundation\Tomcat-5.5.27/org.apache.jetspeed.server.home org.apache.jetspeed.catalina.version.major5.5/org.apache.jetspeed.catalina.version.major org.apache.jetspeed.services.autodeployment.serverlocalhost/org.apache.jetspeed.services.autodeployment.server org.apache.jetspeed.services.autodeployment.port8080/org.apache.jetspeed.services.autodeployment.port org.apache.jetspeed.services.autodeployment.useruser/org.apache.jetspeed.services.autodeployment.user org.apache.jetspeed.services.autodeployment.passwordpassword/org.apache.jetspeed.services.autodeployment.password !-- Derby embedded database properties -- org.apache.jetspeed.production.jdbc.drivers.path/org.apache.jetspeed.production.jdbc.drivers.path org.apache.jetspeed.production.database.default.namederby/org.apache.jetspeed.production.database.default.name org.apache.jetspeed.production.database.urljdbc:derby:/tmp/j2/org.apache.jetspeed.production.database.url org.apache.jetspeed.production.database.driverorg.apache.derby.jdbc.EmbeddedDriver/org.apache.jetspeed.production.database.driver org.apache.jetspeed.production.database.user/org.apache.jetspeed.production.database.user org.apache.jetspeed.production.database.password/org.apache.jetspeed.production.database.password !-- MSSQL
Re: mvn install for ear project
More details would be helpful. Could you provide some pom snipits to show the error? What maven version are you using? Jim On Tue, May 19, 2009 at 2:55 PM, tubin gen fachh...@gmail.com wrote: my project has subprojects one for ear , one for war and one for jar . I get this error when I run mvn install java.lang.NullPointerException at org.apache.maven.plugin.war.util.WebappStructure.getDependencies(WebappStructure.java:109) at org.apache.maven.plugin.war.util.WebappStructure.analyseDependencies(WebappStructure.java:288) at org.apache.maven.plugin.war.packaging.DependenciesAnalysisPackagingTask.performPackaging(DependenciesAnalysisPackagingTask.java:46) at org.apache.maven.plugin.war.AbstractWarMojo.buildWebapp(AbstractWarMojo.java:439) at org.apache.maven.plugin.war.AbstractWarMojo.buildExplodedWebapp(AbstractWarMojo.java:375) at org.apache.maven.plugin.war.WarMojo.performPackaging(WarMojo.java:181) at org.apache.maven.plugin.war.WarMojo.execute(WarMojo.java:143) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:483) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:678) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:540) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:519) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:371) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:332) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:181) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) 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) please help me, what is causing this error ?
How to create many jars in package phase?
Hi everybody... I want to generate more than one .jar when executing mvn package in a module named common, this is necesary because many modules of the parent project use diferent packages of the common module, so, I need to create many .jars with diferent packages form the same common module. I tried with executions sections in the configuration of the maven-jar-plugin, but, it's necesary to set diferent names for the generated .jars and it isn't possible with executions. So, any idea? How can I do this? Thanks in advance... -- View this message in context: http://www.nabble.com/How-to-create-many-jars-in-package-phase--tp23646150p23646150.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: How to create many jars in package phase?
On Wed, May 20, 2009 at 5:46 PM, Jesfre jesfre...@gmail.com wrote: I want to generate more than one .jar when executing mvn package in a module named common, this is necesary because many modules of the parent project use diferent packages of the common module, so, I need to create many .jars with diferent packages form the same common module. I tried with executions sections in the configuration of the maven-jar-plugin, but, it's necesary to set diferent names for the generated .jars and it isn't possible with executions. Generally the rule is that you produce one main artifact from each module. You may want to split this module up into several smaller ones. -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: checkstyle reports won't generate with a mvn clean install
Reports are only generated when you run a site or site-deploy build. You could either do something like mvn clean site or mvn clean install checkstyle:checkstyle I think that the lifecycle doc would explain it better, but I'm having troubles loading the page right now http://maven.apache.org/guides/introduction/introduction-to-the-lifecycle.html HTH Jim On Wed, May 20, 2009 at 6:09 AM, zac001 zac...@gmail.com wrote: Hi All I've configured checkstyle in my project and i can generate the Checkstyle reports when I issue a mvn checkstyle:checkstyle but my requirement is to generate the checkstyle reports once i do a clean build as well I've pasted the high level pom below. appreciate if you guys could point out what i'm doing wrong. I couldn't find a solution for this my searching the web. Thanks dependencyManagement dependencies dependency groupIdorg.hibernate/groupId artifactIdhibernate/artifactId version3.2.4.ga/version /dependency /dependencies /dependencyManagement build pluginManagement plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-compiler-plugin/artifactId configuration source1.5/source target1.5/target /configuration /plugin plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId executions execution phaseverify/phase configuration consoleOutputtrue/consoleOutput configLocation checkstyle.xml /configLocation /configuration goals goalcheck/goal goalclean/goal /goals /execution /executions /plugin /plugins /pluginManagement /build reporting plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId configuration configLocation checkstyle.xml /configLocation /configuration /plugin /plugins /reporting /project -- View this message in context: http://www.nabble.com/checkstyle-reports-won%27t-generate-with-a-mvn-clean-install-tp23632592p23632592.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
