Re: little boring things of maven
On Mon, 29 Dec 2003, at 02:17:49 [GMT -0200] José Luiz Junior wrote: > 1) The biggest, and I thing that version 1.0 cannot be release without a > patch is: Every jar:jar, ejb:ejb, war:war maven always run test:test. I > did a patch in my maven but it is not an official release...I agree that > we need to run test... But if I change a JSP, for example, I need to > war:war (or war:webapp) to see changes and maven run 3-6 minutes of test > (I have a lot of tests) A property like test.alwaysrun or > war.runtest will be wonderful. Set maven.test.skip to 'true' before invoking the other goals, and you'll skip the tests. You'll still enter test:test, but it won't run the tests. Jeff -- mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
When to add or not add dependencies?
Hi, I just added all the dependencies that were not in my local repository to my remote repository. BTW, the JARS in the local repository were downloaded when I initiated my first 'maven java:compile'. Now, does one have to add these dependencies to the project.xml too? At this time, I'm getting error messages when I perform the above mentioned command. It's not clear in the document when and when not to add dependencies to the project.xml file. Thanks in advance for any development advice in regards to this issue. -Conrad - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
little boring things of maven
I love maven, really, I was a heavy ant user that met maven one day. But Maven has few things that I don't like. 1) The biggest, and I thing that version 1.0 cannot be release without a patch is: Every jar:jar, ejb:ejb, war:war maven always run test:test. I did a patch in my maven but it is not an official release...I agree that we need to run test... But if I change a JSP, for example, I need to war:war (or war:webapp) to see changes and maven run 3-6 minutes of test (I have a lot of tests) A property like test.alwaysrun or war.runtest will be wonderful. In jar:jar case is EJB I need to generate jar:jar/ejb:ejb to deploy and see a little change that I did... and 5-10 minutes of test 2) Other thing is... plugin's default properties are not loaded until I use the plugin I need some values to write other values at build.properties. 3) And we have ejb:install and it does not have ejb:install-client. I saw at issue track and I believe that it will be patched. With admiration and respect, Jose Luiz Junior, a Maven lover. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Configuring the remote repository?
Hi, is it possible to automatically generate the dependencies from a list of JAR files? Thanks in advance, -Conrad > It should go in project.properties if you want everyone to use the > same repo. The build.properties file is for local developer overrides. > > If I understand your second question, the answer is yes, you do need > to list all your dependencies in project.xml. The repo property just > tells where to look for the jars. You still need to define someplace > what jars your project actually uses. > > Jeff > > On Mon, 29 Dec 2003, at 20:49:24 [GMT GMT] [EMAIL PROTECTED] wrote: > > > Hi, thanks for the reposnse to my post. Anyway, I added the > > following name value pair to my 'project.properties'. Should this go > > into the build properties instead? Now, does one still need to add > > the dependencies to the project.xml? BTW, this application requires > > quite a few dependent JARS and i hope that I don't have to add them > > to this file. > > > Thanks in advance, > > > -Conrad > > >> maven.repo.remote property (comma separated list) : > >> > >> maven.repo.remote=http://ibiblio.org/maven,http://your.server.1/,http://maven-plugins.sf.net/ > >> > >> http://maven.apache.org/reference/user-guide.html#Behavioural%20Properties > >> > >> -- gd > >> > >> [EMAIL PROTECTED] wrote: > >> > >> >Hi, how does one configure the location of the remote repositoty? > >> > > >> >Thanks, > >> > > >> >-Conrad > >> > > >> > > >> >- > >> >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] > > -- > mailto:[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]
multiple remote repos
i have some digging and see some chatter about maven having the ability to define multiple remote repos. Has there been anything implemented in this reguard? TIA -ScottTavares- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: PostGoal variable context
Stephen,
jar:snapshot (jar-plugin 1.3) calls maven:snapshot that puts a variable
named snapshotSignature into the plugin context. then it sets
maven.final.name to snapshotSignature. so you can look it up by querying
the plugin context :
maven.final.name:
${pom.getPluginContext('maven-jar-plugin').findVariable('maven.final.name')}.jar
works under 1.0-rc1 with maven-jar-plugin-1.3
-- gd
Stephen Colebourne wrote:
I am trying to build another jar file as part of the main jar build (commons
collections).
The following extract maven xml works fine for a normal build. When I do
jar:snapshot however, the maven.build.name is reset from the snapshot to the
original between the actual jar:jar goal and the postGoal. As a result, the
unjar fails. This isn't very useful. Am I doing something wrong??
Stephen
-
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]
PostGoal variable context
I am trying to build another jar file as part of the main jar build (commons collections). The following extract maven xml works fine for a normal build. When I do jar:snapshot however, the maven.build.name is reset from the snapshot to the original between the actual jar:jar goal and the postGoal. As a result, the unjar fails. This isn't very useful. Am I doing something wrong??
Can I suppress the junit output?
How can I fix things so I don't get the 5+ lines of output on the console for every single testcase? I really only want to know when a test fails. The xml reports are fine for when I'm building the site, but 99% of the time I'm building during new development and just want failing testcases. In my ant build files, I used to run the junit task with the "brief" formatter. That's kind of what I'm looking for here. What are my options? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Configuring the remote repository?
It should go in project.properties if you want everyone to use the same repo. The build.properties file is for local developer overrides. If I understand your second question, the answer is yes, you do need to list all your dependencies in project.xml. The repo property just tells where to look for the jars. You still need to define someplace what jars your project actually uses. Jeff On Mon, 29 Dec 2003, at 20:49:24 [GMT GMT] [EMAIL PROTECTED] wrote: > Hi, thanks for the reposnse to my post. Anyway, I added the > following name value pair to my 'project.properties'. Should this go > into the build properties instead? Now, does one still need to add > the dependencies to the project.xml? BTW, this application requires > quite a few dependent JARS and i hope that I don't have to add them > to this file. > Thanks in advance, > -Conrad >> maven.repo.remote property (comma separated list) : >> >> maven.repo.remote=http://ibiblio.org/maven,http://your.server.1/,http://maven-plugins.sf.net/ >> >> http://maven.apache.org/reference/user-guide.html#Behavioural%20Properties >> >> -- gd >> >> [EMAIL PROTECTED] wrote: >> >> >Hi, how does one configure the location of the remote repositoty? >> > >> >Thanks, >> > >> >-Conrad >> > >> > >> >- >> >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] -- mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Configuring the remote repository?
Hi, thanks for the reposnse to my post. Anyway, I added the following name value pair to my 'project.properties'. Should this go into the build properties instead? Now, does one still need to add the dependencies to the project.xml? BTW, this application requires quite a few dependent JARS and i hope that I don't have to add them to this file. Thanks in advance, -Conrad > maven.repo.remote property (comma separated list) : > > maven.repo.remote=http://ibiblio.org/maven,http://your.server.1/,http://maven-plugins.sf.net/ > > http://maven.apache.org/reference/user-guide.html#Behavioural%20Properties > > -- gd > > [EMAIL PROTECTED] wrote: > > >Hi, how does one configure the location of the remote repositoty? > > > >Thanks, > > > >-Conrad > > > > > >- > >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]
Maven and J2ME
Hello all, I am evaluating Maven for a company wide setup and it's looking pretty good at the moment, but the only problem I have run into is J2ME. We occassionally have J2ME projects and the problem is that my pilot project is one of them. I have been unable to find any mention anywhere on how to get Maven up and running with J2ME so I dug around some and tried some stuff but that failed. Basically I tried to set the bootclasspath option in my project.properties file so that it used the appropriate classes.zip. Now that worked just fine for my src/java tree, but it failed miserably on my test tree, because that needs some of the IO classes. Does anyone have any experience with this? The problem is that I have a zip file with both java.lang classes and other stuff. I only need the classes.zip when I compile my src files and I need the other stuff in the zip file with a normal JDK when compiling junit tests. Thanks, Erwin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Small Maven war Question...
Deepak Sable wrote: hi , When i generate the .war file using maven war from the command line. the war is generated but wihout the jsp and other files(other then .class). was wondering am i missing somethign bcoz of why the jsp pages are not being included in the .war file. Set up maven.war.src.includes and maven.war.src.excludes in project.properties also a second question after the docs are generated. i dont get any data in the developer activity report page and the cvs-usage.html page. i mean the pages are generated but with no data in it even though i have included cvs info in the project.xml Probabely you have to be logged in to CVS, (cvs login) befere you do report. -- Norbert Pabiś - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
