Hi David, thanks a lot - my issue anyway is NOT compiling the code, rather than managing the dependencies, the software has been provided by a 3rd party and is closed source, I just have the jars.
So, let's suppose I need the c.jar for mac-x86_64, when specifying that classifier I aim that a.jar and b.jar, that are transitive dependencies, are brought for the same platform... Any suggestion? TIA!!! -Simo http://people.apache.org/~simonetripodi/ http://simonetripodi.livejournal.com/ http://twitter.com/simonetripodi http://www.99soft.org/ On Fri, Sep 14, 2012 at 3:40 PM, David Hoffer <[email protected]> wrote: > There is also the native-maven-plugin. I'm not sure which is best/most > current as it's been years since I have used either one, but they both set > out to help manage builds with native code. > > -Dave > > On Fri, Sep 14, 2012 at 7:31 AM, Simone Tripodi > <[email protected]>wrote: > >> Hi Martin, >> >> very good news, thanks a lot, I am going to have a look at that plugin! >> >> All the best, >> -Simo >> >> http://people.apache.org/~simonetripodi/ >> http://simonetripodi.livejournal.com/ >> http://twitter.com/simonetripodi >> http://www.99soft.org/ >> >> >> On Fri, Sep 14, 2012 at 3:26 PM, Martin Eisengardt >> <[email protected]> wrote: >> > Ask google about maven-nar-plugin. >> > >> > It introduces nar dependencies (<type>nar</type>) and internally tries to >> > find out the correct qualifier depending on the current >> > machine/architecture. >> > >> > I am playing around with it because I have a similar situation. There is >> a >> > problem with the project because there are tens of orks on github. If you >> > have any questions about it please ask. I have contact to one of the >> ative >> > authors and we try to merge all the forks. >> > >> > On Fri, Sep 14, 2012 at 3:13 PM, Simone Tripodi < >> [email protected]>wrote: >> > >> >> Hi all guys, >> >> >> >> I have the task of managing a 3rd party forest of dependencies which >> >> contain JNI code, so let's immagine that the provided library >> >> directory tree is as shown below: >> >> >> >> linux-i386 >> >> ├── a.jar >> >> ├── b.jar (depends from a.jar) >> >> └── c.jar (depends from a.jar and b.jar) >> >> >> >> linux-x86_64 >> >> ├── a.jar >> >> ├── b.jar (depends from a.jar) >> >> └── c.jar (depends from a.jar and b.jar) >> >> >> >> mac-x86_64 >> >> ├── a.jar >> >> ├── b.jar (depends from a.jar) >> >> └── c.jar (depends from a.jar and b.jar) >> >> >> >> I was going to put all that jar in my Nexus installation, when I just >> >> realized I need classifiers to manage each platform... While manage a >> >> single dependency would be really easy, managing transitive >> >> dependencies per platform is not trivial, should be profiled... >> >> >> >> Do you have any suggestion on how that situation could be handled? >> >> >> >> Many thanks in advance, all the best! >> >> -Simo >> >> >> >> http://people.apache.org/~simonetripodi/ >> >> http://simonetripodi.livejournal.com/ >> >> http://twitter.com/simonetripodi >> >> http://www.99soft.org/ >> >> >> >> --------------------------------------------------------------------- >> >> To unsubscribe, e-mail: [email protected] >> >> For additional commands, e-mail: [email protected] >> >> >> >> >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
