Hi Julien, > -----Original Message----- > From: Julien Dubois [mailto:[EMAIL PROTECTED] > Sent: 17 September 2003 22:52 > To: Cactus Developers List > Subject: Re: Maven build patches accepted! > > Hi Vincent, > > Some quick replies and one big question: > > > 2 things: > > - what is your strategy for xdocs? Do you plan to convert every single > > xdoc file to the maven format? > > I'm just trying to keep the xdocs the way it is for the moment. For that I > have two options > 1. Trying to generate the site from Maven, as normal. > Just use my documentation/project.xml with "maven site". It's very basic, > and > I don't know xdocs/maven enough to know if it's totally stupid or not. But > it > might work.
No it won't. Or at least it won't give what we want. The xdocs DTDs are different. > 2. Do my own Maven goal. This would be a lot like what's Ant doing I > guess. > It's more work, and it would require some maintenance, so I'll leave that > as > option B. That will work and I believe this is what we should do for now. The goal should simply do the same as is currently in the Ant build file for generating the web site. Easy to do. The tricky part will be to link the Maven reports but we can leave that for later. > > > - why do you need to have navigation.xml pointing to ../dtds ? > > I don't need it. But in the current navigation.xml, there's a link to that > DTD. So when Maven is working on that file, it fails to find the DTD, and > the > build fails miserably. I can't find navigation.xml on your web site. I'm still not sure why you need the link to that DTD! Simply remove it. In all my navigation.xml, I never use any reference to any DTD. > > *And now for the big question* > I've got two projects (framework and samples/servlet for example). Project > B > depends on project A, because it uses classes compiled or packaged by > project > A. > Well, how on earth do I make this link? > If you're using Eclipse, it's the same thing as in the project properties > > > Java build path > projects (projects required on the build path). Ok, That's easy! Simply call jar:install on project A. This will put project's A jar in the local repository. Then in project B, declare a dependency on project's A jar artifact. You can do that for any artifact type (not just jar). For example if you're doing this for a zip, simply use the <artifact:install> tag, etc. -Vincent --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
