Hi
> my priorities are now - osgeo-livedvd updates
> what do you mean by these?
Update of installation script (done), icon (done) and documentation (to 
be done)
>
>> - source distribution
>> - plus distribution
>> - exe installer
> i have the feeling that changing everything in trunk for 1.5 and taking those 
> snapshots only fixing the strings in readme and properties would do the 
> trick. don't you think?
Yes, the core bin distribution is quite easy.
Just need a small todo list not to forget anything (to be written next 
time if we use maven for release).
>
> if you could give me the next week i could play with izpack and see if i 
> could have a n automated installer build setup, who says we have to ave an 
> installer right away.
Yes, I've already used IzPack a long time ago. Nice software.
>
>> would be happy if you could test, test and test again... (mainly
>> linux/windows that I did not test at all)
>> - ede, do you know how to setup the svn to create a
>>     a 1.5.0 tag and a 1.5.0 branch
>>     (trunk woul become the 1.6 branch ?)
> branches make only sense if you plan to actually keep those and take the 
> doubled effort of patching dev/stable branches with fixes. don't really see 
> the need for it. a simple tag of the revision should suffice, will do so when 
> we have that revision. ok?
OK, we'll consider the question again when we'll actually have more 
developpement ressources.
> Ede, I changed the .bat after I found that on windows 64 box
> having only a 32 bits jvm openjump did not start  .
> Unfortunately, I have now a problem to re-install a 64 bits jvm
> so I can't test the bat will run in this case too.
> Can you review the code ? Test it ?
> will do .. ede
Thanks
>
>> Thanks,
>>
>> Michaël
>>
>>
>> Le 07/01/2012 13:34, [email protected] a écrit :
>>> 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
>>> [email protected]
>>> 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
>> [email protected]
>> 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
> [email protected]
> 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
[email protected]
https://lists.sourceforge.net/lists/listinfo/jump-pilot-devel

Reply via email to