Re: Could we delete old version jar in local repository by mvn ?
If I understand well, it is possible !
If you want to do it manually, go to your home directory's ".m2" hidden
folder, then remove whatever you want from the repository folder.
If you want to do it from a project pom, just use maven-clean-plugin on
${settings.localRepository}/org/.../myproject/3.0.1 in the build section
of the pom. You can also remove the root of "myproject" since your local
repository is just a workspace and the latest version will be installed by
the build after the clean phase.
If you want to do it from .m2/settings.xml you can also create a profile
doing this (not sure but I use a profile in my pom to do so, and you can
add profiles in settings.xml so I guess it is possible).
Best Regards,
Julien Plaquevent
Thales Critical Information Systems
2012/1/4 Jesse Farinacci
> Greetings,
>
> On Tue, Jan 3, 2012 at 11:02 PM, zuxiong lin >wrote:
>
> > Append
> > like:
> > repository\org\springframework\spring-core
> > -3.0.5.RELEASE
> > -3.0.6.RELEASE
> > -3.1.0.RELEASE
> >
> > I want to remove 3.0.5 and 3.0.6.
>
>
> I don't think this is possible with an existing plugin. I don't think it
> would even be advisable for non-SNAPSHOT artifacts..
>
> -Jesse
>
> --
> There are 10 types of people in this world, those
> that can read binary and those that can not.
>
Re: maven migration
Hi Anders, How are you doing... I created repository using nexus and upload the all artifacts.all dependency jars are downloading from repository but maven plugins are not. how to add the plugins to repository. -->added plugins to repository like clean,compiler ,resource and war plugin Unable to download this jar from repo. -->How to configure internal repository and maven central repositoyr.In maven central repository browser remote showing artifacts and browser stroage shows empty. Plz help me Thanks & Regards, Chandra -- View this message in context: http://maven.40175.n5.nabble.com/maven-migration-tp5091757p5118750.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Could we delete old version jar in local repository by mvn ?
Greetings, On Tue, Jan 3, 2012 at 11:02 PM, zuxiong lin wrote: > Append > like: > repository\org\springframework\spring-core > -3.0.5.RELEASE > -3.0.6.RELEASE > -3.1.0.RELEASE > > I want to remove 3.0.5 and 3.0.6. I don't think this is possible with an existing plugin. I don't think it would even be advisable for non-SNAPSHOT artifacts.. -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not.
Re: Could we delete old version jar in local repository by mvn ?
Append like: repository\org\springframework\spring-core -3.0.5.RELEASE -3.0.6.RELEASE -3.1.0.RELEASE I want to remove 3.0.5 and 3.0.6. 2012/1/4 zuxiong lin > Is it possible? > > > Thanks. >
Re: Could we delete old version jar in local repository by mvn ?
Greetings, On Tue, Jan 3, 2012 at 9:14 PM, zuxiong lin wrote: > Is it possible? > http://maven.apache.org/plugins/maven-dependency-plugin/purge-local-repository-mojo.html -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not.
Could we delete old version jar in local repository by mvn ?
Is it possible? Thanks.
Re: Unable to use maven-ant-tasks
I tried the latest binary ant release from ant.apache.org and my original build.xml test works perfectly (with just the xmlns). It appears that there's some problem with the Fedora 16 rpm release of ant that is causing the problem. I'll probably need to find a good testcase and report an issue against Fedora. Thanks, Scott On Jan 3, 2012, at 10:16 AM, Matt Walsh wrote: > I'm using maven-ant-tasks 2.1.3 with just the xmlns specification with no > problems. > I have it installed in ANT_HOME/lib, but initially used it from HOME/.ant/lib > with no problems. Haven't tried it with the -lib parameter, but no reason to > believe it wouldn't work that way as well. > > Maybe try upgrading to the 2.1.3 version, which is the latest released > version. > > Matt > >> -Original Message- >> From: Scott Shambarger [mailto:scott-ma...@shambarger.net] >> Sent: Monday, December 26, 2011 5:41 PM >> To: users@maven.apache.org >> Subject: Unable to use maven-ant-tasks >> >> I'm new to ant and maven, so I'm sure this is a silly >> questionstill, I'm stuck. >> >> I'm using the rpm install of ant/maven/etc for Fedora 16. I'm trying >> to build a project that requires ant and maven, and uses maven-ant- >> tasks >> (I have maven-ant-tasks-2.1.1-8.fc16 installed), however, I always >> receive the following error: >> >> BUILD FAILED >> /opt/devel/test/build.xml:4: Problem: failed to create task or type >> antlib:org.apache.maven.artifact.ant:remoteRepository >> Cause: The name is undefined. >> >> I'm pretty sure I have some sort of configuration error, but after >> several hours crawling the examples and docs, I'm just not making any >> progress... I don't have CLASSPATH defined, and have tried using ant >> -noclasspath with the same results. >> >> I've linked the /usr/share/java/maven-ant-tasks.jar (from the rpm) into >> my ~/.ant/lib directory, and reduced the build.xml file to the >> following >> (this file uses the same syntax as the project I'm trying to build, and >> produces the same error): >> >> --- build.xml >> >> >> > xmlns:artifact="antlib:org.apache.maven.artifact.ant"> >> > url="http://example.com";> >> >> >> >> >> >> >> end build.xml >> >> This appears to follow the example on >> http://maven.apache.org/ant-tasks/installation.html which has the >> following: >> >> >> ... >> >> >> The output of ant -diagnostics are: >> >> --- Ant diagnostics report --- >> Apache Ant(TM) version 1.8.2 compiled on July 6 2011 >> >> --- >> Implementation Version >> --- >> core tasks : 1.8.2 in file:/usr/share/java/ant.jar >> >> --- >> ANT PROPERTIES >> --- >> ant.version: Apache Ant(TM) version 1.8.2 compiled on July 6 2011 >> ant.java.version: 1.6 >> Is this the Apache Harmony VM? no >> Is this the Kaffe VM? no >> Is this gij/gcj? no >> ant.core.lib: /usr/share/java/ant.jar >> ant.home: /usr/share/ant >> >> --- >> ANT_HOME/lib jar listing >> --- >> ant.home: /usr/share/ant >> ant-junit.jar (102000 bytes) >> ant.jar (1935105 bytes) >> ant-bootstrap.jar (19759 bytes) >> ant-launcher.jar (12307 bytes) >> >> --- >> USER_HOME/.ant/lib jar listing >> --- >> user.home: /opt/devel >> maven-ant-tasks.jar (61063 bytes) >> >> --- >> Tasks availability >> --- >> p4reopen : Not Available (the implementation class is not present) >> ...(cut short for simplicity) >> ddcreator : Not Available (the implementation class is not present) >> A task being missing/unavailable should only matter if you are trying >> to use it >> >> --- >> org.apache.env.Which diagnostics >> --- >> Not available. >> Download it at http://xml.apache.org/commons/ >> >> --- >> XML Parser information >> --- >> XML Parser : org.apache.xerces.jaxp.SAXParserImpl >> XML Parser Location: file:/usr/share/java/xerces-j2-2.11.0.jar >> Namespace-aware parser : >> org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser >> Namespace-aware parser Location: >> file:/usr/share/java/xerces-j2-2.11.0.jar >> >> --- >> XSLT Processor information >> --- >> XSLT Processor : >> com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl >> XSLT Processor Location: unknown >> >> --- >> System properties >> --- >> java.runtime.name : OpenJDK Runtime Environment >> sun.boot.library.path : >> /usr/lib/jvm/jav
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
that is because you are using maven-release-plugin 2.2.1 switch to 2.2.2 and see how you feel - Stephen --- Sent from my Android phone, so random spelling mistakes, random nonsense words and other nonsense are a direct result of using swype to type on the screen On 3 Jan 2012 20:58, "Jesse Farinacci" wrote: > Greetings, > > On Tue, Jan 3, 2012 at 3:45 PM, Mark Derricutt wrote: > > > Surely something as egregious as allowing releases to break should block > > 3.0.4 from being released tho. As someone who uses GPG in that manner > for > > some of his releases I'd certainly want 3.0.4 to be able to release... > > > It didn't stop the 3.0.3 release, what's the difference with 3.0.4? It's > getting rather frustrating at seeing all these relatively solitary or > edge-case problems derail the entire release process. > > I have performed many releases with 3.0.3 and 3.0.4-rcX both, so this is > not a problem for me, and I dare say it's a very large majority of users > that it is also not a problem for. > > Stop stopping the presses, please!! It's just a stupid point release! It > doesn't have to solve every existing MNG-* out there! This kind of > localized Chicken Little behavior is making it harder and harder to get > small releases out the door. You're making it worse for all users. > > *sigh* > > (the same goes for all the bike shedding whiners about the dependency fetch > timeout - you know who you are) > > -Jesse > > -- > There are 10 types of people in this world, those > that can read binary and those that can not. >
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Not only properties like I explained it here : http://jira.codehaus.org/browse/MRELEASE-724 Arnaud On Tue, Jan 3, 2012 at 4:18 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > Hi, > > I just found a regression: > > http://jira.codehaus.org/browse/MNG-5224 > > I think it is serious enough to recommend users avoid using the above > combination if you rely on properties in a settings.xml profile to GPG > sign your releases. (i.e. anyone pushing to Central) > > -Stephen > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Greetings, On Tue, Jan 3, 2012 at 3:45 PM, Mark Derricutt wrote: > Surely something as egregious as allowing releases to break should block > 3.0.4 from being released tho. As someone who uses GPG in that manner for > some of his releases I'd certainly want 3.0.4 to be able to release... It didn't stop the 3.0.3 release, what's the difference with 3.0.4? It's getting rather frustrating at seeing all these relatively solitary or edge-case problems derail the entire release process. I have performed many releases with 3.0.3 and 3.0.4-rcX both, so this is not a problem for me, and I dare say it's a very large majority of users that it is also not a problem for. Stop stopping the presses, please!! It's just a stupid point release! It doesn't have to solve every existing MNG-* out there! This kind of localized Chicken Little behavior is making it harder and harder to get small releases out the door. You're making it worse for all users. *sigh* (the same goes for all the bike shedding whiners about the dependency fetch timeout - you know who you are) -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not.
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
it all depends on whether olamy decides as RM to backport or not. he is RM for the 3.0.4 release by virtue of action. On Tuesday, 3 January 2012, Mark Derricutt wrote: > Surely something as egregious as allowing releases to break should block > 3.0.4 from being released tho. As someone who uses GPG in that manner for > some of his releases I'd certainly want 3.0.4 to be able to release... > > -- > "Great artists are extremely selfish and arrogant things" — Steven Wilson, > Porcupine Tree > > On Wed, Jan 4, 2012 at 5:23 AM, Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote: > >> I have checked in a fix towards 3.0.5... >> >> Pester olamy to backport... >> >> though he may want to wait for me to write the tests of the fix >> (manual testing confirms the fix... just have to figure out how to get >> automated testing!) >> >> On 3 January 2012 16:03, Mark Derricutt wrote: >> > Is this still broken under the 3.0.4-RC4 builds, or just 3.0.3? >> > >> > >> > -- >> > "Great artists are extremely selfish and arrogant things" — Steven >> Wilson, >> > Porcupine Tree >> > >> > >> > On Wed, Jan 4, 2012 at 4:18 AM, Stephen Connolly < >> > stephen.alan.conno...@gmail.com> wrote: >> > >> >> Hi, >> >> >> >> I just found a regression: >> >> >> >> http://jira.codehaus.org/browse/MNG-5224 >> >> >> >> I think it is serious enough to recommend users avoid using the above >> >> combination if you rely on properties in a settings.xml profile to GPG >> >> sign your releases. (i.e. anyone pushing to Central) >> >> >> >> -Stephen >> >> >> >> - >> >> 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: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Surely something as egregious as allowing releases to break should block 3.0.4 from being released tho. As someone who uses GPG in that manner for some of his releases I'd certainly want 3.0.4 to be able to release... -- "Great artists are extremely selfish and arrogant things" — Steven Wilson, Porcupine Tree On Wed, Jan 4, 2012 at 5:23 AM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > I have checked in a fix towards 3.0.5... > > Pester olamy to backport... > > though he may want to wait for me to write the tests of the fix > (manual testing confirms the fix... just have to figure out how to get > automated testing!) > > On 3 January 2012 16:03, Mark Derricutt wrote: > > Is this still broken under the 3.0.4-RC4 builds, or just 3.0.3? > > > > > > -- > > "Great artists are extremely selfish and arrogant things" — Steven > Wilson, > > Porcupine Tree > > > > > > On Wed, Jan 4, 2012 at 4:18 AM, Stephen Connolly < > > stephen.alan.conno...@gmail.com> wrote: > > > >> Hi, > >> > >> I just found a regression: > >> > >> http://jira.codehaus.org/browse/MNG-5224 > >> > >> I think it is serious enough to recommend users avoid using the above > >> combination if you rely on properties in a settings.xml profile to GPG > >> sign your releases. (i.e. anyone pushing to Central) > >> > >> -Stephen > >> > >> - > >> 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 > >
Running TestNG tests with Maven fails
Hi All, I am trying to run TestNG tests in Maven. here is my configuration: pom.xml: org.testng testng 6.3.1 test org.apache.maven.plugins maven-surefire-plugin 2.11 src/test/resources/testng.xml This is the testNG conf file: when I run with eclipse - no problem. when I run with mvn test - all test run successfully, but build failed with error: suiteXmlFiles is configured, but there is no TestNG dependency Please help -- View this message in context: http://maven.40175.n5.nabble.com/Running-TestNG-tests-with-Maven-fails-tp5117399p5117399.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Unable to use maven-ant-tasks
If I add the following line to your script, it works smoothly (if the maven-ant-tasks jar is on ant classpath): uri="antlib:org.apache.maven.artifact.ant"/> Cheers, Guillaume Le 27/12/2011 01:41, Scott Shambarger a écrit : I'm new to ant and maven, so I'm sure this is a silly questionstill, I'm stuck. I'm using the rpm install of ant/maven/etc for Fedora 16. I'm trying to build a project that requires ant and maven, and uses maven-ant-tasks (I have maven-ant-tasks-2.1.1-8.fc16 installed), however, I always receive the following error: BUILD FAILED /opt/devel/test/build.xml:4: Problem: failed to create task or type antlib:org.apache.maven.artifact.ant:remoteRepository Cause: The name is undefined. I'm pretty sure I have some sort of configuration error, but after several hours crawling the examples and docs, I'm just not making any progress... I don't have CLASSPATH defined, and have tried using ant -noclasspath with the same results. I've linked the /usr/share/java/maven-ant-tasks.jar (from the rpm) into my ~/.ant/lib directory, and reduced the build.xml file to the following (this file uses the same syntax as the project I'm trying to build, and produces the same error): --- build.xml xmlns:artifact="antlib:org.apache.maven.artifact.ant"> http://example.com";> end build.xml This appears to follow the example on http://maven.apache.org/ant-tasks/installation.html which has the following: ... The output of ant -diagnostics are: --- Ant diagnostics report --- Apache Ant(TM) version 1.8.2 compiled on July 6 2011 --- Implementation Version --- core tasks : 1.8.2 in file:/usr/share/java/ant.jar --- ANT PROPERTIES --- ant.version: Apache Ant(TM) version 1.8.2 compiled on July 6 2011 ant.java.version: 1.6 Is this the Apache Harmony VM? no Is this the Kaffe VM? no Is this gij/gcj? no ant.core.lib: /usr/share/java/ant.jar ant.home: /usr/share/ant --- ANT_HOME/lib jar listing --- ant.home: /usr/share/ant ant-junit.jar (102000 bytes) ant.jar (1935105 bytes) ant-bootstrap.jar (19759 bytes) ant-launcher.jar (12307 bytes) --- USER_HOME/.ant/lib jar listing --- user.home: /opt/devel maven-ant-tasks.jar (61063 bytes) --- Tasks availability --- p4reopen : Not Available (the implementation class is not present) ...(cut short for simplicity) ddcreator : Not Available (the implementation class is not present) A task being missing/unavailable should only matter if you are trying to use it --- org.apache.env.Which diagnostics --- Not available. Download it at http://xml.apache.org/commons/ --- XML Parser information --- XML Parser : org.apache.xerces.jaxp.SAXParserImpl XML Parser Location: file:/usr/share/java/xerces-j2-2.11.0.jar Namespace-aware parser : org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser Namespace-aware parser Location: file:/usr/share/java/xerces-j2-2.11.0.jar --- XSLT Processor information --- XSLT Processor : com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl XSLT Processor Location: unknown --- System properties --- java.runtime.name : OpenJDK Runtime Environment sun.boot.library.path : /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64 java.vm.version : 20.0-b11 ant.library.dir : /usr/share/ant/lib java.vm.vendor : Sun Microsystems Inc. java.vendor.url : http://java.sun.com/ path.separator : : java.vm.name : OpenJDK 64-Bit Server VM file.encoding.pkg : sun.io user.country : US sun.java.launcher : SUN_STANDARD sun.os.patch.level : unknown java.vm.specification.name : Java Virtual Machine Specification user.dir : /opt/devel/test java.runtime.version : 1.6.0_22-b22 java.awt.graphicsenv : sun.awt.X11GraphicsEnvironment java.endorsed.dirs : /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/endorsed os.arch : amd64 java.io.tmpdir : /tmp line.separator : java.vm.specification.vendor : Sun Microsystems Inc. os.name : Linux ant.home : /usr/share/ant sun.jnu.encoding : UTF-8 java.library.path : /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64/server:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64:/usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/../lib/amd64:/usr/java/packages/lib/amd64:/usr/lib64:/lib64:/lib:/usr/lib java.specification.name : Java Platform API S
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
I have checked in a fix towards 3.0.5... Pester olamy to backport... though he may want to wait for me to write the tests of the fix (manual testing confirms the fix... just have to figure out how to get automated testing!) On 3 January 2012 16:03, Mark Derricutt wrote: > Is this still broken under the 3.0.4-RC4 builds, or just 3.0.3? > > > -- > "Great artists are extremely selfish and arrogant things" — Steven Wilson, > Porcupine Tree > > > On Wed, Jan 4, 2012 at 4:18 AM, Stephen Connolly < > stephen.alan.conno...@gmail.com> wrote: > >> Hi, >> >> I just found a regression: >> >> http://jira.codehaus.org/browse/MNG-5224 >> >> I think it is serious enough to recommend users avoid using the above >> combination if you rely on properties in a settings.xml profile to GPG >> sign your releases. (i.e. anyone pushing to Central) >> >> -Stephen >> >> - >> 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
How to configure properties-maven-plugin to report built in properties/variables
How can I get project variables/properties exported to property file?
I'm using properties-maven-plugin and it's good but it only reports
things I have explicitly created as properties in my project. I need
to also get a report on things that maven already defined such as:
scm:svn:https://...
scm:svn:https://...
https://...
...
To get these values reported using this plugin I have to add this to my project:
${project.scm.connection}
${project.scm.developerConnection}
${project.scm.url}
This is tedious and error prone. Is there a way to report this
without adding variables as properties manually?
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
RE: Unable to use maven-ant-tasks
I'm using maven-ant-tasks 2.1.3 with just the xmlns specification with no problems. I have it installed in ANT_HOME/lib, but initially used it from HOME/.ant/lib with no problems. Haven't tried it with the -lib parameter, but no reason to believe it wouldn't work that way as well. Maybe try upgrading to the 2.1.3 version, which is the latest released version. Matt > -Original Message- > From: Scott Shambarger [mailto:scott-ma...@shambarger.net] > Sent: Monday, December 26, 2011 5:41 PM > To: users@maven.apache.org > Subject: Unable to use maven-ant-tasks > > I'm new to ant and maven, so I'm sure this is a silly > questionstill, I'm stuck. > > I'm using the rpm install of ant/maven/etc for Fedora 16. I'm trying > to build a project that requires ant and maven, and uses maven-ant- > tasks > (I have maven-ant-tasks-2.1.1-8.fc16 installed), however, I always > receive the following error: > > BUILD FAILED > /opt/devel/test/build.xml:4: Problem: failed to create task or type > antlib:org.apache.maven.artifact.ant:remoteRepository > Cause: The name is undefined. > > I'm pretty sure I have some sort of configuration error, but after > several hours crawling the examples and docs, I'm just not making any > progress... I don't have CLASSPATH defined, and have tried using ant > -noclasspath with the same results. > > I've linked the /usr/share/java/maven-ant-tasks.jar (from the rpm) into > my ~/.ant/lib directory, and reduced the build.xml file to the > following > (this file uses the same syntax as the project I'm trying to build, and > produces the same error): > > --- build.xml > > > xmlns:artifact="antlib:org.apache.maven.artifact.ant"> > url="http://example.com";> > > > > > > > end build.xml > > This appears to follow the example on > http://maven.apache.org/ant-tasks/installation.html which has the > following: > > >... > > > The output of ant -diagnostics are: > > --- Ant diagnostics report --- > Apache Ant(TM) version 1.8.2 compiled on July 6 2011 > > --- > Implementation Version > --- > core tasks : 1.8.2 in file:/usr/share/java/ant.jar > > --- > ANT PROPERTIES > --- > ant.version: Apache Ant(TM) version 1.8.2 compiled on July 6 2011 > ant.java.version: 1.6 > Is this the Apache Harmony VM? no > Is this the Kaffe VM? no > Is this gij/gcj? no > ant.core.lib: /usr/share/java/ant.jar > ant.home: /usr/share/ant > > --- > ANT_HOME/lib jar listing > --- > ant.home: /usr/share/ant > ant-junit.jar (102000 bytes) > ant.jar (1935105 bytes) > ant-bootstrap.jar (19759 bytes) > ant-launcher.jar (12307 bytes) > > --- > USER_HOME/.ant/lib jar listing > --- > user.home: /opt/devel > maven-ant-tasks.jar (61063 bytes) > > --- > Tasks availability > --- > p4reopen : Not Available (the implementation class is not present) > ...(cut short for simplicity) > ddcreator : Not Available (the implementation class is not present) > A task being missing/unavailable should only matter if you are trying > to use it > > --- > org.apache.env.Which diagnostics > --- > Not available. > Download it at http://xml.apache.org/commons/ > > --- > XML Parser information > --- > XML Parser : org.apache.xerces.jaxp.SAXParserImpl > XML Parser Location: file:/usr/share/java/xerces-j2-2.11.0.jar > Namespace-aware parser : > org.apache.xerces.jaxp.SAXParserImpl$JAXPSAXParser > Namespace-aware parser Location: > file:/usr/share/java/xerces-j2-2.11.0.jar > > --- > XSLT Processor information > --- > XSLT Processor : > com.sun.org.apache.xalan.internal.xsltc.trax.TransformerImpl > XSLT Processor Location: unknown > > --- > System properties > --- > java.runtime.name : OpenJDK Runtime Environment > sun.boot.library.path : > /usr/lib/jvm/java-1.6.0-openjdk-1.6.0.0.x86_64/jre/lib/amd64 > java.vm.version : 20.0-b11 > ant.library.dir : /usr/share/ant/lib > java.vm.vendor : Sun Microsystems Inc. > java.vendor.url : http://java.sun.com/ > path.separator : : > java.vm.name : OpenJDK 64-Bit Server VM > file.encoding.pkg : sun.io > user.country : US > sun.java.launcher : SUN_STANDARD > sun.os.patch.level : unknown > java.vm.specification.name : Java Virtual Machine Specification > user.dir : /opt/devel/test > java.runtime.version : 1.6.0_22-b22 > java.aw
Re: assembly plug-in config
Hi, not sure of what you are trying to achieve here but the documentation should help you: * http://maven.apache.org/plugins/maven-assembly-plugin/assembly.html * http://maven.apache.org/plugins/maven-assembly-plugin/examples/index.html Cheers, Guillaume Le 3/01/2012 09:28, Prashant Neginahal a écrit : Hi, I am using assembly plug-in to create zip of multi-module project of below structure. parent1 --child-1 --child-2 pom.xml I would like to create the parent1.zip of same structure as below. parent1.zip --child-1 --child-2 pom.xml Could someone help what could be the assembly configuration for the same, please? Thanks, Prashant - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Is this still broken under the 3.0.4-RC4 builds, or just 3.0.3? -- "Great artists are extremely selfish and arrogant things" — Steven Wilson, Porcupine Tree On Wed, Jan 4, 2012 at 4:18 AM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > Hi, > > I just found a regression: > > http://jira.codehaus.org/browse/MNG-5224 > > I think it is serious enough to recommend users avoid using the above > combination if you rely on properties in a settings.xml profile to GPG > sign your releases. (i.e. anyone pushing to Central) > > -Stephen > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
WARNING: Cannot use Maven 3.0.3 with Maven Release Plugin 2.2.2 (MNG-5224)
Hi, I just found a regression: http://jira.codehaus.org/browse/MNG-5224 I think it is serious enough to recommend users avoid using the above combination if you rely on properties in a settings.xml profile to GPG sign your releases. (i.e. anyone pushing to Central) -Stephen - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Javadoc creation is giving errors
Our package structure is little different. we have src/com/<>/<>/<>/ . . . . and ours is multi-module adf project. On Tue, Jan 3, 2012 at 7:05 PM, Benson Margulies wrote: > Why src? Aren't your sources in src/main/java? > > On Tue, Jan 3, 2012 at 5:31 AM, yerra babji > wrote: > > Hi, > > > > I have added the following plugin in my pom.xml file's build > > configuration. When i execute the mvn package, Its getting failed during > > javadoc creation and complaining like "import package does not > exist" > > > > > > org.apache.maven.plugins > > maven-javadoc-plugin > > 2.8 > > > > > > package > > jar > > > >src/ > > > > > > > > > > > > But after that if I run " mvn javadoc:jar " (without cleaning the target) > > Its running fine and creating javadoc. > > > > Could anyone please suggest me how to avoid this issue. > > > > Thanks in advance for your support. > > > > Regads, > > Babji > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: Javadoc creation is giving errors
Why src? Aren't your sources in src/main/java? On Tue, Jan 3, 2012 at 5:31 AM, yerra babji wrote: > Hi, > > I have added the following plugin in my pom.xml file's build > configuration. When i execute the mvn package, Its getting failed during > javadoc creation and complaining like "import package does not exist" > > > org.apache.maven.plugins > maven-javadoc-plugin > 2.8 > > > package > jar > > src/ > > > > > > But after that if I run " mvn javadoc:jar " (without cleaning the target) > Its running fine and creating javadoc. > > Could anyone please suggest me how to avoid this issue. > > Thanks in advance for your support. > > Regads, > Babji - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Fatal error compiling: Prohibited package name: java.lang
On Tue, Jan 3, 2012 at 7:41 AM, Martin Gainty wrote: > > Good Catch Benson > $ANT_HOME\lib09/09/2009 03:44 AM 12,605,641 tools.jarcan i toss > tools.jar onto the classpath to resolve this issue? > Is there anyone to ping at Hadoop to determine the missing location for > tools.jar? > Is there anyone at ping at Apple to determine the missing location for > tooks.jar? Martin, it is *not missing.* http://maven.apache.org/general.html#tools-jar-dependency The contents are included in tools.jar. The above-linked doc on our own site shows how to handle it. > thanks, > Martin > __ > the smart people get off at alewife..personal quote > Date: Tue, 3 Jan 2012 > 06:08:13 -0500 >> Subject: Re: Fatal error compiling: Prohibited package name: java.lang >> From: bimargul...@gmail.com >> To: users@maven.apache.org >> >> On Mon, Jan 2, 2012 at 5:45 PM, Ronald Petty wrote: >> > Martin, >> > >> > Thanks for the tip. I tried a few more things and found the root cause. >> > On a Mac, tools.jar is missing and I had placed a symbolic link from >> > tools.jar to classes.jar (to fix other issues). >> >> tools.jar is never present in an Apple JDK. Normally, maven works >> perfectly fine, you shouldn't need that link. If Hadoop has a >> dependency on tools.jar you should open a JIRA on them, there's a >> standard cliche for MacOS. >> >> If your problem is not specific to Hadoop, I'd suspect your setting of >> JAVA_HOME. Mine is : >> >> JAVA_HOME=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home >> >> It turns out that was >> > causing the problem. I am not certain why at this time, but if I can find >> > something I will update. >> > >> > Thanks again. >> > >> > Ron >> > >> > On Mon, Jan 2, 2012 at 5:42 PM, Martin Gainty wrote: >> > >> >> >> >> Hi Ron- If the problem is the javac executable is being lost then:i would >> >> specifically call maven-compiler-plugin and set the configuration >> >> path to specific location of javac e.ghttp:// >> >> maven.apache.org/plugins/maven-compiler-plugin/examples/compile-using-different-jdk.htmlDoes >> >> this help? >> >> Martin >> >> __ >> >> Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité >> >> >> >> Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene >> >> Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte >> >> Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht >> >> dient lediglich dem Austausch von Informationen und entfaltet keine >> >> rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von >> >> E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. >> >> Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le >> >> destinataire prévu, nous te demandons avec bonté que pour satisfaire >> >> informez l'expéditeur. N'importe quelle diffusion non autorisée ou la >> >> copie >> >> de ceci est interdite. Ce message sert à l'information seulement et n'aura >> >> pas n'importe quel effet légalement obligatoire. Étant donné que les email >> >> peuvent facilement être sujets à la manipulation, nous ne pouvons accepter >> >> aucune responsabilité pour le contenu fourni. >> >> >> >> > From: ronald.pe...@gmail.com >> >> > Date: Mon, 2 Jan 2012 17:01:08 -0500 >> >> > Subject: Fatal error compiling: Prohibited package name: java.lang >> >> > To: users@maven.apache.org >> >> > >> >> > Hello, >> >> > >> >> > I am trying to build Hadoop (trunk) on a Mac via "mvn -e -X compile" on >> >> > a >> >> > Mac/Snow Leopard. I am receiving the following error through: >> >> > >> >> > Apache Maven 3.0.3 (r1075438; 2011-02-28 12:31:09-0500) >> >> > Maven home: /usr/share/maven >> >> > Java version: 1.6.0_29, vendor: Apple Inc. >> >> > Java home: >> >> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home >> >> > Default locale: en_US, platform encoding: MacRoman >> >> > OS name: "mac os x", version: "10.6.8", arch: "x86_64", family: "mac" >> >> > [INFO] Error stacktraces are turned on. >> >> > >> >> > ... >> >> > >> >> > [INFO] Compiling 8 source files to >> >> > >> >> /data/hadoop-trunk/hadoop-common-project/hadoop-annotations/target/classes >> >> > [INFO] >> >> > >> >> > [INFO] BUILD FAILURE >> >> > [INFO] >> >> > >> >> > [INFO] Total time: 1.379s >> >> > [INFO] Finished at: Mon Jan 02 16:43:22 EST 2012 >> >> > [INFO] Final Memory: 4M/81M >> >> > [INFO] >> >> > >> >> > [ERROR] Failed to execute goal >> >> > org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile >> >> > (default-compile) on project hadoop-annotations: Fatal error compiling: >> >> > Prohibited package name: java.lang -> [Help 1] >> >> > org.apache.maven.lifecy
RE: Fatal error compiling: Prohibited package name: java.lang
Good Catch Benson $ANT_HOME\lib09/09/2009 03:44 AM12,605,641 tools.jarcan i toss tools.jar onto the classpath to resolve this issue? Is there anyone to ping at Hadoop to determine the missing location for tools.jar? Is there anyone at ping at Apple to determine the missing location for tooks.jar? thanks, Martin __ the smart people get off at alewife..personal quote > Date: Tue, 3 Jan 2012 06:08:13 -0500 > Subject: Re: Fatal error compiling: Prohibited package name: java.lang > From: bimargul...@gmail.com > To: users@maven.apache.org > > On Mon, Jan 2, 2012 at 5:45 PM, Ronald Petty wrote: > > Martin, > > > > Thanks for the tip. I tried a few more things and found the root cause. > > On a Mac, tools.jar is missing and I had placed a symbolic link from > > tools.jar to classes.jar (to fix other issues). > > tools.jar is never present in an Apple JDK. Normally, maven works > perfectly fine, you shouldn't need that link. If Hadoop has a > dependency on tools.jar you should open a JIRA on them, there's a > standard cliche for MacOS. > > If your problem is not specific to Hadoop, I'd suspect your setting of > JAVA_HOME. Mine is : > > JAVA_HOME=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home > > It turns out that was > > causing the problem. I am not certain why at this time, but if I can find > > something I will update. > > > > Thanks again. > > > > Ron > > > > On Mon, Jan 2, 2012 at 5:42 PM, Martin Gainty wrote: > > > >> > >> Hi Ron- If the problem is the javac executable is being lost then:i would > >> specifically call maven-compiler-plugin and set the configuration > >> path to specific location of javac e.ghttp:// > >> maven.apache.org/plugins/maven-compiler-plugin/examples/compile-using-different-jdk.htmlDoes > >> this help? > >> Martin > >> __ > >> Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité > >> > >> Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene > >> Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte > >> Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht > >> dient lediglich dem Austausch von Informationen und entfaltet keine > >> rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von > >> E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. > >> Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le > >> destinataire prévu, nous te demandons avec bonté que pour satisfaire > >> informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie > >> de ceci est interdite. Ce message sert à l'information seulement et n'aura > >> pas n'importe quel effet légalement obligatoire. Étant donné que les email > >> peuvent facilement être sujets à la manipulation, nous ne pouvons accepter > >> aucune responsabilité pour le contenu fourni. > >> > >> > From: ronald.pe...@gmail.com > >> > Date: Mon, 2 Jan 2012 17:01:08 -0500 > >> > Subject: Fatal error compiling: Prohibited package name: java.lang > >> > To: users@maven.apache.org > >> > > >> > Hello, > >> > > >> > I am trying to build Hadoop (trunk) on a Mac via "mvn -e -X compile" on a > >> > Mac/Snow Leopard. I am receiving the following error through: > >> > > >> > Apache Maven 3.0.3 (r1075438; 2011-02-28 12:31:09-0500) > >> > Maven home: /usr/share/maven > >> > Java version: 1.6.0_29, vendor: Apple Inc. > >> > Java home: > >> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home > >> > Default locale: en_US, platform encoding: MacRoman > >> > OS name: "mac os x", version: "10.6.8", arch: "x86_64", family: "mac" > >> > [INFO] Error stacktraces are turned on. > >> > > >> > ... > >> > > >> > [INFO] Compiling 8 source files to > >> > > >> /data/hadoop-trunk/hadoop-common-project/hadoop-annotations/target/classes > >> > [INFO] > >> > > >> > [INFO] BUILD FAILURE > >> > [INFO] > >> > > >> > [INFO] Total time: 1.379s > >> > [INFO] Finished at: Mon Jan 02 16:43:22 EST 2012 > >> > [INFO] Final Memory: 4M/81M > >> > [INFO] > >> > > >> > [ERROR] Failed to execute goal > >> > org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile > >> > (default-compile) on project hadoop-annotations: Fatal error compiling: > >> > Prohibited package name: java.lang -> [Help 1] > >> > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute > >> > goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile > >> > (default-compile) on project hadoop-annotations: Fatal error compiling > >> > at > >> > > >> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) > >> > at > >> > > >> org.apache.maven.lifecycle.interna
Re: Fatal error compiling: Prohibited package name: java.lang
On Mon, Jan 2, 2012 at 5:45 PM, Ronald Petty wrote: > Martin, > > Thanks for the tip. I tried a few more things and found the root cause. > On a Mac, tools.jar is missing and I had placed a symbolic link from > tools.jar to classes.jar (to fix other issues). tools.jar is never present in an Apple JDK. Normally, maven works perfectly fine, you shouldn't need that link. If Hadoop has a dependency on tools.jar you should open a JIRA on them, there's a standard cliche for MacOS. If your problem is not specific to Hadoop, I'd suspect your setting of JAVA_HOME. Mine is : JAVA_HOME=/System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home It turns out that was > causing the problem. I am not certain why at this time, but if I can find > something I will update. > > Thanks again. > > Ron > > On Mon, Jan 2, 2012 at 5:42 PM, Martin Gainty wrote: > >> >> Hi Ron- If the problem is the javac executable is being lost then:i would >> specifically call maven-compiler-plugin and set the configuration >> path to specific location of javac e.ghttp:// >> maven.apache.org/plugins/maven-compiler-plugin/examples/compile-using-different-jdk.htmlDoes >> this help? >> Martin >> __ >> Verzicht und Vertraulichkeitanmerkung/Note de déni et de confidentialité >> >> Diese Nachricht ist vertraulich. Sollten Sie nicht der vorgesehene >> Empfaenger sein, so bitten wir hoeflich um eine Mitteilung. Jede unbefugte >> Weiterleitung oder Fertigung einer Kopie ist unzulaessig. Diese Nachricht >> dient lediglich dem Austausch von Informationen und entfaltet keine >> rechtliche Bindungswirkung. Aufgrund der leichten Manipulierbarkeit von >> E-Mails koennen wir keine Haftung fuer den Inhalt uebernehmen. >> Ce message est confidentiel et peut être privilégié. Si vous n'êtes pas le >> destinataire prévu, nous te demandons avec bonté que pour satisfaire >> informez l'expéditeur. N'importe quelle diffusion non autorisée ou la copie >> de ceci est interdite. Ce message sert à l'information seulement et n'aura >> pas n'importe quel effet légalement obligatoire. Étant donné que les email >> peuvent facilement être sujets à la manipulation, nous ne pouvons accepter >> aucune responsabilité pour le contenu fourni. >> >> > From: ronald.pe...@gmail.com >> > Date: Mon, 2 Jan 2012 17:01:08 -0500 >> > Subject: Fatal error compiling: Prohibited package name: java.lang >> > To: users@maven.apache.org >> > >> > Hello, >> > >> > I am trying to build Hadoop (trunk) on a Mac via "mvn -e -X compile" on a >> > Mac/Snow Leopard. I am receiving the following error through: >> > >> > Apache Maven 3.0.3 (r1075438; 2011-02-28 12:31:09-0500) >> > Maven home: /usr/share/maven >> > Java version: 1.6.0_29, vendor: Apple Inc. >> > Java home: >> /System/Library/Java/JavaVirtualMachines/1.6.0.jdk/Contents/Home >> > Default locale: en_US, platform encoding: MacRoman >> > OS name: "mac os x", version: "10.6.8", arch: "x86_64", family: "mac" >> > [INFO] Error stacktraces are turned on. >> > >> > ... >> > >> > [INFO] Compiling 8 source files to >> > >> /data/hadoop-trunk/hadoop-common-project/hadoop-annotations/target/classes >> > [INFO] >> > >> > [INFO] BUILD FAILURE >> > [INFO] >> > >> > [INFO] Total time: 1.379s >> > [INFO] Finished at: Mon Jan 02 16:43:22 EST 2012 >> > [INFO] Final Memory: 4M/81M >> > [INFO] >> > >> > [ERROR] Failed to execute goal >> > org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile >> > (default-compile) on project hadoop-annotations: Fatal error compiling: >> > Prohibited package name: java.lang -> [Help 1] >> > org.apache.maven.lifecycle.LifecycleExecutionException: Failed to execute >> > goal org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile >> > (default-compile) on project hadoop-annotations: Fatal error compiling >> > at >> > >> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:217) >> > at >> > >> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:153) >> > at >> > >> org.apache.maven.lifecycle.internal.MojoExecutor.execute(MojoExecutor.java:145) >> > >> > >> > Prior to this error message, Maven displays the command and args that are >> > executed. If I copy those and run it from the command line it works. I >> > have seen websites describing what the error means in general, but I have >> > not been able to figure out why Maven fails but the command line works. >> If >> > I echo $JAVA_HOME it is unset on the command line. If I set it to the >> > something else, it is not changed in the Maven output. >> > >> > Any pointers? >> > >> > Kindest regards. >> > >> > Ron >> >> - To unsubscribe, e-mail: users-unsub
Javadoc creation is giving errors
Hi, I have added the following plugin in my pom.xml file's build configuration. When i execute the mvn package, Its getting failed during javadoc creation and complaining like "import package does not exist" org.apache.maven.plugins maven-javadoc-plugin 2.8 package jar src/ But after that if I run " mvn javadoc:jar " (without cleaning the target) Its running fine and creating javadoc. Could anyone please suggest me how to avoid this issue. Thanks in advance for your support. Regads, Babji
assembly plug-in config
Hi, I am using assembly plug-in to create zip of multi-module project of below structure. parent1 --child-1 --child-2 pom.xml I would like to create the parent1.zip of same structure as below. parent1.zip --child-1 --child-2 pom.xml Could someone help what could be the assembly configuration for the same, please? Thanks, Prashant
