ubuntu-gis community,
We, the osgeolive community, wish to improve packaging of java projects on osgeolive, by developing .deb packages, but we are short on expertise on how to make this happen. As below, Jerome has recommended that as a start we extend existing .war packages to .deb packages, and have this role into ubuntugis. To me, this sounds reasonable. Are there any objections or suggestions related to this proposal?

Jerome, Ben, others,
Is there a howto or similar that we can reference, to guide projects in the best practices for converting .war->.deb? I'd like to add a section to our osgeolive processes, and link to it from ~
http://wiki.osgeo.org/wiki/Live_GIS_Add_Project#.deb_Packaging

On 9/06/2014 10:01 pm, Jerome Villeneuve Larouche wrote:
Hi,

Thanks for the tip! I'll take a look.

For GeoServer those were things I found when I looked into it last year, but since I had no experience on how GeoServer buillt and work, I didn't really get it to work. Your expertise will be pretty valuable for this package this year!

And off course the .war -> .deb is simply a quick workaround to try to have some packages ready for OsgeoLive and a way to at least have some Java packages available.

Jerome

On 14-06-08 10:15 PM, Ben Caradoc-Davies wrote:
Hi Jérôme,

have you looked at how Debian packages such as tomcat7-admin handle packing servlets? Even if you are not yet in a position to adopt their patterns, it would help to inform your approach.

One other problem is GeoServer contains some non-free drivers such as the Oracle ojdbc14.jar that is bundled with the Oracle plugin. Debian will require this to be in non-free. Or you could bundle one without ojdbc14.jar and have a script download it (similar tricks are used to install flash). ArcSDE also contains non-free drivers. MS SQL drivers have to be obtained by the user (or at least they were; need to check).

Also, some deployments require JDBC drivers at the tomcat level for JNDI connection pooling between servletss, and having duplicate drivers on the classpath can result in Bad Things Happening. The right way to do with with Debian will be with cunning use of .deb Conflicts.

I am happy for you to go ahead with the simple .war to .deb conversion as you have described; once this is working a detailed translation to .deb is a future work.

Kind regards,
Ben.

On 08/06/14 23:31, Jerome Villeneuve Larouche wrote:
I've also participated in the OsgeoLive meeting this week and talked a
bit about my plans for Java packages. We're thinking of going for a
quick packaging way first by packaging .war to .deb. It won't be
accepted on Debian, but for OsgeoLive and UbuntuGIS it would be a quick
hack to have the packages available. If you have any suggestion or idea
about that, I would be glad to hear them.




--
Cameron Shorter,
Software and Data Solutions Manager
LISAsoft
Suite 112, Jones Bay Wharf,
26 - 32 Pirrama Rd, Pyrmont NSW 2009

P +61 2 9009 5000,  W www.lisasoft.com,  F +61 2 9009 5099

_______________________________________________
Live-demo mailing list
[email protected]
http://lists.osgeo.org/mailman/listinfo/live-demo
http://live.osgeo.org
http://wiki.osgeo.org/wiki/Live_GIS_Disc

Reply via email to