Re: M2Eclipse Plugin Seems can't resolve workspace dependency during build
Maven2 was unable to find http://repo1.maven.org/maven2/com/ocpsoft/ocpsoft-base/1.0.0/ocpsoft-base-1.0.0.pom In short, your artifact with : groupId com.ocpsoft artifactId ocpsoft-base version 1.0.0 doesn't exist in maven's public repository (if you try accessing the URL in the error message, you'll get 404 errors. BUT, you can download the jar file manually from here : http://prettyfaces.googlecode.com/files/ocpsoft-pretty-faces-1.0.0.jar save it on your disk, then install it manually by running : mvn install:install-file -DgroupId=com.ocpsoft -DartifactId=ocpsoft-base -Dversion=1.0.0 -Dpackaging=jar -Dfile=/path/to/file Should now compile. Hope this helps. Yves 2009/2/7 Lincoln Baxter, III lincolnbax...@gmail.com: Hi All, I am trying to run a build without installing my workspace dependencies into the local repository, however, I get this exception, and the build fails: How can I fix this? All projects required are in my workspace. I'm using Eclipse 3.4. Thanks, Lincoln [INFO] Scanning for projects... [INFO] [INFO] Building Hibernate Data Base Package [INFO] [INFO] Id: com.ocpsoft:ocpsoft-data:jar:1.0.0 [INFO] task-segment: [package] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. url = http://repo1.maven.org/maven2 Downloading: http://repo1.maven.org/maven2/com/ocpsoft/ocpsoft-base/1.0.0/ocpsoft-base-1.0.0.pom url = http://repo1.maven.org/maven2 Downloading: http://repo1.maven.org/maven2/com/ocpsoft/ocpsoft-base/1.0.0/ocpsoft-base-1.0.0.pom url = http://repo1.maven.org/maven2 Downloading: http://repo1.maven.org/maven2/com/ocpsoft/ocpsoft-base/1.0.0/ocpsoft-base-1.0.0.jar [ERROR] Transitive dependency resolution for scope: compile has failed for your project. Error message: Missing: -- 1) com.ocpsoft:ocpsoft-base:jar:1.0.0 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=com.ocpsoft -DartifactId=ocpsoft-base -Dversion=1.0.0 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.ocpsoft -DartifactId=ocpsoft-base -Dversion=1.0.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) com.ocpsoft:ocpsoft-data:jar:1.0.0 2) com.ocpsoft:ocpsoft-base:jar:1.0.0 -- 1 required artifact is missing. for artifact: com.ocpsoft:ocpsoft-data:jar:1.0.0 from the specified remote repositories: central (http://repo1.maven.org/maven2) Group-Id: com.ocpsoft Artifact-Id: ocpsoft-data Version: 1.0.0 From file: /gentoo/home/lb3/Projects/ocpsoft-data/pom.xml [INFO] [INFO] For more information, run with the -e flag [INFO] [INFO] BUILD FAILED [INFO] [INFO] Total time: 2 seconds [INFO] Finished at: Sat Feb 07 16:48:04 EST 2009 [INFO] Final Memory: 5M/80M [INFO] - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [ANN] - SCM Changelog Maven Plugin 1.1 Released
Congrats, keep up the good work! Thanks Stevo. We hope that our plugin One new feature suggestion - support for filtering subtasks (at least when jira is issue tracker), e.g. through optional excludeSubtasks attribute of filter configuration element. Are you sure that it is for our plugin and not for the maven-changes-plugin. In fact, with our plugin, you just have to not add the subtasks id in the SCM comment. Regards, Rémy
Running ALL tests and fail at the END
In my Maven project I have several modules which all have tests. If I run the tests and one module fails, then the execution is cancelled. But I want that the tests of ALL modules are executed and then at the end I want a notification that some tests have failed. I have tried it with setting the testFailureIgnore option on my pom.xml: configuration testFailureIgnoretrue/testFailureIgnore /configuration But in this case mvn test will return successfully: [...] [INFO] [INFO] [INFO] Reactor Summary: [INFO] [INFO] Module A .. SUCCESS [4.520s] [INFO] Module B ... SUCCESS [4:06.863s] [INFO] Module C . SUCCESS [14.553s] [INFO] Module D . SUCCESS [10.785s] [INFO] [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 4 minutes 28 seconds [INFO] Finished at: Tue Feb 10 09:15:56 CET 2009 [INFO] Final Memory: 36M/69M [INFO] All module tests return success even though for example Module B failed. (without setting testFailureIgnore option only tests of Module B are executed) Is there any other option to achieve that all tests are executed with a fail notification at the end? (I have also played around with 'maven.test.haltafterfailure' but it seemed not to have any effect) Thanks for any help! -- View this message in context: http://www.nabble.com/Running-ALL-tests-and-fail-at-the-END-tp21930359p21930359.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: How to manage your artifact versions
On Mon, Feb 9, 2009 at 5:46 PM, Avihaimar avihai...@yahoo.com wrote: Hey, My application is composite from a lot of artifacts. If i set my artifact version to be snapshot than each time a developer will build the ear on his machine maven will download a newer version from the remote repository and not use the developer version. Well, sounds like you need some background info here. The purpose of SNAPSHOT is to give you latest development version of an artifact. Ideally (IMO), SNAPSHOTs should be deployed by a developer when (s)he considers that it reaches some state (feature partly implemented or stable, etc). If you have a CI system that deploys every 2 hours it defeats this principle. However, you can configure your settings to look for snapshot only when your copy is 1 hour, 4 hours, 1 day old, etc. When you say that it does not use the developer version, it simply means that the version on the repository is newer than the one from the developer. If you decide to use SNAPSHOT, it is normal that you get the latest one. You can have some fallback strategies though. For instance, we have two snapshot repositories. The first one is stable development snapshot and contains only artifacts deployed by a team member. The second one is updated automatically at every CI build. That way, if an artifact was never deployed for a given version, we can just activate a profile and fetch it from the second repository. HTH, Stéphane So, i dont understand the benefit of snapshot. From the other side if i have 20 artifacts , which develop by differnet teams there is no reason to me to compile the artifacts that i didnt touch them. Advices will be welcome -- View this message in context: http://www.nabble.com/How-to-manage-your-artifact-versions-tp21916752p21916752.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 -- Large Systems Suck: This rule is 100% transitive. If you build one, you suck -- S.Yegge
CI checkout on floating tag, then using maven-scm-plugin to update pom.xml to latest?
Hello, I am trying to use Hudson to perform automated software releases based on a floating CVS tag. When developers move the floating tag on the sources, they indicate that the tagged code can go in a next build. Hudson then checks out the code and executes a release:prepare. Problem now is that the changes to pom.xml (done by the release plugin) can't be checked in since the CVS information indicates that the version retrieved is a sticky tag (although usually it is the latest version). To get around this, I want to use maven-scm-plugin (in the validate phase of my Maven run) to update pom.xml to the latest version. However, I tried several goals (update, checkout, export) but pom.xml remains the the version based on the tag. Can anyone tell me how to update pom.xml to the latest version coming from the branch configured in the connectionUrl/developerConnectionUrl info from the POM? Also, my experiments so far seem to indicate that includes/excludes configuration is ignored in the goals tried. Known bug? Ringo * Dit e-mail bericht inclusief eventuele ingesloten bestanden kan informatie bevatten die vertrouwelijk is en/of beschermd door intellectuele eigendomsrechten. Dit bericht is uitsluitend bestemd voor de geadresseerde(n). Elk gebruik van de informatie vervat in dit bericht (waaronder de volledige of gedeeltelijke reproductie of verspreiding onder elke vorm) door andere personen dan de geadresseerde(n) is verboden. Indien u dit bericht per vergissing heeft ontvangen, gelieve de afzender hiervan te verwittigen en dit bericht te verwijderen. This e-mail and any attachment thereto may contain information which is confidential and/or protected by intellectual property rights and are intended for the sole use of the addressees. Any use of the information contained herein (including but not limited to total or partial reproduction or distribution in any form) by other persons than the addressees is prohibited. If you have received this e-mail in error, please notify the sender and delete its contents. Ce courriel et les annexes �ventuelles peuvent contenir des informations confidentielles et/ou prot�g�es par des droits de propri�t� intellectuelle. Ce message est adress� exclusivement � son (ses) destinataire(s). Toute utilisation du contenu de ce message (y compris la reproduction ou diffusion partielle ou compl�te sous toute forme) par une autre personne que le(s) destinataire(s) est formellement interdite. Si vous avez re�u ce message par erreur, veuillez pr�venir l'exp�diteur du message et en d�truire le contenu. *
Re: Running ALL tests and fail at the END
mvn test --fail-at-end or mvn test -fae mvn -h also helps regards, Stefan On Tue, 10 Feb 2009 01:35:48 -0800 (PST) Peter Meier blackicec...@gmx.net wrote: In my Maven project I have several modules which all have tests. If I run the tests and one module fails, then the execution is cancelled. But I want that the tests of ALL modules are executed and then at the end I want a notification that some tests have failed. I have tried it with setting the testFailureIgnore option on my pom.xml: configuration testFailureIgnoretrue/testFailureIgnore /configuration But in this case mvn test will return successfully: [...] [INFO] [INFO] [INFO] Reactor Summary: [INFO] [INFO] Module A .. SUCCESS [4.520s] [INFO] Module B ... SUCCESS [4:06.863s] [INFO] Module C . SUCCESS [14.553s] [INFO] Module D . SUCCESS [10.785s] [INFO] [INFO] [INFO] BUILD SUCCESSFUL [INFO] [INFO] Total time: 4 minutes 28 seconds [INFO] Finished at: Tue Feb 10 09:15:56 CET 2009 [INFO] Final Memory: 36M/69M [INFO] All module tests return success even though for example Module B failed. (without setting testFailureIgnore option only tests of Module B are executed) Is there any other option to achieve that all tests are executed with a fail notification at the end? (I have also played around with 'maven.test.haltafterfailure' but it seemed not to have any effect) Thanks for any help! -- Mit freundlichen Grüßen, Stefan Seidel Software-Entwickler VUB Printmedia GmbH Chopinstraße 4, 04103 Leipzig tel.+49 (341) 9 60 50 93 fax.+49 (341) 9 60 50 92 mail. ssei...@vub.de web.www.vub.de HRB Köln 24015 UStID DE 122 649 251 GF Dr. Achim Preuss Neudorf, Dr. Christian Preuss Neudorf - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Doesn't suppress box around APT text
Hello, according to the APT format a text like this: Some text should look without box around in the html, but there is a box around... I tried the sample in the format description but the result is the same. Does it work for anybody? Or it can be a bug? Thanks a lot! Czollli -- View this message in context: http://www.nabble.com/Doesn%27t-suppress-box-around-APT-text-tp21931250p21931250.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: Running ALL tests and fail at the END
Great! Thanks for the hint, that really helped! Stefan Seidel wrote: mvn test --fail-at-end or mvn test -fae mvn -h also helps regards, Stefan -- View this message in context: http://www.nabble.com/Running-ALL-tests-and-fail-at-the-END-tp21930359p21931545.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: Doesn't suppress box around APT text
I can confirm your observation, i.e., it doesn't work for me either (using Maven 2.0.9 and site plugin 2.0-beta-7). But I havn't checked if there is already an issue about that in JIRA. -- Thorsten Czollli wrote: Hello, according to the APT format a text like this: Some text should look without box around in the html, but there is a box around... I tried the sample in the format description but the result is the same. Does it work for anybody? Or it can be a bug? Thanks a lot! Czollli -- View this message in context: http://www.nabble.com/Doesn%27t-suppress-box-around-APT-text-tp21931250p21932504.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: Does maven not use VERSION while detecting circular dependencies?
- Geoffrey This is too limiting IMO. Sahoo Why? You can't have multiple versions of the same jar on the classpath, so allowing these circular dependencies to take version into consideration just pushes the problem futher down the stack. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Mavenium browser specification
hi,
is it possible to set up the mavenium plugin that the testsuits will be run
in more than one browser ?
For example my configuration now is like this:
plugin
groupIdcom.agilepirates/groupId
artifactIdmavenium/artifactId
version0.1/version
executions
execution
goals
goallaunch-selenium/goal
goalvalidate-selenium-tests/goal
/goals
/execution
/executions
configuration
server.port80/server.port
selenium.tests.source.dir${basedir}/src/selenium/selenium.tests.source.dir
browser.nameopera/browser.name
/configuration
/plugin
Atm this will execute my test in opera, how do i have to change the
configuration that opera,firefox,iexplore and custom browsers get executed
one by one ? Is this even possbile by configuration?
thanks kukudas
--
View this message in context:
http://www.nabble.com/Mavenium-browser-specification-tp21934224p21934224.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: Resolved Version Weirdness
Sounds to me like a classic case of not specifying your direct dependencies. Some other pom changed and introduced a transitive change breaking something you actually depend on. Run mvn dependency:analyze on your projects, if it says you are missing direct dependencies, you should fix them. Yes, dependency-plugin and jar-plugin use the same resolution -- that is core hands the artifact list over to the plugins when they start. The dependency-plugin get the test scope to start which includes everything, perhaps some test dependency you have slightly changed and is influencing the dependency tree as seen by it. -Original Message- From: Reinhard Nägele [mailto:reinhard.naeg...@mgm-tp.com] Sent: Monday, February 09, 2009 2:41 AM To: users@maven.apache.org Subject: Resolved Version Weirdness Hello, We have a multi-module project which transitively uses Commons Logging. We do not use it directly ourselves and so did not explicitly declare it as a dependency. So far, this has not been a problem. But for some reason, something must have changed over the weekend. I started our application and got a NoClassDefFoundError because org.apache.commons.logging.LogFactory was missing. I then checked the following: - Maven dependencies in Eclipse (using m2eclipse) showed commons-logging-1.1 - The dependency hierarchy and dependency:tree showed commons-logging-1.1 as the winner (amongst 1.0, 1.0.3, 1.0.4, 1.1, 1.1.1) . dependency:copy copied commons-logging-1.1.jar - The Jar plugin wrote commons-logging-1.1.1 into the manifest. So, the problem is that either the Jar plugin or the Dependency plugin is wrong. Don't they use the same mechanism in order to determine the classpath? Naturally, I would expect the latest version to win. I don't understand why this happened all of a sudden. Nothing has changed here, and all our plugin versions are locked. For now, I fixed the problem by explicitly adding commons-logging-1.1.1 as a dependency, but I don't really like this. I'd appreciate any insight into what's going on here. Thanks, Reinhard - 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
How to build maven project using Maven Ant Tasks?
Hi Friends, I want to build maven project using Maven Ant Tasks. As posted in http://www.nabble.com/Ant-Task---Build-maven-pom.xml-td17657445.html#a17657445 ; can I just build maven project using ant tasks? I have project xyz which has myprojects/xyz/pom.xml file and I can build this project using command mvn install. Now, If I have other project abc, which has ant myprojects/abc/build.xml file. I want to build xyz project from abc project. Is this possible using Maven Ant Tasks? Thanks regards Vikas
Request for release of maven-eclipse-plugin 2.6
Hi together The last release of maven-eclipse-plugin is from April 2008 and as I see in Jira version 2.6 is complete (taskfree). Who may I ask for a release, I'm waiting for the fix for: http://jira.codehaus.org/browse/MECLIPSE-111 Thanks a lot Martin - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven 2.0.9 - Upgrade Hints/Conflicts with other tools?
Hello, I work for a company that is fairly new to Maven and open source in general. We are currently using Maven 2.0.5 with Continuum for our continuous build server and Artifactory for our internal artifact repository. We need to upgrade to Maven 2.0.9, but this is the first time we have upgraded and I have a few questions/concerns. I tried to search for related info on Google but did not find much. I also tried to search the last few months worth of posts on the mailing list. I did come across an older post on issues with Continuum and Maven 2.0.7 http://jira.codehaus.org/browse/MNG-3084 and while it is obviously not an issue for 2.0.9, it's an example of some of the concerns I have of potential issues to watch out for. Essentially, my question is, are there any best practices to follow when upgrading versions of Maven? Are there easy ways to upgrade all the latest versions of various plug-ins for example? Does one necessarily need to upgrade to the latest versions of plug-ins or is it more of a case by case basis? Are there any issues to be aware of with Continuum? Perhaps that's a post for the Continuum mailing list. I apologize if this is too basic a question, as I mentioned we are fairly new to the environment and I would like to make this initial upgrade as seamless as possible. It's not the actual upgrade of Maven, that's simple enough, more any related steps in the process that we may not be aware of. Thanks in advance for any assistance. Dave Bruley Technical Analyst CoreLink Administrative Solutions Confidentiality Notice: This e-mail message and any attachments are for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure, distribution or copying is prohibited. If you are not the intended recipient(s), please contact the sender by replying to this e-mail and destroy/delete all copies of this e-mail message. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Maven 2.0.9 - Upgrade Hints/Conflicts with other tools?
Hudson is another viable option: https://hudson.dev.java.net/ --- Thank You… Mick Knutson, President BASE Logic, Inc. Enterprise Architecture, Design, Mentoring Agile Consulting p. (866) BLiNC-411: (254-6241-1) f. (415) 685-4233 Website: http://baselogic.com Linked IN: http://linkedin.com/in/mickknutson Twitter: http://twitter.com/mickknutson Vacation Rental: http://tahoe.baselogic.com --- On Tue, Feb 10, 2009 at 9:52 AM, David Bruley david.bru...@bcbsnd.comwrote: Hello, I work for a company that is fairly new to Maven and open source in general. We are currently using Maven 2.0.5 with Continuum for our continuous build server and Artifactory for our internal artifact repository. We need to upgrade to Maven 2.0.9, but this is the first time we have upgraded and I have a few questions/concerns. I tried to search for related info on Google but did not find much. I also tried to search the last few months worth of posts on the mailing list. I did come across an older post on issues with Continuum and Maven 2.0.7 http://jira.codehaus.org/browse/MNG-3084 and while it is obviously not an issue for 2.0.9, it's an example of some of the concerns I have of potential issues to watch out for. Essentially, my question is, are there any best practices to follow when upgrading versions of Maven? Are there easy ways to upgrade all the latest versions of various plug-ins for example? Does one necessarily need to upgrade to the latest versions of plug-ins or is it more of a case by case basis? Are there any issues to be aware of with Continuum? Perhaps that's a post for the Continuum mailing list. I apologize if this is too basic a question, as I mentioned we are fairly new to the environment and I would like to make this initial upgrade as seamless as possible. It's not the actual upgrade of Maven, that's simple enough, more any related steps in the process that we may not be aware of. Thanks in advance for any assistance. Dave Bruley Technical Analyst CoreLink Administrative Solutions Confidentiality Notice: This e-mail message and any attachments are for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure, distribution or copying is prohibited. If you are not the intended recipient(s), please contact the sender by replying to this e-mail and destroy/delete all copies of this e-mail message. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Release plugin question
Hi, I use maven 2.0.9 and do releases with the release plug-in. Everything works fine but I would like to prevent release:perform from generating a source jar and javadoc jar file. The plug-in also installs the generated jars it in our local repository. Is it away to prevent this? Thanks, Gunnar - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How to list the maven final output without executing the actual build process
We have a process that creates the maven artifact in the development stage. Later for the packaging and/or direct deployment we want to refer to the same output (but without recreating the artifact.). How can I do that with maven ? for example maven (actual build process) creates the output as abc.build_number.ear I want to list that (abc.build_number.ear ) without executing the actual build (that is using certain command line parameter) like a dry run (indicating this is what you will generate if you execute the actual build) I do not want to recreate the artifact (abc.build_number.ear) though. Thanks Atul CONFIDENTIALITY NOTICE: The information contained in this message is intended only for the recipient and may contain information that is confidential. If you are not the intended recipient or an employee or agent responsible for delivering this message to the intended recipient; please be aware that any dissemination, forwarding, printing, copying, disclosure or distribution of this communication is strictly prohibited. If you have received this communication in error, please immediately notify the sender by replying to the message and deleting all copies, including attachments, from your system.
Re: Release plugin question
Use releaseProfile=false (see documentation at http://maven.apache.org/plugins/maven-release-plugin/perform-mojo.html), you can add it in the pom as part of release plugin's configuration. Kalle On Tue, Feb 10, 2009 at 7:17 AM, gunnar.bost...@tieto.com wrote: Hi, I use maven 2.0.9 and do releases with the release plug-in. Everything works fine but I would like to prevent release:perform from generating a source jar and javadoc jar file. The plug-in also installs the generated jars it in our local repository. Is it away to prevent this? Thanks, Gunnar - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Problems with maven-kogo-plugin
I'Hi there - I'm trying to get this plug in to work when installing one of my projects. This is the message I am getting when trying to do an mvn install: [INFO]task-segment: [install] [INFO] [INFO] artifact org.apache.maven.plugins:maven-eclipse-plugin: checking for updates from central [INFO] [ERROR] FATAL ERROR [INFO] [INFO] The PluginDescriptor for the plugin Plugin [maven-plugins:maven-kodo-plugin] was not found. [INFO] [INFO] Trace java.lang.IllegalStateException: The PluginDescriptor for the plugin Plugin [maven-plugins:maven-kodo-plugin] was not found. at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:325) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:212) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:176) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1274) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycle(DefaultLifecycleExecutor.java:1238) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1004) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:477) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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) [INFO] [INFO] Total time: 2 seconds [INFO] Finished at: Tue Feb 10 09:25:37 CST 2009 The pom for my project contains the following: plugin groupIdmaven-plugins/groupId artifactIdmaven-kodo-plugin/artifactId version3.1.2/version executions execution phasecompile/phase goals goalenhance/goal /goals /execution /executions /plugin Any suggestions? Thanks! -- View this message in context: http://www.nabble.com/Problems-with-maven-kogo-plugin-tp21936149p21936149.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: How can the checkstyle plugin be configured to fail the build?
nitinaggarwal wrote: Hi I am facing a similiar issue in my project. But additionally i want the a checkstyle file FC-CheckStyle.xml customized to my project be invoked in order to find out if there are checkstyle errors . how do i do that? Additionally can some one tell me how can i refer to this file as this is located in my root directory and i want to invoke the file in a directory fc to be more clear i will provide a brief about my project. FC-4.0 Source--application--fc(my pom is here) --er (and here) --portal -- components--pom -- pom Can some one suggest me how to perform this checkstyle validation. would you suggest me the validation to be at the top level or at every level as i am having a multli project build. but the issue with this approach is that all the developers would have to build the entire project rather than a sub project for finding out check style errors. any comments how we can extend something from the top level pom. Nitin nitin.fbsi.aggar...@fidelity.com Guillaume Boucherie wrote: try something like this. build plugins plugin groupIdorg.apache.maven.pluginsgroupId artifactIdmaven-checkstyle-plugin/artifactId executions execution goals goalcheck/goal /goals /execution /executions /plugin /plugins /build by default the check goal is link to verify phase CletteBou 2007/6/21, Andrew Moores amoore...@yahoo.com: Hello I want to make my build fail if there are any checkstyle errors in my code. I have added the following to my pom: build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId configuration failOnViolationtrue/failOnViolation /configuration /plugin /plugins /build When I execute mvn checkstyle:check my build fails when I have a checkstyle error. When I execute mvn install the build does not fail. Reading the plugin pages I expected my build to fail for the intall goal as well, what else do I need to add to the POM to make the build fail? I am running Maven 2.0.5. Thanks Andrew This would be more apt: build ….. plugins … plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-checkstyle-plugin/artifactId executions execution phaseinstall/phase goals goalcheckstyle/goal !—checkstyle : generates the reports in a site folder in HTML format-- !— check: can be used if only the errors have to be checked-- /goals /execution /executions configuration failOnViolationtrue/failOnViolation !—will fail the build if checkstyle violated -- enableRulesSummaryfalse/enableRulesSummary configLocationcheckstyle-checker1.xml/configLocation !—Customized checker xml located in the location of the pom.xml-- /configuration /plugin /plugins /build If checkstyle doesn't work then use check -- View this message in context: http://www.nabble.com/How-can-the-checkstyle-plugin-be-configured-to-fail-the-build--tp11235269p21936262.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: Problems with maven-kogo-plugin
transcription error perhaps? maven-kodo vs maven-kogo -Original Message- From: maven_noob [mailto:kristianfra...@gmail.com] Sent: Tuesday, February 10, 2009 7:33 AM To: users@maven.apache.org Subject: Problems with maven-kogo-plugin I'Hi there - I'm trying to get this plug in to work when installing one of my projects. This is the message I am getting when trying to do an mvn install: [INFO]task-segment: [install] [INFO] [INFO] artifact org.apache.maven.plugins:maven-eclipse-plugin: checking for updates from central [INFO] [ERROR] FATAL ERROR [INFO] [INFO] The PluginDescriptor for the plugin Plugin [maven-plugins:maven-kodo-plugin] was not found. [INFO] [INFO] Trace java.lang.IllegalStateException: The PluginDescriptor for the plugin Plugin [maven-plugins:maven-kodo-plugin] was not found. at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:325) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:212) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:176) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1274) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycle(DefaultLifecycleExecutor.java:1238) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1004) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:477) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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) [INFO] [INFO] Total time: 2 seconds [INFO] Finished at: Tue Feb 10 09:25:37 CST 2009 The pom for my project contains the following: plugin groupIdmaven-plugins/groupId artifactIdmaven-kodo-plugin/artifactId version3.1.2/version executions execution phasecompile/phase goals goalenhance/goal /goals /execution /executions /plugin Any suggestions? Thanks! -- View this message in context: http://www.nabble.com/Problems-with-maven-kogo-plugin-tp21936149p21936149.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: Problems with maven-kogo-plugin
I see a Sourceforge project [1] which haven't been updated for quite a while (2005) and a codehaus project [2], which also seems a bit dead. (Correct me if I'm wrong) It seems the Sourceforge project is still a maven 1 plugin and the codehaus project didn't got any further than an alpha version. I think you're out of luck. [1] http://maven-plugins.sourceforge.net/maven-kodo-plugin/ [2] http://mojo.codehaus.org/kodo-maven-plugin/index.html Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Tue, Feb 10, 2009 at 4:57 PM, Sean Hennessy shenne...@astutenetworks.com wrote: transcription error perhaps? maven-kodo vs maven-kogo -Original Message- From: maven_noob [mailto:kristianfra...@gmail.com] Sent: Tuesday, February 10, 2009 7:33 AM To: users@maven.apache.org Subject: Problems with maven-kogo-plugin I'Hi there - I'm trying to get this plug in to work when installing one of my projects. This is the message I am getting when trying to do an mvn install: [INFO]task-segment: [install] [INFO] [INFO] artifact org.apache.maven.plugins:maven-eclipse-plugin: checking for updates from central [INFO] [ERROR] FATAL ERROR [INFO] [INFO] The PluginDescriptor for the plugin Plugin [maven-plugins:maven-kodo-plugin] was not found. [INFO] [INFO] Trace java.lang.IllegalStateException: The PluginDescriptor for the plugin Plugin [maven-plugins:maven-kodo-plugin] was not found. at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:325) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:212) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:176) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1274) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycle(DefaultLifecycleExecutor.java:1238) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1004) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:477) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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) [INFO] [INFO] Total time: 2 seconds [INFO] Finished at: Tue Feb 10 09:25:37 CST 2009 The pom for my project contains the following: plugin groupIdmaven-plugins/groupId artifactIdmaven-kodo-plugin/artifactId version3.1.2/version executions execution phasecompile/phase goals goalenhance/goal /goals /execution /executions /plugin Any suggestions? Thanks! -- View this message in context: http://www.nabble.com/Problems-with-maven-kogo-plugin-tp21936149p21936149.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 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For
Re: Problems with maven-kogo-plugin
Nick Stolwijk-4 wrote: I see a Sourceforge project [1] which haven't been updated for quite a while (2005) and a codehaus project [2], which also seems a bit dead. (Correct me if I'm wrong) It seems the Sourceforge project is still a maven 1 plugin and the codehaus project didn't got any further than an alpha version. I think you're out of luck. [1] http://maven-plugins.sourceforge.net/maven-kodo-plugin/ [2] http://mojo.codehaus.org/kodo-maven-plugin/index.html Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Tue, Feb 10, 2009 at 4:57 PM, Sean Hennessy shenne...@astutenetworks.com wrote: transcription error perhaps? maven-kodo vs maven-kogo -Original Message- From: maven_noob [mailto:kristianfra...@gmail.com] Sent: Tuesday, February 10, 2009 7:33 AM To: users@maven.apache.org Subject: Problems with maven-kogo-plugin I'Hi there - I'm trying to get this plug in to work when installing one of my projects. This is the message I am getting when trying to do an mvn install: [INFO]task-segment: [install] [INFO] [INFO] artifact org.apache.maven.plugins:maven-eclipse-plugin: checking for updates from central [INFO] [ERROR] FATAL ERROR [INFO] [INFO] The PluginDescriptor for the plugin Plugin [maven-plugins:maven-kodo-plugin] was not found. [INFO] [INFO] Trace java.lang.IllegalStateException: The PluginDescriptor for the plugin Plugin [maven-plugins:maven-kodo-plugin] was not found. at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:325) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:212) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:176) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1274) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycle(DefaultLifecycleExecutor.java:1238) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1004) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:477) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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) [INFO] [INFO] Total time: 2 seconds [INFO] Finished at: Tue Feb 10 09:25:37 CST 2009 The pom for my project contains the following: plugin groupIdmaven-plugins/groupId artifactIdmaven-kodo-plugin/artifactId version3.1.2/version executions execution phasecompile/phase goals goalenhance/goal /goals /execution /executions /plugin Any suggestions? Thanks! -- View this message in context: http://www.nabble.com/Problems-with-maven-kogo-plugin-tp21936149p21936149.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 - To unsubscribe,
eclipse:eclipse - no .project for POM packaging?
Is there a way to force the maven-eclipse-plugin to produce .project files for modules that are packaging=pom? I didn't see anything in the docs that indicated it would work, but I thought I'd ask. (We've got an integration-test module that really doesn't need to produce an artifact.) - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Aggregator pom fails, but modules work
I'm not quite sure what you mean by abusing 'src' and 'test'. At any rate, yes, I get the same problem if I rename the sub-projects dir1 and dir2. Also, I had a look at the shitty-maven-plugin, and it looks like it will require a directory re-structure, since it expects the tests to be under src/it. Unfortunately we must make Maven work without modifying our directory structure, so that won't be an option for us unless that bit can be configured. Any other ideas/suggestions? Merv Green wrote: You may be abusing 'src' and 'test.' Do you get the same problem if you rename the sub-projects 'dir1' and 'dir2?' Have you considered something like the shitty-maven-plugin? Google for 'maven integration testing.' -- View this message in context: http://www.nabble.com/Aggregator-pom-fails%2C-but-modules-work-tp21882332p21938575.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: Maven 2.0.9 - Upgrade Hints/Conflicts with other tools?
The first thing I would do is lock down all the versions of plugins in all your builds Then you can try with the newer version of maven, and once that is working, try updating the plugin versions. If you have not locked down your plugin versions, your build is not reproducible and you need to lock them down right now. With locked down plugin versions I usually find very little issues switching maven versions. 2009/2/10 Mick Knutson mickknut...@gmail.com: Hudson is another viable option: https://hudson.dev.java.net/ --- Thank You… Mick Knutson, President BASE Logic, Inc. Enterprise Architecture, Design, Mentoring Agile Consulting p. (866) BLiNC-411: (254-6241-1) f. (415) 685-4233 Website: http://baselogic.com Linked IN: http://linkedin.com/in/mickknutson Twitter: http://twitter.com/mickknutson Vacation Rental: http://tahoe.baselogic.com --- On Tue, Feb 10, 2009 at 9:52 AM, David Bruley david.bru...@bcbsnd.comwrote: Hello, I work for a company that is fairly new to Maven and open source in general. We are currently using Maven 2.0.5 with Continuum for our continuous build server and Artifactory for our internal artifact repository. We need to upgrade to Maven 2.0.9, but this is the first time we have upgraded and I have a few questions/concerns. I tried to search for related info on Google but did not find much. I also tried to search the last few months worth of posts on the mailing list. I did come across an older post on issues with Continuum and Maven 2.0.7 http://jira.codehaus.org/browse/MNG-3084 and while it is obviously not an issue for 2.0.9, it's an example of some of the concerns I have of potential issues to watch out for. Essentially, my question is, are there any best practices to follow when upgrading versions of Maven? Are there easy ways to upgrade all the latest versions of various plug-ins for example? Does one necessarily need to upgrade to the latest versions of plug-ins or is it more of a case by case basis? Are there any issues to be aware of with Continuum? Perhaps that's a post for the Continuum mailing list. I apologize if this is too basic a question, as I mentioned we are fairly new to the environment and I would like to make this initial upgrade as seamless as possible. It's not the actual upgrade of Maven, that's simple enough, more any related steps in the process that we may not be aware of. Thanks in advance for any assistance. Dave Bruley Technical Analyst CoreLink Administrative Solutions Confidentiality Notice: This e-mail message and any attachments are for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure, distribution or copying is prohibited. If you are not the intended recipient(s), please contact the sender by replying to this e-mail and destroy/delete all copies of this e-mail message. - 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: [ANN] - SCM Changelog Maven Plugin 1.1 Released
Yes, I was thinking on scmchangelog. With excludeSubtasks set and JIRA as issue tracker, for commits with issue id provided scmchangelog could obtain issue details, check if the issue is a subtask, and based on that decide whether to include issue in or exclude issue from the report. Commits without issue id can be excluded in this case, or even better another filter configuration option (e.g. new excludeNonIssues attribute of filter element) should be provided that would allow user to specify desired behavior. After applying these filters, regular already present filter option (if not empty) should be applied. These are all nice-to-haves. Regards, Stevo. On Tue, Feb 10, 2009 at 9:34 AM, Rémy Sanlaville remy.sanlavi...@gmail.comwrote: Congrats, keep up the good work! Thanks Stevo. We hope that our plugin One new feature suggestion - support for filtering subtasks (at least when jira is issue tracker), e.g. through optional excludeSubtasks attribute of filter configuration element. Are you sure that it is for our plugin and not for the maven-changes-plugin. In fact, with our plugin, you just have to not add the subtasks id in the SCM comment. Regards, Rémy
Re: Maven 2.0.9 - Upgrade Hints/Conflicts with other tools?
FWIW, we setup a second CI system (hudson) in order to run builds with several different future versions of maven to help catch upgrade issues. On Tue, Feb 10, 2009 at 10:31 AM, Stephen Connolly stephen.alan.conno...@gmail.com wrote: The first thing I would do is lock down all the versions of plugins in all your builds Then you can try with the newer version of maven, and once that is working, try updating the plugin versions. If you have not locked down your plugin versions, your build is not reproducible and you need to lock them down right now. With locked down plugin versions I usually find very little issues switching maven versions. 2009/2/10 Mick Knutson mickknut...@gmail.com: Hudson is another viable option: https://hudson.dev.java.net/ --- Thank You… Mick Knutson, President BASE Logic, Inc. Enterprise Architecture, Design, Mentoring Agile Consulting p. (866) BLiNC-411: (254-6241-1) f. (415) 685-4233 Website: http://baselogic.com Linked IN: http://linkedin.com/in/mickknutson Twitter: http://twitter.com/mickknutson Vacation Rental: http://tahoe.baselogic.com --- On Tue, Feb 10, 2009 at 9:52 AM, David Bruley david.bru...@bcbsnd.com wrote: Hello, I work for a company that is fairly new to Maven and open source in general. We are currently using Maven 2.0.5 with Continuum for our continuous build server and Artifactory for our internal artifact repository. We need to upgrade to Maven 2.0.9, but this is the first time we have upgraded and I have a few questions/concerns. I tried to search for related info on Google but did not find much. I also tried to search the last few months worth of posts on the mailing list. I did come across an older post on issues with Continuum and Maven 2.0.7 http://jira.codehaus.org/browse/MNG-3084 and while it is obviously not an issue for 2.0.9, it's an example of some of the concerns I have of potential issues to watch out for. Essentially, my question is, are there any best practices to follow when upgrading versions of Maven? Are there easy ways to upgrade all the latest versions of various plug-ins for example? Does one necessarily need to upgrade to the latest versions of plug-ins or is it more of a case by case basis? Are there any issues to be aware of with Continuum? Perhaps that's a post for the Continuum mailing list. I apologize if this is too basic a question, as I mentioned we are fairly new to the environment and I would like to make this initial upgrade as seamless as possible. It's not the actual upgrade of Maven, that's simple enough, more any related steps in the process that we may not be aware of. Thanks in advance for any assistance. Dave Bruley Technical Analyst CoreLink Administrative Solutions Confidentiality Notice: This e-mail message and any attachments are for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure, distribution or copying is prohibited. If you are not the intended recipient(s), please contact the sender by replying to this e-mail and destroy/delete all copies of this e-mail message. - 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: Using the release-plugin on a mercurial release branch.
Bump. Any Mercurial and Maven users here that struggle with the release plugin? What I am doing to get around this isn't pretty and I'd prefer avoid it and fold that feature in the release plugin itself. Essentially, I configured a post-clone hook that triggers a script to update to the right branch. When maven release:perform clones the hg repository, the hook becomes active. It works, but it's dirty. On Feb 8, 2009, at 10:51 PM, Sebastien Martel wrote: Hello List-- I am trying to use the release plugin to make a release build off a named branch using Mercurial. The problem I am running into is that release:perform is not switching to the release branch, it is, however, pulling the right tag, but that's not enough with mercurial, the branch needs to be specified as well: hg clone -r release-tag -r release-branch ... Is there a way to get the plugin to clone the repository that way? Thanks, Sebastien Martel Sebastien Martel smime.p7s Description: S/MIME cryptographic signature
Eclipse Plugin - No .classpath file.
How does the maven-eclipse-pluging know to create .classpath for Eclipse? I've created a custom packaging type for my integration test module to prevent undesirable activity. So, for now, only the compile and resources phases are actually doing anything. Now, when I run eclipse:eclipse on the project, I get a .project file and .settings directory, but there is no .classpath. I'd really like for my integration tests to be in the .classpath file since they are Java-based, but I don't know what triggers the maven-eclipse-plugin to generate that file - unless it's the packaging type, in which case I'm basically hosed. If it's just a matter of having another specific lifecycle event added to my packaging type, that's an easy fix. Thanks, Dave - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Maven 2.0.9 - Upgrade Hints/Conflicts with other tools?
There were changes between 2.0.5 and 2.0.6 that related to the handling of transitive dependencies and dependencyManagment. There is a goal in the dependency plugin to help you prepare your build before you migrate. You definitely want to look at this: http://maven.apache.org/plugins/maven-dependency-plugin/examples/prepari ng-dependencies.html Anything else should be documented in the release notes for each release which is still on the site. Also note that 2.0.10 is staged and being voted on. Assuming it will pass, it's 2 days away from a release. -Original Message- From: David Bruley [mailto:david.bru...@bcbsnd.com] Sent: Tuesday, February 10, 2009 9:52 AM To: users@maven.apache.org Subject: Maven 2.0.9 - Upgrade Hints/Conflicts with other tools? Hello, I work for a company that is fairly new to Maven and open source in general. We are currently using Maven 2.0.5 with Continuum for our continuous build server and Artifactory for our internal artifact repository. We need to upgrade to Maven 2.0.9, but this is the first time we have upgraded and I have a few questions/concerns. I tried to search for related info on Google but did not find much. I also tried to search the last few months worth of posts on the mailing list. I did come across an older post on issues with Continuum and Maven 2.0.7 http://jira.codehaus.org/browse/MNG-3084 and while it is obviously not an issue for 2.0.9, it's an example of some of the concerns I have of potential issues to watch out for. Essentially, my question is, are there any best practices to follow when upgrading versions of Maven? Are there easy ways to upgrade all the latest versions of various plug-ins for example? Does one necessarily need to upgrade to the latest versions of plug-ins or is it more of a case by case basis? Are there any issues to be aware of with Continuum? Perhaps that's a post for the Continuum mailing list. I apologize if this is too basic a question, as I mentioned we are fairly new to the environment and I would like to make this initial upgrade as seamless as possible. It's not the actual upgrade of Maven, that's simple enough, more any related steps in the process that we may not be aware of. Thanks in advance for any assistance. Dave Bruley Technical Analyst CoreLink Administrative Solutions Confidentiality Notice: This e-mail message and any attachments are for the sole use of the intended recipient(s) and may contain confidential and privileged information. Any unauthorized review, use, disclosure, distribution or copying is prohibited. If you are not the intended recipient(s), please contact the sender by replying to this e-mail and destroy/delete all copies of this e-mail message. - 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: Problems with maven-kogo-plugin
This was my project and since it got blocked by maven 2.0.2 bugs at the time... I never went back to fixing it. Now that you can fairly easily wrap ant tasks into plugins, I would suggest that approach. The kodo plugin in the sandbox required too much hacking of the ant task code to make it work reliably. It did work ok for enhancing at the time but I would be surprised if it worked with later versions of their tools. -Original Message- From: Nick Stolwijk [mailto:nick.stolw...@gmail.com] Sent: Tuesday, February 10, 2009 11:06 AM To: Maven Users List Subject: Re: Problems with maven-kogo-plugin I see a Sourceforge project [1] which haven't been updated for quite a while (2005) and a codehaus project [2], which also seems a bit dead. (Correct me if I'm wrong) It seems the Sourceforge project is still a maven 1 plugin and the codehaus project didn't got any further than an alpha version. I think you're out of luck. [1] http://maven-plugins.sourceforge.net/maven-kodo-plugin/ [2] http://mojo.codehaus.org/kodo-maven-plugin/index.html Nick Stolwijk ~Java Developer~ Iprofs BV. Claus Sluterweg 125 2012 WS Haarlem www.iprofs.nl On Tue, Feb 10, 2009 at 4:57 PM, Sean Hennessy shenne...@astutenetworks.com wrote: transcription error perhaps? maven-kodo vs maven-kogo -Original Message- From: maven_noob [mailto:kristianfra...@gmail.com] Sent: Tuesday, February 10, 2009 7:33 AM To: users@maven.apache.org Subject: Problems with maven-kogo-plugin I'Hi there - I'm trying to get this plug in to work when installing one of my projects. This is the message I am getting when trying to do an mvn install: [INFO]task-segment: [install] [INFO] [INFO] artifact org.apache.maven.plugins:maven-eclipse-plugin: checking for updates from central [INFO] [ERROR] FATAL ERROR [INFO] [INFO] The PluginDescriptor for the plugin Plugin [maven-plugins:maven-kodo-plugin] was not found. [INFO] [INFO] Trace java.lang.IllegalStateException: The PluginDescriptor for the plugin Plugin [maven-plugins:maven-kodo-plugin] was not found. at org.apache.maven.plugin.DefaultPluginManager.addPlugin(DefaultPluginManager.java:325) at org.apache.maven.plugin.DefaultPluginManager.verifyVersionedPlugin(DefaultPluginManager.java:212) at org.apache.maven.plugin.DefaultPluginManager.verifyPlugin(DefaultPluginManager.java:176) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin(DefaultLifecycleExecutor.java:1274) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycle(DefaultLifecycleExecutor.java:1238) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:1004) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:477) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:330) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:291) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:142) at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:336) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:129) at org.apache.maven.cli.MavenCli.main(MavenCli.java:287) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) 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) [INFO] [INFO] Total time: 2 seconds [INFO] Finished at: Tue Feb 10 09:25:37 CST 2009 The pom for my project contains the following: plugin groupIdmaven-plugins/groupId artifactIdmaven-kodo-plugin/artifactId version3.1.2/version executions execution phasecompile/phase goals goalenhance/goal /goals /execution /executions /plugin Any suggestions? Thanks! -- View this message in context:
Re: M2Eclipse Plugin can't resolve workspace dependency during MVN compile
On 10-Feb-09, at 8:47 AM, Lincoln Baxter, III wrote: Hey Yves, thanks for looking in to this. ocpsoft-base hasn't been released yet, but it exists in my workspace. If I'm understanding the M2eclipse plugin correctly, it should be able to detect that I have a project with that groupId/artifactId in my The version must also match. If you refer to a project and the version doesn't match the version in your workspace then m2eclipse will use normal Maven resolution which is checking your local and then remote versions. workspace, and resolve it without having a JAR file installed in any repository, however, it doesn't seem to be doing that. I have to install the jar into my local repository before any projects that depend on it will compile as a MVN build (they compile ok in eclipse). Maven is not m2eclipse. The Maven CLI is not going to be able to build anything if you don't have it installed. The CLI and m2eclipse's operation inside Eclipse are two separate things. And actually :) the download you listed is the prettyfaces extension. Is what I'm saying making any sense, or is the M2eclipse plugin not designed for what I want to do? Thanks! Lincoln On Tue, 2009-02-10 at 09:11 +0100, Yves Dessertine wrote: Maven2 was unable to find http://repo1.maven.org/maven2/com/ocpsoft/ocpsoft-base/1.0.0/ocpsoft-base-1.0.0.pom In short, your artifact with : groupId com.ocpsoft artifactId ocpsoft-base version 1.0.0 doesn't exist in maven's public repository (if you try accessing the URL in the error message, you'll get 404 errors. BUT, you can download the jar file manually from here : http://prettyfaces.googlecode.com/files/ocpsoft-pretty- faces-1.0.0.jar save it on your disk, then install it manually by running : mvn install:install-file -DgroupId=com.ocpsoft -DartifactId=ocpsoft-base -Dversion=1.0.0 -Dpackaging=jar -Dfile=/path/to/file Should now compile. Hope this helps. Yves 2009/2/7 Lincoln Baxter, III lincolnbax...@gmail.com: Hi All, I am trying to run a build without installing my workspace dependencies into the local repository, however, I get this exception, and the build fails: How can I fix this? All projects required are in my workspace. I'm using Eclipse 3.4. Thanks, Lincoln [INFO] Scanning for projects... [INFO] [INFO] Building Hibernate Data Base Package [INFO] [INFO] Id: com.ocpsoft:ocpsoft-data:jar:1.0.0 [INFO] task-segment: [package] [INFO] [INFO] [resources:resources] [INFO] Using default encoding to copy filtered resources. url = http://repo1.maven.org/maven2 Downloading: http://repo1.maven.org/maven2/com/ocpsoft/ocpsoft-base/1.0.0/ocpsoft-base-1.0.0.pom url = http://repo1.maven.org/maven2 Downloading: http://repo1.maven.org/maven2/com/ocpsoft/ocpsoft-base/1.0.0/ocpsoft-base-1.0.0.pom url = http://repo1.maven.org/maven2 Downloading: http://repo1.maven.org/maven2/com/ocpsoft/ocpsoft-base/1.0.0/ocpsoft-base-1.0.0.jar [ERROR] Transitive dependency resolution for scope: compile has failed for your project. Error message: Missing: -- 1) com.ocpsoft:ocpsoft-base:jar:1.0.0 Try downloading the file manually from the project website. Then, install it using the command: mvn install:install-file -DgroupId=com.ocpsoft -DartifactId=ocpsoft-base -Dversion=1.0.0 -Dpackaging=jar -Dfile=/path/to/file Alternatively, if you host your own repository you can deploy the file there: mvn deploy:deploy-file -DgroupId=com.ocpsoft -DartifactId=ocpsoft-base -Dversion=1.0.0 -Dpackaging=jar -Dfile=/path/to/file -Durl=[url] -DrepositoryId=[id] Path to dependency: 1) com.ocpsoft:ocpsoft-data:jar:1.0.0 2) com.ocpsoft:ocpsoft-base:jar:1.0.0 -- 1 required artifact is missing. for artifact: com.ocpsoft:ocpsoft-data:jar:1.0.0 from the specified remote repositories: central (http://repo1.maven.org/maven2) Group-Id: com.ocpsoft Artifact-Id: ocpsoft-data Version: 1.0.0 From file: /gentoo/home/lb3/Projects/ocpsoft-data/pom.xml [INFO] [INFO] For more information, run with the -e flag [INFO] [INFO] BUILD FAILED [INFO] [INFO] Total time: 2 seconds [INFO] Finished at: Sat Feb 07 16:48:04 EST 2009 [INFO] Final Memory: 5M/80M [INFO] Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- In short, man creates for himself a new religion of a rational and technical order to justify his work and to be justified in it. -- Jacques Ellul, The Technological
Assembling artifact attachments derived from actual project dependencies [maven-assembly-plugin]
Hi, I added something into the maven-assembly-plugin that I wanted to share. We want to know if you think it make sense and fit in there to discuss and eventually prepare a contribution. The fact is that the maven-dependency-plugin can be already used to accomplish what I need but in a much more verbose way. The motivation: To be able to include in an assembly artifact attachments derived from actual project dependencies (without having the attachments itself as a real dependency). In my case, it happens that a whole family (same groupid) of artifacts has all a zip attachment. In one project, we need to merge all those zip attachments, resolving then automatically using transitive dependencies, This is how I did that: assembly ... dependencySets dependencySet dependenciesAttachmentSets dependenciesAttachmentSet typezip/type classifierXYZ/classifier /dependenciesAttachmentSet /dependenciesAttachmentSets /dependencySet /dependencySets ... /assembly With this extended :-) assembly descriptor we are including in the assembly all zip XYZ attachments from all dependencies (transitively). In dependenciesAttachmentSet we support includes/excludes exactly as in dependencySet. -- Pedro Rodriguez OpnWorks - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: M2Eclipse Plugin can't resolve workspace dependency during MVN compile
The version must also match. If you refer to a project and the version doesn't match the version in your workspace then m2eclipse will use normal Maven resolution which is checking your local and then remote versions. Yeah the versions match :) Maven is not m2eclipse. The Maven CLI is not going to be able to build anything if you don't have it installed. The CLI and m2eclipse's operation inside Eclipse are two separate things. So when, in Eclipse, I do: Run As - Maven Build Is that invoking the CLI or is m2eclipse doing the work? If it's actually invoking the CLI, then that's the reason, but if m2eclipse is doing the work, I would expect it to find my workspace dependencies during the build. (Which it's not) Does that make sense? Thanks again, Lincoln
Maven Class not found exception
Hey All, I am running my jetty with maven, and I have a dependency in my POM for wicket-contrib-tinymce. Maven downloaded the wicket-contrib-tinymce jar file and I can see it in my repo. Jetty starts up fine as well, but I get a NoClassDefFoundError when I click on a link that contains a page that references this class. I am not sure where or how the classpath is generated when I run maven/jetty. Can someone please help? WicketMessage: Can't instantiate page using constructor public com.jasneo.web.EditQuestion() Root cause: java.lang.NoClassDefFoundError: wicket/contrib/tinymce/TinyMceBehavior at com.jasneo.web.EditQuestion$QuestionsMCForm.init(EditQuestion.java:54) at com.jasneo.web.EditQuestion.init(EditQuestion.java:25) at java.lang.reflect.Constructor.newInstance(Constructor.java:494) at org.apache.wicket.session.DefaultPageFactory.newPage(DefaultPageFactory.java:149) Thanks! -- View this message in context: http://www.nabble.com/Maven-Class-not-found-exception-tp21944885p21944885.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: Maven Class not found exception
I am running my jetty with maven, and I have a dependency in my POM for wicket-contrib-tinymce. Maven downloaded the wicket-contrib-tinymce jar file and I can see it in my repo. Jetty starts up fine as well, but I get a NoClassDefFoundError when I click on a link that contains a page that references this class. What does the dependency look like in your pom? How are you starting Jetty? What kind of packaging are you using in your project - war? Wayne - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Dependency can't be resolved...
I keep getting this error when one of my subprojects builds with Maven 2.1 (the XXX represents a child module of the project): [INFO] [site:attach-descriptor] [WARNING] The dependency: XXX can't be resolved ut has been found in the reactor. This dependency has been excluded from the plugin execution. You should rerun this mojo after executing mvn i stall. What I don't understand about this error, it gives this error for modules that haven't been built yet, but aren't dependencies on the current project. Also, it says this for all but the first child project of the parent module. The first child module does not depend on any of the modules, not are they referenced from it. So if these child projects aren't referenced and are in the reactor to be built, why is it complaining? It's telling me to run mvn install, but that's what I am doing. I'm not sure exactly how to resolve this problem since it makes no sense and just came out of the blue. The other odd thing is that I'm starting the build from a parent pom which is the parent of the submodules causing me problems. If I built from the parent of the problematic child modules, they seem to build fine. If I execute my build from one level higher, then they fail with that error. All my other projects that are similarly structured, don't have this issue. It's only this one particular parent module and it's children. Also, I ran the build with the exact same project revision on my developer machine, same version of maven2 and same jdk, It built successfully. So I guess it's only our build server that's hosed. No clue why, since the same project builds fine on a different machine and depending on where the build is started. Has anyone seen this error crop up with no cause? Thanks!
Re: Maven Class not found exception
Thanks for replying Wayne. This is my depedency. dependency groupIdorg.wicketstuff/groupId artifactIdwicket-contrib-tinymce/artifactId version1.3-SNAPSHOT/version /dependency I start jetty like this - mvn jetty:run and all of that starts fine and does not complain about this missing class file. And the packaging is war. modelVersion4.0.0/modelVersion groupIdcom.jasneo/groupId artifactIdib/artifactId packagingwar/packaging version1.3.5/version !-- TODO project name -- namequickstart/name description/description -- View this message in context: http://www.nabble.com/Maven-Class-not-found-exception-tp21944885p21945560.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: Request for release of maven-eclipse-plugin 2.6
On Tue, Feb 10, 2009 at 11:53 PM, Martin Jäger martin.jae...@netcetera.ch wrote: Hi together The last release of maven-eclipse-plugin is from April 2008 and as I see in Jira version 2.6 is complete (taskfree). Who may I ask for a release, I'm waiting for the fix for: http://jira.codehaus.org/browse/MECLIPSE-111 I've been on it since before Christmas, but work has got in the way. Say next couple of weeks? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Dependency can't be resolved...
So there are some more differences, even though my development machine are building the same version of our project, my developer box can build the whole thing successfully, but our build server quits 75% of the way though with a PermGenSpace out of memory error. Also, our build server also misses some dependencies in the output artifacts, but my developer box bundles artifacts perfectly fine. So my build box can't build our project correctly and if I manually execute the rest of the build after the point of failure, I have invalid artifacts that are missing files... It makes me think something is screwy with the Assembly plugin or something? On Tue, Feb 10, 2009 at 6:46 PM, Ryan Moquin fragility...@gmail.com wrote: I keep getting this error when one of my subprojects builds with Maven 2.1 (the XXX represents a child module of the project): [INFO] [site:attach-descriptor] [WARNING] The dependency: XXX can't be resolved ut has been found in the reactor. This dependency has been excluded from the plugin execution. You should rerun this mojo after executing mvn i stall. What I don't understand about this error, it gives this error for modules that haven't been built yet, but aren't dependencies on the current project. Also, it says this for all but the first child project of the parent module. The first child module does not depend on any of the modules, not are they referenced from it. So if these child projects aren't referenced and are in the reactor to be built, why is it complaining? It's telling me to run mvn install, but that's what I am doing. I'm not sure exactly how to resolve this problem since it makes no sense and just came out of the blue. The other odd thing is that I'm starting the build from a parent pom which is the parent of the submodules causing me problems. If I built from the parent of the problematic child modules, they seem to build fine. If I execute my build from one level higher, then they fail with that error. All my other projects that are similarly structured, don't have this issue. It's only this one particular parent module and it's children. Also, I ran the build with the exact same project revision on my developer machine, same version of maven2 and same jdk, It built successfully. So I guess it's only our build server that's hosed. No clue why, since the same project builds fine on a different machine and depending on where the build is started. Has anyone seen this error crop up with no cause? Thanks!
Re: M2Eclipse Plugin can't resolve workspace dependency during MVN compile
On 10-Feb-09, at 5:36 PM, Lincoln Baxter, III wrote: The version must also match. If you refer to a project and the version doesn't match the version in your workspace then m2eclipse will use normal Maven resolution which is checking your local and then remote versions. Yeah the versions match :) Maven is not m2eclipse. The Maven CLI is not going to be able to build anything if you don't have it installed. The CLI and m2eclipse's operation inside Eclipse are two separate things. So when, in Eclipse, I do: Run As - Maven Build Is that invoking the CLI or is m2eclipse doing the work? If it's actually invoking the CLI, then that's the reason, but if m2eclipse is doing the work, I would expect it to find my workspace dependencies during the build. (Which it's not) When you are executing a build the default is to use the embedder and _not_ use artifacts in the workspace. You have to enable that in the run configurations. There is a toggle for that. But whether the embedded version of external version of Maven is used it's the CLI code that is called. But this only affects Maven and Maven plugins that you are working on, not your dependent projects. Maven executes as it normally would from the command line. Maven itself cannot resolve artifacts in your Eclipse workspace. Does that make sense? Thanks again, Lincoln Thanks, Jason -- Jason van Zyl Founder, Apache Maven jason at sonatype dot com -- People develop abstractions by generalizing from concrete examples. Every attempt to determine the correct abstraction on paper without actually developing a running system is doomed to failure. No one is that smart. A framework is a resuable design, so you develop it by looking at the things it is supposed to be a design of. The more examples you look at, the more general your framework will be. -- Ralph Johnson Don Roberts, Patterns for Evolving Frameworks - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
How can i execute multiple shell command in maven
Hi, I have a reqmt to execute start, stop tomcat through its shell script. How can i do this in maven? In Ant, we have exec command and i can configure targets for stop and start.I read through the usage of Exec maven plugin and configured this execution goals goalexec/goal /goals /execution /executions configuration executablestartup.bat/executable !-- optional -- workingDirectoryD:\apache-tomcat-6.0.16\bin/workingDirectory arguments/ /configuration While i'm able to do a tomcat start, i'm not sure how i can do a tomcat stop as the xml configuration doesn't seem to support multile exec commands. Rgds, Sathya
Prevent a build
Hello all, I am having two problems. The first one is I don't want to compile the classes when creating the artifact (jar). I want the source only to be there. Later on, if I need to build a whole program and wrap it in assembly, Then I would like to include only the sources. How can I do this ? The second part is going through the whole build cycle (compile, test, package. ...etc) when I do deploy. There's no need for this, as the processes takes time to recreate a package again. can this be prevent. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Ant Task - Build maven pom.xml
Hi I am also facing same problem. Have anyone found solution? Thanks regards Vikas Tim Kettler wrote: Hi, halsafar schrieb: I am trying to write an ant script to automate some maven tasks and hopefully decide not to rebuild the entire thing if it detects no changes. Just to give an idea I am working with Jasig CAS Server which has several modules all which are Maven projects. The build time is brutal on this beast and it will always rebuild no matter what it seems. So even if Ant won't help I am still stuck using Ant as I need to auto-deploy the CAS Server to both a Tomcat and Glassfish server. Now everything has been done and Maven is being run from a simple exec call in the build.xml for the ant script. I did find some Official Maven Ant Tasks jar I would like to try. However I have been unable to find any examples which actually show this maven ant tasks building a maven project. Any help? The maven ant tasks bring the dependency management features of maven to ant, they don't enable ant to build a maven project. Anyway, here [1] is the link to the official homepage containing usage instructions. -Tim [1] http://maven.apache.org/ant-tasks.html - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- View this message in context: http://www.nabble.com/Ant-Task---Build-maven-pom.xml-tp17657445p21948877.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: How can i execute multiple shell command in maven
I can't imagine why it would matter if you start and stop Tomcat through its own shell script. If you're doing so for integration testing purposes, you're probably better off using the Cargo plugin to wrap the Tomcat container. However, you can probably configure the Exec plugin to do what you want to do by binding the executions to a couple of different phases in the build lifecycle. For instance: executions execution idstartTomcat/id phasepre-integration-test/phase goals goalexec/exec /goals configuration executablestartup.bat/executable ... /configuration /execution execution idstopTomcat/id phasepost-integration-test/phase goals goalexec/exec /goals configuration executableshutdown.bat/executable ... /configuration /execution /executions One really good reason to avoid using the method you're trying to use is that it's not portable. Try to execute that on any Unix system, and it's going to choke all over itself - unless you start modifying the names of the Tomcat execution scripts. You're also depending on the scripts to be on the execution path, which is a dangerous assumption. Good luck! Dave Sathyanarayanan Nagarajan wrote: Hi, I have a reqmt to execute start, stop tomcat through its shell script. How can i do this in maven? In Ant, we have exec command and i can configure targets for stop and start.I read through the usage of Exec maven plugin and configured this execution goals goalexec/goal /goals /execution /executions configuration executablestartup.bat/executable !-- optional -- workingDirectoryD:\apache-tomcat-6.0.16\bin/workingDirectory arguments/ /configuration While i'm able to do a tomcat start, i'm not sure how i can do a tomcat stop as the xml configuration doesn't seem to support multile exec commands. Rgds, Sathya - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Aggregator pom fails, but modules work
Apologies if I was a bit brusque. Though I can't think of any reason why, I was speculating that it might involve something insidious about how the compiler or surefire expects the project structure. Different directory names help isolate the problem. Anyhow, you might have an old version of the artifact under test in your local repo. klimane wrote: I'm not quite sure what you mean by abusing 'src' and 'test'. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Resolved Version Weirdness
Thanks for the insight, Brian. The culprit might indeed be a test dependency. I'll verify this. I originally checked for missing direct dependencies, but I might have to do that again. Reinhard -Original Message- From: Brian E. Fox [mailto:bri...@reply.infinity.nu] Sent: Tuesday, February 10, 2009 2:42 PM To: Maven Users List Subject: RE: Resolved Version Weirdness Sounds to me like a classic case of not specifying your direct dependencies. Some other pom changed and introduced a transitive change breaking something you actually depend on. Run mvn dependency:analyze on your projects, if it says you are missing direct dependencies, you should fix them. Yes, dependency-plugin and jar-plugin use the same resolution -- that is core hands the artifact list over to the plugins when they start. The dependency-plugin get the test scope to start which includes everything, perhaps some test dependency you have slightly changed and is influencing the dependency tree as seen by it. -Original Message- From: Reinhard Nägele [mailto:reinhard.naeg...@mgm-tp.com] Sent: Monday, February 09, 2009 2:41 AM To: users@maven.apache.org Subject: Resolved Version Weirdness Hello, We have a multi-module project which transitively uses Commons Logging. We do not use it directly ourselves and so did not explicitly declare it as a dependency. So far, this has not been a problem. But for some reason, something must have changed over the weekend. I started our application and got a NoClassDefFoundError because org.apache.commons.logging.LogFactory was missing. I then checked the following: - Maven dependencies in Eclipse (using m2eclipse) showed commons-logging-1.1 - The dependency hierarchy and dependency:tree showed commons-logging-1.1 as the winner (amongst 1.0, 1.0.3, 1.0.4, 1.1, 1.1.1) . dependency:copy copied commons-logging-1.1.jar - The Jar plugin wrote commons-logging-1.1.1 into the manifest. So, the problem is that either the Jar plugin or the Dependency plugin is wrong. Don't they use the same mechanism in order to determine the classpath? Naturally, I would expect the latest version to win. I don't understand why this happened all of a sudden. Nothing has changed here, and all our plugin versions are locked. For now, I fixed the problem by explicitly adding commons-logging-1.1.1 as a dependency, but I don't really like this. I'd appreciate any insight into what's going on here. Thanks, Reinhard - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Ant Task - Build maven pom.xml
Hi, I thought Tim's reply didn't need any addition, but it seems that even the documentation is still not clear enough (multiple people did a lot of work on it, though...). Let's try to understand your problem, then improve the doc. Perhaps 2 examples will help us to understand each other. 1. Maven Ant Tasks have a sample.build.xml [2] to unit-test the components features As stated before, Maven Ant Tasks are not meant to really *build* a project, but only get dependencies. So you won't see in this example anything really building: only getting dependencies in multiple forms, installing an artifact into local repository and deploying to a remote repo (how the artifact installed/deployed is really build is not shown, since once again, it's not the purpose of the tasks) 2. Maven itself can be bootstrapped using Maven Ant Tasks: see build.xml in Maven Core sources [3] This time, this is really a project (Maven Core) built by Ant, getting its multiple dependencies with Maven Ant Tasks: seems to be what you want to do with your project. As you can see in the build file, most content is about building a specific project: there is only a little part that is about getting dependencies, ie the pull target (with its depends). Are these examples more clear? Regards, Hervé [2] http://svn.apache.org/viewvc/maven/ant-tasks/branches/maven-ant-tasks-2.0.x/sample.build.xml?view=markup [3] http://svn.apache.org/viewvc/maven/components/branches/maven-2.0.x/build.xml?view=markup Le mercredi 11 février 2009, vikask a écrit : Hi I am also facing same problem. Have anyone found solution? Thanks regards Vikas Tim Kettler wrote: Hi, halsafar schrieb: I am trying to write an ant script to automate some maven tasks and hopefully decide not to rebuild the entire thing if it detects no changes. Just to give an idea I am working with Jasig CAS Server which has several modules all which are Maven projects. The build time is brutal on this beast and it will always rebuild no matter what it seems. So even if Ant won't help I am still stuck using Ant as I need to auto-deploy the CAS Server to both a Tomcat and Glassfish server. Now everything has been done and Maven is being run from a simple exec call in the build.xml for the ant script. I did find some Official Maven Ant Tasks jar I would like to try. However I have been unable to find any examples which actually show this maven ant tasks building a maven project. Any help? The maven ant tasks bring the dependency management features of maven to ant, they don't enable ant to build a maven project. Anyway, here [1] is the link to the official homepage containing usage instructions. -Tim [1] http://maven.apache.org/ant-tasks.html - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
