Jose Gonzalez Gomez <[EMAIL PROTECTED]> wrote on 02/04/2003 09:23:23 PM:
> > So do you have this projects in different locations, or could you > just create several project.properties (or whatever) to specify the > information for this projects and keep all the source under a common > location and/or repository? Usually several projects with a common parent directory where I work. > Currently I'm developing a J2EE application that has a war and two > ejb jars, that's why I'm so interested in this issue. Could you please > outline you file hierarchy? basedir /war-project /ejb-jar1-project /ejb-jar2-project /ear-project > I understand that you could override some of the standard goals and > finally call your custom build script if those standard goals doesn't > match your interests, couldn't you? Or create new goals... By the way, > what are the standard cases? I've seen goals in maven for j2ee:ejb, > j2ee:war, etc, but they seem to be oriented for a J2EE application with > a single war and a single jar file, am I wrong? I have the feeling that You're wrong. ears can depend on wars and jars and bundle them into the resulting ear file. Wars can depend on jars and bundle them into the resulting war file > maven is rather inmatture in this sense, I mean, working with a fairly > complex J2EE application requires some hacking or workaround to get > maven working (or using reactor, as you point out in your last mail). > Maybe I just don't know how to use it... Or there are bugs in Maven. It should be able to handle complex j2ee apps. -- dIon Gillard, Multitask Consulting Blog: http://www.freeroller.net/page/dion/Weblog Work: http://www.multitask.com.au --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
