RE: eXist native XML database
Hi there I am one of the eXist developers. We certainly are interested in what our users want, but as yet we have only had 2 or 3 express an interest in using Maven it is unfortunately not a top priority for us at the present time. I myself am a big fan of Maven, and would love to do a port of eXist from Ant (we are heavily invested), over to Maven. Unfortunately I just don't have enough hours in the day at present to undertake this. If there is an experienced Maven developer out there that might be interested in contributing such changes then I would certainly encourage that. For the time being the solution is really to place eXist and its dependencies into your own artifact repository (either local or server e.g. Artifactory et al.) Thanks Adam. -Original Message- From: Wayne Fay [mailto:wayne...@gmail.com] Sent: 09 May 2010 19:00 To: Maven Users List Subject: Re: eXist native XML database I'm working on maven project and I need to use embedded eXist database. Unfortunatelly, there is only 5 years old version in repo1.maven.org. You need to get the eXist people to do the uploads for newer versions of their files. If enough eXist users and developers care about Maven, they will do it. how could I tell maven developers to add required packages to the repository? You don't. If you can't get the eXist folks to get it done, you will need to (less ideally) manually install them into your own local repo cache on each machine that will build your project or (more ideally) install something like Nexus, Archiva, Artifactory and install them there so your coworkers can use the artifacts too. Wayne - 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: Can't avoid Maven (embedded) 3.0-SNAPSHOT with m2eclipse
About the enforcer problem that you can see in the console: I don't if you're having the very same one, but there're many bugs that were fixed in the recent m2e versions. M2E 0.10 fixed a lot of issues and uses a more recent maven3 version. If you're not using it, you should really give it a try. (https://issues.sonatype.org/browse/MNGECLIPSE-1091 or https://issues.sonatype.org/browse/MNGECLIPSE-1361). Then, you should know there's a m2eclipse list if you have particularly specific questions. You should ask questions about this on this list, and maybe file an issue in the m2eclipse bug tracker (sonatype JIRA). Cheers 2010/5/27 Andrew Hughes ahhug...@gmail.com Thanks for the reply... It has to use the embedded maven3 SNAPSHOT to fetch the dependencies. There were a lot of warning regarding missing versions that I fixed (to reduce noise which probably exists for good reason). My case is unique because I was using the enforcer plugin for maven 2.2.1-2..9.9 and this appeared to break the embedded maven AUTO_BUILD. Eventually for some reason (restart, re-import of the projects eclipse:clean) something worked and it stopped using the embedded. However, my co-workers are still suffering. I don't know how I can really re-produce this or gather some kind of dump that will show what I am working with at any point in time. The stack is just too big and it may never be resolved. So this works but seems unreliable. Cheers :) On Mon, May 24, 2010 at 8:19 PM, Baptiste MATHUS m...@batmat.net wrote: Hi Andrew, First, you should know there's a dedicated list for m2eclipse, which is a separated project from Maven, designed to integrate Eclipse and Maven. From what I know, it's impossible. M2eclipse internally uses maven 3 (and has always been doing so, long before maven3 first releases) for all dependency resolution and so on. That is not configurable. But you can configure M2eclipse to use external maven installation for command launched through the Run As/Debug menus. Having read your mail twice, I can't seem to find what your problem is. Maven 3 is dedicated to be fully compatible with maven 2. So can you describe what's the difference/problem you're encountering more precisely? This would let us help you understand what's going on, or even file an issue for maven3 before it's released as a final version (beta1 currently, after several stages of alpha). Thanks 2010/5/24 Andrew Hughes ahhug...@gmail.com *I have set Window - Preferences - Maven - Installed to a external 2.2.1 instance and have enabled this as the default maven instance. But, whatever 24/05/10 9:50:53 AM: Maven Builder: AUTO_BUILD is - it still using the 3.0-SNAPSHOT embedded maven instance. It refuses to use the external maven (2.2.1) instance I have configured. I have deliberately set the enforcer to Maven 2.2.1 so that this doesn't happen (+1 for enforcer actually working, CHEERS).* * * http://m2eclipse.sonatype.org/m2eclipse-faq.html#17 Why is it working from the command line but not in m2eclipse Because m2eclipse is using the embedded Maven runtimehttp://m2eclipse.sonatype.org/m2eclipse-faq.html#version.html in Maven 3.0, you can see differences in the execution between m2eclipse and command line when Maven 2.1.x is used. We hope that such regressions and incompatibilities will be fixed in the future releases of Maven 3.0. Note that m2eclipse is always using embedded Maven runtime when running Maven builder, importing projects and updating project configuration, however you can configure m2eclipse to use external Maven installation when launching Maven using Run as… / Maven XXX actions. The above statement seems incorrect... I can't clearly can't configure m2eclipse to use an external maven instance for the AUTO_BUILD. In fact, I tried to uninstall the Maven Embedded v3.0.0.200912160759 but Haahahaha it say's it's required by other plugins - indicating that m2eclipse really is dependent on 3.0-SNAPSHOT. I just want to use eclipse 2.2.1, how can I do this? Can I rollback to an old version of m2eclipse? Life is very painful for everyone on my dev team right now :'( Any help would be most appreciated, cheers. --AH -- Baptiste Batmat MATHUS - http://batmat.net Sauvez un arbre, Mangez un castor !
AW: Maven Enforcer: Banned dependencies including type, classifier etc.
Ok, I checked JIRA and found http://jira.codehaus.org/browse/MENFORCER-74 http://jira.codehaus.org/browse/MENFORCER-75 http://jira.codehaus.org/browse/MENFORCER-72 (seems to be the same as 75) So, from groupId:artifactId:packaging:classifier:version everything except packaging would be done if these issues are fixed. Best regards, Eric -Ursprüngliche Nachricht- Von: Brian Fox [mailto:bri...@infinity.nu] Gesendet: Freitag, 28. Mai 2010 05:07 An: Maven Users List Betreff: Re: Maven Enforcer: Banned dependencies including type, classifier etc. Yes, it appears to support g:a:v only. I'm sure I had a reason at the time but I can't think of one now. It should be g:a:v:c:t On Thu, May 27, 2010 at 12:11 PM, Lewis, Eric eric.le...@ipi.ch wrote: Hi As far as I know, most Maven plugins rely on the Maven coordinates as described in http://maven.apache.org/pom.html#Maven_Coordinates I just tried to use them in the Maven Enforcer plugin's banned dependencies rule, but from reading the source, it looks like the Maven coordinates are only supported up to the version. Am I right with this? Should I write an enhancement request? Best regards, Eric - 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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
I want Maven to fail
I'm looking for a plugin which has a fail goal, something like: mvn fail-maven-plugin:fail -Dfail.maven.plugin.message=you failed! I've seen how enforcer or antrun can fail on-demand, but I'm looking for something I can fully configure from the command line Thanks -- View this message in context: http://old.nabble.com/I-want-Maven-to-fail-tp28706080p28706080.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: Chaining Maven goals of different Base Directories
This works! Thanks a lot! /close 2010/5/27 Stephen Connolly stephen.alan.conno...@gmail.com define a profile for deploying your app with cargo:deploy bound to the install phase in module A... you can even define defaultGoals in the profile so that all you need to type is mvn -Pmy-deploy-profile -Stephen On 26 May 2010 17:08, Daniel Hoffmann biggibig...@googlemail.com wrote: Defining profiles this way is a good way to group the projects. But the core problem remains: If I call 'clean install cargo:deploy' on this profile, maven executes 'clean install cargo:deploy' on module A and 'clean install cargo:deploy' on module B. But I want it to execute 'clean install' on module A and 'clean install cargo:deploy' on module B. I tried to configure cargo to exclude a file, but I didn´t find a way to do this. And Cargo is defined in a grandparent pom I don´t want to change anyway. Thanks anyway, Daniel 2010/5/25 Peter Bennett ucygfimuihc...@mailinator.com Profiles to the rescue ;-) Define a profile in the top-level pom containing just the the war and ear modules in the modules/ section. -Peter Daniel Hoffmann-6 wrote: 1.) and 2.) are different projects. There are much more projects in 'myproject', so I can´t execute mvn on 'myproject' (without deleting the other projects from my myproject pom), because I don´t want the other projects to be build. Daniel P.S.: I don´t think it makes any differences, but I am using m2e. 2010/5/19 Jesse Farinacci jie...@gmail.com Hi Daniel, On Wed, May 19, 2010 at 9:47 AM, Daniel Hoffmann biggibig...@googlemail.com wrote: 1.) myproject/makewar clean install 2.) myproject/makeear clean install cargo:deploy Daniel Why not attach cargo:deploy to the deploy phase and then call mvn clean deploy? -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not. - 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/Chaining-Maven-goals-of-different-Base-Directories-tp28608528p28670270.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: I want Maven to fail
I'm looking for a plugin which has a fail goal, something like: mvn fail-maven-plugin:fail -Dfail.maven.plugin.message=you failed! Never seen one or needed one myself, but it would be super trivial to build yourself. If you had a good justification for it, you could maybe get it added to the Codehaus Mojo project for broader deployment. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: I want Maven to fail
You could use the enforcer always fail rule in a profile of its own, and then activate from the command line with something like mvn -P alwaysFailProfile enforcer:enforce or even with profile activation using properties, something like: profiles profile idalwaysFailProfile /id activation property namefailure/name /property /activation build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-enforcer-plugin/artifactId version1.0/version executions execution idenforce/id goals goalenforce/goal /goals configuration rules AlwaysFail/ /rules failtrue/fail /configuration /execution /executions /plugin /plugins /build /profile /profiles Ben On 28 May 2010, at 13:12, lukewpatterson wrote: I'm looking for a plugin which has a fail goal, something like: mvn fail-maven-plugin:fail -Dfail.maven.plugin.message=you failed! I've seen how enforcer or antrun can fail on-demand, but I'm looking for something I can fully configure from the command line Thanks -- View this message in context: http://old.nabble.com/I-want-Maven-to-fail-tp28706080p28706080.html Sent from the Maven - Users mailing list archive at Nabble.comhttp://Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.orgmailto:users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.orgmailto:users-h...@maven.apache.org
Re: eXist native XML database
I myself am a big fan of Maven, and would love to do a port of eXist from Ant (we are heavily invested), over to Maven. Unfortunately I just don't have enough hours in the day at present to undertake this. You do realize that simply uploading your artifacts (built by Ant, Eclipse, Netbeans, shell script, whatever) to a Maven repo is very different from actually porting your build to Maven, right? This user is just asking to get your artifacts in Central or another repo. I suggest you consider the Sonatype FOSS forge which is an easy way to make it happen: http://nexus.sonatype.org/oss-repository-hosting.html Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: eXist native XML database
Adam, I work on the struts project here at apache, but I am getting pretty good with maven ;) I'd like to help you guys port to maven... I don't use exist, but came across it recently and was very interested. If you don't mind, I'll start perusing the source and send you questions off-list. Is there a developers mailing list for eXist? -Wes On Fri, May 28, 2010 at 4:59 AM, Adam Retter adam.ret...@landmark.co.uk wrote: Hi there I am one of the eXist developers. We certainly are interested in what our users want, but as yet we have only had 2 or 3 express an interest in using Maven it is unfortunately not a top priority for us at the present time. I myself am a big fan of Maven, and would love to do a port of eXist from Ant (we are heavily invested), over to Maven. Unfortunately I just don't have enough hours in the day at present to undertake this. If there is an experienced Maven developer out there that might be interested in contributing such changes then I would certainly encourage that. For the time being the solution is really to place eXist and its dependencies into your own artifact repository (either local or server e.g. Artifactory et al.) Thanks Adam. -Original Message- From: Wayne Fay [mailto:wayne...@gmail.com] Sent: 09 May 2010 19:00 To: Maven Users List Subject: Re: eXist native XML database I'm working on maven project and I need to use embedded eXist database. Unfortunatelly, there is only 5 years old version in repo1.maven.org. You need to get the eXist people to do the uploads for newer versions of their files. If enough eXist users and developers care about Maven, they will do it. how could I tell maven developers to add required packages to the repository? You don't. If you can't get the eXist folks to get it done, you will need to (less ideally) manually install them into your own local repo cache on each machine that will build your project or (more ideally) install something like Nexus, Archiva, Artifactory and install them there so your coworkers can use the artifacts too. Wayne - 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 -- Wes Wannemacher Head Engineer, WanTii, Inc. Need Training? Struts, Spring, Maven, Tomcat... Ask me for a quote! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
m2eclipse mailing list?
Is there a separate list for m2eclipse questions? Got m2eclipse properly building my aar services, but I get an annoying error on startup. An internal error occurred during: Repository registry initialization. The repositoryId cannot be null when creating new repository! Here is my settings.xml. Maven sees my nexus repository and pulls in all my artifacts from it properly so Im confused as to where this error is coming from. Thanks, Chris settings localRepository./repository/localRepository interactiveMode/ usePluginRegistry/ offline/ proxies proxy active/ protocol/ username/ password/ port/ host/ nonProxyHosts/ id/ /proxy /proxies servers server username/ password/ privateKey/ passphrase/ filePermissions/ directoryPermissions/ configuration/ id/ /server /servers mirrors mirror mirrorOf/ name/ url/ id/ /mirror /mirrors profiles profile activation activeByDefault/ jdk/ os name/ family/ arch/ version/ /os property name/ value/ /property file missing/ exists/ /file /activation properties/ repositories repository releases enabled/ updatePolicy/ checksumPolicy/ /releases snapshots enabled/ updatePolicy/ checksumPolicy/ /snapshots idmayo_rep/id name/name urlhttp://MYSERVERHOST:PORT/nexus/content/repositories/mayo_rep/url layout/ /repository /repositories pluginRepositories pluginRepository releases enabled/ updatePolicy/ checksumPolicy/ /releases snapshots enabled/ updatePolicy/ checksumPolicy/ /snapshots id12345/id name/ urlhttp://mayoweb//url layout/ /pluginRepository /pluginRepositories idmayo_plugin/id /profile /profiles activeProfiles/ pluginGroups/ /settings - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
SCM for cvs version 1.12.12
I am using CVS for my SCM. I have one repository that is version 1.11.14 and one that is 1.12.12. When I try to do a release using the 1.12.12 CVS repository I get the error Received unknown response from server. But when I use the 1.11.14 repository it works. Is there a CVS plugin that will work with 1.12.12? And how do I configure my pom to use it? Tim McGinnis 717 720-1962 Web Development AES/PHEAA == This message contains privileged and confidential information intended for the above addressees only. If you receive this message in error please delete or destroy this message and/or attachments. The sender of this message will fully cooperate in the civil and criminal prosecution of any individual engaging in the unauthorized use of this message. ==
Re: m2eclipse mailing list?
See info here: http://m2eclipse.sonatype.org/project-information.html /Anders On Fri, May 28, 2010 at 15:56, Meeusen, Christopher W. meeusen.christop...@mayo.edu wrote: Is there a separate list for m2eclipse questions? Got m2eclipse properly building my aar services, but I get an annoying error on startup. An internal error occurred during: Repository registry initialization. The repositoryId cannot be null when creating new repository! Here is my settings.xml. Maven sees my nexus repository and pulls in all my artifacts from it properly so Im confused as to where this error is coming from. Thanks, Chris settings localRepository./repository/localRepository interactiveMode/ usePluginRegistry/ offline/ proxies proxy active/ protocol/ username/ password/ port/ host/ nonProxyHosts/ id/ /proxy /proxies servers server username/ password/ privateKey/ passphrase/ filePermissions/ directoryPermissions/ configuration/ id/ /server /servers mirrors mirror mirrorOf/ name/ url/ id/ /mirror /mirrors profiles profile activation activeByDefault/ jdk/ os name/ family/ arch/ version/ /os property name/ value/ /property file missing/ exists/ /file /activation properties/ repositories repository releases enabled/ updatePolicy/ checksumPolicy/ /releases snapshots enabled/ updatePolicy/ checksumPolicy/ /snapshots idmayo_rep/id name/name urlhttp://MYSERVERHOST:PORT/nexus/content/repositories/mayo_rep/url layout/ /repository /repositories pluginRepositories pluginRepository releases enabled/ updatePolicy/ checksumPolicy/ /releases snapshots enabled/ updatePolicy/ checksumPolicy/ /snapshots id12345/id name/ urlhttp://mayoweb//url layout/ /pluginRepository /pluginRepositories idmayo_plugin/id /profile /profiles activeProfiles/ pluginGroups/ /settings - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: eXist native XML database
Good Afternoon Adam before you take long holiday could you offer any information on which MVC framework eXist 1.4 will be supporting? Martin __ 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: Fri, 28 May 2010 09:48:45 -0400 Subject: Re: eXist native XML database From: w...@wantii.com To: users@maven.apache.org Adam, I work on the struts project here at apache, but I am getting pretty good with maven ;) I'd like to help you guys port to maven... I don't use exist, but came across it recently and was very interested. If you don't mind, I'll start perusing the source and send you questions off-list. Is there a developers mailing list for eXist? -Wes On Fri, May 28, 2010 at 4:59 AM, Adam Retter adam.ret...@landmark.co.uk wrote: Hi there I am one of the eXist developers. We certainly are interested in what our users want, but as yet we have only had 2 or 3 express an interest in using Maven it is unfortunately not a top priority for us at the present time. I myself am a big fan of Maven, and would love to do a port of eXist from Ant (we are heavily invested), over to Maven. Unfortunately I just don't have enough hours in the day at present to undertake this. If there is an experienced Maven developer out there that might be interested in contributing such changes then I would certainly encourage that. For the time being the solution is really to place eXist and its dependencies into your own artifact repository (either local or server e.g. Artifactory et al.) Thanks Adam. -Original Message- From: Wayne Fay [mailto:wayne...@gmail.com] Sent: 09 May 2010 19:00 To: Maven Users List Subject: Re: eXist native XML database I'm working on maven project and I need to use embedded eXist database. Unfortunatelly, there is only 5 years old version in repo1.maven.org. You need to get the eXist people to do the uploads for newer versions of their files. If enough eXist users and developers care about Maven, they will do it. how could I tell maven developers to add required packages to the repository? You don't. If you can't get the eXist folks to get it done, you will need to (less ideally) manually install them into your own local repo cache on each machine that will build your project or (more ideally) install something like Nexus, Archiva, Artifactory and install them there so your coworkers can use the artifacts too. Wayne - 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 -- Wes Wannemacher Head Engineer, WanTii, Inc. Need Training? Struts, Spring, Maven, Tomcat... Ask me for a quote! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org _ The New Busy is not the old busy. Search, chat and e-mail from your inbox. http://www.windowslive.com/campaign/thenewbusy?ocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_3
Re: Chaining Maven goals of different Base Directories
Dan, On Fri, May 28, 2010 at 8:18 AM, Daniel Hoffmann biggibig...@googlemail.com wrote: This works! Thanks a lot! define a profile for deploying your app with cargo:deploy bound to the install phase in module A... you can even define defaultGoals in the profile so that all you need to type is mvn -Pmy-deploy-profile Why didn't you just attach cargo:deploy to the deploy phase within the WAR module?? I told you this 9 days ago. -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Mavenizing a project
I'm working on Mavenizing a small project. In the current project, there are three source directories. The Main source, the JUnit test source and a dir called test_informal that contains some helper classes for doing interactive testing... In a maven project, where would one put that type of source? -- Greg Akins http://insomnia-consulting.org http://www.pghcodingdojo.org http://pittjug.dev.java.net http://twitter.com/akinsgre http://www.linkedin.com/in/akinsgre - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Mavenizing a project
My advice is to fit your needs into Maven's standard directory layout (project structure). http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html Your main source and junit source will fit well there. Unsure how your helper classes fit in but it seems to me that the case can probably be made for that to be packaged within the test source branch as well. SF On Fri, May 28, 2010 at 1:26 PM, Greg Akins angryg...@gmail.com wrote: I'm working on Mavenizing a small project. In the current project, there are three source directories. The Main source, the JUnit test source and a dir called test_informal that contains some helper classes for doing interactive testing... In a maven project, where would one put that type of source? -- Greg Akins http://insomnia-consulting.org http://www.pghcodingdojo.org http://pittjug.dev.java.net http://twitter.com/akinsgre http://www.linkedin.com/in/akinsgre - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Mavenizing a project
On Fri, May 28, 2010 at 1:43 PM, Steve Francolla sfranco...@gmail.com wrote: My advice is to fit your needs into Maven's standard directory layout (project structure). http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html Your main source and junit source will fit well there. Unsure how your helper classes fit in but it seems to me that the case can probably be made for that to be packaged within the test source branch as well. That seems like it might work better for my team. I think I'll have a bit more of a fight if I have to create a separate project. And truth is, I don't even think these tests get executed anymore. I just need to keep them intact until I can replace them with something better. -- Greg Akins http://insomnia-consulting.org http://www.pghcodingdojo.org http://pittjug.dev.java.net http://twitter.com/akinsgre http://www.linkedin.com/in/akinsgre - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Mavenizing a project
My experience has consistently been that if I adapt my projects to Maven instead of vice-versa, life is just peachy. Have yet to come across a circumstance in Maven that hasn't already been solved for. Just go with it. On Fri, May 28, 2010 at 2:04 PM, Greg Akins angryg...@gmail.com wrote: On Fri, May 28, 2010 at 1:43 PM, Steve Francolla sfranco...@gmail.com wrote: My advice is to fit your needs into Maven's standard directory layout (project structure). http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html Your main source and junit source will fit well there. Unsure how your helper classes fit in but it seems to me that the case can probably be made for that to be packaged within the test source branch as well. That seems like it might work better for my team. I think I'll have a bit more of a fight if I have to create a separate project. And truth is, I don't even think these tests get executed anymore. I just need to keep them intact until I can replace them with something better. -- Greg Akins http://insomnia-consulting.org http://www.pghcodingdojo.org http://pittjug.dev.java.net http://twitter.com/akinsgre http://www.linkedin.com/in/akinsgre
RE: Mavenizing a project
one is re-factoring your ANT taskdef class into a Mojo path of least resistance is to stick with antrun http://maven.apache.org/plugins/maven-antrun-plugin/ 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: Fri, 28 May 2010 14:56:37 -0400 Subject: Re: Mavenizing a project From: sfranco...@gmail.com To: angryg...@gmail.com CC: users@maven.apache.org My experience has consistently been that if I adapt my projects to Maven instead of vice-versa, life is just peachy. Have yet to come across a circumstance in Maven that hasn't already been solved for. Just go with it. On Fri, May 28, 2010 at 2:04 PM, Greg Akins angryg...@gmail.com wrote: On Fri, May 28, 2010 at 1:43 PM, Steve Francolla sfranco...@gmail.com wrote: My advice is to fit your needs into Maven's standard directory layout (project structure). http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html Your main source and junit source will fit well there. Unsure how your helper classes fit in but it seems to me that the case can probably be made for that to be packaged within the test source branch as well. That seems like it might work better for my team. I think I'll have a bit more of a fight if I have to create a separate project. And truth is, I don't even think these tests get executed anymore. I just need to keep them intact until I can replace them with something better. -- Greg Akins http://insomnia-consulting.org http://www.pghcodingdojo.org http://pittjug.dev.java.net http://twitter.com/akinsgre http://www.linkedin.com/in/akinsgre _ The New Busy is not the too busy. Combine all your e-mail accounts with Hotmail. http://www.windowslive.com/campaign/thenewbusy?tile=multiaccountocid=PID28326::T:WLMTAGL:ON:WL:en-US:WM_HMP:042010_4
[ANN] Maven Doxia 1.1.3 and Maven Doxia Site Tools 1.1.3 Released
The Maven team is pleased to announce the release of the Maven Doxia and Maven Doxia Site Tools, version 1.1.3 http://maven.apache.org/doxia/ Release Notes - Maven Doxia - Version 1.1.3 ** Bug * [DOXIA-370] - Confluence module cannot parse horizontal separator * [DOXIA-374] - Xdoc: tables without border attribute get a border * [DOXIA-379] - Regression: title block isn't parsed in APT file if comment is present before it * [DOXIA-382] - Sink cannot be reused after parsing with ConfluenceParser * [DOXIA-384] - Including a DTD reference in a source element results in a SAXParseException * [DOXIA-385] - Xdoc: tables without align attribute is center aligned * [DOXIA-390] - Validation logic is not correct ** Improvement * [DOXIA-376] - FO: add periods to numbered lists * [DOXIA-392] - Switch off xml validation by default ** Task * [DOXIA-391] - Repare markmail references Release Notes - Maven Doxia Sitetools - Version 1.1.3 ** Improvement * [DOXIASITETOOLS-37] - Make SiteRenderer validate xml docs Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Mavenizing a project
Put your tests in src/test/java as normal. If your helper classes are to be used by multiple projects, create a new project just for the helper classes, call it foo-test or something. Put the helper classes in src/main/java in the foo-test project, not src/test/main. Then you can create a dependency with test scope on foo-test from the projects that need the test helper classes. If you don't use that little trick, project B cannot depend on project A for it's test classes because the final artifacts never contain test classes. Brian On May 28, 2010, at 1:26 PM, Greg Akins wrote: I'm working on Mavenizing a small project. In the current project, there are three source directories. The Main source, the JUnit test source and a dir called test_informal that contains some helper classes for doing interactive testing... In a maven project, where would one put that type of source? -- Greg Akins http://insomnia-consulting.org http://www.pghcodingdojo.org http://pittjug.dev.java.net http://twitter.com/akinsgre http://www.linkedin.com/in/akinsgre - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] Maven Antrun Plugin 1.4 Released
The Maven team is pleased to announce the release of the Maven Antrun Plugin, version 1.4 This plugin allows Ant tasks to be run inside a Maven build. See the plugin's site for more details: http://maven.apache.org/plugins/maven-antrun-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-antrun-plugin/artifactId version1.4/version /plugin Release Notes - Maven 2.x Antrun Plugin - Version 1.4 ** Bug * [MANTRUN-51] - Problems with multiple antrun declarations in multiproject * [MANTRUN-62] - line.separator property not passed properly to ant * [MANTRUN-104] - Documentation for referring to artifacts classpaths is wrong * [MANTRUN-139] - There is a problem with the site plugin preventing proper site documentation ** Improvement * [MANTRUN-40] - Properties defined in pom properties do not propagate to the antrun environment * [MANTRUN-110] - mistake in antrun docs: refid=maven.dependency * [MANTRUN-126] - Antrun plugin should follow the more common pattern groupId:artifactId:classifier:type pattern for dependency properties. * [MANTRUN-128] - Deprecate sourceRoot and testSourceRoot parameters in favor of using build helper maven plugin * [MANTRUN-135] - Mark antrun plugin as @threadSafe * [MANTRUN-136] - Upgrade to ant 1.8.1 * [MANTRUN-137] - Use ant-nodeps artifact instead of ant and ant-launcher ** New Feature * [MANTRUN-100] - Allow antrun plugin to attach artifacts to maven build * [MANTRUN-138] - Add version mapper to Antrun similar to the Maven Ant tasks ** Wish * [MANTRUN-47] - Provide FileSet references dependencies. Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Mavenizing a project
If you don't use that little trick, project B cannot depend on project A for it's test classes because the final artifacts never contain test classes. That is one way to do it... but I'd suggest the test-jar approach: http://maven.apache.org/guides/mini/guide-attached-tests.html Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
