[m2]Multi-module site aggregation
Hello! When building multiple project sites in Maven 1 there was an option to aggregate the sub-project sites in the parent modules target/site/multiproject directory. Is there a similar option in Maven 2? I have googled for it with no luck. Cheers Daniel -- __ [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to set properties during a build - build date
Hi all, In order to generate build timestamps in manifest files, I need to somehow set properties so that when copying resources, filtering replaces them in my files. So far, I see 2 possibilities: 1. Write my own Mojo/plugin (never did that before, but that would be the occasion of learning). After a quick glance at the doc, I do not see how one can make a property available outside a plugin... But again I did not investigate much... 2. Use an Ant task to set the property and make it available to Maven. The problem here is again to make the property available... Does anyone know how to achieve that ? Thanks in advance, Thierry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 1.1 RC1 SNAPSHOT needs testers
Hi! I gave this a spin with my build. I changed over to have my reports in project.xml like this reports reportmaven-pmd-plugin/report reportmaven-junit-report-plugin/report reportmaven-javadoc-plugin/report reportmaven-license-plugin/report reportmaven-changelog-plugin/report reportmaven-checkstyle-plugin/report reportmaven-file-activity-plugin/report reportmaven-jxr-plugin/report reportmaven-jdepend-plugin/report reportmaven-java-plugin/report reportmaven-linkcheck-plugin/report reportmaven-developer-activity-plugin/report reportmaven-tasklist-plugin/report reportmaven-xdoc-plugin/report reportmaven-cobertura-plugin/report /reports For some reason without the xdoc plugin my xdocs located in /xdocs were not copied. And now with the xdoc plugin i get the following error. BUILD FAILED File.. file:/C:/Documents and Settings/manfred/.maven/cache/maven-xdoc-plugin-1.10.1-SNAPSHOT/plugin.jelly Element... attainGoal Line.. 1153 Column 48 No goal [maven-xdoc-plugin:register] Total time : 4 seconds Finished at : Friday, October 13, 2006 2:52:24 PM PDT I am sure I am missing something trivial.. but what? manfred - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to unpack a zip file into a source directory
Hi,
I would like to unpack a zip file into a source directory using Maven.
What is the best way to do this? Here are the details of what I am
trying to do:
- The zip file is essentially the Dojo JavaScript library
(ajax-2006.10.10.zip ) - it simply contains JavaScript source.
- I would like to unpack this file under my project's
${basedir}/src/main/webapp/scripts.
- I don't know if it is ok to keep such artifacts in the maven local
repository, but for right now I have kept the Dojo library at
.m2/repository/dojo/ajax/2006.10.10/ajax-2006.10.10.zip
- I was playing around with the assembly:unpack goal to unpack the
library. I tried the following command but it absolutely did not work -
obviously I don't know how to use it:
mvn assembly:unpack \
-DfinalName=ajax-2006.10.10.zip \
-DoutputDirectory=${basedir}/src/main/webapp/scripts
- I would ideally like to have a goal in my pom.xml which will make it
easy to perform the unpacking, something like
mvn unpack-dojo
How can I create something equivalent to this?
Thanks for your help.
Naresh
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to unpack a zip file into a source directory
Please ignore this message. I had sent it to the mailing list without
realizing that I was not subscribed to the list. This message has
already been answered satisfactorily.
Naresh
-Original Message-
From: Naresh Bhatia [mailto:[EMAIL PROTECTED]
Sent: Saturday, October 14, 2006 11:11 AM
To: users@maven.apache.org
Subject: How to unpack a zip file into a source directory
Hi,
I would like to unpack a zip file into a source directory using Maven.
What is the best way to do this? Here are the details of what I am
trying to do:
- The zip file is essentially the Dojo JavaScript library
(ajax-2006.10.10.zip ) - it simply contains JavaScript source.
- I would like to unpack this file under my project's
${basedir}/src/main/webapp/scripts.
- I don't know if it is ok to keep such artifacts in the maven local
repository, but for right now I have kept the Dojo library at
.m2/repository/dojo/ajax/2006.10.10/ajax-2006.10.10.zip
- I was playing around with the assembly:unpack goal to unpack the
library. I tried the following command but it absolutely did not work -
obviously I don't know how to use it:
mvn assembly:unpack \
-DfinalName=ajax-2006.10.10.zip \
-DoutputDirectory=${basedir}/src/main/webapp/scripts
- I would ideally like to have a goal in my pom.xml which will make it
easy to perform the unpacking, something like
mvn unpack-dojo
How can I create something equivalent to this?
Thanks for your help.
Naresh
-
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]
XSD or DTD support for Site's XML files.
It could be nice to have an XSD or DTD file, which can be attached to each xml file use by the site plugin, since there are a lot of XML editors aware of those, It would make life easier for us, so we don't have to be remembering or looking at someone else file to understand and write XML files. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Generating aggregate JUnit reports
All, I want to generate aggregate JUnit report for all my projects. I am trying to do it via the surefire report plugin but: 1. I did not find a way to create one aggregate report for all my projects 2. I did not find a way to add a link to these reports in the site that maven creates. Is there a way to overcome these 2 problems? Thanks, Ronen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: XSD or DTD support for Site's XML files.
On 10/15/06, Manuel Ledesma [EMAIL PROTECTED] wrote: It could be nice to have an XSD or DTD file, which can be attached to each xml file use by the site plugin, since there are a lot of XML editors aware of those, It would make life easier for us, so we don't have to be remembering or looking at someone else file to understand and write XML files. There's an issue open for this: http://jira.codehaus.org/browse/MSITE-118 -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: XSD or DTD support for Site's XML files.
Thanks for the information. Wendy Smoak wrote: On 10/15/06, Manuel Ledesma [EMAIL PROTECTED] wrote: It could be nice to have an XSD or DTD file, which can be attached to each xml file use by the site plugin, since there are a lot of XML editors aware of those, It would make life easier for us, so we don't have to be remembering or looking at someone else file to understand and write XML files. There's an issue open for this: http://jira.codehaus.org/browse/MSITE-118 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] finalName not working
Doug,
thanks for your reply.
Yes that's true, Maven has no knowledge of projet A. But it knows that A
is a dependency. So it should include A as a reference in module B using
the finalName: is it completly non sens?
Moreover I found dangerous that the behavior is not the same when
building projet B alone or when building within a multimodule.
finalName is not used for the repository which is perfect. But the
finalName doesn't only effect the name of the artifact but also
references in ClassPath entry of the manifest file, references in
application.xml for EAR or references in WEB-INF/lib for web module...
Yann
Doug Douglass wrote:
Yann,
This is to be expected. When running maven in your B project, maven has no
knowledge of project A as a module to be built and referenced, only as a
dependency that needs to be retrieved from a repository and added to the
classpath.
In addition, finalName only effects the name of the artifact generated in
the target directory. If you install/deploy the same artifact it will
(should) have the standard naming of ${artifactId}-${version}. This is A
Good Thing, as it prevents ambiguity in the repository.
HTH,
Doug
On 10/12/06, Yann Albou [EMAIL PROTECTED] wrote:
Hi,
I try to use the finalName in my parent pom as following:
finalName${artifactId}/finalName (without the version number)
If I run maven from the parent pom everything works fine: all my
artifacts are generated without the version number. and also the
classpath entry of the manifest.mf file is correctly set.
For instance I get :
parent
--- A module
--- B module (with a dependency on A)
So it generates B.jar with a Manifest containning ClassPath: A.Jar
Now If I run maven from B module it generates a B.jar but with a
manifest containing ClassPath: A-1.2.1.Jar for instance.
I get exactly the same behaviour with an EAR module that generate the
application.xml = module are not generated with the correct name...
If I run maven from the parent pom then the application.xml is generated
correctly
Did I miss something ?
Yann.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] finalName not working
In the last couple of months, this same discussion has come up once or
twice. I believe someone even suggested adding another node to
dependency to allow you to change the name of the artifact when it
was brought into your project/jar/war. There might even be a JIRA
already posted as an enchancement request, something along these
lines:
dep
groupId/
artifactId/
version/
scope/
finalNameblah.jar/finalName
/dep
Ultimately, arguing over how this should work in Maven 2.0 is an
exercise in futility. Your time will be better spent convincing the
Maven Dev team to somehow make it work and add it to M2.1. You will
need a fairly strong business case to make this happen I would think,
as it seems to go against many of the Maven best practices in my mind.
Additionally... you **could** make this work today in M2.0 by using
System scope and specifying the path to the dependency as
../projectA/target/finalName.jar. But I am generally anti-system-scope
(due to various unintended consequences w/it), so please don't
complain if this screws some other things up...
Wayne
On 10/15/06, Yann Albou [EMAIL PROTECTED] wrote:
Doug,
thanks for your reply.
Yes that's true, Maven has no knowledge of projet A. But it knows that A
is a dependency. So it should include A as a reference in module B using
the finalName: is it completly non sens?
Moreover I found dangerous that the behavior is not the same when
building projet B alone or when building within a multimodule.
finalName is not used for the repository which is perfect. But the
finalName doesn't only effect the name of the artifact but also
references in ClassPath entry of the manifest file, references in
application.xml for EAR or references in WEB-INF/lib for web module...
Yann
Doug Douglass wrote:
Yann,
This is to be expected. When running maven in your B project, maven has no
knowledge of project A as a module to be built and referenced, only as a
dependency that needs to be retrieved from a repository and added to the
classpath.
In addition, finalName only effects the name of the artifact generated in
the target directory. If you install/deploy the same artifact it will
(should) have the standard naming of ${artifactId}-${version}. This is A
Good Thing, as it prevents ambiguity in the repository.
HTH,
Doug
On 10/12/06, Yann Albou [EMAIL PROTECTED] wrote:
Hi,
I try to use the finalName in my parent pom as following:
finalName${artifactId}/finalName (without the version number)
If I run maven from the parent pom everything works fine: all my
artifacts are generated without the version number. and also the
classpath entry of the manifest.mf file is correctly set.
For instance I get :
parent
--- A module
--- B module (with a dependency on A)
So it generates B.jar with a Manifest containning ClassPath: A.Jar
Now If I run maven from B module it generates a B.jar but with a
manifest containing ClassPath: A-1.2.1.Jar for instance.
I get exactly the same behaviour with an EAR module that generate the
application.xml = module are not generated with the correct name...
If I run maven from the parent pom then the application.xml is generated
correctly
Did I miss something ?
Yann.
-
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: exclude integration tests from test phase in surefire-plugin ?
Jan, maybe it's the pair of asterisks at the end of the exclude pattern. Try it with just the one. Question for you: how do you specify the different executions to run from the command line? rgds Adam Jan-Olav Eide on 12/10/06 08:44, wrote: I have a set of tests that I only want to run in the integration-test phase. These are all in in the .../integration/.. package I have the following in my pom, but the plugin still insists on running the integration tests in the test phase. What is wrong with this configuration ? plugin artifactIdmaven-surefire-plugin/artifactId executions execution idsurefire-test/id phasetest/phase goals goaltest/goal /goals configuration excludes exclude**/integration/**/exclude /excludes /configuration /execution execution idsurefire-integrationtest/id phaseintegration-test/phase goals goaltest/goal /goals configuration includes include**/integration/**/include /includes /configuration /execution /executions /plugin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: exclude integration tests from test phase in surefire-plugin ?
On 10/12/06, Jan-Olav Eide [EMAIL PROTECTED] wrote: I have a set of tests that I only want to run in the integration-test phase. These are all in in the .../integration/.. package I have the following in my pom, but the plugin still insists on running the integration tests in the test phase. What is wrong with this configuration ? Compare your pom to this one, which is working: http://svn.apache.org/repos/asf/shale/framework/trunk/shale-apps/shale-usecases/pom.xml I've started writing about this topic, but haven't had time to complete it... http://docs.codehaus.org/display/MAVENUSER/Maven+and+Integration+Testing -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: docbook plugin
On 13 Oct 2006, at 16:39, pjungwir wrote: ir. ing. Jan Dockx wrote: http://cvs.peopleware.be/training/maven/maven2/ buildLifecyclePhases.html hope this helps. Thanks. That is the best table I've seen so far. I eventually figured this out by looking here: https://svn.apache.org/repos/asf/maven/components/tags/maven-2.0.4/ maven-core/src/main/resources/META-INF/plexus/components.xml One thing I still don't understand: most of the lists out there don't mention the initialize phase. The list you posted has it, but in brackets with no description. Why is that? Because, as far as I understand, it is there only for internal reasons, and not for plugins to be used. Maven developers might confirm or deny this … Paul -- View this message in context: http://www.nabble.com/docbook-plugin- tf2408569.html#a6796874 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ** Attachment: Extremely Witty Signature.doc
settings.xml location
I am setting up profiles for various different deploy-environments / customer sites and users, storing variables for use in filtering classpath and web resources. The settings.xml that I edit extensively in m2-home/conf/ is currently not in source control and I want to ask where would be best to keep it. It would be ideal if continuum checked out the latest copy from the scm each time. however the default location in the maven installation directory is out of continuum's reach. in fact unless I kept the settings.xml in each project, then continuum is never going to check out the latest version. So it seems to me that there is no automated solution. Has anyone considered this and is there in fact a solution? Regards Adam
[ANN] Building Eclipse PDE artifact with Maven
Hello I have cooked up a Maven adapter to run Eclipse PDE headless automation build. The site is at http://mojo.codehaus.org/pde-maven-plugin/ A snapshot has been deployed. Check out live example at the site for details. Feedbacks are greatly appreciated. Enjoy. -D
Re: [ANN] Building Eclipse PDE artifact with Maven
Great, John Casey and me are working in something to build Eclipse plugins so they are still usable inside PDE GUI. On 10/15/06, Dan Tran [EMAIL PROTECTED] wrote: Hello I have cooked up a Maven adapter to run Eclipse PDE headless automation build. The site is at http://mojo.codehaus.org/pde-maven-plugin/ A snapshot has been deployed. Check out live example at the site for details. Feedbacks are greatly appreciated. Enjoy. -D -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Building Eclipse PDE artifact with Maven
Can we contribute that example to m2eclipse and have it referenced from PDE plugin? On 10/16/06, Carlos Sanchez [EMAIL PROTECTED] wrote: Great, John Casey and me are working in something to build Eclipse plugins so they are still usable inside PDE GUI. On 10/15/06, Dan Tran [EMAIL PROTECTED] wrote: Hello I have cooked up a Maven adapter to run Eclipse PDE headless automation build. The site is at http://mojo.codehaus.org/pde-maven-plugin/ A snapshot has been deployed. Check out live example at the site for details. Feedbacks are greatly appreciated. Enjoy. -D -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 1.1 RC1 SNAPSHOT needs testers
Doesn't work for me. I get a stacktrace on starting: __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.1-RC1-SNAPSHOT Directory C:\Documents and Settings\Dion Gillard\.maven\cache does not exist. At tempting to create. Plugin cache will be regenerated org.apache.maven.project.Model: method setModelEncoding(Ljava/lang/String;)V not found Exception stack traces : java.lang.NoSuchMethodError: org.apache.maven.project.Model: method setModelEnco ding(Ljava/lang/String;)V not found at org.apache.maven.project.io.dom4j.MavenDom4jReader.parseModel(MavenDo m4jReader.java:1263) at org.apache.maven.project.io.dom4j.MavenDom4jReader.read(MavenDom4jRea der.java:2617) at org.apache.maven.project.io.dom4j.MavenDom4jReader.read(MavenDom4jRea der.java:2628) at org.apache.maven.project.Project.init(Project.java:151) at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:194) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:123) at org.apache.maven.plugin.JellyScriptHousing.getProject(JellyScriptHous ing.java:109) at org.apache.maven.plugin.PluginManager.createPluginHousing(PluginManag er.java:349) at org.apache.maven.plugin.PluginManager.loadUncachedPlugins(PluginManag er.java:240) at org.apache.maven.plugin.PluginManager.initialize(PluginManager.java:3 11) at org.apache.maven.MavenSession.initializePluginManager(MavenSession.ja va:205) at org.apache.maven.MavenSession.initialize(MavenSession.java:172) at org.apache.maven.cli.App.doMain(App.java:543) at org.apache.maven.cli.App.main(App.java:1411) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:41) at java.lang.reflect.Method.invoke(Method.java:386) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) On 10/10/06, Arnaud HERITIER [EMAIL PROTECTED] wrote: Hi everybody, We just deployed a new SNAPSHOT of maven 1.1 RC1 [1]. This version incorporates 2 important changes and we would like to have your feedback : - MAVEN-1755 : We fixed the last main backward incompability with maven 1.0.x, this new version supports XML entities in the POM. - MAVEN-1789 : The default repository is now http://repo1.maven.org/maven/ ( These two issues aren't yet closed because we have to update the documentation and we are waiting for your feedback ;-) ) Be careful, that to use this snapshot version, you'll certainly have to define the following set of remote repositories to download dependencies. maven.repo.remote = http://repo1.maven.org/maven,http://people.apache.org/repo/m1-snapshot-repository/ These version includes severals plugins [4] updated since the beta 3, and particularly the fix for MPARTIFACT-71 to avoid the error about the rejected key of the host if you use the scp or the sftp protocols to deploy your artifacts. The more feedbacks we'll have, the more stable will be the RC1 !! Thanks for your help... Cheers, The maven team. [1] http://people.apache.org/repo/m1-snapshot-repository/maven/distributions/20061009/ [2] http://jira.codehaus.org/browse/MAVEN-1755 [3] http://jira.codehaus.org/browse/MAVEN-1789 [4] http://jira.codehaus.org/browse/MAVEN-1769 -- http://www.multitask.com.au/people/dion/ Rule of Acquisition #91: Hear all, trust nothing. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 1.1 RC1 SNAPSHOT needs testers
Looks like a bad cache/install. I reinstalled, removing the cache and maven directory in the repo and this error went away. On 10/16/06, Dion Gillard [EMAIL PROTECTED] wrote: Doesn't work for me. I get a stacktrace on starting: __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.1-RC1-SNAPSHOT Directory C:\Documents and Settings\Dion Gillard\.maven\cache does not exist. At tempting to create. Plugin cache will be regenerated org.apache.maven.project.Model: method setModelEncoding(Ljava/lang/String;)V not found Exception stack traces : java.lang.NoSuchMethodError: org.apache.maven.project.Model: method setModelEnco ding(Ljava/lang/String;)V not found at org.apache.maven.project.io.dom4j.MavenDom4jReader.parseModel(MavenDo m4jReader.java:1263) at org.apache.maven.project.io.dom4j.MavenDom4jReader.read(MavenDom4jRea der.java:2617) at org.apache.maven.project.io.dom4j.MavenDom4jReader.read(MavenDom4jRea der.java:2628) at org.apache.maven.project.Project.init(Project.java:151) at org.apache.maven.MavenUtils.getNonJellyProject(MavenUtils.java:194) at org.apache.maven.MavenUtils.getProject(MavenUtils.java:123) at org.apache.maven.plugin.JellyScriptHousing.getProject(JellyScriptHous ing.java:109) at org.apache.maven.plugin.PluginManager.createPluginHousing(PluginManag er.java:349) at org.apache.maven.plugin.PluginManager.loadUncachedPlugins(PluginManag er.java:240) at org.apache.maven.plugin.PluginManager.initialize(PluginManager.java:3 11) at org.apache.maven.MavenSession.initializePluginManager(MavenSession.ja va:205) at org.apache.maven.MavenSession.initialize(MavenSession.java:172) at org.apache.maven.cli.App.doMain(App.java:543) at org.apache.maven.cli.App.main(App.java:1411) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl. java:79) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAcces sorImpl.java:41) at java.lang.reflect.Method.invoke(Method.java:386) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) On 10/10/06, Arnaud HERITIER [EMAIL PROTECTED] wrote: Hi everybody, We just deployed a new SNAPSHOT of maven 1.1 RC1 [1]. This version incorporates 2 important changes and we would like to have your feedback : - MAVEN-1755 : We fixed the last main backward incompability with maven 1.0.x, this new version supports XML entities in the POM. - MAVEN-1789 : The default repository is now http://repo1.maven.org/maven/ ( These two issues aren't yet closed because we have to update the documentation and we are waiting for your feedback ;-) ) Be careful, that to use this snapshot version, you'll certainly have to define the following set of remote repositories to download dependencies. maven.repo.remote = http://repo1.maven.org/maven,http://people.apache.org/repo/m1-snapshot-repository/ These version includes severals plugins [4] updated since the beta 3, and particularly the fix for MPARTIFACT-71 to avoid the error about the rejected key of the host if you use the scp or the sftp protocols to deploy your artifacts. The more feedbacks we'll have, the more stable will be the RC1 !! Thanks for your help... Cheers, The maven team. [1] http://people.apache.org/repo/m1-snapshot-repository/maven/distributions/20061009/ [2] http://jira.codehaus.org/browse/MAVEN-1755 [3] http://jira.codehaus.org/browse/MAVEN-1789 [4] http://jira.codehaus.org/browse/MAVEN-1769 -- http://www.multitask.com.au/people/dion/ Rule of Acquisition #91: Hear all, trust nothing. -- http://www.multitask.com.au/people/dion/ Rule of Acquisition #91: Hear all, trust nothing. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Building Eclipse PDE artifact with Maven
That would be great. -D On 10/15/06, Carlos Sanchez [EMAIL PROTECTED] wrote: Can we contribute that example to m2eclipse and have it referenced from PDE plugin? On 10/16/06, Carlos Sanchez [EMAIL PROTECTED] wrote: Great, John Casey and me are working in something to build Eclipse plugins so they are still usable inside PDE GUI. On 10/15/06, Dan Tran [EMAIL PROTECTED] wrote: Hello I have cooked up a Maven adapter to run Eclipse PDE headless automation build. The site is at http://mojo.codehaus.org/pde-maven-plugin/ A snapshot has been deployed. Check out live example at the site for details. Feedbacks are greatly appreciated. Enjoy. -D -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [ANN] Building Eclipse PDE artifact with Maven
Thanks Dear. I really appreciate your help / efforts towards this. -Original Message- From: Dan Tran [mailto:[EMAIL PROTECTED] Sent: Monday, October 16, 2006 3:01 AM To: Maven Users List Subject: [ANN] Building Eclipse PDE artifact with Maven Hello I have cooked up a Maven adapter to run Eclipse PDE headless automation build. The site is at http://mojo.codehaus.org/pde-maven-plugin/ A snapshot has been deployed. Check out live example at the site for details. Feedbacks are greatly appreciated. Enjoy. -D - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
AW: [M2- MVN Deploy Problem Error Code 201]
Hi,
now I get this, but I can make nothing of it :-)
Here is my stacktrace:
[INFO] [deploy:deploy]
[INFO] Retrieving previous build number from QIR
[DEBUG] repository metadata for: 'snapshot xx.yy:zz:1.0.0-SNAPSHOT' could not
be found on repository: QIR
[DEBUG] not adding permissions to wagon connection
Uploading:
http://{myHost}/xx/yy/zz/1.0.0-SNAPSHOT/zz-1.0.0-20061016.051508-1.jar
25K uploaded
[INFO]
[ERROR] BUILD ERROR
[INFO]
[INFO] Error deploying artifact: Unable to transfer file. HttpURLConnection
returned the response code: 201
[INFO]
[DEBUG] Trace
org.apache.maven.lifecycle.LifecycleExecutionException: Error deploying
artifact: Unable to transfer file. HttpURLConnection retur
ned the response code: 201
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:559)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalWithLifecycle(DefaultLifecycleExecutor.java:475)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:454)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandleFailures(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:273)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:140)
at org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
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)
Caused by: org.apache.maven.plugin.MojoExecutionException: Error deploying
artifact: Unable to transfer file. HttpURLConnection re
turned the response code: 201
at
org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:145)
at
org.apache.maven.plugin.DefaultPluginManager.executeMojo(DefaultPluginManager.java:412)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(DefaultLifecycleExecutor.java:534)
... 16 more
Caused by: org.apache.maven.artifact.deployer.ArtifactDeploymentException:
Error deploying artifact: Unable to transfer file. Http
URLConnection returned the response code: 201
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:91)
at
org.apache.maven.plugin.deploy.DeployMojo.execute(DeployMojo.java:133)
... 18 more
Caused by: org.apache.maven.wagon.TransferFailedException: Unable to transfer
file. HttpURLConnection returned the response code:
201
at
org.apache.maven.wagon.providers.http.LightweightHttpWagon.put(LightweightHttpWagon.java:143)
at
org.apache.maven.artifact.manager.DefaultWagonManager.putRemoteFile(DefaultWagonManager.java:180)
at
org.apache.maven.artifact.manager.DefaultWagonManager.putArtifact(DefaultWagonManager.java:109)
at
org.apache.maven.artifact.deployer.DefaultArtifactDeployer.deploy(DefaultArtifactDeployer.java:77)
... 19 more
[INFO]
[INFO] Total time: 14 seconds
[INFO] Finished at: Mon Oct 16 07:15:19 CEST 2006
[INFO] Final Memory: 5M/9M
[INFO]
Sebastian
-Ursprüngliche Nachricht-
Von: Wayne Fay [mailto:[EMAIL PROTECTED]
Gesendet: Freitag, 13. Oktober 2006 16:45
An: Maven Users List
Betreff: Re: [M2- MVN Deploy Problem Error Code 201]
Try it again using mvn -X for additional debugging information that
might be useful.
Wayne
On 10/13/06, Sebastian Krebs [EMAIL PROTECTED] wrote:
Hi together,
I've got the following problem using M2.0.4
I want to deploy an artefact into my remote repository using mvn deploy.
Normally, or as I had understood, M2 will deploy the resulting jar and
the needed *.pom files.
When I'm calling mvn deploy, M2 only copies the resulting jar into my
repo.
After copying, M2 results in an error code of 201.
So M2 don't copy the other needed files, so further projects will not
