In "apps" are we getting to a single artifact per project.xml? Yes!
So, what's the deal with docs? There's struts/trunk/doc and struts/trunk/xdoc.
If I recall correctly, xdoc was a failed attempt to move us over to a different documentation builder. Is that not correct?
Do we want to continue to build the tld and documentation from the same xml? (I am sure the answer is yes, but I need to know for sure). So, that said, what would be our best strategy? Given the new restructuring of apps, we can now build the apps against any version of struts, simply by changing the project.xml (locally).
(from here down, when I say "install", I mean how Maven compiles, JARs, and sticks that
jar under your local .maven/repository/struts/jars)
From a global perspective, what should a full build do? (and in what
order?)
- core - bsf - taglib - docs - apps - el
...come to think of it, with the dependencies declared correctly in project.xml, maven will automatically figure it out for us, right?
Given the decision on a new global script, what kinds of targets do we want to setup?
before: ant dist - did a full distribution ant test.tomcat.x.y - ran the full test suite under jakarta-tomcat-x.y ant release - the "do it all" target that got us
Now that the project is fractured into smaller pieces, we are closer to a continuous integration strategy.
So, those of use that want to use Maven...I'm thinking.... - core:dist (builds a struts-core-x.y.z) - core:install (this installs the new jar) - taglib:dist (simply builds a distribution for this project) - taglib:install (same as core...sort of) - and so on - and so forth
and from core/trunk:
maven global:release(would build a complete distribution of all the latest components or artifacts)
Your thoughts?
-- James Mitchell Software Engineer / Open Source Evangelist EdgeTech, Inc. 678.910.8017 AIM: jmitchtx
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
