Re: build maven project without setting compiler source and target
Hi Matt, > So I guess it's an issue with NetBeans then a) using such an old version > of maven b) not handle compiler version and minium required > source/target correctly. > Guess I just set it to 8, as that's the oldest jdk/vm I still have lay > around, and don't bother anymore about it. > Thanks for your replies and time anyway. Normally an IDE should respect what you have configured in your pom.xml when you execute a Maven build. Therefore I still assume that you don’t have specified what exact version of m-compiler-p you’d like to use. And that you don’t have configured source and target in m-compiler-p, i.e. you use the default parameters which - according to your mail - are an older version of Maven‘s compiler plugin and/or no source/target version set. Can you show us a minimal sample? Regards Thorsten - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: build maven project without setting compiler source and target
BUILD FAILURE Total time: 1.995 s Finished at: 2020-02-17T12:28:58+01:00 Final Memory: 10M/40M Failed to execute goal org.apache.maven.plugins:maven-compiler-plugin:3.1:compile (default-compile) on project YouTubeLiveChat: Compilation failure: Compilation failure: Source option 5 is no longer supported. Use 6 or later. Target option 1.5 is no longer supported. Use 1.6 or later. -> [Help 1] To see the full stack trace of the errors, re-run Maven with the -e switch. Re-run Maven using the -X switch to enable full debug logging. For more information about the errors and possible solutions, please read the following articles: [Help 1] http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException From what I was able to find this is because the hardcoded default value wich is used when no other setting is found in pom in the compiler plugin is version 5. As the error message says, this is no longer supported and 6 or higher should be used. I didn'T filed a bug report cause it's possible that there're version mismatches wich may cause this - I'm not sure about that. So, as I don't want to set a fixed value (maybe would be 8 if I have to) I would rather prefer to disable this settings at all and just let it compile with what ever version the system has a JDK of. Or, if it's not possible to complete throw it out is there at least a way to not just set a specific version but rather only a minimum? So, that a system wich has only J8 can use this, but other system with 9, 11, 13 won'T be enforced to compile v8 but with their own version? As I also mentioned else where: I thought IDEs and all their build stuff is supposed to make developing easier - but I had so many issues I encountered since I started to use it a few days ago I really though of go back to basic editor and terminal - wich seems easier (side-note about dependency management: yes, sure, it's nice to have a build system handle it for you, but as I'm used to gather libs and dependencies myself, and many often come in bundles, and manage different and matching versions by myself, I got a rather big lib collection used by just point my system wide classpath to the lib directory). So, any thoughts about how to solve that issue? I'm honestly kind of lost, not just using Netbeans as a gui wrapper (as one of its devs called it on their list) but also get my head around maven as the build environment). Thanks for any help in advance, Matt Am 2020-02-17 05:24, schrieb Bernd Eckenfels: > Can you show the actual error message and give a concrete project? > Normally Maven works with not specifying target/source as long as your > JDK is recent enough. (But it's not ways a good idea, it's better to > specify the properties (IDEs normally read them) > > > -- > http://bernd.eckenfels.net > > Von: java-cry...@cryptearth.de > Gesendet: Monday, February 17, 2020 4:27:16 AM > An: users@maven.apache.org > Betreff: build maven project without setting compiler source and target > > So as I just got new into using Netbeans someone on its list explained > me, that it's just a gui wrapper around maven and it's adviced to get > the basics of maven to correctly use netbeans. > Ok, so as I just used a simple editor and a terminal it didn't mattered > wich version I compiled with or for in the past as I ran the class with > the same vm I compiled them with. So, the I thought I could just ommit > the setting - but maven just fails with an error that no source/target > version was specified. So I had them re-add by re-apply the project > settings. > Is there a way I could tell the compiler plugin just to ignore the > version but also to ignore if it's missing and just compile it with > whatever version I ran maven with? > It's basically: I use different systems all with different jdk > installed > - so when just clone the most recent version from github I always have > to set the correct version manual as netbeans doesn't seem to be handle > that by itself - and I could find an option to just get rid of it at > all. > > Thanks in advance, > > Matt > > - > 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: Re: build maven project without setting compiler source and target
Hi, > Scanning for projects... (...) > - > COMPILATION ERROR : > - > Source option 5 is no longer supported. Use 6 or later. > Target option 1.5 is no longer supported. Use 1.6 or later. > 2 errors > - You obviously use an older version of maven-compiler-plugin that still defaults to Java 5. In that case this error is expectable as Java 11 doesn't support compiling for Java 5 anymore. The actual version 3.8.1 of m-compiler-p (see [1]) defaults to Java 6 as source and target for the compiler. I suggest you upgrade your pom.xml to that version. Anyway, I recommend you pin the version of each used plugin in your pom.xml. Otherwise you may get different results if you upgrade Maven, the JVM, use another OS and so on. [1] https://maven.apache.org/plugins/maven-compiler-plugin/ Regards Thorsten
Re: build maven project without setting compiler source and target
, this is no longer > supported and 6 or higher should be used. I didn'T filed a bug report > cause it's possible that there're version mismatches wich may cause this > - I'm not sure about that. > So, as I don't want to set a fixed value (maybe would be 8 if I have to) > I would rather prefer to disable this settings at all and just let it > compile with what ever version the system has a JDK of. Or, if it's not > possible to complete throw it out is there at least a way to not just > set a specific version but rather only a minimum? So, that a system wich > has only J8 can use this, but other system with 9, 11, 13 won'T be > enforced to compile v8 but with their own version? > > As I also mentioned else where: I thought IDEs and all their build stuff > is supposed to make developing easier - but I had so many issues I > encountered since I started to use it a few days ago I really though of > go back to basic editor and terminal - wich seems easier (side-note > about dependency management: yes, sure, it's nice to have a build system > handle it for you, but as I'm used to gather libs and dependencies > myself, and many often come in bundles, and manage different and > matching versions by myself, I got a rather big lib collection used by > just point my system wide classpath to the lib directory). > > So, any thoughts about how to solve that issue? I'm honestly kind of > lost, not just using Netbeans as a gui wrapper (as one of its devs > called it on their list) but also get my head around maven as the build > environment). > > Thanks for any help in advance, > > Matt > > Am 2020-02-17 05:24, schrieb Bernd Eckenfels: > > Can you show the actual error message and give a concrete project? > > Normally Maven works with not specifying target/source as long as your > > JDK is recent enough. (But it's not ways a good idea, it's better to > > specify the properties (IDEs normally read them) > > > > > > -- > > http://bernd.eckenfels.net > > > > Von: java-cry...@cryptearth.de > > Gesendet: Monday, February 17, 2020 4:27:16 AM > > An: users@maven.apache.org > > Betreff: build maven project without setting compiler source and target > > > > So as I just got new into using Netbeans someone on its list explained > > me, that it's just a gui wrapper around maven and it's adviced to get > > the basics of maven to correctly use netbeans. > > Ok, so as I just used a simple editor and a terminal it didn't mattered > > wich version I compiled with or for in the past as I ran the class with > > the same vm I compiled them with. So, the I thought I could just ommit > > the setting - but maven just fails with an error that no source/target > > version was specified. So I had them re-add by re-apply the project > > settings. > > Is there a way I could tell the compiler plugin just to ignore the > > version but also to ignore if it's missing and just compile it with > > whatever version I ran maven with? > > It's basically: I use different systems all with different jdk > > installed > > - so when just clone the most recent version from github I always have > > to set the correct version manual as netbeans doesn't seem to be handle > > that by itself - and I could find an option to just get rid of it at > > all. > > > > Thanks in advance, > > > > Matt > > > > - > > 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 > > -- Thomas Broyer /tɔ.ma.bʁwa.je/ <http://xn--nna.ma.xn--bwa-xxb.je/>
Re: build maven project without setting compiler source and target
as long as your JDK is recent enough. (But it's not ways a good idea, it's better to specify the properties (IDEs normally read them) -- http://bernd.eckenfels.net ____ Von: java-cry...@cryptearth.de Gesendet: Monday, February 17, 2020 4:27:16 AM An: users@maven.apache.org Betreff: build maven project without setting compiler source and target So as I just got new into using Netbeans someone on its list explained me, that it's just a gui wrapper around maven and it's adviced to get the basics of maven to correctly use netbeans. Ok, so as I just used a simple editor and a terminal it didn't mattered wich version I compiled with or for in the past as I ran the class with the same vm I compiled them with. So, the I thought I could just ommit the setting - but maven just fails with an error that no source/target version was specified. So I had them re-add by re-apply the project settings. Is there a way I could tell the compiler plugin just to ignore the version but also to ignore if it's missing and just compile it with whatever version I ran maven with? It's basically: I use different systems all with different jdk installed - so when just clone the most recent version from github I always have to set the correct version manual as netbeans doesn't seem to be handle that by itself - and I could find an option to just get rid of it at all. Thanks in advance, Matt - 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: build maven project without setting compiler source and target
Can you show the actual error message and give a concrete project? Normally Maven works with not specifying target/source as long as your JDK is recent enough. (But it's not ways a good idea, it's better to specify the properties (IDEs normally read them) -- http://bernd.eckenfels.net Von: java-cry...@cryptearth.de Gesendet: Monday, February 17, 2020 4:27:16 AM An: users@maven.apache.org Betreff: build maven project without setting compiler source and target So as I just got new into using Netbeans someone on its list explained me, that it's just a gui wrapper around maven and it's adviced to get the basics of maven to correctly use netbeans. Ok, so as I just used a simple editor and a terminal it didn't mattered wich version I compiled with or for in the past as I ran the class with the same vm I compiled them with. So, the I thought I could just ommit the setting - but maven just fails with an error that no source/target version was specified. So I had them re-add by re-apply the project settings. Is there a way I could tell the compiler plugin just to ignore the version but also to ignore if it's missing and just compile it with whatever version I ran maven with? It's basically: I use different systems all with different jdk installed - so when just clone the most recent version from github I always have to set the correct version manual as netbeans doesn't seem to be handle that by itself - and I could find an option to just get rid of it at all. Thanks in advance, Matt - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
build maven project without setting compiler source and target
So as I just got new into using Netbeans someone on its list explained me, that it's just a gui wrapper around maven and it's adviced to get the basics of maven to correctly use netbeans. Ok, so as I just used a simple editor and a terminal it didn't mattered wich version I compiled with or for in the past as I ran the class with the same vm I compiled them with. So, the I thought I could just ommit the setting - but maven just fails with an error that no source/target version was specified. So I had them re-add by re-apply the project settings. Is there a way I could tell the compiler plugin just to ignore the version but also to ignore if it's missing and just compile it with whatever version I ran maven with? It's basically: I use different systems all with different jdk installed - so when just clone the most recent version from github I always have to set the correct version manual as netbeans doesn't seem to be handle that by itself - and I could find an option to just get rid of it at all. Thanks in advance, Matt - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Byldan, NPanday or MS-Build & Maven Which would be the preferred build tool for C#?
Hi, We have a C# project which is build using "Byldan" . Now we are kind of thinking of replacing the "Byldan" with some other Build tool. Preferably the two options we have is:- 1) NPanday 2) MS Build along with Maven I would greatly appreciate if you could throw some light on this, and which would be the preferred tool going ahead. Thank you in advance. Regards Achyuth -- View this message in context: http://maven.40175.n5.nabble.com/Byldan-NPanday-or-MS-Build-Maven-Which-would-be-the-preferred-build-tool-for-C-tp5768914.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: WARNINGS in Maven Build: maven-compiler-plugins missing
An explanation can be found in the Maven 3.x Compatibility Notes: https://cwiki.apache.org/MAVEN/maven-3x-compatibility-notes.html#Maven3.xCompatibilityNotes-AutomaticPluginVersionResolution BTW: The version numbers can either be defined in the 'pluginManagement' and/or in the 'plugins' section - depends on Your project. On 04/02/11 06:47, Anders Hammar wrote: A very similar question was asked on the list some weeks ago. You need to lock down the (specify) the version of maven-compiler-plugin. You do that in the pluginManagement section. An example is here: http://maven.apache.org/pom.html#Plugin_Management (Note: You don't need to specify any executions though.) /Anders On Fri, Feb 4, 2011 at 06:16, Jonthan DeMaagd wrote: [INFO] Scanning for projects... [WARNING] [WARNING] Some problems were encountered while building the effective model for org.sonatype.mavenbook.custom:simple-weather:jar:1.0 [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-compiler-plugin is missing. @ line 69, column 12 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. [WARNING] .. .. Project builds and runs fine. But I really want to take care of these WARNINGS! Have not had much luck with tutorial, "Maven by Example" or online resources. Went to this as last resource! Thanks much! - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: WARNINGS in Maven Build: maven-compiler-plugins missing
A very similar question was asked on the list some weeks ago. You need to lock down the (specify) the version of maven-compiler-plugin. You do that in the pluginManagement section. An example is here: http://maven.apache.org/pom.html#Plugin_Management (Note: You don't need to specify any executions though.) /Anders On Fri, Feb 4, 2011 at 06:16, Jonthan DeMaagd wrote: > [INFO] Scanning for projects... > > [WARNING] > > [WARNING] Some problems were encountered while building the effective model > for org.sonatype.mavenbook.custom:simple-weather:jar:1.0 > > [WARNING] 'build.plugins.plugin.version' for > org.apache.maven.plugins:maven-compiler-plugin is missing. @ line 69, > column > 12 > > [WARNING] > > [WARNING] It is highly recommended to fix these problems because they > threaten the stability of your build. > > [WARNING] > > [WARNING] For this reason, future Maven versions might no longer support > building such malformed projects. > > [WARNING] > > .. > > .. > > > > Project builds and runs fine. > > But I really want to take care of these WARNINGS! > > > > Have not had much luck with tutorial, "Maven by Example" or online > resources. > > Went to this as last resource! > > > > Thanks much! > > > >
WARNINGS in Maven Build: maven-compiler-plugins missing
[INFO] Scanning for projects... [WARNING] [WARNING] Some problems were encountered while building the effective model for org.sonatype.mavenbook.custom:simple-weather:jar:1.0 [WARNING] 'build.plugins.plugin.version' for org.apache.maven.plugins:maven-compiler-plugin is missing. @ line 69, column 12 [WARNING] [WARNING] It is highly recommended to fix these problems because they threaten the stability of your build. [WARNING] [WARNING] For this reason, future Maven versions might no longer support building such malformed projects. [WARNING] .. .. Project builds and runs fine. But I really want to take care of these WARNINGS! Have not had much luck with tutorial, "Maven by Example" or online resources. Went to this as last resource! Thanks much!
Re: Build "Works" on my machine. Not on build (maven-antrun-plugin)
I updated Maven on the build system to Maven 2.2.0, and that seemed to take care of this issue. The antrun tasks are running. On Mon, Aug 10, 2009 at 12:11 PM, David Weintraub wrote: > I have a multi-module build that depends upon the maven-antrun-plugin. This > module has to take a zip file and unzip it to a particular directory inside > the war. It's pretty straight forward, and it works fine on my machine. > Unfortunately, on our build system, the same build structure on the same > source code doesn't unzip the zipfile to the needed directory. As far as I > can tell, it does nothing. > > There are several differences on the build machine and mine which might > make a difference. I am running Maven 2.1.0 while my build system is running > Maven 2.0.8. I am also using Subversion 1.6 while the build machine uses > 1.3. My version of Ant is 1.7.1 while the build machine's version of Ant is > 1.7. > > Any idea what the issue could be? > > -- > David Weintraub > qazw...@gmail.com > -- David Weintraub qazw...@gmail.com
Build "Works" on my machine. Not on build (maven-antrun-plugin)
I have a multi-module build that depends upon the maven-antrun-plugin. This module has to take a zip file and unzip it to a particular directory inside the war. It's pretty straight forward, and it works fine on my machine. Unfortunately, on our build system, the same build structure on the same source code doesn't unzip the zipfile to the needed directory. As far as I can tell, it does nothing. There are several differences on the build machine and mine which might make a difference. I am running Maven 2.1.0 while my build system is running Maven 2.0.8. I am also using Subversion 1.6 while the build machine uses 1.3. My version of Ant is 1.7.1 while the build machine's version of Ant is 1.7. Any idea what the issue could be? -- David Weintraub qazw...@gmail.com pom.xml.tar.gz Description: GNU Zip compressed data - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: timestamped artifacts in multi module build - maven bug or mymisunderstanding
It seems that it is bug in MAVEN: http://jira.codehaus.org/browse/MNG-2486 anyone knows any workaround for this? my first guess is to filter generated pom.xml version from X.X-SNAPSHOT to TIMESTAMP in deploy phase, before deploying it to the snapshot repo. Probably i'll try to patch deploy plugin to do so. Can anyone tell whether it seems like a good approach, or suggest another one? Regards Michal -- View this message in context: http://www.nabble.com/timestamped-artifacts-in-multi-module-build---maven-bug-or-mymisunderstanding-tp23496396p23501583.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
timestamped artifacts in multi module build - maven bug or mymisunderstanding
Hi,
I am doing deploy (mvn deploy) of timestamped multi-module build.
It puts nice timestamped versions of all those modules in my repo,
updating maven-metadata.xml accordingly.
Modules in that build depend on each other (say moduleA depends on
moduleB) - using ${pom.version}.
I need to use that timestamped modules in my other build, but it seems
that when i declare dependency on moduleA (version timestamped), still
the transitive moduleB dependency version retrieved is not timestamped,
but latest available in the repo. This makes my build not unique, and
thus timestamp concept does not seem to work for this scenario at all.
Please tell me, whether I do something wrong, or just maven concept does
not fully fit to releasing timestamped artifacts at all?
Thanks
Michal Szalinski
Diese Nachricht könnte vertrauliche und/oder rechtlich
geschützte Informationen enthalten. Wenn Sie nicht der
Adressat dieser Email sind oder nicht autorisiert sind, diese
für den Adressaten entgegenzunehmen, so ist es untersagt,
diese Nachricht oder in ihr enthaltene Informationen zu nutzen,
zu kopieren, offen zu legen oder anderweitig weiterzuverarbeiten.
Sollten Sie diese Nachricht fälschlicherweise erhalten haben,
verständigen Sie den Absender bitte unverzüglich per Antwort auf
diese Mail und löschen sie diese anschließend.
Vielen Dank für Ihre Kooperation.
This message may contain confidential and/or privileged
information. If you are not the addressee or authorized
to receive this for the addressee, you must not use, copy,
disclose or take any action based on this message or any
information herein. If you have received this message in
error, please advise the sender immediately by reply e-mail
and delete this message. Thank you for your co-operation.
We make your business move.
Re: Ant Task - Build maven pom.xml
Le mercredi 11 février 2009, vikask a écrit : > Hi, > Thanks for you detailed explanation. I got the scope of "maven ant tasks". > case 1 is what I am looking for. great what is missing in the doc? what do you feel should be improved? > Definitely now I will try with ant task. If I understand this comment, you're really wanting to build the project: yes, is the way to do it, not Maven Ant Tasks > > Just for curiosity, Is there any plan to in maven 3 to give such facility > to build any maven (pom.xml) project from ant build.xml file? no, Maven Ant Tasks are rewritten within Mercury (won't explain here the difference, that's not useful), but the scope doesn't change: only dependencies and install/deploy. In fact, I don't understand the use case: if full Maven power is needed, just use Maven, not Ant, no? Implementing such tasks would be equivalent as writing a replacement to Maven CLI, to avoid * but having a wrapper doing some equivalent work. I really don't understand. > > Thanks once again for your great explanation. please help me improve the doc :) regards, Hervé > > regards > Vikas > > Hervé BOUTEMY wrote: > > Hi, > > > > I thought Tim's reply didn't need any addition, but it seems that even > > the documentation is still not clear enough (multiple people did a lot of > > work on > > it, though...). > > Let's try to understand your problem, then improve the doc. > > > > Perhaps 2 examples will help us to understand each other. > > > > 1. Maven Ant Tasks have a sample.build.xml [2] to unit-test the > > components features > > As stated before, Maven Ant Tasks are not meant to really *build* a > > project, > > but only get dependencies. So you won't see in this example anything > > really > > building: only getting dependencies in multiple forms, installing an > > artifact > > into local repository and deploying to a remote repo (how the artifact > > installed/deployed is really build is not shown, since once again, it's > > not > > the purpose of the tasks) > > > > 2. Maven itself can be bootstrapped using Maven Ant Tasks: see build.xml > > in > > Maven Core sources [3] > > This time, this is really a project (Maven Core) built by Ant, getting > > its multiple dependencies with Maven Ant Tasks: seems to be what you want > > to do > > with your project. > > As you can see in the build file, most content is about building a > > specific > > project: there is only a little part that is about getting dependencies, > > ie > > the "pull" target (with its depends). > > > > > > Are these examples more clear? > > > > > > Regards, > > > > Hervé > > > > > > [2] > > http://svn.apache.org/viewvc/maven/ant-tasks/branches/maven-ant-tasks-2.0 > >.x/sample.build.xml?view=markup > > > > [3] > > http://svn.apache.org/viewvc/maven/components/branches/maven-2.0.x/build. > >xml?view=markup > > > > Le mercredi 11 février 2009, vikask a écrit : > >> Hi > >> > >> I am also facing same problem. Have anyone found solution? > >> > >> Thanks > >> > >> regards > >> Vikas > >> > >> Tim Kettler wrote: > >> > Hi, > >> > > >> > halsafar schrieb: > >> >> I am trying to write an ant script to automate some maven tasks and > >> >> hopefully > >> >> decide not to rebuild the entire thing if it detects no changes. > >> >> Just to give an idea I am working with Jasig CAS Server which has > >> >> several modules all which are Maven projects. The build time is > >> >> brutal on > >> > >> this > >> > >> >> beast and it > >> >> will always rebuild no matter what it seems. So even if Ant won't > >> > >> help > >> > >> >> I am > >> >> still stuck using Ant as I need to auto-deploy the CAS Server to both > >> > >> a > >> > >> >> Tomcat and Glassfish server. Now everything has been done and Maven > >> > >> is > >> > >> >> being run from a simple call in the build.xml for the ant > >> > >> script. > >> > >> >> I > >> >> did find some Official Maven Ant Tasks jar I would like to try. > >> > >> However > >> > >> >> I > >> >> have been unable to find any examples which actually show this maven > >> > >> ant > >> > >> >> tasks building a maven project. Any help? > >> > > >> > The maven ant tasks bring the dependency management features of maven > >> > >> to > >> > >> > ant, they don't enable ant to build a maven project. Anyway, here [1] > >> > >> is > >> > >> > the link to the official homepage containing usage instructions. > >> > > >> > -Tim > >> > > >> > [1] http://maven.apache.org/ant-tasks.html > >> > > >> > - > >> > 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...@mav
Re: Ant Task - Build maven pom.xml
Hi, Thanks for you detailed explanation. I got the scope of "maven ant tasks". case 1 is what I am looking for. Definitely now I will try with ant task. Just for curiosity, Is there any plan to in maven 3 to give such facility to build any maven (pom.xml) project from ant build.xml file? Thanks once again for your great explanation. regards Vikas Hervé BOUTEMY wrote: > > Hi, > > I thought Tim's reply didn't need any addition, but it seems that even the > documentation is still not clear enough (multiple people did a lot of work > on > it, though...). > Let's try to understand your problem, then improve the doc. > > Perhaps 2 examples will help us to understand each other. > > 1. Maven Ant Tasks have a sample.build.xml [2] to unit-test the components > features > As stated before, Maven Ant Tasks are not meant to really *build* a > project, > but only get dependencies. So you won't see in this example anything > really > building: only getting dependencies in multiple forms, installing an > artifact > into local repository and deploying to a remote repo (how the artifact > installed/deployed is really build is not shown, since once again, it's > not > the purpose of the tasks) > > 2. Maven itself can be bootstrapped using Maven Ant Tasks: see build.xml > in > Maven Core sources [3] > This time, this is really a project (Maven Core) built by Ant, getting its > multiple dependencies with Maven Ant Tasks: seems to be what you want to > do > with your project. > As you can see in the build file, most content is about building a > specific > project: there is only a little part that is about getting dependencies, > ie > the "pull" target (with its depends). > > > Are these examples more clear? > > > Regards, > > Hervé > > > [2] > http://svn.apache.org/viewvc/maven/ant-tasks/branches/maven-ant-tasks-2.0.x/sample.build.xml?view=markup > > [3] > http://svn.apache.org/viewvc/maven/components/branches/maven-2.0.x/build.xml?view=markup > > Le mercredi 11 février 2009, vikask a écrit : >> Hi >> >> I am also facing same problem. Have anyone found solution? >> >> Thanks >> >> regards >> Vikas >> >> Tim Kettler wrote: >> > Hi, >> > >> > halsafar schrieb: >> >> I am trying to write an ant script to automate some maven tasks and >> >> hopefully >> >> decide not to rebuild the entire thing if it detects no changes. Just >> >> to give an idea I am working with Jasig CAS Server which has several >> >> modules all which are Maven projects. The build time is brutal on >> this >> >> beast and it >> >> will always rebuild no matter what it seems. So even if Ant won't >> help >> >> I am >> >> still stuck using Ant as I need to auto-deploy the CAS Server to both >> a >> >> Tomcat and Glassfish server. Now everything has been done and Maven >> is >> >> being run from a simple call in the build.xml for the ant >> script. >> >> I >> >> did find some Official Maven Ant Tasks jar I would like to try. >> However >> >> I >> >> have been unable to find any examples which actually show this maven >> ant >> >> tasks building a maven project. Any help? >> > >> > The maven ant tasks bring the dependency management features of maven >> to >> > ant, they don't enable ant to build a maven project. Anyway, here [1] >> is >> > the link to the official homepage containing usage instructions. >> > >> > -Tim >> > >> > [1] http://maven.apache.org/ant-tasks.html >> > >> > - >> > 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 > > > -- View this message in context: http://www.nabble.com/Ant-Task---Build-maven-pom.xml-tp17657445p21951942.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: Ant Task - Build maven pom.xml
Hi, I thought Tim's reply didn't need any addition, but it seems that even the documentation is still not clear enough (multiple people did a lot of work on it, though...). Let's try to understand your problem, then improve the doc. Perhaps 2 examples will help us to understand each other. 1. Maven Ant Tasks have a sample.build.xml [2] to unit-test the components features As stated before, Maven Ant Tasks are not meant to really *build* a project, but only get dependencies. So you won't see in this example anything really building: only getting dependencies in multiple forms, installing an artifact into local repository and deploying to a remote repo (how the artifact installed/deployed is really build is not shown, since once again, it's not the purpose of the tasks) 2. Maven itself can be bootstrapped using Maven Ant Tasks: see build.xml in Maven Core sources [3] This time, this is really a project (Maven Core) built by Ant, getting its multiple dependencies with Maven Ant Tasks: seems to be what you want to do with your project. As you can see in the build file, most content is about building a specific project: there is only a little part that is about getting dependencies, ie the "pull" target (with its depends). Are these examples more clear? Regards, Hervé [2] http://svn.apache.org/viewvc/maven/ant-tasks/branches/maven-ant-tasks-2.0.x/sample.build.xml?view=markup [3] http://svn.apache.org/viewvc/maven/components/branches/maven-2.0.x/build.xml?view=markup Le mercredi 11 février 2009, vikask a écrit : > Hi > > I am also facing same problem. Have anyone found solution? > > Thanks > > regards > Vikas > > Tim Kettler wrote: > > Hi, > > > > halsafar schrieb: > >> I am trying to write an ant script to automate some maven tasks and > >> hopefully > >> decide not to rebuild the entire thing if it detects no changes. Just > >> to give an idea I am working with Jasig CAS Server which has several > >> modules all which are Maven projects. The build time is brutal on this > >> beast and it > >> will always rebuild no matter what it seems. So even if Ant won't help > >> I am > >> still stuck using Ant as I need to auto-deploy the CAS Server to both a > >> Tomcat and Glassfish server. Now everything has been done and Maven is > >> being run from a simple call in the build.xml for the ant script. > >> I > >> did find some Official Maven Ant Tasks jar I would like to try. However > >> I > >> have been unable to find any examples which actually show this maven ant > >> tasks building a maven project. Any help? > > > > The maven ant tasks bring the dependency management features of maven to > > ant, they don't enable ant to build a maven project. Anyway, here [1] is > > the link to the official homepage containing usage instructions. > > > > -Tim > > > > [1] http://maven.apache.org/ant-tasks.html > > > > - > > 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: Ant Task - Build maven pom.xml
Hi I am also facing same problem. Have anyone found solution? Thanks regards Vikas Tim Kettler wrote: > > Hi, > > halsafar schrieb: >> I am trying to write an ant script to automate some maven tasks and >> hopefully >> decide not to rebuild the entire thing if it detects no changes. Just to >> give an idea I am working with Jasig CAS Server which has several modules >> all which are Maven projects. The build time is brutal on this beast and >> it >> will always rebuild no matter what it seems. So even if Ant won't help I >> am >> still stuck using Ant as I need to auto-deploy the CAS Server to both a >> Tomcat and Glassfish server. Now everything has been done and Maven is >> being run from a simple call in the build.xml for the ant script. >> I >> did find some Official Maven Ant Tasks jar I would like to try. However >> I >> have been unable to find any examples which actually show this maven ant >> tasks building a maven project. Any help? > > The maven ant tasks bring the dependency management features of maven to > ant, they don't enable ant to build a maven project. Anyway, here [1] is > the link to the official homepage containing usage instructions. > > -Tim > > [1] http://maven.apache.org/ant-tasks.html > > - > To unsubscribe, e-mail: users-unsubscr...@maven.apache.org > For additional commands, e-mail: users-h...@maven.apache.org > > > -- View this message in context: http://www.nabble.com/Ant-Task---Build-maven-pom.xml-tp17657445p21948877.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
How to build maven project using "Maven Ant Tasks"?
Hi Friends, I want to build maven project using "Maven Ant Tasks". As posted in http://www.nabble.com/Ant-Task---Build-maven-pom.xml-td17657445.html#a17657445 ; can I just build maven project using ant tasks? I have project "xyz" which has "myprojects/xyz/pom.xml" file and I can build this project using command "mvn install". Now, If I have other project "abc", which has ant "myprojects/abc/build.xml" file. I want to build "xyz" project from "abc" project. Is this possible using "Maven Ant Tasks"? Thanks regards Vikas
Re: Ant Task - Build maven pom.xml
Hi, halsafar schrieb: I am trying to write an ant script to automate some maven tasks and hopefully decide not to rebuild the entire thing if it detects no changes. Just to give an idea I am working with Jasig CAS Server which has several modules all which are Maven projects. The build time is brutal on this beast and it will always rebuild no matter what it seems. So even if Ant won't help I am still stuck using Ant as I need to auto-deploy the CAS Server to both a Tomcat and Glassfish server. Now everything has been done and Maven is being run from a simple call in the build.xml for the ant script. I did find some Official Maven Ant Tasks jar I would like to try. However I have been unable to find any examples which actually show this maven ant tasks building a maven project. Any help? The maven ant tasks bring the dependency management features of maven to ant, they don't enable ant to build a maven project. Anyway, here [1] is the link to the official homepage containing usage instructions. -Tim [1] http://maven.apache.org/ant-tasks.html - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Ant Task - Build maven pom.xml
I am trying to write an ant script to automate some maven tasks and hopefully decide not to rebuild the entire thing if it detects no changes. Just to give an idea I am working with Jasig CAS Server which has several modules all which are Maven projects. The build time is brutal on this beast and it will always rebuild no matter what it seems. So even if Ant won't help I am still stuck using Ant as I need to auto-deploy the CAS Server to both a Tomcat and Glassfish server. Now everything has been done and Maven is being run from a simple call in the build.xml for the ant script. I did find some Official Maven Ant Tasks jar I would like to try. However I have been unable to find any examples which actually show this maven ant tasks building a maven project. Any help? -- View this message in context: http://www.nabble.com/Ant-Task---Build-maven-pom.xml-tp17657445p17657445.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem svn when I build Maven 2.0 project
Finally, I reinstall all... continuum, svn, maven in my pc and reset server and my computer and it's working :) Thanks all people for your help =^D -- View this message in context: http://www.nabble.com/Problem-svn-when-I-build-Maven-2.0-project-tf4689729.html#a13407110 Sent from the Continuum - Users mailing list archive at Nabble.com.
Re: Problem svn when I build Maven 2.0 project
try echo %PATH%. In my case it contains : ...;C:\Subversion\bin;... 2007/10/25, Saruqui <[EMAIL PROTECTED]>: > > I think that svn isn't in the path but.. where I configure it? > I included it in environment Windows path variable and it don't work :( > > > olamy wrote: > > > > Hi, > > Not really familiar with the language :-) > > But looks svn is not in the path. > > > > > > > > 2007/10/25, [EMAIL PROTECTED] <[EMAIL PROTECTED]>: > >> I'm newby with Continuum and I have the following error when I build my > >> Maven 2.0 project: > >> > >> Provider message: The svn command failed. > >> Command output: > >> --- > >> "svn" no se reconoce como un comando interno o externo, > >> programa o archivo por lotes ejecutable. > >> --- > >> > >> I have installed Continuum in my PC and svn server in other pc and I can > >> access to svn from other programs like eclipse or Tortoise svn. > >> Also I installed svn-win32-1.4.5 in my pc and I add > >> c:\svn-win32-1.4.5\bin > >> directory in Windows path. > >> > >> My project settings are: > >> I add in my pom.xml (in local): > >> > >> > >> scm:svn:http://:/svn/repo//trunk > >> scm:svn:http://:/svn/repo//trunk > >> > >> > >> In admin management Continuum: > >> SCM URL. scm:svn:http://:/svn/repo//trunk > >> > >> Can somebody help me?? Any idea?? > >> > >> Thx > >> > > > > > > -- > > Olivier > > > > > > -- > View this message in context: > http://www.nabble.com/Problem-svn-when-I-build-Maven-2.0-project-tf4689729.html#a13403659 > Sent from the Continuum - Users mailing list archive at Nabble.com. > > -- Olivier
Re: Problem svn when I build Maven 2.0 project
I think that svn isn't in the path but.. where I configure it? I included it in environment Windows path variable and it don't work :( olamy wrote: > > Hi, > Not really familiar with the language :-) > But looks svn is not in the path. > > > > 2007/10/25, [EMAIL PROTECTED] <[EMAIL PROTECTED]>: >> I'm newby with Continuum and I have the following error when I build my >> Maven 2.0 project: >> >> Provider message: The svn command failed. >> Command output: >> --- >> "svn" no se reconoce como un comando interno o externo, >> programa o archivo por lotes ejecutable. >> --- >> >> I have installed Continuum in my PC and svn server in other pc and I can >> access to svn from other programs like eclipse or Tortoise svn. >> Also I installed svn-win32-1.4.5 in my pc and I add >> c:\svn-win32-1.4.5\bin >> directory in Windows path. >> >> My project settings are: >> I add in my pom.xml (in local): >> >> >> scm:svn:http://:/svn/repo//trunk >> scm:svn:http://:/svn/repo//trunk >> >> >> In admin management Continuum: >> SCM URL. scm:svn:http://:/svn/repo//trunk >> >> Can somebody help me?? Any idea?? >> >> Thx >> > > > -- > Olivier > > -- View this message in context: http://www.nabble.com/Problem-svn-when-I-build-Maven-2.0-project-tf4689729.html#a13403659 Sent from the Continuum - Users mailing list archive at Nabble.com.
Re: Problem svn when I build Maven 2.0 project
Probably ;) You have to set up integration (Continuum) platform as any other development platform. In your case, you have to install and setup: JDK, SVN, Maven2. Vanja On 10/25/07, olivier lamy <[EMAIL PROTECTED]> wrote: > > Hi, > Not really familiar with the language :-) > But looks svn is not in the path. > > > > 2007/10/25, [EMAIL PROTECTED] <[EMAIL PROTECTED]>: > > I'm newby with Continuum and I have the following error when I build my > > Maven 2.0 project: > > > > Provider message: The svn command failed. > > Command output: > > > --- > > "svn" no se reconoce como un comando interno o externo, > > programa o archivo por lotes ejecutable. > > > --- > > > > I have installed Continuum in my PC and svn server in other pc and I can > > access to svn from other programs like eclipse or Tortoise svn. > > Also I installed svn-win32-1.4.5 in my pc and I add c:\svn- > win32-1.4.5\bin > > directory in Windows path. > > > > My project settings are: > > I add in my pom.xml (in local): > > > > > > > scm:svn:http://:/svn/repo//trunk > > > scm:svn:http://:/svn/repo//trunk > > > > > > In admin management Continuum: > > SCM URL. scm:svn:http://:/svn/repo//trunk > > > > Can somebody help me?? Any idea?? > > > > Thx > > > > > -- > Olivier >
Re: Problem svn when I build Maven 2.0 project
Hi, Not really familiar with the language :-) But looks svn is not in the path. 2007/10/25, [EMAIL PROTECTED] <[EMAIL PROTECTED]>: > I'm newby with Continuum and I have the following error when I build my > Maven 2.0 project: > > Provider message: The svn command failed. > Command output: > --- > "svn" no se reconoce como un comando interno o externo, > programa o archivo por lotes ejecutable. > --- > > I have installed Continuum in my PC and svn server in other pc and I can > access to svn from other programs like eclipse or Tortoise svn. > Also I installed svn-win32-1.4.5 in my pc and I add c:\svn-win32-1.4.5\bin > directory in Windows path. > > My project settings are: > I add in my pom.xml (in local): > > > scm:svn:http://:/svn/repo//trunk > scm:svn:http://:/svn/repo//trunk > > > In admin management Continuum: > SCM URL. scm:svn:http://:/svn/repo//trunk > > Can somebody help me?? Any idea?? > > Thx > -- Olivier
Problem svn when I build Maven 2.0 project
I'm newby with Continuum and I have the following error when I build my Maven 2.0 project: Provider message: The svn command failed. Command output: --- "svn" no se reconoce como un comando interno o externo, programa o archivo por lotes ejecutable. --- I have installed Continuum in my PC and svn server in other pc and I can access to svn from other programs like eclipse or Tortoise svn. Also I installed svn-win32-1.4.5 in my pc and I add c:\svn-win32-1.4.5\bin directory in Windows path. My project settings are: I add in my pom.xml (in local): scm:svn:http://:/svn/repo//trunk scm:svn:http://:/svn/repo//trunk In admin management Continuum: SCM URL. scm:svn:http://:/svn/repo//trunk Can somebody help me?? Any idea?? Thx
Re: Multiple-Module Build? maven-assembly-plugin or maven-jar-plugin?
Hi, Andrew Leer schrieb: I am making my first attempt at building a multiple-module project. Should I use the maven-assembly-plugin, or the maven-jar-plugin? just building a multi-module project doesn't imply you have to explicitly use the jar- or assembly-plugin. Think of a multi-module project building a J2EE application contained in an ear. You would just have a couple of projects with packaging types jar, war, and ear. What is the difference between them? The main purpose of the jar plugin is to provide the packaging for standard jar-type projects. It is used when you not explicitly specify a packaging in your pom or specify a packaging of type 'jar'. The assembly-plugin's purpose is to build distributions of a project. For a standalone app for example you can use the assembly-plugin to put all jars of the project (including dependencies) in a directory structure and package that into an archive. Does which plugin should be used have to do with if the project is a standalone app, or something else? Thank you, Andrew J. Leer -Tim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Multiple-Module Build? maven-assembly-plugin or maven-jar-plugin?
I am making my first attempt at building a multiple-module project. Should I use the maven-assembly-plugin, or the maven-jar-plugin? What is the difference between them? Does which plugin should be used have to do with if the project is a standalone app, or something else? Thank you, Andrew J. Leer - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: multimodule project build, maven assembly plugin
Had the exact same problem! AFAIK the only way around this is to have
a dedicated module with the correct dependencies in place.
Unfortunately I could not figure out how to access plain files (not
just the artifacts or sources) from the assembly then.
Sad story as it is - in the end I did the assembly with a shell
script ...instead of spending even more time on maven.
If you find good solution - please let me know.
cheers
--
Torsten
On 14.06.2007, at 01:25, Francois Fernandes wrote:
Hi list,
and again a problem using the maven-assembly-plugin. I've got a
multimodule build with a custom assembly descriptor I would like to
execute the assembly plugin when the install phase is beeing executed.
Unfortunately this doesn't work as expected. The assembly is beeing
defined and attached to the lifecycle in the parent pom. When
invoking the install phase the parent is processed and the
assembly:attach is called immediately after the install of the
parent pom. That means that the submodules (which I'm referencing
in the assembly descriptor) haven't been invoked. I've attached the
resulting error to the bottom of this mail.
Thx for any help
The Parent POM:
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://
maven.apache.org/maven-v4_0_0.xsd">
4.0.0
my.group
parent
pom
1.0-SNAPSHOT
parent
client
shared
server
maven-assembly-plugin
false
build-distribution
install
attached
dist.xml
This is the resulting output:
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] parent
[INFO] shared
[INFO] client
[INFO] server
[INFO]
--
--
[INFO] Building parent
[INFO]task-segment: [install]
[INFO]
--
--
[INFO] [site:attach-descriptor]
[INFO] [install:install]
[INFO] Installing C:\temp\parent\pom.xml to ...\home\.m2\repository
\my\group\parent\1.0-SNAPSHOT\parent-1.0-SNAPSHOT.pom
[INFO] [assembly:attached {execution: build-distribution}]
[INFO] Reading assembly descriptor: C:\temp\parent\dist.xml
[INFO]
--
--
[ERROR] BUILD ERROR
[INFO]
--
--
[INFO] Failed to create assembly: Artifact: my.group:server:jar:1.0-
SNAPSHOT
(included by module) does not have an artifact with a file. Please
ensure the
package phase is run before the assembly is generated.
[INFO]
--
--
[INFO] For more information, run Maven with the -e switch
[INFO]
--
--
[INFO] Total time: 2 seconds
[INFO] Finished at: Thu Jun 14 01:15:57 CEST 2007
[INFO] Final Memory: 7M/14M
[INFO]
--
--
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
multimodule project build, maven assembly plugin
Hi list,
and again a problem using the maven-assembly-plugin. I've got a
multimodule build with a custom assembly descriptor I would like to
execute the assembly plugin when the install phase is beeing executed.
Unfortunately this doesn't work as expected. The assembly is beeing
defined and attached to the lifecycle in the parent pom. When invoking the
install phase the parent is processed and the assembly:attach is called
immediately after the install of the parent pom. That means that the
submodules (which I'm referencing in the assembly descriptor) haven't been
invoked. I've attached the resulting error to the bottom of this mail.
Thx for any help
The Parent POM:
http://maven.apache.org/POM/4.0.0";
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance";
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd";>
4.0.0
my.group
parent
pom
1.0-SNAPSHOT
parent
client
shared
server
maven-assembly-plugin
false
build-distribution
install
attached
dist.xml
This is the resulting output:
[INFO] Scanning for projects...
[INFO] Reactor build order:
[INFO] parent
[INFO] shared
[INFO] client
[INFO] server
[INFO]
[INFO] Building parent
[INFO]task-segment: [install]
[INFO]
[INFO] [site:attach-descriptor]
[INFO] [install:install]
[INFO] Installing C:\temp\parent\pom.xml to
...\home\.m2\repository\my\group\parent\1.0-SNAPSHOT\parent-1.0-SNAPSHOT.pom
[INFO] [assembly:attached {execution: build-distribution}]
[INFO] Reading assembly descriptor: C:\temp\parent\dist.xml
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Failed to create assembly: Artifact:
my.group:server:jar:1.0-SNAPSHOT
(included by module) does not have an artifact with a file. Please ensure
the
package phase is run before the assembly is generated.
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 2 seconds
[INFO] Finished at: Thu Jun 14 01:15:57 CEST 2007
[INFO] Final Memory: 7M/14M
[INFO]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Trying to build Maven 2.0.x - used to create uber jar, now it doens't
On 4/17/07, gilclark <[EMAIL PROTECTED]> wrote: A couple weeks back I was successfully building Maven 2.0.x. The last stage of the build is to run mvn assembly:assembly in the maven-core directory. The resultant zip, gz, etc. contained the uberjar called maven-2.0.x-uber.jar which goes in the lib directory. Unzip it somewhere - everything runs fine. About 4 days ago the build mysteriously stopped building the uber jar. I've tried this on two different machines with the same result - I have no idea what changed - nothing I did (on purpose). Come join us on the dev list if you have questions about building Maven itself; this list generally focuses on how to use the released bits. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Trying to build Maven 2.0.x - used to create uber jar, now it doens't
Not sure if this is the right forum but I'll start here. A couple weeks back I was successfully building Maven 2.0.x. The last stage of the build is to run mvn assembly:assembly in the maven-core directory. The resultant zip, gz, etc. contained the uberjar called maven-2.0.x-uber.jar which goes in the lib directory. Unzip it somewhere - everything runs fine. About 4 days ago the build mysteriously stopped building the uber jar. I've tried this on two different machines with the same result - I have no idea what changed - nothing I did (on purpose). Any help appreciated. -- View this message in context: http://www.nabble.com/Trying-to-build-Maven-2.0.x---used-to-create-uber-jar%2C-now-it-doens%27t-tf3598598s177.html#a10051099 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Cannot build maven project
Thank you, Robert. I changed the log level to DEBUG, but no more useful information was logged. As a desperate solution, I made a backup of Continuum and installed a new one from the scratch. I created a very simple project that works outside Continuum. The "mvn help:effective-pom help:effective-settings" command don't reveal anything suspicious for this project. But the problem still remains. Now, even with a fresh installation, Continuum doesn't work and I can't add any project. Following is the pom.xml of the project: 4.0.0 moleque.test simple-app jar 1.0-SNAPSHOT simple-app http://maven.apache.org scm:svn:http://dev.moleque.com.br:8086/svn/simple-app/trunk scm:svn:http://dev.moleque.com.br:8086/svn/simple-app/trunk simple-app.site file:///Library/WebServer/Documents/docs/simple-app dev.moleque.repo.snapshot Snapshot Repository Moleque file:///Users/devadmin/proximity/inhouse I don't know if it's a bug. But if it is, I don't know how to reproduce. :( Any suggestions are very welcome. :) Thanks in advance, Henrique Robert Dale wrote: /apps/continuum/conf/application.xml: There's a logging component at the bottom. Modify LEVEL. -- \o/ Henrique Prange, Moleque de Idéias Educação e Tecnologia Ltda | Phone: 55-21-2710-0178 E-mail: [EMAIL PROTECTED] / \ http://www.moleque.com.br
Re: Cannot build maven project
/apps/continuum/conf/application.xml: There's a logging component at the bottom. Modify LEVEL. -- Robert Dale Henrique Prange <[EMAIL PROTECTED]> wrote on 12/18/2006 07:20:14 AM: > Hi Rahul, > > Maybe it is a stupid question, but how can I turn on DEBUG level on > Continuum? > > I removed the settings.xml from the user .m2 configuration folder. Also, > I verified that settings.xml from maven installation folder is the > original version (without changes). I think the problem is not on Maven > settings, because "mvn clean deploy" command works with the projects on > Continuum working directory. Could a Continuum specific option be the > problem? > > Thanks, > > Henrique > > Rahul Thakur wrote: > > Hi, > > > > I don't think if there is a way to verify the settings.xml (someone can > > correct if I am wrong). You can turn on the DEBUG level for continuum > > and see what settings.xml it logs on the console in the scenario where > > this error occurs. > > > > I ran into same error few weeks ago and ended up reverting the > > settings.xml to a sane revision and then making small incremental > > updates to it. Is that new repository location missing a property like > > - id, name? > > > > Cheers, > > Rahul > > > > > > Henrique Prange wrote: > >> Hi Rahul, > >> > >> Thank you to answer. I've changed the settings.xml to add a new > >> repository location (this configuration seems to work correctly). > >> Anyway, I removed the settings.xml file from ~/.m2 and the error > >> persists. I really can't figure out what is the reason for that > >> problem. Is there a way to verify the correctness of Continuum > >> configuration? > >> > >> Cheers, > >> > >> Henrique > >> > >> Rahul Thakur wrote: > >>> > >>> Has something changed in the settings.xml lately for the user account > >>> under with Continuum is running? > >>> > >>> > >>> Henrique Prange wrote: > >>>> Hi List, > >>>> > >>>> I'm using Continuum for a time without problems. Today, however, my > >>>> projects stop building with the following error: > >>>> > >>>> > > >>>> > >>>> Build Error: > >>>> > > >>>> > >>>> org.apache.maven.continuum.execution.ContinuumBuildExecutorException: > >>>> Error while mapping metadata. > >>>> at > >>>> org.apache.maven.continuum.execution.maven.m2. > MavenTwoBuildExecutor. > updateProjectFromCheckOut(MavenTwoBuildExecutor.java:117) > >>>> > >>>> at > >>>> org.apache.maven.continuum.core.action. > UpdateProjectFromWorkingDirectoryContinuumAction. > execute(UpdateProjectFromWorkingDirectoryContinuumAction.java:64) > >>>> > >>>> at > >>>> org.apache.maven.continuum.buildcontroller. > DefaultBuildController.build(DefaultBuildController.java:273) > >>>> > >>>> at > >>>> org.apache.maven.continuum.buildcontroller. > BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:47) > >>>> > >>>> at > >>>> org.codehaus.plexus.taskqueue.execution. > ThreadedTaskQueueExecutor$ExecutorRunnable. > run(ThreadedTaskQueueExecutor.java:103) > >>>> > >>>> at java.lang.Thread.run(Thread.java:613) > >>>> Caused by: > >>>> org.apache.maven.continuum.execution.maven.m2. > MavenBuilderHelperException: > >>>> Cannot build maven project from > >>>> /usr/local/continuum/apps/continuum/working-directory/1/pom.xml (null). > >>>> > >>>> at > >>>> org.apache.maven.continuum.execution.maven.m2. > DefaultMavenBuilderHelper.getMavenProject(DefaultMavenBuilderHelper.java:339) > >>>> > >>>> at > >>>> org.apache.maven.continuum.execution.maven.m2. > DefaultMavenBuilderHelper. > mapMetadataToProject(DefaultMavenBuilderHelper.java:112) > >>>> > >>>> at > >>>> org.apache.maven.continuum.execution.maven.m2. > MavenTwoBuildExecutor. > upda
Re: Cannot build maven project
Hi Rahul, Maybe it is a stupid question, but how can I turn on DEBUG level on Continuum? I removed the settings.xml from the user .m2 configuration folder. Also, I verified that settings.xml from maven installation folder is the original version (without changes). I think the problem is not on Maven settings, because "mvn clean deploy" command works with the projects on Continuum working directory. Could a Continuum specific option be the problem? Thanks, Henrique Rahul Thakur wrote: Hi, I don't think if there is a way to verify the settings.xml (someone can correct if I am wrong). You can turn on the DEBUG level for continuum and see what settings.xml it logs on the console in the scenario where this error occurs. I ran into same error few weeks ago and ended up reverting the settings.xml to a sane revision and then making small incremental updates to it. Is that new repository location missing a property like - id, name? Cheers, Rahul Henrique Prange wrote: Hi Rahul, Thank you to answer. I've changed the settings.xml to add a new repository location (this configuration seems to work correctly). Anyway, I removed the settings.xml file from ~/.m2 and the error persists. I really can't figure out what is the reason for that problem. Is there a way to verify the correctness of Continuum configuration? Cheers, Henrique Rahul Thakur wrote: Has something changed in the settings.xml lately for the user account under with Continuum is running? Henrique Prange wrote: Hi List, I'm using Continuum for a time without problems. Today, however, my projects stop building with the following error: Build Error: org.apache.maven.continuum.execution.ContinuumBuildExecutorException: Error while mapping metadata. at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.updateProjectFromCheckOut(MavenTwoBuildExecutor.java:117) at org.apache.maven.continuum.core.action.UpdateProjectFromWorkingDirectoryContinuumAction.execute(UpdateProjectFromWorkingDirectoryContinuumAction.java:64) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:273) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:47) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:103) at java.lang.Thread.run(Thread.java:613) Caused by: org.apache.maven.continuum.execution.maven.m2.MavenBuilderHelperException: Cannot build maven project from /usr/local/continuum/apps/continuum/working-directory/1/pom.xml (null). at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.getMavenProject(DefaultMavenBuilderHelper.java:339) at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.mapMetadataToProject(DefaultMavenBuilderHelper.java:112) at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.updateProjectFromCheckOut(MavenTwoBuildExecutor.java:113) ... 5 more Caused by: java.lang.NullPointerException at org.codehaus.plexus.util.xml.pull.MXSerializer.writeElementContent(MXSerializer.java:912) at org.codehaus.plexus.util.xml.pull.MXSerializer.text(MXSerializer.java:776) at org.apache.maven.settings.io.xpp3.SettingsXpp3Writer.writeSettings(SettingsXpp3Writer.java:581) at org.apache.maven.settings.io.xpp3.SettingsXpp3Writer.write(SettingsXpp3Writer.java:71) at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.writeSettings(DefaultMavenBuilderHelper.java:489) at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.getMavenProject(DefaultMavenBuilderHelper.java:301) ... 7 more The projects were building normally sometime ago. If I try to build using maven manually on working directory, the build works. Also, I can't add new projects to the project list too, because of the same problem. Any ideas? Thanks, Henrique -- \o/ Henrique Prange, Moleque de Idéias Educação e Tecnologia Ltda | Phone: 55-21-2710-0178 E-mail: [EMAIL PROTECTED] / \ http://www.moleque.com.br
Re: Cannot build maven project
Hi, I don't think if there is a way to verify the settings.xml (someone can correct if I am wrong). You can turn on the DEBUG level for continuum and see what settings.xml it logs on the console in the scenario where this error occurs. I ran into same error few weeks ago and ended up reverting the settings.xml to a sane revision and then making small incremental updates to it. Is that new repository location missing a property like - id, name? Cheers, Rahul Henrique Prange wrote: Hi Rahul, Thank you to answer. I've changed the settings.xml to add a new repository location (this configuration seems to work correctly). Anyway, I removed the settings.xml file from ~/.m2 and the error persists. I really can't figure out what is the reason for that problem. Is there a way to verify the correctness of Continuum configuration? Cheers, Henrique Rahul Thakur wrote: Has something changed in the settings.xml lately for the user account under with Continuum is running? Henrique Prange wrote: Hi List, I'm using Continuum for a time without problems. Today, however, my projects stop building with the following error: Build Error: org.apache.maven.continuum.execution.ContinuumBuildExecutorException: Error while mapping metadata. at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.updateProjectFromCheckOut(MavenTwoBuildExecutor.java:117) at org.apache.maven.continuum.core.action.UpdateProjectFromWorkingDirectoryContinuumAction.execute(UpdateProjectFromWorkingDirectoryContinuumAction.java:64) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:273) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:47) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:103) at java.lang.Thread.run(Thread.java:613) Caused by: org.apache.maven.continuum.execution.maven.m2.MavenBuilderHelperException: Cannot build maven project from /usr/local/continuum/apps/continuum/working-directory/1/pom.xml (null). at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.getMavenProject(DefaultMavenBuilderHelper.java:339) at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.mapMetadataToProject(DefaultMavenBuilderHelper.java:112) at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.updateProjectFromCheckOut(MavenTwoBuildExecutor.java:113) ... 5 more Caused by: java.lang.NullPointerException at org.codehaus.plexus.util.xml.pull.MXSerializer.writeElementContent(MXSerializer.java:912) at org.codehaus.plexus.util.xml.pull.MXSerializer.text(MXSerializer.java:776) at org.apache.maven.settings.io.xpp3.SettingsXpp3Writer.writeSettings(SettingsXpp3Writer.java:581) at org.apache.maven.settings.io.xpp3.SettingsXpp3Writer.write(SettingsXpp3Writer.java:71) at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.writeSettings(DefaultMavenBuilderHelper.java:489) at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.getMavenProject(DefaultMavenBuilderHelper.java:301) ... 7 more The projects were building normally sometime ago. If I try to build using maven manually on working directory, the build works. Also, I can't add new projects to the project list too, because of the same problem. Any ideas? Thanks, Henrique
Re: Cannot build maven project
Hi Rahul, Thank you to answer. I've changed the settings.xml to add a new repository location (this configuration seems to work correctly). Anyway, I removed the settings.xml file from ~/.m2 and the error persists. I really can't figure out what is the reason for that problem. Is there a way to verify the correctness of Continuum configuration? Cheers, Henrique Rahul Thakur wrote: Has something changed in the settings.xml lately for the user account under with Continuum is running? Henrique Prange wrote: Hi List, I'm using Continuum for a time without problems. Today, however, my projects stop building with the following error: Build Error: org.apache.maven.continuum.execution.ContinuumBuildExecutorException: Error while mapping metadata. at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.updateProjectFromCheckOut(MavenTwoBuildExecutor.java:117) at org.apache.maven.continuum.core.action.UpdateProjectFromWorkingDirectoryContinuumAction.execute(UpdateProjectFromWorkingDirectoryContinuumAction.java:64) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:273) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:47) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:103) at java.lang.Thread.run(Thread.java:613) Caused by: org.apache.maven.continuum.execution.maven.m2.MavenBuilderHelperException: Cannot build maven project from /usr/local/continuum/apps/continuum/working-directory/1/pom.xml (null). at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.getMavenProject(DefaultMavenBuilderHelper.java:339) at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.mapMetadataToProject(DefaultMavenBuilderHelper.java:112) at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.updateProjectFromCheckOut(MavenTwoBuildExecutor.java:113) ... 5 more Caused by: java.lang.NullPointerException at org.codehaus.plexus.util.xml.pull.MXSerializer.writeElementContent(MXSerializer.java:912) at org.codehaus.plexus.util.xml.pull.MXSerializer.text(MXSerializer.java:776) at org.apache.maven.settings.io.xpp3.SettingsXpp3Writer.writeSettings(SettingsXpp3Writer.java:581) at org.apache.maven.settings.io.xpp3.SettingsXpp3Writer.write(SettingsXpp3Writer.java:71) at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.writeSettings(DefaultMavenBuilderHelper.java:489) at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.getMavenProject(DefaultMavenBuilderHelper.java:301) ... 7 more The projects were building normally sometime ago. If I try to build using maven manually on working directory, the build works. Also, I can't add new projects to the project list too, because of the same problem. Any ideas? Thanks, Henrique -- \o/ Henrique Prange, Moleque de Idéias Educação e Tecnologia Ltda | Phone: 55-21-2710-0178 E-mail: [EMAIL PROTECTED] / \ http://www.moleque.com.br
Re: Cannot build maven project
Has something changed in the settings.xml lately for the user account under with Continuum is running? Henrique Prange wrote: Hi List, I'm using Continuum for a time without problems. Today, however, my projects stop building with the following error: Build Error: org.apache.maven.continuum.execution.ContinuumBuildExecutorException: Error while mapping metadata. at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.updateProjectFromCheckOut(MavenTwoBuildExecutor.java:117) at org.apache.maven.continuum.core.action.UpdateProjectFromWorkingDirectoryContinuumAction.execute(UpdateProjectFromWorkingDirectoryContinuumAction.java:64) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:273) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:47) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:103) at java.lang.Thread.run(Thread.java:613) Caused by: org.apache.maven.continuum.execution.maven.m2.MavenBuilderHelperException: Cannot build maven project from /usr/local/continuum/apps/continuum/working-directory/1/pom.xml (null). at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.getMavenProject(DefaultMavenBuilderHelper.java:339) at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.mapMetadataToProject(DefaultMavenBuilderHelper.java:112) at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.updateProjectFromCheckOut(MavenTwoBuildExecutor.java:113) ... 5 more Caused by: java.lang.NullPointerException at org.codehaus.plexus.util.xml.pull.MXSerializer.writeElementContent(MXSerializer.java:912) at org.codehaus.plexus.util.xml.pull.MXSerializer.text(MXSerializer.java:776) at org.apache.maven.settings.io.xpp3.SettingsXpp3Writer.writeSettings(SettingsXpp3Writer.java:581) at org.apache.maven.settings.io.xpp3.SettingsXpp3Writer.write(SettingsXpp3Writer.java:71) at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.writeSettings(DefaultMavenBuilderHelper.java:489) at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.getMavenProject(DefaultMavenBuilderHelper.java:301) ... 7 more The projects were building normally sometime ago. If I try to build using maven manually on working directory, the build works. Also, I can't add new projects to the project list too, because of the same problem. Any ideas? Thanks, Henrique
Cannot build maven project
Hi List, I'm using Continuum for a time without problems. Today, however, my projects stop building with the following error: Build Error: org.apache.maven.continuum.execution.ContinuumBuildExecutorException: Error while mapping metadata. at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.updateProjectFromCheckOut(MavenTwoBuildExecutor.java:117) at org.apache.maven.continuum.core.action.UpdateProjectFromWorkingDirectoryContinuumAction.execute(UpdateProjectFromWorkingDirectoryContinuumAction.java:64) at org.apache.maven.continuum.buildcontroller.DefaultBuildController.build(DefaultBuildController.java:273) at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.executeTask(BuildProjectTaskExecutor.java:47) at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$ExecutorRunnable.run(ThreadedTaskQueueExecutor.java:103) at java.lang.Thread.run(Thread.java:613) Caused by: org.apache.maven.continuum.execution.maven.m2.MavenBuilderHelperException: Cannot build maven project from /usr/local/continuum/apps/continuum/working-directory/1/pom.xml (null). at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.getMavenProject(DefaultMavenBuilderHelper.java:339) at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.mapMetadataToProject(DefaultMavenBuilderHelper.java:112) at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.updateProjectFromCheckOut(MavenTwoBuildExecutor.java:113) ... 5 more Caused by: java.lang.NullPointerException at org.codehaus.plexus.util.xml.pull.MXSerializer.writeElementContent(MXSerializer.java:912) at org.codehaus.plexus.util.xml.pull.MXSerializer.text(MXSerializer.java:776) at org.apache.maven.settings.io.xpp3.SettingsXpp3Writer.writeSettings(SettingsXpp3Writer.java:581) at org.apache.maven.settings.io.xpp3.SettingsXpp3Writer.write(SettingsXpp3Writer.java:71) at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.writeSettings(DefaultMavenBuilderHelper.java:489) at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelper.getMavenProject(DefaultMavenBuilderHelper.java:301) ... 7 more The projects were building normally sometime ago. If I try to build using maven manually on working directory, the build works. Also, I can't add new projects to the project list too, because of the same problem. Any ideas? Thanks, Henrique -- \o/ Henrique Prange, Moleque de Idéias Educação e Tecnologia Ltda | Phone: 55-21-2710-0178 E-mail: [EMAIL PROTECTED] / \ http://www.moleque.com.br
RE: Continuum Build maven 1.0 project twice
ok thanks Steve Sopra Group. Agence de Normandie Tél. : +33 (0)2 32 81 57 57 - Fax : +33 (0)2 32 81 57 58 *: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> -Message d'origine- De : Emmanuel Venisse [mailto:[EMAIL PROTECTED] Envoyé : jeudi 31 août 2006 17:19 À : continuum-users@maven.apache.org Objet : Re: Continuum Build maven 1.0 project twice Hmm, I use the same version without problem. File an issue, and we'll look at it later. Emmanuel Pigache Steve a écrit : > firefox 1.5 > > Cordialement, > > Steve Pigache > > Sopra Group. > Agence de Normandie > Tél. : +33 (0)2 32 81 57 57 - Fax : +33 (0)2 32 81 57 58 > *: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> > > > -Message d'origine- > De : Emmanuel Venisse [mailto:[EMAIL PROTECTED] > Envoyé : jeudi 31 août 2006 17:11 > À : continuum-users@maven.apache.org > Objet : Re: Continuum Build maven 1.0 project twice > > > what is your browser? > > Emmanuel > > Pigache Steve a écrit : >> no, I run the project a lot of time and all the time the process run twice >> and I do a simple click (at the beginning I thought that I had done a >> double-click so the following time I paid attention) >> >> Steve >> >> -Message d'origine- >> De : Emmanuel Venisse [mailto:[EMAIL PROTECTED] >> Envoyé : jeudi 31 août 2006 16:22 >> À : continuum-users@maven.apache.org >> Objet : Re: Continuum Build maven 1.0 project twice >> >> >> I think you double-clicked on the build icon, because the project is >> enqueing twice with few >> milliseconds interval. >> >> INFO | jvm 1| 2006/08/31 15:56:08 | 2006-08-31 15:56:08,406 >> [SocketListener0-1] INFO >> Continuum - Enqueuing 'galion' (Build definition id=2). >> INFO | jvm 1| 2006/08/31 15:56:08 | 2006-08-31 15:56:08,686 [Thread-2] >> INFO ContinuumScm >>- Updating project: id: '1', name 'galion'. >> INFO | jvm 1| 2006/08/31 15:56:08 | 2006-08-31 15:56:08,767 >> [SocketListener0-1] INFO >> Continuum - Enqueuing 'galion' (Build definition id=2). >> >> Emmanuel >> >> Pigache Steve a écrit : >>> I joined to you my logs >>> >>> Steve >>> >>> >>> -Message d'origine- >>> De : Emmanuel Venisse [mailto:[EMAIL PROTECTED] >>> Envoyé : jeudi 31 août 2006 15:48 >>> À : continuum-users@maven.apache.org >>> Objet : Re: Continuum Build maven 1.0 project twice >>> >>> >>> Send us your logs >>> >>> Emmanuel >>> >>> Pigache Steve a écrit : >>>> Hi, >>>> >>>> I use continuum with a Maven 1 project >>>> I run the goal clean war and a custom goal >>>> When I click on the build button, the generation of the project is ok but >>>> when the generation is finish, a second build is launch at once. >>>> I don't know if it is a bug or if there is a parameter setting to do to >>>> stop the automatic second run. >>>> >>>> Thanks, >>>> Steve >>>> >>>> >> >> >> > > > >
Re: Continuum Build maven 1.0 project twice
Hmm, I use the same version without problem. File an issue, and we'll look at it later. Emmanuel Pigache Steve a écrit : firefox 1.5 Cordialement, Steve Pigache Sopra Group. Agence de Normandie Tél. : +33 (0)2 32 81 57 57 - Fax : +33 (0)2 32 81 57 58 *: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> -Message d'origine- De : Emmanuel Venisse [mailto:[EMAIL PROTECTED] Envoyé : jeudi 31 août 2006 17:11 À : continuum-users@maven.apache.org Objet : Re: Continuum Build maven 1.0 project twice what is your browser? Emmanuel Pigache Steve a écrit : no, I run the project a lot of time and all the time the process run twice and I do a simple click (at the beginning I thought that I had done a double-click so the following time I paid attention) Steve -Message d'origine- De : Emmanuel Venisse [mailto:[EMAIL PROTECTED] Envoyé : jeudi 31 août 2006 16:22 À : continuum-users@maven.apache.org Objet : Re: Continuum Build maven 1.0 project twice I think you double-clicked on the build icon, because the project is enqueing twice with few milliseconds interval. INFO | jvm 1| 2006/08/31 15:56:08 | 2006-08-31 15:56:08,406 [SocketListener0-1] INFO Continuum - Enqueuing 'galion' (Build definition id=2). INFO | jvm 1| 2006/08/31 15:56:08 | 2006-08-31 15:56:08,686 [Thread-2] INFO ContinuumScm - Updating project: id: '1', name 'galion'. INFO | jvm 1| 2006/08/31 15:56:08 | 2006-08-31 15:56:08,767 [SocketListener0-1] INFO Continuum - Enqueuing 'galion' (Build definition id=2). Emmanuel Pigache Steve a écrit : I joined to you my logs Steve -Message d'origine- De : Emmanuel Venisse [mailto:[EMAIL PROTECTED] Envoyé : jeudi 31 août 2006 15:48 À : continuum-users@maven.apache.org Objet : Re: Continuum Build maven 1.0 project twice Send us your logs Emmanuel Pigache Steve a écrit : Hi, I use continuum with a Maven 1 project I run the goal clean war and a custom goal When I click on the build button, the generation of the project is ok but when the generation is finish, a second build is launch at once. I don't know if it is a bug or if there is a parameter setting to do to stop the automatic second run. Thanks, Steve
RE: Continuum Build maven 1.0 project twice
firefox 1.5 Cordialement, Steve Pigache Sopra Group. Agence de Normandie Tél. : +33 (0)2 32 81 57 57 - Fax : +33 (0)2 32 81 57 58 *: [EMAIL PROTECTED] <mailto:[EMAIL PROTECTED]> -Message d'origine- De : Emmanuel Venisse [mailto:[EMAIL PROTECTED] Envoyé : jeudi 31 août 2006 17:11 À : continuum-users@maven.apache.org Objet : Re: Continuum Build maven 1.0 project twice what is your browser? Emmanuel Pigache Steve a écrit : > no, I run the project a lot of time and all the time the process run twice > and I do a simple click (at the beginning I thought that I had done a > double-click so the following time I paid attention) > > Steve > > -Message d'origine- > De : Emmanuel Venisse [mailto:[EMAIL PROTECTED] > Envoyé : jeudi 31 août 2006 16:22 > À : continuum-users@maven.apache.org > Objet : Re: Continuum Build maven 1.0 project twice > > > I think you double-clicked on the build icon, because the project is enqueing > twice with few > milliseconds interval. > > INFO | jvm 1| 2006/08/31 15:56:08 | 2006-08-31 15:56:08,406 > [SocketListener0-1] INFO > Continuum - Enqueuing 'galion' (Build definition id=2). > INFO | jvm 1| 2006/08/31 15:56:08 | 2006-08-31 15:56:08,686 [Thread-2] > INFO ContinuumScm >- Updating project: id: '1', name 'galion'. > INFO | jvm 1| 2006/08/31 15:56:08 | 2006-08-31 15:56:08,767 > [SocketListener0-1] INFO > Continuum - Enqueuing 'galion' (Build definition id=2). > > Emmanuel > > Pigache Steve a écrit : >> I joined to you my logs >> >> Steve >> >> >> -Message d'origine- >> De : Emmanuel Venisse [mailto:[EMAIL PROTECTED] >> Envoyé : jeudi 31 août 2006 15:48 >> À : continuum-users@maven.apache.org >> Objet : Re: Continuum Build maven 1.0 project twice >> >> >> Send us your logs >> >> Emmanuel >> >> Pigache Steve a écrit : >>> Hi, >>> >>> I use continuum with a Maven 1 project >>> I run the goal clean war and a custom goal >>> When I click on the build button, the generation of the project is ok but >>> when the generation is finish, a second build is launch at once. >>> I don't know if it is a bug or if there is a parameter setting to do to >>> stop the automatic second run. >>> >>> Thanks, >>> Steve >>> >>> > > > >
Re: Continuum Build maven 1.0 project twice
what is your browser? Emmanuel Pigache Steve a écrit : no, I run the project a lot of time and all the time the process run twice and I do a simple click (at the beginning I thought that I had done a double-click so the following time I paid attention) Steve -Message d'origine- De : Emmanuel Venisse [mailto:[EMAIL PROTECTED] Envoyé : jeudi 31 août 2006 16:22 À : continuum-users@maven.apache.org Objet : Re: Continuum Build maven 1.0 project twice I think you double-clicked on the build icon, because the project is enqueing twice with few milliseconds interval. INFO | jvm 1| 2006/08/31 15:56:08 | 2006-08-31 15:56:08,406 [SocketListener0-1] INFO Continuum - Enqueuing 'galion' (Build definition id=2). INFO | jvm 1| 2006/08/31 15:56:08 | 2006-08-31 15:56:08,686 [Thread-2] INFO ContinuumScm - Updating project: id: '1', name 'galion'. INFO | jvm 1| 2006/08/31 15:56:08 | 2006-08-31 15:56:08,767 [SocketListener0-1] INFO Continuum - Enqueuing 'galion' (Build definition id=2). Emmanuel Pigache Steve a écrit : I joined to you my logs Steve -Message d'origine- De : Emmanuel Venisse [mailto:[EMAIL PROTECTED] Envoyé : jeudi 31 août 2006 15:48 À : continuum-users@maven.apache.org Objet : Re: Continuum Build maven 1.0 project twice Send us your logs Emmanuel Pigache Steve a écrit : Hi, I use continuum with a Maven 1 project I run the goal clean war and a custom goal When I click on the build button, the generation of the project is ok but when the generation is finish, a second build is launch at once. I don't know if it is a bug or if there is a parameter setting to do to stop the automatic second run. Thanks, Steve
RE: Continuum Build maven 1.0 project twice
no, I run the project a lot of time and all the time the process run twice and I do a simple click (at the beginning I thought that I had done a double-click so the following time I paid attention) Steve -Message d'origine- De : Emmanuel Venisse [mailto:[EMAIL PROTECTED] Envoyé : jeudi 31 août 2006 16:22 À : continuum-users@maven.apache.org Objet : Re: Continuum Build maven 1.0 project twice I think you double-clicked on the build icon, because the project is enqueing twice with few milliseconds interval. INFO | jvm 1| 2006/08/31 15:56:08 | 2006-08-31 15:56:08,406 [SocketListener0-1] INFO Continuum - Enqueuing 'galion' (Build definition id=2). INFO | jvm 1| 2006/08/31 15:56:08 | 2006-08-31 15:56:08,686 [Thread-2] INFO ContinuumScm - Updating project: id: '1', name 'galion'. INFO | jvm 1| 2006/08/31 15:56:08 | 2006-08-31 15:56:08,767 [SocketListener0-1] INFO Continuum - Enqueuing 'galion' (Build definition id=2). Emmanuel Pigache Steve a écrit : > I joined to you my logs > > Steve > > > -Message d'origine- > De : Emmanuel Venisse [mailto:[EMAIL PROTECTED] > Envoyé : jeudi 31 août 2006 15:48 > À : continuum-users@maven.apache.org > Objet : Re: Continuum Build maven 1.0 project twice > > > Send us your logs > > Emmanuel > > Pigache Steve a écrit : >> Hi, >> >> I use continuum with a Maven 1 project >> I run the goal clean war and a custom goal >> When I click on the build button, the generation of the project is ok but >> when the generation is finish, a second build is launch at once. >> I don't know if it is a bug or if there is a parameter setting to do to stop >> the automatic second run. >> >> Thanks, >> Steve >> >> >
Re: Continuum Build maven 1.0 project twice
I think you double-clicked on the build icon, because the project is enqueing twice with few milliseconds interval. INFO | jvm 1| 2006/08/31 15:56:08 | 2006-08-31 15:56:08,406 [SocketListener0-1] INFO Continuum - Enqueuing 'galion' (Build definition id=2). INFO | jvm 1| 2006/08/31 15:56:08 | 2006-08-31 15:56:08,686 [Thread-2] INFO ContinuumScm - Updating project: id: '1', name 'galion'. INFO | jvm 1| 2006/08/31 15:56:08 | 2006-08-31 15:56:08,767 [SocketListener0-1] INFO Continuum - Enqueuing 'galion' (Build definition id=2). Emmanuel Pigache Steve a écrit : I joined to you my logs Steve -Message d'origine- De : Emmanuel Venisse [mailto:[EMAIL PROTECTED] Envoyé : jeudi 31 août 2006 15:48 À : continuum-users@maven.apache.org Objet : Re: Continuum Build maven 1.0 project twice Send us your logs Emmanuel Pigache Steve a écrit : Hi, I use continuum with a Maven 1 project I run the goal clean war and a custom goal When I click on the build button, the generation of the project is ok but when the generation is finish, a second build is launch at once. I don't know if it is a bug or if there is a parameter setting to do to stop the automatic second run. Thanks, Steve
Re: Continuum Build maven 1.0 project twice
Send us your logs Emmanuel Pigache Steve a écrit : Hi, I use continuum with a Maven 1 project I run the goal clean war and a custom goal When I click on the build button, the generation of the project is ok but when the generation is finish, a second build is launch at once. I don't know if it is a bug or if there is a parameter setting to do to stop the automatic second run. Thanks, Steve
Continuum Build maven 1.0 project twice
Hi, I use continuum with a Maven 1 project I run the goal clean war and a custom goal When I click on the build button, the generation of the project is ok but when the generation is finish, a second build is launch at once. I don't know if it is a bug or if there is a parameter setting to do to stop the automatic second run. Thanks, Steve
Re: How do I build maven-artifact-ant-2.0.2-dep.jar?
Fixed the issues with repository IDs and built this:
http://cvs.apache.org/maven-snapshot-repository/org/apache/maven/maven-artifact-ant/2.0.2-SNAPSHOT/maven-artifact-ant-2.0.2-20051220.231658-1-dep.jar
It successfully run through the test builds script.
This is not an officially endorsed release by the Maven PMC. Use at
your own risk :)
You shouldn't need to build maven-repository-tools (and it is not
included in the root POM - in fact it should be sandboxed). To build
shoul djust require mvn install at the root of the project, then a
follow up build maven-artifact-ant.
- Brett
On 12/21/05, Matt Raible <[EMAIL PROTECTED]> wrote:
> Hmmm, I'm able to build the JAR just fine by cd-ing into
> maven-artifact-ant and running "mvn assembly:assembly". However, when
> I copy it to my project, I get:
>
> BUILD FAILED
> C:\Source\equinox\build.xml:24: Unable to find component:
> org.apache.maven.artif
> act.repository.layout.ArtifactRepositoryLayout[default]
>
> Total time: 0 seconds
>
> I've tried running "mvn install" on a number of other modules before
> running "assembly", but I can't get maven-repository-tools to build.
> The error I'm getting is:
>
> [INFO] Failed to resolve artifact.
>
> required artifacts missing:
> org.apache.maven:maven-core:jar:2.0-SNAPSHOT
> org.apache.maven:maven-artifact:jar:2.0-SNAPSHOT
> plexus:plexus:jar:1.0-alpha-1
> org.apache.maven:maven-model:jar:2.0-SNAPSHOT
> xstream:xstream:jar:1.0-SNAPSHOT
>
> for the artifact:
> org.apache.maven:maven-repository-tools:jar:1.0-SNAPSHOT
>
> from the specified remote repositories:
> central (http://repo1.maven.org/maven2)
>
> Also, the Repository.java has a System.out.println that should
> probably be removed.
>
> Index: src/main/java/org/apache/maven/artifact/ant/Repository.java
>
> ===
>
> --- src/main/java/org/apache/maven/artifact/ant/Repository.java (revision
> 357937)
>
> +++ src/main/java/org/apache/maven/artifact/ant/Repository.java (working copy)
>
> @@ -36,7 +36,6 @@
>
>
> public String getId()
> {
> - System.out.println("Repository.getId() == " + getInstance().id);
> if (getInstance().id == null)
> {
> throw new BuildException("id must be specified for a
> repository definition");
>
> Thanks,
>
> Matt
>
> On 12/19/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> > The 2.0.2-SNAPSHOT is here:
> >
> > https://svn.apache.org/repos/asf/maven/components/branches/maven-2.0.x/
> >
> > Sorry, the dev docs haven't been updated to reflect this yet, it was a
> > recent change.
> >
> > - Brett
> >
> > On 12/20/05, Matt Raible <[EMAIL PROTECTED]> wrote:
> > > I'd like to build a version of maven-artifact-ant-2.0.2-dep.jar for
> > > distribution with a project of mine (Equinox). I could wait for the
> > > 2.0.2 release, but I'd prefer to get the release done before COB
> > > tomorrow b/c that's when I go on vacation. ;-)
> > >
> > > I checked out "maven" from svn using:
> > >
> > > svn co https://svn.apache.org/repos/asf/maven/trunks maven
> > >
> > > I've been able to build everything, but versions are showing up with
> > > version 2.1-SNAPSHOT, and I can't figure out how to build the
> > > artifact-ant-*-dep.jar. Am I checking out from the wrong repository?
> > >
> > > Thanks,
> > >
> > > Matt
> > >
> > > -
> > > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > > For additional commands, e-mail: [EMAIL PROTECTED]
> > >
> > >
> >
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: How do I build maven-artifact-ant-2.0.2-dep.jar?
Hmmm, I'm able to build the JAR just fine by cd-ing into
maven-artifact-ant and running "mvn assembly:assembly". However, when
I copy it to my project, I get:
BUILD FAILED
C:\Source\equinox\build.xml:24: Unable to find component: org.apache.maven.artif
act.repository.layout.ArtifactRepositoryLayout[default]
Total time: 0 seconds
I've tried running "mvn install" on a number of other modules before
running "assembly", but I can't get maven-repository-tools to build.
The error I'm getting is:
[INFO] Failed to resolve artifact.
required artifacts missing:
org.apache.maven:maven-core:jar:2.0-SNAPSHOT
org.apache.maven:maven-artifact:jar:2.0-SNAPSHOT
plexus:plexus:jar:1.0-alpha-1
org.apache.maven:maven-model:jar:2.0-SNAPSHOT
xstream:xstream:jar:1.0-SNAPSHOT
for the artifact:
org.apache.maven:maven-repository-tools:jar:1.0-SNAPSHOT
from the specified remote repositories:
central (http://repo1.maven.org/maven2)
Also, the Repository.java has a System.out.println that should
probably be removed.
Index: src/main/java/org/apache/maven/artifact/ant/Repository.java
===
--- src/main/java/org/apache/maven/artifact/ant/Repository.java (revision
357937)
+++ src/main/java/org/apache/maven/artifact/ant/Repository.java (working copy)
@@ -36,7 +36,6 @@
public String getId()
{
- System.out.println("Repository.getId() == " + getInstance().id);
if (getInstance().id == null)
{
throw new BuildException("id must be specified for a
repository definition");
Thanks,
Matt
On 12/19/05, Brett Porter <[EMAIL PROTECTED]> wrote:
> The 2.0.2-SNAPSHOT is here:
>
> https://svn.apache.org/repos/asf/maven/components/branches/maven-2.0.x/
>
> Sorry, the dev docs haven't been updated to reflect this yet, it was a
> recent change.
>
> - Brett
>
> On 12/20/05, Matt Raible <[EMAIL PROTECTED]> wrote:
> > I'd like to build a version of maven-artifact-ant-2.0.2-dep.jar for
> > distribution with a project of mine (Equinox). I could wait for the
> > 2.0.2 release, but I'd prefer to get the release done before COB
> > tomorrow b/c that's when I go on vacation. ;-)
> >
> > I checked out "maven" from svn using:
> >
> > svn co https://svn.apache.org/repos/asf/maven/trunks maven
> >
> > I've been able to build everything, but versions are showing up with
> > version 2.1-SNAPSHOT, and I can't figure out how to build the
> > artifact-ant-*-dep.jar. Am I checking out from the wrong repository?
> >
> > Thanks,
> >
> > Matt
> >
> > -
> > To unsubscribe, e-mail: [EMAIL PROTECTED]
> > For additional commands, e-mail: [EMAIL PROTECTED]
> >
> >
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: How do I build maven-artifact-ant-2.0.2-dep.jar?
The 2.0.2-SNAPSHOT is here: https://svn.apache.org/repos/asf/maven/components/branches/maven-2.0.x/ Sorry, the dev docs haven't been updated to reflect this yet, it was a recent change. - Brett On 12/20/05, Matt Raible <[EMAIL PROTECTED]> wrote: > I'd like to build a version of maven-artifact-ant-2.0.2-dep.jar for > distribution with a project of mine (Equinox). I could wait for the > 2.0.2 release, but I'd prefer to get the release done before COB > tomorrow b/c that's when I go on vacation. ;-) > > I checked out "maven" from svn using: > > svn co https://svn.apache.org/repos/asf/maven/trunks maven > > I've been able to build everything, but versions are showing up with > version 2.1-SNAPSHOT, and I can't figure out how to build the > artifact-ant-*-dep.jar. Am I checking out from the wrong repository? > > Thanks, > > Matt > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How do I build maven-artifact-ant-2.0.2-dep.jar?
I'd like to build a version of maven-artifact-ant-2.0.2-dep.jar for distribution with a project of mine (Equinox). I could wait for the 2.0.2 release, but I'd prefer to get the release done before COB tomorrow b/c that's when I go on vacation. ;-) I checked out "maven" from svn using: svn co https://svn.apache.org/repos/asf/maven/trunks maven I've been able to build everything, but versions are showing up with version 2.1-SNAPSHOT, and I can't figure out how to build the artifact-ant-*-dep.jar. Am I checking out from the wrong repository? Thanks, Matt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: build maven offline
> No, if you want to bootstrap then you have to be online in order to get
> any missing dependencies the first time. After you have them all you can
> bootstrap offline if you wish.
Of course but did I have to copy them in ${basedir}/lib or did I have to create the
~/.maven/repository by hand ?
Nicolas
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: build maven offline
On Tue, 2003-12-16 at 08:59, [EMAIL PROTECTED] wrote: > I try to install maven from the cvs src. The computer has no acces to > internet. My problem is that ant -f build-boostrap.xml try to download > dependencies from ibiblio. > Is there a way to use a local directory during my first maven installation > ? Or an other install methods ? No, if you want to bootstrap then you have to be online in order to get any missing dependencies the first time. After you have them all you can bootstrap offline if you wish. > Nicolas, > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] -- jvz. Jason van Zyl [EMAIL PROTECTED] http://tambora.zenplex.org In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological Society - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
build maven offline
I try to install maven from the cvs src. The computer has no acces to internet. My problem is that ant -f build-boostrap.xml try to download dependencies from ibiblio. Is there a way to use a local directory during my first maven installation ? Or an other install methods ? Nicolas, - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: build maven
While this may sound like a good idea, consider that the repository is currently 325M and contains a lot of stuff that you will never use. It would only be of real use if you were going offline for a long period of time and might need a whole lot of odd versions. Moretti, Luciano (MED) wrote: David- I don't know of it, and can't find it in my list of goals, but I am a Newbie... If you're under linux/unix I'd probably use wget to handle that. wget is really well designed to get recursive online filesystems and copy them to the local filesystem. after a little experimenting on our local repo, (as wget can't go through my proxy as it's currently configured) if you're going to try it, I'd suggest trying to use the FTP functionality, as the HTTP version generates a bunch of junk files that are created by apache (index files & graphics). Using my local repo instead of ibiblio's, here's what I came up with- Execute it from $MAVEN_HOME wget -r -nH ftp://ibiblio.org/maven -r =Recursively navigate the tree -nH=No Home- by default it'll create a directory ibiblio.org and put all the files in there.. this is not what you want. You may have to tweak the ftp statement, as I can't see what ibiblio's dir structure looks like from inside the proxy- which means you might have to add the --cut-dirs= statement to get rid of junk directories. This should create a mirror of the remote repo with in the $MAVEN_HOME/maven dir. Inspect the new repo to make sure it looks good, then use the mv command to move it to $MAVEN_HOME/repository. I'd personally suggest backing up the old repo if one exists, as I've ran into problems when completely overwriting the local repo. Good Luck- I'm pretty new at this, so this is use at your own risk, Luciano -Original Message- From: David Liles [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 01, 2003 4:54 PM To: Maven Users List Subject: RE: build maven I was under the impression that there was a generic call that could be made that basically downloads all of the available jars and places them in the repository strucuture. -Original Message- From: Moretti, Luciano (MED) [mailto:[EMAIL PROTECTED] Sent: Tue 7/1/2003 4:47 PM To: 'Maven Users List' Cc: Subject: RE: build maven Dave- Maven will automatically generate the repository on the 1st run. There is no specific step needed to build a local repository- it will fetch the needed jars off the web when they are called for. Just create your project.properties file, make sure that you have the proxy configuration stuff if you need it, and go ahead and start defining & building your project. It's one of the coolest things about maven that I've run into so far. Have fun, Luciano -Original Message- From: David Liles [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 01, 2003 4:29 PM To: [EMAIL PROTECTED] Subject: build maven I just downloaded and installed maven 1.0 b9. What is the syntax I need to use to begin the process to have maven generate all of the repository jar files? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: build maven
David- I don't know of it, and can't find it in my list of goals, but I am a Newbie... If you're under linux/unix I'd probably use wget to handle that. wget is really well designed to get recursive online filesystems and copy them to the local filesystem. after a little experimenting on our local repo, (as wget can't go through my proxy as it's currently configured) if you're going to try it, I'd suggest trying to use the FTP functionality, as the HTTP version generates a bunch of junk files that are created by apache (index files & graphics). Using my local repo instead of ibiblio's, here's what I came up with- Execute it from $MAVEN_HOME wget -r -nH ftp://ibiblio.org/maven -r =Recursively navigate the tree -nH=No Home- by default it'll create a directory ibiblio.org and put all the files in there.. this is not what you want. You may have to tweak the ftp statement, as I can't see what ibiblio's dir structure looks like from inside the proxy- which means you might have to add the --cut-dirs= statement to get rid of junk directories. This should create a mirror of the remote repo with in the $MAVEN_HOME/maven dir. Inspect the new repo to make sure it looks good, then use the mv command to move it to $MAVEN_HOME/repository. I'd personally suggest backing up the old repo if one exists, as I've ran into problems when completely overwriting the local repo. Good Luck- I'm pretty new at this, so this is use at your own risk, Luciano -Original Message- From: David Liles [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 01, 2003 4:54 PM To: Maven Users List Subject: RE: build maven I was under the impression that there was a generic call that could be made that basically downloads all of the available jars and places them in the repository strucuture. -Original Message- From: Moretti, Luciano (MED) [mailto:[EMAIL PROTECTED] Sent: Tue 7/1/2003 4:47 PM To: 'Maven Users List' Cc: Subject: RE: build maven Dave- Maven will automatically generate the repository on the 1st run. There is no specific step needed to build a local repository- it will fetch the needed jars off the web when they are called for. Just create your project.properties file, make sure that you have the proxy configuration stuff if you need it, and go ahead and start defining & building your project. It's one of the coolest things about maven that I've run into so far. Have fun, Luciano -Original Message- From: David Liles [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 01, 2003 4:29 PM To: [EMAIL PROTECTED] Subject: build maven I just downloaded and installed maven 1.0 b9. What is the syntax I need to use to begin the process to have maven generate all of the repository jar files? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: build maven
I was under the impression that there was a generic call that could be made that basically downloads all of the available jars and places them in the repository strucuture. -Original Message- From: Moretti, Luciano (MED) [mailto:[EMAIL PROTECTED] Sent: Tue 7/1/2003 4:47 PM To: 'Maven Users List' Cc: Subject: RE: build maven Dave- Maven will automatically generate the repository on the 1st run. There is no specific step needed to build a local repository- it will fetch the needed jars off the web when they are called for. Just create your project.properties file, make sure that you have the proxy configuration stuff if you need it, and go ahead and start defining & building your project. It's one of the coolest things about maven that I've run into so far. Have fun, Luciano -Original Message- From: David Liles [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 01, 2003 4:29 PM To: [EMAIL PROTECTED] Subject: build maven I just downloaded and installed maven 1.0 b9. What is the syntax I need to use to begin the process to have maven generate all of the repository jar files? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: build maven
Dave- Maven will automatically generate the repository on the 1st run. There is no specific step needed to build a local repository- it will fetch the needed jars off the web when they are called for. Just create your project.properties file, make sure that you have the proxy configuration stuff if you need it, and go ahead and start defining & building your project. It's one of the coolest things about maven that I've run into so far. Have fun, Luciano -Original Message- From: David Liles [mailto:[EMAIL PROTECTED] Sent: Tuesday, July 01, 2003 4:29 PM To: [EMAIL PROTECTED] Subject: build maven I just downloaded and installed maven 1.0 b9. What is the syntax I need to use to begin the process to have maven generate all of the repository jar files? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
build maven
I just downloaded and installed maven 1.0 b9. What is the syntax I need to use to begin the process to have maven generate all of the repository jar files?
