Hi,
some words to the libraries: I personally prefer the maven build. The ant
build is used for release builds and the maven build for the nightly
snapshot. I really like about the maven build that the filenames of the
jars are more readable and that it is not necessary to bundle the jars in
the repository.
Two weeks ago I experimented a bit with the maven build and the source
layout and copied the sourcecode of some releases the a new repository. The
size was minimized from 120 MB of an svn export of OpenJUMP to a zipped
file of 2 MB.
The only difference in the compilation result is, that I stripped the big
unicode font away.
Repository with releases (also see "Downloads" tab):
https://github.com/hastebrot/openjump-core-rels
Here is a transscript of what I changed and stripped away:
http://cloud.github.com/downloads/hastebrot/openjump-core-rels/openjump-core-rel-transscript.txt
--Benjamin
2012/1/7 <edgar.sol...@web.de>
> On 07.01.2012 10:01, Michaël Michaud wrote:
> > Hi Ede, Stefan,
> >
> > Some notes and questions about packaging/releasing
> >
> > I'm comparing the ant build with the NB maven results and noticed some
> differences :
> >
> > *ant build*
> > - includes all jar and dll of plus distribution
> > * I will make a core distribution by hand and update the build to have
> choice between core and plus
> > * I think I just have to exclude batik.jar and PLUS dir for core distro
>
> sounds reasonable. for the sake of administration we should maybe decide
> to use either ant or maven? in the future?
>
> > - manifest includes all jars (should include only core jar)
>
> don't use ant, dunno about it
>
> > *maven build (core nb)*
> > - includes junit.jar which is probably useless for core
>
> you can remove it if you are sure. comment it out in pom.xml. we'll see if
> something breaks in the snapshots ;)
>
> > - manifest is empty (cannot start OJ from jar)
>
> removed it because oj has to be started with the scripts anyway to be
> useful
>
> > Question : for your daily developments, do you use and
> > test OpenJUMP after a compilation made from ant, from mvn or another way
> ?
>
> i run and debug with eclipse run configurations.
>
> for quick checks of fixed or changed functionality by others i use the
> snapshots. especially on machines where eclispse is not set up.
>
> >
> > *Different jar versions :*
> >
>
> never changed any of that sorry.. ede
>
>
> ------------------------------------------------------------------------------
> Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
> infrastructure or vast IT resources to deliver seamless, secure access to
> virtual desktops. With this all-in-one solution, easily deploy virtual
> desktops for less than the cost of PCs and save 60% on VDI infrastructure
> costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
> _______________________________________________
> Jump-pilot-devel mailing list
> Jump-pilot-devel@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
>
------------------------------------------------------------------------------
Ridiculously easy VDI. With Citrix VDI-in-a-Box, you don't need a complex
infrastructure or vast IT resources to deliver seamless, secure access to
virtual desktops. With this all-in-one solution, easily deploy virtual
desktops for less than the cost of PCs and save 60% on VDI infrastructure
costs. Try it free! http://p.sf.net/sfu/Citrix-VDIinabox
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
