Re: Maven2 jsf-web project on Eclipse
On Thu, Sep 17, 2009 at 11:43 PM, MavenZede wrote: > > I have been trying to run a maven2 jsf project on Eclipse Galileo, but I did > not unfortunately. I tried a lot of ways, read thousands of web pages. My > first problem is that I cannot import my maven2 web project into Eclipse. I > know it should be happen when I run this mvn eclipse:eclipse, however it > doesnt. The eclipse project file (.project) already came after I run above > mentioned command, but again unfortunately this .project file could not > opened with eclipse. Please be specific when you say "could not opened with eclipse". Do you mean that when you tried File > Import... that * the project was not available for selection * Eclipse gave an error message If it was "the project was not available for selection" then you need did you read http://maven.apache.org/plugins/maven-eclipse-plugin/faq.html#import-project Also in http://maven.apache.org/plugins/maven-eclipse-plugin/reactor.html it tells you in the paragraph after step 11 to "Note, you have to delete the .project-file of your parent project before." This is because if the project already exists inside eclipse it won't let you import projects that are located "under" that directory. By deleting the .project file your are tricking eclipse into allowing this. If it was "Eclipse gave an error message", then providing the error message would be helpful in trouble shooting the problem. > Some specification of system are ; > ---Apache tomcat 6.0 > ---myFaces 1.2.7 for jsf > ---Eclipse galileo (3.5 with WTP 3.1) - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to identify the Jdk version ???
essentially you can even compile with java 1.6 and use the 1.3 runtime libraries and source 1.3 and target 1.3 and the resulting classes will be just as good as compiling with java 1.3 the real issue you have is ensuring that the class and method signatures that you have used in your code are only those for 1.4 or earlier that is where either a full set of unit tests or something like animal- sniffer comes in. unfortunately I have not released animal-sniffer from codehaus *yet* so you'd have to use the original version from java.net if you can wait a short while org.codehaus.mojo:animal-sniffer-maven- plugin and you can use that (short time is a week or two) Sent from my [rhymes with tryPod] ;-) On 17 Sep 2009, at 23:06, raghu guru wrote: Thanks Again, Is there any properties available that shows compiled with 1.4, may be if its available i want to include into MANIFEST.MF or is there a way to just confirm it On Thu, Sep 17, 2009 at 4:57 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: sorry, I missed your pom snippet on this small screen your classes were compiled with java 1.4 your jar was packaged up by a java 1.5 jre Sent from my [rhymes with tryPod] ;-) On 17 Sep 2009, at 22:50, raghu guru wrote: thanks for replying is this means, that configuring compiler version / executable in compiler plugin will not have any effect on this?? i thought by classes are compiled with javac mentioned in executable tag.. On Thu, Sep 17, 2009 at 4:40 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: your code was compiled with java 1.5 in compatibility mode for 1.4 providing you have only used classes and methods only from the 1.4 runtime libraries, everything will be fine you need to use another tool to ensure that you have not accidentally used some 1.5 methods (eg String.isEmpty()) animal-sniffer is one tool to do this check for you Sent from my [rhymes with tryPod] ;-) On 17 Sep 2009, at 22:32, raghu guru wrote: Hi All, I use Maven 2.2.1 and it runs on JDK 1.5 and above, but my source code is not 1.5 compatible yet, so i configured my compiler plugin as shown below. Everything works fine. but when i look into MANIFEST.MF of my jar file it shows Build-Jdk: 1.5.0_13. So how do i confirm that my code were compiled with 1.4 only not with 1.5 ?? Please Help . org.apache.maven.plugins maven-compiler-plugin true C:\JDK\ibm-jdk-1.4\bin\javac IBM-JDK-1.4 Thanks Jan --- -- 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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to identify the Jdk version ???
animal-sniffer or a similar tool Sent from my [rhymes with tryPod] ;-) On 17 Sep 2009, at 23:06, raghu guru wrote: Thanks Again, Is there any properties available that shows compiled with 1.4, may be if its available i want to include into MANIFEST.MF or is there a way to just confirm it On Thu, Sep 17, 2009 at 4:57 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: sorry, I missed your pom snippet on this small screen your classes were compiled with java 1.4 your jar was packaged up by a java 1.5 jre Sent from my [rhymes with tryPod] ;-) On 17 Sep 2009, at 22:50, raghu guru wrote: thanks for replying is this means, that configuring compiler version / executable in compiler plugin will not have any effect on this?? i thought by classes are compiled with javac mentioned in executable tag.. On Thu, Sep 17, 2009 at 4:40 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: your code was compiled with java 1.5 in compatibility mode for 1.4 providing you have only used classes and methods only from the 1.4 runtime libraries, everything will be fine you need to use another tool to ensure that you have not accidentally used some 1.5 methods (eg String.isEmpty()) animal-sniffer is one tool to do this check for you Sent from my [rhymes with tryPod] ;-) On 17 Sep 2009, at 22:32, raghu guru wrote: Hi All, I use Maven 2.2.1 and it runs on JDK 1.5 and above, but my source code is not 1.5 compatible yet, so i configured my compiler plugin as shown below. Everything works fine. but when i look into MANIFEST.MF of my jar file it shows Build-Jdk: 1.5.0_13. So how do i confirm that my code were compiled with 1.4 only not with 1.5 ?? Please Help . org.apache.maven.plugins maven-compiler-plugin true C:\JDK\ibm-jdk-1.4\bin\javac IBM-JDK-1.4 Thanks Jan --- -- 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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to identify the Jdk version ???
Thanks Again, Is there any properties available that shows compiled with 1.4, may be if its available i want to include into MANIFEST.MF or is there a way to just confirm it On Thu, Sep 17, 2009 at 4:57 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > sorry, I missed your pom snippet on this small screen > > your classes were compiled with java 1.4 > > your jar was packaged up by a java 1.5 jre > > Sent from my [rhymes with tryPod] ;-) > > On 17 Sep 2009, at 22:50, raghu guru wrote: > > thanks for replying >> >> is this means, that configuring compiler version / executable in compiler >> plugin will not have any effect on this?? >> >> i thought by classes are compiled with javac mentioned in executable tag.. >> >> On Thu, Sep 17, 2009 at 4:40 PM, Stephen Connolly < >> stephen.alan.conno...@gmail.com> wrote: >> >> your code was compiled with java 1.5 in compatibility mode for 1.4 >>> >>> providing you have only used classes and methods only from the 1.4 >>> runtime >>> libraries, everything will be fine >>> >>> you need to use another tool to ensure that you have not accidentally >>> used >>> some 1.5 methods (eg String.isEmpty()) >>> >>> animal-sniffer is one tool to do this check for you >>> >>> Sent from my [rhymes with tryPod] ;-) >>> >>> >>> On 17 Sep 2009, at 22:32, raghu guru wrote: >>> >>> Hi All, >>> I use Maven 2.2.1 and it runs on JDK 1.5 and above, but my source code is not 1.5 compatible yet, so i configured my compiler plugin as shown below. Everything works fine. but when i look into MANIFEST.MF of my jar file it shows Build-Jdk: 1.5.0_13. So how do i confirm that my code were compiled with 1.4 only not with 1.5 ?? Please Help . org.apache.maven.plugins maven-compiler-plugin true C:\JDK\ibm-jdk-1.4\bin\javac IBM-JDK-1.4 Thanks Jan >>> - >>> 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: How to identify the Jdk version ???
sorry, I missed your pom snippet on this small screen your classes were compiled with java 1.4 your jar was packaged up by a java 1.5 jre Sent from my [rhymes with tryPod] ;-) On 17 Sep 2009, at 22:50, raghu guru wrote: thanks for replying is this means, that configuring compiler version / executable in compiler plugin will not have any effect on this?? i thought by classes are compiled with javac mentioned in executable tag.. On Thu, Sep 17, 2009 at 4:40 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: your code was compiled with java 1.5 in compatibility mode for 1.4 providing you have only used classes and methods only from the 1.4 runtime libraries, everything will be fine you need to use another tool to ensure that you have not accidentally used some 1.5 methods (eg String.isEmpty()) animal-sniffer is one tool to do this check for you Sent from my [rhymes with tryPod] ;-) On 17 Sep 2009, at 22:32, raghu guru wrote: Hi All, I use Maven 2.2.1 and it runs on JDK 1.5 and above, but my source code is not 1.5 compatible yet, so i configured my compiler plugin as shown below. Everything works fine. but when i look into MANIFEST.MF of my jar file it shows Build-Jdk: 1.5.0_13. So how do i confirm that my code were compiled with 1.4 only not with 1.5 ?? Please Help . org.apache.maven.plugins maven-compiler-plugin true C:\JDK\ibm-jdk-1.4\bin\javac IBM-JDK-1.4 Thanks Jan - 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: How to identify the Jdk version ???
thanks for replying is this means, that configuring compiler version / executable in compiler plugin will not have any effect on this?? i thought by classes are compiled with javac mentioned in executable tag.. On Thu, Sep 17, 2009 at 4:40 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > your code was compiled with java 1.5 in compatibility mode for 1.4 > > providing you have only used classes and methods only from the 1.4 runtime > libraries, everything will be fine > > you need to use another tool to ensure that you have not accidentally used > some 1.5 methods (eg String.isEmpty()) > > animal-sniffer is one tool to do this check for you > > Sent from my [rhymes with tryPod] ;-) > > > On 17 Sep 2009, at 22:32, raghu guru wrote: > > Hi All, >> >> I use Maven 2.2.1 and it runs on JDK 1.5 and above, but my source code is >> not 1.5 compatible yet, so i configured my compiler plugin as shown below. >> Everything works fine. but when i look into MANIFEST.MF of my jar file it >> shows Build-Jdk: 1.5.0_13. So how do i confirm that my code were compiled >> with 1.4 only not with 1.5 ?? >> >> Please Help >> >> >> . >> org.apache.maven.plugins >> maven-compiler-plugin >> >> true >> C:\JDK\ibm-jdk-1.4\bin\javac >> IBM-JDK-1.4 >> >> >> Thanks >> Jan >> > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: How to identify the Jdk version ???
your code was compiled with java 1.5 in compatibility mode for 1.4 providing you have only used classes and methods only from the 1.4 runtime libraries, everything will be fine you need to use another tool to ensure that you have not accidentally used some 1.5 methods (eg String.isEmpty()) animal-sniffer is one tool to do this check for you Sent from my [rhymes with tryPod] ;-) On 17 Sep 2009, at 22:32, raghu guru wrote: Hi All, I use Maven 2.2.1 and it runs on JDK 1.5 and above, but my source code is not 1.5 compatible yet, so i configured my compiler plugin as shown below. Everything works fine. but when i look into MANIFEST.MF of my jar file it shows Build-Jdk: 1.5.0_13. So how do i confirm that my code were compiled with 1.4 only not with 1.5 ?? Please Help . org.apache.maven.plugins maven-compiler-plugin true C:\JDK\ibm-jdk-1.4\bin\javac IBM-JDK-1.4 Thanks Jan - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How to identify the Jdk version ???
Hi All, I use Maven 2.2.1 and it runs on JDK 1.5 and above, but my source code is not 1.5 compatible yet, so i configured my compiler plugin as shown below. Everything works fine. but when i look into MANIFEST.MF of my jar file it shows Build-Jdk: 1.5.0_13. So how do i confirm that my code were compiled with 1.4 only not with 1.5 ?? Please Help . org.apache.maven.plugins maven-compiler-plugin true C:\JDK\ibm-jdk-1.4\bin\javac IBM-JDK-1.4 Thanks Jan
Maven-war-plugin overlay overrides the current war project source.
Hi, I posted earlier about maven-war-plugin ovelay adding dependent's artifacts to the ccurrent project's webapp. After some more experiments, I found that it's even worse. Overlay overrides the current project's source with the one from the dependent war, even though the document says the current project's source has the precedence by default. I also specifically added the current project (empty ) in front of the depdendent war, and that did not correct the wrong behavior. Any idea? I'm using mavey-war-plugin 2.1-beta-1. Thanks, Gang - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: It's works, but I don't understand why...
I thought I had solved it, but I didn't. The solution lay in moving the particular troublesome module higher up in the build order. I couldn't find any conflicts, but there must have been some. I did not use the specification of the version in a parent pom. Hope this helps someone. johoso wrote: > > It seems like it works when I run it in Eclipse (Version: 3.4.1 Build id: > M20080911-1700, Maven plugin: Maven Integration for Eclipse by Sonatype > v0.9.6) > > But not in the following environment: > @mvn -version > Maven version: 2.0.9 > Java version: 1.6.0_06 > OS name: "sunos" version: "5.10" arch: "sparc" Family: "unix" > > However the workaround by Rémy works for the unix environment. > -- View this message in context: http://www.nabble.com/It%27s-works%2C-but-I-don%27t-understand-why...-tp21215546p25492254.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: help getting maven jetty plugin and jmx to work
Sorry... I am trying to start jetty with the Maven jetty plugin to allow me to see the JMX MBeans in Jetty. Specifically trying to track down JNDI errors, and according to the way you start the standalone Jetty, you pass in the JVM args. We How can I do this with the Maven plugin as there are no directions on the Jetty Wiki, and I have been trying different things all day with no luck at all. --- Thank You… Mick Knutson, President BASE Logic, Inc. Enterprise Architecture, Design, Mentoring & Agile Consulting p. (866) BLiNC-411: (254-6241-1) f. (415) 685-4233 Website: http://baselogic.com Linked IN: http://linkedin.com/in/mickknutson Vacation Rental: http://tahoe.baselogic.com --- On Thu, Sep 17, 2009 at 2:54 PM, Stephen Connolly < stephen.alan.conno...@gmail.com> wrote: > I might be a tad thick, but I'm having trouble seeing what your > questionhas to do with maven. have you tried the jetty lists first? > > On Thursday, September 17, 2009, Mick Knutson > wrote: > > I have tried to understand: > > http://wiki.eclipse.org/Jetty/Howto/Run_Jetty_with_JConsole > > > > But I do not have a jetty-jmx.xml that seems to work. > > > > I have tried this jetty-jmx.xml: > > > http://blogs.exist.com/oching/2009/02/26/configuring-jsw-embedded-jetty-with-jmx/ > > > > But I get deployment errors with this configuration. > > > > I am now trying to find out hot to add an OPTION as per: > > > > *Jetty 7 requires -DOPTIONS=jmx to be used when starting up Jetty. That > is, > > instead of the > > above, use this: > > java -DOPTIONS=jmx -jar start.jar etc/jetty-jmx.xml etc/jetty.xml > > * > > > > > > Any help would be greatly appreciated > > > > > > --- > > Thank You… > > > > Mick Knutson, President > > > > BASE Logic, Inc. > > Enterprise Architecture, Design, Mentoring & Agile Consulting > > p. (866) BLiNC-411: (254-6241-1) > > f. (415) 685-4233 > > > > Website: http://baselogic.com > > Linked IN: http://linkedin.com/in/mickknutson > > Vacation Rental: http://tahoe.baselogic.com > > --- > > > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Re: help getting maven jetty plugin and jmx to work
I might be a tad thick, but I'm having trouble seeing what your questionhas to do with maven. have you tried the jetty lists first? On Thursday, September 17, 2009, Mick Knutson wrote: > I have tried to understand: > http://wiki.eclipse.org/Jetty/Howto/Run_Jetty_with_JConsole > > But I do not have a jetty-jmx.xml that seems to work. > > I have tried this jetty-jmx.xml: > http://blogs.exist.com/oching/2009/02/26/configuring-jsw-embedded-jetty-with-jmx/ > > But I get deployment errors with this configuration. > > I am now trying to find out hot to add an OPTION as per: > > *Jetty 7 requires -DOPTIONS=jmx to be used when starting up Jetty. That is, > instead of the > above, use this: > java -DOPTIONS=jmx -jar start.jar etc/jetty-jmx.xml etc/jetty.xml > * > > > Any help would be greatly appreciated > > > --- > Thank You… > > Mick Knutson, President > > BASE Logic, Inc. > Enterprise Architecture, Design, Mentoring & Agile Consulting > p. (866) BLiNC-411: (254-6241-1) > f. (415) 685-4233 > > Website: http://baselogic.com > Linked IN: http://linkedin.com/in/mickknutson > Vacation Rental: http://tahoe.baselogic.com > --- > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven Central Compliance
Thanks Brian, I am sure eventually the person who does this validations will get tired of this manual labor, and starts writing scripts instead (or a nexus plugin). If you know the whereabouts of this script, what is just being written, please send me a link to source file (I am hoping it will be available in an open repo, am I wrong?). I believe once this validation script will be written, somebody will convert it to some kind of a Report plugin to validate early. Albert On Thu, Sep 17, 2009 at 1:17 PM, Brian Fox wrote: > Hi Albert, > We currently validate that signatures are present and valid for > artifacts. Most of that process is covered in the documents here: > http://nexus.sonatype.org/oss-repository-hosting.html#7 > > In the future we will hopefully be able to validate poms and other > content more thoroughly, but for now it's a manual scan of the pom > before the sync is turned on or the jars are loaded. > > On Thu, Sep 17, 2009 at 10:13 AM, Albert Kurucz > wrote: >> Hi, >> >> I have a project with builds with Maven. >> My goal is to see my project on Central. >> >> There is a nice guide at >> http://maven.apache.org/guides/mini/guide-central-repository-upload.html >> which tells me the requirements. >> >> Is there any Report plugin out there, which would check all the >> requirements for Central? >> If there is no such Report plugin, where is the actual script which >> handles the verifications and handles the uploads. I cannot believe >> projects are checked manually. >> >> I have another problem, "Guide to uploading artifacts to the Central >> Repository" does not specify requirements for multi-module Maven >> projects. >> >> Many of the project's POM configurations are inherited by the modules >> of the project. >> It is unspecified by this guide, whether the modules POMs also need to >> specify those settings explicitly or not, in case the developers' >> intention is to release those on Central. >> >> I have made this questions also to >> http://jira.codehaus.org/browse/MNG-4362 >> >> Thanks, >> Al >> >> - >> 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 > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven Central Compliance
Hi Albert, We currently validate that signatures are present and valid for artifacts. Most of that process is covered in the documents here: http://nexus.sonatype.org/oss-repository-hosting.html#7 In the future we will hopefully be able to validate poms and other content more thoroughly, but for now it's a manual scan of the pom before the sync is turned on or the jars are loaded. On Thu, Sep 17, 2009 at 10:13 AM, Albert Kurucz wrote: > Hi, > > I have a project with builds with Maven. > My goal is to see my project on Central. > > There is a nice guide at > http://maven.apache.org/guides/mini/guide-central-repository-upload.html > which tells me the requirements. > > Is there any Report plugin out there, which would check all the > requirements for Central? > If there is no such Report plugin, where is the actual script which > handles the verifications and handles the uploads. I cannot believe > projects are checked manually. > > I have another problem, "Guide to uploading artifacts to the Central > Repository" does not specify requirements for multi-module Maven > projects. > > Many of the project's POM configurations are inherited by the modules > of the project. > It is unspecified by this guide, whether the modules POMs also need to > specify those settings explicitly or not, in case the developers' > intention is to release those on Central. > > I have made this questions also to > http://jira.codehaus.org/browse/MNG-4362 > > Thanks, > Al > > - > 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: Plugin snapshot problem with Apache nexus repository
This seems to have been a nexus bug. I made some changes in how my mirrors were configured, and this problem evaporated. On Thu, Sep 17, 2009 at 10:22 AM, Olivier Lamy wrote: > Hi, > The snapshot url you are using and the stack trace you have could be > very helpfull. > > 2009/9/17 Benson Margulies : > > I set out to use a snapshot of the maven-release-plugin. I added the > > snapshot repo to the pluginRepositories, with snapshots set to true. > > > > Then I called out version 2.0-beta-10-SNAPSHOT as my release. I got an > error > > message from maven to the effect that it could not find the jar file. > > > > So I changed the version to call out the full timestamp version number, > and > > it worked. > > > > is this the intended behavior? > > > > > > -- > Olivier > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > >
Maven SNAPSHOT dependencies are not treated as snapshots
Hi all,
I have a problem that maven does not appear to be treating dependencies that
are specified as snapshots (i.e. Have a version that ends with ³-SNAPSHOT²)
as snapshots.
Even when the snapshot does appear in a remote repository within my
organisation, using a timestamp based filename, with a metadata file
describing the correct one. It seems that maven makes no attempt to work
out the actual snapshot to download and just attempts to download an
artifact with the exact version specified.
I have specified the repository in my pom that specifies snapshots ->
enabled -> true
I have seen the same pom file working on someone elses machine in the
company. I have upgraded from maven version 2.0.9 to 2.2.1 and it has made
no difference. I have no particular settings in my local settings file. I
am running OS X 10.5.8.
Here is an example of the output:
INFO] Scanning for projects...
[INFO]
[INFO] Building XXX Security
[INFO]task-segment: [package]
[INFO]
[INFO] [resources:resources {execution: default-resources}]
[WARNING] File encoding has not been set, using platform encoding MacRoman,
i.e. build is platform dependent!
[WARNING] Using platform encoding (MacRoman actually) to copy filtered
resources, i.e. build is platform dependent!
[INFO] Copying 2 resources
Downloading:
file:///Volumes/XXX_Dev/Maven/repository/com/package/xxx/XXX-Unit-Test/1.0-S
NAPSHOT/XXX-Unit-Test-1.0-SNAPSHOT.pom
[INFO] Unable to find resource
'com.package.xxx:XXX-Unit-Test:pom:1.0-SNAPSHOT' in repository internal
(file:///Volumes/XXX_Dev/Maven/repository)
Downloading:
http://repo2.maven.org/maven2/com/package/xxx/XXX-Unit-Test/1.0-SNAPSHOT/XXX
-Unit-Test-1.0-SNAPSHOT.pom
[INFO] Unable to find resource
'com.package.xxx:XXX-Unit-Test:pom:1.0-SNAPSHOT' in repository maven
(http://repo2.maven.org/maven2)
Downloading:
http://repository.jboss.org/maven2/com/package/xxx/XXX-Unit-Test/1.0-SNAPSHO
T/XXX-Unit-Test-1.0-SNAPSHOT.pom
[INFO] Unable to find resource
'com.package.xxx:XXX-Unit-Test:pom:1.0-SNAPSHOT' in repository JBoss
Repository (http://repository.jboss.org/maven2)
[INFO] [compiler:compile {execution: default-compile}]
[INFO] Nothing to compile - all classes are up to date
[INFO] [resources:testResources {execution: default-testResources}]
[WARNING] File encoding has not been set, using platform encoding MacRoman,
i.e. build is platform dependent!
[WARNING] Using platform encoding (MacRoman actually) to copy filtered
resources, i.e. build is platform dependent!
[INFO] Copying 1 resource
[INFO] Copying 7 resources
[INFO] Copying 2 resources
Downloading:
file:///Volumes/XXX_Dev/Maven/repository/com/package/xxx/XXX-Unit-Test/1.0-S
NAPSHOT/XXX-Unit-Test-1.0-SNAPSHOT.jar
[INFO] Unable to find resource
'com.package.xxx:XXX-Unit-Test:jar:1.0-SNAPSHOT' in repository internal
(file:///Volumes/XXX_Dev/Maven/repository)
Downloading:
http://repo2.maven.org/maven2/com/package/xxx/XXX-Unit-Test/1.0-SNAPSHOT/XXX
-Unit-Test-1.0-SNAPSHOT.jar
[INFO] Unable to find resource
'com.package.xxx:XXX-Unit-Test:jar:1.0-SNAPSHOT' in repository maven
(http://repo2.maven.org/maven2)
Downloading:
http://repository.jboss.org/maven2/com/package/xxx/XXX-Unit-Test/1.0-SNAPSHO
T/XXX-Unit-Test-1.0-SNAPSHOT.jar
[INFO] Unable to find resource
'com.package.xxx:XXX-Unit-Test:jar:1.0-SNAPSHOT' in repository JBoss
Repository (http://repository.jboss.org/maven2)
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to resolve artifact.
Missing:
--
1) com.package.xxx:XXX-Unit-Test:jar:1.0-SNAPSHOT
I hope you can help, as I have run out of ideas.
Thanks,
Paul Thomas
Re: Maven2 jsf-web project on Eclipse
For the web-part you probably need to configure the eclipse:eclipse goal with WTP-settings... Check the plugin-description on the exact settings. I've been using this plugin for almost 3 years now and i works like a charm... I have to admit though, I haven't used it in eclipse 3.5 or on TomCat, but that shouldn't be a real problem... On Thursday 17 September 2009 16:08, MavenZede wrote: > I have been trying to run a maven2 jsf project on Eclipse Galileo, but I > did not unfortunately. I tried a lot of ways, read thousands of web pages. > My first problem is that I cannot import my maven2 web project into > Eclipse. I know it should be happen when I run this mvn eclipse:eclipse, > however it doesnt. The eclipse project file (.project) already came after I > run above mentioned command, but again unfortunately this .project file > could not opened with eclipse. Some specification of system are ; > ---Apache tomcat 6.0 > ---myFaces 1.2.7 for jsf > ---Eclipse galileo (3.5 with WTP 3.1) -- Roland Asmann CFC Informationssysteme Entwicklungsgesellschaft m.b.H Bäckerstrasse 1/2/7 A-1010 Wien FN 266155f, Handelsgericht Wien Tel.: +43/1/513 88 77 - 27 Fax.: +43/1/513 88 62 Email: roland.asm...@cfc.at Web: www.cfc.at - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
help getting maven jetty plugin and jmx to work
I have tried to understand: http://wiki.eclipse.org/Jetty/Howto/Run_Jetty_with_JConsole But I do not have a jetty-jmx.xml that seems to work. I have tried this jetty-jmx.xml: http://blogs.exist.com/oching/2009/02/26/configuring-jsw-embedded-jetty-with-jmx/ But I get deployment errors with this configuration. I am now trying to find out hot to add an OPTION as per: *Jetty 7 requires -DOPTIONS=jmx to be used when starting up Jetty. That is, instead of the above, use this: java -DOPTIONS=jmx -jar start.jar etc/jetty-jmx.xml etc/jetty.xml * Any help would be greatly appreciated --- Thank You… Mick Knutson, President BASE Logic, Inc. Enterprise Architecture, Design, Mentoring & Agile Consulting p. (866) BLiNC-411: (254-6241-1) f. (415) 685-4233 Website: http://baselogic.com Linked IN: http://linkedin.com/in/mickknutson Vacation Rental: http://tahoe.baselogic.com ---
AW: mvn dependency:tree ends up in a nullpointer
Upppsss, sorry, I mean: > This is building fine and works as expected but > Sadly the version definition [1.0,) leads to a null pointer when I generate > the dependency:tree (mvn dependency:tree) Regards Matthias -Ursprüngliche Nachricht- Von: Vach, Matthias [mailto:matthias.v...@sap.com] Gesendet: Donnerstag, 17. September 2009 17:09 An: users@maven.apache.org Betreff: mvn dependency:tree ends up in a nullpointer Hi all, I need to define that any versions of javax.el:el-api are provided by my runtime system and must not be packed into my ear. To avoid excluding that artifact javax.el:el-api from each and every dependency where it is referenced, I defined it as explicit provided artefact: javax.el el-api [1.0,) provided This is building fine and works as expected but Sadly the version definition [1.0,) leads to an null pointer: [ERROR] FATAL ERROR [INFO] [INFO] version was null for javax.el:el-api [INFO] [INFO] Trace java.lang.NullPointerException: version was null for javax.el:el-api at org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:390) at org.apache.maven.artifact.DefaultArtifact.getId(DefaultArtifact.java:225) Can you give me the reason for that NPE? THX for your help, Regards Matthias - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
mvn dependency:tree ends up in a nullpointer
Hi all, I need to define that any versions of javax.el:el-api are provided by my runtime system and must not be packed into my ear. To avoid excluding that artifact javax.el:el-api from each and every dependency where it is referenced, I defined it as explicit provided artefact: javax.el el-api [1.0,) provided This is building fine and works as expected but Sadly the version definition [1.0,) leads to an null pointer: [ERROR] FATAL ERROR [INFO] [INFO] version was null for javax.el:el-api [INFO] [INFO] Trace java.lang.NullPointerException: version was null for javax.el:el-api at org.apache.maven.artifact.DefaultArtifact.getBaseVersion(DefaultArtifact.java:390) at org.apache.maven.artifact.DefaultArtifact.getId(DefaultArtifact.java:225) Can you give me the reason for that NPE? THX for your help, Regards Matthias
Re: Maven2 jsf-web project on Eclipse
install this plugin: http://m2eclipse.sonatype.org/update/ do some configuration, first of all set $M2_REPO classpath variable then open workspace and import maven2 projects by Import... -> Maven projects -> choose direcory with pom.xml -> Finish and wait pretty lng time for rebuilding Eclipse stuff :) good luck Martin Schayna MavenZede wrote: I have been trying to run a maven2 jsf project on Eclipse Galileo, but I did not unfortunately. I tried a lot of ways, read thousands of web pages. My first problem is that I cannot import my maven2 web project into Eclipse. I know it should be happen when I run this mvn eclipse:eclipse, however it doesnt. The eclipse project file (.project) already came after I run above mentioned command, but again unfortunately this .project file could not opened with eclipse. Some specification of system are ; ---Apache tomcat 6.0 ---myFaces 1.2.7 for jsf ---Eclipse galileo (3.5 with WTP 3.1) - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Plugin snapshot problem with Apache nexus repository
Hi, The snapshot url you are using and the stack trace you have could be very helpfull. 2009/9/17 Benson Margulies : > I set out to use a snapshot of the maven-release-plugin. I added the > snapshot repo to the pluginRepositories, with snapshots set to true. > > Then I called out version 2.0-beta-10-SNAPSHOT as my release. I got an error > message from maven to the effect that it could not find the jar file. > > So I changed the version to call out the full timestamp version number, and > it worked. > > is this the intended behavior? > -- Olivier - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Plugin snapshot problem with Apache nexus repository
I set out to use a snapshot of the maven-release-plugin. I added the snapshot repo to the pluginRepositories, with snapshots set to true. Then I called out version 2.0-beta-10-SNAPSHOT as my release. I got an error message from maven to the effect that it could not find the jar file. So I changed the version to call out the full timestamp version number, and it worked. is this the intended behavior?
Maven Central Compliance
Hi, I have a project with builds with Maven. My goal is to see my project on Central. There is a nice guide at http://maven.apache.org/guides/mini/guide-central-repository-upload.html which tells me the requirements. Is there any Report plugin out there, which would check all the requirements for Central? If there is no such Report plugin, where is the actual script which handles the verifications and handles the uploads. I cannot believe projects are checked manually. I have another problem, "Guide to uploading artifacts to the Central Repository" does not specify requirements for multi-module Maven projects. Many of the project's POM configurations are inherited by the modules of the project. It is unspecified by this guide, whether the modules POMs also need to specify those settings explicitly or not, in case the developers' intention is to release those on Central. I have made this questions also to http://jira.codehaus.org/browse/MNG-4362 Thanks, Al - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven2 jsf-web project on Eclipse
I have been trying to run a maven2 jsf project on Eclipse Galileo, but I did not unfortunately. I tried a lot of ways, read thousands of web pages. My first problem is that I cannot import my maven2 web project into Eclipse. I know it should be happen when I run this mvn eclipse:eclipse, however it doesnt. The eclipse project file (.project) already came after I run above mentioned command, but again unfortunately this .project file could not opened with eclipse. Some specification of system are ; ---Apache tomcat 6.0 ---myFaces 1.2.7 for jsf ---Eclipse galileo (3.5 with WTP 3.1) -- View this message in context: http://www.nabble.com/Maven2-jsf-web-project-on-Eclipse-tp25491909p25491909.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
AW: Maven2 jsf-web project on Eclipse
Have you tried m2eclipse? Best regards, Eric > -Ursprüngliche Nachricht- > Von: MavenZede [mailto:asiyeki...@gmail.com] > Gesendet: Donnerstag, 17. September 2009 16:11 > An: users@maven.apache.org > Betreff: Maven2 jsf-web project on Eclipse > > > I have been trying to run a maven2 jsf project on Eclipse > Galileo, but I did > not unfortunately. I tried a lot of ways, read thousands of > web pages. My > first problem is that I cannot import my maven2 web project > into Eclipse. I > know it should be happen when I run this mvn eclipse:eclipse, > however it > doesnt. The eclipse project file (.project) already came > after I run above > mentioned command, but again unfortunately this .project file > could not > opened with eclipse. Some specification of system are ; > ---Apache tomcat 6.0 > ---myFaces 1.2.7 for jsf > ---Eclipse galileo (3.5 with WTP 3.1) > > > -- > View this message in context: > http://www.nabble.com/Maven2-jsf-web-project-on-Eclipse-tp2549 > 1908p25491908.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 > > - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven2 jsf-web project on Eclipse
I have been trying to run a maven2 jsf project on Eclipse Galileo, but I did not unfortunately. I tried a lot of ways, read thousands of web pages. My first problem is that I cannot import my maven2 web project into Eclipse. I know it should be happen when I run this mvn eclipse:eclipse, however it doesnt. The eclipse project file (.project) already came after I run above mentioned command, but again unfortunately this .project file could not opened with eclipse. Some specification of system are ; ---Apache tomcat 6.0 ---myFaces 1.2.7 for jsf ---Eclipse galileo (3.5 with WTP 3.1) -- View this message in context: http://www.nabble.com/Maven2-jsf-web-project-on-Eclipse-tp25491908p25491908.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: War packaged in ear. How to exclude shared jars
I just went through this a couple of weeks ago, and here's how we're currently doing it at work. The ear project includes the war project twice, once as a war, once as a POM. The war plugin is set to include only the struts-tiles.jar and struts-taglibs.jar in the WEB-INF/lib. At home, I've been playing with the maven plugin for Netbeans, and do things a little differently. I added all of the shared dependencies to the parent POM. The ear and war projects both inherit the dependencies and as above, the war plugin is set to include only certain jar files. Both seem to work equally well. Personally, I think I like the parent POM approach, adding a project as a dependency twice seems a bit hackerish to me. I welcome any comments on why one approach might be better than the other, since I'm still learning. Thanks, Dave --- There are 10 types of people in the world, those that understand binary, and those that don't. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven2 jsf-web project on Eclipse
I have been trying to run a maven2 jsf project on Eclipse Galileo, but I did not unfortunately. I tried a lot of ways, read thousands of web pages. My first problem is that I cannot import my maven2 web project into Eclipse. I know it should be happen when I run this mvn eclipse:eclipse, however it doesnt. The eclipse project file (.project) already came after I run above mentioned command, but again unfortunately this .project file could not opened with eclipse. Some specification of system are ; ---Apache tomcat 6.0 ---myFaces 1.2.7 for jsf ---Eclipse galileo (3.5 with WTP 3.1) -- View this message in context: http://www.nabble.com/Maven2-jsf-web-project-on-Eclipse-tp25491907p25491907.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: Failing to Fetch Snapshots with Every Build - How to disable undesired Behaviour
Just an update. I rebuilt OpenEJB and Geronimo, and it took away all those errors except the ones for openejb-core. It seems they didn't build that snapshot? Though that's not the point. I have, however, found the reason for this happening. It seems it is what I suspected, in that it tries to update those pom/jar files, fails because it can't them, and thus leaves them alone. Next time it tries again. So I am able to fix this by simply "touch"ing the files, thus updating their modification dates. I'll just keep doing this until later this month when these libraries are released, and thus they can be updated properly. Just though I'd let everyone know, in case someone else suffers the same. Q On Wed, Sep 16, 2009 at 5:25 PM, Edelson, Justin wrote: > See http://maven.apache.org/repository-management.html > > > > From: Quintin Beukes [mailto:quin...@skywalk.co.za] > Sent: Wed 9/16/2009 11:20 AM > To: Maven Users List > Subject: Re: Failing to Fetch Snapshots with Every Build - How to disable > undesired Behaviour > > > > Sounds good. > > How does it help you to "hit the internet" less often? > > Q > > On Wed, Sep 16, 2009 at 4:48 PM, Todd Thiessen wrote: >> BTW. Are you using a repository manager? This would keep you from having to >> hit the internet often and improve download speeds. >> >> --- >> Todd Thiessen >> >> >>> -Original Message- >>> From: Quintin Beukes [mailto:quin...@skywalk.co.za] >>> Sent: Wednesday, September 16, 2009 10:41 AM >>> To: Maven Users List >>> Subject: Re: Failing to Fetch Snapshots with Every Build - >>> How to disable undesired Behaviour >>> >>> Nuking it?!?! You mean delete all 1GB of it and start over? >>> Or can I just delete the SNAPSHOT directory and rebuild it? >>> >>> Q >>> >>> On Wed, Sep 16, 2009 at 4:37 PM, Todd Thiessen >>> wrote: >>> > Perhaps the metadata is corrupt. Have you tried nuking your local? >>> > >>> > If that doesn't work, perhaps there is corruption on the >>> java.net side >>> > >>> > --- >>> > Todd Thiessen >>> > >>> > >>> >> -Original Message- >>> >> From: Quintin Beukes [mailto:quin...@skywalk.co.za] >>> >> Sent: Wednesday, September 16, 2009 10:31 AM >>> >> To: Maven Users List >>> >> Subject: Re: Failing to Fetch Snapshots with Every Build - How to >>> >> disable undesired Behaviour >>> >> >>> >> Could it be because it's a snapshot, the file isn't there, >>> and since >>> >> it keeps NOT being found it never marks it as updated, and >>> thus keeps >>> >> trying. >>> >> >>> >> Q >>> >> >>> >> On Wed, Sep 16, 2009 at 4:27 PM, Quintin Beukes >>> >> wrote: >>> >> > No. I even tried to disable checking for updates. It keeps >>> >> doing this >>> >> > with every build. The exact same set of files. >>> >> > >>> >> > Q >>> >> > >>> >> > On Wed, Sep 16, 2009 at 2:37 PM, Edelson, Justin >>> >> > wrote: >>> >> >> By default, Maven will only check for updated snapshots >>> >> once per day. >>> >> >> Are you overriding this in the settings.xml file? >>> >> >> >>> >> >> Justin >>> >> >> >>> >> >> On Sep 16, 2009, at 4:09 AM, "Quintin Beukes" >>> >> wrote: >>> >> >> >>> >> >>> Everytime I build I get the following (and a couple of others, >>> >> >>> including JARs, but all for the same project, ie. >>> >> >>> openejb-3.1.2-SNAPSHOT). >>> >> >>> >>> >> >>> [resources:resources] >>> >> >>> [WARNING] Using platform encoding (UTF-8 actually) to >>> >> copy filtered >>> >> >>> resources, i.e. build is platform dependent! >>> >> >>> Copying 5 resources >>> >> >>> Downloading: >>> >> >>> >>> >> >>> http://download.java.net/maven/2/org/apache/openejb/openejb-client/3 >>> >> >>> .1.2-SNAPSHOT/openejb-client-3.1.2-SNAPSHOT.pom >>> >> >>> Unable to find resource >>> >> >>> 'org.apache.openejb:openejb-client:pom:3.1.2-SNAPSHOT' in >>> >> repository >>> >> >>> java.net2 (http://download.java.net/maven/2) >>> >> >>> Downloading: >>> >> >>> >>> >> >>> http://download.java.net/maven/2/org/apache/openejb/server/3.1.2-SNA >>> >> >>> PSHOT/server-3.1.2-SNAPSHOT.pom Unable to find resource >>> >> >>> 'org.apache.openejb:server:pom:3.1.2-SNAPSHOT' >>> >> >>> in repository java.net2 (http://download.java.net/maven/2) >>> >> >>> Downloading: >>> >> >>> >>> >> >>> http://download.java.net/maven/2/org/apache/openejb/openejb/3.1.2-SN >>> >> >>> APSHOT/openejb-3.1.2-SNAPSHOT.pom Unable to find resource >>> >> >>> 'org.apache.openejb:openejb:pom:3.1.2-SNAPSHOT' in repository >>> >> >>> java.net2 (http://download.java.net/maven/2) >>> >> >>> snapshot >>> org.apache.openejb:openejb-core:3.1.2-SNAPSHOT: checking >>> >> >>> for updates from java.net2 >>> >> >>> Downloading: >>> >> >>> >>> >> >>> http://download.java.net/maven/2/org/apache/openejb/openejb-core/3.1 >>> >> >>> .2-SNAPSHOT/openejb-core-3.1.2-SNAPSHOT.pom >>> >> >>> Unable to find resource >>> >> >>> 'org.apache.openejb:openejb-core:pom:3.1.2-SNAPSHOT' in >>> >> >>> repository >>> >> >>> java.net2 (http://download.java.net/maven/2) >>> >> >>> Downloading: >>> >> >>> >>> >
Re: only one artifact per project
The basic idea with Maven is that one Maven project produces one artifact. An artifact could be a jar file, a war file, a zip file, or pretty much anything. There are possibilities to force Maven to produce more than one artifact though. Normally that's not the right road, but it's your choice. This is different from normal usage with Ant where you often have an ant script producing, for instance, several jar files, war file(s) and the ear including these. It's just a different mind set. You just have more "projects". I think it is good, because it encourages a better design and you'll easier find circular dependencies between jars/libraries. /Anders On Thu, Sep 17, 2009 at 11:46, Sammaiah Nagapuri wrote: > Hi all, > > I am not getting what it means the following statement. Is it really > disadvantage from maven. Can anybody explain me with ant? > > The restriction imposed by Maven is that only one artifact is generated per > project (A project in Maven terminology is a folder with a project.xml file > in it). > > > Thanks & Regards > Sammaiah Nagapuri > P We have a responsibility to the environment > Before printing this e-mail or any other document, let's ask ourselves > whether we need a hard copy > > > DISCLAIMER: > > --- > > The contents of this e-mail and any attachment(s) are confidential and > intended for the named recipient(s) only. > It shall not attach any liability on the originator or HCL or its > affiliates. Any views or opinions presented in > this email are solely those of the author and may not necessarily reflect > the opinions of HCL or its affiliates. > Any form of reproduction, dissemination, copying, disclosure, modification, > distribution and / or publication of > this message without the prior written consent of the author of this e-mail > is strictly prohibited. If you have > received this email in error please delete it and notify the sender > immediately. Before opening any mail and > attachments please check them for viruses and defect. > > > --- >
Re: Moving Repository
Yes. That's what I wanted to confirm. Thanks. Q On Thu, Sep 17, 2009 at 11:53 AM, Juven Xu wrote: > your local repository is _~/.m2/repository/_, while the file > _~/.m2/settings.xml_ is user specific maven settings > > you will want to move the repository, while you won't want to move the > settings, and you can configure the settings to point at the new repository > location > > or did I misunderstand you? > > On Thu, Sep 17, 2009 at 5:37 PM, Quintin Beukes wrote: > >> It's ~/.m2/repository I want to move. So I'm asking if it's save to >> move the existing directory away, or does it have metadata somewhere >> that fixes it in place, meaning a new location would have to start >> from scratch (I'm referring to the possibility of having absolute >> paths perhaps?). >> >> I just want to be sure, in case I corrupt it and have to start over. >> >> Q >> >> On Thu, Sep 17, 2009 at 9:59 AM, Juven Xu wrote: >> > yep, you can edit your ~/.m2/settings.xml to point the local maven repo >> to >> > any FS place. >> > >> > On Thu, Sep 17, 2009 at 3:31 PM, Quintin Beukes >> wrote: >> > >> >> Hey, >> >> >> >> I have a very large repository and would like to keep it (not start >> >> over). Though, I would like to move it to a more "official" location >> >> on my PC. >> >> >> >> I am planning to install a repository manager next week, but I still >> >> want my local repository in a better place. This is mostly so I can >> >> reference the JARs in there in non-maven projects. Can I just rename >> >> it and change my maven settings, or is there anything else? >> >> >> >> -- >> >> Quintin Beukes >> >> >> >> - >> >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> >> For additional commands, e-mail: users-h...@maven.apache.org >> >> >> >> >> > >> > >> > -- >> > - juven >> > >> >> >> >> -- >> Quintin Beukes >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> > > > -- > - juven > -- Quintin Beukes - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Moving Repository
your local repository is _~/.m2/repository/_, while the file _~/.m2/settings.xml_ is user specific maven settings you will want to move the repository, while you won't want to move the settings, and you can configure the settings to point at the new repository location or did I misunderstand you? On Thu, Sep 17, 2009 at 5:37 PM, Quintin Beukes wrote: > It's ~/.m2/repository I want to move. So I'm asking if it's save to > move the existing directory away, or does it have metadata somewhere > that fixes it in place, meaning a new location would have to start > from scratch (I'm referring to the possibility of having absolute > paths perhaps?). > > I just want to be sure, in case I corrupt it and have to start over. > > Q > > On Thu, Sep 17, 2009 at 9:59 AM, Juven Xu wrote: > > yep, you can edit your ~/.m2/settings.xml to point the local maven repo > to > > any FS place. > > > > On Thu, Sep 17, 2009 at 3:31 PM, Quintin Beukes > wrote: > > > >> Hey, > >> > >> I have a very large repository and would like to keep it (not start > >> over). Though, I would like to move it to a more "official" location > >> on my PC. > >> > >> I am planning to install a repository manager next week, but I still > >> want my local repository in a better place. This is mostly so I can > >> reference the JARs in there in non-maven projects. Can I just rename > >> it and change my maven settings, or is there anything else? > >> > >> -- > >> Quintin Beukes > >> > >> - > >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > >> For additional commands, e-mail: users-h...@maven.apache.org > >> > >> > > > > > > -- > > - juven > > > > > > -- > Quintin Beukes > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- - juven
only one artifact per project
Hi all, I am not getting what it means the following statement. Is it really disadvantage from maven. Can anybody explain me with ant? The restriction imposed by Maven is that only one artifact is generated per project (A project in Maven terminology is a folder with a project.xml file in it). Thanks & Regards Sammaiah Nagapuri P We have a responsibility to the environment Before printing this e-mail or any other document, let's ask ourselves whether we need a hard copy DISCLAIMER: --- The contents of this e-mail and any attachment(s) are confidential and intended for the named recipient(s) only. It shall not attach any liability on the originator or HCL or its affiliates. Any views or opinions presented in this email are solely those of the author and may not necessarily reflect the opinions of HCL or its affiliates. Any form of reproduction, dissemination, copying, disclosure, modification, distribution and / or publication of this message without the prior written consent of the author of this e-mail is strictly prohibited. If you have received this email in error please delete it and notify the sender immediately. Before opening any mail and attachments please check them for viruses and defect. ---
Re: Moving Repository
It's ~/.m2/repository I want to move. So I'm asking if it's save to move the existing directory away, or does it have metadata somewhere that fixes it in place, meaning a new location would have to start from scratch (I'm referring to the possibility of having absolute paths perhaps?). I just want to be sure, in case I corrupt it and have to start over. Q On Thu, Sep 17, 2009 at 9:59 AM, Juven Xu wrote: > yep, you can edit your ~/.m2/settings.xml to point the local maven repo to > any FS place. > > On Thu, Sep 17, 2009 at 3:31 PM, Quintin Beukes wrote: > >> Hey, >> >> I have a very large repository and would like to keep it (not start >> over). Though, I would like to move it to a more "official" location >> on my PC. >> >> I am planning to install a repository manager next week, but I still >> want my local repository in a better place. This is mostly so I can >> reference the JARs in there in non-maven projects. Can I just rename >> it and change my maven settings, or is there anything else? >> >> -- >> Quintin Beukes >> >> - >> To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> For additional commands, e-mail: users-h...@maven.apache.org >> >> > > > -- > - juven > -- Quintin Beukes - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: AW: How to specify a plugin version from the command line?
Or create a default pom in your home directory and call 'mvn -F ~/pom.xml' or put this in a script. Hth, Nick Stolwijk ~Java Developer~ IPROFS BV. Claus Sluterweg 125 2012 WS Haarlem http://www.iprofs.nl On Thu, Sep 17, 2009 at 10:53 AM, Stephen Connolly wrote: > you could just create a throwaway pom.xml in your working directory > and that will be consulted > > 2009/9/17 Lewis, Eric : >> Ok, but this doesn't work when I use install:install-file, because that POM >> I'm using is not under my control. >> So in this case I have to fully qualify the plugin including the version, >> right? >> >> Best regards, >> Eric >> >>> -Ursprüngliche Nachricht- >>> Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] >>> Gesendet: Donnerstag, 17. September 2009 10:44 >>> An: Maven Users List >>> Betreff: Re: AW: How to specify a plugin version from the >>> command line? >>> >>> plugin management of current pom or any of its parents >>> >>> 2009/9/17 Lewis, Eric : >>> > Ok, that's no problem, but can I specify somewhere that >>> Maven should at least take version x for plugin y? >>> > >>> > Best regards, >>> > Eric >>> > >>> >> -Ursprüngliche Nachricht- >>> >> Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] >>> >> Gesendet: Donnerstag, 17. September 2009 10:41 >>> >> An: Maven Users List >>> >> Betreff: Re: AW: How to specify a plugin version from the >>> >> command line? >>> >> >>> >> version ranges are not supported for plugins >>> >> >>> >> 2009/9/17 Lewis, Eric : >>> >> > Hmmm... >>> >> > >>> >> > This works: >>> >> > mvn org.apache.maven.plugins:maven-help-plugin:2.1:describe >>> >> -Dplugin=help >>> >> > >>> >> > This doesn't work: >>> >> > mvn >>> >> org.apache.maven.plugins:maven-help-plugin:[1.0,2.1):describe >>> >> -Dplugin=help >>> >> > >>> >> > Best regards, >>> >> > Eric >>> >> > >>> >> >> -Ursprüngliche Nachricht- >>> >> >> Von: Martin Gainty [mailto:mgai...@hotmail.com] >>> >> >> Gesendet: Mittwoch, 16. September 2009 17:36 >>> >> >> An: users@maven.apache.org >>> >> >> Betreff: RE: AW: How to specify a plugin version from the >>> >> >> command line? >>> >> >> >>> >> >> >>> >> >> try [1.0,2.0) >>> >> >> >>> >> >> version 1.0 <= x < 2.0 inclusive >>> >> >> >>> >> >> http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+an >>> >> >> d+Conflict+Resolution#DependencyMediationandConflictResolution >>> >> >> -DependencyVersionRanges >>> >> >> >>> >> >> Martin Gainty >>> >> >> __ >>> >> >> 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: eric.le...@ipi.ch >>> >> >> > To: users@maven.apache.org >>> >> >> > Date: Wed, 16 Sep 2009 17:25:33 +0200 >>> >> >> > Subject: AW: How to specify a plugin version from the >>> >> command line? >>> >> >> > >>> >> >> > Hi Martin >>> >> >> > >>> >> >> > Thanks, that works. >>> >> >> > >>> >> >> > However, it's not really elegant ;-) >>> >> >> > >>> >> >> > Is there a way to nail the plugin versions somewhere in the >>> >> >> configuration? If possible with version ranges, like [2.3) >>> >> >> > >>> >> >> > Best regards, >>> >> >> > Eric >>> >> >> > >>> >> >> > > -Ursprüngliche Nachricht- >>> >> >> > > Von: Martin Gainty [mailto:mgai...@hotmail.com] >>> >> >> > > Gesendet: Mittwoch, 16. September 2009 17:21 >>> >> >> > > An: users@maven.apache.org >>> >> >> > > Betreff: RE: How to specify a plugin version from the >>> >> >> command line? >>> >> >> > > >>> >> >> > > >>> >> >> > > Eric >>> >> >> > > >>> >> >> > > did you try running mvn with groupId:artifactId:version:goal >>> >> >> > > at command line e.g. >>> >> >> > > mvn >>> >> >> > > >>> PlugIngroupID:PlugInartifactID:PlugInversion:goalhttp://maven. >>> >> >> > > apache.org/guides/plugin/guide-java-plugin-development.html >>> >> >> > > Martin Gainty >>> >> >> > >
Re: AW: How to specify a plugin version from the command line?
you could just create a throwaway pom.xml in your working directory and that will be consulted 2009/9/17 Lewis, Eric : > Ok, but this doesn't work when I use install:install-file, because that POM > I'm using is not under my control. > So in this case I have to fully qualify the plugin including the version, > right? > > Best regards, > Eric > >> -Ursprüngliche Nachricht- >> Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] >> Gesendet: Donnerstag, 17. September 2009 10:44 >> An: Maven Users List >> Betreff: Re: AW: How to specify a plugin version from the >> command line? >> >> plugin management of current pom or any of its parents >> >> 2009/9/17 Lewis, Eric : >> > Ok, that's no problem, but can I specify somewhere that >> Maven should at least take version x for plugin y? >> > >> > Best regards, >> > Eric >> > >> >> -Ursprüngliche Nachricht- >> >> Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] >> >> Gesendet: Donnerstag, 17. September 2009 10:41 >> >> An: Maven Users List >> >> Betreff: Re: AW: How to specify a plugin version from the >> >> command line? >> >> >> >> version ranges are not supported for plugins >> >> >> >> 2009/9/17 Lewis, Eric : >> >> > Hmmm... >> >> > >> >> > This works: >> >> > mvn org.apache.maven.plugins:maven-help-plugin:2.1:describe >> >> -Dplugin=help >> >> > >> >> > This doesn't work: >> >> > mvn >> >> org.apache.maven.plugins:maven-help-plugin:[1.0,2.1):describe >> >> -Dplugin=help >> >> > >> >> > Best regards, >> >> > Eric >> >> > >> >> >> -Ursprüngliche Nachricht- >> >> >> Von: Martin Gainty [mailto:mgai...@hotmail.com] >> >> >> Gesendet: Mittwoch, 16. September 2009 17:36 >> >> >> An: users@maven.apache.org >> >> >> Betreff: RE: AW: How to specify a plugin version from the >> >> >> command line? >> >> >> >> >> >> >> >> >> try [1.0,2.0) >> >> >> >> >> >> version 1.0 <= x < 2.0 inclusive >> >> >> >> >> >> http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+an >> >> >> d+Conflict+Resolution#DependencyMediationandConflictResolution >> >> >> -DependencyVersionRanges >> >> >> >> >> >> Martin Gainty >> >> >> __ >> >> >> 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: eric.le...@ipi.ch >> >> >> > To: users@maven.apache.org >> >> >> > Date: Wed, 16 Sep 2009 17:25:33 +0200 >> >> >> > Subject: AW: How to specify a plugin version from the >> >> command line? >> >> >> > >> >> >> > Hi Martin >> >> >> > >> >> >> > Thanks, that works. >> >> >> > >> >> >> > However, it's not really elegant ;-) >> >> >> > >> >> >> > Is there a way to nail the plugin versions somewhere in the >> >> >> configuration? If possible with version ranges, like [2.3) >> >> >> > >> >> >> > Best regards, >> >> >> > Eric >> >> >> > >> >> >> > > -Ursprüngliche Nachricht- >> >> >> > > Von: Martin Gainty [mailto:mgai...@hotmail.com] >> >> >> > > Gesendet: Mittwoch, 16. September 2009 17:21 >> >> >> > > An: users@maven.apache.org >> >> >> > > Betreff: RE: How to specify a plugin version from the >> >> >> command line? >> >> >> > > >> >> >> > > >> >> >> > > Eric >> >> >> > > >> >> >> > > did you try running mvn with groupId:artifactId:version:goal >> >> >> > > at command line e.g. >> >> >> > > mvn >> >> >> > > >> PlugIngroupID:PlugInartifactID:PlugInversion:goalhttp://maven. >> >> >> > > apache.org/guides/plugin/guide-java-plugin-development.html >> >> >> > > Martin Gainty >> >> >> > > __ >> >> >> > > 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 unzu
AW: AW: How to specify a plugin version from the command line?
Ok, but this doesn't work when I use install:install-file, because that POM I'm using is not under my control. So in this case I have to fully qualify the plugin including the version, right? Best regards, Eric > -Ursprüngliche Nachricht- > Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] > Gesendet: Donnerstag, 17. September 2009 10:44 > An: Maven Users List > Betreff: Re: AW: How to specify a plugin version from the > command line? > > plugin management of current pom or any of its parents > > 2009/9/17 Lewis, Eric : > > Ok, that's no problem, but can I specify somewhere that > Maven should at least take version x for plugin y? > > > > Best regards, > > Eric > > > >> -Ursprüngliche Nachricht- > >> Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] > >> Gesendet: Donnerstag, 17. September 2009 10:41 > >> An: Maven Users List > >> Betreff: Re: AW: How to specify a plugin version from the > >> command line? > >> > >> version ranges are not supported for plugins > >> > >> 2009/9/17 Lewis, Eric : > >> > Hmmm... > >> > > >> > This works: > >> > mvn org.apache.maven.plugins:maven-help-plugin:2.1:describe > >> -Dplugin=help > >> > > >> > This doesn't work: > >> > mvn > >> org.apache.maven.plugins:maven-help-plugin:[1.0,2.1):describe > >> -Dplugin=help > >> > > >> > Best regards, > >> > Eric > >> > > >> >> -Ursprüngliche Nachricht- > >> >> Von: Martin Gainty [mailto:mgai...@hotmail.com] > >> >> Gesendet: Mittwoch, 16. September 2009 17:36 > >> >> An: users@maven.apache.org > >> >> Betreff: RE: AW: How to specify a plugin version from the > >> >> command line? > >> >> > >> >> > >> >> try [1.0,2.0) > >> >> > >> >> version 1.0 <= x < 2.0 inclusive > >> >> > >> >> http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+an > >> >> d+Conflict+Resolution#DependencyMediationandConflictResolution > >> >> -DependencyVersionRanges > >> >> > >> >> Martin Gainty > >> >> __ > >> >> 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: eric.le...@ipi.ch > >> >> > To: users@maven.apache.org > >> >> > Date: Wed, 16 Sep 2009 17:25:33 +0200 > >> >> > Subject: AW: How to specify a plugin version from the > >> command line? > >> >> > > >> >> > Hi Martin > >> >> > > >> >> > Thanks, that works. > >> >> > > >> >> > However, it's not really elegant ;-) > >> >> > > >> >> > Is there a way to nail the plugin versions somewhere in the > >> >> configuration? If possible with version ranges, like [2.3) > >> >> > > >> >> > Best regards, > >> >> > Eric > >> >> > > >> >> > > -Ursprüngliche Nachricht- > >> >> > > Von: Martin Gainty [mailto:mgai...@hotmail.com] > >> >> > > Gesendet: Mittwoch, 16. September 2009 17:21 > >> >> > > An: users@maven.apache.org > >> >> > > Betreff: RE: How to specify a plugin version from the > >> >> command line? > >> >> > > > >> >> > > > >> >> > > Eric > >> >> > > > >> >> > > did you try running mvn with groupId:artifactId:version:goal > >> >> > > at command line e.g. > >> >> > > mvn > >> >> > > > PlugIngroupID:PlugInartifactID:PlugInversion:goalhttp://maven. > >> >> > > apache.org/guides/plugin/guide-java-plugin-development.html > >> >> > > Martin Gainty > >> >> > > __ > >> >> > > 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
Re: AW: How to specify a plugin version from the command line?
plugin management of current pom or any of its parents 2009/9/17 Lewis, Eric : > Ok, that's no problem, but can I specify somewhere that Maven should at least > take version x for plugin y? > > Best regards, > Eric > >> -Ursprüngliche Nachricht- >> Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] >> Gesendet: Donnerstag, 17. September 2009 10:41 >> An: Maven Users List >> Betreff: Re: AW: How to specify a plugin version from the >> command line? >> >> version ranges are not supported for plugins >> >> 2009/9/17 Lewis, Eric : >> > Hmmm... >> > >> > This works: >> > mvn org.apache.maven.plugins:maven-help-plugin:2.1:describe >> -Dplugin=help >> > >> > This doesn't work: >> > mvn >> org.apache.maven.plugins:maven-help-plugin:[1.0,2.1):describe >> -Dplugin=help >> > >> > Best regards, >> > Eric >> > >> >> -Ursprüngliche Nachricht- >> >> Von: Martin Gainty [mailto:mgai...@hotmail.com] >> >> Gesendet: Mittwoch, 16. September 2009 17:36 >> >> An: users@maven.apache.org >> >> Betreff: RE: AW: How to specify a plugin version from the >> >> command line? >> >> >> >> >> >> try [1.0,2.0) >> >> >> >> version 1.0 <= x < 2.0 inclusive >> >> >> >> http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+an >> >> d+Conflict+Resolution#DependencyMediationandConflictResolution >> >> -DependencyVersionRanges >> >> >> >> Martin Gainty >> >> __ >> >> 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: eric.le...@ipi.ch >> >> > To: users@maven.apache.org >> >> > Date: Wed, 16 Sep 2009 17:25:33 +0200 >> >> > Subject: AW: How to specify a plugin version from the >> command line? >> >> > >> >> > Hi Martin >> >> > >> >> > Thanks, that works. >> >> > >> >> > However, it's not really elegant ;-) >> >> > >> >> > Is there a way to nail the plugin versions somewhere in the >> >> configuration? If possible with version ranges, like [2.3) >> >> > >> >> > Best regards, >> >> > Eric >> >> > >> >> > > -Ursprüngliche Nachricht- >> >> > > Von: Martin Gainty [mailto:mgai...@hotmail.com] >> >> > > Gesendet: Mittwoch, 16. September 2009 17:21 >> >> > > An: users@maven.apache.org >> >> > > Betreff: RE: How to specify a plugin version from the >> >> command line? >> >> > > >> >> > > >> >> > > Eric >> >> > > >> >> > > did you try running mvn with groupId:artifactId:version:goal >> >> > > at command line e.g. >> >> > > mvn >> >> > > PlugIngroupID:PlugInartifactID:PlugInversion:goalhttp://maven. >> >> > > apache.org/guides/plugin/guide-java-plugin-development.html >> >> > > Martin Gainty >> >> > > __ >> >> > > 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: eric.le...@ipi.ch >> >> > > > To: users@maven.apache.org >>
AW: AW: How to specify a plugin version from the command line?
Ok, that's no problem, but can I specify somewhere that Maven should at least take version x for plugin y? Best regards, Eric > -Ursprüngliche Nachricht- > Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] > Gesendet: Donnerstag, 17. September 2009 10:41 > An: Maven Users List > Betreff: Re: AW: How to specify a plugin version from the > command line? > > version ranges are not supported for plugins > > 2009/9/17 Lewis, Eric : > > Hmmm... > > > > This works: > > mvn org.apache.maven.plugins:maven-help-plugin:2.1:describe > -Dplugin=help > > > > This doesn't work: > > mvn > org.apache.maven.plugins:maven-help-plugin:[1.0,2.1):describe > -Dplugin=help > > > > Best regards, > > Eric > > > >> -Ursprüngliche Nachricht- > >> Von: Martin Gainty [mailto:mgai...@hotmail.com] > >> Gesendet: Mittwoch, 16. September 2009 17:36 > >> An: users@maven.apache.org > >> Betreff: RE: AW: How to specify a plugin version from the > >> command line? > >> > >> > >> try [1.0,2.0) > >> > >> version 1.0 <= x < 2.0 inclusive > >> > >> http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+an > >> d+Conflict+Resolution#DependencyMediationandConflictResolution > >> -DependencyVersionRanges > >> > >> Martin Gainty > >> __ > >> 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: eric.le...@ipi.ch > >> > To: users@maven.apache.org > >> > Date: Wed, 16 Sep 2009 17:25:33 +0200 > >> > Subject: AW: How to specify a plugin version from the > command line? > >> > > >> > Hi Martin > >> > > >> > Thanks, that works. > >> > > >> > However, it's not really elegant ;-) > >> > > >> > Is there a way to nail the plugin versions somewhere in the > >> configuration? If possible with version ranges, like [2.3) > >> > > >> > Best regards, > >> > Eric > >> > > >> > > -Ursprüngliche Nachricht- > >> > > Von: Martin Gainty [mailto:mgai...@hotmail.com] > >> > > Gesendet: Mittwoch, 16. September 2009 17:21 > >> > > An: users@maven.apache.org > >> > > Betreff: RE: How to specify a plugin version from the > >> command line? > >> > > > >> > > > >> > > Eric > >> > > > >> > > did you try running mvn with groupId:artifactId:version:goal > >> > > at command line e.g. > >> > > mvn > >> > > PlugIngroupID:PlugInartifactID:PlugInversion:goalhttp://maven. > >> > > apache.org/guides/plugin/guide-java-plugin-development.html > >> > > Martin Gainty > >> > > __ > >> > > 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: eric.le...@ipi.ch > >> > > > To: users@maven.apache.org > >> > > > Date: Wed, 16 Sep 2009 17:11:46 +0200 > >> > > > Subject: How to specify a plugin version from the > command line? > >> > > > > >> > > > Hi > >> > > > > >> > > > I'm setting the exact versions for
Re: AW: How to specify a plugin version from the command line?
version ranges are not supported for plugins 2009/9/17 Lewis, Eric : > Hmmm... > > This works: > mvn org.apache.maven.plugins:maven-help-plugin:2.1:describe -Dplugin=help > > This doesn't work: > mvn org.apache.maven.plugins:maven-help-plugin:[1.0,2.1):describe > -Dplugin=help > > Best regards, > Eric > >> -Ursprüngliche Nachricht- >> Von: Martin Gainty [mailto:mgai...@hotmail.com] >> Gesendet: Mittwoch, 16. September 2009 17:36 >> An: users@maven.apache.org >> Betreff: RE: AW: How to specify a plugin version from the >> command line? >> >> >> try [1.0,2.0) >> >> version 1.0 <= x < 2.0 inclusive >> >> http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+an >> d+Conflict+Resolution#DependencyMediationandConflictResolution >> -DependencyVersionRanges >> >> Martin Gainty >> __ >> 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: eric.le...@ipi.ch >> > To: users@maven.apache.org >> > Date: Wed, 16 Sep 2009 17:25:33 +0200 >> > Subject: AW: How to specify a plugin version from the command line? >> > >> > Hi Martin >> > >> > Thanks, that works. >> > >> > However, it's not really elegant ;-) >> > >> > Is there a way to nail the plugin versions somewhere in the >> configuration? If possible with version ranges, like [2.3) >> > >> > Best regards, >> > Eric >> > >> > > -Ursprüngliche Nachricht- >> > > Von: Martin Gainty [mailto:mgai...@hotmail.com] >> > > Gesendet: Mittwoch, 16. September 2009 17:21 >> > > An: users@maven.apache.org >> > > Betreff: RE: How to specify a plugin version from the >> command line? >> > > >> > > >> > > Eric >> > > >> > > did you try running mvn with groupId:artifactId:version:goal >> > > at command line e.g. >> > > mvn >> > > PlugIngroupID:PlugInartifactID:PlugInversion:goalhttp://maven. >> > > apache.org/guides/plugin/guide-java-plugin-development.html >> > > Martin Gainty >> > > __ >> > > 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: eric.le...@ipi.ch >> > > > To: users@maven.apache.org >> > > > Date: Wed, 16 Sep 2009 17:11:46 +0200 >> > > > Subject: How to specify a plugin version from the command line? >> > > > >> > > > Hi >> > > > >> > > > I'm setting the exact versions for all Maven plugins in our >> > > company-wide parent POM. >> > > > However, that doesn't help when I'm using the command line. >> > > > So how can I force Maven to use a certain version of a plugin? >> > > > >> > > > Best regards, >> > > > Eric >> > > > >> > > >> - >> > > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org >> > > > For additional commands, e-mail: users-h...@maven.apache.org >> > > > >> > > >> > > _ >> > > Hotmail: Free, trusted and rich email service. >> > > http://clk.atdm
AW: AW: How to specify a plugin version from the command line?
Hmmm... This works: mvn org.apache.maven.plugins:maven-help-plugin:2.1:describe -Dplugin=help This doesn't work: mvn org.apache.maven.plugins:maven-help-plugin:[1.0,2.1):describe -Dplugin=help Best regards, Eric > -Ursprüngliche Nachricht- > Von: Martin Gainty [mailto:mgai...@hotmail.com] > Gesendet: Mittwoch, 16. September 2009 17:36 > An: users@maven.apache.org > Betreff: RE: AW: How to specify a plugin version from the > command line? > > > try [1.0,2.0) > > version 1.0 <= x < 2.0 inclusive > > http://docs.codehaus.org/display/MAVEN/Dependency+Mediation+an > d+Conflict+Resolution#DependencyMediationandConflictResolution > -DependencyVersionRanges > > Martin Gainty > __ > 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: eric.le...@ipi.ch > > To: users@maven.apache.org > > Date: Wed, 16 Sep 2009 17:25:33 +0200 > > Subject: AW: How to specify a plugin version from the command line? > > > > Hi Martin > > > > Thanks, that works. > > > > However, it's not really elegant ;-) > > > > Is there a way to nail the plugin versions somewhere in the > configuration? If possible with version ranges, like [2.3) > > > > Best regards, > > Eric > > > > > -Ursprüngliche Nachricht- > > > Von: Martin Gainty [mailto:mgai...@hotmail.com] > > > Gesendet: Mittwoch, 16. September 2009 17:21 > > > An: users@maven.apache.org > > > Betreff: RE: How to specify a plugin version from the > command line? > > > > > > > > > Eric > > > > > > did you try running mvn with groupId:artifactId:version:goal > > > at command line e.g. > > > mvn > > > PlugIngroupID:PlugInartifactID:PlugInversion:goalhttp://maven. > > > apache.org/guides/plugin/guide-java-plugin-development.html > > > Martin Gainty > > > __ > > > 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: eric.le...@ipi.ch > > > > To: users@maven.apache.org > > > > Date: Wed, 16 Sep 2009 17:11:46 +0200 > > > > Subject: How to specify a plugin version from the command line? > > > > > > > > Hi > > > > > > > > I'm setting the exact versions for all Maven plugins in our > > > company-wide parent POM. > > > > However, that doesn't help when I'm using the command line. > > > > So how can I force Maven to use a certain version of a plugin? > > > > > > > > Best regards, > > > > Eric > > > > > > > > - > > > > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > > > > For additional commands, e-mail: users-h...@maven.apache.org > > > > > > > > > > _ > > > Hotmail: Free, trusted and rich email service. > > > http://clk.atdmt.com/GBL/go/171222984/direct/01/ > > > - > > To unsubscribe, e-m
RE: Porpuse of src/main/config
Hi,
Thanks for the answer. It's a bit more clear now.
May be, it would be nice to update online documentation
http://maven.apache.org/guides/introduction/introduction-to-the-standard-directory-layout.html
I googled a lot to get such information without any success even if i found
this question a lot of times.
Jean-Louis
Chris Helck wrote:
>
> Here's my understanding...
>
> In maven1, files in 'config' were packaged into the jar file. At some
> point it was decided that 'resources' was a better name than 'config',
> so now 'config' is just another directory that Maven doesn't do anything
> with.
>
> In general Maven doesn't know how you're going to deploy your package,
> so it doesn't know what to do with directories like: config, etc, bin,
> and so on. So you need to figure this out and come up with your own
> convention. Plugin's like assemble (assembly?) can help a lot. I often
> use it to create a tar ball that unpacks into a directory something
> like:
>
> app/
> bin # all files have execute
> etc # User configurable files
> jars# all dependencies
> logs# where app writes logs.
>
> Basically my bin and etc directories under src/main get copied into the
> tar ball.
>
> Hope this helps.
> C. Helck
>
>
>
>
>
> -Original Message-
> From: Jean-Louis MONTEIRO [mailto:jean-louis.monte...@atosorigin.com]
> Sent: Wednesday, September 16, 2009 12:06 PM
> To: users@maven.apache.org
> Subject: Re: Porpuse of src/main/config
>
>
>
>
> Geoffrey Wiseman wrote:
>>
>> On Fri, Aug 1, 2008 at 11:00 AM, DOMINGUEZ Felipe <
>> felipe.doming...@eurocontrol.int> wrote:
>>
>>> I am new to Maven, and I am a bit confuse about the porpuse of
>>> directory src/main/config porpuse
>>>
>>> I have been looking for information about it but it does not seems to
>
>>> be much.
>>>
>>> I initially thought that in directory src/main/resources I could put
>>> any static resource used by the jar file and in src/main/config I
>>> could put any configuration file that needs to be customised before
>>> the jar file is used. For example in the config file I would add the
>>> hibernate.cfg.xml file, since the DB connection information needs to
>>> be modify by the person who will use the jar file.
>>>
>>> placing hibernage.cfg.xml in the resources files is not good, since
>>> this file will be added to the jar file, so the person who will use
>>> the jar file will have to extract it to be able to modify its
>>> properties. So initially I thought that src/main/config was for this
>
>>> porpuse, but all files that I put in congif directory are ignored.
>>>
>>> Can any body clarify the usage of src/main/config and what is maven
>>> approach for using configuration files such as hibernate.cfg.xml or
>>> other config files that need to be modified on the live environment?
>>>
>>
>> What about this?
>> http://maven.apache.org/guides/introduction/introduction-to-the-standa
>> rd-directory-layout.html
>>
>> --
>> Geoffrey Wiseman
>>
>>
> Hi Geoffrey,
>
> it's not clear at all.
> Can you please explicitly give us the difference between
> src/main/resources and src/main/config ?
> I guess src/main/resources goes to target package (jar, war, ...). And
> from my understanding, src/main/config is not part of the classpath and
> is used only for build (configuration files used to build, ...).
>
> Thanks for your help.
> Regards,
> Jean-Louis
> --
> View this message in context:
> http://www.nabble.com/Porpuse-of-src-main-config-tp18776348p25475583.htm
> l
> 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
>
>
> **
> This communication and all information (including, but not limited to,
> market prices/levels and data) contained therein (the "Information") is
> for informational purposes only, is confidential, may be legally
> privileged and is the intellectual property of ICAP plc and its
> affiliates
> ("ICAP") or third parties. No confidentiality or privilege is waived or
> lost by any mistransmission. The Information is not, and should not
> be construed as, an offer, bid or solicitation in relation to any
> financial instrument or as an official confirmation of any transaction.
> The Information is not warranted, including, but not limited, as to
> completeness, timeliness or accuracy and is subject to change
> without notice. ICAP assumes no liability for use or misuse of the
> Information. All representations and warranties are expressly
> disclaimed. The Information does not necessarily reflect the views of
> ICAP. Access to the Information by anyone else other than the
> recipient is unauthorized and any disclosure, copying, distribution or
> any action taken or omi
Re: Moving Repository
yep, you can edit your ~/.m2/settings.xml to point the local maven repo to any FS place. On Thu, Sep 17, 2009 at 3:31 PM, Quintin Beukes wrote: > Hey, > > I have a very large repository and would like to keep it (not start > over). Though, I would like to move it to a more "official" location > on my PC. > > I am planning to install a repository manager next week, but I still > want my local repository in a better place. This is mostly so I can > reference the JARs in there in non-maven projects. Can I just rename > it and change my maven settings, or is there anything else? > > -- > Quintin Beukes > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > -- - juven
Moving Repository
Hey, I have a very large repository and would like to keep it (not start over). Though, I would like to move it to a more "official" location on my PC. I am planning to install a repository manager next week, but I still want my local repository in a better place. This is mostly so I can reference the JARs in there in non-maven projects. Can I just rename it and change my maven settings, or is there anything else? -- Quintin Beukes - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
