I'm not aware of any published "best practices for people who want to
use Maven but can't follow the conventions".
Perhaps someone else will reply with something more useful. My general
response is "do what works best for you".
Wayne
On 10/15/07, Saloucious <[EMAIL PROTECTED]> wrote:
>
> Sure this is painful.
>
> The only solution I have found is :
>
> my-app
> |-- pom.xml
> |-- build.xml
> |-- src
> | |- App.java
> |
> |--m2
> |--jar
> | |--pom.xml
> |
> |--ejb
> | |--pom.xml
> |
> |--sar
> |--pom.xml
>
>
> Is better to put everything in one pom.xml, with many classifier attached
> artifacts ?
>
>
>
> Wendy Smoak-3 wrote:
> >
> > On 10/12/07, Graham Leggett <[EMAIL PROTECTED]> wrote:
> >
> >> Get the most simplest part of your project (the jars) building cleanly
> >> with maven, and use this as a testing ground to get you familiar with the
> >> maven build process. Do this on the existing sources if you can, by
> >> dropping in pom.xml into the root of each jar as necessary. It will
> >> probably become apparent as you go on that some of your code needs to be
> >> restructured. Do this as necessary, updating your ant build as you go
> >> along to keep everything working.
> >
> > I agree, but the original message specifically said "without changes".
> > That's a huge red flag to me that things are about to get very
> > painful for everyone involved.
> >
> > --
> > Wendy
> >
> >>
> >> Sometimes, you may find that an ant build produces more than one
> >> artifact,
> >> such as an EJB, and then an EAR file. What we did was to create new
> >> projects alongside the EJB project, which only built the EAR file (This
> >> project contained a pom.xml file and nothing else).
> >>
> >> Eventually we were ready to wean people off the ant build and get things
> >> going with maven only, and the conversion has worked very well.
> >>
> >> The prize at the end of all this work is worth it: All our code is built
> >> and tested using continuous integration, with no platform or machine
> >> specific build setups (we had hard coded paths *everywhere*).
> >>
> >> A release is tested, tagged, and built from the pristine tag (no more
> >> releases from working copies) start to finish within 30 minutes ("Help!
> >> We
> >> need to get this bugfix into UAT as soon as possible!", "No problem".),
> >> and we now have the *exact* source code used to create a production
> >> release ("Help! We need to replicate this production problem in a
> >> development environment!", "No problem").
> >>
> >> The docs are all auto-built and auto-deployed ("Help! We need to cook up
> >> a
> >> plan to make javadocs available, which will be very difficult!", "Already
> >> done, here is the URL").
> >>
> >> Regards,
> >> Graham
> >> --
> >>
> >>
> >>
> >> ---------------------------------------------------------------------
> >> 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]
> >
> >
> >
>
> --
> View this message in context:
> http://www.nabble.com/Maven-good-Design-tf4610394s177.html#a13219789
> 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]
