Re: [java-gnome-hackers] [Java-gnome-developer] (Hacked) version of 4.0.13 in Maven repo

[Jacek F. <ja...@gm...>]

Andrew, I was thinking that the easiest solution to this would be to allow
overriding the default .so prefix (i.e. "libgtkjni-") with a different one
via a command line property, e.g.

-DgnomePrefix=java-gnome-lib

or something along those lines. That way we could override the default
"libgtkjni" during development (in Maven or whatever else) and let it
fallback to the regular standard way
when the app is deployed on a distro.

I still like the approach of the .so embedded directly in the JAR, but if
you're strongly opposed to it I won't push it any further.

Cheers,
Jacek

On Wed, Nov 18, 2009 at 6:55 PM, Jacek Furmankiewicz <ja...@gm...>wrote:

> I understand your point of view, but Maven and Ant (regardless of how you
> feel about them) are very typical
> setups for any regular Java developer...the type of folks we would like to
> see more exposed to Java-GNOME
> and interested in using it for developing apps.
>
> I think we should maybe differentiate though between development time usage
> (Maven in my case) and deployment on distros (native packaging system).
> It would be great to use Maven for developing JG apps (the whole setup
> makes it so easy)...actually getting them deployed is a
> different issue altogether and could alleviate a lot of your security
> concerns.
>
> I will continue this on the hackers list, as per your suggestion.
>
> Cheers,
> Jacek
>
>
>
>
>