RE: Use third-party jar with natives in Maven
Hello Stephen, thank you for the link. Unfortunately I was not able to find it myself. Regards, Jens From: Stephen Connolly [stephen.alan.conno...@gmail.com] Sent: Tuesday, October 14, 2014 11:17 AM To: Maven Users List Subject: Re: Use third-party jar with natives in Maven http://developer-blog.cloudbees.com/2013/03/playing-trade-offs-with-maven.html On 14 October 2014 10:01, Rabe, Jens wrote: > Hello, > > I have a third-party Java library which is a binary-only jar (not > open-source) and has separate native libraries. Is there a way to wrap this > up and use it with Maven? Can anyone point out how it is done, if possible? > > Thanks in advance, > Jens > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Use third-party jar with natives in Maven
http://developer-blog.cloudbees.com/2013/03/playing-trade-offs-with-maven.html On 14 October 2014 10:01, Rabe, Jens wrote: > Hello, > > I have a third-party Java library which is a binary-only jar (not > open-source) and has separate native libraries. Is there a way to wrap this > up and use it with Maven? Can anyone point out how it is done, if possible? > > Thanks in advance, > Jens >
Use third-party jar with natives in Maven
Hello, I have a third-party Java library which is a binary-only jar (not open-source) and has separate native libraries. Is there a way to wrap this up and use it with Maven? Can anyone point out how it is done, if possible? Thanks in advance, Jens
Re: Third Party Jar
I see. However, i don't think the codehaus plugin is close enough nor would be usefull to update it with my needs. This is a very specific plugin and should not be used as a general purpose XSL translator. Anyways, in case you ever get the time to take a look: 1. the plugin's pom.xml: http://testng-xslt.googlecode.com/svn/trunk/pom.xml 2. the actual report Mojo: http://testng-xslt.googlecode.com/svn/trunk/src/main/java/org/testng/xslt/mavenplugin/TestNgXsltMojo.java (You can ignore the boiler plate. The problem is around the commented lines above the TODO - the project that is used to test the plugin fails with " javax.xml.transform.TransformerFactoryConfigurationError: Provider net.sf.saxon.TransformerFactoryImpl not found" when uncommenting them) 3. the pom.xml of the project that I use to test the plugin: http://testng-xslt.googlecode.com/svn/trunk/test/maven/pom.xml There are workarounds that I could implement. However, i need to know if I am missing something as this seems to be a classloader issue, as far as I can tell. I also tried to manually set the classloader on the current thread with the one of net.sf.saxon.TransformerFactoryImpl and curiously it worked, so my guess is that the search is performed in the plugin's classloader and not in the top-level classloader. Thanks anyways, Cosmin On Tue, Apr 1, 2008 at 6:25 PM, Wayne Fay <[EMAIL PROTECTED]> wrote: > I have no clue without going into the code and looking at it, and I'm > not doing that today. > > If you decide the codehaus plugin is close enough, feel free to modify > it and submit your modifications for future incorporation into the > plugin. Then everyone benefits from your changes. > > Wayne > > On 4/1/08, Cosmin Marginean <[EMAIL PROTECTED]> wrote: > > Hi, > > > > Thanks for the suggestion. I have tried this and it seems to lack some > > features that I really need in my plugin. So appearently I will need to > > write my own plugin. However, I analyzed some of the code in this plugin > and > > it doesn't seem to do a lot more different stuff that I am doing, since > the > > standard transformation API is used. The only difference seems to be > that > > the xml-maven-plugin is run at build time, while mine is run at report > time > > (in the section). Could this be a cause why the transformer > is > > not loaded? > > > > Thanks > > > > On Fri, Mar 28, 2008 at 5:29 PM, Wayne Fay <[EMAIL PROTECTED]> wrote: > > > > > There is already an XML plugin in Codehaus which has XSLT > > > functionality. Why don't you just take a look at it before moving too > > > far down this path of possibly re-implementing an existing solution? > > > > > > http://mojo.codehaus.org/xml-maven-plugin/ > > > > > > Wayne > > > > > > On 3/28/08, Cosmin Marginean <[EMAIL PROTECTED]> wrote: > > > > It seems that this goes deeper. What I actually need to do is create > a > > > Maven > > > > plugin that performs an XSL transformation using Saxon 9. I unpacked > the > > > > Saxon 9 jar and added the classes to my plugin jar to make sure the > > > > transformer is loaded. However, it seems that the transformer won't > get > > > > loaded, even when I run Maven with > > > >- > > > > > > > > Djava.xml.transform.TransformerFactory=net.sf.saxon.TransformerFactoryImpl > > > > Some people seem to have worked around this by specifying the Saxon > > > > dependency in the client pom.xml but this doesn't seem to work if I > make > > > the > > > > transformation call from the plugin Jar. I even set the property > > > manually in > > > > the plugin: > > > >TransformerFactory factory = TransformerFactory.newInstance(); > > > > But without any luck. The transformer will not be found > > > > > > > > Thanks in advance > > > > > > > > On Fri, Mar 28, 2008 at 9:04 AM, Cosmin Marginean < > [EMAIL PROTECTED]> > > > > wrote: > > > > > > > > > Hello guys, > > > > > > > > > > Sorry to bother you with such issues, but I've googling my brains > out > > > with > > > > > this without any relevant results. > > > > > I have a question regarding bundling a 3rd party jar in a Maven > > > Plugin. I > > > > > am a bit new to Maven and Maven plugins. > > > > > I tried bundling it in the plugin jar and adding it to the > Class-Path > > > > > attribute of MANIFEST.MF, but it seems to be ignored when using > the > > > > > plugin. > > > > > Another question would be: assuming that somehow this 3rd party > jar > > > will > > > > > make it into a public repository, what is the proper way to > configure > > > the > > > > > dependency to make sure that the client (plugin user) will > download > > > and load > > > > > this jar correctly without having to configure 3rd third party > > > dependency in > > > > > the pom.xml? > > > > > > > > > > Many thanks in advance > > > > > > > > > > -- > > > > > Cosmin Marginean > > > > > > > > > > > > > > > > > > > > -- > > > > Cosmin Marginean > > > > > > > > > > - > > > To unsubscribe, e-mail: [EMAIL
Re: Third Party Jar
I have no clue without going into the code and looking at it, and I'm not doing that today. If you decide the codehaus plugin is close enough, feel free to modify it and submit your modifications for future incorporation into the plugin. Then everyone benefits from your changes. Wayne On 4/1/08, Cosmin Marginean <[EMAIL PROTECTED]> wrote: > Hi, > > Thanks for the suggestion. I have tried this and it seems to lack some > features that I really need in my plugin. So appearently I will need to > write my own plugin. However, I analyzed some of the code in this plugin and > it doesn't seem to do a lot more different stuff that I am doing, since the > standard transformation API is used. The only difference seems to be that > the xml-maven-plugin is run at build time, while mine is run at report time > (in the section). Could this be a cause why the transformer is > not loaded? > > Thanks > > On Fri, Mar 28, 2008 at 5:29 PM, Wayne Fay <[EMAIL PROTECTED]> wrote: > > > There is already an XML plugin in Codehaus which has XSLT > > functionality. Why don't you just take a look at it before moving too > > far down this path of possibly re-implementing an existing solution? > > > > http://mojo.codehaus.org/xml-maven-plugin/ > > > > Wayne > > > > On 3/28/08, Cosmin Marginean <[EMAIL PROTECTED]> wrote: > > > It seems that this goes deeper. What I actually need to do is create a > > Maven > > > plugin that performs an XSL transformation using Saxon 9. I unpacked the > > > Saxon 9 jar and added the classes to my plugin jar to make sure the > > > transformer is loaded. However, it seems that the transformer won't get > > > loaded, even when I run Maven with > > >- > > > > > Djava.xml.transform.TransformerFactory=net.sf.saxon.TransformerFactoryImpl > > > Some people seem to have worked around this by specifying the Saxon > > > dependency in the client pom.xml but this doesn't seem to work if I make > > the > > > transformation call from the plugin Jar. I even set the property > > manually in > > > the plugin: > > >TransformerFactory factory = TransformerFactory.newInstance(); > > > But without any luck. The transformer will not be found > > > > > > Thanks in advance > > > > > > On Fri, Mar 28, 2008 at 9:04 AM, Cosmin Marginean <[EMAIL PROTECTED]> > > > wrote: > > > > > > > Hello guys, > > > > > > > > Sorry to bother you with such issues, but I've googling my brains out > > with > > > > this without any relevant results. > > > > I have a question regarding bundling a 3rd party jar in a Maven > > Plugin. I > > > > am a bit new to Maven and Maven plugins. > > > > I tried bundling it in the plugin jar and adding it to the Class-Path > > > > attribute of MANIFEST.MF, but it seems to be ignored when using the > > > > plugin. > > > > Another question would be: assuming that somehow this 3rd party jar > > will > > > > make it into a public repository, what is the proper way to configure > > the > > > > dependency to make sure that the client (plugin user) will download > > and load > > > > this jar correctly without having to configure 3rd third party > > dependency in > > > > the pom.xml? > > > > > > > > Many thanks in advance > > > > > > > > -- > > > > Cosmin Marginean > > > > > > > > > > > > > > > -- > > > Cosmin Marginean > > > > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Cosmin Marginean > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Third Party Jar
Hi, Thanks for the suggestion. I have tried this and it seems to lack some features that I really need in my plugin. So appearently I will need to write my own plugin. However, I analyzed some of the code in this plugin and it doesn't seem to do a lot more different stuff that I am doing, since the standard transformation API is used. The only difference seems to be that the xml-maven-plugin is run at build time, while mine is run at report time (in the section). Could this be a cause why the transformer is not loaded? Thanks On Fri, Mar 28, 2008 at 5:29 PM, Wayne Fay <[EMAIL PROTECTED]> wrote: > There is already an XML plugin in Codehaus which has XSLT > functionality. Why don't you just take a look at it before moving too > far down this path of possibly re-implementing an existing solution? > > http://mojo.codehaus.org/xml-maven-plugin/ > > Wayne > > On 3/28/08, Cosmin Marginean <[EMAIL PROTECTED]> wrote: > > It seems that this goes deeper. What I actually need to do is create a > Maven > > plugin that performs an XSL transformation using Saxon 9. I unpacked the > > Saxon 9 jar and added the classes to my plugin jar to make sure the > > transformer is loaded. However, it seems that the transformer won't get > > loaded, even when I run Maven with > >- > > > Djava.xml.transform.TransformerFactory=net.sf.saxon.TransformerFactoryImpl > > Some people seem to have worked around this by specifying the Saxon > > dependency in the client pom.xml but this doesn't seem to work if I make > the > > transformation call from the plugin Jar. I even set the property > manually in > > the plugin: > >TransformerFactory factory = TransformerFactory.newInstance(); > > But without any luck. The transformer will not be found > > > > Thanks in advance > > > > On Fri, Mar 28, 2008 at 9:04 AM, Cosmin Marginean <[EMAIL PROTECTED]> > > wrote: > > > > > Hello guys, > > > > > > Sorry to bother you with such issues, but I've googling my brains out > with > > > this without any relevant results. > > > I have a question regarding bundling a 3rd party jar in a Maven > Plugin. I > > > am a bit new to Maven and Maven plugins. > > > I tried bundling it in the plugin jar and adding it to the Class-Path > > > attribute of MANIFEST.MF, but it seems to be ignored when using the > > > plugin. > > > Another question would be: assuming that somehow this 3rd party jar > will > > > make it into a public repository, what is the proper way to configure > the > > > dependency to make sure that the client (plugin user) will download > and load > > > this jar correctly without having to configure 3rd third party > dependency in > > > the pom.xml? > > > > > > Many thanks in advance > > > > > > -- > > > Cosmin Marginean > > > > > > > > > > -- > > Cosmin Marginean > > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Cosmin Marginean
Re: Third Party Jar
There is already an XML plugin in Codehaus which has XSLT functionality. Why don't you just take a look at it before moving too far down this path of possibly re-implementing an existing solution? http://mojo.codehaus.org/xml-maven-plugin/ Wayne On 3/28/08, Cosmin Marginean <[EMAIL PROTECTED]> wrote: > It seems that this goes deeper. What I actually need to do is create a Maven > plugin that performs an XSL transformation using Saxon 9. I unpacked the > Saxon 9 jar and added the classes to my plugin jar to make sure the > transformer is loaded. However, it seems that the transformer won't get > loaded, even when I run Maven with >- > Djava.xml.transform.TransformerFactory=net.sf.saxon.TransformerFactoryImpl > Some people seem to have worked around this by specifying the Saxon > dependency in the client pom.xml but this doesn't seem to work if I make the > transformation call from the plugin Jar. I even set the property manually in > the plugin: >TransformerFactory factory = TransformerFactory.newInstance(); > But without any luck. The transformer will not be found > > Thanks in advance > > On Fri, Mar 28, 2008 at 9:04 AM, Cosmin Marginean <[EMAIL PROTECTED]> > wrote: > > > Hello guys, > > > > Sorry to bother you with such issues, but I've googling my brains out with > > this without any relevant results. > > I have a question regarding bundling a 3rd party jar in a Maven Plugin. I > > am a bit new to Maven and Maven plugins. > > I tried bundling it in the plugin jar and adding it to the Class-Path > > attribute of MANIFEST.MF, but it seems to be ignored when using the > > plugin. > > Another question would be: assuming that somehow this 3rd party jar will > > make it into a public repository, what is the proper way to configure the > > dependency to make sure that the client (plugin user) will download and load > > this jar correctly without having to configure 3rd third party dependency in > > the pom.xml? > > > > Many thanks in advance > > > > -- > > Cosmin Marginean > > > > > -- > Cosmin Marginean > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Third Party Jar
It seems that this goes deeper. What I actually need to do is create a Maven plugin that performs an XSL transformation using Saxon 9. I unpacked the Saxon 9 jar and added the classes to my plugin jar to make sure the transformer is loaded. However, it seems that the transformer won't get loaded, even when I run Maven with - Djava.xml.transform.TransformerFactory=net.sf.saxon.TransformerFactoryImpl Some people seem to have worked around this by specifying the Saxon dependency in the client pom.xml but this doesn't seem to work if I make the transformation call from the plugin Jar. I even set the property manually in the plugin: TransformerFactory factory = TransformerFactory.newInstance(); But without any luck. The transformer will not be found Thanks in advance On Fri, Mar 28, 2008 at 9:04 AM, Cosmin Marginean <[EMAIL PROTECTED]> wrote: > Hello guys, > > Sorry to bother you with such issues, but I've googling my brains out with > this without any relevant results. > I have a question regarding bundling a 3rd party jar in a Maven Plugin. I > am a bit new to Maven and Maven plugins. > I tried bundling it in the plugin jar and adding it to the Class-Path > attribute of MANIFEST.MF, but it seems to be ignored when using the > plugin. > Another question would be: assuming that somehow this 3rd party jar will > make it into a public repository, what is the proper way to configure the > dependency to make sure that the client (plugin user) will download and load > this jar correctly without having to configure 3rd third party dependency in > the pom.xml? > > Many thanks in advance > > -- > Cosmin Marginean -- Cosmin Marginean
Third Party Jar
Hello guys, Sorry to bother you with such issues, but I've googling my brains out with this without any relevant results. I have a question regarding bundling a 3rd party jar in a Maven Plugin. I am a bit new to Maven and Maven plugins. I tried bundling it in the plugin jar and adding it to the Class-Path attribute of MANIFEST.MF, but it seems to be ignored when using the plugin. Another question would be: assuming that somehow this 3rd party jar will make it into a public repository, what is the proper way to configure the dependency to make sure that the client (plugin user) will download and load this jar correctly without having to configure 3rd third party dependency in the pom.xml? Many thanks in advance -- Cosmin Marginean
Re: Third party jar deployment
http://jira.codehaus.org/browse/MNG-1551 On 11/14/05, Oscar Picasso <[EMAIL PROTECTED]> wrote: > I have read it. But it install it on the local repository. > > I want to deploy it on a remote repository so any other developer working on > the project could use this jar without manually install it in its local > repository. > > --- Alexandre Poitras <[EMAIL PROTECTED]> wrote: > > > You should take a look at this guide. Quite simple but does the job : > > http://maven.apache.org/guides/mini/guide-installing-3rd-party-jars.html > > > > On 11/11/05, Oscar Picasso <[EMAIL PROTECTED]> wrote: > > > > > > I solved this by extracting the third party into a target/classes folder. > > > > > > It works but there is surely somehing more elegant. > > > > > > --- Oscar Picasso <[EMAIL PROTECTED]> wrote: > > > > > > > Hi, > > > > > > > > How do I deploy a third party jar to a remote repostory. > > > > > > > > I have read that the best way is to user mvn deploy. But obviously > > > that's not > > > > enough. > > > > > > > > But where do I put the jar to be deployed? > > > > > > > > > > > > > > > > __ > > > > Do You Yahoo!? > > > > Tired of spam? Yahoo! Mail has the best spam protection around > > > > http://mail.yahoo.com > > > > > > > > - > > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > > > > > > > > > __ > > > Yahoo! Mail - PC Magazine Editors' Choice 2005 > > > http://mail.yahoo.com > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > -- > > Alexandre Poitras > > Québec, Canada > > > > > > > __ > Yahoo! FareChase: Search multiple travel sites in one click. > http://farechase.yahoo.com > > - > 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]
Re: Third party jar deployment
I have read it. But it install it on the local repository. I want to deploy it on a remote repository so any other developer working on the project could use this jar without manually install it in its local repository. --- Alexandre Poitras <[EMAIL PROTECTED]> wrote: > You should take a look at this guide. Quite simple but does the job : > http://maven.apache.org/guides/mini/guide-installing-3rd-party-jars.html > > On 11/11/05, Oscar Picasso <[EMAIL PROTECTED]> wrote: > > > > I solved this by extracting the third party into a target/classes folder. > > > > It works but there is surely somehing more elegant. > > > > --- Oscar Picasso <[EMAIL PROTECTED]> wrote: > > > > > Hi, > > > > > > How do I deploy a third party jar to a remote repostory. > > > > > > I have read that the best way is to user mvn deploy. But obviously > > that's not > > > enough. > > > > > > But where do I put the jar to be deployed? > > > > > > > > > > > > __ > > > Do You Yahoo!? > > > Tired of spam? Yahoo! Mail has the best spam protection around > > > http://mail.yahoo.com > > > > > > - > > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > > > > > > > > > __ > > Yahoo! Mail - PC Magazine Editors' Choice 2005 > > http://mail.yahoo.com > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > -- > Alexandre Poitras > Québec, Canada > __ Yahoo! FareChase: Search multiple travel sites in one click. http://farechase.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Third party jar deployment
You should take a look at this guide. Quite simple but does the job : http://maven.apache.org/guides/mini/guide-installing-3rd-party-jars.html On 11/11/05, Oscar Picasso <[EMAIL PROTECTED]> wrote: > > I solved this by extracting the third party into a target/classes folder. > > It works but there is surely somehing more elegant. > > --- Oscar Picasso <[EMAIL PROTECTED]> wrote: > > > Hi, > > > > How do I deploy a third party jar to a remote repostory. > > > > I have read that the best way is to user mvn deploy. But obviously > that's not > > enough. > > > > But where do I put the jar to be deployed? > > > > > > > > __ > > Do You Yahoo!? > > Tired of spam? Yahoo! Mail has the best spam protection around > > http://mail.yahoo.com > > > > - > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > > __ > Yahoo! Mail - PC Magazine Editors' Choice 2005 > http://mail.yahoo.com > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > -- Alexandre Poitras Québec, Canada
Re: Third party jar deployment
I solved this by extracting the third party into a target/classes folder. It works but there is surely somehing more elegant. --- Oscar Picasso <[EMAIL PROTECTED]> wrote: > Hi, > > How do I deploy a third party jar to a remote repostory. > > I have read that the best way is to user mvn deploy. But obviously that's not > enough. > > But where do I put the jar to be deployed? > > > > __ > Do You Yahoo!? > Tired of spam? Yahoo! Mail has the best spam protection around > http://mail.yahoo.com > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > __ Yahoo! Mail - PC Magazine Editors' Choice 2005 http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Third party jar deployment
Hi, How do I deploy a third party jar to a remote repostory. I have read that the best way is to user mvn deploy. But obviously that's not enough. But where do I put the jar to be deployed? __ Do You Yahoo!? Tired of spam? Yahoo! Mail has the best spam protection around http://mail.yahoo.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Third party JAR version naming conventions
If they call it 1.1.2_01 the version is 1.1.2_01 On 11/2/05, Richard Allen <[EMAIL PROTECTED]> wrote: > Thanks. I read the coping with sun jars guide, but I don't know what the > proper naming convention for versions is. I didn't think it was what Sun > is using, which is 1.1.2_01. For now I'm using 1.1.2.1. > > > Carlos Sanchez wrote: > > >http://maven.apache.org/guides/mini/guide-coping-with-sun-jars.html > > > >I'm preparing a naming conventions doc that will be available at > >http://maven.apache.org/guides/mini/guide-naming-conventions.html > > > >On 11/1/05, Richard Allen <[EMAIL PROTECTED]> wrote: > > > > > >>I'm new to Maven and I'm trying to convert an existing build process > >>that uses Ant to Maven 2. > >> > >>I've started creating a POM where I have to add third party SUN JARs as > >>dependencies, one of them being JAI. > >> > >>JAI version 1.1.2_01 includes three JARs. Is there a way to install JAI > >>into my repository such that I only have to reference JAI as a > >>dependency instead of referencing each JAR as a separate dependency? And > >>what is the version naming convention that I should use within the POM > >> tag for JAI? Should it read 1.1.2_01 ? > >> > >>Thanks, > >>Richard > >> > >>- > >>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] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Third party JAR version naming conventions
Thanks. I read the coping with sun jars guide, but I don't know what the proper naming convention for versions is. I didn't think it was what Sun is using, which is 1.1.2_01. For now I'm using 1.1.2.1. Carlos Sanchez wrote: http://maven.apache.org/guides/mini/guide-coping-with-sun-jars.html I'm preparing a naming conventions doc that will be available at http://maven.apache.org/guides/mini/guide-naming-conventions.html On 11/1/05, Richard Allen <[EMAIL PROTECTED]> wrote: I'm new to Maven and I'm trying to convert an existing build process that uses Ant to Maven 2. I've started creating a POM where I have to add third party SUN JARs as dependencies, one of them being JAI. JAI version 1.1.2_01 includes three JARs. Is there a way to install JAI into my repository such that I only have to reference JAI as a dependency instead of referencing each JAR as a separate dependency? And what is the version naming convention that I should use within the POM tag for JAI? Should it read 1.1.2_01 ? Thanks, Richard - 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]
Re: Third party JAR version naming conventions
http://maven.apache.org/guides/mini/guide-coping-with-sun-jars.html I'm preparing a naming conventions doc that will be available at http://maven.apache.org/guides/mini/guide-naming-conventions.html On 11/1/05, Richard Allen <[EMAIL PROTECTED]> wrote: > I'm new to Maven and I'm trying to convert an existing build process > that uses Ant to Maven 2. > > I've started creating a POM where I have to add third party SUN JARs as > dependencies, one of them being JAI. > > JAI version 1.1.2_01 includes three JARs. Is there a way to install JAI > into my repository such that I only have to reference JAI as a > dependency instead of referencing each JAR as a separate dependency? And > what is the version naming convention that I should use within the POM > tag for JAI? Should it read 1.1.2_01 ? > > Thanks, > Richard > > - > 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]
Third party JAR version naming conventions
I'm new to Maven and I'm trying to convert an existing build process that uses Ant to Maven 2. I've started creating a POM where I have to add third party SUN JARs as dependencies, one of them being JAI. JAI version 1.1.2_01 includes three JARs. Is there a way to install JAI into my repository such that I only have to reference JAI as a dependency instead of referencing each JAR as a separate dependency? And what is the version naming convention that I should use within the POM tag for JAI? Should it read 1.1.2_01 ? Thanks, Richard - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to deploy third party jar files to remote repository
Hi, I'm currently working in a project defining a new set of developer tools and procedures for java based development in a insurance company. They have used ANT up to now, but have decided to switch to maven. One of their few regrets are, that the procedure of uploading a new thirdparty jar file (such as the weblogic jar files, the ejb.jar, logging framework jar files e.t.c.) is a purely manual process. Have anyone devised a neat way of storing new thirdparty jar files, given the groupId, artifactId and version that the thirdparty jar file should be store as in the remote repository ? Btw, the remote repository in question is a companywide simple file share. br, /Sverre - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
