In Maven, a POM is a unit of work, so a project must have just one. Usually, targetting multiple platforms involves setting up multiple projects.
pom.xml - parent that has <modules/> for the following: +- foo-common/pom.xml - shared information +- foo-j2se/pom.xml - j2se specific build, depends on foo-common +- foo-cdc/pom.xml - CDC specific build, depends on foo-common Does this suit your situation? What are the actual differences between the two platforms? We currently have a new solution for environmental specifics in alpha-3 (profiles), however these are not intended to be used to build multiple artifacts from a single build, but rather building differently in separate environments. You may have justification for allowing them to be incorporated into a single build, so I'd like to walk through the use case with you. Cheers, Brett On 6/17/05, Shane Isbell <[EMAIL PROTECTED]> wrote: > For my current project, I am testing a migration from ANT to Maven 2.0 > (alpha 2). I have encountered an issue that I am unable to resolve. I > have a single source tree, but I need to compile and package a JAR > for two different platforms: J2SE and CDC. I have built two separate > pom.xml files: pom-J2SE.xml and pom-CDC.xml, within the same > directory. I was hoping there would be a command similar to ant: ant > -buildfile <myfile> but I have been unable to find it. If this is a > possible solution, I also need to manage the entire platform build > from a master pom.xml, which propagates target platform information > down to the sub projects. Is there a feasible solution in Maven 2.0? > > Thanks, > Shane > > --------------------------------------------------------------------- > 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]
