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?
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?
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 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...
Thank you very much for your kind help. By the way, where are you from? I'm from Spain, and I'm right now trying to stablish as a freelance developer, what about your experience?
Regards Jose
Konstantin Priblouda wrote:
--- Jose Gonzalez Gomez <[EMAIL PROTECTED]>
wrote:
I still don't see the diference or relation
between maven.xml and build.xml. From what I read and your answers I
understand that maven is thought for the development of a "monolithic"
application or library, the one that tipically is bundled in one jar, am I
right?
Yep. Maven is really powerfull for such task. Of course you can produce several artifacts from
single project, but easier way would be to structure
your code
and use reactor to pull the things together.
Maven is really nice when it comes to active
development of several dependent projects at the
same time. Right now, we have 4 projects and 4
developers, without clear separation.
Dependency management ( and artifact distribution ) would be plain unmanageable without maven... )
So if you need a custom build, you still may use
ant... but can you call this build from maven, or must you call ant
directly?
You can call any ant task from maven.xml - because maven uses ant behind the scenes ( but not
only ant )
Think of goals defined in plugins as pre-cooked ant tasks.
regards,
===== Konstantin Priblouda ( ko5tik ) Freelance Software developer < http://www.pribluda.de > < play java games -> http://www.yook.de > < render charts online -> http://www.pribluda.de/povray/ >
__________________________________________________ Do you Yahoo!? Yahoo! Tax Center - File online, calculators, forms, and more http://tax.yahoo.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]
