From: Jody G. <jga...@re...> - 2006-05-17 08:56:51
|
Martin Desruisseaux wrote: >> I have documented the progress I have made so far: >> http://docs.codehaus.org/display/GEOT/How+to+cut+a+release >> >> It's right at the top in the big blue box. > > Can we delete the Maven 1 specific instructions in the above page, and > reformat the blue box as top-level text? I ask that because I would > like to add some additional notes to the Maven 2 release process, but > would prefer to do that in properly formatted text... Remove away, getting useful docs for what works today is rather important. >> Right now I am looking into the maven assembly plug-in to >> automatically create our distribution archives. > If the assembly plugin do what we want, that would be great. Up to > date, I was using some custom plugins as workaround. > > Geotools has a few custom Maven 2 plugins. For example all JAR > (including dependencies) are copied together in the gt/target > directory. If peoples agree, I would suggest to keep all JAR in such > flat directory in our distribution: this help to reduce duplication > (in the Maven 1 distribution, some dependencies were copied many time > in different directories), and is essential if we want to get the > "Class-path" entry in META-INF/MANIFEST.MF to work. Wow not sure I understood that, ... > The current standard Maven javadoc plugin (beta 3) still have a lot of > bugs and is unable to create cross-module javadoc. If possible I would like to get a smaller javaodc of "module/*" - aka just the geotools library. Jody |