David Williams is out of the office.
I will be out of the office starting 07/04/2007 and will not return until 07/09/2007. I will respond to your message as soon as I return. If you need assistance, please contact Steve Kaminski in my absence. Thanks, David - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: problem in release:prepare
add a trailing slash perhaps? On 3 Jul 2007, at 12:36, javijava wrote: Thanks to reply Andy, I quit all the references to repositorys at the POm file except the SCM, I include /trunk in the scm:svn:http:// connection string, but i have the same error!! :( Maven try to tag release with the label svn://localhost:80/svn/autentia/trunkautentia-1.0 More ideas Andrew??? Javier F. -- View this message in context: http://www.nabble.com/problem-in- release%3Aprepare-tf4017258s177.html#a11410367 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: how to configure Default Repository Layout for local repository
Using install:install-file or deploy:deploy-file will enable you to install your legacy named jars into the repository format by passing metadata on the command line. Though jars may not have the version in their name they still have metadata or a release number associated with them where this information will be available. Andy On 3 Jul 2007, at 20:56, Harish Kachoria wrote: I understand.. But the bad thing is backward compatiablty. Maven 1.0 support tag by which we can avoid version number. and Maven 2.0 not. and renaming of legacy jar is not a good idea. Because they are provided by third party. and because Maven don't like the name of jar, so rename the jar Maven designer should consider the fact that Many of Legacy jars do not have version numbers. and Mangement always afraid to touch such jars. even if it is a small change. I think I have to convince for renaming jar on development env. Wayne Fay wrote: Your only option (if you want to continue using Maven) is to starting using versions. Even if you use scope=system you still need to set a version in the node. And system scope is just a bad idea in the first place, generally. Wayne On 7/3/07, Harish Kachoria wrote: OK it works from me.. I created remote repo on my local machine. and maven downloded the jars stored them in the way he likes. still I have one problem, my libraries does not have any version number. and version number is mandatory for maven 2.0. ( tag had been removed in maven 2.0) so now I have two solution - - rename all jar with some fake version(may be 1.0) and then convince management for this. which I know won't happen - forget maven. which I don't prefer. (this was my idea to use maven in this project) so can you find any other solution. Carlos Sanchez-4 wrote: you can't change the local repository layout, it's a cache for maven and it shouldn't matter how it's stored you can change the remote repositories layout, so just create a remote repo for your projects in whatever style you want, although not a great idea On 7/3/07, Harish Kachoria wrote: It would be better if I can explain my problem then you can suggest me some solution Currently I have one project which has around 30+sub projects (Which I can say modules) Each sub project has its own ear which contains 1 war module and 1 ejb module. There are some common libraries also which are shared accros the projects. In development env we copy this library at local location and use them from JBuilder. In production env, many ears are deployed (this project as well as other projects) and all common libraries are in server lib folder. now I want to build one sub project using maven. and I need to refer all common libraries just for compilations (as we never include common library in EAR) To use maven I need to define dependancy and needs to copy common library in repo. I wants to copy all jars in one folder of repo and trying to use it but with Maven 2.0 it seems to be not possible. If you have any alternate way then please let me know -- View this message in context: http://www.nabble.com/how-to-configure-Default-Repository-Layout- for-local-repository-tf4018468s177.html#a11417704 Sent from the Maven - Users mailing list archive at Nabble.com. -- --- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride --- -- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/how-to-configure-Default-Repository-Layout- for-local-repository-tf4018468s177.html#a11418660 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] :arguing::arguing::arguing::arguing::arguing::arguing::arguing: -- View this message in context: http://www.nabble.com/how-to- configure-Default-Repository-Layout-for-local-repository- tf4018468s177.html#a11419527 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Release several artifacts depending on profiles
Hi, we have the following scenario we want to solve with maven: we have projects generating axis clients using the axistools-maven-plugin. Depending on the environment in which these client projects are deployed the clients are build with either axis 1.1 or axis 1.3. Now we want to use maven to create and release artifacts for these client projects. We can use profiles (one for Axis 1.1, one for Axis 1.3) to create different artifacts. But how can we produce release artifacts for all profiles in one run. Perhaps this can be better solved using assemblies. We would have to define one assembly for each variation which creates a release file looking something like client-axis1.1-1.0.0.jar. The next problem is then to define a dependency to this artefact in another project. Any help or best practises are welcome. Best regards Achim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Axis 1.4 POM files missing on central?
Hi list, one of the projects I'm trying to convert from an Ant build structure to Maven is using Axis. Instead of version 1.1 that is originally used in the Ant build I'm trying to use Axis 1.4 so I added the following snippet to my pom.xml: dependency groupIdaxis/groupId artifactIdaxis/artifactId version1.4/version /dependency which itself has dependencies to axis:axis-jaxrpc:1.4 and axis:axis-saaj:1.4. Each time I execute mvn compile I see the following messages: [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. Downloading: http://localhost:4080/artifactory/repo/axis/axis-jaxrpc/1.4/axis-jaxrpc-1.4.pom Downloading: http://localhost:4080/artifactory/repo/axis/axis-saaj/1.4/axis-saaj-1.4.pom [INFO] [compiler:compile] [INFO] Nothing to compile - all classes are up to date [INFO] When looking at central repo (proxied by a local running instance of Artifactory) I discovered that the above mentioned pom files are missing; also missing is the pom file for axis:axis-ant:1.4. The directories on central only contain the jar files, metadata and their checksums, but no sources jar (apart from axis-ant:1.4). Coincidence? Intention? Apart from the messages the build success, btw... Thorsten
Re: Unpack
Hi Brian... Its open! http://jira.codehaus.org/browse/MDEP-99 Thanks for any help. VELO On 7/3/07, Brian E. Fox [EMAIL PROTECTED] wrote: If swc is really a zip, why don't they call it a zip? I think the archiver would have to have its map updated, but we might be able to mess around with the hints. File a jira and attach an swc for me to try out. Thanks, Brian -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Marvin Froeder Sent: Tuesday, July 03, 2007 10:05 AM To: Maven Users List Subject: Unpack Hi guys... How can I use the dependency plugin: http://maven.apache.org/plugins/maven-dependency-plugin/unpack-mojo.html To unpack an artifact file (is a ZIP file) with a the extension SWC? I got this error: [INFO] Unknown archiver type Embedded error: No such archiver: 'swc'. SWCs are adobe's flex packaging file. VELO - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: No more problem in release:prepare
add a trailing slash perhaps? Thanks 4 all to help me!! i can do the release now. In the POM file I only have in the scm the dev connexion developerConnectionscm:svn:svn://localhost:80/svn/prova/repo/autentia/trunk/developerConnection An I specify the tag base there: build plugins plugin artifactIdmaven-release-plugin/artifactId configuration tagBasehttp://localhost/svn/prova/repo/autentia/tags/tagBase usernamexavi/username passwordsvn/password /configuration /plugin /plugins /build Well, now i must investigate how to do it automatic with continuum Javier -- View this message in context: http://www.nabble.com/problem-in-release%3Aprepare-tf4017258s177.html#a11429196 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Using Maven with Eclipse well: mvn eclipse:eclipse and nested projects
I have a multi-module project and I am trying to get the right set up to use Maven with Eclipse. I have a question below on mvn eclipse:eclipse, but some background first. I used to use m2eclipse with Eclipse 3.1 but as the projects have grown, m2eclipse has shown to have problems. For example in a multi-module project, each module might want different versions of a jar file in the path (say in different WAR files). m2eclipse seems to load all the different source directories up into one mega-project, and come up with a single list of all dependencies flattened across projects. When m2eclipse worked, I sometimes got different versions of artifacts in the dependency list. Frequently it just refused to work, not finding all the dependencies correctly - which is probably a bug. However regardless of any possible bugs, the basic premise seems wrong - each module should have its own dependencies worked out as they may *want* different versions of jar files. mvn eclipse:eclipse therefore looks a better way to go. I can check out a SVN tree, run mvn eclipse:eclipse, then load up all the modules as separate projects with only the jar file dependencies for that module included. This works much more reliably - no problems so far. However, because it creates a project per module, I cannot use the global Eclipse SVN support for tagging, branching, switching etc. I cannot do this from the top of the tree. I have to go back to the command line. I just downloaded Eclipse Europa (3.3) and it (as well as 3.2 I believe) supports nested projects. That is, it appears I can have a .project file in the root directory plus one in each module directory. (I am having a little trouble with Subclipse and Subversive, but I think they will be resolved so I am going to assume they work.) This looks almost ideal, which leads me to finally to my question... Q: Is there any way to make mvn eclipse:elipse generate a .project file for the root directory as well as each module? That way I can check out the whole project tree from the root and have a project per pom file. Eclipse can now handle nested projects, so it will load them all up (it used to refuse to load up child directory projects under a parent directory project). I saw a hack somewhere of changing the root pom file to temporarily use jar packaging, then put it back to pom packaging - but this is pretty ugly. Now that Eclipse supports nested projects, is there any reason not to do this? It would give me the ability to do all the svn commands from inside Eclipse from the root package (I don't need or want to compile any Java code from the root package - I just want to be able to explore the tree, do 'sync with repository', commits, svn switches etc) plus each module would get its own correct dependency list as occurs now. I would do all compiles in the module directories. Is this possible now? (I don't think so.) Can it be added? Would it allow what I am trying to do? Thanks! Alan Kent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Pre-phase execution of a plugin
Hello, is there any chance to define a plugin to run before the inherited goal executions? I have to tag a cvs-module and check for an already deployed version with the same versionnumber before deploying. I wrote an ant-plugin to test these conditions which is executed within the deploy-phase and which will break the deploy-process if one condition fails. This is rather stupid because the conditions are checked when deploy is already done... The install-phase is not the right position for my plugin, because these checks must not be done if I will only install to local repository :-( I need a pre-phase... Anyone who can help? Best regards, Torsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
moving from maven1 to maven2
where to place the properties defined in project.properties and build.properties of maven1,in maven2
Re: Using Maven with Eclipse well: mvn eclipse:eclipse and nested projects
Alan Kent wrote: Q: Is there any way to make mvn eclipse:elipse generate a .project file for the root directory as well as each module? That way I can check out the whole project tree from the root and have a project per pom file. Not that I know of, but this works for me: 1. Check out the parent module into your workspace. 2. mvn eclipse:eclipse to create the various .project and .classpath files in the sub-modules. 3. Switch to the Java perspective in Eclipse. 4. Select the parent module and hit F5 to refresh (just for grins). 5. Choose File-Import..., Existing Projects into Workspace, and browse in your workspace into your parent module. 6. Select one of the sub-modules, make sure Copy projects into workspace is /not/ checked, and hit Finish. 7. Lather, rinse, and repeat steps 5 and 6 with the other submodules. In this way, you can do all of your SCM in Eclipse via the parent module, yet play with the submodules as proper Java projects. As far as I know, this is the recommended way to develop a multi-module project with Eclipse. Someone please correct me if I'm wrong. -- -Greg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Generate DDL with Maven2, Spring2 and Hibernate3
I want to generate a DDL using Maven2, Spring2 and Hibernate3. I would like to use the maven-hibernate3-plugin with the goal hibernate3:hbm2ddl, but I don't use the hibernate.cfg.xml file, instead I'm configuring Hibernate with Spring's LocalSessionFactoryBean. How do I get the hibernate3 plugin to use my configuration? Kind Regards, Jonas - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: moving from maven1 to maven2
it must be converted to plugin configuration - the properties are likely to be different in each case as the plugins behaviour has changed, so you will need to review the plugins on a case by case basis. There are some conversion tools available - you can try mvn one:convert. - Brett On 04/07/07, bhaskar [EMAIL PROTECTED] wrote: where to place the properties defined in project.properties and build.properties of maven1,in maven2 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Snapshot dependency naming problem
Hi all I'm having a problem with dependency jar naming within the war file generated by the WAR plugin. There's a dependency on X-2.0.1-SNAPSHOT.jar, but when maven downloads it form the local repository, it puts it in using the unique timestamped name the way it is stored in snapshot repository. It's fine like that normally, except when you need to include its name in the manifest as Class-Path So you get something like this WAR contents: . `-- WEB-INF `-- lib |-- dep1-1.0.jar |-- dep2-1.0.jar `-- X-2.0.1-20070626.141521-7 war/META-INF/manifest.mf contents: Class-Path: dep1-1.0.jar dep2-1.0.jar X-2.0.1-SNAPSHOT.jar So when application loads, it's trying to set X-2.0.1-SNAPSHOT.jar in the classpath because that's what's listed in the manifest, but doesn't find such library. Is there a workaround for this kind of issue? Is there a way to force certain dependency name when it gets included in the war file? You'd expect maven plugin to figure out to either rename the dependency artifact or use the full unique name in the manifest; does this qualify as a bug? Appreciate any suggestions, -p Be smarter than spam. See how smart SpamGuard is at giving junk email the boot with the All-new Yahoo! Mail at http://mrd.mail.yahoo.com/try_beta?.intl=ca - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[M2] creating Jndi context programmatically
Hi, In my database access (using) hibernate i define the usage of the datasource by jndi. But i don't know how to inject the datasource in the jndi context nor how to inject the jndi context in the testCase.setup method. Any help is welcome. Regards, Raphaël
RE: [M2] creating Jndi context programmatically
Hi, Have a look at plexus-naming [1] which can certainly help. Configure a component as this [2], add this component in loadOnStartup. Note : Your testCase must extends PlexusTestCase. -- Olivier [1] http://fisheye.codehaus.org/browse/plexus/plexus-components/trunk/plexus-naming [2] http://fisheye.codehaus.org/browse/~raw,r=6444/plexus/plexus-components/trunk/plexus-naming/src/test/resources/org/codehaus/plexus/naming/NamingTest.xml -Message d'origine- De : Raphaël Piéroni [mailto:[EMAIL PROTECTED] Envoyé : mercredi 4 juillet 2007 17:55 À : Maven Users List Objet : [M2] creating Jndi context programmatically Hi, In my database access (using) hibernate i define the usage of the datasource by jndi. But i don't know how to inject the datasource in the jndi context nor how to inject the jndi context in the testCase.setup method. Any help is welcome. Regards, Raphaël This e-mail, any attachments and the information contained therein (this message) are confidential and intended solely for the use of the addressee(s). If you have received this message in error please send it back to the sender and delete it. Unauthorized publication, use, dissemination or disclosure of this message, either in whole or in part is strictly prohibited. ** Ce message électronique et tous les fichiers joints ainsi que les informations contenues dans ce message ( ci après le message ), sont confidentiels et destinés exclusivement à l'usage de la personne à laquelle ils sont adressés. Si vous avez reçu ce message par erreur, merci de le renvoyer à son émetteur et de le détruire. Toutes diffusion, publication, totale ou partielle ou divulgation sous quelque forme que se soit non expressément autorisées de ce message, sont interdites. ** - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Axis 1.4 POM files missing on central?
It is impossible for the Maven dev group to be responsible for all the hundreds of poms, and so this is really the responsibility of the project itself to provide the pom, binaries, source, javadocs, etc. File a bug with Axis and perhaps they will resolve the missing poms. Wayne On 7/4/07, Thorsten Heit [EMAIL PROTECTED] wrote: Hi list, one of the projects I'm trying to convert from an Ant build structure to Maven is using Axis. Instead of version 1.1 that is originally used in the Ant build I'm trying to use Axis 1.4 so I added the following snippet to my pom.xml: dependency groupIdaxis/groupId artifactIdaxis/artifactId version1.4/version /dependency which itself has dependencies to axis:axis-jaxrpc:1.4 and axis:axis-saaj:1.4. Each time I execute mvn compile I see the following messages: [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. Downloading: http://localhost:4080/artifactory/repo/axis/axis-jaxrpc/1.4/axis-jaxrpc-1.4.pom Downloading: http://localhost:4080/artifactory/repo/axis/axis-saaj/1.4/axis-saaj-1.4.pom [INFO] [compiler:compile] [INFO] Nothing to compile - all classes are up to date [INFO] When looking at central repo (proxied by a local running instance of Artifactory) I discovered that the above mentioned pom files are missing; also missing is the pom file for axis:axis-ant:1.4. The directories on central only contain the jar files, metadata and their checksums, but no sources jar (apart from axis-ant:1.4). Coincidence? Intention? Apart from the messages the build success, btw... Thorsten - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
problems with mvn2, Spring and Hibernate... anyone could help?
hi all, i know i should post this to maven list but it is about spring and i am sure someone here is using maven for building its environment I have an app composed of 3 project: - domain OBjects , contains domain objects used by web and backend project - backend project contains hibernate code - webapp contains webwork code that uses hibernate to access database i have been searching for solutions for not hardcoding hibernate mapping files.. i came across mappingJarLocations where you can specify jars where hbm.xml file are located. this is fine, however i am building my project using maven2 and i am setting the dependency scope for domainObjects.jar on my backend project.. if i use scopetest/scope test will fail because spring won't be able to find hbm.xml file (jar is not in classpath) if i use scopecompile/scope jar won't be in test classpath i was wondering if anyone on this forum came across same situation... here's my spring context... bean id=sessionFactory class= org.springframework.orm.hibernate3.LocalSessionFactoryBean property name=dataSource ref bean=dataSource/ /property property name=mappingJarLocations valueclasspath*:domainObjects-1.0-SNAPSHOT.jar/value /property property name=hibernateProperties ref bean=exampleHibernateProperties / /property /bean thanks in advancea nd regards marco
Re: Generate DDL with Maven2, Spring2 and Hibernate3
Jonas Thurfors wrote: I want to generate a DDL using Maven2, Spring2 and Hibernate3. I would like to use the maven-hibernate3-plugin with the goal hibernate3:hbm2ddl, but I don't use the hibernate.cfg.xml file, instead I'm configuring Hibernate with Spring's LocalSessionFactoryBean. How do I get the hibernate3 plugin to use my configuration? unfortunately you have to configure it twice - or refactor out your settings to hibernate.cfg.xml and point the spring configured localsession... to it. -- David J. M. Karlsen - +47 90 68 22 43 http://www.davidkarlsen.com http://mp3.davidkarlsen.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Ant Mojo - Maven classpath
Hi All,
Is it possible to pass / access the maven project classpath inside of an
ant mojo build file.
I see that you can with the antrun plugin, but can you do the same with
self written ant mojo's ?
I want to get at :
${maven.dependency.classpath}
${maven.compile.classpath}
${maven.runtime.classpath}
${maven.test.classpath}
${maven.plugin.classpath}
Thanks
Jon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
FW: Using Maven with Eclipse well: mvn eclipse:eclipse and nested projects
An interesting message on the Maven User's list, especially for those (Daryoush!) who have expressed frustration about the inability to mass-perforce-enable all those Eclipse projects that you get when using mvn eclipse:eclipse. I'm not sure I understand completely where he's coming from, but basically it seems like a way to maintain an RRmodules Eclipse project, for the purpose of SCM, and also a bunch of subprojects, for mvn eclipse:eclipse. I'm not positive that this mixture of things will cause Perforce to always check things out automatically if the RRmodules project is Perforce-enabled and the others are not, but it seems worth a try, because it seems to be working for this guy, and I doubt he'd be so enthusiastic if that part didn't work. The downside, which I have discovered myself by accident, is that with this setup you can no longer mass-import Eclipse projects at the RRmodules level, but instead have to do your importing iteratively, one level down. Not a big deal for ongoing updates, but somewhat of a pain the very first time. Happy 4th! Especially to Balazs, who's actually working today, presumably because his East European upbringing didn't instill an irresistable compulsion to grill something outdoors on this special day. -- Bryan -Original Message- From: Greg Thompson [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 04, 2007 5:53 AM To: Maven Users List Subject: Re: Using Maven with Eclipse well: mvn eclipse:eclipse and nested projects Alan Kent wrote: Q: Is there any way to make mvn eclipse:elipse generate a .project file for the root directory as well as each module? That way I can check out the whole project tree from the root and have a project per pom file. Not that I know of, but this works for me: 1. Check out the parent module into your workspace. 2. mvn eclipse:eclipse to create the various .project and .classpath files in the sub-modules. 3. Switch to the Java perspective in Eclipse. 4. Select the parent module and hit F5 to refresh (just for grins). 5. Choose File-Import..., Existing Projects into Workspace, and browse in your workspace into your parent module. 6. Select one of the sub-modules, make sure Copy projects into workspace is /not/ checked, and hit Finish. 7. Lather, rinse, and repeat steps 5 and 6 with the other submodules. In this way, you can do all of your SCM in Eclipse via the parent module, yet play with the submodules as proper Java projects. As far as I know, this is the recommended way to develop a multi-module project with Eclipse. Someone please correct me if I'm wrong. -- -Greg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Using Maven with Eclipse well: mvn eclipse:eclipse and nested projects
Sorry. Not intended for the list. Apologies. -Original Message- From: Bryan Loofbourrow [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 04, 2007 2:43 PM To: *Qpass - Content Catalog Discussion Cc: Maven Users List Subject: FW: Using Maven with Eclipse well: mvn eclipse:eclipse and nested projects An interesting message on the Maven User's list, especially for those (Daryoush!) who have expressed frustration about the inability to mass-perforce-enable all those Eclipse projects that you get when using mvn eclipse:eclipse. I'm not sure I understand completely where he's coming from, but basically it seems like a way to maintain an RRmodules Eclipse project, for the purpose of SCM, and also a bunch of subprojects, for mvn eclipse:eclipse. I'm not positive that this mixture of things will cause Perforce to always check things out automatically if the RRmodules project is Perforce-enabled and the others are not, but it seems worth a try, because it seems to be working for this guy, and I doubt he'd be so enthusiastic if that part didn't work. The downside, which I have discovered myself by accident, is that with this setup you can no longer mass-import Eclipse projects at the RRmodules level, but instead have to do your importing iteratively, one level down. Not a big deal for ongoing updates, but somewhat of a pain the very first time. Happy 4th! Especially to Balazs, who's actually working today, presumably because his East European upbringing didn't instill an irresistable compulsion to grill something outdoors on this special day. -- Bryan -Original Message- From: Greg Thompson [mailto:[EMAIL PROTECTED] Sent: Wednesday, July 04, 2007 5:53 AM To: Maven Users List Subject: Re: Using Maven with Eclipse well: mvn eclipse:eclipse and nested projects Alan Kent wrote: Q: Is there any way to make mvn eclipse:elipse generate a .project file for the root directory as well as each module? That way I can check out the whole project tree from the root and have a project per pom file. Not that I know of, but this works for me: 1. Check out the parent module into your workspace. 2. mvn eclipse:eclipse to create the various .project and .classpath files in the sub-modules. 3. Switch to the Java perspective in Eclipse. 4. Select the parent module and hit F5 to refresh (just for grins). 5. Choose File-Import..., Existing Projects into Workspace, and browse in your workspace into your parent module. 6. Select one of the sub-modules, make sure Copy projects into workspace is /not/ checked, and hit Finish. 7. Lather, rinse, and repeat steps 5 and 6 with the other submodules. In this way, you can do all of your SCM in Eclipse via the parent module, yet play with the submodules as proper Java projects. As far as I know, this is the recommended way to develop a multi-module project with Eclipse. Someone please correct me if I'm wrong. -- -Greg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to execute a system command from maven 2?
Jerome, I'm seeing the same missing executable argument problem. I'm using exec-maven-plugin 1.1-beta-1 My maven POM section is below. I'm pretty sure i have the groupId/artifactID correct. Also, is there any way to fork (ie run the executed command in the background) aside from putting a in the shell script itself? Specifying -Dexec.executable=runExchange.sh does work, but i can't get it to work from inside maven POM itself. thanks! POM: plugin groupIdorg.codehaus.mojo/groupId artifactIdexec-maven-plugin/artifactId configuration executablerunExchange.sh/executable /configuration executions execution idstart-exchange/id phasepre-integration-test/phase goals goalexec/goal /goals /execution /executions /plugin Error: [INFO] One or more required plugin parameters are invalid/missing for 'exec:exec' [0] inside the definition for plugin: 'exec-maven-plugin'specify the following: configuration executableVALUE/executable /configuration -OR- on the command line, specify: '-Dexec.executable=VALUE' -- Toli Kuznets http://www.marketcetera.com: Open-Source Trading Platform download.run.trade. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
