news <[EMAIL PROTECTED]> wrote on 01/10/2003 12:36:12 AM: [snip] > Some projects want to use Forrest. There are a lot of features for Forrest > that are really nice--if you know how to use them. There has been some work > to simplify the forrest integration, but it seems that Maven dist and deploy > want to use the Maven format for XDocs and its own document system. There > is no support for integrating with the Forrest XDocs format, or having the > dist target use the Forrest plugin.
Someone could take the xdocs plugin and use what Vincent has committed as a 'caller' plugin, and work out how to get forrest to place nice with Maven. This is OSS, and unless there's an itch for someone, it doesn't happen. > I imagine that certain things like that can be componentized so that when > we call the xdocs build targets, it deferrs either to the Maven or the Forrest > integration plugin. That would be preferred. However, how to do that seems > like a pipe dream with current Maven. It's as if there needs to be > a "document > plugin interface" of sorts. It's easy enough to do. It just takes time, effort, and someone who understands Maven and Forrest. > Also, getting started--esp. if you have several smaller projects that make up > one larger project is not very easy. For instance I have my GUIApp project > using Maven. It works great, and the reactor (once I got it working) does its > job. Unfortunately, getting the parent project to create a distribution with > the proper documentation and packaging isn't set up. I'm somewhat at a loss > how to do this. Have you looked at how Maven produces it's installation/distribution? > Conversely, with ANT, while it can be painful, it is obvious how to get things > done. It's also DEAD easy to write Maven plugins. > I think the best thing that describes developing a Maven plugin, andtrying to > make it work the way you want it to is "emergent behavior". In [snip] You mean something like http://wiki.codehaus.org/maven/HowToCreateYourFirstPlugIn2 is "emergent behaviour"? You and I have very different opinions on that one. > As it is, Maven is very usable, and I like it alot. I also think it can be > improved to provide some level of predictability. Speak to me in words I can use to create issues :-) -- dIon Gillard, Multitask Consulting Blog: http://blogs.codehaus.org/people/dion/ --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
