hi Michael,

On 12.01.2012 08:39, Michaël Michaud wrote:
> Last time I compiled with my good old ant build file (yesterday),
> I get the following version named
> Version ${version.number} ${version.release} rev.${version.revision}

it's easier to replace placeholders

> OK, time for me to switch to maven, I suppose
> Could you give some hints or a documentation for newbies :
> The old pom file used to have 2 small dependencies.
> Did you remove them to gather everything in a single pom file ?

no i retailored as follows, all files now in etc/mvn to not fill up trunk root 
needlessly
bin_zip-<edition>_<release>.xml
- currently 4 files, the assemblies that pick the correct assembly components 
for the specific edition e.g. bin_zip-core_snapshot.xml
 . remember we keep the language files extracted in the snapshots, while 
releases do not carry sources in oj.jar ;)
cmp_oj-<hint>.xml
- oj.jar in different flavors
cmp_core.xml
- includes all files for the CORE distro
cmp_plus.xml
- includes additional files for PLUS

> What are the options
> - to simply compile
> - to release
> - to release sources*, doc...
> - to release automatically the NB?

A) i don't actually only compile. it is used locally or on a server to package 
releases. we would have to overhaul it some more for that as it currently 
compiles into target/classes .

B) mvn release [-P <core,plus,[release> -D version.number=X.X.X [-D 
version.release=]]]

- you can select one or more profiles core, plus (both are the snapshots) or 
release (builds releases for CORE and PLUS)
- without a given profile CORE snapshot will be built by default
- for releases you might want to give a version.number (default=unknown) and a 
version.release (default=stable)

C) didn't think about sources so far, but if you'd like to have them zipped 
automatically i'll make it happen. what do you mean with 'doc,...', javadocs?

D) releasing to sf.net is done via shell scripting on my server, statically to 
snapshots. so if you want to release a release build on your site you will have 
to manually push it to sf.net files section.
 
> On JPP download page, after my last change, 10 files have been uploaded
> in NB directory (over 200 Mo) !
> Is that really necessary ?

probably not ;) .. i was playing with linux distros to have native libs have 
their symlinks withing the distro. we will probably end up having izpack 
setting these up during installation.

> What are the differences between
> OpenJUMP-x.y.z-rrrrr-CORE.zip and
> OpenJUMP-aaaa-mm-dd-rrrrr-CORE.zip ?

http://www.mail-archive.com/jump-pilot-devel@lists.sourceforge.net/msg09977.html

> How the final release will be recognized from NB ?

we build them with 
 mvn release -P release -D version.number=X.X.X
and release them to sf.net/files/OpenJUMP/X.X.X

> Why are there as many linux distro as standard distro ?

essentially tgz versions of the zip. has to do with the symlink issue, but i'll 
drop this again.
 
> * for documentation, I use the following url, but I'm not sure it is 
> uptodate
> any idea how to automatize that ?
> http://jump-pilot.sourceforge.net/javadoc/openjump_javadoc/

would have to find out. if not by maven i could simply run javadoc daily and 
upload the result to sf.net webspace.

> 
> Sorry for asking so many questions and thanks for all the work done on 
> release side.

it's work in progress. when it's finished please remind me to update the 
wikipage accordingly... ede

> 
> Michaël
> 
> ------------------------------------------------------------------------------
> RSA(R) Conference 2012
> Mar 27 - Feb 2
> Save $400 by Jan. 27
> Register now!
> http://p.sf.net/sfu/rsa-sfdev2dev2
> _______________________________________________
> Jump-pilot-devel mailing list
> Jump-pilot-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

------------------------------------------------------------------------------
RSA(R) Conference 2012
Mar 27 - Feb 2
Save $400 by Jan. 27
Register now!
http://p.sf.net/sfu/rsa-sfdev2dev2
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Reply via email to