Re: dependency on system library (java.library.path)

2007-04-17 Thread Joerg Hohwiller
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, > On 4/12/07, Aaron Digulla <[EMAIL PROTECTED]> wrote: >> >> Joerg Hohwiller wrote: >> > Hi there, >> > >> > I have already used SWT and GWT together with maven. Both need native >> system >> > libraries at some specific point. This causes tr

Re: dependency on system library (java.library.path)

2007-04-17 Thread Joerg Hohwiller
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Marc, > We can change the license to something else, no problem. Of course this is your decision. But you could think about dual licensing your project. Here is something to consider: http://wiki.apache.org/jakarta/Using_LGPL'd_code > > Regards > M

Re: dependency on system library (java.library.path)

2007-04-15 Thread Eric Redmond
On 4/12/07, Aaron Digulla <[EMAIL PROTECTED]> wrote: Joerg Hohwiller wrote: > Hi there, > > I have already used SWT and GWT together with maven. Both need native system > libraries at some specific point. This causes trouble when running code (e.g. > test-cases) with maven. The latest 3.3 relea

Re: dependency on system library (java.library.path)

2007-04-12 Thread Aaron Digulla
Joerg Hohwiller wrote: > Hi there, > > I have already used SWT and GWT together with maven. Both need native system > libraries at some specific point. This causes trouble when running code (e.g. > test-cases) with maven. The latest 3.3 release of SWT includes the library files in the JAR! I have

Re: dependency on system library (java.library.path)

2007-04-10 Thread Mark Donszelmann
Hi Joerg, our test nar goal (which we call integration test nar, since it checks tests against the jar and the native libs, will put any native libs on the java.library.parth which are (transitive) dependencies. For libs that are dependencies but that we do not build, we just wrap them in a nar

Re: dependency on system library (java.library.path)

2007-04-10 Thread Damien Lecan
Hello, For system libraries however the name cares when it is loaded from something that I can not control (foo-1.0.jar loads foo.dll and it can not be named foo-1.0.dll). Is there a way to put various artifacts with different versions but the same file-name into a maven repository? In other wor

Re: dependency on system library (java.library.path)

2007-04-09 Thread Joerg Hohwiller
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 > Hi Hello Mark, > > the freehep-nar-plugin does exactly what you describe. > > http://java.freehep.org/freehep-nar-plugin Thanks for the hint. This sounds promising. Anyways I am not creating system libraries, I just want to use them in my project.

Re: dependency on system library (java.library.path)

2007-04-07 Thread Mark Donszelmann
We can change the license to something else, no problem. Regards Mark On Apr 7, 2007, at 12:37 AM, Jason Dillon wrote: Ah, I remember reading about this before, though it was a while ago. Too bad this is LGPL, as that is going to prevent a lot of folks from using it :-( --jason On Apr 6

Re: dependency on system library (java.library.path)

2007-04-07 Thread Jason Dillon
Ah, I remember reading about this before, though it was a while ago. Too bad this is LGPL, as that is going to prevent a lot of folks from using it :-( --jason On Apr 6, 2007, at 7:21 PM, Mark Donszelmann wrote: Hi the freehep-nar-plugin does exactly what you describe. http://java.freeh

RE: dependency on system library (java.library.path)

2007-04-06 Thread Brian E. Fox
Nice powerpoint on that site. In less than 3 mins, I already know a ton about the plugin and how it works. -Original Message- From: Mark Donszelmann [mailto:[EMAIL PROTECTED] Sent: Friday, April 06, 2007 10:22 PM To: Maven Developers List Subject: Re: dependency on system library

Re: dependency on system library (java.library.path)

2007-04-06 Thread Mark Donszelmann
Hi the freehep-nar-plugin does exactly what you describe. http://java.freehep.org/freehep-nar-plugin Regards Mark Donszelmann On Apr 6, 2007, at 5:33 PM, [EMAIL PROTECTED] wrote: Its probably better to zip the natives up and then use the zip file as the artifact, and then hook up support to

Re: dependency on system library (java.library.path)

2007-04-06 Thread jason . dillon
Its probably better to zip the natives up and then use the zip file as the artifact, and then hook up support to extract them to some tmp dir for inclusion in the library path. Would also be nice to have a standard artifact type/ext to use for all share library types. And perhaps allow multi

Re: dependency on system library (java.library.path)

2007-04-06 Thread Joerg Hohwiller
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi Eric, > It should be a type, I agree. But if you are trying to keep moving, I just > drop the dll in the repo directory with the GWT jar. Thanks for the hint. This works for the GWT but NOT for a raw SWT project. > > Eric Regards Jörg > > On 4/

Re: dependency on system library (java.library.path)

2007-04-06 Thread Eric Redmond
It should be a type, I agree. But if you are trying to keep moving, I just drop the dll in the repo directory with the GWT jar. Eric On 4/6/07, Joerg Hohwiller <[EMAIL PROTECTED]> wrote: -BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Hi there, I have already used SWT and GWT together with mav