Re: Is dependency:copy-dependencies config property broken?
Anders --
That did it. Thanks very much.
Solution summary:
- remove plugin from life-cycle,
- apply execution id "default-cli"
- contain plugin def by promoting it to build.pluginManagement element.
Working segment:
--
org.apache.maven.plugins
maven-dependency-plugin
default-cli
copy-dependencies
${basedir}/war/WEB-INF/lib/
false
false
true
gwt-user,gwt-dev
...
--
Cheers.
SF
On Mon, Oct 11, 2010 at 4:06 PM, Anders Hammar wrote:
> The problem is that the configuration you have is written within the
> execution. That execution is NOT for your CLI usage.
>
> You have two options:
> 1. You need to use the somewhat magic id of "default-cli":
> http://maven.apache.org/guides/mini/guide-default-execution-ids.html
> 2. Move the configuration stuff outside of execution.
>
> Btw, I strongly recommend that you put this plugin stuff within the
> pluginManagement section instead as it is not to be bound to the lifecycle.
>
> /Anders
>
> On Mon, Oct 11, 2010 at 22:01, Steve Francolla
> wrote:
>
> > I actually want to run it outside the lifecycle. I've removed the
>
> > binding and run it with the same usage. It runs but the output gets
> > written
> > to the default ${basedir}/target/dependency dir instead of the
> > outputDirectory I've overridden it with in the configuration. Seems
> > clearly
> > broken there, unless I'm missing something. Ideas?
> >
> > Thanks again.
> >
> >
> >
> >
> > On Mon, Oct 11, 2010 at 3:42 PM, Vincent Latombe
> > wrote:
> >
> > > Hi,
> > >
> > > Your execution is attached to the lifecycle. You'll get the expected
> > > behaviour if you type mvn package, not by calling directly the mojo
> from
> > > command line.
> > >
> > > 2010/10/11 Steve Francolla
> > >
> > > > Help! My dependencies only ever get written to the default
> > > > ${basedir}/target/dependency dir.
> > > >
> > > > Usage:
> > > > mvn dependency:copy-dependencies
> > > >
> > > > Pom.xml segment:
> > > > -
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >org.apache.maven.plugins
> > > >maven-dependency-plugin
> > > >
> > > >
> > > >copy-dependencies
> > > >package
> > > >
> > > > copy-dependencies
> > > >
> > > >
> > > >
> > > > ${basedir}/war/WEB-INF/lib/
> > > > false
> > > > false
> > > > true
> > > >
> > > gwt-user,gwt-dev
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > >
> > > > -
> > > >
> > > >
> > > > Thanks.
> > > >
> > > >
> > > > SF
> > > >
> > >
> > >
> > >
> > > --
> > > Vincent
> > >
> >
>
Re: Is dependency:copy-dependencies config property broken?
I actually want to run it outside the lifecycle. I've removed the
binding and run it with the same usage. It runs but the output gets written
to the default ${basedir}/target/dependency dir instead of the
outputDirectory I've overridden it with in the configuration. Seems clearly
broken there, unless I'm missing something. Ideas?
Thanks again.
On Mon, Oct 11, 2010 at 3:42 PM, Vincent Latombe
wrote:
> Hi,
>
> Your execution is attached to the lifecycle. You'll get the expected
> behaviour if you type mvn package, not by calling directly the mojo from
> command line.
>
> 2010/10/11 Steve Francolla
>
> > Help! My dependencies only ever get written to the default
> > ${basedir}/target/dependency dir.
> >
> > Usage:
> > mvn dependency:copy-dependencies
> >
> > Pom.xml segment:
> > -
> >
> >
> >
> >
> >
> >org.apache.maven.plugins
> >maven-dependency-plugin
> >
> >
> >copy-dependencies
> >package
> >
> > copy-dependencies
> >
> >
> >
> > ${basedir}/war/WEB-INF/lib/
> > false
> > false
> > true
> >
> gwt-user,gwt-dev
> >
> >
> >
> >
> >
> >
> >
> >
> > -
> >
> >
> > Thanks.
> >
> >
> > SF
> >
>
>
>
> --
> Vincent
>
Is dependency:copy-dependencies config property broken?
Help! My dependencies only ever get written to the default
${basedir}/target/dependency dir.
Usage:
mvn dependency:copy-dependencies
Pom.xml segment:
-
org.apache.maven.plugins
maven-dependency-plugin
copy-dependencies
package
copy-dependencies
${basedir}/war/WEB-INF/lib/
false
false
true
gwt-user,gwt-dev
-
Thanks.
SF
Re: Mavenizing a project
My experience has consistently been that if I adapt my projects to Maven instead of vice-versa, life is just peachy. Have yet to come across a circumstance in Maven that hasn't already been solved for. Just go with it. On Fri, May 28, 2010 at 2:04 PM, Greg Akins wrote: > On Fri, May 28, 2010 at 1:43 PM, Steve Francolla > wrote: > > My advice is to fit your needs into Maven's standard directory layout > > (project structure). > > > http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html > > Your main source and junit source will fit well there. Unsure how your > > helper classes fit in but it seems to me that the case can probably be > made > > for that to be packaged within the test source branch as well. > > > > That seems like it might work better for my team. I think I'll have a > bit more of a fight if I have to create a separate project. And truth > is, I don't even think these tests get executed anymore. I just need > to keep them intact until I can replace them with something better. > > -- > Greg Akins > > http://insomnia-consulting.org > http://www.pghcodingdojo.org > http://pittjug.dev.java.net > http://twitter.com/akinsgre > http://www.linkedin.com/in/akinsgre >
Re: Mavenizing a project
My advice is to fit your needs into Maven's standard directory layout (project structure). http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html Your main source and junit source will fit well there. Unsure how your helper classes fit in but it seems to me that the case can probably be made for that to be packaged within the test source branch as well. SF On Fri, May 28, 2010 at 1:26 PM, Greg Akins wrote: > I'm working on Mavenizing a small project. In the current project, > there are three "source" directories. > > The Main source, the JUnit test source and a dir called > "test_informal" that contains some "helper" classes for doing > interactive testing... > > In a maven project, where would one put that type of source? > > -- > Greg Akins > > http://insomnia-consulting.org > http://www.pghcodingdojo.org > http://pittjug.dev.java.net > http://twitter.com/akinsgre > http://www.linkedin.com/in/akinsgre > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: I have the right version, but maven can't find it
Ohh, I'm sorry. Ugh. :-/ Below is the mmm pom that causes the install failure. This pom simulates exactly how a project I'm depending on is erroneously defined. To get around it, I've implemented the fix as in nnn.xml. Just providing a concluding example here for anybody with the same issue in the future. - start mmm.xml http://maven.apache.org/POM/4.0.0"; xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> 4.0.0 testGroup mmm jar 1.0-SNAPSHOT mmm http://maven.apache.org log4j log4j [1.2.13] compile - end mmm.xml --- On Sun, May 16, 2010 at 5:44 PM, Ron Wheeler wrote: > > Who is asking for 1.2.13 now? I only see 1.2.15 in your poms? > > I am not sure why you have the "[]" around the version in mmm's pom.xml > > > Ron > > > On 16/05/2010 5:03 PM, Steve Francolla wrote: > >> I just needed to resolve this issue myself with log4j [1.2.13]. Working >> example is below. Thank yous go out to the gentlemen pointing me to >> depMgmt. >> >> >> Case: >> - Artifact mmm depends on log4j with version "[1.2.13]" >> - Artifact nnn depends on mmm. >> - Mvn clean install of nnn fails with "Couldn't find a version in [1.2.15, >> 1.2.16] to match range [1.2.13,1.2.13]" message. >> - Added dependencyManagement section to nnn pom.xml to include dependency >> on >> mmm with scope value "import" and dependency on log4j with version value >> "1.2.15" to override the inherited log4j dependency's version and >> successfully build artifact nnn. >> >> >> Functional pom files: >> >> - start mmm pom.xml: >> >> http://maven.apache.org/POM/4.0.0"; xmlns:xsi=" >> http://www.w3.org/2001/XMLSchema-instance"; >> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 >> http://maven.apache.org/maven-v4_0_0.xsd";> >> 4.0.0 >> >> testGroup >> mmm >> jar >> 1.0-SNAPSHOT >> mmm >> http://maven.apache.org >> >> >> >> log4j >> log4j >> [1.2.15] >> compile >> >> >> >> - end mmm pom.xml: >> >> >> - start nnn pom.xml: >> >> http://maven.apache.org/POM/4.0.0"; xmlns:xsi=" >> http://www.w3.org/2001/XMLSchema-instance"; >> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 >> http://maven.apache.org/maven-v4_0_0.xsd";> >> 4.0.0 >> >> testGroup >> nnn >> jar >> 1.0-SNAPSHOT >> nnn >> http://maven.apache.org >> >> >> >> >> testGroup >> mmm >> 1.0-SNAPSHOT >> jar >> import >> >> >> log4j >> log4j >> 1.2.15 >> >> >> >> >> >> >> testGroup >> mmm >> compile >> >> >> >> >> - end nnn pom.xml: >> >> >> >> SF >> >> >> >> >> On Wed, Apr 28, 2010 at 3:55 AM, Jörg Schaible> >wrote: >> >> >> >>> Hi Grant, >>> >>> Grant Birchmeier wrote: >>> >>> >>> >>>> If anyone can help, I'd appreciate it. This is driving me up the >>>> wall. I tried googling, but I couldn't find what I needed. >>>> >>>> When I build, I get this error: >>>> >>>> --- >>>> Couldn't find a version in [1.2.15, 1.2.16] to match range >>>> >>>> >>> [1.2.13,1.2.13] >>> >>> >>>> log4j:log4j:jar:null >>>> --- >>>> >>>> >>> [snip] >>> >>> >>> >>>> So if I have 1.2.13 in my repo, then why is maven only finding 1.2.14 >>>> and 1.2.15? >>>> >>>> >>> Actually you (in your project) or some of your dependencies declare >>> version >>> ranges for log4j and one requires log4j to be used exactly in version >>> 1.2.13 >>> while another say it must have log4j 1.2.15 or 1.2.16. This requirements >>> can >>> obviously not be fulfilled. As Anders already recommended, use a depMgmt >>> section to override the version with the one you like to use, but you >>> should >>> probably ask the developers of the artifacts in question why they think >>> they >>> need exactly those versions. Find the artifacts with dependency:tree. >>> >>> - Jörg >>> >>> >>> >>> - >>> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >>> For additional commands, e-mail: users-h...@maven.apache.org >>> >>> >>> >>> >> >> > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: I have the right version, but maven can't find it
I just needed to resolve this issue myself with log4j [1.2.13]. Working example is below. Thank yous go out to the gentlemen pointing me to depMgmt. Case: - Artifact mmm depends on log4j with version "[1.2.13]" - Artifact nnn depends on mmm. - Mvn clean install of nnn fails with "Couldn't find a version in [1.2.15, 1.2.16] to match range [1.2.13,1.2.13]" message. - Added dependencyManagement section to nnn pom.xml to include dependency on mmm with scope value "import" and dependency on log4j with version value "1.2.15" to override the inherited log4j dependency's version and successfully build artifact nnn. Functional pom files: - start mmm pom.xml: http://maven.apache.org/POM/4.0.0"; xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> 4.0.0 testGroup mmm jar 1.0-SNAPSHOT mmm http://maven.apache.org log4j log4j [1.2.15] compile - end mmm pom.xml: - start nnn pom.xml: http://maven.apache.org/POM/4.0.0"; xmlns:xsi=" http://www.w3.org/2001/XMLSchema-instance"; xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd";> 4.0.0 testGroup nnn jar 1.0-SNAPSHOT nnn http://maven.apache.org testGroup mmm 1.0-SNAPSHOT jar import log4j log4j 1.2.15 testGroup mmm compile - end nnn pom.xml: SF On Wed, Apr 28, 2010 at 3:55 AM, Jörg Schaible wrote: > Hi Grant, > > Grant Birchmeier wrote: > > > If anyone can help, I'd appreciate it. This is driving me up the > > wall. I tried googling, but I couldn't find what I needed. > > > > When I build, I get this error: > > > > --- > > Couldn't find a version in [1.2.15, 1.2.16] to match range > [1.2.13,1.2.13] > > log4j:log4j:jar:null > > --- > > [snip] > > > So if I have 1.2.13 in my repo, then why is maven only finding 1.2.14 > > and 1.2.15? > > Actually you (in your project) or some of your dependencies declare version > ranges for log4j and one requires log4j to be used exactly in version > 1.2.13 > while another say it must have log4j 1.2.15 or 1.2.16. This requirements > can > obviously not be fulfilled. As Anders already recommended, use a depMgmt > section to override the version with the one you like to use, but you > should > probably ask the developers of the artifacts in question why they think > they > need exactly those versions. Find the artifacts with dependency:tree. > > - Jörg > > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: Beginner question: I can't find the library i'm using on the repository
Yes, it includes the classes of the 3rd party lib directly extracted within your classpath. In my opinion... a project exists in two forms, source and package. The package can be referenced as a dependency in other projects. The source is the manager of what gets built into the package. So, as long as my project source maintains its relationship to the 3rd party library by way of pom dependency to it as installed to my local system repository, it continues to be very easily upgradable/maintainable. Employing the mvn-shade plugin with mvn-release plugin lets me then include the 3rd party lib cohesively within my package, directly within the same classpath, so that no dependency resolution issues arise on any users' ends. In sum, the combination of the acknowledgement of source and package being different things plus mvn-shade lets me provide a functional library of my own by being agnostic to how it becomes that way. ...but I'm only 1.5 weeks into my Maven love affair. :) Look up the mvn-shade plugin website. It's an apache project. SF 2010/3/30 Benoît Thiébault > I'm at chapter 11, I guess I read this part too quickly. > Very good book by the way > > Regarding mvn-shade, I'm not really sure I understood what it does: does it > include the classes of this third party library within my software package ? > Seems good to me (even though I have no idea if this is a recommended best > practice) > > Regards > Ben > > Le 30 mars 2010 à 17:44, nicolas de loof a écrit : > > > you should read chapter 6, it explains the issue you get here :) > > > > The short term solution is to write a custom pom and use mvn > > install:install-file > > > > If you plan to share the project with other in your company, or on the > Net, > > you will have to document this step and loose some advantages of Maven. > > Working inside a company, the simpliest solution is to install Nexus (or > any > > other repository manager) and deploy your custom artifacts. For public > > distribution, you will need to make the dependency publicly available. > > > > For legacy artifact this is really an issue. Creating yet another public > > repo with some artifacts that may conflict with central and adding > > in your POM is not a good option (read > > > http://www.sonatype.com/people/2010/03/why-external-repos-are-being-phased-out-of-central/ > ). > > The best way IMHO would be to propose the artifact for upload in central. > > > > Cheers, > > Nicolas > > > > 2010/3/30 Wendy Smoak > > > >> 2010/3/30 Benoît Thiébault : > >>> My software depends on an open source software, jlibeps ( > >> http://jlibeps.sourceforge.net/), but I can't find it in any Maven > >> repository. This library seems not very maintained anymore, but it does > what > >> I need it to do. I don't want (yet) to host my own Maven repository and > I > >> was wondering what are my options here ? Should I create a POM file for > the > >> library and submit it to a Maven repository ? It seems ( > >> > http://maven.apache.org/guides/mini/guide-central-repository-upload.html) > >> the simplest way to do it would be to host is on an approved forge, but > I > >> don't own the project (that looks dead to me)... > >> > >> Eventually, you'll need to get it into some remote repository. > >> > >> For the moment, you can install it into your local repo with "mvn > >> install:install-file -Dfile=... -DgeneratePom=true ..." . (See the > >> maven install plugin docs for the missing bits.) > >> > >> Unfortunately that means everyone who wants to build your project will > >> also need to do that, but as a temporary fix it will get you past the > >> missing dependency errors. > >> > >> -- > >> Wendy > >> > >> - > >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > >> For additional commands, e-mail: users-h...@maven.apache.org > >> > >> > > > Benoît Thiébault > > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: Beginner question: I can't find the library i'm using on the repository
Forgot to mention that mvn-shade will also produce an updated-dependency-pom.xml (or similarly named) where white-listed lib's dependency on your local repo will be removed from the packaged pom.xml. I use mvn-shade with mvn release plugin to deploy to Nexus OSS repo with those adjustments. On Tue, Mar 30, 2010 at 11:48 AM, Steve Francolla wrote: > You can install the lib to your local system repo and then completely avoid > others having the anticipated dependency build problem by applying the > mvn-shade-plugin: > > (1) mvn install the lib to my local system repo. > > mvn install:install-file -Dfile=lib\.jar -DgroupId= > -DartifactId= -Dversion= -Dpackaging=jar > > > (2) then, simply package this dependency within my proj's package with > something like: > > > ... > > > > org.apache.maven.plugins > maven-shade-plugin > 1.3.2 > > > package > > shade > > > > > > [the-lib-group]:[the-lib-artifact]:* > > > > > ... > > > Those who pull down your project will receive the depended upon library's > classes built directly into the project tree. > > SF > > > > On Tue, Mar 30, 2010 at 11:29 AM, Jeff MAURY wrote: > >> If it does not exist on the cloud, don't try to put it there, there are >> probably many reasons for that. >> I would recommand that you install a Maven repository manager like Nexus >> and >> once you've set it up, then deploy on it the missing jar and all your >> internal Maven projects will see it now !!! >> >> Regards >> Jeff MAURY >> >> 2010/3/30 Benoît Thiébault >> >> > Hello everyone, >> > >> > I am currently reading the very good Maven book from Nicolas De loof and >> > Arnaud Héritier (written in French) and I have decided to convert one of >> my >> > test projects to Maven. Unfortunately, I already have a problem :-). >> > >> > My software depends on an open source software, jlibeps ( >> > http://jlibeps.sourceforge.net/), but I can't find it in any Maven >> > repository. This library seems not very maintained anymore, but it does >> what >> > I need it to do. I don't want (yet) to host my own Maven repository and >> I >> > was wondering what are my options here ? Should I create a POM file for >> the >> > library and submit it to a Maven repository ? It seems ( >> > >> http://maven.apache.org/guides/mini/guide-central-repository-upload.html) >> > the simplest way to do it would be to host is on an approved forge, but >> I >> > don't own the project (that looks dead to me)... >> > >> > Thanks for your feedbacks >> > >> > Ben >> > - >> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> > For additional commands, e-mail: users-h...@maven.apache.org >> > >> > >> >> >> -- >> http://www.jeffmaury.com >> http://riadiscuss.jeffmaury.com >> http://www.lastfm.fr/listen/user/jeffmaury/personal >> > > > > > > On Tue, Mar 30, 2010 at 11:29 AM, Jeff MAURY wrote: > >> If it does not exist on the cloud, don't try to put it there, there are >> probably many reasons for that. >> I would recommand that you install a Maven repository manager like Nexus >> and >> once you've set it up, then deploy on it the missing jar and all your >> internal Maven projects will see it now !!! >> >> Regards >> Jeff MAURY >> >> 2010/3/30 Benoît Thiébault >> >> > Hello everyone, >> > >> > I am currently reading the very good Maven book from Nicolas De loof and >> > Arnaud Héritier (written in French) and I have decided to convert one of >> my >> > test projects to Maven. Unfortunately, I already have a problem :-). >> > >> > My software depends on an open source software, jlibeps ( >> > http://jlibeps.sourceforge.net/), but I can't find it in any Maven >> > repository. This library seems not very maintained anymore, but it does >> what >> > I need it to do. I don't want (yet) to host my own Maven repository and >> I >> > was wondering what are my options here ? Should I create a POM file for >> the >> > library and submit it to a Maven repository ? It seems ( >> > >> http://maven.apache.org/guides/mini/guide-central-repository-upload.html) >> > the simplest way to do it would be to host is on an approved forge, but >> I >> > don't own the project (that looks dead to me)... >> > >> > Thanks for your feedbacks >> > >> > Ben >> > - >> > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> > For additional commands, e-mail: users-h...@maven.apache.org >> > >> > >> >> >> -- >> http://www.jeffmaury.com >> http://riadiscuss.jeffmaury.com >> http://www.lastfm.fr/listen/user/jeffmaury/personal >> > >
Re: Beginner question: I can't find the library i'm using on the repository
You can install the lib to your local system repo and then completely avoid others having the anticipated dependency build problem by applying the mvn-shade-plugin: (1) mvn install the lib to my local system repo. mvn install:install-file -Dfile=lib\.jar -DgroupId= -DartifactId= -Dversion= -Dpackaging=jar (2) then, simply package this dependency within my proj's package with something like: ... org.apache.maven.plugins maven-shade-plugin 1.3.2 package shade [the-lib-group]:[the-lib-artifact]:* ... Those who pull down your project will receive the depended upon library's classes built directly into the project tree. SF On Tue, Mar 30, 2010 at 11:29 AM, Jeff MAURY wrote: > If it does not exist on the cloud, don't try to put it there, there are > probably many reasons for that. > I would recommand that you install a Maven repository manager like Nexus > and > once you've set it up, then deploy on it the missing jar and all your > internal Maven projects will see it now !!! > > Regards > Jeff MAURY > > 2010/3/30 Benoît Thiébault > > > Hello everyone, > > > > I am currently reading the very good Maven book from Nicolas De loof and > > Arnaud Héritier (written in French) and I have decided to convert one of > my > > test projects to Maven. Unfortunately, I already have a problem :-). > > > > My software depends on an open source software, jlibeps ( > > http://jlibeps.sourceforge.net/), but I can't find it in any Maven > > repository. This library seems not very maintained anymore, but it does > what > > I need it to do. I don't want (yet) to host my own Maven repository and I > > was wondering what are my options here ? Should I create a POM file for > the > > library and submit it to a Maven repository ? It seems ( > > http://maven.apache.org/guides/mini/guide-central-repository-upload.html > ) > > the simplest way to do it would be to host is on an approved forge, but I > > don't own the project (that looks dead to me)... > > > > Thanks for your feedbacks > > > > Ben > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > > > -- > http://www.jeffmaury.com > http://riadiscuss.jeffmaury.com > http://www.lastfm.fr/listen/user/jeffmaury/personal > On Tue, Mar 30, 2010 at 11:29 AM, Jeff MAURY wrote: > If it does not exist on the cloud, don't try to put it there, there are > probably many reasons for that. > I would recommand that you install a Maven repository manager like Nexus > and > once you've set it up, then deploy on it the missing jar and all your > internal Maven projects will see it now !!! > > Regards > Jeff MAURY > > 2010/3/30 Benoît Thiébault > > > Hello everyone, > > > > I am currently reading the very good Maven book from Nicolas De loof and > > Arnaud Héritier (written in French) and I have decided to convert one of > my > > test projects to Maven. Unfortunately, I already have a problem :-). > > > > My software depends on an open source software, jlibeps ( > > http://jlibeps.sourceforge.net/), but I can't find it in any Maven > > repository. This library seems not very maintained anymore, but it does > what > > I need it to do. I don't want (yet) to host my own Maven repository and I > > was wondering what are my options here ? Should I create a POM file for > the > > library and submit it to a Maven repository ? It seems ( > > http://maven.apache.org/guides/mini/guide-central-repository-upload.html > ) > > the simplest way to do it would be to host is on an approved forge, but I > > don't own the project (that looks dead to me)... > > > > Thanks for your feedbacks > > > > Ben > > - > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > > > -- > http://www.jeffmaury.com > http://riadiscuss.jeffmaury.com > http://www.lastfm.fr/listen/user/jeffmaury/personal >
How to manipulate pom produced for release before deployment to Nexus?
Hi. I've automated my deployment to Nexus OSS repo with maven-release-plugin. My project has open source dependencies that do not source from Central. So, since Nexus requires projects to be self-contained, I'm also using maven-shade-plugin to include those dependencies in the jar and strip their tags from the release's pom.xml. However, the block still exists in it, this makes the package not self-contained, and therefore it fails to release on Nexus. To solve the problem, I need a way to strip the branch of xml from the release pom.xml. Is there a plug-in out there that would help me do this? Do I need to write something custom? Thanks. Steven
