RE: New Maven Site is Live
+1, I'm interested in too. And thanks to the Maven team, the website is very powerful. Gab -Message d'origine- De : Martijn Dashorst [mailto:[EMAIL PROTECTED] Envoyé : mardi 15 mars 2005 16:05 À : Maven Users List Objet : Re: New Maven Site is Live James Mitchell wrote: > Fantastic! Very nice job Brett! > > Is there any way you can publish a zip of the site for offline > browsing? I've needed that on many occasions. If not, would you mind > if I put one together and publish it? +1, especially the plugin documentation would be nice to have available for offline browsing. Martijn Dashorst - 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: having troubles with maven RC2
I verified in maven rc2, and I didn't find this jar in default distribution (ie in lib folder). -Message d'origine- De : nicolas De Loof [mailto:[EMAIL PROTECTED] Envoyé : mercredi 24 mars 2004 14:55 À : Maven Users List Objet : Re: having troubles with maven RC2 OK about that, but didn't maven dependency ensure this when runing the eclipse plugin ? I re-installed maven RC2 and deleted my local repo for test. without the cactus plugin, eclipse:generate-classpath goal works fine with cactus plugin 1.6dev-20040226, I get this ClassNotFoundException Do I need to use and earlier cactus plugin version ? Nico. Barbier Gabriel a écrit : >this jar must be place in your folder >${MAVEN_HOME_LOCAL}/repository/commons-jelly/jars/ and not in folder where maven is >installed. > >-Message d'origine- >De : nicolas De Loof [mailto:[EMAIL PROTECTED] >Envoyé : mercredi 24 mars 2004 14:46 >À : Maven Users List >Objet : having troubles with maven RC2 > > >Hello, > >I'm trying to use maven RC2 on some of our projects that are using RC1. > >Everything looks good (build, test, cactus with new cactus-maven >plugin...), but I get some troubles with maven-eclipse plugin : > >maven eclipse:generate-classpath fails with this error : > > __ __ >| \/ |__ _Apache__ ___ >| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ >|_| |_\__,_|\_/\___|_||_| v. 1.0-rc2 > >Could not find the class: org.apache.commons.jelly.tags.xml.XMLTagLibrary >java.lang.ClassNotFoundException: >org.apache.commons.jelly.tags.xml.XMLTagLibrary >at java.net.URLClassLoader$1.run(URLClassLoader.java:199) > > > >I added commons-jelly-tags-xml-20030211.142705.jar to my >${maven-home}/bin and it works >Has it been omitted from mavenRC2 dist or are eclipse-plugin >dependencies broken with RC2 ? > >I used windows Exe installer to get maven RC2. > >Nico. > > >- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > >- >To unsubscribe, e-mail: [EMAIL PROTECTED] >For additional commands, e-mail: [EMAIL PROTECTED] > > > - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: having troubles with maven RC2
this jar must be place in your folder ${MAVEN_HOME_LOCAL}/repository/commons-jelly/jars/ and not in folder where maven is installed. -Message d'origine- De : nicolas De Loof [mailto:[EMAIL PROTECTED] Envoyé : mercredi 24 mars 2004 14:46 À : Maven Users List Objet : having troubles with maven RC2 Hello, I'm trying to use maven RC2 on some of our projects that are using RC1. Everything looks good (build, test, cactus with new cactus-maven plugin...), but I get some troubles with maven-eclipse plugin : maven eclipse:generate-classpath fails with this error : __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-rc2 Could not find the class: org.apache.commons.jelly.tags.xml.XMLTagLibrary java.lang.ClassNotFoundException: org.apache.commons.jelly.tags.xml.XMLTagLibrary at java.net.URLClassLoader$1.run(URLClassLoader.java:199) I added commons-jelly-tags-xml-20030211.142705.jar to my ${maven-home}/bin and it works Has it been omitted from mavenRC2 dist or are eclipse-plugin dependencies broken with RC2 ? I used windows Exe installer to get maven RC2. Nico. - 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: [maven] Re: why repository is set per user?
Hi Frederico, The rc1 allows you to share repository with the variable MAVEN_HOME_LOCAL (in fact each user must set this variable) Gab. -Message d'origine- De : Federico Spinazzi [mailto:[EMAIL PROTECTED] Envoyé : mercredi 17 décembre 2003 15:50 À : Maven Users List Objet : Re: [maven] Re: why repository is set per user? Jason van Zyl wrote: >On Wed, 2003-12-17 at 08:29, Federico Spinazzi wrote: > > >[..] >I can't say I understand your question, what other possibilities are >there for a single user on a single machine? > Jason, it looks like in beta-9 the repository was %MAVEN_HOME%/repository so by default it was shared by all the users on the same computer. Now rc1 uses the user.home system property, not too friendly in windows as it has an awful name (c:\documents and settings\user) and doesn't map to the HOME directory but to the USERPROFILE one. Friendliness is not the point, the point is that each user has a copy of the repository. The solution used in beta-9 is better, IMHO. Thanks, Federico - 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: Réf. : Re: Réf. : RE: Plugin dependancies
In fact, I select all plugin I need in the list provided by command "maven -g". Yet, I think Tim's solution is better, leech the site iBiblio and redirect remote repository to it. -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Envoyé : mardi 16 décembre 2003 15:29 À : [EMAIL PROTECTED] Objet : Réf. : Re: Réf. : RE: Plugin dependancies Yes, but it would require I know all the plugins i would use when i donwload maven. Extranet [EMAIL PROTECTED] - 16/12/2003 15:25 Veuillez répondre à [EMAIL PROTECTED] Pour : users cc : Objet : Re: Réf. : RE: Plugin dependancies Dont forget that all the required jars of your project are only downloaded once. If maven is able to find them in your repository after that it will not attempt to download them again. So you can connect to the internet once.. download maven... build your project one time and it will not need to connect to the internet for any build after that unless you change a dependency in your build or delete a dependency from your repository. -Tim [EMAIL PROTECTED] wrote: >Thanks but if this mean looking throught all plugins and download all the >jars one by one (what I think), my question was exactly to avoid such a >thing > > > > > >Extranet >[EMAIL PROTECTED] - 16/12/2003 15:11 > > >Veuillez répondre à [EMAIL PROTECTED] >Pour : users > >cc : > > >Objet : RE: Plugin dependancies > > >You can download the jars you need from ibiblio (try a search through >google, for example ant-1.5.1.jar) and install them in your local >repository. >The folder structure look like : >${MAVEN_HOME_LOCAL}\repository\ant\jars >for the example ant-1.5.1.jar > >-Message d'origine- >De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] >Envoyé : mardi 16 décembre 2003 09:21 >À : [EMAIL PROTECTED] >Objet : Plugin dependancies > > > >I would install maven on a machine that is generally not connected to >internet so I can't download the dependancy jar at runtime, is there a goal >(or a command) to download all the dependancies required by ALL the plugins >(so i could connect the machine to internet, download maven, download all >the jars and disconnect it ) ? > >Julien > > > > > >This message and any attachments (the "message") is intended solely for the >addressees and is confidential. >If you receive this message in error, please delete it and immediately >notify the sender. Any use not in accord with >its purpose, any dissemination or disclosure, either whole or partial, is >prohibited except formal approval. >The internet can not guarantee the integrity of this message. BNP PARIBAS >(and its subsidiaries) shall (will) not >therefore be liable for the message if modified. > >- > >Ce message et toutes les pieces jointes (ci-apres le "message") sont >etablis a l'intention exclusive de ses >destinataires et sont confidentiels. Si vous recevez ce message par erreur, >merci de le detruire et d'en avertir >immediatement l'expediteur. Toute utilisation de ce message non conforme a >sa destination, toute diffusion >ou toute publication, totale ou partielle, est interdite, sauf autorisation >expresse. L'internet ne permettant pas >d'assurer l'integrite de ce message, BNP PARIBAS (et ses filiales) >decline(nt) toute responsabilite au titre de ce >message, dans l'hypothese ou il aurait ete modifie. > > >- >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] > > > > > > > > > > >This message and any attachments (the "message") is intended solely for the addressees and is confidential. >If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with >its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. >The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not >therefore be liable for the message if modified. > >- > >Ce message et toutes les pieces jointes (ci-apres le "message") sont etablis a l'intention exclusive de ses >destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le detruire et d'en avertir >immediatement l'expediteur. Toute utilisation de ce message non conforme a sa destination, toute diffusion >ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L'internet ne permettant pas >d'assurer l'integrite de ce message, BNP PARIBAS (et ses filiales) decline(nt) toute responsabilite au titre de ce >message, dans l'hypothese ou il aurait ete modifie. > > >-
RE: Plugin dependancies
You can download the jars you need from ibiblio (try a search through google, for example ant-1.5.1.jar) and install them in your local repository. The folder structure look like : ${MAVEN_HOME_LOCAL}\repository\ant\jars for the example ant-1.5.1.jar -Message d'origine- De : [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Envoyé : mardi 16 décembre 2003 09:21 À : [EMAIL PROTECTED] Objet : Plugin dependancies I would install maven on a machine that is generally not connected to internet so I can't download the dependancy jar at runtime, is there a goal (or a command) to download all the dependancies required by ALL the plugins (so i could connect the machine to internet, download maven, download all the jars and disconnect it ) ? Julien This message and any attachments (the "message") is intended solely for the addressees and is confidential. If you receive this message in error, please delete it and immediately notify the sender. Any use not in accord with its purpose, any dissemination or disclosure, either whole or partial, is prohibited except formal approval. The internet can not guarantee the integrity of this message. BNP PARIBAS (and its subsidiaries) shall (will) not therefore be liable for the message if modified. - Ce message et toutes les pieces jointes (ci-apres le "message") sont etablis a l'intention exclusive de ses destinataires et sont confidentiels. Si vous recevez ce message par erreur, merci de le detruire et d'en avertir immediatement l'expediteur. Toute utilisation de ce message non conforme a sa destination, toute diffusion ou toute publication, totale ou partielle, est interdite, sauf autorisation expresse. L'internet ne permettant pas d'assurer l'integrite de ce message, BNP PARIBAS (et ses filiales) decline(nt) toute responsabilite au titre de ce message, dans l'hypothese ou il aurait ete modifie. - 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: Newbee Question
Thanks, it works with Gab. -Message d'origine- De : Ole Matzura [mailto:[EMAIL PROTECTED] Envoyà : lundi 24 novembre 2003 11:28 à : Maven Users List Objet : SV: Newbee Question Hi.. you need to import the ant namespace, ie set the root element to good luck! regards, Ole -Ursprungligt meddelande- FrÃn: Barbier Gabriel [mailto:[EMAIL PROTECTED] Skickat: mà 2003-11-24 11:20 Till: Maven Users List Kopia: Ãmne: RE: Newbee Question Hi, I test this help in my maven.xml : And i have this error : | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-rc1-SNAPSHOT Fatal Error [line 7, row 58]: The prefix "ant" for element "ant:path" is not bound. An XML error occurred parsing the file 'D:\JAGUAR\JAGUAR_dev\maven.xml' plugin org.xml.sax.SAXParseException: The prefix "ant" for element "ant:path" is not bound. at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at javax.xml.parsers.SAXParser.parse(Unknown Source) at org.apache.maven.plugin.PluginCacheManager.parse(PluginCacheManager.java:365) at org.apache.maven.plugin.PluginManager.loadJellyScript(PluginManager.java:481) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:398) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:348) at org.apache.maven.cli.App.doMain(App.java:543) at org.apache.maven.cli.App.main(App.java:1109) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) org.xml.sax.SAXParseException: The prefix "ant" for element "ant:path" is not bound. at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.commons.jelly.parser.XMLParser.parse(XMLParser.java:320) at org.apache.maven.jelly.JellyUtils.compileScript(JellyUtils.java:209) at org.apache.maven.jelly.JellyUtils.compileScript(JellyUtils.java:175) at org.apache.maven.jelly.JellyUtils.runScript(JellyUtils.java:112) at org.apache.maven.jelly.JellyUtils.runScript(JellyUtils.java:140) at org.apache.maven.plugin.PluginManager.loadJellyScript(PluginManager.java:491) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:398) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:348) at org.apache.maven.cli.App.doMain(App.java:543) at org.apache.maven.cli.App.main(App.java:1109) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) Total time: 7 seconds Finished at: Mon Nov 24 11:17:49 CET 2003 If anyone use a multiple source directories specification, can you show me an exemple or tell me where is my mistake. Thanks. Gab. -Message d'origine- De : Dominik Roblek [mailto:[EMAIL PROTECTED] Envoyà : lundi 10 novembre 2003 08:07 à : Maven Users List Objet : Re: Newbee Question Look at the http://wiki.codehaus.org/maven/FrequentlyAskedQuestions under "4.7. How do I specify multiple source directories in a single POM (project.xml)?". Dominik --- "Rauf, Saleem" <[EMAIL PROTECTED]> wrote: > Its not possible to specify multiple source > directories in your project.xml. > However you can add source paths to a project; this > is done in any > plugin that generates source, eg this snippet from > the antlr pl
RE: Newbee Question
Hi, I test this help in my maven.xml : And i have this error : | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.0-rc1-SNAPSHOT Fatal Error [line 7, row 58]: The prefix "ant" for element "ant:path" is not bound. An XML error occurred parsing the file 'D:\JAGUAR\JAGUAR_dev\maven.xml' plugin org.xml.sax.SAXParseException: The prefix "ant" for element "ant:path" is not bound. at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at javax.xml.parsers.SAXParser.parse(Unknown Source) at org.apache.maven.plugin.PluginCacheManager.parse(PluginCacheManager.java:365) at org.apache.maven.plugin.PluginManager.loadJellyScript(PluginManager.java:481) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:398) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:348) at org.apache.maven.cli.App.doMain(App.java:543) at org.apache.maven.cli.App.main(App.java:1109) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) org.xml.sax.SAXParseException: The prefix "ant" for element "ant:path" is not bound. at org.apache.xerces.parsers.AbstractSAXParser.parse(Unknown Source) at org.apache.commons.jelly.parser.XMLParser.parse(XMLParser.java:320) at org.apache.maven.jelly.JellyUtils.compileScript(JellyUtils.java:209) at org.apache.maven.jelly.JellyUtils.compileScript(JellyUtils.java:175) at org.apache.maven.jelly.JellyUtils.runScript(JellyUtils.java:112) at org.apache.maven.jelly.JellyUtils.runScript(JellyUtils.java:140) at org.apache.maven.plugin.PluginManager.loadJellyScript(PluginManager.java:491) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:398) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:348) at org.apache.maven.cli.App.doMain(App.java:543) at org.apache.maven.cli.App.main(App.java:1109) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:324) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) Total time: 7 seconds Finished at: Mon Nov 24 11:17:49 CET 2003 If anyone use a multiple source directories specification, can you show me an exemple or tell me where is my mistake. Thanks. Gab. -Message d'origine- De : Dominik Roblek [mailto:[EMAIL PROTECTED] Envoyé : lundi 10 novembre 2003 08:07 À : Maven Users List Objet : Re: Newbee Question Look at the http://wiki.codehaus.org/maven/FrequentlyAskedQuestions under "4.7. How do I specify multiple source directories in a single POM (project.xml)?". Dominik --- "Rauf, Saleem" <[EMAIL PROTECTED]> wrote: > Its not possible to specify multiple source > directories in your project.xml. > However you can add source paths to a project; this > is done in any > plugin that generates source, eg this snippet from > the antlr plugin: > location="${maven.build.dir}/antlr"/> > > refid="maven.antlr.compile.src.set"/> > You'd put this in your maven.xml. > > Can some please give me an example code how to use > this idea above, Please.. > I am multiple source directories in your > project.xml. > > The following maven.xml file: >default="nightly-build" > xmlns:maven="maven" > xmlns:j="jelly:core" > xmlns:u="jelly:util"> > > nightly-build >location="${maven.build.dir}/antlr"/> > > > refid="maven.antlr.compile.src.set"/> > > value="compile,test,site:generate" /> > ${maven.build.dir} > > delim=",">${goals} > indexVar="goalNumber"> > Now attaining goal number ${goalNumber}, which > is ${goal} > > > > > compile > > > test > > > > > > > > > -Original Message- > From: [EMAIL PROTECTED] > [mailto:[EMAIL PROTECTED] > Sent: Sun 11/09/2003 12:28 AM > To: Maven Users List > Cc: > Subject: Re: classpath > > > > > -- > dIon Gillard, Multitask Consulting > Blog: http://blogs.codehaus.org/people/dion/ > Pub > Key:http://blogs.codehaus.org/people/dion/public-key.asc >
RE: [java:compile] RC1 and ${maven.compile.source}
To avoid this problem you can use in file project.properties : maven.compile.source=1.4 maven.compile.target=1.4 maven.javadoc.source=1.4 maven.test.source=1.4 gab. -Message d'origine- De : Rademacher Tobias [mailto:[EMAIL PROTECTED] Envoyé : mercredi 19 novembre 2003 11:25 À : '[EMAIL PROTECTED]' Cc : Rothermel Wolfgang Objet : [java:compile] RC1 and ${maven.compile.source} Hi Folks, I'm upgraded to RC1 and have now problems compiling a project which uses assert keyword. Whe I set ${maven.compile.source} to 1.4 the problem should be compilable as in beta-9. Has the property name changed or is this a bug? Here the output I got: java:compile: [echo] Compiling to C:\java\project\repos\wps-manwe/target/classes [javac] Compiling 26 source files to C:\java\project\repos\wps-manwe\target\ classes javac: source release 1.4 requires target release 1.4 Usage: javac where possible options include: -gGenerate all debugging info -g:none Generate no debugging info -g:{lines,vars,source}Generate only some debugging info -nowarn Generate no warnings -verbose Output messages about what the compiler is doing -deprecation Output source locations where deprecated APIs are us ed -classpath Specify where to find user class files -sourcepath Specify where to find input source files -bootclasspath Override location of bootstrap class files -extdirsOverride location of installed extensions -d Specify where to place generated class files -encoding Specify character encoding used by source files -source Provide source compatibility with specified release -target Generate class files for specific VM version -help Print a synopsis of standard options Whats wrong? Thx Toby - 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]