Maven release plugin + CVS
I have a problem while performing a mvn release:prepare task when the project is downloaded from CVS, because the files are read only (so pom.xml can't be updated with new version). Error writing POM: C:\Documents and Settings\a.dionisi\Desktop\PLX\Source\AuditingWebService\pom.xml (Access is denied) I tried with useEditMode parameter for the plugin: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-release-plugin/artifactId version2.0/version configuration preparationGoalsclean install/preparationGoals autoVersionSubmodulestrue/autoVersionSubmodules useEditModetrue/useEditMode /configuration /plugin but I receive the warning: [WARNING] Provider cvs does not support edit operation. I tried also with scm:edit...same story. Is there a way to edit the project before release:prepare? Thank you for help. -- View this message in context: http://maven.40175.n5.nabble.com/Maven-release-plugin-CVS-tp1033588p1033588.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
Assembly as dependency of the same project
Hi all, I have the following issue... The pom of my project is the following: artifactId: it.mega groupId: streamer version: 1.0.1 1) First of all I generate an Apache CXF web service client into folder target/generated 2) Then I create an assembly (jar) containing the .class files 3) Next the assembly is installed into the local repo with the same identifier of the project but classifier web-service-client (e.g. /.m2/it/mega/streamer/1.0.1/Streamer-1.0.1-web-service-client.jar) 4) Now, I want to import this jar in the same project as a dependency, because I prefer a single jar instead of hundreds of classes in packages. I tried inserting the following snippet in pom: artifactIdit.mega/artifactId groupIdstreamer/groupId version1.0.1/version classifierweb-service-client/classifier and It doesn't work in the same project (circular dependency error) while it works correctly in other projects. How can I solve this problem with a correct approach? Thank you in advance for any answer! -- View this message in context: http://old.nabble.com/Assembly-as-dependency-of-the-same-project-tp27134967p27134967.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: Assembly as dependency of the same project
Just to maintain the things not too complex. Furthermore, the same behavior I described is needed for XmlBeans class generation. I have a set of classes generated from XSDs and I want to package them into a jar and put it as a dependency of the project. justinedelson wrote: Why do you want to do this? It seems like it'd be much simpler to have a separate project to produce the web service client. Justin On Tue, Jan 12, 2010 at 4:24 PM, Cecchi Sandrone cecchisandr...@gmail.comwrote: Hi all, I have the following issue... The pom of my project is the following: artifactId: it.mega groupId: streamer version: 1.0.1 1) First of all I generate an Apache CXF web service client into folder target/generated 2) Then I create an assembly (jar) containing the .class files 3) Next the assembly is installed into the local repo with the same identifier of the project but classifier web-service-client (e.g. /.m2/it/mega/streamer/1.0.1/Streamer-1.0.1-web-service-client.jar) 4) Now, I want to import this jar in the same project as a dependency, because I prefer a single jar instead of hundreds of classes in packages. I tried inserting the following snippet in pom: artifactIdit.mega/artifactId groupIdstreamer/groupId version1.0.1/version classifierweb-service-client/classifier and It doesn't work in the same project (circular dependency error) while it works correctly in other projects. How can I solve this problem with a correct approach? Thank you in advance for any answer! -- View this message in context: http://old.nabble.com/Assembly-as-dependency-of-the-same-project-tp27134967p27134967.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 -- View this message in context: http://old.nabble.com/Assembly-as-dependency-of-the-same-project-tp27134967p27135141.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: Assembly as dependency of the same project
Ok I understand your answers. For this kind of problem you recommend a module or a subproject (parent-child)? Maybe I don't have clear the difference between the two... Dana Lacoste wrote: I understand your desire for not wanting things too complex but, in maven, it's important to follow one simple rule: Every pom.xml (maven project) _should_ produce exactly one file as a resulting artifact If you need two files (a .jar and a .war) then you need two pom.xml (maven projects) and it's actually very very easy to split things up that way. Yes, it does take some adjusting to use this model, and yes it can be quite difficult sometimes to follow hey, why is it doing that here? but in the end, if you follow the maven model, you might find it makes more sense to do it the maven way. (and if you don't like splitting it up, I would DEFINITELY recommend using Ivy or something: maven works wonders when it's used the maven way and causes no end of headache when you try to twist it do something else) Dana Lacoste -Original Message- From: Cecchi Sandrone [mailto:cecchisandr...@gmail.com] Sent: Tuesday, January 12, 2010 1:34 PM To: users@maven.apache.org Subject: Re: Assembly as dependency of the same project Just to maintain the things not too complex. Furthermore, the same behavior I described is needed for XmlBeans class generation. I have a set of classes generated from XSDs and I want to package them into a jar and put it as a dependency of the project. - 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/Assembly-as-dependency-of-the-same-project-tp27134967p27135449.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
Best practices to generate a webapp test package?
Hi all, I'm relatively new to Maven and I'm working on a web app project. It's packaged as a war archive, but what I want is to generate an alternative package that contains also test classes and resources. The ideal situation is an executable jar from which test classes can be launched. I tried with the following pom: modelVersion4.0.0/modelVersion groupIdit.ids/groupId artifactIdPLX-WS/artifactId packagingwar/packaging namePLX-WS/name version0.1/version parent groupIdit.ids/groupId artifactIdPLX-WS/artifactId version0.1/version /parent build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId version2.2/version executions execution includes include**/include /includes goals goaltest-jar/goal /goals phasepackage/phase /execution /executions /plugin /plugins /build I tried with mvn jar:jar-test but I receive: V:\Workspace\PLX-WSmvn jar:test-jar [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'jar'. [INFO] [INFO] Building PLX-WS [INFO]task-segment: [jar:test-jar] [INFO] [INFO] [jar:test-jar] [WARNING] JAR will be empty - no content was marked for inclusion! [INFO] Building jar: V:\Workspace\PLX-WS\target\PLX-WS-tests.jar [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 4 seconds [INFO] Finished at: Wed Feb 18 14:04:39 CET 2009 [INFO] Final Memory: 10M/18M [INFO] and an empty Jar is created. If I change to packagingjar/packaging however it works... What should I change in my configuration? Is there a common practice to create test packages for web applications? Can you give me some recommendations? Thanks in advance -- View this message in context: http://www.nabble.com/Best-practices-to-generate-a-webapp-test-package--tp22078616p22078616.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
Customize properties in an already packaged application
Hi all, In my build scenario I have this problem... 1) A packaged war is available to download (from a website) for the user. It contains all properties specified in the pom (also database connection properties) that substitute those specified in the hibernate.properties during the filtering phase. 2) Obviously every user has his own database configuration and wants to customize these parameters (username, password, etc). How can I solve this problem without burdening too much the unqualified user from configuration details? Ideally, He wants a war package + an easy configuration file to enjoy the application... Thanks in advance for every advice. -- View this message in context: http://www.nabble.com/Customize-properties-in-an-already-packaged-application-tp21747726p21747726.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
