Re: release:prepare errors
This is also what we are doing, except that we never check-in the x.x.xversion (it goes only in the tag). This way, nobody else - including Continuum - will work on the version x.x.x and produce a x.x.x-stampedartifact that would erroneously look like a release. 1. Check that all dependencies are non-SNAPSHOT 2. Replace version x.x.x-SNAPSHOT with x.x.x 3. Tag FROM THE WORKING COPY 4. Replace version x.x.x with x.x.x+1-SNAPSHOT 5. Check in 6. (Optionnaly deploy, but Continuum will do it for us) 7. Check out tag 8. Deploy tag On 3/10/06, Brian E. Fox [EMAIL PROTECTED] wrote: This is exactly what I have to do. I use a tool to find and replace across files. Fortunately, we are using 4 digit build numbers so I know I'm not replacing something incorrectly (example: 2.1.0.7). So it goes like this: Replace x.x.x.x-SNAPSHOT with x.x.x.x Check in. Tag. Replace x.x.x.x with x.x.x.x+1-SNAPSHOT Check in. Deploy. Check out tag. Deploy (doing all the above as fast as possible so continuum doesn't find mismatched versions) -Original Message- From: Barrie Treloar [mailto:[EMAIL PROTECTED] Sent: Thursday, March 09, 2006 10:08 PM To: Maven Users List Subject: Re: release:prepare errors On 3/10/06, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: The pom in the scm, I then check out the project then, I can run maven from the work directory. Then the release:prepare replaces the current pom with the tag pom that is generated. Can someone help with this problem? Thanks, Caveat: I have not done any of this yet, we are nowhere near needing to build a release, however I scraped this off the list somewhere so I am including it here in case it offers you any help. I have no idea whether the release plugin has had the known issues fixed. I would suggest checking JIRA. Notes I have collected follow: - Given that the mvn release:prepare / perform still has known major issues. Does anyone out there have a reliable method for doing a manual release. e.g . 1) Can you just do a search and replace version1.0-SNAPSHOT/version replace with version1.0/version I guess you have to look at each dependency first ? 2) Then check into SCM 3) Then do you do a CVS label / tag 4) Then do you do a second search and replace for version1.0 version1.0/version replace with version1.1-SNAPSHOT/version Again I guess you have to look at all dependencies first ? 5) Then check into SCM again ? Any thoughts on how to semi automate the replace steps ? or at least document how to do a manual mvn release. - 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]
[m2] defining new lifecycle / packaging with maven-plugin-tools-ant
Hi, some of you might have followed my trials to setup a new project [1]: I'm now trying to work on the first step, which is using the assembly plugin to stuff all generated sources into a zip/jar file. The problem is, that during the build lifecycle I actually only want two plugins to be executed: 1) my custom plugin in the generate-sources phase and 2) the assembly plugin for packaging. How can that be achieved? When I define only those plugins and no packaging, maven defaults to the jar packaging, which is invoking a lot of other unwanted plugins/mojos. I tried to define a new packaging in my plugin for the source code generation, but I don't know how to do that. I was following the giode [2] so far, but there isn't explained how the plexus/components.xml can be integrated, or if it's possible at all. [1] http://www.mail-archive.com/users@maven.apache.org/msg37006.html [2] http://maven.apache.org/guides/plugin/guide-ant-plugin-development.html Thanks for your feedback. Andreas Ebbert-Karroum Software Design Engineer - Nokia Networks Services / Middleware phone: +49-211-94123928, fax: +49-211-94123838 Heltorfer Straße 1, 40472 Düsseldorf, Germany This message is confidential. If you have received this message in error, please delete it from your system. You should not copy it for any purpose, or disclose its contents to any other person. Internet communications are not secure and therefore Nokia GmbH does not accept legal responsibility for the contents of this message as it has been transmitted over a public network. Thank you. Nokia GmbH, Nokia Networks is a German Company. Further information about the Company is available from its principal offices at Heltorferstrasse 1, D-40472, Düsseldorf, Germany and from the website at http://www.nokia.com/
Re: test report in m2
I agree. You shoudn't specify a plugin version unless you really need to (for instance you want to use a snapshot version). This way Maven will tell you when there is a new version released and ask you if you want to install it and use it from now on. On 3/11/06, Wayne Fay [EMAIL PROTECTED] wrote: Sorry about the /src/tests mistake -- you're right, the correct directory is /src/test. I'm not specifying the version number as you are... Mine plugin groupIdorg.codehaus.mojo/groupId artifactIdsurefire-report-maven-plugin/artifactId /plugin Yours: plugin groupIdorg.codehaus.mojo/groupId artifactIdsurefire-report-maven-plugin/artifactId version2.0-beta-1/version /plugin Perhaps this is causing your issue? I'm not sure what the most recent release is but according to my local user repo I've got: 2.0-20060106.225541-3 2.0-alpha-2 2.0-beta-4 2.0-SNAPSHOT Without specifying a version, I'm getting maven-site-plugin:2.0-beta-4. I'd assume there are updates between beta-1 and beta-4 that you are missing, which is leading to some of your troubles. Wayne On 3/10/06, Miguel Griffa [EMAIL PROTECTED] wrote: I alsgo have all test classes named FooTest but the dir is src/test/java (note singluar test, not plural) however, if I run mvn test, it will take 20' to run all tests, but when I run site, tests are run, but report says 0 tests. I noticed there are not TESTfoo.xml in the generated reports dir, but I guess that should be automatic, shouldn't it? you didn't have to set anything special, did you? plugin is defined like this reporting plugins plugin groupIdorg.codehaus.mojo/groupId artifactIdsurefire-report-maven-plugin/artifactId version2.0-beta-1/version /plugin On 3/10/06, Wayne Fay [EMAIL PROTECTED] wrote: I also use it with zero issues. Tests are in src/tests/java and named BlahVOTest.java with methods setUp, tearDown, and testBlah1, testBlah2, etc. I can only think you are doing something strange, Miguel. ;-) Wayne On 3/10/06, Alexandre Poitras [EMAIL PROTECTED] wrote: I use it without any problems. What are you test methods names ? textXXX ? Or you prefer to use test suites? On 3/10/06, Miguel Griffa [EMAIL PROTECTED] wrote: anyone being able to use surfire test report in m2? I have a project with 2000+ tests, with m2 dir layout and test report says all zero... any ideas? -- Miguel Griffa Skype: miguel.griffa Y!: m_griffa MSN: [EMAIL PROTECTED] Cell: 15-62519355 -- Alexandre Poitras Québec, Canada - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Miguel Griffa Skype: miguel.griffa Y!: m_griffa MSN: [EMAIL PROTECTED] Cell: 15-62519355 -- Alexandre Poitras Québec, Canada - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: how to point 'mvn archetype:create' at internal repository?
Thanks for the reply. I'm afraid I still can't get this to work. The page you refer to gives instructions for using a remote (internal) repository from within an existing project, but not when creating a new project from an archetype. As you say, it looks as though I need to add something to my (user or global) settings.xml, as desribed in http://maven.apache.org/guides/ mini/guide-multiple-repositories.html . So, I put the following into my ~/.m2/settings.xml: settings profiles profile iddevt-profile/id repositories repository idinternal-rep/id nameInternal Repository/name urlfile:///usr/local/mvnrep/url /repository /repositories /profile /profiles activeProfiles activeProfiledevt-profile/activeProfile /activeProfiles /settings When I run 'mvn archetype:create ...' or 'mvn -Pdevt-profile ...' it attempts to download the archetype from http://repo1.maven.org/ maven2, and appears to have no knowledge of the repository specified above. PLEASE COULD SOMEBODY CHECK THAT THIS DOES IN FACT WORK for maven 2.0.2, making sure that they are not in fact downloading the archetype from their local repository. Thanks, Rob On 10 Mar 2006, at 00:25, John Tolentino wrote: Hi Rob, This might help: http://maven.apache.org/guides/introduction/ introduction-to-repositories.html If you've already done that, then just include your internal repository in your settings.xml repositories section and use the archetype. - John Rob Dickens wrote: Dear list, Using the instructions on the Guide to Creating Archetypes webpage, I have created an archetype, and deployed it to my internal repository (file:///usr/local/mvnrep say). Please could someone let me in on how to now access it. Many thanks, Rob - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: [m2] Internal Repositories
On 3/10/06, Treloar, Barrie [EMAIL PROTECTED] wrote: On 3/10/06, Khin, Gerald [EMAIL PROTECTED] wrote: Hi! Being a newbie to maven, I wonder if this idea could work: [del] The first question that springs to mind is Why? What benefit is there to restrict maven in this way, it makes no sense. My idea behind is to conserve all things I needed to build my project so that once my product will be released, that I will be still able to build my project in case, even in a couple of years, completely independent of the availability of the central repository and its public mirrors. Control the version numbers of artifacts that you have sanctioned is a better way of enforcing standards in the organisation that banning maven from downloading more plugins. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: deploy war to remote repository
When I say one command , I mean one user command. Just create a script file that contains multiple maven and other commands. YOu understand? Gordon Quoting Evan Bollig [EMAIL PROTECTED]: Im running maven 2 and need to deploy a war to a remote tomcat server. The goal is to limit the deployment to one command: mvn tomcat:deploy or mvn cargo:deploy, so checking out a plugin (i.e. the latest tomcat-maven-plugin) and manually compiling it is not an option; if this can be automated by maven I havent figured out how. I found two pre-deployed plugins: cargo and the maven-tomcat-plugin, but I cant get either one configured correctly. From the cargo docs, I found how to specify the remote host, username, etc, but I still face a problem that the server is apache-tomcat 5.5.15 and the manager url ends with /manager/html instead of /manager the way cargo is pre-configured. As for the other plugin, once I got maven to download tomcat-maven-plugin-1.0-SNAPSHOT from snapshots.maven.codehaus.org, I found that it wont accept a different destination url (even though I follow to a T what the docs say should work). Im sure someone on this list has gone through this process before. Can you post some tips, or an example of a working pom that does a remote deployment? Thanks, -- -Evan Bollig [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Gordon Erlebacher 489 Dirac Science Library Florida State University Tallahassee, FL 32309 Tel: (850) 644-0186 FAX: (850) 644-0098 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: ejb3 plugin
Hello Tim, i have downloaded the plugins,but they are as sources... can you tell me how do i go from sources to install them in my local repository? thanks in advance an dregards marco On 3/7/06, Tim Kettler [EMAIL PROTECTED] wrote: Hi Nidhi, you can checkout the maven-ejb3-plugin vie svn from the maven sandbox at: http://svn.apache.org/repos/asf/maven/sandbox/plugins/maven-ejb3-plugin you then probably also want the maven-par-plugin from: http://svn.apache.org/repos/asf/maven/sandbox/plugins/maven-par-plugin Once you have the plugins on your harddrive you can install them to your local repository by executing 'mvn install' in the project root directories. There is an attached zip file (test-prj.zip) at http://jira.codehaus.org/browse/MNG-1723 which contains a very minimalistic test project with an EJB3 project and an EAR project that packages the EJB file. You can use that as an starting point for your project. However, according to the latest draft of the spec (see section 6.2 of ejb-3_0-pfd-spec-persistence.pdf and chapter 19 of ejb-3_0- pfd-spec-ejbcore.pdf) Enterprise Beans are packaged in plain Jar files (not .ejb3 and .par). So if you use an EJB3 implementation that implements the latest spec (like the one from JBoss) you can use the 'standard' maven-ejb-plugin. The only problem with this is that the plugin enforces the presence of an 'ejb-jar.xml' file which is not needed with EJB3 if you use annotations. I submitted a patch for the plugin ( http://jira.codehaus.org/browse/MEJB-6) to make the 'ejb-jar.xml' optional but i don't know if this will be applyed in the near furure. -Tim Nidhi Tuli schrieb: Hi, I just started working on Maven 2 and trying to build my EJB3 project using maven2. Any ideas what plug-in should I use? In one of the articles I am advised to do ejb3 on the jar file which I created. The package for that is suggested to be maven-ejb3-plugin with groupId of goal bindings org.apache.maven.plugins. But I am not able to find this plugin? Any suggestions? Thanks Nidhi - 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: ejb3 plugin / solved
hello, ok i launche d a mvn install for each plugins sorry for bothering rgds marco On 3/11/06, Marco Mistroni [EMAIL PROTECTED] wrote: Hello Tim, i have downloaded the plugins,but they are as sources... can you tell me how do i go from sources to install them in my local repository? thanks in advance an dregards marco On 3/7/06, Tim Kettler [EMAIL PROTECTED] wrote: Hi Nidhi, you can checkout the maven-ejb3-plugin vie svn from the maven sandbox at: http://svn.apache.org/repos/asf/maven/sandbox/plugins/maven-ejb3-plugin you then probably also want the maven-par-plugin from: http://svn.apache.org/repos/asf/maven/sandbox/plugins/maven-par-plugin Once you have the plugins on your harddrive you can install them to your local repository by executing 'mvn install' in the project root directories. There is an attached zip file (test-prj.zip) at http://jira.codehaus.org/browse/MNG-1723 which contains a very minimalistic test project with an EJB3 project and an EAR project that packages the EJB file. You can use that as an starting point for your project. However, according to the latest draft of the spec (see section 6.2 of ejb-3_0-pfd-spec-persistence.pdf and chapter 19 of ejb-3_0- pfd-spec-ejbcore.pdf) Enterprise Beans are packaged in plain Jar files (not .ejb3 and .par). So if you use an EJB3 implementation that implements the latest spec (like the one from JBoss) you can use the 'standard' maven-ejb-plugin. The only problem with this is that the plugin enforces the presence of an 'ejb-jar.xml' file which is not needed with EJB3 if you use annotations. I submitted a patch for the plugin ( http://jira.codehaus.org/browse/MEJB-6) to make the 'ejb-jar.xml' optional but i don't know if this will be applyed in the near furure. -Tim Nidhi Tuli schrieb: Hi, I just started working on Maven 2 and trying to build my EJB3 project using maven2. Any ideas what plug-in should I use? In one of the articles I am advised to do ejb3 on the jar file which I created. The package for that is suggested to be maven-ejb3-plugin with groupId of goal bindings org.apache.maven.plugins . But I am not able to find this plugin? Any suggestions? Thanks Nidhi - 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: deploy war to remote repository
Evan, You can try cargo example https://svn.codehaus.org/cargo/cargo/trunk/samples/extensions/maven2/src /test/projects/testRemoteDeploy/pom.xml After this you just need to use cargo:deploy. Also in listed pom file if you are using cargo 0.8 please change cargo.tomcat.manager.username on cargo.remote.password and change cargo.tomcat.manager.password on cargo.remote.password Best regards, Juri. -Original Message- From: Evan Bollig [mailto:[EMAIL PROTECTED] Sent: Saturday, March 11, 2006 9:39 AM To: users@maven.apache.org Subject: deploy war to remote repository Im running maven 2 and need to deploy a war to a remote tomcat server. The goal is to limit the deployment to one command: mvn tomcat:deploy or mvn cargo:deploy, so checking out a plugin (i.e. the latest tomcat-maven-plugin) and manually compiling it is not an option; if this can be automated by maven I havent figured out how. I found two pre-deployed plugins: cargo and the maven-tomcat-plugin, but I cant get either one configured correctly. From the cargo docs, I found how to specify the remote host, username, etc, but I still face a problem that the server is apache-tomcat 5.5.15 and the manager url ends with /manager/html instead of /manager the way cargo is pre-configured. As for the other plugin, once I got maven to download tomcat-maven-plugin-1.0-SNAPSHOT from snapshots.maven.codehaus.org, I found that it wont accept a different destination url (even though I follow to a T what the docs say should work). Im sure someone on this list has gone through this process before. Can you post some tips, or an example of a working pom that does a remote deployment? Thanks, -- -Evan Bollig [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: deploy war to remote repository
I think /manager/html is just the web view. It is this way in Tomcat 5.0, 4.x, etc. too. /manager is still the right configuration. -Stephen On 3/11/06, Evan Bollig [EMAIL PROTECTED] wrote: Im running maven 2 and need to deploy a war to a remote tomcat server. The goal is to limit the deployment to one command: mvn tomcat:deploy or mvn cargo:deploy, so checking out a plugin (i.e. the latest tomcat-maven-plugin) and manually compiling it is not an option; if this can be automated by maven I havent figured out how. I found two pre-deployed plugins: cargo and the maven-tomcat-plugin, but I cant get either one configured correctly. From the cargo docs, I found how to specify the remote host, username, etc, but I still face a problem that the server is apache-tomcat 5.5.15 and the manager url ends with /manager/html instead of /manager the way cargo is pre-configured. As for the other plugin, once I got maven to download tomcat-maven-plugin-1.0-SNAPSHOT from snapshots.maven.codehaus.org, I found that it wont accept a different destination url (even though I follow to a T what the docs say should work). Im sure someone on this list has gone through this process before. Can you post some tips, or an example of a working pom that does a remote deployment? Thanks, -- -Evan Bollig [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Stephen Duncan Jr www.stephenduncanjr.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: how to point 'mvn archetype:create' at internal repository?
On 3/11/06, Rob Dickens [EMAIL PROTECTED] wrote: When I run 'mvn archetype:create ...' or 'mvn -Pdevt-profile ...' it attempts to download the archetype from http://repo1.maven.org/ maven2, and appears to have no knowledge of the repository specified above. PLEASE COULD SOMEBODY CHECK THAT THIS DOES IN FACT WORK for maven 2.0.2, making sure that they are not in fact downloading the archetype from their local repository. I can confirm that it does NOT work in Maven 2.0.2, see this thread for more info: http://www.nabble.com/How-to-install-use-a-third-party-archetype--t1024045.html#a2662843 If you build the archetype plugin from source, then you can use -DremoteRepositories=... See also: http://www.nabble.com/-m2-Release-archetype-plugin--t1134662.html#a3023526 HTH, -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: maven 2 with jdk 1.3
Hi!
PS Sanjay, you can find out what version a given class was compiled if
you look at the unsigned short integers starting at byte offset 4,
right after 0xCAFEBABE in every class file. See this Javaworld article
for more details, page 2:
http://www.javaworld.com/javaqa/2003-05/02-qa-0523-version.html
An easier way to find the classfile version is to run
javap -classpath {jarfile} -verbose {classname}
eg
javap -verbose java.lang.String
If you are luck and work on an linux box you can also try file
eg
# file UserRoleAware.class
UserRoleAware.class: compiled Java class data, version 45.3
:-)
Ciao,
Mario
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: how to point 'mvn archetype:create' at internal repository?
On 3/11/06, Wendy Smoak [EMAIL PROTECTED] wrote: I can confirm that it does NOT work in Maven 2.0.2, see this thread for more info: http://www.nabble.com/How-to-install-use-a-third-party-archetype--t1024045.html#a2662843 Sorry, that should say it (retrieving an archetype from a remote repository) does not work with the current version of the archetype plugin, which is 1.0-alpha-3 released in September 2005. I am able to build the plugin from source and use it with Maven 2.0.2 with no problems. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: plugin use in multiprojects seems broken
Bugs like this are one of the reasons the plugin is still alpha. Although, I have to admit that I did not expect the plugin to get used like this since I figured each project that wanted to be able to build an RPM would need an individual configuration; I wasn't expecting anyone to want to use an identical configuration for the plugin on every project. I'll take a look at some of the other plugins and figure out how to do this check and update the sources to make this work. -Original Message- From: Brett Porter [mailto:[EMAIL PROTECTED] Sent: Friday, March 10, 2006 20:44 To: Maven Users List Subject: Re: plugin use in multiprojects seems broken You'll need to provide more details. Why doesn't it work if you don't put it in the parent? Where do you put it if not in the parent? Regardless, it should work in the parent. It's a bug in the rpm plugin if it attempts to produce an rpm for a pom - it should be testing the packaging. - Brett On 3/11/06, Xavier Toth [EMAIL PROTECTED] wrote: Maybe I'm missing something but the use of plugins in multiprojects seems broken to me. I've got three projects that build rpms so I made a parent projects to run them all. However unless I add the plugin into the parent as in : modules modulemicro_proxy/module modulesocks/module modulejwss/module /modules build plugins plugin groupIdorg.codehaus.mojo/groupId artifactIdrpm-maven-plugin/artifactId version1.0-alpha-2-SNAPSHOT/version configuration release1/release mappings /mappings /configuration /plugin /plugins /build the submodules won't build. I really don't want to run the plugin (rpm:rpm) goal in the parent project. It seem to me that a mulitproject parent ought to be able to ignore plugin goals that it doesn't have build information for and simple pass them along to its submodules. Xavier - 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: [m2] Internal Repositories
You should use Maven-proxy and an internal repository wich share the same location. This way, your goal is going to be achieved automatically. Or if you prefer a manual process, just run regularly a synchronise file tool between Maven-Proxy repository and your internal repository. On 3/11/06, Khin, Gerald [EMAIL PROTECTED] wrote: On 3/10/06, Treloar, Barrie [EMAIL PROTECTED] wrote: On 3/10/06, Khin, Gerald [EMAIL PROTECTED] wrote: Hi! Being a newbie to maven, I wonder if this idea could work: [del] The first question that springs to mind is Why? What benefit is there to restrict maven in this way, it makes no sense. My idea behind is to conserve all things I needed to build my project so that once my product will be released, that I will be still able to build my project in case, even in a couple of years, completely independent of the availability of the central repository and its public mirrors. Control the version numbers of artifacts that you have sanctioned is a better way of enforcing standards in the organisation that banning maven from downloading more plugins. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Alexandre Poitras Québec, Canada - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: rpm-plugin mapping file rename
Looking at the sources, it looks like it will not rename the file. If ../../micro_proxy is a directory, then the file micro_proxy.xinetd in that directory will be installed in the destination (/etc/xinetd.d) with the name micro_proxy.xinetd. If ../../micro_proxy is a file, then that file will be installed in the destination with the name micro_proxy (the includes will be ignored). My suggestion on how to do this would be to have a directory in the project src/main/xinetd and place the file micro_proxy in that directory. You can then instruct the RPM plugin to just place everything in the source directory into the destination (no need for includes in this case). -Original Message- From: Xavier Toth [mailto:[EMAIL PROTECTED] Sent: Friday, March 10, 2006 08:52 To: Maven Users List Subject: Re: rpm-plugin mapping file rename I'm not sure how I'd do a rename. Here is an example where I'd like what ends up in /etc/xinetd.d to be simple micro_proxy and not micro_proxy.xinetd, any idea how I'd do this? mapping directory/etc/xinetd.d/directory filemode755/filemode sources source location../../micro_proxy/location includes includemicro_proxy.xinetd/include /includes /source /sources /mapping On 3/10/06, Allison, Bob [EMAIL PROTECTED] wrote: I believe the answer is that it will not unless the item to be renamed is the item specified in the mapping. I would say to give it a try and let me know if it works or doesn't work. If it works, I can add that information to the docs; if it doesn't work, send me more info on what you are doing and I can see what I might be able to do so it will. -Original Message- From: Xavier Toth [mailto:[EMAIL PROTECTED] Sent: Thursday, March 09, 2006 4:31 PM To: Maven Users List Subject: rpm-plugin mapping file rename Can the mapping element be used to rename a file being installed? Xavier - 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: rpm plugin location
The links on that page were automatically created from information inherited from the sandbox parent. I think the sandbox parent was updated since then to provide the correct links, but I haven't regenerated the site since then. I'll try to get this updated. -Original Message- From: Edwin Punzalan [mailto:[EMAIL PROTECTED] Sent: Friday, March 10, 2006 21:55 To: Maven Users List Subject: Re: rpm plugin location That page is wrong. It should be: svn://svn.codehaus.org/mojo/scm/trunk/mojo/mojo-sandbox/rpm-maven-plugin Xavier Toth wrote: I can't find the rpm plugin source. The links and svn commands at http://www.codehaus.org/~boba/rpm-plugin/source-repository.html don't work. Anyone know where this plugin is now? - 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-corburtura POM v3 in repo
If possible, can u share with us the XSLT u wrote to convert POMv3 to POMv4? How did I _know_ that question was coming? :-) Please find it attached. -- /v\atthew ?xml version=1.0 encoding=UTF-8? !-- Version: 1.0 Copyright 2006 Matthew L Daniel [EMAIL PROTECTED] Licensed under the Apache License, Version 2.0 (the License); you may not use this file except in compliance with the License. You may obtain a copy of the License at http://www.apache.org/licenses/LICENSE-2.0 Unless required by applicable law or agreed to in writing, software distributed under the License is distributed on an AS IS BASIS, WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied. See the License for the specific language governing permissions and limitations under the License. /-- !-- This xslt purposefully does not use xsl:copy-of for the same reason it injects @xmlns into the project element: namespaces are not honored in either the v3 or v4 POM, and xsl:copy-of introduces more risk of NamespaceMania than it does benefit. /-- xsl:stylesheet version=1.0 xmlns:xsl=http://www.w3.org/1999/XSL/Transform; xsl:output method=xml version=1.0 encoding=UTF-8 indent=yes/ xsl:template match='/' xsl:apply-templates select='project'/ /xsl:template xsl:template match='project' project xsl:attribute name='xmlns' http://maven.apache.org/POM/4.0.0/xsl:attribute modelVersion4.0.0/modelVersion xsl:choose xsl:when test='boolean(id) and not(boolean(groupId)) and contains(id, :)' groupId xsl:value-of select='string-before(id,:)'/ /groupId artifactId xsl:value-of select='string-after(id,:)'/ /artifactId /xsl:when xsl:when test='boolean(id) and not(boolean(groupId)) and not(contains(id, :))' groupIdxsl:value-of select='id' //groupId artifactIdxsl:value-of select='id' //artifactId /xsl:when xsl:when test='boolean(id) and boolean(groupId) and not(contains(id, :))' groupIdxsl:value-of select='groupId' //groupId artifactIdxsl:value-of select='id' //artifactId /xsl:when xsl:otherwise groupId xsl:value-of select='groupId' / /groupId artifactId xsl:value-of select='artifactId' / /artifactId /xsl:otherwise /xsl:choose packagingjar/packaging namexsl:value-of select='name' //name version xsl:value-of select='currentVersion' / /version description !-- use shortDescription since m2 puts this in the Jar Manifest, so it needs to be a one-liner -- xsl:value-of select='shortDescription' / /description urlxsl:value-of select='url' //url xsl:apply-templates select='dependencies' / /project /xsl:template xsl:template match='dependencies' dependencies xsl:apply-templates select='dependency' / /dependencies /xsl:template xsl:template match='dependency[id and contains(id,:) and not(groupId)]' dependency groupId xsl:value-of select='string-before(id,:)'/ /groupId artifactId xsl:value-of select='string-after(id,:)'/ /artifactId versionxsl:value-of select='version' //version xsl:call-template name='typeOrDefault' / /dependency /xsl:template xsl:template match='dependency[id and not(contains(id,:)) and not(groupId)]' dependency groupIdxsl:value-of select='id' //groupId artifactIdxsl:value-of select='id' //artifactId versionxsl:value-of select='version' //version xsl:call-template name='typeOrDefault' / /dependency /xsl:template xsl:template match='dependency[groupId]' dependency groupIdxsl:value-of select='groupId' //groupId artifactIdxsl:value-of select='artifactId' //artifactId versionxsl:value-of select='version' //version xsl:call-template name='typeOrDefault' / /dependency /xsl:template xsl:template name='typeOrDefault' xsl:choose xsl:when test='boolean(type)' type xsl:value-of select='type' / /type /xsl:when xsl:otherwise typejar/type
Re: maven-corburtura POM v3 in repo
You can also take a look at : http://svn.apache.org/viewcvs.cgi/maven/components/trunk/maven-model-converter/ Arnaud On 3/11/06, Matthew L Daniel [EMAIL PROTECTED] wrote: If possible, can u share with us the XSLT u wrote to convert POMv3 to POMv4? How did I _know_ that question was coming? :-) Please find it attached. -- /v\atthew - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2,maven-proxy,newbie] Struggling with maven-proxy
Hi! I'm new m2 and maven-proxy and struggling to get it working. If I call mvn clean, then the console debug output shows: [INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking for updates from wollox-plugin-repo [DEBUG] repository metadata for: 'artifact org.apache.maven.plugins:maven-clean-plugin' could not be found on repository : wollox-plugin-repo [INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking for updates from central [DEBUG] maven-clean-plugin: resolved to version 2.1 from repository central [DEBUG] Trying repository central Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.1/maven-clean-plugin-2.1.pom 703b downloaded ... It appears that my maven-proxy instance was tried to be used, but that something went wrong there so that things were retrieved from central at the end . The console output of maven-proxy is: Y:\maven-proxyjava -jar maven-proxy-standalone-0.2-app.jar maven-proxy.properties maven-proxy Unversioned 2006-03-11 16:44:06,406 [INFO ] proxy.config.RepoConfiguration - Disabling snapshot cache 2006-03-11 16:44:06,421 [INFO ] proxy.config.RepoConfiguration - Disabling snapshot cache 2006-03-11 16:44:06,421 [INFO ] proxy.config.RepoConfiguration - Repo[www-ibiblio-org]: Enabling cache with period of 3 600 seconds 2006-03-11 16:44:06,421 [INFO ] proxy.config.RepoConfiguration - Repo[dist-codehaus-org]: Enabling cache with period of 3600 seconds Saving repository at U:///Modules/maven/remote-repo Scanning repository: file:///U:///Modules/maven/remote-repo Scanning repository: file:///./target/repo-local Scanning repository: http://www.ibiblio.org/maven Scanning repository: http://dist.codehaus.org Starting... Prefix: 'repository' Started. Add the following to your ~/build.properties file: maven.repo.remote=http://localhost:1516/repository The proxy can be managed at http://localhost:1516 The repository can be browsed at http://localhost:1516/repository Repository searching is enabled. 2006-03-11 16:44:48,281 [INFO ] proxy.servlets.RepositoryServlet - Received request: /org/apache/maven/plugins/maven-clean-plugin/maven-metadata.xml 2006-03-11 16:44:48,296 [DEBUG] proxy.engine.DownloadEngine - Request: source=127.0.0.1, path=/org/apache/maven/plugins/maven-clean-plugin/maven-metadata.xml, lastModified=-1, headOnly=false, ifModifiedSince=-1 2006-03-11 16:44:48,296 [WARN ] proxy.engine.DownloadEngine - Neither If-Modified-Since nor Last-Modified are set 2006-03-11 16:44:48,296 [DEBUG] proxy.config.FileRepoConfiguration - Repo[global]: Checking last modified time for U:\Modules\maven\remote-repo\org\apache\maven\plugins\maven-clean-plugin\maven-metadata.xml 2006-03-11 16:44:48,312 [DEBUG] proxy.config.FileRepoConfiguration - Repo[local-repo]: Checking last modified time for .\target\repo-local\org\apache\maven\plugins\maven-clean-plugin\maven-metadata.xml 2006-03-11 16:44:48,312 [DEBUG] components.impl.DefaultSnapshotCache - Unable to find /org/apache/maven/plugins/maven-clean-plugin/maven-metadata.xml in snapshot cache 2006-03-11 16:44:48,312 [INFO ] proxy.config.HttpRepoConfiguration - Repo[www-ibiblio-org]: Checking last modified time for http://www.ibiblio.org/maven/org/apache/maven/plugins/maven-clean-plugin/maven-metadata.xml 2006-03-11 16:44:48,875 [INFO ] components.impl.DefaultSnapshotCache - Adding /org/apache/maven/plugins/maven-clean-plugin/maven-metadata.xml to snapshot cache 2006-03-11 16:44:48,875 [DEBUG] components.impl.DefaultSnapshotCache - Unable to find /org/apache/maven/plugins/maven-clean-plugin/maven-metadata.xml in snapshot cache 2006-03-11 16:44:48,875 [INFO ] proxy.config.HttpRepoConfiguration - Repo[dist-codehaus-org]: Checking last modified time for http://dist.codehaus.org/org/apache/maven/plugins/maven-clean-plugin/maven-metadata.xml 2006-03-11 16:44:49,218 [INFO ] components.impl.DefaultSnapshotCache - Adding /org/apache/maven/plugins/maven-clean-plugin/maven-metadata.xml to snapshot cache 2006-03-11 16:44:49,218 [INFO ] proxy.engine.DownloadEngine - Artifact not found: /org/apache/maven/plugins/maven-clean-plugin/maven-metadata.xml ... What could I have done wrong? My pom.xml looks like this: pluginRepositories pluginRepository idwollox-plugin-repo/id urlhttp://localhost:1516/repository/url snapshots enabledtrue/enabled /snapshots releases enabledtrue/enabled /releases layoutdefault/layout /pluginRepository /pluginRepositories Regards Gerald
EJB3/J2EE project using Maven2
Hello all, i have done a J2EE project which includes some EJB3, using Maven2. as of now, main limitation (due to its simplicity) is that i am NOT using maven-ejb-plugin since i am letting jboss figure out the ejb-jar.xml from the deployed package the current project does not use any maven-ejb3 plugins, nor any maven-par-plugins... but it's a very simple example of a J2EE project using maven2 Btw, i have copied from a sample that i have downloaded from some maven repositories i'd like to send it to the whole list, but i guess it's impractical if someone is interested, please let me know email and i send it privately alternatively, if i can post it to some maven guy so that it ends up in some repositories, i will be glad to do so regards marco
Re: Passing maven variables as system properties
Hello,
not sure about maven2, but in maven1 i was using following (espeically for
junit)
maven.junit.sysproperties=db.url db.user db.password db.driver db.seedfile
maven.final.name
is there a similar thing for maven2?
rgds
marco
On 3/11/06, Simon Kitching [EMAIL PROTECTED] wrote:
Thanks Hermod, you've helped me make *some* progress.
It appears the problem is that the variable name I'm using is not
recognised, so the original expression is passed unaltered.
${pom.name} works fine for example (expanded)
However none of the following work:
${project.build.outputDirectory}
${project.build.directory}
${pom.build.directory}
Anyone know what the magic variable name is for passing the
outputDirectory (ie dir where main java src gets compiled to) to the
unit tests as a system property?
Thanks,
Simon
On Fri, 2006-03-10 at 11:47 +0100, [EMAIL PROTECTED] wrote:
Hi
Try project.build.directory
Hermod
-Original Message-
From: Simon Kitching [mailto:[EMAIL PROTECTED]
Sent: Friday, March 10, 2006 3:53 AM
To: users@maven.apache.org
Subject: Passing maven variables as system properties
Hi,
I'm trying to store some maven vars into system properties so I can
access them from unit test code:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-surefire-plugin/artifactId
configuration
systemProperties
property
namecore-static/name
value${project.build.outputDirectory}//value
/property
property
namecore-static-tests/name
value${project.build.testOutputDirectory}//value
/property
/systemProperties
/configuration
/plugin
/plugins
However the value of
System.getProperty(core-static)
is literally ${project.build.outputDirectory}, not the expanded value.
Does anyone know how I can pass the value of this expression?
Thanks,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* *
This email with attachments is solely for the use of the individual or
entity to whom it is addressed. Please also be aware that DnB NOR cannot
accept any payment orders or other legally binding correspondence with
customers as a part of an email.
This email message has been virus checked by the virus programs used
in the DnB NOR Group.
* * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * * *
* *
-
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: Exploded directory Structure
Can't you just run the build again? I have Tomcat setup to point to the exploded archive in target. Then a change is made and we rebuild. -Original Message- From: chetan mehrotra [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 07, 2006 5:39 AM To: users@maven.apache.org Subject: Exploded directory Structure Hi, I am new to Maven and was going through the features available. Ours is a big project and currently we were planning for some major changes. Till now we were using ant to build the app but now we were looking into the possibility of using Maven. One feature that I was not able to find was related to exploded dir structure. Till now we were following the exploded structure for development using WebLogic. In that the java classes were compiled to WEB-INF classes. But the jsps need not to be copied.. So for a developer if he is changing the jsp then he can see the result immediately by refreshing on the browser. But in the Maven structure everything is copied to the target. So for seeing the changes in jsp the person has to copy the changed jsp every time. Can this be achieved in a better way!!!. -- Chetan Mehrotra - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: EJB3/J2EE project using Maven2
Hi Marco, Can you try sending it to me again please. I know yesterday you tried sending the M1 version, but I never received it. many thanks Pete On 11/03/06, Marco Mistroni [EMAIL PROTECTED] wrote: Hello all, i have done a J2EE project which includes some EJB3, using Maven2. as of now, main limitation (due to its simplicity) is that i am NOT using maven-ejb-plugin since i am letting jboss figure out the ejb-jar.xml from the deployed package the current project does not use any maven-ejb3 plugins, nor any maven-par-plugins... but it's a very simple example of a J2EE project using maven2 Btw, i have copied from a sample that i have downloaded from some maven repositories i'd like to send it to the whole list, but i guess it's impractical if someone is interested, please let me know email and i send it privately alternatively, if i can post it to some maven guy so that it ends up in some repositories, i will be glad to do so regards marco
Re: [m2,maven-proxy,newbie] Struggling with maven-proxy
You have to declare it as mirror of central in your settings.xml file. It is very important to understand that a proxy is not a true repository. It is always confused because a lot of people share their proxy *cache* (where the artifacts are copied) and their internal corporation repository in case their internet access go down. Well that's what I do. On 3/11/06, Khin, Gerald [EMAIL PROTECTED] wrote: Hi! I'm new m2 and maven-proxy and struggling to get it working. If I call mvn clean, then the console debug output shows: [INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking for updates from wollox-plugin-repo [DEBUG] repository metadata for: 'artifact org.apache.maven.plugins:maven-clean-plugin' could not be found on repository : wollox-plugin-repo [INFO] artifact org.apache.maven.plugins:maven-clean-plugin: checking for updates from central [DEBUG] maven-clean-plugin: resolved to version 2.1 from repository central [DEBUG] Trying repository central Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-clean-plugin/2.1/maven-clean-plugin-2.1.pom 703b downloaded ... It appears that my maven-proxy instance was tried to be used, but that something went wrong there so that things were retrieved from central at the end . The console output of maven-proxy is: Y:\maven-proxyjava -jar maven-proxy-standalone-0.2-app.jar maven-proxy.properties maven-proxy Unversioned 2006-03-11 16:44:06,406 [INFO ] proxy.config.RepoConfiguration - Disabling snapshot cache 2006-03-11 16:44:06,421 [INFO ] proxy.config.RepoConfiguration - Disabling snapshot cache 2006-03-11 16:44:06,421 [INFO ] proxy.config.RepoConfiguration - Repo[www-ibiblio-org]: Enabling cache with period of 3 600 seconds 2006-03-11 16:44:06,421 [INFO ] proxy.config.RepoConfiguration - Repo[dist-codehaus-org]: Enabling cache with period of 3600 seconds Saving repository at U:///Modules/maven/remote-repo Scanning repository: file:///U:///Modules/maven/remote-repo Scanning repository: file:///./target/repo-local Scanning repository: http://www.ibiblio.org/maven Scanning repository: http://dist.codehaus.org Starting... Prefix: 'repository' Started. Add the following to your ~/build.properties file: maven.repo.remote=http://localhost:1516/repository The proxy can be managed at http://localhost:1516 The repository can be browsed at http://localhost:1516/repository Repository searching is enabled. 2006-03-11 16:44:48,281 [INFO ] proxy.servlets.RepositoryServlet - Received request: /org/apache/maven/plugins/maven-clean-plugin/maven-metadata.xml 2006-03-11 16:44:48,296 [DEBUG] proxy.engine.DownloadEngine - Request: source=127.0.0.1, path=/org/apache/maven/plugins/maven-clean-plugin/maven-metadata.xml, lastModified=-1, headOnly=false, ifModifiedSince=-1 2006-03-11 16:44:48,296 [WARN ] proxy.engine.DownloadEngine - Neither If-Modified-Since nor Last-Modified are set 2006-03-11 16:44:48,296 [DEBUG] proxy.config.FileRepoConfiguration - Repo[global]: Checking last modified time for U:\Modules\maven\remote-repo\org\apache\maven\plugins\maven-clean-plugin\maven-metadata.xml 2006-03-11 16:44:48,312 [DEBUG] proxy.config.FileRepoConfiguration - Repo[local-repo]: Checking last modified time for .\target\repo-local\org\apache\maven\plugins\maven-clean-plugin\maven-metadata.xml 2006-03-11 16:44:48,312 [DEBUG] components.impl.DefaultSnapshotCache - Unable to find /org/apache/maven/plugins/maven-clean-plugin/maven-metadata.xml in snapshot cache 2006-03-11 16:44:48,312 [INFO ] proxy.config.HttpRepoConfiguration - Repo[www-ibiblio-org]: Checking last modified time for http://www.ibiblio.org/maven/org/apache/maven/plugins/maven-clean-plugin/maven-metadata.xml 2006-03-11 16:44:48,875 [INFO ] components.impl.DefaultSnapshotCache - Adding /org/apache/maven/plugins/maven-clean-plugin/maven-metadata.xml to snapshot cache 2006-03-11 16:44:48,875 [DEBUG] components.impl.DefaultSnapshotCache - Unable to find /org/apache/maven/plugins/maven-clean-plugin/maven-metadata.xml in snapshot cache 2006-03-11 16:44:48,875 [INFO ] proxy.config.HttpRepoConfiguration - Repo[dist-codehaus-org]: Checking last modified time for http://dist.codehaus.org/org/apache/maven/plugins/maven-clean-plugin/maven-metadata.xml 2006-03-11 16:44:49,218 [INFO ] components.impl.DefaultSnapshotCache - Adding /org/apache/maven/plugins/maven-clean-plugin/maven-metadata.xml to snapshot cache 2006-03-11 16:44:49,218 [INFO ] proxy.engine.DownloadEngine - Artifact not found: /org/apache/maven/plugins/maven-clean-plugin/maven-metadata.xml ... What could I have done wrong? My pom.xml looks like this: pluginRepositories pluginRepository idwollox-plugin-repo/id urlhttp://localhost:1516/repository/url snapshots enabledtrue/enabled /snapshots releases enabledtrue/enabled /releases
Re: Exploded directory Structure
If I've understood what you are trying to do, you can tomcat config point to the src/main/webapp directory, you can then run a mvn compile war:inplace, and it will copy all of classes and dependencies into the appropriate places in your WEB-INF folder. When doing this, it's also helpful to bind add something to your clean phase: *-* http://svn.dynamic-info.com/svn/bizbidplace/trunk/pom.xml#plugin artifactIdmaven-antrun-plugin/artifactId executions execution phaseclean/phase configuration tasks echo message=Removing files from WEB-INF\lib and WEB-INF\classes / delete dir=src\main\webapp\WEB-INF\lib / delete dir=src\main\webapp\WEB-INF\classes / /tasks /configuration goals goalrun/goal /goals /execution /executions /plugin YYou may also want to check out the jetty6 plugin, it's very good for this sort of thing as well. Greg Case I' On 3/11/06, Brian E. Fox [EMAIL PROTECTED] wrote: Can't you just run the build again? I have Tomcat setup to point to the exploded archive in target. Then a change is made and we rebuild. -Original Message- From: chetan mehrotra [mailto:[EMAIL PROTECTED] Sent: Tuesday, March 07, 2006 5:39 AM To: users@maven.apache.org Subject: Exploded directory Structure Hi, I am new to Maven and was going through the features available. Ours is a big project and currently we were planning for some major changes. Till now we were using ant to build the app but now we were looking into the possibility of using Maven. One feature that I was not able to find was related to exploded dir structure. Till now we were following the exploded structure for development using WebLogic. In that the java classes were compiled to WEB-INF classes. But the jsps need not to be copied.. So for a developer if he is changing the jsp then he can see the result immediately by refreshing on the browser. But in the Maven structure everything is copied to the target. So for seeing the changes in jsp the person has to copy the changed jsp every time. Can this be achieved in a better way!!!. -- Chetan Mehrotra - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Greg Case (m) 612-730-6558 (aim) gcase1975
Re: test report in m2
I've removed the version and the report got generate in the same way as before, without finding any tests (tests that I see run while running site, BTW) So I specified version 2.0-SNAPSHOT and got this GroupId: org.codehaus.mojo ArtifactId: surefire-report-maven-plugin Version: 2.0-SNAPSHOT Reason: Unable to download the artifact from any repository org.codehaus.mojo:surefire-report-maven-plugin:pom:2.0-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), tech-1 (http://localhost:9090/testux/maven2/), wife.repo (http://wife.sf.net/m2-snapshots/), wire.repo2 (http://wife.sf.net/m2-repository/) probably because I haven't installed a snapshot of the plugin locally I specified version 2.0-beta-4 but it wasn't found (I've already checked and defined that dep by seeing the only deployed version at http://www.ibiblio.org/maven2/org/codehaus/mojo/surefire-report-maven-plugin/ ) so my guess is, did you compile the plugin locally? or: do you have another repository defined? thank you all so much On 3/11/06, Alexandre Poitras [EMAIL PROTECTED] wrote: I agree. You shoudn't specify a plugin version unless you really need to (for instance you want to use a snapshot version). This way Maven will tell you when there is a new version released and ask you if you want to install it and use it from now on. On 3/11/06, Wayne Fay [EMAIL PROTECTED] wrote: Sorry about the /src/tests mistake -- you're right, the correct directory is /src/test. I'm not specifying the version number as you are... Mine plugin groupIdorg.codehaus.mojo/groupId artifactIdsurefire-report-maven-plugin/artifactId /plugin Yours: plugin groupIdorg.codehaus.mojo/groupId artifactIdsurefire-report-maven-plugin/artifactId version2.0-beta-1/version /plugin Perhaps this is causing your issue? I'm not sure what the most recent release is but according to my local user repo I've got: 2.0-20060106.225541-3 2.0-alpha-2 2.0-beta-4 2.0-SNAPSHOT Without specifying a version, I'm getting maven-site-plugin:2.0-beta-4. I'd assume there are updates between beta-1 and beta-4 that you are missing, which is leading to some of your troubles. Wayne On 3/10/06, Miguel Griffa [EMAIL PROTECTED] wrote: I alsgo have all test classes named FooTest but the dir is src/test/java (note singluar test, not plural) however, if I run mvn test, it will take 20' to run all tests, but when I run site, tests are run, but report says 0 tests. I noticed there are not TESTfoo.xml in the generated reports dir, but I guess that should be automatic, shouldn't it? you didn't have to set anything special, did you? plugin is defined like this reporting plugins plugin groupIdorg.codehaus.mojo/groupId artifactIdsurefire-report-maven-plugin/artifactId version2.0-beta-1/version /plugin On 3/10/06, Wayne Fay [EMAIL PROTECTED] wrote: I also use it with zero issues. Tests are in src/tests/java and named BlahVOTest.java with methods setUp, tearDown, and testBlah1, testBlah2, etc. I can only think you are doing something strange, Miguel. ;-) Wayne On 3/10/06, Alexandre Poitras [EMAIL PROTECTED] wrote: I use it without any problems. What are you test methods names ? textXXX ? Or you prefer to use test suites? On 3/10/06, Miguel Griffa [EMAIL PROTECTED] wrote: anyone being able to use surfire test report in m2? I have a project with 2000+ tests, with m2 dir layout and test report says all zero... any ideas? -- Miguel Griffa Skype: miguel.griffa Y!: m_griffa MSN: [EMAIL PROTECTED] Cell: 15-62519355 -- Alexandre Poitras Québec, Canada - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Miguel Griffa Skype: miguel.griffa Y!: m_griffa MSN: [EMAIL PROTECTED] Cell: 15-62519355 -- Alexandre Poitras Québec, Canada - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Miguel Griffa Skype: miguel.griffa Y!: m_griffa MSN: [EMAIL PROTECTED] Cell: 15-62519355
plugin:download in m2
Hello Guys, Im having a doub that would like to ask you, Im an AndroMDA ( http://www.andromda.org), this guys use maven to generate their MDa projects. Recently thay provided a plugin for m2, but to use it I have to download the entire sources and compile them myself using m2 (Not big deal but when using m1 I only needed to download a plugin. Im pasting below my original question and the answer to that: *dbendlin* Joined: 17 May 2005 Posts: 172 Location: Asunción - Paraguay [image: Post]http://galaxy.andromda.org/forum/viewtopic.php?p=10748sid=84cd644eec69f3a99820238de7a328ed#10748Posted: Sat Mar 11, 2006 1:26 pmPost subject: [image: Reply with quote]http://galaxy.andromda.org/forum/posting.php?mode=quotep=10748sid=84cd644eec69f3a99820238de7a328ed [image: Edit/Delete this post]http://galaxy.andromda.org/forum/posting.php?mode=editpostp=10748sid=84cd644eec69f3a99820238de7a328ed -- Hello Guys, I have a doub about m2 usage, as you AndroMDA guys are the only ones I know using it I'm sure you could help See, in M1 you needed to download andromdapp plugin to be able to generate a M1 project (maven plugin:download), after generating the project M1 automaticaly downloaded every dependency needed to the local repository and that was it. In M2 things seem to work in a diferent way, the plugin download mechanism seems to be a missing feature, or am I missing something? How to get andromdapp in m2 (Is it mandatory to download andromda-all from CVS? or is there another way?). Thanks in advance! _ Diego Bendlin Back to tophttp://galaxy.andromda.org/forum/viewtopic.php?t=2015#top [image: View user's profile]http://galaxy.andromda.org/forum/profile.php?mode=viewprofileu=54sid=84cd644eec69f3a99820238de7a328ed [image: Send private message]http://galaxy.andromda.org/forum/privmsg.php?mode=postu=54sid=84cd644eec69f3a99820238de7a328ed [image: Send e-mail] [EMAIL PROTECTED] [image: MSN Messenger]http://galaxy.andromda.org/forum/profile.php?mode=viewprofileu=54sid=84cd644eec69f3a99820238de7a328ed *chad.brandon* AndroMDA Admin Joined: 06 May 2005 Posts: 2105 Location: Colorado Springs, CO, USA [image: New post]http://galaxy.andromda.org/forum/viewtopic.php?p=10752sid=84cd644eec69f3a99820238de7a328ed#10752Posted: Sat Mar 11, 2006 3:13 pmPost subject: [image: Reply with quote]http://galaxy.andromda.org/forum/posting.php?mode=quotep=10752sid=84cd644eec69f3a99820238de7a328ed -- Yeah its necessary to build andromda-all from CVS, for some reason maven2 seems to have issues with downloading and installing a plugin with groupIds other than org.apache.maven.plugins and the mojo groupId for codehaus (can't remember what it is). I haven't had time much to look into why it won't work, maybe you can ask the maven team why? Until we figure out why, you'll need to build the src yourself so that it will be installed. _ Chad Brandon - chad [at] andromda [dot] org http://www.andromda.org Back to tophttp://galaxy.andromda.org/forum/viewtopic.php?t=2015#top [image: View user's profile]http://galaxy.andromda.org/forum/profile.php?mode=viewprofileu=5sid=84cd644eec69f3a99820238de7a328ed [image: Send private message]http://galaxy.andromda.org/forum/privmsg.php?mode=postu=5sid=84cd644eec69f3a99820238de7a328ed [image: Send e-mail] [EMAIL PROTECTED] [image: Visit poster's website]http://www.andromda.org/ [image: AIM Address] aim:goim?screenname=chdbrandonmessage=Hello+Are+you+there? [image: Yahoo Messenger]http://edit.yahoo.com/config/send_webmesg?.target=chdbrandon.src=pg [image: MSN Messenger]http://galaxy.andromda.org/forum/profile.php?mode=viewprofileu=5sid=84cd644eec69f3a99820238de7a328ed I wasn't sure if this question should be for developers or users so I copied this mail to both. Any help regarding this doub will be great! Thanks in advance for your help and support Kind Regards, Diego Bendlin
Re: test report in m2
Last release of surefire-report-maven-plugin is indeed 2.0-beta-1 [1] 2.0-beta-4 is maven-site-plugin [2] [1] http://www.ibiblio.org/maven2/org/codehaus/mojo/surefire-report-maven-plugin/ [2] http://www.ibiblio.org/maven2/org/apache/maven/plugins/maven-site-plugin/ On 3/11/06, Miguel Griffa [EMAIL PROTECTED] wrote: I've removed the version and the report got generate in the same way as before, without finding any tests (tests that I see run while running site, BTW) So I specified version 2.0-SNAPSHOT and got this GroupId: org.codehaus.mojo ArtifactId: surefire-report-maven-plugin Version: 2.0-SNAPSHOT Reason: Unable to download the artifact from any repository org.codehaus.mojo:surefire-report-maven-plugin:pom:2.0-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), tech-1 (http://localhost:9090/testux/maven2/), wife.repo (http://wife.sf.net/m2-snapshots/), wire.repo2 (http://wife.sf.net/m2-repository/) probably because I haven't installed a snapshot of the plugin locally I specified version 2.0-beta-4 but it wasn't found (I've already checked and defined that dep by seeing the only deployed version at http://www.ibiblio.org/maven2/org/codehaus/mojo/surefire-report-maven-plugin/ ) so my guess is, did you compile the plugin locally? or: do you have another repository defined? thank you all so much On 3/11/06, Alexandre Poitras [EMAIL PROTECTED] wrote: I agree. You shoudn't specify a plugin version unless you really need to (for instance you want to use a snapshot version). This way Maven will tell you when there is a new version released and ask you if you want to install it and use it from now on. On 3/11/06, Wayne Fay [EMAIL PROTECTED] wrote: Sorry about the /src/tests mistake -- you're right, the correct directory is /src/test. I'm not specifying the version number as you are... Mine plugin groupIdorg.codehaus.mojo/groupId artifactIdsurefire-report-maven-plugin/artifactId /plugin Yours: plugin groupIdorg.codehaus.mojo/groupId artifactIdsurefire-report-maven-plugin/artifactId version2.0-beta-1/version /plugin Perhaps this is causing your issue? I'm not sure what the most recent release is but according to my local user repo I've got: 2.0-20060106.225541-3 2.0-alpha-2 2.0-beta-4 2.0-SNAPSHOT Without specifying a version, I'm getting maven-site-plugin:2.0-beta-4. I'd assume there are updates between beta-1 and beta-4 that you are missing, which is leading to some of your troubles. Wayne On 3/10/06, Miguel Griffa [EMAIL PROTECTED] wrote: I alsgo have all test classes named FooTest but the dir is src/test/java (note singluar test, not plural) however, if I run mvn test, it will take 20' to run all tests, but when I run site, tests are run, but report says 0 tests. I noticed there are not TESTfoo.xml in the generated reports dir, but I guess that should be automatic, shouldn't it? you didn't have to set anything special, did you? plugin is defined like this reporting plugins plugin groupIdorg.codehaus.mojo/groupId artifactIdsurefire-report-maven-plugin/artifactId version2.0-beta-1/version /plugin On 3/10/06, Wayne Fay [EMAIL PROTECTED] wrote: I also use it with zero issues. Tests are in src/tests/java and named BlahVOTest.java with methods setUp, tearDown, and testBlah1, testBlah2, etc. I can only think you are doing something strange, Miguel. ;-) Wayne On 3/10/06, Alexandre Poitras [EMAIL PROTECTED] wrote: I use it without any problems. What are you test methods names ? textXXX ? Or you prefer to use test suites? On 3/10/06, Miguel Griffa [EMAIL PROTECTED] wrote: anyone being able to use surfire test report in m2? I have a project with 2000+ tests, with m2 dir layout and test report says all zero... any ideas? -- Miguel Griffa Skype: miguel.griffa Y!: m_griffa MSN: [EMAIL PROTECTED] Cell: 15-62519355 -- Alexandre Poitras Québec, Canada - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Miguel Griffa Skype: miguel.griffa Y!: m_griffa MSN: [EMAIL PROTECTED] Cell: 15-62519355 -- Alexandre Poitras Québec, Canada - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional
Re: test report in m2
got that too plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-site-plugin/artifactId version2.0-beta-4/version /plugin I guess that the problem is in the report plugin, or the test plugin, since no TEST... xml are generated, but this is according to plugin doc in the site, so it may be obsolete or not apply anymore, still is consistent On 3/11/06, Yann Le Du [EMAIL PROTECTED] wrote: Last release of surefire-report-maven-plugin is indeed 2.0-beta-1 [1] 2.0-beta-4 is maven-site-plugin [2] [1] http://www.ibiblio.org/maven2/org/codehaus/mojo/surefire-report-maven-plugin/ [2] http://www.ibiblio.org/maven2/org/apache/maven/plugins/maven-site-plugin/ On 3/11/06, Miguel Griffa [EMAIL PROTECTED] wrote: I've removed the version and the report got generate in the same way as before, without finding any tests (tests that I see run while running site, BTW) So I specified version 2.0-SNAPSHOT and got this GroupId: org.codehaus.mojo ArtifactId: surefire-report-maven-plugin Version: 2.0-SNAPSHOT Reason: Unable to download the artifact from any repository org.codehaus.mojo:surefire-report-maven-plugin:pom:2.0-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), tech-1 (http://localhost:9090/testux/maven2/), wife.repo (http://wife.sf.net/m2-snapshots/), wire.repo2 (http://wife.sf.net/m2-repository/) probably because I haven't installed a snapshot of the plugin locally I specified version 2.0-beta-4 but it wasn't found (I've already checked and defined that dep by seeing the only deployed version at http://www.ibiblio.org/maven2/org/codehaus/mojo/surefire-report-maven-plugin/ ) so my guess is, did you compile the plugin locally? or: do you have another repository defined? thank you all so much On 3/11/06, Alexandre Poitras [EMAIL PROTECTED] wrote: I agree. You shoudn't specify a plugin version unless you really need to (for instance you want to use a snapshot version). This way Maven will tell you when there is a new version released and ask you if you want to install it and use it from now on. On 3/11/06, Wayne Fay [EMAIL PROTECTED] wrote: Sorry about the /src/tests mistake -- you're right, the correct directory is /src/test. I'm not specifying the version number as you are... Mine plugin groupIdorg.codehaus.mojo/groupId artifactIdsurefire-report-maven-plugin/artifactId /plugin Yours: plugin groupIdorg.codehaus.mojo/groupId artifactIdsurefire-report-maven-plugin/artifactId version2.0-beta-1/version /plugin Perhaps this is causing your issue? I'm not sure what the most recent release is but according to my local user repo I've got: 2.0-20060106.225541-3 2.0-alpha-2 2.0-beta-4 2.0-SNAPSHOT Without specifying a version, I'm getting maven-site-plugin:2.0-beta-4. I'd assume there are updates between beta-1 and beta-4 that you are missing, which is leading to some of your troubles. Wayne On 3/10/06, Miguel Griffa [EMAIL PROTECTED] wrote: I alsgo have all test classes named FooTest but the dir is src/test/java (note singluar test, not plural) however, if I run mvn test, it will take 20' to run all tests, but when I run site, tests are run, but report says 0 tests. I noticed there are not TESTfoo.xml in the generated reports dir, but I guess that should be automatic, shouldn't it? you didn't have to set anything special, did you? plugin is defined like this reporting plugins plugin groupIdorg.codehaus.mojo/groupId artifactIdsurefire-report-maven-plugin/artifactId version2.0-beta-1/version /plugin On 3/10/06, Wayne Fay [EMAIL PROTECTED] wrote: I also use it with zero issues. Tests are in src/tests/java and named BlahVOTest.java with methods setUp, tearDown, and testBlah1, testBlah2, etc. I can only think you are doing something strange, Miguel. ;-) Wayne On 3/10/06, Alexandre Poitras [EMAIL PROTECTED] wrote: I use it without any problems. What are you test methods names ? textXXX ? Or you prefer to use test suites? On 3/10/06, Miguel Griffa [EMAIL PROTECTED] wrote: anyone being able to use surfire test report in m2? I have a project with 2000+ tests, with m2 dir layout and test report says all zero... any ideas? -- Miguel Griffa Skype: miguel.griffa Y!: m_griffa MSN: [EMAIL PROTECTED] Cell:
CRITICAL: Line too long error when I try to fork the compiler for jdk1.3
On Windows XP ( haven't tried it on unix or linux as yet) I get line too long error. This only happens for the projects that have more than 40 files or classpath entries are too many. Is there a way I can fix this? Please advice. cheers, Sanjay
Re: CRITICAL: Line too long error when I try to fork the compiler for jdk1.3
It seems to be a known issue: http://jira.codehaus.org/browse/MCOMPILER-22 Please stop directly CCing me on these mails. I already read the list. - Brett On 3/12/06, Sanjay Choudhary [EMAIL PROTECTED] wrote: On Windows XP ( haven't tried it on unix or linux as yet) I get line too long error. This only happens for the projects that have more than 40 files or classpath entries are too many. Is there a way I can fix this? Please advice. cheers, Sanjay - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven 2.0 and j2ee and serious work
Hi, I use maven 1.1 in my project in Bank of America and it has been very handy. But I reluctant to migrate to Maven 2.0 because of the lack of the j2ee support. It does not matter how nice and wonderful the new features of Maven 2.0 are, at the end of day is how it can support serious work. I can play it around for entertainment but I will stick to Maven 1 until I see a minimum of enterprise level application support in Maven 2.0 (and I am including j2ee and web services in the minimum requirement level). If maven 2 wants to be taken seriously it MUST support j2ee and web services otherwise maven 1.1 will stick for much longer than you expect. Thanks for the good work on maven 1 and I hope maven 2 will improve (at lot - with much better documentation) Roberto N Nanamura
