Re: [ANN] Maven Project Info Reports Plugin 2.2 Released
We've got the same problem in our enterprise pom. I just ran mvn dependency:resolve-plugins and discovered that there are many different versions of doxia that output: [dependency:resolve] Plugin Resolved: findbugs-maven-plugin-2.3.1.jar Plugin Dependency Resolved: maven-reporting-impl-2.0.jar Plugin Dependency Resolved: maven-reporting-api-2.0.8.jar Plugin Dependency Resolved: maven-doxia-tools-1.0.jar Plugin Dependency Resolved: findbugs-ant-1.3.9.jar Plugin Dependency Resolved: plastic-1.2.0.jar Plugin Dependency Resolved: gmaven-mojo-1.0-rc-3.jar Plugin Dependency Resolved: plexus-resources-1.0-alpha-4.jar Plugin Dependency Resolved: plexus-utils-1.5.1.jar Plugin Resolved: clirr-maven-plugin-2.2.2.jar Plugin Dependency Resolved: clirr-core-0.6.jar Plugin Dependency Resolved: bcel-5.2.jar Plugin Dependency Resolved: doxia-site-renderer-1.0-alpha-8.jar Plugin Dependency Resolved: maven-reporting-impl-2.0.4.jar Plugin Dependency Resolved: maven-artifact-manager-2.0.4.jar Plugin Dependency Resolved: plexus-i18n-1.0-beta-6.jar Plugin Resolved: maven-pmd-plugin-2.5.jar Plugin Dependency Resolved: maven-model-2.0.6.jar Plugin Dependency Resolved: maven-plugin-api-2.0.6.jar Plugin Dependency Resolved: maven-project-2.0.6.jar Plugin Dependency Resolved: maven-reporting-api-2.0.6.jar Plugin Dependency Resolved: maven-reporting-impl-2.0.4.3.jar Plugin Dependency Resolved: doxia-sink-api-1.0.jar Plugin Dependency Resolved: doxia-decoration-model-1.0.jar Plugin Dependency Resolved: doxia-site-renderer-1.0.jar Plugin Dependency Resolved: plexus-resources-1.0-alpha-7.jar Plugin Dependency Resolved: plexus-utils-1.5.6.jar Plugin Dependency Resolved: pmd-jdk14-4.2.5.jar Plugin Dependency Resolved: xmlParserAPIs-2.6.2.jar Plugin Resolved: maven-surefire-report-plugin-2.5.jar Plugin Dependency Resolved: maven-project-2.0.6.jar Plugin Dependency Resolved: maven-model-2.0.6.jar Plugin Dependency Resolved: maven-plugin-api-2.0.6.jar Plugin Dependency Resolved: maven-reporting-api-2.0.6.jar Plugin Dependency Resolved: maven-reporting-impl-2.0.4.3.jar Plugin Dependency Resolved: doxia-sink-api-1.0.jar Plugin Dependency Resolved: doxia-decoration-model-1.0.jar Plugin Dependency Resolved: doxia-site-renderer-1.0.jar Plugin Dependency Resolved: plexus-container-default-1.0-alpha-9.jar Plugin Dependency Resolved: plexus-utils-1.5.9.jar Plugin Resolved: cobertura-maven-plugin-2.4.jar Plugin Dependency Resolved: cobertura-1.9.4.1.jar Plugin Dependency Resolved: cobertura-runtime-1.9.4.1.pom Plugin Dependency Resolved: java-getopt-1.0.9.jar Plugin Dependency Resolved: maven-artifact-2.0.jar Plugin Dependency Resolved: maven-plugin-api-2.0.jar Plugin Dependency Resolved: maven-reporting-api-2.0.jar Plugin Dependency Resolved: maven-project-2.0.jar Plugin Dependency Resolved: maven-reporting-impl-2.0.jar Plugin Dependency Resolved: plexus-container-default-1.0-alpha-9.jar Plugin Dependency Resolved: commons-lang-2.4.jar Plugin Dependency Resolved: plexus-utils-2.0.2.jar Plugin Resolved: jdepend-maven-plugin-2.0-beta-2.jar Plugin Dependency Resolved: maven-reporting-api-2.0.jar Plugin Dependency Resolved: maven-reporting-impl-2.0.jar Plugin Dependency Resolved: jdepend-2.9.1.jar Plugin Resolved: javancss-maven-plugin-2.0.jar Plugin Dependency Resolved: plexus-utils-1.5.9.jar Plugin Dependency Resolved: maven-project-2.0.jar Plugin Dependency Resolved: maven-model-2.0.jar Plugin Dependency Resolved: maven-plugin-api-2.0.jar Plugin Dependency Resolved: maven-reporting-api-2.0.jar Plugin Dependency Resolved: doxia-sink-api-1.0-alpha-4.jar Plugin Dependency Resolved: doxia-core-1.0-alpha-4.jar Plugin Dependency Resolved: dom4j-1.6.1.jar Plugin Dependency Resolved: jaxen-1.1-beta-6.jar Plugin Dependency Resolved: maven-reporting-impl-2.0.jar Plugin Dependency Resolved: javancss-32.53.jar Plugin Resolved: maven-pmd-plugin-2.5.jar Plugin Dependency Resolved: maven-model-2.0.6.jar Plugin Dependency Resolved: maven-plugin-api-2.0.6.jar Plugin Dependency Resolved: maven-project-2.0.6.jar Plugin Dependency Resolved: maven-reporting-api-2.0.6.jar Plugin Dependency Resolved: maven-reporting-impl-2.0.4.3.jar Plugin Dependency Resolved: doxia-sink-api-1.0.jar Plugin Dependency Resolved: doxia-decoration-model-1.0.jar Plugin Dependency Resolved: doxia-site-renderer-1.0.jar Plugin Dependency Resolved: plexus-resources-1.0-alpha-7.jar Plugin Dependency Resolved: plexus-utils-1.5.6.jar Plugin Dependency Resolved: pmd-jdk14-4.2.5.jar Plugin Dependency Resolved: xmlParserAPIs-2.6.2.jar Plugin Resolved: maven-site-plugin-2.1.jar Plugin Dependency Resolved: maven-artifact-2.0.6.jar Plugin Dependency Resolved: maven-artifact-manager-2.0.6.jar Plugin Dependency
Re: lock down plugin versions in enterprise poms?
Thanks all, we know where to go from here! On Tue, May 4, 2010 at 6:03 PM, Jesse Farinacci jie...@gmail.com wrote: Hi Ravi, On Tue, May 4, 2010 at 7:01 PM, Ravi Luthra cod...@gmail.com wrote: I've heard that locking down the plugin version is a bad practice mostly because of major versions of Maven being released. Is this really a bad practice? Not only is it a best practice, but there is support for you to ensure you've done your job well[1] as well as locate new versions of plugins for you to upgrade onto. [1] http://maven.apache.org/enforcer/enforcer-rules/requirePluginVersions.html [2] http://mojo.codehaus.org/versions-maven-plugin/display-plugin-updates-mojo.html What consequences would we face if we locked down our versions and upgraded them on our own, rather than allowing Maven to choose for us? The only consequence would be that you'd not pick up any critical plugin updates due to bad plugins, but I'm not very convinced by this. Usually monitoring for [ANN] on maven-users is sufficient to keep abreast of changes. -Jesse -- There are 10 types of people in this world, those that can read binary and those that can not. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
lock down plugin versions in enterprise poms?
At our company we maintain a top-level enterprise pom that all projects inherit. We're considering adding versions to lock down our plugin versions. What we are trying to avoid is having our build break because of a third-party plugin upgrading on us unexpectedly. I've heard that locking down the plugin version is a bad practice mostly because of major versions of Maven being released. Is this really a bad practice? What consequences would we face if we locked down our versions and upgraded them on our own, rather than allowing Maven to choose for us? Thanks, Ravi
Re: [ANN] Maven Javadoc Plugin 2.6 Released
Any word on the release date of 2.6.1, all of our builds in Hudson failed this weekend upon the release of 2.6. Thank you though for your work on this, I know its terrible to put in all the effort improving all of our lives and get bitten by it by random people like me. Thanks, Ravi On Fri, Jul 31, 2009 at 2:40 AM, Vincent Siveton vsive...@apache.orgwrote: The Maven team is pleased to announce the release of the Maven Javadoc Plugin, version 2.6. The Maven Javadoc Plugin is a plugin that uses the javadoc tool for generating javadocs for the specified project. http://maven.apache.org/plugins/maven-javadoc-plugin/ You should specify the version in your project's plugin configuration: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-javadoc-plugin/artifactId version2.6/version /plugin Release Notes - Maven 2.x Javadoc Plugin - Version 2.6 ** Sub-task * [MJAVADOC-239] - Helpfile loaded from classpath ** Bug * [MJAVADOC-181] - Javadoc report not generated for multi-module project if run from parent level. * [MJAVADOC-215] - warning proxyHost' is deprecated since 2.4 * [MJAVADOC-219] - skip parameter is ignored in aggregate goal * [MJAVADOC-220] - ArrayIndexOutOfBoundsException in JavadocUtil.getIncludedFiles * [MJAVADOC-230] - aggregate report requires to have aggregate=true configuration parameter * [MJAVADOC-231] - tagletpath does not seem to work * [MJAVADOC-232] - copied doc-files folder contains svn meta files * [MJAVADOC-238] - No timeout set for URLConnection which can cause build to get stuck ** Improvement * [MJAVADOC-216] - Stylesheet file loaded from classpath * [MJAVADOC-222] - Documentation Issues * [MJAVADOC-225] - The plugin should be able to generate a jar of the aggregated javadoc * [MJAVADOC-226] - Add a new goal to fix Javadoc tags * [MJAVADOC-240] - Add default Javadoc link depending the values of maven-compiler-plugin configuration ** New Feature * [MJAVADOC-97] - enable internal/external dependency references as links ** Task * [MJAVADOC-217] - Update Aggregating Javadocs example Enjoy, -The Maven team - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [PLEASE TEST] Maven 2.0.10-RC11
Yes it was inside Hudson. I just tested in Netbeans using external Maven, and the warnings are not there. On Thu, Aug 28, 2008 at 7:37 AM, John Casey [EMAIL PROTECTED] wrote: Are you running this build in hudson, or in some sort of modified maven environment? Ravi Luthra wrote: I don't know what this means: [WARNING] WARNING This Maven runtime contains a LifecycleExecutor component with an incomplete configuration. LifecycleExecutor class: org.apache.maven.lifecycle.LifecycleExecutorInterceptor Missing component requirement: org.apache.maven.project.MavenProjectBuilder [WARNING] WARNING This Maven runtime contains a LifecycleExecutor component with an incomplete configuration. LifecycleExecutor class: org.apache.maven.lifecycle.LifecycleExecutorInterceptor Missing component requirement: org.apache.maven.project.interpolation.ModelInterpolator But I get that on all my builds. Is there some POM problem this could indicate? On Mon, Aug 25, 2008 at 1:15 PM, John Casey [EMAIL PROTECTED] wrote: Hi again, One bug was identified in 2.0.10-RC10 last Friday night. This release candidate addresses that issue. You can find it here: http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC11/org/apache/maven/apache-maven/2.0.10-RC11/http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC11/org/apache/maven/apache-maven/2.0.10-RC11/ http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC11/org/apache/maven/apache-maven/2.0.10-RC11/ Please give this a spin when you get a chance, and let us know if you find any problems. We'll file any issues in JIRA against version 2.0.10 for tracking purposes, and to give us a JIRA # to use when writing the integration test to verify the fix. Thanks, -john -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [PLEASE TEST] Maven 2.0.10-RC11
I don't know what this means: [WARNING] WARNING This Maven runtime contains a LifecycleExecutor component with an incomplete configuration. LifecycleExecutor class: org.apache.maven.lifecycle.LifecycleExecutorInterceptor Missing component requirement: org.apache.maven.project.MavenProjectBuilder [WARNING] WARNING This Maven runtime contains a LifecycleExecutor component with an incomplete configuration. LifecycleExecutor class: org.apache.maven.lifecycle.LifecycleExecutorInterceptor Missing component requirement: org.apache.maven.project.interpolation.ModelInterpolator But I get that on all my builds. Is there some POM problem this could indicate? On Mon, Aug 25, 2008 at 1:15 PM, John Casey [EMAIL PROTECTED] wrote: Hi again, One bug was identified in 2.0.10-RC10 last Friday night. This release candidate addresses that issue. You can find it here: http://people.apache.org/~jdcasey/stage/apache-maven/2.0.10-RC11/org/apache/maven/apache-maven/2.0.10-RC11/http://people.apache.org/%7Ejdcasey/stage/apache-maven/2.0.10-RC11/org/apache/maven/apache-maven/2.0.10-RC11/ Please give this a spin when you get a chance, and let us know if you find any problems. We'll file any issues in JIRA against version 2.0.10 for tracking purposes, and to give us a JIRA # to use when writing the integration test to verify the fix. Thanks, -john -- John Casey Developer, PMC Member - Apache Maven (http://maven.apache.org) Blog: http://www.ejlife.net/blogs/buildchimp/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Profile activation by time range?
Does anyone know how to activate a profile in maven if the time is between a certain hour of the day? I'm using a CI to build during every checkin, which also deploys the code. However the build server does the entire site generation and has about 10 plugins connected to it, This makes our builds very slow on the server. What I want to do is only do the site build at midnight. The only problem is our CI server (hudson) doesn't let you specify different run options for different times of the day. (at least when using Maven integration mode). What I want to do is have Maven activate the profile based on the time of day, so that Hudson doesn't have to know about it. I had a bunch of thoughts on this: 1) Create a separate process that drops a file onto the system only between 11:50pm and 12:10am. Have the profile containing the site plugin configuration activate based on this file existing. 2) OR I could create a maven plugin that runs first, and if it is between a certain time range, activate other profiles during that same build. (not sure how to do this) 3) Request an enhancement to Maven devs to support time based profile activation. Any of these feasible? Thanks, Ravi - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Debugging Maven in Netbeans
I get the same Exception when I try to set a main class in the properties of a project. Almost all of the projects I open are not created from the archetype, but custom edited. Same configuration too 5.5.1 and latest Mevenide listed on the Mevenide 2 website. I actually upgraded from 5.5 to see if this problem would go away. It didn't.. Should I upgrade to 6.0? Ravi On 9/5/07, Milos Kleint [EMAIL PROTECTED] wrote: I've checked the stacktrace and it's not clear to me how a NPE could get there. Does it happen for you all the time? can you try on a sample quickstart project created from archetype? I'm personally using Nb 6.0 + mevenide 3.0.x (close to what ships on netbeans AU for milestone 10) and use this feature occationally. This code is almost the same. Not sure if pasting the pom snippet is enough. an assempty descriptor is also generated and you might be missing that one tool. Maybe I can send you a zipped sample project privately? Milos On 9/5/07, Demian Mrakovich [EMAIL PROTECTED] wrote: Now, that would be great - if it worked. When trying this in Netbeans 5.5.1, Maven 2 project support 2.3.4: java.lang.NullPointerException at org.codehaus.mevenide.netbeans.customizer.RunJarPanel.checkAssemblyPlugin(RunJarPanel.java:337) at org.codehaus.mevenide.netbeans.customizer.RunJarPanel.applyChanges(RunJarPanel.java:274) at org.codehaus.mevenide.netbeans.customizer.CustomizerProviderImpl$OptionListener.actionPerformed(CustomizerProviderImpl.java:236) at org.netbeans.modules.project.uiapi.CustomizerDialog$OptionListener.actionPerformed(CustomizerDialog.java:162) at javax.swing.AbstractButton.fireActionPerformed(AbstractButton.java:1849) .. Anyone care to share the actual XML for pom.xml? Milos Kleint wrote: that's in project's popup menu. last item on the list.. Properties.. there in Run tab, you set the main class. Milos On 8/28/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hi, I have opened few maven project. I use NB6 Ms10 with external maven build enabled. The maven version I have is 2.0.7. I am able to compile( mvn install) the project. Now when I try to execute the same I get the following message. In order to run the project, Netbeans needs a custom profile in your pom.xml . To create and customise the profile, go to the project's Properties dialog and update the Run Panel. I can see profiles tag in settings.xml but nothing in pom.xml. Any help appretiated. I want to run the programs in debug mode to understand what happens. Thanks Regards, Jayaram -- View this message in context: http://www.nabble.com/Debugging-Maven-in-Netbeans-tf4341676s177.html#a12495884 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Hudson
I use Hudson mainly because the interface is very awesome. The AJAX controls make the process very nice. Also setting up Hudson is literally automatic. Just save the war file in Tomcat's webapps directory. So easy. Software is getting easier and easier to install. I can't wait till we are back to the days of DOS like install (copy and run). Ravi On 7/6/07, Gregory Kick [EMAIL PROTECTED] wrote: I've used hudson and have been very happy with it. In my opinion, the biggest advantage over other CI servers is the ridiculously quick turn-around on bug fixes and requested enhancements. Kohsuke pushes out releases faster than anyone I've ever seen... On 7/6/07, Wendy Smoak [EMAIL PROTECTED] wrote: On 7/6/07, Milos Kleint [EMAIL PROTECTED] wrote: Like define a unique local repo for the project, to prevent local repository cross-pollination by other maven projects built on the same machine. FWIW, I haven't tried it yet, but you should be able to do that fairly easily with Continuum by adding -Dmaven.repo.local=/path/to/separate/repo to the arguments. Or even -s /path/to/alt-settings.xml if you want completely different settings. (I went through an exercise recently trying to figure out how to make sure official builds don't use anything in the 'sandbox' repository, but only the approved third-party artifacts.) -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Gregory Kick http://kickstyle.net/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven embedder examples
I want to use the Maven Embedder but I am having trouble with the online example. The dependencies I have on my project are: dependency groupIdorg.apache.maven/groupId artifactIdmaven-core/artifactId version2.0.7/version /dependency dependency groupIdorg.apache.maven/groupId artifactIdmaven-project/artifactId version2.0.7/version /dependency dependency groupIdorg.apache.maven/groupId artifactIdmaven-embedder/artifactId version2.0.4/version /dependency The example code seems to have classes that no longer exist I think. I don't know exactly what dependencies are supposed to be used for that example anyway, they are not documented. Any help?
Re: WSDL2Java execution failed
If these artifacts are already in the main remote repository you didn't even
need to touch jar/pom files relating to those artifacts. You're
misunderstanding something.
.m2\repository\javax.activation and .m2\repository\javax.mail directories
should be removed if you made them by hand.
However don't erase anything else.
Ravi
On 5/29/07, xiaojie han [EMAIL PROTECTED] wrote:
at first, I just went to
http://repo1.maven.org/maven2/javax/activation/activation/1.1/
and
http://repo1.maven.org/maven2/javax/mail/mail/1.4/
download .jar and pom.xml to the local repository.
mvn install failed.
I deleted javax folder to follow the instruction using
C:\maven-2.0.5\sample code\Code_Ch04\daytradermvn install:install-file
-Dfile=pom.xml -DgroupId=javax.activation
-DartifactId=activation -Dversion=1.1 -Dpackaging=jar
and
C:\maven-2.0.5\sample code\Code_Ch04\daytradermvn install:install-file
-Dfile=pom.xml -DgroupId=javax.mail -DartifactId=mail
-Dversion=1.4 -Dpackaging=jar
successfully download the two jar file to
.m2\repository\javax\activation
and .m2\repository\javax\mail folder. however the command mvn install
still failed and error messages are the same as before.
**
C:\maven-2.0.5\sample code\Code_Ch04\daytrader\wsappclientmvn install
[INFO] Scanning for projects...
[INFO]
[INFO] Building DayTrader :: WS Application Client
[INFO]task-segment: [install]
[INFO]
Downloading:
http://repo1.maven.org/maven2/javax/activation/activation/1.1/activ
ation-1.1.pom
1K downloaded
Downloading:
http://repo1.maven.org/maven2/javax/mail/mail/1.4/mail-1.4.pom
993b downloaded
[INFO] [axistools:wsdl2java {execution: default}]
[INFO] about to add compile source root
[INFO] processing wsdl: C:\maven-2.0.5\sample
code\Code_Ch04\daytrader\wsappclient\src\main\resources\
META-INF\wsdl\TradeServices.wsdl
May 29, 2007 9:56:18 AM org.apache.axis.utils.JavaUtils
isAttachmentSupported
WARNING: Unable to find required classes (
javax.activation.DataHandler and javax.mail.internet.MimeMultipart).
Attachment support is disabled.
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] error executing plugin
Embedded error: WSDL2Java execution failed
unknown protocol: c
[INFO]
[INFO] For more information, run Maven with the -e switch
[INFO]
[INFO] Total time: 4 seconds
[INFO] Finished at: Tue May 29 09:56:18 CDT 2007
[INFO] Final Memory: 5M/10M
[INFO]
**
is there anything else I missed?
thanks.
--- Thorsten Heit [EMAIL PROTECTED] wrote:
Hi,
I tried to build chapter4 daytrader example by manually adding
javax.mail and javax.activation jar to the local repository as
[..]\.m2\repository\javax\mail\mail\1.4\mail-1.4.jar
and
[..]\.m2\repository\javax\activation\activation\1.1\activation-1.1.jar
However, it still said unable to find required classes.
How did you add those files to your repository? By manual copying or
via mvn install:install-file / mvn deploy:deploy-file?
Have you read http://maven.apache.org/guides/mini/guide-coping-with-
sun-jars.html?
HTH
Thorsten
Fussy?
Opinionated? Impossible to please? Perfect. Join Yahoo!'s user panel and
lay it on us. http://surveylink.yahoo.com/gmrs/yahoo_panel_invite.asp?a=7
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Creating a Repository in weblogic server
Here is a web application we use as our companies internal repository. It doubles as an open source cache too: http://proximity.abstracthorizon.org/ On 5/15/07, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote: Hello, I want to create my own repository in my weblogic server like http://localhost:7001/maven/repository Can some one suggest how to get this?Do I need to define a web application to get this done Regards Jaish - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: A beginner´s question
It isn't always a bad thing to just check in changes no matter what. I mean you still benefit from Maven's versioning so if you find yourself barking up the wrong tree with a bunch of bad commits, your users will still be happy using the stable or earlier versions of your code. The nice thing about Maven is that to get something deployed, even snapshots, it must compile and pass tests too. If anything Maven makes using source code repositories even easier because it decouples the requirement of making sure the build ALWAYS works from the source repository and other projects using the outputting artifact. Essentially Maven fills in the missing artifact repository that developers have always needed. Ravi On 5/15/07, Siegmann Daniel, NY [EMAIL PROTECTED] wrote: Thanks for the answer. So you think the best way is to let developers commit manually and use the integration Server to make the builds once the SCM repository has change and inform in case of error? I expect that your developers will sometimes wish to run the unit tests without committing the changes. Therefore having the commit be automatic is undesirable. Heck, I have occasionally deployed a snapshot from my machine before committing changes. If you want to commit after running tests, just execute mvn test scm:checkin. However, I am strongly of the believe that developers should test changes on their own machine before committing to the repository. Having CI does not make it OK to break the build! CI simply allows mistakes to be caught sooner rather than later (probably the most common IME is forgetting to add files to the repository before committing). -- Daniel Siegmann FJA-US, Inc. 512 Seventh Ave., New York, NY 10018 (212) 840-2618 ext. 139 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Extra directory level being created by Assembly in Maven 2.0.6, as compared with 2.0.4
I reported this to Mevenide and should be fixed in future versions. A work around is to lock down the assembly version you are using: ... plugin artifactIdmaven-assembly-plugin/artifactId version2.1/version executions ... Maven does not require all artifact-specifying attributes for plugins like it does with normal dependencies. Whether the beta version of the assembly plugin is a bug or not, remains to be seen. It could simply be a side effect of configuration changes. And by not providing it with its required configuration, it does this. I hope they will fix automatic plugin resolution to exclude beta editions somehow. Ravi [EMAIL PROTECTED] wrote on 05/11/2007 11:47:50 AM: On 5/5/07, Marshall Schor [EMAIL PROTECTED] wrote: snip/ However, if the same XML is used with Maven 2.0.6, an extra directory is created having the name of the packed zip source: root / eclipsePlugins / uimaj-ep-debug-2.1.0-incubating.zip / org.apache.uima.debug.2.1.0.incubating / etc. extra directory ** Is this a bug, or do we need to change something when moving to 2.0.6? Did the version of assembly plugin change when moving from Maven 2.0.4 to 2.0.6? I think I may have traced this problem back to version 2.2-beta1 of the Maven assembly plugin. It appears to create these extra directories when unpacking zip files from dependencySets, whereas version 2.1 did not. Does anyone know if this is an expected change in behavior of the assembly plugin, or a bug? -Adam - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Embedder for normal application use?
Does anyone have any code that demonstrates using the MavenEmbedder to read the classpath for /META-INF/maven/path/to/pom.xml to expand all dependencies, download if necessary and modify the classpath such that an application can run without copying Jars everywhere. In other words, I want to keep the Jars in the user's .m2 folder and still run an application from anywhere. I don't know if this is possible, but it would be useful. An even more useful one would be a hard-coded class to copy and paste in a project that does some initial loading of the standard maven jars -then once it gets enough maven, do the rest of the Pom processing. So in other words if I was handed a Jar as an application, it would automatically install Maven2, download Maven2 to the local repository, then process the internal POM of that original jar, such that all dependencies get added to the classpath, and as a final step, run some psvm method specified somewhere. Maybe I'm talking about Maven v3, but this would be cool.
