SS,
When I think modules I think top level directories in the SVN with their
own trunk, tags and branches.
So we would have
/openjump-launcher
/trunk
/tags
/branches
This module would contain any source code for building binary launchers
and installers. I changed my mind from win32 specific as we may want
win64, macosx, linux etc launchers and installers in the future.
You would then compile this module to create the actual executables.
We could also add a copy of the generated binary into the core module
when we generate it for the releases.
By having separate modules they can have their own life cycle that is
independent from the core module.
On the issue of JSmooth v.s. launch4j v.s. eclipse base launcher I
personally think I'd like to take Larry's code and make changes to brand
it as OpenJump as he's done a lot of work to make things work smoothly.
When I tried JSmooth it didn't create a valid exe.
Paul
Sunburned Surveyor wrote:
> Paul,
>
> I don't have a problem with adding a module to the SVN for Microsoft
> Windows specific items either.
>
> Would we make a subdiredtory of /trunk/installer or /trunk/scripts for
> this purpose?
>
> The Sunburned Surveyor
>
>
-------------------------------------------------------------------------
This SF.net email is sponsored by DB2 Express
Download DB2 Express C - the FREE version of DB2 express and take
control of your XML. No limits. Just data. Click to get it now.
http://sourceforge.net/powerbar/db2/
_______________________________________________
Jump-pilot-devel mailing list
Jump-pilot-devel@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel
