Hello All, I find myself building and wanting to package more and more apps written in java which use maven as the build/dependency tool. Java devs seem to be more then happy to allow maven to grab and trust xyz.jar from whatever external repo it can found on. Repackaging jar's is unclean and any dependencies need to be available as rpm packages and this is something I've been struggling with for java packages, especially since a few I'd like to push into Factory at some point, examples being puppetdb and wirefly. For other development languages, lets use perl, we have tools like cpanspec which does a great job of grabbing the source and creating the spec files. There are also some automated process on the build service which create packages in devel:languages:perl:CPAN-[A-Z] repo's so it's super easy to branch them and push them into devel:languages:perl and subsequently into Factory or another devel repo. Is anyone aware of a cpanspec like tool for java libraries to accomplish this? I've looked briefly but haven't found anything. I dont' know if anyone as SuSE's put any thought into this, but I figured i'd ask. thanks! -- Later, Darin -- To unsubscribe, e-mail: opensuse-java+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-java+owner@opensuse.org
On Mon, Dec 23, 2013 at 12:21 PM, Darin Perusich
I find myself building and wanting to package more and more apps written in java which use maven as the build/dependency tool. Java devs seem to be more then happy to allow maven to grab and trust xyz.jar from whatever external repo it can found on. Repackaging jar's is unclean and any dependencies need to be available as rpm packages and this is something I've been struggling with for java packages, especially since a few I'd like to push into Factory at some point, examples being puppetdb and wirefly.
Maven is a big problem. E.g. see recent thread: http://lists.opensuse.org/opensuse-java/2013-12/msg00000.html Not sure what the best solution is, but we definitely need something. -Archie -- Archie L. Cobbs -- To unsubscribe, e-mail: opensuse-java+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-java+owner@opensuse.org
On Mon, Dec 23, 2013 at 3:03 PM, Archie Cobbs
On Mon, Dec 23, 2013 at 12:21 PM, Darin Perusich
wrote: I find myself building and wanting to package more and more apps written in java which use maven as the build/dependency tool. Java devs seem to be more then happy to allow maven to grab and trust xyz.jar from whatever external repo it can found on. Repackaging jar's is unclean and any dependencies need to be available as rpm packages and this is something I've been struggling with for java packages, especially since a few I'd like to push into Factory at some point, examples being puppetdb and wirefly.
Maven is a big problem. E.g. see recent thread:
http://lists.opensuse.org/opensuse-java/2013-12/msg00000.html
Not sure what the best solution is, but we definitely need something.
I came across this XMvn package/project which looks like a promising solution to this. I'll need to grab the source and/or fedora packages and see what needs to be done to package for SuSE. http://mizdebsk.fedorapeople.org/xmvn/site/ -- To unsubscribe, e-mail: opensuse-java+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-java+owner@opensuse.org
On 23/12/13 21:18, Darin Perusich wrote:
I came across this XMvn package/project which looks like a promising solution to this. I'll need to grab the source and/or fedora packages and see what needs to be done to package for SuSE.
Yes, that is the right solution (xmvn). But the problem is not actually maven itself but the dependency chain. Normal C programs have sane dependencies. "make" does not depend on much, and they usually depend always in a certain "direction" from upper layers to lower layers. to build software A that uses a pom.xml you need maven, and some maven-plugins maven requires maven to build the maven plugins need maven to build plus some software C software C requires maven, the plugins and software A. ... loop maven is silly. it is a project build tool, but it has the most basic functionality like "compiling" as a plugin, it depends on a IoC container (plexus) that has more dependencies (future maven versions now switched to guice without removing the plexus dependency). This basically means that in order to build some packages build with maven you will need hundred of packages built with maven in order to bootstrap everything from source. Fedora has most of them. We would need lot of contributors to maintain hundred of Java packages. I have personally tried various approaches. The most promising was to build the fedora packages themselves, bootstrapping everything using the fedora binary packages, but some dependencies would need to be solved at the lower levels (eg, we do already have some java packages, with different name and implementations). -- Duncan Mac-Vicar P. - http://www.suse.com/ SUSE LINUX Products GmbH, GF: Jeff Hawn, Jennifer Guild, Felix Imendörffer, HRB 16746 (AG Nürnberg) Maxfeldstraße 5, 90409 Nürnberg, Germany -- To unsubscribe, e-mail: opensuse-java+unsubscribe@opensuse.org To contact the owner, e-mail: opensuse-java+owner@opensuse.org
participants (3)
-
Archie Cobbs
-
Darin Perusich
-
Duncan Mac-Vicar P.