[1.2.3] dependency sources

[Duncan Mac-Vicar P. <dmacvicar@suse.de>]

Hi!

I was looking into packaging Play 1.2.3 into a rpm package, as I am
evaluating using Play for a product, and this means we need to be able
to distribute it as an rpm that has to be built 100% from sources
among it dependencies. This is typically something Java makes hard or
impossible :-(.

I have the package building against its dependencies in lib/, which
now I should start removing one by one, replacing them by symlinks to
jars coming from another rpm package (also built from source).

I was able to replace a few ones but then I found the jj-* jars (e.g.
jj-imaging.jar). Where do those jars come from?

Thanks in advance,

Duncan

[Duncan Mac-Vicar P. <dmacvicar@suse.de>]

On Nov 30, 4:52 pm, "Duncan Mac-Vicar P. <dmacvi...@suse.de>"

<dmacvi...@gmail.com> wrote:
> jj-imaging.jar). Where do those jars come from?

I found out that they are 3rd party software like jhlabs filters or
mylyn.wikitext repackaged and in a different namespace. What is the
reason the namespace is changed?

[Neoh59]

FYI I package my Play! apps with the "play war" command. And then package the war in a RPM ( using a Maven plugin and finally the war is deployed in a JBoss server ... but for this part you can build the RPM as you want).

Search "maven rpm " on this group to find my recent post about my experience. .

[Alex]

There is also a debian play module that can help in some cases: https://github.com/lunatech-labs/play-module-debian/wiki

[Alex]

sources of jar can be found on http://repo1.maven.org/maven2/com/google/code/maven-play-plugin/org/playframework/