On 3/3/06, Martin Cooper <[EMAIL PROTECTED]> wrote: > On 3/3/06, Henri Yandell <[EMAIL PROTECTED]> wrote: > > > > On 3/3/06, Martin Cooper <[EMAIL PROTECTED]> wrote: > > > On 3/3/06, Henri Yandell <[EMAIL PROTECTED]> wrote: > > > > > > > > Yeah, seems Maven 2 picks up the xdoc one first. We should probably > > > > discuss if we want to standardise on one or the other doc format prior > > > > to doing too much more work on the migration. > > > > > > > > > If you decide to standardise on what we have now, I'm right with you. If > > you > > > want to standardise on a new format, and therefore require all > > components to > > > switch to something else, then I'm very likely outta here. I have better > > > things to spend my time on than learning a new format when what we have > > > works just fine. > > > > Two problems with our Maven-1 build: > > > > 1) Maven-1.0.2 is not the latest version from the Maven community, so > > there's the support question etc. Not a huge problem - we're stable > > build-wise etc and don't need new things. > > > > 2) I contend it doesn't work fine. We use some bizarre group of > > non-1.0.2 plugins, and getting the site working is a pain in the arse. > > > IMO, Phil solved that problem by adding this file: > > https://svn.apache.org/repos/asf/jakarta/commons/proper/commons-build/trunk/pluginUpdate.txt > > I haven't had problems since I used that file as a batch file and got the > exact set of plugin versions. Now, I'll be the first to admit that I'm far > from being the most frequent builder of any part of the site, so maybe other > people have problems for some other reason, but for me, everything just > works. I'd like to keep it that way without having to learn a new build > system. If other people want to pull the rug out from under themselves, > that's perfectly fine with me. Just don't pull the rug out from under _me_ > when it's _you_ that's not happy.
Good point. I see a list of problems in Jakarta and Commons - which as I think Commons is the main engine of Jakarta have a fair amount of overlap. I've iterated some on general@; but haven't iterated the Commons problems on commons-dev so that people can tell me that everything is fine in Commons. Will do so. > > Some of the questions are not about our build system. A group id of > > org.apache.jakarta.commons is more about the maven-2 repository and > > how it stores our jars - and what the foundation policy is. > > > I guess I don't understand this part. What does that have to do with xdoc > versus apt? Oops. This was xdoc vs apt? Thought it was part of the larger build/site stuff. I'm +1 to stay on xdoc, was mistake in thinking I had to use apt when migrating. Preferring xdoc, though think HTML is better than any of them. Hen --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
