If you are truly "converting" from Ant to Maven, the correct approach would be to "convert" the application structure into the suggested Maven layout.
You should be able to do this in a branch in your SCM so as to not disturb the rest of your team until you are ready to finalize your changes. Wayne On 10/11/07, Saloucious <[EMAIL PROTECTED]> wrote: > > Sorry for the really poor subject title, Ant to Maven : Best Practises would > be better ... > > > > Saloucious wrote: > > > > Hi, > > > > i'm newbie with Maven and i'm in charge to convert application projects > > from Ant to Maven > > > > Each Ant scripts creates one or more artifacts : jar , ejb, aar, sar (with > > embeded artifacts) ... > > As i can see in Maven : one pom.xml = one artifact (recommanded). > > > > I search a good design solution to convert these Ant's processes to Maven > > (without changes). > > > > What i've proposed to my manager is to create in each root project dir a > > m2 dir > > > > In root project direct, a parent pom.xml with reference to module in m2 > > dir. > > > > We can easily see which artifacts are produced by project, and we can > > create artifacts with embded artifacts (eg: ejb go into sar ...) > > > > my-app > > |-- pom.xml > > |-- build.xml > > |-- src > > | |- App.java > > | > > |--m2 > > |--jar > > | |--pom.xml > > | > > |--ejb > > | |--pom.xml > > | > > |--sar > > |--pom.xml > > > > > > Is a good design ? Have you any better ideas ? > > > > Thanks > > > > -- > View this message in context: > http://www.nabble.com/Maven-good-Design-tf4610394s177.html#a13166299 > 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]
