Martin Desruisseaux wrote:
Richard Gould a écrit :
I have successfully built all of the release jars for 2.2-RC3 and they
have been uploaded to maven.geotools.fr. The only part that remains is
to have the release process construct the standard binary/src/javadoc
archives that we use for normal distribution.
Thanks a lot for yours work.
No problem!
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...
Yeah, I was intending to properly format it and clean it up once the
release process was done and (more or less) finalized. I'll see if I can
do it tomorrow.
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.
I agree that a flat hierarchy is better for the binary release. I have
been able to make an assembly directive that creates a proper binary zip
file with a flat hierarchy. I have not had success with javadoc or
sources though.
Someone on #maven recommended that I check out the <moduleSets/>
directive, but I can't find *any* documentation on how to use it. It
seems to aggregate project items (which seems to be what we want) but it
chokes on projects that have no artifacts (gt2, module, plugin, ext,
etc.). When I exclude those projects, I get this rather cryptic message:
-------------------------------------------------------
T E S T S
-------------------------------------------------------
[INFO] [jar:jar]
[INFO] Building jar:
/home/rgould/dev/gt-2.2.x/2.2.x/target/checkout/ext/widgets-swing/target/gt2-widgets-swing-2.2-RC3.jar
[INFO] [gt2-jar-collector:collect {execution: default}]
[INFO] [assembly:assembly]
[INFO]
------------------------------------------------------------------------
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Error creating assembly: You must set at least one file.
For now, cross-module javadoc is generated using the following custom
plugin:
mvn org.geotools:gt2-javadoc:javadoc
Does this create the javadoc zip archive that was normally generated
during maven 1 createRelease?
Do you have anything similar for creating the source archive?
The current standard Maven javadoc plugin (beta 3) still have a lot of
bugs and is unable to create cross-module javadoc.
I am asking the maven list for help now. Hopefully I might have
something tomorrow.
-------------------------------------------------------
Using Tomcat but need to do more? Need to support web services, security?
Get stuff done quickly with pre-integrated technology to make your job easier
Download IBM WebSphere Application Server v.1.0.1 based on Apache Geronimo
http://sel.as-us.falkag.net/sel?cmd=lnk&kid0709&bid&3057&dat1642
_______________________________________________
Geotools-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/geotools-devel
