Re: Checktyle report incomplete
http://maven.apache.org/plugins/maven-checkstyle-plugin/checkstyle-mojo.html#includes You should use this command instead: mvn -Dcheckstyle.includes=**/Named.java compile pre-site checkstyle:checkstyle John Coleman wrote: Hi, When I run the command below I only get checkstyle reports for 2 classes in the project, and the class I have named is missed out. Why isn't the file I have referred to used? Perhaps I cannot put maven properties on the command line, who knows? mvn -Dmaven.checkstyle.includes=**/Named.java compile pre-site checkstyle:checkstyle TIA, John Eurobase International Limited and its subsidiaries (Eurobase) are unable to exercise control over the content of information in E-Mails. Any views and opinions expressed may be personal to the sender and are not necessarily those of Eurobase. Eurobase will not enter into any contractual obligations in respect of any part of its business in any E-mail. Privileged / confidential information may be contained in this message and /or any attachments. This E-mail is intended for the use of the addressee(s) only and may contain confidential information. If you are not the / an intended recipient, you are hereby notified that any use or dissemination of this communication is strictly prohibited. If you receive this transmission in error, please notify us immediately, and then delete this E-mail. Neither the sender nor Eurobase accepts any liability whatsoever for any defects of any kind either in or arising from this E-mail transmission. E-Mail transmission cannot be guaranteed to be secure or error-free, as messages can be intercepted, lost, corrupted, destroyed, contain viruses, or arrive late or incomplete. Eurobase does not accept any responsibility for viruses and it is your responsibility to scan any attachments. Eurobase Systems Limited is the main trading company in the Eurobase International Group; registered in England and Wales as company number 02251162; registered address: Essex House, 2 County Place, Chelmsford, Essex CM2 0RE, UK. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: ejb manifest -- strip version numbers of dependencies
You could have a go with the 2.2-SNAPSHOT version of the plugin. That
version has an updated version of Maven Archiver, which is the component
that handles everything you put into the archive configuration.
Michael Hüttermann wrote:
Hello,
I create an EJB and want to cut off the version numbers of my dependencies
which are put into my manifest. I tried the following but it does not work
.. the message is Failed to configure plugin parameters for:
org.apache.maven.plugins:maven-ejb-plugin:2.1. How can I cut off the
version numbers? Thank you !!
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-ejb-plugin/artifactId
configuration
ejbVersion2.1/ejbVersion
generateClientfalse/generateClient
archive
manifest
addClasspathtrue/addClasspath
classpathLayoutTypecustom/classpathLayoutType
customClasspathLayout${artifact.artifactId}/customClasspathLayout
/manifest
/archive
/configuration
/plugin
Michael
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
--
Dennis Lundberg
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
RE: dependency:unpack-dependencies not updating releases
Hi Brian, I'm confused. What is the meaning of an updatePolicy for releases? repositories repository releases updatePolicyalways/updatePolicy /releases snapshots updatePolicyalways/updatePolicy /snapshots idcaplin/id urlfile:/maven/maven-repo/url /repository Richard -Original Message- From: Brian E. Fox [mailto:bri...@reply.infinity.nu] Sent: 27 March 2009 18:44 To: Maven Users List Subject: RE: dependency:unpack-dependencies not updating releases By changing a release artifact you are violating Maven Commandment #1: Release artifacts are immutable. Maven will never recheck for updated release artifacts, so it will just hand back what's in the local repository to the plugin every time. -Original Message- From: Richard Chamberlain [mailto:richard.chamberl...@caplin.com] Sent: Friday, March 27, 2009 12:28 PM To: Maven Users List Subject: dependency:unpack-dependencies not updating releases Hi, I'm using dependency:unpack-dependencies to get some zips of artefacts from our company repository. However if I update a released artefact without changing the version (i.e. documentation change), our company repository is never checked by my script. The only way to get the latest version is to delete the artefact from my cache so it re-resolves it. When a dependency is a snapshot it is always updated. The command i'm using is: mvn dependency:unpack-dependencies -DoutputDirectory=mvn -DmarkersDirectory=mvn And the output from mvn help:effective-pom shows that my updatePolicy is set to always: ... repositories repository releases updatePolicyalways/updatePolicy /releases snapshots updatePolicyalways/updatePolicy /snapshots idcaplin/id urlfile:/maven/maven-repo/url /repository repository snapshots enabledfalse/enabled /snapshots idcentral/id nameMaven Repository Switchboard/name urlhttp://repo1.maven.org/maven2/url /repository /repositories ... My project pom file is: ?xml version=1.0? project modelVersion4.0.0/modelVersion groupIdcaplin/groupId artifactIdtestproject/artifactId version1.4.1/version dependencies dependency groupIdtest.richardc/groupId artifactIdtest/artifactId version1.0/version typezip/type /dependency /dependencies /project And the debug output is: D:\Development\Sandbox\testmvn -X dependency:unpack-dependencies -DoutputDirect ory=mvn -DmarkersDirectory=mvn + Error stacktraces are turned on. Maven version: 2.0.10-RC7 Java version: 1.5.0_08 OS name: windows xp version: 5.1 arch: x86 Family: windows [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settin gs\richardc\.m2\plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: 'D:\buildTools\apache- maven-2.0.10-RC7\bin\..\conf\plugin-registry.xml' [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'dependency'. [DEBUG] Loading plugin prefixes from group: com.octo.mtg [DEBUG] Loading plugin prefixes from group: org.apache.maven.plugins [DEBUG] Loading plugin prefixes from group: org.codehaus.mojo [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins:pom:10 for project: org.apache.maven.plugins:maven-dependency-plugin:maven-plugin:2.0 from the repository. [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent:pom:7 for project: org.apache.maven.plugins:maven-plugins:pom:10 from the repository. [DEBUG] Retrieving parent-POM: org.apache:apache:pom:4 for project: org.apache.m aven:maven-parent:pom:7 from the repository. [DEBUG] Wagons could not be registered as the extension container was never crea ted [INFO] [INFO] Building Unnamed - caplin:testproject:jar:1.4.1 [INFO]task-segment: [dependency:unpack-dependencies] [INFO] [DEBUG] caplin:testproject:jar:1.4.1 (selected for null) [DEBUG] test.richardc:test:zip:1.0:compile (selected for compile) [DEBUG] Plugin dependencies for: org.apache.maven.plugins:maven-dependency-plugin:2.0 are: org.apache.maven:maven-artifact:jar:2.0.8:runtime org.apache.maven:maven-plugin-api:jar:2.0.8:runtime org.apache.maven:maven-project:jar:2.0.8:runtime org.apache.maven:maven-model:jar:2.0.8:runtime org.apache.maven:maven-core:jar:2.0.8:runtime org.codehaus.plexus:plexus-archiver:jar:1.0-alpha-9:runtime org.codehaus.plexus:plexus-utils:jar:1.4.6:runtime org.apache.maven.shared:file-management:jar:1.1:runtime
POM 'org.apache.maven.plugins:maven-checkstyle-plugin' no t found in repository: Unable to download the artifact from any repository
Hi, I'm trying to set up Sonar for our project. (http://docs.codehaus.org/display/SONAR/Collect+data#Collectdata-NonMavenprojects(sonarlightmode)) Currently, I have the following ERROR and I couldn't find the solution. May be somebody can advise what's wrong. I use Maven 2.0.10. mvn org.codehaus.sonar:sonar-maven-plugin:1.7:sonar [INFO] Scanning for projects... [INFO] [INFO] Building My Project [INFO]task-segment: [org.codehaus.sonar:sonar-maven-plugin:1.7:sonar] (aggre gator-style) [INFO] Downloading: http://repo1.maven.org/maven2/xerces/xercesImpl/2.0.2/xercesImpl-2. 0.2.pom [INFO] [sonar:sonar] [INFO] [INFO] Building My Project [INFO]task-segment: [org.codehaus.sonar:sonar-core-maven-plugin:1.7:dependen cies] [INFO] Downloading: http://repo1.maven.org/maven2/xerces/xercesImpl/2.0.2/xercesImpl-2. 0.2.pom [INFO] [sonar-core:dependencies] [INFO] [INFO] Building My Project [INFO]task-segment: [org.codehaus.sonar:sonar-core-maven-plugin:1.7:prepare] [INFO] Downloading: http://dbmosws2169.ru.com:9000/deploy/maven/xerces/xercesImpl/2. 0.2/xercesImpl-2.0.2.pom Downloading: http://repo1.maven.org/maven2/xerces/xercesImpl/2.0.2/xercesImpl-2. 0.2.pom [INFO] [sonar-core:prepare] [INFO] org.sonar.maven.ProfileProvider Selected quality profile : Sonar way, lan guage=java Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-checks tyle-plugin/2.2/maven-checkstyle-plugin-2.2.pom Downloading: http://repo1.maven.org/maven2/org/apache/maven/plugins/maven-checks tyle-plugin/2.2/maven-checkstyle-plugin-2.2.pom Downloading: http://dbmosws2169.ru.com:9000/deploy/maven/org/apache/maven/plu gins/maven-checkstyle-plugin/2.2/maven-checkstyle-plugin-2.2.pom [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Cannot execute the command org.apache.maven.plugins:maven-checkstyle-plug in::checkstyle Embedded error: Unable to build project for plugin 'org.apache.maven.plugins:mav en-checkstyle-plugin': POM 'org.apache.maven.plugins:maven-checkstyle-plugin' no t found in repository: Unable to download the artifact from any repository org.apache.maven.plugins:maven-checkstyle-plugin:pom:2.2 from the specified remote repositories: sonar (http://dbmosws2169.ru.com:9000/deploy/maven), central (http://repo1.maven.org/maven2) for project org.apache.maven.plugins:maven-checkstyle-plugin [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 2 minutes 19 seconds [INFO] Finished at: Mon Mar 30 13:01:36 MSD 2009 [INFO] Final Memory: 6M/18M [INFO] -- View this message in context: http://n2.nabble.com/POM-%27org.apache.maven.plugins%3Amaven-checkstyle-plugin%27-no-t-found-in-repository%3A-Unable-to-download-the-artifact-from-any-repository-tp2556257p2556257.html Sent from the maven users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Checktyle report incomplete
Yes that works, many thanks. Are there similar ways to do this for the PMD report and Corbertura? It would be nice if the reporting plugins were more consistent. TIA John -Original Message- From: Dennis Lundberg [mailto:dennisl.apa...@gmail.com] On Behalf Of Dennis Lundberg Sent: 28 March 2009 17:06 To: Maven Users List Subject: Re: Checktyle report incomplete http://maven.apache.org/plugins/maven-checkstyle-plugin/checks tyle-mojo.html#includes You should use this command instead: mvn -Dcheckstyle.includes=**/Named.java compile pre-site checkstyle:checkstyle John Coleman wrote: Hi, When I run the command below I only get checkstyle reports for 2 classes in the project, and the class I have named is missed out. Why isn't the file I have referred to used? Perhaps I cannot put maven properties on the command line, who knows? mvn -Dmaven.checkstyle.includes=**/Named.java compile pre-site checkstyle:checkstyle TIA, John Eurobase International Limited and its subsidiaries (Eurobase) are unable to exercise control over the content of information in E-Mails. Any views and opinions expressed may be personal to the sender and are not necessarily those of Eurobase. Eurobase will not enter into any contractual obligations in respect of any part of its business in any E-mail. Privileged / confidential information may be contained in this message and /or any attachments. This E-mail is intended for the use of the addressee(s) only and may contain confidential information. If you are not the / an intended recipient, you are hereby notified that any use or dissemination of this communication is strictly prohibited. If you receive this transmission in error, please notify us immediately, and then delete this E-mail. Neither the sender nor Eurobase accepts any liability whatsoever for any defects of any kind either in or arising from this E-mail transmission. E-Mail transmission cannot be guaranteed to be secure or error-free, as messages can be intercepted, lost, corrupted, destroyed, contain viruses, or arrive late or incomplete. Eurobase does not accept any responsibility for viruses and it is your responsibility to scan any attachments. Eurobase Systems Limited is the main trading company in the Eurobase International Group; registered in England and Wales as company number 02251162; registered address: Essex House, 2 County Place, Chelmsford, Essex CM2 0RE, UK. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Verbatim HTML in site documentation
Can't you use xdoc? Xdoc is basically xhtml with some additional tags, see http://maven.apache.org/doxia/references/xdoc-format.html -Lukas TomStrummer wrote: I just realized the snippet macro is actually not at all what I'm looking for. I don't want the source of a file displayed in my document; instead I want to actually _render_ a piece of verbatim HTML. So that I can i.e. include a form that the user can fill out and submit. Thanks! Lukas Theussl-3 wrote: TomStrummer wrote: Hi, I'm trying to figure out how I can add a little HTML into a site documentation page. I haven't found any examples of this in the APT or XDoc documentation. Is it possible? I'm actually trying to insert a little markup for a generated PayPal Donate button. Thanks in advance. Sounds like this issue: http://jira.codehaus.org/browse/DOXIA-142 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: dependency:unpack-dependencies not updating releases
It's because the same modello model is used for both, but that value is ignored. Trust me, if you try to start changing releases, you will have endless problems. -Original Message- From: Richard Chamberlain [mailto:richard.chamberl...@caplin.com] Sent: Monday, March 30, 2009 4:39 AM To: Maven Users List Subject: RE: dependency:unpack-dependencies not updating releases Hi Brian, I'm confused. What is the meaning of an updatePolicy for releases? repositories repository releases updatePolicyalways/updatePolicy /releases snapshots updatePolicyalways/updatePolicy /snapshots idcaplin/id urlfile:/maven/maven-repo/url /repository Richard -Original Message- From: Brian E. Fox [mailto:bri...@reply.infinity.nu] Sent: 27 March 2009 18:44 To: Maven Users List Subject: RE: dependency:unpack-dependencies not updating releases By changing a release artifact you are violating Maven Commandment #1: Release artifacts are immutable. Maven will never recheck for updated release artifacts, so it will just hand back what's in the local repository to the plugin every time. -Original Message- From: Richard Chamberlain [mailto:richard.chamberl...@caplin.com] Sent: Friday, March 27, 2009 12:28 PM To: Maven Users List Subject: dependency:unpack-dependencies not updating releases Hi, I'm using dependency:unpack-dependencies to get some zips of artefacts from our company repository. However if I update a released artefact without changing the version (i.e. documentation change), our company repository is never checked by my script. The only way to get the latest version is to delete the artefact from my cache so it re-resolves it. When a dependency is a snapshot it is always updated. The command i'm using is: mvn dependency:unpack-dependencies -DoutputDirectory=mvn -DmarkersDirectory=mvn And the output from mvn help:effective-pom shows that my updatePolicy is set to always: ... repositories repository releases updatePolicyalways/updatePolicy /releases snapshots updatePolicyalways/updatePolicy /snapshots idcaplin/id urlfile:/maven/maven-repo/url /repository repository snapshots enabledfalse/enabled /snapshots idcentral/id nameMaven Repository Switchboard/name urlhttp://repo1.maven.org/maven2/url /repository /repositories ... My project pom file is: ?xml version=1.0? project modelVersion4.0.0/modelVersion groupIdcaplin/groupId artifactIdtestproject/artifactId version1.4.1/version dependencies dependency groupIdtest.richardc/groupId artifactIdtest/artifactId version1.0/version typezip/type /dependency /dependencies /project And the debug output is: D:\Development\Sandbox\testmvn -X dependency:unpack-dependencies -DoutputDirect ory=mvn -DmarkersDirectory=mvn + Error stacktraces are turned on. Maven version: 2.0.10-RC7 Java version: 1.5.0_08 OS name: windows xp version: 5.1 arch: x86 Family: windows [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settin gs\richardc\.m2\plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: 'D:\buildTools\apache- maven-2.0.10-RC7\bin\..\conf\plugin-registry.xml' [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'dependency'. [DEBUG] Loading plugin prefixes from group: com.octo.mtg [DEBUG] Loading plugin prefixes from group: org.apache.maven.plugins [DEBUG] Loading plugin prefixes from group: org.codehaus.mojo [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins:pom:10 for project: org.apache.maven.plugins:maven-dependency-plugin:maven-plugin:2.0 from the repository. [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent:pom:7 for project: org.apache.maven.plugins:maven-plugins:pom:10 from the repository. [DEBUG] Retrieving parent-POM: org.apache:apache:pom:4 for project: org.apache.m aven:maven-parent:pom:7 from the repository. [DEBUG] Wagons could not be registered as the extension container was never crea ted [INFO] [INFO] Building Unnamed - caplin:testproject:jar:1.4.1 [INFO]task-segment: [dependency:unpack-dependencies] [INFO] [DEBUG] caplin:testproject:jar:1.4.1 (selected for null) [DEBUG] test.richardc:test:zip:1.0:compile (selected for compile) [DEBUG] Plugin dependencies for: org.apache.maven.plugins:maven-dependency-plugin:2.0 are: org.apache.maven:maven-artifact:jar:2.0.8:runtime org.apache.maven:maven-plugin-api:jar:2.0.8:runtime
Re: Verbatim HTML in site documentation
Know what? The section on validation and block elements gave me the impression that XDoc provided a restricted subset of HTML. I missed where it said any valid XHTML could be used. I tried it and it works great. Sorry for the confusion and thanks again for the help. Lukas Theussl-3 wrote: Can't you use xdoc? Xdoc is basically xhtml with some additional tags, see http://maven.apache.org/doxia/references/xdoc-format.html -Lukas TomStrummer wrote: I just realized the snippet macro is actually not at all what I'm looking for. I don't want the source of a file displayed in my document; instead I want to actually _render_ a piece of verbatim HTML. So that I can i.e. include a form that the user can fill out and submit. Thanks! Lukas Theussl-3 wrote: TomStrummer wrote: Hi, I'm trying to figure out how I can add a little HTML into a site documentation page. I haven't found any examples of this in the APT or XDoc documentation. Is it possible? I'm actually trying to insert a little markup for a generated PayPal Donate button. Thanks in advance. Sounds like this issue: http://jira.codehaus.org/browse/DOXIA-142 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://www.nabble.com/Verbatim-HTML-in-site-documentation-tp22559536p22781966.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Sharing Maven-based project
Yes, create a repository for your unit/company. You don't want to let your colleagues download artifacs manually from eg. SVN. We use Artifactoy as a repository and central mirror for every maven installation in the company. Its running on Tomcat, easy to install and integrated with the company LDAP. Regards Am 29.03.2009 um 16:08 schrieb HHB: Hey, I use Maven as the build tool for our project. Now my team mates want to checkout the project from the SVN and I want to add the project to out continuous integration server (Hudson). I'm not sure but should I create a central repository in our unit? or let each mate (and CI server) download the dependency himself? What repository manager do you suggest? Thanks. -- View this message in context: http://www.nabble.com/Sharing-Maven-based-project-tp22767986p22767986.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How to perform a deploy only
I still don't think your solution is easier than mvn install if not errorlevel 1 mvn deploy:deploy But - everyone has their own solutions ;) Thanks for sharing. Stefan On Fri, 27 Mar 2009 13:17:43 -0500 Jim McCaskey jim.mccas...@pervasive.com wrote: Hi Stephen, Sure no problem. What I came up with was another set of posts, and was essentially following the advice you gave me a few days ago and some help from Dan Tran. That is, I use mvn deploy but output to a empty directory, then use a maven plugin to merge that to my primary repository. Here are some details (note I am using Maven 2.1.0 on Windows machines). So essentially I build like this: mvn -DaltDeploymentRepository=repo::default::file://E:\staging-repo deploy I then use the wagon-maven-plugin to merge this sparse area up to my corporate repository like this: mvn org.codehaus.mojo:wagon-maven-plugin:1.0-beta-1:merge-maven-repos -Dwagon.source=file://E:\staging-repo -Dwagon.target=file://\\server\share\mavenrepo -Djava.io.tmpdir=deploytemp Note that deploytemp is a directory that is created in the local directory. I can't seem to point it to a C:\temp for some reason, and really don't care. I just create the directory and use it. It's empty when it gets done. If you don't create that directory (or forget the java.io.tmpdir), you get a rather cryptic message about volume labels. I'm able to chain these two commands together after appropriate error checking in my automation server (IBM Rational Build Forge FWIW). So what I was after originally was a step for me to build, then another step to deploy only that I could use later on after everything was done. This accomplishes that goal, with a little help from the wagon-maven-plugin, and Dan Tran. Needless to say this methodology was not documented anywhere that I could find, so I am guessing that not many folks are interested in it. Frankly without the nudges in the right direction from this list, I would not have been able to figure it out. So thanks to everyone. -Jim -Original Message- From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Sent: Friday, March 27, 2009 12:45 PM To: Maven Users List Subject: Re: How to perform a deploy only Any chance you could post your solution? 2009/3/27 Jim McCaskey jim.mccas...@pervasive.com I have found a solution that is working nicely. Having said that, I don't think the request is that farfetched. When doing a deploy, you would definitely want to make sure that all the components that made up the run built successfully before deploying. Not doing so leaves your repository in a corrupt state. Perhaps having the ability to delay the deploy phase until all components are built/tested is what is needed, not necessarily a Deploy only ability. In other words, run all other phases for all components, then swing back through on a deploy run once all components are verified to build/test. My guess would be that as more and more projects use Maven to glue everything together, these sorts of things will come up more often. Anyway just a suggestion. Like I say, I have a solution that I'm happy with. -Jim -Original Message- From: Brian E. Fox [mailto:bri...@reply.infinity.nu] Sent: Thursday, March 26, 2009 9:43 PM To: Maven Users List Subject: RE: How to perform a deploy only Running the full lifecycle is a fundamental of Maven, so this type of feature request is unlikely to gain traction. You should rather look at your build configuration to solve the problem, or as mentioned use a repo man that can help you out. -Original Message- From: Jim McCaskey [mailto:jim.mccas...@pervasive.com] Sent: Wednesday, March 25, 2009 11:26 PM To: 'Maven Users List' Subject: RE: How to perform a deploy only Thanks for the suggestion. I have been trying to avoid using repository managers for a number of reasons that are beyond the scope of this thread. I may have to break down eventually... I'm surprised no one has needed this sort of feature, or maybe they have and that's why Nexus has the features that it does. I was hoping to find a Maven native (whatever native means in a highly pluggable architecture) way to do this that would not take much additional work. mvn -DdoNothingButDeploy=true deploy That would be about perfect. :) Would this even be consider for an enhancement request if I opened it? Perhaps I am the only one interested in such a thing. Thanks! -Jim -Original Message- From: Edelson, Justin [mailto:justin.edel...@mtvstaff.com] Sent: Wednesday, March 25, 2009 9:55 PM To: Maven Users List Subject: RE: How to perform a deploy only Brian can pitch his own stuff far better than I can, but this kind of transactional deployment can be done with Nexus' Staging feature. I realized after I sent my
Maven surefire plugin - testFailureIgnore and its behaviour with forkMode
I am using Maven surefire plugin 2.4.2 with the following configurations: plugin artifactIdmaven-surefire-plugin/artifactId configuration ... testFailureIgnorefalse/testFailureIgnore ... forkModealways/forkMode ... /configuration /plugin I have intentionally set testFailureIgnore=false (i.e. the default value), so that if the test fails the build process fails. However when my tests fail with ERROR, i see that irrespective of this property value, the rest of the build is carried out and the build reports a SUCCESS. A bit of debugging and playing with the forkMode, shows that the testFailureIgnore=false results in the build to fail (which is what i expect) *only* when the forkMode is set to never. Setting the forkMode to always or once always results in a successful build irrespective of the testFailureIgnore setting. Is this the expected behaviour? -- View this message in context: http://www.nabble.com/Maven-surefire-plugin---testFailureIgnore-and-its-behaviour-with-forkMode-tp22782458p22782458.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
AW: SpeedUp the release process
how can i define the local directory? please could you post a pom.xml snippet for that? -Ursprüngliche Nachricht- Von: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Gesendet: Freitag, 27. März 2009 22:57 An: Maven Users List Betreff: Re: SpeedUp the release process we deploy the site to a local directory and then afterwards copy the site to the web server location 2009/3/27 Hoehmann, Andreas andreas.hoehmann@siemens.com Hi folks, i have a multi-module-project (~30 artifacts). I wrote a little script to release the whole project from root - check dependencies - try site-build - try release:prepare - clean up - release:prepare - release:perform - deploy new snapshots My repository works with webdav behind a apache2. The release of the 30 artifacts is running ~ 2 hours ... and the most time cost the deployment of the project-sites (upload javadoc etc.) ... is there a better way to deploy a project-site, e.g. deploy in a local mounten networkdevice, or in a local directory and the syn to the server ? Ideas are welcome :) Regards andreas - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: How to perform a deploy only
With the minor caveat that I could never get mvn deploy:deploy to work at all. :) I had posted the error I was getting several days ago. Thanks for the suggestion though. In any event, I like this solution a lot better the more I have used it. It prevents any and all accidental running of anything. It does not even make use of my existing pom's (they are not needed). -Jim -Original Message- From: Stefan Seidel [mailto:ssei...@vub.de] Sent: Monday, March 30, 2009 4:55 AM To: users@maven.apache.org Subject: Re: How to perform a deploy only I still don't think your solution is easier than mvn install if not errorlevel 1 mvn deploy:deploy But - everyone has their own solutions ;) Thanks for sharing. Stefan On Fri, 27 Mar 2009 13:17:43 -0500 Jim McCaskey jim.mccas...@pervasive.com wrote: Hi Stephen, Sure no problem. What I came up with was another set of posts, and was essentially following the advice you gave me a few days ago and some help from Dan Tran. That is, I use mvn deploy but output to a empty directory, then use a maven plugin to merge that to my primary repository. Here are some details (note I am using Maven 2.1.0 on Windows machines). So essentially I build like this: mvn -DaltDeploymentRepository=repo::default::file://E:\staging-repo deploy I then use the wagon-maven-plugin to merge this sparse area up to my corporate repository like this: mvn org.codehaus.mojo:wagon-maven-plugin:1.0-beta-1:merge-maven-repos -Dwagon.source=file://E:\staging-repo -Dwagon.target=file://\\server\share\mavenrepo -Djava.io.tmpdir=deploytemp Note that deploytemp is a directory that is created in the local directory. I can't seem to point it to a C:\temp for some reason, and really don't care. I just create the directory and use it. It's empty when it gets done. If you don't create that directory (or forget the java.io.tmpdir), you get a rather cryptic message about volume labels. I'm able to chain these two commands together after appropriate error checking in my automation server (IBM Rational Build Forge FWIW). So what I was after originally was a step for me to build, then another step to deploy only that I could use later on after everything was done. This accomplishes that goal, with a little help from the wagon-maven-plugin, and Dan Tran. Needless to say this methodology was not documented anywhere that I could find, so I am guessing that not many folks are interested in it. Frankly without the nudges in the right direction from this list, I would not have been able to figure it out. So thanks to everyone. -Jim -Original Message- From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Sent: Friday, March 27, 2009 12:45 PM To: Maven Users List Subject: Re: How to perform a deploy only Any chance you could post your solution? 2009/3/27 Jim McCaskey jim.mccas...@pervasive.com I have found a solution that is working nicely. Having said that, I don't think the request is that farfetched. When doing a deploy, you would definitely want to make sure that all the components that made up the run built successfully before deploying. Not doing so leaves your repository in a corrupt state. Perhaps having the ability to delay the deploy phase until all components are built/tested is what is needed, not necessarily a Deploy only ability. In other words, run all other phases for all components, then swing back through on a deploy run once all components are verified to build/test. My guess would be that as more and more projects use Maven to glue everything together, these sorts of things will come up more often. Anyway just a suggestion. Like I say, I have a solution that I'm happy with. -Jim -Original Message- From: Brian E. Fox [mailto:bri...@reply.infinity.nu] Sent: Thursday, March 26, 2009 9:43 PM To: Maven Users List Subject: RE: How to perform a deploy only Running the full lifecycle is a fundamental of Maven, so this type of feature request is unlikely to gain traction. You should rather look at your build configuration to solve the problem, or as mentioned use a repo man that can help you out. -Original Message- From: Jim McCaskey [mailto:jim.mccas...@pervasive.com] Sent: Wednesday, March 25, 2009 11:26 PM To: 'Maven Users List' Subject: RE: How to perform a deploy only Thanks for the suggestion. I have been trying to avoid using repository managers for a number of reasons that are beyond the scope of this thread. I may have to break down eventually... I'm surprised no one has needed this sort of feature, or maybe they have and that's why Nexus has the features that it does. I was hoping to find a Maven native (whatever native means in a highly pluggable architecture) way to do this that would not take much additional work. mvn -DdoNothingButDeploy=true deploy That
Assemble zip from multiple modules
I want to make a distribution containing several war files, located in modules in my parent pom. The file would look like this: file.zip | --file.ear | | | --- project1.war | --- project2.war | --- project3.war | --- project4.war |--- project5.war |--- Releasenotes.txt Is this possible with the assemble plugin? I have no clue how to do this. I would appreciate any links with some real examples how to accomplish this scenario. But any help is appreciated Thanks in advance -- View this message in context: http://www.nabble.com/Assemble-zip-from-multiple-modules-tp22783969p22783969.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
swap between snapshot- and release versions in a large system
Hi, we have a large system, containing separate software modules (backend.ear, ui.war, services.war and so on) During developement, we use snapshot dependencies to reference the other modules. So a version of the whole system can be build by one click on our buildsystem, which than just deploys a new snapshot version and all is fine. During release (one times a week) we need first to release the modules one by one - actually per hand, swap dependency versions and so on, than swap dependency versions back to next snapshot for the develeopement of next week and so on. This is very error-prone and time consuming. What´s the way to do this more efficient? Always build the whole system as one multimodule build? Is there a plugin that automatically can change dependency versions in pom.xml if there are newer versions available? Thanx, torsten
Re: Maven surefire plugin - testFailureIgnore and its behaviour with forkMode
As far as I know, it's not expected behaviour. If you can create a jira issue with a sample project to reproduce this, I'm sure someone can take a look. Also, try version 2.4.3 since that is the latest. Jaikiran wrote: I am using Maven surefire plugin 2.4.2 with the following configurations: plugin artifactIdmaven-surefire-plugin/artifactId configuration ... testFailureIgnorefalse/testFailureIgnore ... forkModealways/forkMode ... /configuration /plugin I have intentionally set testFailureIgnore=false (i.e. the default value), so that if the test fails the build process fails. However when my tests fail with ERROR, i see that irrespective of this property value, the rest of the build is carried out and the build reports a SUCCESS. A bit of debugging and playing with the forkMode, shows that the testFailureIgnore=false results in the build to fail (which is what i expect) *only* when the forkMode is set to never. Setting the forkMode to always or once always results in a successful build irrespective of the testFailureIgnore setting. Is this the expected behaviour? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Variable substitution question...
I've searched the archives for this but no luck -
I need to build my web.xml file with specific values based on the target
environment for which I'm performing the build. Therefore, I'd like maven
to perform some variable substitution when I run the mvn install goal. I'm
trying to use profiles for this (though I obviously lack solid
understanding of profiles at this point). Here is what I did:
I've setup 3 profiles in the parent pom.xml file like this:
profiles
profile
iddev/id
activation
activeByDefaulttrue/activeByDefault
/activation
properties
app.context.parmdev_values.../app.context.parm
/properties
/profile
profile
idqa/id
properties
app.context.parmqa_values.../app.context.parm
/properties
/profile
profile
idprod/id
properties
app.context.parmprod_values.../app.context.parm
/properties
/profile
/profiles
In my web.xml file I currently have something like this:
context-param
param-namecontextConfigLocation/param-name
param-value${app.context.parm}/param-value -- need the
variable substitution HERE...
/context-param
I then run mvn -Pqa install goal, hoping that maven will insert the proper
application context values into this placeholder based on the profile
that's active, but so far this does not work for me... please tell me
what else I'm missing to make this work.
Thanks,
James
Re: Grandparent classes not found at compile time
I've been using the m2eclipse dependency hierarchy view, as well. That helped me identify the extra piece I needed to include. But if I must do manual dependency analysis every time I update a third party jar -- just in case it now incurs a new dependency for me -- then what value are transitive dependencies in Maven at all? Regards, Brian. Stephen Connolly-2 wrote: have a look at dependency:analyze it will tell you what you are depending on in-directly and you can then add those indirect dependencies to your pom 2009/3/28 Trinition trin+nabble@trinition.org The problem I have is that I don't necesssarily know what the dependencies need to be. If I pull in thidparty.jar so I can use one of the classes in it, how do I know if one of the classes actually extends someone else's class in another jar? And if the next release of thirdparty.jar changes their internal implementations, I have to revisit this again. I thought this was the point of having transitive dependency support in Maven. If this isn't the reason, what is? Regards, Brian. Stephen Connolly-2 wrote: if your module requires the dependency to complie then it is a dependency of your module what you describe as a work around is actually what you are supposed to do the real issue is that compile is transitive. compile needs to be transitive as a runtime dependency but should not be a transitive compile dependency in order to force you to list all your dependencies in your pom in short, if your module needs the dependency to compile, you should add it as a dependency and not rely on it being pulled in as a transitive dependency of anothe dependency of yours On 27/03/2009, Trinition trin+nabble@trinition.org wrote: I'm confused about why transitive provided dependencies shouldn't be included at compile time. I have a project, myapp-web, which defines a custom Servlet, MyServlet. MyServlet extends a BaseServlet from framework. BaseServlet extends a Servlet class from thirdparty, ThirdPartyServlet. ThirdPartyServlet in turn implements the third party's CacheableServlet interface among other things. myapp-web: MyServlet framework: BaseServlet thirdparty: ThidrdPartyServlet, CacheableServlet, etc. So myapp's pom declares a compile-time dependency on framework, and framework declares a provided dependency on thirdparty. This is because the thirdparty jar is available at runtime in my container, thus I don't want to ever include it transitively for packaging. So when myapp-web compiles, it needs the definition of BaseServlet.class which it finds in its compile time dependency of framework. However, it seems to not know about the definitions of BaseServelt's parent class (MyServlet's grandparent class), ThirdPartyServlet. I get compile-time errors like these: MyServlet.java:[199,20] cannot find symbol symbol : variable this location: class com.myapp.MyServlet MyServlet.java:[201,24] cannot find symbol symbol : variable super location: class com.myapp.MyServlet Because MyServlet extends BaseServlet which extends ThirdPartyServlet, doesn't the compile NEED to know about all classes in the hierarchy in order to compile? Thus, I would think anything that was available at compile time during the building of BaseServlet COULD BE a compile-time dependency to dependents of framework (such as myapp-web). So why does Maven NOT include provided dependencies transitively at compile time? This is presently blocking me. My workaround is to explicitly add thirdparty as a provided dependency to myapp-web so that the ThirdPartyServlet and CacheableServlet definitions will be available at compile time. But this is the very thing that transitive dependencies solves for COMPILE dependencies (which are really COMPILED and PACKAGED). Why not solve it for TRANSITIVE dependencies (whcich are COMPILED but NOT PACKAGED). -- View this message in context: http://www.nabble.com/Grandparent-classes-not-found-at-compile-time-tp22733894p22733894.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://www.nabble.com/Grandparent-classes-not-found-at-compile-time-tp22733894p22759625.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail:
Config File Consistency
Hello all: I am working in a Maven multi-project environment and I would like to maintain some consistency across projects for some tools like CheckStyle, FindBugs, etc. In order to do this, I am thinking of using the remote resource plugin. However, the documentation states that the files from the resource bundle is deposited in the $basedir/target/classes directory. However, I would like it deposited in the $basedir/some_arbitrary_location directory? Can I configure the directory where the files are deposited or am I off in the weeds and there is an easier way? Thank you, Perry Hoekstra - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
help deploying with tomcat-maven-plugin, please
Anybody can give me a hint about what I am doing wrong, please? I installed tomcat-maven-plugin and tomcat manager plugin for eclipse. My project builds ok after mvn package but when I try to deploy to tomcat server with mvn -e tomcat:exploded it throws org.apache.maven.lifecycle.LifecycleExecutionException: Cannot invoke Tomcat man ager. From the trace I can't find out what I am doing wrong. As far as I am concerned I haven't changed the default settings and my tomcat-users.xml shouldn't be the problem: ?xml version='1.0' encoding='utf-8'? tomcat-users role rolename=tomcat/ role rolename=role1/ role rolename=manager/ role rolename=admin/ user username=tomcat password=tomcat roles=tomcat/ user username=both password=tomcat roles=tomcat,role1/ user username=role1 password=tomcat roles=role1/ user username=manager password=manager roles=manager/ user username=admin password= roles=admin,manager/ /tomcat-users The error log is as follows: C:\Documents and Settings\pablog\workspace2\parentmvn -e tomcat:exploded + Error stacktraces are turned on. [INFO] Scanning for projects... [INFO] Reactor build order: [INFO] OpenCms Parent [INFO] OpenCms Webapp [INFO] OpenCms System [INFO] OpenCms Content [INFO] OpenCms Orgunits [INFO] [INFO] Building OpenCms Parent [INFO]task-segment: [tomcat:exploded] [INFO] [INFO] [tomcat:exploded] [INFO] Skipping non-war project [INFO] [INFO] Building OpenCms Webapp [INFO]task-segment: [tomcat:exploded] [INFO] [INFO] [tomcat:exploded] [INFO] Deploying war to http://localhost:8080/opencms-basic [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Cannot invoke Tomcat manager Embedded error: http://localhost:8080/manager/deploy?path=%2Fopencms-basicwar=f ile%3A%2FC%3A%2FDocuments+and+Settings%2Fpablog%2Fworkspace2%2Fwebapp%2Ftarget%2 Fwebapp%2F [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Cannot invoke Tomcat man ager at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:703) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone Goal(DefaultLifecycleExecutor.java:553) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau ltLifecycleExecutor.java:523) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:371) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:332) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:181) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot invoke Tomcat manager at org.codehaus.mojo.tomcat.AbstractCatalinaMojo.execute(AbstractCatalin aMojo.java:149) at org.codehaus.mojo.tomcat.AbstractWarCatalinaMojo.execute(AbstractWarC atalinaMojo.java:63) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:483) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:678) ... 16 more Caused by: java.io.FileNotFoundException: http://localhost:8080/manager/deploy?p ath=%2Fopencms-basicwar=file%3A%2FC%3A%2FDocuments+and+Settings%2Fpablog%2Fwork space2%2Fwebapp%2Ftarget%2Fwebapp%2F at sun.net.www.protocol.http.HttpURLConnection.getInputStream(HttpURLCon nection.java:1303) at org.codehaus.mojo.tomcat.TomcatManager.invoke(TomcatManager.java:604) at org.codehaus.mojo.tomcat.TomcatManager.deployImpl(TomcatManager.java: 662) at
Re: help deploying with tomcat-maven-plugin, please
Due to the FileNotFoundException I created the target folder opencms-basic manually and now the trace is a bit different (below). It seems to be a problem with permissions accessing tomcat manager... Embedded error: Connection refused: connect [INFO] [INFO] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Cannot invoke Tomcat man ager at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:703) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandalone Goal(DefaultLifecycleExecutor.java:553) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(Defau ltLifecycleExecutor.java:523) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHan dleFailures(DefaultLifecycleExecutor.java:371) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegmen ts(DefaultLifecycleExecutor.java:332) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLi fecycleExecutor.java:181) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:356) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:137) at org.apache.maven.cli.MavenCli.main(MavenCli.java:356) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.plugin.MojoExecutionException: Cannot invoke Tomcat manager at org.codehaus.mojo.tomcat.AbstractCatalinaMojo.execute(AbstractCatalin aMojo.java:149) at org.codehaus.mojo.tomcat.AbstractWarCatalinaMojo.execute(AbstractWarC atalinaMojo.java:63) at org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPlugi nManager.java:483) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(Defa ultLifecycleExecutor.java:678) ... 16 more Caused by: java.net.ConnectException: Connection refused: connect at java.net.PlainSocketImpl.socketConnect(Native Method) at java.net.PlainSocketImpl.doConnect(PlainSocketImpl.java:333) at java.net.PlainSocketImpl.connectToAddress(PlainSocketImpl.java:195) at java.net.PlainSocketImpl.connect(PlainSocketImpl.java:182) at java.net.SocksSocketImpl.connect(SocksSocketImpl.java:366) at java.net.Socket.connect(Socket.java:519) at java.net.Socket.connect(Socket.java:469) at sun.net.NetworkClient.doConnect(NetworkClient.java:163) at sun.net.www.http.HttpClient.openServer(HttpClient.java:394) at sun.net.www.http.HttpClient.openServer(HttpClient.java:529) at sun.net.www.http.HttpClient.init(HttpClient.java:233) at sun.net.www.http.HttpClient.New(HttpClient.java:306) at sun.net.www.http.HttpClient.New(HttpClient.java:323) at sun.net.www.protocol.http.HttpURLConnection.getNewHttpClient(HttpURLC onnection.java:852) at sun.net.www.protocol.http.HttpURLConnection.plainConnect(HttpURLConne ction.java:793) at sun.net.www.protocol.http.HttpURLConnection.connect(HttpURLConnection .java:718) at org.codehaus.mojo.tomcat.TomcatManager.invoke(TomcatManager.java:597) at org.codehaus.mojo.tomcat.TomcatManager.deployImpl(TomcatManager.java: 662) at org.codehaus.mojo.tomcat.TomcatManager.deploy(TomcatManager.java:245) at org.codehaus.mojo.tomcat.AbstractDeployMojo.deployWar(AbstractDeployM ojo.java:175) at org.codehaus.mojo.tomcat.AbstractDeployMojo.invokeManager(AbstractDep loyMojo.java:85) at org.codehaus.mojo.tomcat.AbstractCatalinaMojo.execute(AbstractCatalin aMojo.java:141) ... 19 more [INFO] [INFO] Total time: 5 seconds [INFO] Finished at: Mon Mar 30 17:43:51 CEST 2009 [INFO] Final Memory: 5M/10M [INFO] Anybody can give me a hint about what I am doing wrong, please? I installed tomcat-maven-plugin and tomcat manager plugin for eclipse. My project builds ok after mvn package but when I try to deploy to tomcat server with mvn -e tomcat:exploded it throws org.apache.maven.lifecycle.LifecycleExecutionException: Cannot invoke Tomcat man ager. From the trace I can't find out what I am doing wrong. As far as I am concerned I haven't changed the default settings and my
Re: Config File Consistency
Hi Perry, Typically, I have used the configuration options of the tool, such as specifying the config file via a URL with Checkstyle. I have also bundled them together a separate project, deployed that jar, and made it a dependency of the projects. This works when the respective tool can can load the config file via the classpath. HTH On Mon, 30 Mar 2009 10:55:09 -0400 dutchman...@charter.net wrote: Hello all: I am working in a Maven multi-project environment and I would like to maintain some consistency across projects for some tools like CheckStyle, FindBugs, etc. In order to do this, I am thinking of using the remote resource plugin. However, the documentation states that the files from the resource bundle is deposited in the $basedir/target/classes directory. However, I would like it deposited in the $basedir/some_arbitrary_location directory? Can I configure the directory where the files are deposited or am I off in the weeds and there is an easier way? Thank you, Perry Hoekstra - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
maven repository version
Hello all, I have a hunch the answer to this is going to be use a repository manager but thought I would ask. I have built up 3 internal maven repositories that we point at via settings in our settings.xml. I would like to be able to version 2 of them. Essentially what I am thinking of is writing a file to the root of each repository that has a tag in it so I can tie a version of my maven repositories to a version of a component that I built. My reason for doing this is why use ranges in a number of places, I don't want a build to suddenly get the wrong version of a component based on the ranges. Has anyone tried this sort of thing without a repository manager? -Jim - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Grandparent classes not found at compile time
But if I must do manual dependency analysis every time I update a third party jar -- just in case it now incurs a new dependency for me -- then what value are transitive dependencies in Maven at all? You are expected to know what Jars your project (specifically) depends on. I've followed this thread and still don't understand why you don't know this. If artifacts you depend on have dependencies themselves (which is what should happen when one class extends another), they should be declared in the pom files of those projects. If those artifacts do not properly declare the scope of all of their dependencies, such that a needed class is not being found during compilation/testing/runtime, then you need to talk to the owner of the bad artifact. If those artifacts do not have pom files at all (you're using mvn install:install-file or deploy:deploy-file on them), then that is another issue. Maven's (transitive) dependency management works extremely well for a lot of people. I still don't know why you're having such troubles with it, and I can only blame the artifacts you're working with and not the system itself at this point. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven Release release:prepare / perform etc.
Hi there, i have a project which is building etc. with mvn clean package etc. Now i would like to do a mvn release:prepare answering questins: like release Version 1.0.0 and the tag name etc. but it's comming up that during the release:prepare cycle Maven want to download artifact like xyz-1.0.0.pom from a repository but that can't be cause that artifact is exactly what is currently buildin Version 1.0.0 ? So can someone give me hint what I'm doing wrong ? Or do i understand something wrong ? Kind regards Karl Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven Release release:prepare / perform etc.
Hey Karl, This issue has been coming up quite a bit, lately. Some will disagree with me, but here is my solution to this problem. mvn release:prepare -DpreparationGoals=clean install The release:prepare normally only does a packaging, so the install step never happens. It really should find the artifact in the reactor, but it doesn't. So, you have to install it. Good luck, Dave Karl Heinz Marbaise wrote: Hi there, i have a project which is building etc. with mvn clean package etc. Now i would like to do a mvn release:prepare answering questins: like release Version 1.0.0 and the tag name etc. but it's comming up that during the release:prepare cycle Maven want to download artifact like xyz-1.0.0.pom from a repository but that can't be cause that artifact is exactly what is currently buildin Version 1.0.0 ? So can someone give me hint what I'm doing wrong ? Or do i understand something wrong ? Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Config File Consistency
Jeff: If it was a single file (ie. CheckStyle) I would have most likely gone down the URL route. However, I have multiple configuration files (CheckStyle, PMD, FindBugs, testing, etc) so I would like it all as single dependency. If I go down the *.jar route, it works for CheckStyle but does not seem to work for other plug-ins. That is why I was looking for a solution that would allow a *.jar file to be pulled from a repository and explode to a defined directory. All of the plug-ins have an option to point to a given directory for configuration files. I can do it through the Ant plug-in (unzip) but I was trying to find a pure Maven solution first. Perry Hoekstra Jeff Jensen jeffjen...@upstairstechnology.com wrote: Hi Perry, Typically, I have used the configuration options of the tool, such as specifying the config file via a URL with Checkstyle. I have also bundled them together a separate project, deployed that jar, and made it a dependency of the projects. This works when the respective tool can can load the config file via the classpath. HTH On Mon, 30 Mar 2009 10:55:09 -0400 dutchman...@charter.net wrote: Hello all: I am working in a Maven multi-project environment and I would like to maintain some consistency across projects for some tools like CheckStyle, FindBugs, etc. In order to do this, I am thinking of using the remote resource plugin. However, the documentation states that the files from the resource bundle is deposited in the $basedir/target/classes directory. However, I would like it deposited in the $basedir/some_arbitrary_location directory? Can I configure the directory where the files are deposited or am I off in the weeds and there is an easier way? Thank you, Perry Hoekstra - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Compiling a specific module with the dependencies
Hello,
I have a project with 2 jars maestro-ee - maestro-core.
I'm trying to setup the continuous integration with cruisecontrol, but I'm
having some problems.
Is it possible when a compile the project maestro-ee automatically compile the
project maestro-core?
I'm not interested in always run a mvn install:install-file And I
wouldn't like compile all projects in the parent POM.
_ _ _
I have a parent Project with all modules:
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdnet.weg.eng/groupId
artifactIdmaestro-project/artifactId
packagingpom/packaging
version0.2/version
urlhttp://maven.apache.org/url
...
modules
modulemaestro-core/module
modulemaestro-ee/module
...
/modules
...
And the dependencies specified in each modules, for example:
project xmlns=http://maven.apache.org/POM/4.0.0;
xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation=http://maven.apache.org/POM/4.0.0
http://maven.apache.org/maven-v4_0_0.xsd;
modelVersion4.0.0/modelVersion
groupIdnet.weg.eng/groupId
artifactIdmaestro-ee/artifactId
packagingjar/packaging
version0.2/version
namemaestro-ee/name
urlhttp://maven.apache.org/url
parent
groupIdnet.weg.eng/groupId
artifactIdmaestro-project/artifactId
version0.2/version
relativePath../pom.xml/relativePath
/parent
...
dependency
groupId${project.groupId}/groupId
artifactIdmaestro-core/artifactId
version${project.version}/version
scopecompile/scope
/dependency
Thanks a lot,
Cleiton Garcia.
Depto. de Sistemas de Informação
Fone (0xx47)3276-6917 / 3276-7829 Fax (0xx47) 3276-4010
-
To unsubscribe, e-mail: users-unsubscr...@maven.apache.org
For additional commands, e-mail: users-h...@maven.apache.org
Re: How to bulk load the jars in my local repo into a new (empty) corporate remote repo?
Thank you for your replies. I am writing a script to do it, at the suggestion of another poster. Thank you one and all! -jeff On Sun, Mar 29, 2009 at 3:45 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: The danger with that is that the metadata (local vs remote) will be incorrect and version ranges will not work correctly 2009/3/29 Tim che...@gmail.com Are you on a linux system? I just rsynced my repo recently to accomplish the same thing. It was really easy. On Sat, Mar 28, 2009 at 12:05 PM, Jeff Walker webservices.archit...@gmail.com wrote: Hi, I'm a relative newbie to Maven2. My problem is, I have a local repository full of about 400 jars. All is well and good, my projects build and I am happy. My happiness level is now in jeopardy! Another team has created a remote repository in our domain. I have to switch to use it. I located it and updated my pom files. Great, just one problem, it's of course empty! How do I bulk load the jars in my local repo into this new remote repo, without doing the mvn:deploy:deploy-file thing for each jar (400 times). I can get no help from the person who created the remote repo. (Company politics, you understand). Thanks, -jeff -- P. J. O'Rourke - If government were a product, selling it would be illegal.
Re: Maven Release release:prepare / perform etc.
Hi David, first thanks for your fast answer... Hey Karl, This issue has been coming up quite a bit, lately. Hm...my english seemed to be no good enough to understand this... Some will disagree with me, but here is my solution to this problem. mvn release:prepare -DpreparationGoals=clean install The release:prepare normally only does a packaging, so the install step never happens. It really should find the artifact in the reactor, but it doesn't. So, you have to install it. Good luck, Dave Karl Heinz Marbaise wrote: Hi there, i have a project which is building etc. with mvn clean package etc. Now i would like to do a mvn release:prepare answering questins: like release Version 1.0.0 and the tag name etc. but it's comming up that during the release:prepare cycle Maven want to download artifact like xyz-1.0.0.pom from a repository but that can't be cause that artifact is exactly what is currently buildin Version 1.0.0 ? So can someone give me hint what I'm doing wrong ? Or do i understand something wrong ? Kind regards Karl Heinz Marbaise - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven Release release:prepare / perform etc.
Hi David, sorry.. a second one... mvn release:prepare -DpreparationGoals=clean install In my opinion this couldn't work, cause the goal clean tries to download things from local repository (like xy-1.0.0.pom) which will be created by the process so the only goal in this case could be install ... Kind regards Karl Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: swap between snapshot- and release versions in a large system
versions-maven-plugin some of the mojo's we're (or I'm) intending on putting in are not there yet. The first mojo to look at is: update-properties (you'd be wanting the version from 1.0-alpha-3-SNAPSHOT btw) This picks up any dependencies who's version comes from a property and allows picking the newest version available and using that. Two other goals which I'm planning are use-releases (will scan your project for any dependencies which are -SNAPSHOT and have the corresponding release version available) use-snapshots (will scan your project for any dependencies which have a newer -SNAPSHOT available and use that) note that use-releases is safer than use-snapshots as removing the -SNAPSHOT is unambiguous, but adding a -SNAPSHOT is more difficult... 1.0.3 = 1.0.4-SNAPSHOT, or 1.1.0-SNAPSHOT, or 2.0.0-SNAPSHOT what one should we look for, and when should we use it 2009/3/30 torsten.reinh...@gi-de.com Hi, we have a large system, containing separate software modules (backend.ear, ui.war, services.war and so on) During developement, we use snapshot dependencies to reference the other modules. So a version of the whole system can be build by one click on our buildsystem, which than just deploys a new snapshot version and all is fine. During release (one times a week) we need first to release the modules one by one - actually per hand, swap dependency versions and so on, than swap dependency versions back to next snapshot for the develeopement of next week and so on. This is very error-prone and time consuming. What´s the way to do this more efficient? Always build the whole system as one multimodule build? Is there a plugin that automatically can change dependency versions in pom.xml if there are newer versions available? Thanx, torsten
Re: Maven Release release:prepare / perform etc.
I am going to bet that you might be using the dependency:copy or the dependency:unpack goals and not dependency:copy-dependencies If you are picking something up from the reactor you need to use goals that look in the reactor 2009/3/30 Karl Heinz Marbaise khmarba...@gmx.de Hi David, sorry.. a second one... mvn release:prepare -DpreparationGoals=clean install In my opinion this couldn't work, cause the goal clean tries to download things from local repository (like xy-1.0.0.pom) which will be created by the process so the only goal in this case could be install ... Kind regards Karl Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven Release release:prepare / perform etc.
Hi, Hi David, sorry.. a second one... mvn release:prepare -DpreparationGoals=clean install In my opinion this couldn't work, cause the goal clean tries to download things from local repository (like xy-1.0.0.pom) which will be created by the process so the only goal in this case could be install ... If i had written -DpreparationGoals correct than it had worked... Thanks for your help Kind regards Karl Heinz Marbaise -- SoftwareEntwicklung Beratung SchulungTel.: +49 (0) 2405 / 415 893 Dipl.Ing.(FH) Karl Heinz MarbaiseICQ#: 135949029 Hauptstrasse 177 USt.IdNr: DE191347579 52146 Würselen http://www.soebes.de - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: maven repository version
any advantages to manually track file versions (instead of using version control to manage the process) ? Martin __ Disclaimer and confidentiality note This message is confidential and may be privileged. If you are not the intended recipient, we kindly ask you to please inform the sender. Any unauthorised dissemination or copying hereof is prohibited. This message serves for information purposes only and shall not have any legally binding effect. Given that e-mails can easily be subject to manipulation, we can not accept any liability for the content provided. From: jim.mccas...@pervasive.com To: users@maven.apache.org Date: Mon, 30 Mar 2009 11:38:48 -0500 Subject: maven repository version Hello all, I have a hunch the answer to this is going to be use a repository manager but thought I would ask. I have built up 3 internal maven repositories that we point at via settings in our settings.xml. I would like to be able to version 2 of them. Essentially what I am thinking of is writing a file to the root of each repository that has a tag in it so I can tie a version of my maven repositories to a version of a component that I built. My reason for doing this is why use ranges in a number of places, I don't want a build to suddenly get the wrong version of a component based on the ranges. Has anyone tried this sort of thing without a repository manager? -Jim - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org _ Hotmail® is up to 70% faster. Now good news travels really fast. http://windowslive.com/online/hotmail?ocid=TXT_TAGLM_WL_HM_70faster_032009
Senior Release Engineer Opportunity in Boston
Seek individual with strong skills in Subversion, Maven, J2EE, Weblogic, Builds Releases for Release Engineer position with an established and growing software service company. Responsibilities: • Build various versions of the application (Maven) and deploy to development environments • Maintain the source code and related content in Subversion • Maintain and enhance build scripts • Plan and automate the release process • Provide support to the development team for Configuration Management and Build issues • Ability to learn new tools as well as think and lead independently Qualifications: • 7+ years experience with build and release engineering with at least 3 years in Java/J2EE • Worked in a web based J2EE environment • Excellent knowledge of Java/J2EE • Good knowledge of BEA Weblogic • Good grasp of a scripting language like Perl • Good understanding of Solaris/Unix and Windows OS • Knowledge of Continuum, Jira and Ant a big plus • Knowledge of Oracle/SQL Server/MYSQL a plus • Prior experience developing Java/J2EE applications a plus Please send a Word resume when you contact me! No work authorization (visa) support can be provided. Thanks, Durga Kotikalapudi Recruiter, CMI durga.kotikalap...@cmi.com -- View this message in context: http://www.nabble.com/Senior-Release-Engineer-Opportunity-in-Boston-tp22790247p22790247.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Variable substitution question...
You need to configure filtering for the file you want filtered.
Have a look at the war plugin for how to define which files get filtered
2009/3/30 James Depaul jjdep...@us.ibm.com
I've searched the archives for this but no luck -
I need to build my web.xml file with specific values based on the target
environment for which I'm performing the build. Therefore, I'd like maven
to perform some variable substitution when I run the mvn install goal. I'm
trying to use profiles for this (though I obviously lack solid
understanding of profiles at this point). Here is what I did:
I've setup 3 profiles in the parent pom.xml file like this:
profiles
profile
iddev/id
activation
activeByDefaulttrue/activeByDefault
/activation
properties
app.context.parmdev_values.../app.context.parm
/properties
/profile
profile
idqa/id
properties
app.context.parmqa_values.../app.context.parm
/properties
/profile
profile
idprod/id
properties
app.context.parmprod_values.../app.context.parm
/properties
/profile
/profiles
In my web.xml file I currently have something like this:
context-param
param-namecontextConfigLocation/param-name
param-value${app.context.parm}/param-value -- need the
variable substitution HERE...
/context-param
I then run mvn -Pqa install goal, hoping that maven will insert the proper
application context values into this placeholder based on the profile
that's active, but so far this does not work for me... please tell me
what else I'm missing to make this work.
Thanks,
James
Re: How to perform a deploy only
Stefan, The problem is that the deploy:deploy will be running in a separate reactor and will be missing any attached artifacts from the reactor build. So actually what you propose will completely fail for more than a non-trivial build -Stephen 2009/3/30 Stefan Seidel ssei...@vub.de I still don't think your solution is easier than mvn install if not errorlevel 1 mvn deploy:deploy But - everyone has their own solutions ;) Thanks for sharing. Stefan On Fri, 27 Mar 2009 13:17:43 -0500 Jim McCaskey jim.mccas...@pervasive.com wrote: Hi Stephen, Sure no problem. What I came up with was another set of posts, and was essentially following the advice you gave me a few days ago and some help from Dan Tran. That is, I use mvn deploy but output to a empty directory, then use a maven plugin to merge that to my primary repository. Here are some details (note I am using Maven 2.1.0 on Windows machines). So essentially I build like this: mvn -DaltDeploymentRepository=repo::default::file://E:\staging-repo deploy I then use the wagon-maven-plugin to merge this sparse area up to my corporate repository like this: mvn org.codehaus.mojo:wagon-maven-plugin:1.0-beta-1:merge-maven-repos -Dwagon.source=file://E:\staging-repo -Dwagon.target=file://\\server\share\mavenrepo -Djava.io.tmpdir=deploytemp Note that deploytemp is a directory that is created in the local directory. I can't seem to point it to a C:\temp for some reason, and really don't care. I just create the directory and use it. It's empty when it gets done. If you don't create that directory (or forget the java.io.tmpdir), you get a rather cryptic message about volume labels. I'm able to chain these two commands together after appropriate error checking in my automation server (IBM Rational Build Forge FWIW). So what I was after originally was a step for me to build, then another step to deploy only that I could use later on after everything was done. This accomplishes that goal, with a little help from the wagon-maven-plugin, and Dan Tran. Needless to say this methodology was not documented anywhere that I could find, so I am guessing that not many folks are interested in it. Frankly without the nudges in the right direction from this list, I would not have been able to figure it out. So thanks to everyone. -Jim -Original Message- From: Stephen Connolly [mailto:stephen.alan.conno...@gmail.com] Sent: Friday, March 27, 2009 12:45 PM To: Maven Users List Subject: Re: How to perform a deploy only Any chance you could post your solution? 2009/3/27 Jim McCaskey jim.mccas...@pervasive.com I have found a solution that is working nicely. Having said that, I don't think the request is that farfetched. When doing a deploy, you would definitely want to make sure that all the components that made up the run built successfully before deploying. Not doing so leaves your repository in a corrupt state. Perhaps having the ability to delay the deploy phase until all components are built/tested is what is needed, not necessarily a Deploy only ability. In other words, run all other phases for all components, then swing back through on a deploy run once all components are verified to build/test. My guess would be that as more and more projects use Maven to glue everything together, these sorts of things will come up more often. Anyway just a suggestion. Like I say, I have a solution that I'm happy with. -Jim -Original Message- From: Brian E. Fox [mailto:bri...@reply.infinity.nu] Sent: Thursday, March 26, 2009 9:43 PM To: Maven Users List Subject: RE: How to perform a deploy only Running the full lifecycle is a fundamental of Maven, so this type of feature request is unlikely to gain traction. You should rather look at your build configuration to solve the problem, or as mentioned use a repo man that can help you out. -Original Message- From: Jim McCaskey [mailto:jim.mccas...@pervasive.com] Sent: Wednesday, March 25, 2009 11:26 PM To: 'Maven Users List' Subject: RE: How to perform a deploy only Thanks for the suggestion. I have been trying to avoid using repository managers for a number of reasons that are beyond the scope of this thread. I may have to break down eventually... I'm surprised no one has needed this sort of feature, or maybe they have and that's why Nexus has the features that it does. I was hoping to find a Maven native (whatever native means in a highly pluggable architecture) way to do this that would not take much additional work. mvn -DdoNothingButDeploy=true deploy That would be about perfect. :) Would this even be consider for an enhancement request if I opened it? Perhaps I am the only one interested in such a thing. Thanks! -Jim -Original
Re: Senior Release Engineer Opportunity in Boston
What is the salary/rate? bob.aie...@ieee.org - http://www.linkedin.com/in/BobAiello - Sent via BlackBerry -Original Message- From: durgaK durga.kotikalap...@cmi.com Date: Mon, 30 Mar 2009 11:49:04 To: users@maven.apache.org Subject: Senior Release Engineer Opportunity in Boston Seek individual with strong skills in Subversion, Maven, J2EE, Weblogic, Builds Releases for Release Engineer position with an established and growing software service company. Responsibilities: • Build various versions of the application (Maven) and deploy to development environments • Maintain the source code and related content in Subversion • Maintain and enhance build scripts • Plan and automate the release process • Provide support to the development team for Configuration Management and Build issues • Ability to learn new tools as well as think and lead independently Qualifications: • 7+ years experience with build and release engineering with at least 3 years in Java/J2EE • Worked in a web based J2EE environment • Excellent knowledge of Java/J2EE • Good knowledge of BEA Weblogic • Good grasp of a scripting language like Perl • Good understanding of Solaris/Unix and Windows OS • Knowledge of Continuum, Jira and Ant a big plus • Knowledge of Oracle/SQL Server/MYSQL a plus • Prior experience developing Java/J2EE applications a plus Please send a Word resume when you contact me! No work authorization (visa) support can be provided. Thanks, Durga Kotikalapudi Recruiter, CMI durga.kotikalap...@cmi.com -- View this message in context: http://www.nabble.com/Senior-Release-Engineer-Opportunity-in-Boston-tp22790247p22790247.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Senior Release Engineer Opportunity in Boston
On Mon, Mar 30, 2009 at 1:49 PM, durgaK durga.kotikalap...@cmi.com wrote: Seek individual with... Please use j...@apache.org for job postings... you can find more info here: http://www.apachenews.org/archives/000465.html Thanks, -- Wendy - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Invalid or missing parameter add-source
I'm using maven eclipse plugin. During build, I see the following in the maven console: 3/30/09 1:28:49 PM PDT: Build errors for ProjectName; org.apache.maven.lifecycle.LifecycleExecutionException: Invalid or missing parameters: [Mojo parameter [name: 'sources'; alias: 'null']] for mojo: org.codehaus.mojo:build-helper-maven-plugin:1.1:add-source I think this is the pertinent config in my pom.xml: plugin groupIdorg.codehaus.mojo/groupId artifactIdbuild-helper-maven-plugin/artifactId executions execution idadd-source/id phasegenerate-sources/phase goals goaladd-source/goal /goals configuration sources sourcesrc/main/repoClient/source sourcesrc/main/repoImpl/source sourcesrc/main/repoModel/source sourcesrc/main/repoServer/source sourcesrc/main/user/source sourcesrc/main/aspect/source /sources /configuration /execution /executions /plugin -- View this message in context: http://www.nabble.com/Invalid-or-missing-parameter-add-source-tp22792469p22792469.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
[ANN] findbugs-maven-plugin v 2.0 release
The Maven Findbugs team would like to announce the release of the Maven Findbugs Plugin version 2.0 This plugin allows the developer to run Findbugs analysis against a Maven project and produce site output in HTML to match other site reports. There are options to produce other XML outputs which are used by other plugins. Issues fixed in this release: http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truefixfor=14335pid=11701status=6sorter/field=issuekeysorter/order=DESCsorter/field=issuetypesorter/order=DESC More information can be found at the plugin site: http://mojo.codehaus.org/findbugs-maven-plugin/ Issues Can be registered in JIRA at: http://jira.codehaus.org/browse/MFINDBUGS More information on FindBugs http://findbugs.sourceforge.net/index.html You can test the Maven Findbugs Plugin in your own project by adding the following dependency: dependency groupIdorg.codehaus.mojo/groupId artifactIdfindbugs-maven-plugin/artifactId version2.0/version /dependency *NOTE* Version 2.0 and greater of the Maven Findbugs plugin will require Maven to be run with a minimum of Java 5. This is consistent with Findbugs requirement for their versions of 1.3.X and greater. -- Enjoy, Garvin LeClaire garvin.lecla...@gmail.com
Re: Grandparent classes not found at compile time
My point is about transitive support for provided dependencies. The middle artifact here does declare a dependency to the third-party jar. But its declared as *provided*, not *compile*. Now I understand the intent of provided. It's to say I expect this to be provided in the runtime environment, so don't package it into anything -- but since you're compiling outside of said runtime environment, include it for compile purposes. Is this correct? On the other hand, a *compile* dependency is something you need tom compile against and include in any subsequent packaging, true? So then a project's own dependencies... *compile* Used at compile: TRUE Used in package: TRUE *provided* Used at compile: TRUE Used in package: FALSE So compiling against a direct provided dependency works fine. But if I put a layer in there, it breaks down according to Maven's own rules: transitive *compile* Used at compile: TRUE Used in package: TRUE transitive *provided* Used at compile: FALSE Used in package: FALSE A transitive *provided* dependency is not included at runtime. But I'm still in a compile phase, trying to compile against the same jars all of my dependencies had available to them when they compiled. I can certainly see times when you wouldn't want this, but in the case of a class hierarchy, you must have them. So my option is to go into the middle artifact's pom and change the dependency to the third party from *provided* to *compile* or explicitly include the third party *provided* jar directly form my application's pom (which mean's I'm duplicating information already in the middle component's pom). For the time being, I'm doing the latter, but it doesn't feel right. I feel like there's a certain degree of freedom missing here where I want something to NOT be packaged because it'll be included but still make it a compile time dependency since I'm not in the container at runtime. I have that for direct dependencies but not transitive dependencies. Regards, Brian. Wayne Fay wrote: But if I must do manual dependency analysis every time I update a third party jar -- just in case it now incurs a new dependency for me -- then what value are transitive dependencies in Maven at all? You are expected to know what Jars your project (specifically) depends on. I've followed this thread and still don't understand why you don't know this. If artifacts you depend on have dependencies themselves (which is what should happen when one class extends another), they should be declared in the pom files of those projects. If those artifacts do not properly declare the scope of all of their dependencies, such that a needed class is not being found during compilation/testing/runtime, then you need to talk to the owner of the bad artifact. If those artifacts do not have pom files at all (you're using mvn install:install-file or deploy:deploy-file on them), then that is another issue. Maven's (transitive) dependency management works extremely well for a lot of people. I still don't know why you're having such troubles with it, and I can only blame the artifacts you're working with and not the system itself at this point. Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://www.nabble.com/Grandparent-classes-not-found-at-compile-time-tp22733894p22795415.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
The skin does not exist: Unable to determine the release version
Sorry if I missed this as a recent posting. Last night, several of my Maven projects running in Hudson starting to fail with the same error message. Does the recent site plug-in release have anything to do with this? It's becoming problematic to delete files in a repo and have maven auto-download them, which seems to fix this problem. Thanks. [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] The skin does not exist: Unable to determine the release version Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.maven.skins -DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.maven.skins -DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.apache.maven.skins:maven-default-skin:jar:RELEASE The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail.
RE: The skin does not exist: Unable to determine the release version
version is indeterminant what happens if you follow instructions to d/l the requested skin and install with known group-id,version and artifact-id ? Martin __ Disclaimer and confidentiality note This message is confidential and may be privileged. If you are not the intended recipient, we kindly ask you to please inform the sender. Any unauthorised dissemination or copying hereof is prohibited. This message serves for information purposes only and shall not have any legally binding effect. Given that e-mails can easily be subject to manipulation, we can not accept any liability for the content provided. To: users@maven.apache.org Subject: The skin does not exist: Unable to determine the release version From: jerry.th...@hewitt.com Date: Mon, 30 Mar 2009 20:27:05 -0500 Sorry if I missed this as a recent posting. Last night, several of my Maven projects running in Hudson starting to fail with the same error message. Does the recent site plug-in release have anything to do with this? It's becoming problematic to delete files in a repo and have maven auto-download them, which seems to fix this problem. Thanks. [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] The skin does not exist: Unable to determine the release version Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=org.apache.maven.skins -DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=org.apache.maven.skins -DartifactId=maven-default-skin -Dversion=RELEASE -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] org.apache.maven.skins:maven-default-skin:jar:RELEASE The information contained in this e-mail and any accompanying documents may contain information that is confidential or otherwise protected from disclosure. If you are not the intended recipient of this message, or if this message has been addressed to you in error, please immediately alert the sender by reply e-mail and then delete this message, including any attachments. Any dissemination, distribution or other use of the contents of this message by anyone other than the intended recipient is strictly prohibited. All messages sent to and from this e-mail address may be monitored as permitted by applicable law and regulations to ensure compliance with our internal policies and to protect our business. E-mails are not secure and cannot be guaranteed to be error free as they can be intercepted, amended, lost or destroyed, or contain viruses. You are deemed to have accepted these risks if you communicate with us by e-mail. _ Express your personality in color! Preview and select themes for Hotmail®. http://www.windowslive-hotmail.com/LearnMore/personalize.aspx?ocid=TXT_MSGTX_WL_HM_express_032009#colortheme
The plugin 'org.apache.maven.plugins:maven-aar-plugin' does not exist
Hi. I cannot get the service archiver plugin to work (AAR). mvn aar:aar gives this result: [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'aar'. [INFO] [ERROR] BUILD ERROR [INFO] [INFO] The plugin 'org.apache.maven.plugins:maven-aar-plugin' does not exist or no valid version could be found and with mvn -U aar:aar it says it is checking for updates from central but fails also. I've tried mvn org.aparche.axis2-aar-maven-plugin:aar as well but with same result. When I tried changing the version number in the pom.xml file and tried the command again it seemed to start downloading but failed again. Any suggestions as to what is wrong? -Az. _ Dobbelt så moro – del bilder med andre mens du chatter på Windows Live Messenger. http://www.microsoft.com/windows/windowslive/products/messenger.aspx
Duplicate Module/Project Names in m2eclipse
Hi, Eclipse can't seem to handle two modules in the same workspace that have the same artifactId. For example if I have a multi-module project (groupId:artifact) as below: - carworld:carworld - carworld:ferrari - carworld.ferrari:car - carworld:porsche - carworld.porsche:car There are two modules that have artifactIdcar/artifactId (but different groupId's). m2Eclipse+Eclipse appears to use the artifactId as the project identifier and when the two car projects are imported only one is actually imported. Is this a known issue? are there any workarounds? Cheers.
Re: Repository 'central' will be blacklisted
Hi, I can able to access http://repo1.maven.org/ from the browser and I have made changes in the proxy settings like this: !-- proxies | This is a list of proxies which can be used on this machine to connect to the network. | Unless otherwise specified (by system property or command-line switch), the first proxy | specification in this list marked as active will be used. |-- proxies !-- proxy | Specification for one proxy, to be used in connecting to the network. | proxy idoptional/id activetrue/active protocolhttp/protocol usernameproxyuser/username passwordproxypass/password hostproxy.mycompany.com/host port6050/port nonProxyHostswww.google.com|*.somewhere.com/nonProxyHosts /proxy -- /proxies I am not having any local repository. I am very new to Maven, please provide the step by step procedure to resolve the issue (If possible with the screen shots). Is it necessary to have a repository? This is my Maven folder structure : http://www.nabble.com/file/p22798782/untitled.jpeg Thanks in advance, === brettporter wrote: It was in my email: repo1.maven.org. You can configure alternatives from the mirror list on the site. - Brett On 23/03/2009, at 5:05 PM, NR031 wrote: Hi, In my company some of the sites are blocked, is it the problem which is causing the issue? If yes can you please send me the URL for which the Maven is trying to connect, so that I can check the same by connecting directly. Thanks in advance, = = = = = = = = = == brettporter wrote: Note the connection refused message - please check the installation instructions to make sure you've set up your proxy server, etc. You'll need access to repo1.maven.org. - Brett On 23/03/2009, at 4:48 PM, NR031 wrote: Hi, I just installed Maven Apache 2.1.0 from http://www.ecoficial.com/apachemirror/maven/binaries/apache-maven-2.1.0-bin.zip http://www.ecoficial.com/apachemirror/maven/binaries/apache-maven-2.1.0-bin.zip . Then I used the command mvn archetype:create - DgroupId=com.mycompany.app -DartifactId=my-app, but I am getting the following error : http://www.nabble.com/file/p22654645/1.jpg I am new to Maven, please provide the step by step procedure to resolve the issue. Is there anything to do apart from the normal settings? Thanks in advance, -- View this message in context: http://www.nabble.com/Repository-%27central%27-will-be-blacklisted-tp22654645p22654645.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Brett Porter br...@apache.org http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://www.nabble.com/Repository-%27central%27-will-be-blacklisted-tp22654645p22654729.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Brett Porter br...@apache.org http://blogs.exist.com/bporter/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://www.nabble.com/Repository-%27central%27-will-be-blacklisted-tp22654645p22798782.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
