RE: problems with Maven 1.1 -beta-1 in defining entities in project.xml
Andy Glick wrote on Saturday, September 10, 2005 4:10 AM: Marco, When I executed maven pom:validate on your project.xml file I found 2 lines that the Modello generated parser rejected. 1) Maven 1.1 no longer supports XML entities as a means of including XML fragments This is a complete show-stopper for Maven 1.1 for us. We make heavily use of XML entities for all kind of information in the POMs and we use company wide system entities and entitiy overload mechanism. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: problems with Maven 1.1 -beta-1 in defining entities in project.xml
http://jira.codehaus.org/browse/MODELLO-18 when this is fixed it will be possible (however, it will be a non-default option) - Brett On 9/12/05, Jörg Schaible [EMAIL PROTECTED] wrote: Andy Glick wrote on Saturday, September 10, 2005 4:10 AM: Marco, When I executed maven pom:validate on your project.xml file I found 2 lines that the Modello generated parser rejected. 1) Maven 1.1 no longer supports XML entities as a means of including XML fragments This is a complete show-stopper for Maven 1.1 for us. We make heavily use of XML entities for all kind of information in the POMs and we use company wide system entities and entitiy overload mechanism. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: problems with Maven 1.1 -beta-1 in defining entities in project.xml
Hi Brett, Brett Porter wrote on Monday, September 12, 2005 8:46 AM: http://jira.codehaus.org/browse/MODELLO-18 when this is fixed it will be possible (however, it will be a non-default option) that will be good. I followed the discussion for M2 close enough, to be quite sure, that we can do with M2 what we currently do with M1 entitites. But for M1.x we're stuck and need a way to enable system entities. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] Torque plugin?
Hi, you can generate a sample mojo using the archetype plugin, this can be treated as your additional reference for creating plugin just execute on your command line m2 archetype:create -DgroupId=your_groupId -DartifactId=your_artifactId -DarchetypeArtifactId=maven-archetype-mojo you can also read http://maven.apache.org/maven2/developers/mojo-api-specification.html for additional information regarding mojo. regards, -allan Choong Yong Koh wrote: So it means that if I wanted to use torque in maven 2, I have to write the plugin myself. :) However, the plugin development guide at http://maven.apache.org/maven2/developers/plugin-development-guide.html is quite bare. Nothing could be found on the maven wiki at http://wiki.apache.org/maven/ too. Is there any reference elsewhere I can refer to to start attempting to write the plugin? Thanks. Choong Yong On 9/11/05, Brett Porter [EMAIL PROTECTED] wrote: I believe that the torque plugin is only for Maven 1.x (currently, even Maven 1.x plugins appear in the Maven 2.x repository). - Brett On 9/10/05, Choong Yong Koh [EMAIL PROTECTED] wrote: Hi, I was trying to install the torque plugin for maven2, but was not succcessful (probably because I am still not familiar with maven2, although I have been using maven1 in many of my other projects). Question 1 is: - there are multiple copies of the maven torque plugin - http://www.ibiblio.org/maven2/torque/maven-torque-plugin/ - http://www.ibiblio.org/maven2/maven-torque-plugin/maven-torque-plugin/ Which one should I be refering to? How should I be installing the plugin? Question 2 is: How should I define my pom.xml in my project to use the plugin? Thanks for any response, as I was not really able to find much documentation on maven2 plugins. Choong Yong No virus found in this incoming message. Checked by AVG Anti-Virus. Version: 7.0.344 / Virus Database: 267.10.20/95 - Release Date: 9/9/2005 - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] maven-ear-plugin
what is garg-ejb packaging? an ejb packaging? regards, Edward Yakop Note: By default, all dependency will not be generated inside application.xml unless if it is either ejb-client, ejb or war. On 9/11/05, Adam Hardy [EMAIL PROTECTED] wrote: I'm bootstrapping m2 from svn source and I cannot work out how to get maven-ear-plugin to enter the module list into the application.xml. My application.xml contains only the project description and that's it. I've looked in the source code and it seems that the GenerateApplicationXmlMojo is not getting any modules in its modules collection - but if you look at my pom below, you'll see that the modules are all set up there (and the .ear file looks good apart from this application.xml). Any help would be gladly received! Here's my pom.xml: ?xml version=1.0 encoding=UTF-8? project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdorg.garg/groupId artifactIdgarg-ear/artifactId packagingear/packaging version1.0-SNAPSHOT/version nameGarg EAR/name descriptionGarg Application EAR Package with EJBs and Jars/description urlhttp://www.garg.com/url dependencies dependency groupIdorg.garg/groupId artifactIdgarg-delegate/artifactId version1.0-SNAPSHOT/version scopecompile/scope /dependency dependency groupIdorg.garg/groupId artifactIdgarg-ejb/artifactId version1.0-SNAPSHOT/version scopecompile/scope /dependency /dependencies build plugins plugin artifactIdmaven-ear-plugin/artifactId version2.0-beta-1-SNAPSHOT/version configuration version1.4/version archive manifest addClasspathtrue/addClasspath /manifest /archive /configuration executions execution goals goalgenerate-application-xml/goal goalear/goal /goals /execution /executions /plugin /plugins /build modules module../garg-dto/module module../garg-subdto/module module../garg-remote/module module../garg-delegate/module module../garg-ejb/module /modules /project - 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] how to deal with missing dependencies
On 11.09.2005, at 19:03, Jorg Heymans wrote: In this case, who is right : the pom declaring dependency groupIdd-haven-managed-pool/groupId artifactIdd-haven-managed-pool/artifactId version1.0/version /dependency or the maven repository having groupId and artifactId d-haven-mpool ? As I didn't feel to change the poms, i adjusted my local repository to match the pom declarations - but this quickly became a pain as I find more and more dependencies are mismatched :( Another option would be to exclude the incorrect transitive dependency and add the correct one to your project. Cheers, -Ralph. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[M2] Resource filtering with encoding
Hello,
How to specify encoding for resource files during filtering? In ant we
used copy encoding=UTF8 attribute, otherwise non-english letters get
messed up.
copy encoding=UTF8 todir=${ui.dest}/WEB-INF/conf
fileset
dir=${merged}/${conf.source}/web-client/WEB-INF/conf
include name=*.xml /
/fileset
filterset refid=filt.ui.conf /
/copy
Thank you,
Andrius Karpavicius
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: problems with Maven 1.1 -beta-1 in defining entities in project.xml
Hello,
Pls do not bother to test...i found theproblem in compatibility issues..
*Entities and JDK 1.4*
Due to a bug in the parser included with JDK 1.4, relative SYSTEM entities
will not work in maven.xml where they may have previously.
*Fix:* As above, we recommend not using entities in maven.xml, in favour of
inheritance and plugins. If you want an existing file to work without
modifications, you should download
Xerceshttp://repo1.maven.org/xerces/jars/xerces-2.6.2.jarand place
it in
JAVA_HOME/jre/lib/endorsed (this directory may need to be created).
i have a question for you then
how do you deal with this situation?
i have a project P which contains subprojects P1 P2
P1 P2 shares some of the dependencies, so ri ght not i am putting them
into a single file and i am using
entities to load them in both P1 P2.
in maven 1.1. how will you do that then? define common dependencies in the
master project.xml?
thanx in advance and regards
marco
On 9/12/05, Marco Mistroni [EMAIL PROTECTED] wrote:
Hello,
sorry it didnt help... i attach my project.xml, could you run it
and tell me what is the result
on your pc? i may have installed maven incorrectly
thanx in advance and regards
marco
On 9/10/05, Curtis, Harrison [EMAIL PROTECTED] wrote:
I have had similar problems transistioning from 1.0.2 to 1.1. I would
guess if you change
idejb-testing-examples/id
To
artifactIdejb-testing-examples/artifactId
It will work.
Bud Curtis
JDIMS Project
L-3 Communications
(719) 637-5633
-Original Message-
From: Marco Mistroni [mailto: [EMAIL PROTECTED]
Sent: Friday, September 09, 2005 10:01 AM
To: Maven Users List
Subject: problems with Maven 1.1 -beta-1 in defining entities in
project.xml
hello all,
i have following project.xml file
?xml version=1.0 encoding=ISO-8859-1?
!DOCTYPE project [
!ENTITY xdoclet-commons SYSTEM
file:${basedir}/xdoclet- commons.ent
]
!-- $Revision: 1.6 $ $Date: 2004/04/27 00:39:55 $ --
project
nameNRFX :: EJB Unit Testing Examples/name
idejb-testing-examples/id
groupIdnrfx/groupId
currentVersion1.0/currentVersion
inceptionYear2004/inceptionYear
packagecom.nrfx.articles.openejb/package
organization
nameNRFX Technologies LLC/name
urlhttp://www.nrfx.com//url
logo http://www.nrfx.com/images/logo01.gif/logo
/organization
description
EJB unit testing examples to accompany my OpenEJB article
/description
dependencies
xdoclet-commons;
dependency
groupIdgeronimo-spec/groupId
artifactIdgeronimo-spec-j2ee/artifactId
version1.4-rc1/version
/dependency
dependency
groupIddbunit/groupId
artifactIddbunit/artifactId
version2.0/version
/dependency
dependency
groupIdmysql/groupId
artifactIdmysql-connector/artifactId
version3.0.11/version
/dependency
dependency
groupIdgeronimo-spec/groupId
artifactIdgeronimo-spec-j2ee/artifactId
version1.4-rc1/version
/dependency
dependency
groupIdopenejb/groupId
artifactIdopenejb-core/artifactId
version1.0-SNAPSHOT/version
/dependency
dependency
idlog4j/id
version1.2.8/version
url http://jakarta.apache.org/log4j/url
properties
runtimetrue/runtime
/properties
/dependency
dependency
groupIdxerces/groupId
artifactIdxercesImpl/artifactId
version2.6.0/version
urlhttp://xml.apache.org/url
properties
runtimetrue/runtime
/properties
/dependency
dependency
idxml-apis/id
version1.0.b2/version
properties
runtimetrue/runtime
/properties
/dependency
dependency
idcastor/id
version0.9.5.3 http://0.9.5.3/ http://0.9.5.3/version
urlhttp://www.castor.org/url
properties
runtimetrue/runtime
/properties
/dependency
dependency
idoro/id
version2.0.8/version
properties
runtimetrue/runtime
/properties
/dependency
dependency
groupIdcommons-logging/groupId
artifactIdcommons-logging/artifactId
version1.0.3 /version
urlhttp://jakarta.apache.org/commons/logging//url
properties
runtimetrue/runtime
/properties
/dependency
!--
required for the database connection configured in
the openejb.conf
--
dependency
groupIdaxion/groupId
artifactIdaxion/artifactId
version1.0-M3-dev/version
properties
runtimetrue/runtime
/properties
/dependency
!-- required by axion --
dependency
groupIdcommons-collections/groupId
artifactIdcommons-collections/artifactId
version2.1/version
properties
repositorytrue/repository
/properties
/dependency
dependency
groupIdcommons-primitives/groupId
Re: [M2] maven-ear-plugin
It seems I didn't send my reply, so if it arrives twice, my apologies. garg-ejb is declared as ejb packaging. No modules declarations at all appear in the application xml. This is what it has: ?xml version=1.0 encoding=UTF-8? application xmlns=http://java.sun.com/xml/ns/j2ee; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd; version=1.4 display-namegarg-ear/display-name descriptionGarg Application EAR Package with EJBs and Jars/description /application Edward Yakop on 12/09/05 08:06, wrote: what is garg-ejb packaging? an ejb packaging? regards, Edward Yakop Note: By default, all dependency will not be generated inside application.xml unless if it is either ejb-client, ejb or war. On 9/11/05, Adam Hardy [EMAIL PROTECTED] wrote: I'm bootstrapping m2 from svn source and I cannot work out how to get maven-ear-plugin to enter the module list into the application.xml. My application.xml contains only the project description and that's it. I've looked in the source code and it seems that the GenerateApplicationXmlMojo is not getting any modules in its modules collection - but if you look at my pom below, you'll see that the modules are all set up there (and the .ear file looks good apart from this application.xml). Any help would be gladly received! Here's my pom.xml: ?xml version=1.0 encoding=UTF-8? project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdorg.garg/groupId artifactIdgarg-ear/artifactId packagingear/packaging version1.0-SNAPSHOT/version nameGarg EAR/name descriptionGarg Application EAR Package with EJBs and Jars/description urlhttp://www.garg.com/url dependencies dependency groupIdorg.garg/groupId artifactIdgarg-delegate/artifactId version1.0-SNAPSHOT/version scopecompile/scope /dependency dependency groupIdorg.garg/groupId artifactIdgarg-ejb/artifactId version1.0-SNAPSHOT/version scopecompile/scope /dependency /dependencies build plugins plugin artifactIdmaven-ear-plugin/artifactId version2.0-beta-1-SNAPSHOT/version configuration version1.4/version archive manifest addClasspathtrue/addClasspath /manifest /archive /configuration executions execution goals goalgenerate-application-xml/goal goalear/goal /goals /execution /executions /plugin /plugins /build modules module../garg-dto/module module../garg-subdto/module module../garg-remote/module module../garg-delegate/module module../garg-ejb/module /modules /project - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Naming convention for Maven plugin
Hello, is there any naming convention for new Maven plugins? If my project is named foo, should I name the belonging Maven plugin maven-foo-plugin ($pom.id)? Are names starting with maven- reserved for official plugins? Background: I named my plugin ddchange-maven-debugging and I wonder if that was a good idea. Perhaps I should choose maven-ddchange-plugin as it's name? Regards, Martin - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Naming convention for Maven plugin
On Mon, 2005-09-12 at 11:15 +0200, Martin Burger wrote: Hello, is there any naming convention for new Maven plugins? If my project is named foo, should I name the belonging Maven plugin maven-foo-plugin ($pom.id)? Are names starting with maven- reserved for official plugins? Background: I named my plugin ddchange-maven-debugging and I wonder if that was a good idea. Perhaps I should choose maven-ddchange-plugin as it's name? product-maven-plugin is the preferred naming convention. We will clean up and change the names of the plugins in the Mojo project sometime soon. Real soon now! -- Trygve - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Maven 1.1 Beta 2 Released
I started to have the following exception after installed beta 2: __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.1-beta-2 build:start: multiproject:projects-init: [echo] Gathering project list Starting the reactor... BUILD FAILED File.. C:\Documents and Settings\EmersonC\.maven\cache\maven-multiproject-pl ugin-1.4.1\plugin.jelly Element... maven:reactor Line.. 64 Column -1 Unknown error reading project Total time : 2 seconds Finished at : 12 September 2005 10:58:27 BST This was when I tried to run multiproject goal, when I try to build a subproject directly, the following happens: C:\workspace\com.yell.businessobjectsmaven site:deploy __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.1-beta-2 Attempting to download com.yell.java-1.0-SNAPSHOT.jar. Artifact /com.yell/jars/com.yell.java-1.0-SNAPSHOT.jar doesn't exist in remote r epository, but it exists locally. build:start: site:deploy: Attempting to download fop-0.20.5.jar. 1484K downloaded Attempting to download batik-1.5-fop-0.20-5.jar. 2062K downloaded Attempting to download avalon-framework-4.1.5.jar. 71K downloaded Attempting to download xalan-2.4.1.jar. 1006K downloaded BUILD FAILED File.. C:\Documents and Settings\EmersonC\.maven\cache\maven-xdoc-plugin-1.9 .2\plugin.jelly Element... attainGoal Line.. 989 Column -1 No goal [maven-findbugs-plugin:register] Total time : 35 seconds Finished at : 12 September 2005 11:06:58 BST Better to go back to 1.1 beta 1? Emerson On 12/09/05, Brett Porter [EMAIL PROTECTED] wrote: The Apache Maven team is pleased to announce the release of Maven 1.1 Beta 2 http://maven.apache.org/start/download.html Maven is a project management and project comprehension tool. Maven is based on the concept of a project object model: builds, documentation creation, site publication, and distribution publication are all controlled from the project object model. Maven also provides tools to create source metrics, change logs based directly on source repository, and source cross-references. For a list of changes since 1.1 beta 1, please see JIRA [2]. The 1.1 release focuses on the following objectives: * Integration of Maven 2 technologies such as Maven Wagon, Maven SCM and the new model code * Ant 1.6.5 support, including forkmode=once * Upgrade to later releases of dependencies, in particular Jelly * Significant improvements in memory usage * Improved POM layout * Bugfixes With just a few exceptions [1], Maven 1.1 is backwards compatible with Maven 1.0. *IMPORTANT: * You must ensure that Maven 1.1 is first in your path if you want to have it installed side-by-side with Maven 1.0.2 We hope you enjoy using Maven! If you have any questions, please consult: * the FAQ: http://maven.apache.org/faq.html * the maven-user mailing list: http://maven.apache.org/mail-lists.html For news and information, see: * Maven Blogs: http://www.mavenblogs.com/ - The Apache Maven Team [1] http://maven.apache.org/reference/backwards-compatibility.html [2] http://jira.codehaus.org/secure/ReleaseNote.jspa?version=10211styleName=HtmlprojectId=10030Create=Create - 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: [ANN] Maven 1.1 Beta 2 Released
-Original Message- From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] Sent: lundi 12 septembre 2005 12:16 To: Maven Users List; [EMAIL PROTECTED] Subject: Re: [ANN] Maven 1.1 Beta 2 Released For your first error, can you launch maven with the -e option to see which pom is invalid ? For your second error you must re-install the findbugs plugin because it was certainly deleted during the installation (it doesn't come with maven). Also note that you may have some issue with the findbugs plugin and Maven 1.1. See http://tinyurl.com/b7ev7 [snip] -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [ANN] Maven 1.1 Beta 2 Released
Hi, I just ran into the same problem myself. As a quick temporary fix you can use the 0.9.2-SNAPSHOT version of the findbugs plugin, which is available through ibiblio. It works with maven 1.1 beta2. I just updated this to my project.xml : dependency groupIdmaven-plugins/groupId artifactIdmaven-findbugs-plugin/artifactId version0.9.2-SNAPSHOT/version typeplugin/type /dependency -- jean-laurent On 9/12/05, Vincent Massol [EMAIL PROTECTED] wrote: -Original Message- From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] Sent: lundi 12 septembre 2005 12:16 To: Maven Users List; [EMAIL PROTECTED] Subject: Re: [ANN] Maven 1.1 Beta 2 Released For your first error, can you launch maven with the -e option to see which pom is invalid ? For your second error you must re-install the findbugs plugin because it was certainly deleted during the installation (it doesn't come with maven). Also note that you may have some issue with the findbugs plugin and Maven 1.1. See http://tinyurl.com/b7ev7 [snip] -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Jean-Laurent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] xsd updates
Just wondering when does http://maven.apache.org/maven-v4_0_0.xsd get updated? I noticed that it's missing distributionManagement/snapshotRepository but not sure if it gets updated when you publish the site? Cheers, Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Fwd: [ANN] Maven 1.1 Beta 2 Released
Hu I was testing mavenbook with maven 1.0.2, I had to update changelog plugin in order to succefull build the site. I used the command: maven plugin:download -Dmaven.repo.remote=http://www.ibiblio.org/maven, http://cvs.apache.org/repository/ -DgroupId=maven -DartifactId=maven-changelog-plugin -Dversion=1.7 Gonna test my project to see if now it works :) thanks Emerson On 12/09/05, Vincent Massol [EMAIL PROTECTED] wrote: -Original Message- From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] Sent: lundi 12 septembre 2005 12:16 To: Maven Users List; [EMAIL PROTECTED] Subject: Re: [ANN] Maven 1.1 Beta 2 Released For your first error, can you launch maven with the -e option to see which pom is invalid ? For your second error you must re-install the findbugs plugin because it was certainly deleted during the installation (it doesn't come with maven). Also note that you may have some issue with the findbugs plugin and Maven 1.1. See http://tinyurl.com/b7ev7 [snip] -Vincent - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] xsd updates
It will next be updated when the next Maven release goes out. It will be locked down at 2.0 final, and after that changes to the POM will cause a model increment (4.0.1, etc). - Brett On 9/12/05, Mark Hobson [EMAIL PROTECTED] wrote: Just wondering when does http://maven.apache.org/maven-v4_0_0.xsd get updated? I noticed that it's missing distributionManagement/snapshotRepository but not sure if it gets updated when you publish the site? Cheers, Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] xsd updates
On 12/09/05, Brett Porter [EMAIL PROTECTED] wrote: It will next be updated when the next Maven release goes out. It will be locked down at 2.0 final, and after that changes to the POM will cause a model increment (4.0.1, etc). Thanks for the clarification guys. Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] using deployed plugin snapshots with new metadata
I've just svn up'd to the latest m2 and seem to be having issues with using deployed snapshots of custom plugins that was working previously. I deploy the custom plugin with m2 -DupdateReleaseInfo=true deploy. All seems to deploy okay, complete with the new XML metadata files. I then delete any local-repo versions of the plugin and delete plugin-registry.xml to force auto-discovery of my plugin. My settings.xml is setup with the correct pluginGroup. I then run the plugin goal against another project which fails. It seems to be looking for pom urls of the form xxx-SNAPSHOT.pom, rather than those that are there of the form xxx-20050912.112423-1.pom, even though the metadata XML file indicates the snapshot version is indeed 20050912.112423, build 1. Am I doing anything wrong here? Cheers, Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] using deployed plugin snapshots with new metadata
It sounds like you've got it right. It should simply work. what is the contents of maven-metadata.xml for the artifact and version on the remote server? what about the various copies in the local repository? I will do a quick test as we don't have integration tests for deployment. - Brett On 9/12/05, Mark Hobson [EMAIL PROTECTED] wrote: I've just svn up'd to the latest m2 and seem to be having issues with using deployed snapshots of custom plugins that was working previously. I deploy the custom plugin with m2 -DupdateReleaseInfo=true deploy. All seems to deploy okay, complete with the new XML metadata files. I then delete any local-repo versions of the plugin and delete plugin-registry.xml to force auto-discovery of my plugin. My settings.xml is setup with the correct pluginGroup. I then run the plugin goal against another project which fails. It seems to be looking for pom urls of the form xxx-SNAPSHOT.pom, rather than those that are there of the form xxx-20050912.112423-1.pom, even though the metadata XML file indicates the snapshot version is indeed 20050912.112423, build 1. Am I doing anything wrong here? Cheers, Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] using deployed plugin snapshots with new metadata
On 12/09/05, Brett Porter [EMAIL PROTECTED] wrote: It sounds like you've got it right. It should simply work. what is the contents of maven-metadata.xml for the artifact and version on the remote server? what about the various copies in the local repository? The remote artfiact metadata is: metadata groupIdorg.codehaus.mojo/groupId artifactIdmaven-tomcat-plugin/artifactId versioning latest1.0-SNAPSHOT/latest release1.0-SNAPSHOT/release versions version1.0-SNAPSHOT/version /versions /versioning /metadata The remote version metadata is: metadata groupIdorg.codehaus.mojo/groupId artifactIdmaven-tomcat-plugin/artifactId version1.0-SNAPSHOT/version versioning snapshot timestamp20050912.112423/timestamp buildNumber1/buildNumber localCopytrue/localCopy /snapshot /versioning /metadata My local group metadata for both central and my remote repo is: metadata groupIdorg.codehaus.mojo/groupId plugins plugin prefixtomcat/prefix artifactIdmaven-tomcat-plugin/artifactId /plugin /plugins /metadata My local artifact metadata for both central and my remote repo is: metadata groupIdorg.codehaus.mojo/groupId artifactIdmaven-tomcat-plugin/artifactId versioning latest1.0-SNAPSHOT/latest release1.0-SNAPSHOT/release versions version1.0-SNAPSHOT/version /versions /versioning /metadata My local version metadata for my remote repo only is: metadata groupIdorg.codehaus.mojo/groupId artifactIdmaven-tomcat-plugin/artifactId version1.0-SNAPSHOT/version versioning snapshot timestamp20050912.112423/timestamp buildNumber1/buildNumber localCopytrue/localCopy /snapshot /versioning /metadata No other local files were downloaded. I will do a quick test as we don't have integration tests for deployment. Cheers, Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] using deployed plugin snapshots with new metadata
On 9/12/05, Mark Hobson [EMAIL PROTECTED] wrote: The remote version metadata is: ... localCopytrue/localCopy That's the problem. Will fix. - Brett
Re: [m2] using deployed plugin snapshots with new metadata
On 12/09/05, Brett Porter [EMAIL PROTECTED] wrote: That's the problem. Will fix. Thanks Brett - I did think that was a bit strange but couldn't find any docs on the new metadata format so didn't look into it further. Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
WAS Re: problems with Maven 1.1 -beta-1 in defining entities in project.xml - NOW Potential POM policy change
Brett Porter wrote: http://jira.codehaus.org/browse/MODELLO-18 when this is fixed it will be possible (however, it will be a non-default option) - Brett On 9/12/05, Jörg Schaible [EMAIL PROTECTED] wrote: Andy Glick wrote on Saturday, September 10, 2005 4:10 AM: Marco, When I executed maven pom:validate on your project.xml file I found 2 lines that the Modello generated parser rejected. 1) Maven 1.1 no longer supports XML entities as a means of including XML fragments This is a complete show-stopper for Maven 1.1 for us. We make heavily use of XML entities for all kind of information in the POMs and we use company wide system entities and entitiy overload mechanism. The requirements on a deployed POM have changed greatly between M1 and M2, and I believe they have have actually changed between M 1.0.2 and M 1.1B1. Because of the various incompatibility issues that are being mentioned on the list and because I have to believe that the active community would like to see the transitions between releases be as convenient and smooth as possible, both for now and going forward, I wanted to propose that we discuss the possibility of having development time POM binding and deployment time POM binding. That would mean that there could be 1) a private form of the POM maintained by the development team in a manner that was compatible with their development conventions and goals 2) a public form of the POM that was a well defined member of a per artifact/version upload bundle that would follow strict conventions so that it can be used in an as is fashion and supports transitive dependency computation and conflict resolution. The M2 POM repository models now support much finer grained control and variation than M1 at the artifact/version level. 3) Some set of default as well as optional interception points to allow the integration of transformers which could produce a deployment POM from a development POM I didn't mention implementation details, because I don't want to muddy the water. If we can agree that this is an issue that we would like to address, I'm sure that we will be able to identify candidate implementations. I'm sorry if this is already under active discussion, but if it is, I missed it on the lists. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] Hibernate plugin
Hello Jose If you need annotations support I put something together quickly for a project I'm working on. You can get it from here: http://www.hiberforum.org/2005/09/maven2_hibernate_and_dbunit_pl.html and also there it specifies where you can get the source code from it. Regards Johann Reyes
[m2] unit test question
I'm keen to see a particular low priority bug fixed (high priority to me) so I thought I'd take a look myself. Is there a good example of a unit test I should follow within the maven source code that I should try to follow? Thanks AW - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] quick update question
Actually running install will run the unit tests. Maybe I have to bite the bullet and do a full rebuild every time I svn update?? On 12 Sep 2005, at 14:06, Ashley Williams wrote: First of all what's the quickest way to update my maven installation? I'm very keen to avoid running the tests so I was hoping to do something like svn update, followed by m2 clean:clean install at the maven-components level. This would update my repository artifacts, but obviously I wouldn't get a new maven/bin directory. Is this direction workable? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Multiple remote repositories
I'm currently looking at the task ahead of us, migrating from Maven 1 to Maven 2. Transitive dependency resolving will cure many of our current ill's But: I'm having trouble getting M2 to work with multiple repositories. I wish M2 to first look at ibiblio (http://www.ibiblio.org/maven2) and secondary at my own repository (http://jarsm2.dyndns.dk). I attempt to achieve this by defining a profile which is referenced in the alwaysActive part of the POM. Only, the repositories I define in the profile seems to be completely ignored. I can't locate any documentation on remote repositories apart from the ones listed in the profiles sections. Have I missed something ? A small sample of how to address multiple remote repositories would make me a happy man *S*. br, /Sverre Eplov - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] quick update question
you need to run m2-bootstrap.sh Emmanuel Ashley Williams wrote: First of all what's the quickest way to update my maven installation? I'm very keen to avoid running the tests so I was hoping to do something like svn update, followed by m2 clean:clean install at the maven-components level. This would update my repository artifacts, but obviously I wouldn't get a new maven/bin directory. Is this direction workable? - 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] using deployed plugin snapshots with new metadata
fixed - will commit when svn cleanup gives me back my console :) - Brett On 9/12/05, Mark Hobson [EMAIL PROTECTED] wrote: On 12/09/05, Brett Porter [EMAIL PROTECTED] wrote: That's the problem. Will fix. Thanks Brett - I did think that was a bit strange but couldn't find any docs on the new metadata format so didn't look into it further. Mark
Building Mavenbook sources (was RE: [ANN] Maven 1.1 Beta 2 Released)
Hi Emerson, -Original Message- From: emerson cargnin [mailto:[EMAIL PROTECTED] Sent: lundi 12 septembre 2005 13:13 To: Maven Users List Subject: Fwd: [ANN] Maven 1.1 Beta 2 Released Hu I was testing mavenbook with maven 1.0.2, I had to update changelog plugin in order to succefull build the site. I used the command: maven plugin:download -Dmaven.repo.remote=http://www.ibiblio.org/maven, http://cvs.apache.org/repository/ -DgroupId=maven -DartifactId=maven-changelog-plugin -Dversion=1.7 Gonna test my project to see if now it works :) Actually I you have a look at Appendix A you'll see listed the minimal versions of all the plugins required for building the mavenbook source code. For the changelog plugin the minimal version is 1.8. Thanks -Vincent On 12/09/05, Vincent Massol [EMAIL PROTECTED] wrote: -Original Message- From: Arnaud HERITIER [mailto:[EMAIL PROTECTED] Sent: lundi 12 septembre 2005 12:16 To: Maven Users List; [EMAIL PROTECTED] Subject: Re: [ANN] Maven 1.1 Beta 2 Released For your first error, can you launch maven with the -e option to see which pom is invalid ? For your second error you must re-install the findbugs plugin because it was certainly deleted during the installation (it doesn't come with maven). Also note that you may have some issue with the findbugs plugin and Maven 1.1. See http://tinyurl.com/b7ev7 [snip] -Vincent - 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] quick update question
That's the safest option, but I also do this: m2 install cp target/*.jar $M2_HOME/lib for a single lib. For all libs, you can do m2 install at the root, then m2 assembly:assembly in maven-core and use the temp directory in target as your M2_HOME. We expect to add something more useful in the near future. -Dmaven.test.skip=true skips test, if you must. But they are pretty fast - its the integration tests that are slow. - Brett On 9/12/05, Emmanuel Venisse [EMAIL PROTECTED] wrote: you need to run m2-bootstrap.sh Emmanuel Ashley Williams wrote: First of all what's the quickest way to update my maven installation? I'm very keen to avoid running the tests so I was hoping to do something like svn update, followed by m2 clean:clean install at the maven-components level. This would update my repository artifacts, but obviously I wouldn't get a new maven/bin directory. Is this direction workable? - 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] quick update question, Mac OS X build failure
Ok thanks, useful property to know. Also at last I've noticed I get an integration test countdown! Worth pointing out is that for the last four svn updates over a week and a half I consistently get: Failed tests: [it0065, it0063]. You should know that it doesn't (seem to) affect day to day maven usage though. Here are the details of the two failures on Mac OS X tiger: ** it0065... FAILED - Standard Out - Command: /Applications/maven-latest/bin/m2 -e --no-plugin-registry -- batch-mode -Dmaven.repo.local=/Users/developer/.m2/repository clean:clean install *** Verifying: fail when [ERROR] detected? true *** Error Stacktrace: org.apache.maven.it.VerificationException: Expected file was not found: /Users/developer/projects/maven-working/maven-core-it/it0065/ target/parent-basedir at org.apache.maven.it.Verifier.verifyExpectedResult (Verifier.java:530) at org.apache.maven.it.Verifier.verify(Verifier.java:117) at org.apache.maven.it.Verifier.main(Verifier.java:759) Error Stacktrace * it0063... FAILED - Standard Out - Command: /Applications/maven-latest/bin/m2 -e --no-plugin-registry -- batch-mode -Dmaven.repo.local=/Users/developer/.m2/repository clean:clean package - Standard Error - Exit code: 1 Error Stacktrace: org.apache.maven.it.VerificationException at org.apache.maven.it.Verifier.executeGoals(Verifier.java:639) at org.apache.maven.it.Verifier.main(Verifier.java:753) Error Stacktrace Log file contents: + Error stacktraces are turned on. [INFO] Searching repository for plugin with prefix: 'clean'. [INFO] [INFO] Building org.apache.maven.it:maven-core-it0063:jar:1.0 [INFO]task-segment: [clean:clean, package] [INFO] [INFO] [clean:clean] [INFO] [resources:resources] [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Main Error: System artifact: jdk-tools:jdk-tools:jar:1.4.2 not found in path: / System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Home/../lib/ tools.jar jdk-tools:jdk-tools:1.4.2:jar Path to dependency: 1) org.apache.maven.it:maven-core-it0063:jar:1.0 2) jdk-tools:jdk-tools:jar:1.4.2 Root error: System artifact: jdk-tools:jdk-tools:jar:1.4.2 not found in path: / System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Home/../lib/ tools.jar jdk-tools:jdk-tools:1.4.2:jar Path to dependency: 1) org.apache.maven.it:maven-core-it0063:jar:1.0 2) jdk-tools:jdk-tools:jar:1.4.2 On 12 Sep 2005, at 14:43, Brett Porter wrote: That's the safest option, but I also do this: m2 install cp target/*.jar $M2_HOME/lib for a single lib. For all libs, you can do m2 install at the root, then m2 assembly:assembly in maven-core and use the temp directory in target as your M2_HOME. We expect to add something more useful in the near future. -Dmaven.test.skip=true skips test, if you must. But they are pretty fast - its the integration tests that are slow. - Brett On 9/12/05, Emmanuel Venisse [EMAIL PROTECTED] wrote: you need to run m2-bootstrap.sh Emmanuel Ashley Williams wrote: First of all what's the quickest way to update my maven installation? I'm very keen to avoid running the tests so I was hoping to do something like svn update, followed by m2 clean:clean install at the maven-components level. This would update my repository artifacts, but obviously I wouldn't get a new maven/bin directory. Is this direction workable? - 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: [m2] quick update question, Mac OS X build failure
65 was only created in the last couple of hours and I broke it - fixing now. 63 is a bug on Mac OS X - it would be great if you could file that in JIRA as it will mean you can't use anything wanting tools.jar as a dependency. Thanks, Brett On 9/12/05, Ashley Williams [EMAIL PROTECTED] wrote: Ok thanks, useful property to know. Also at last I've noticed I get an integration test countdown! Worth pointing out is that for the last four svn updates over a week and a half I consistently get: Failed tests: [it0065, it0063]. You should know that it doesn't (seem to) affect day to day maven usage though. Here are the details of the two failures on Mac OS X tiger: ** it0065... FAILED - Standard Out - Command: /Applications/maven-latest/bin/m2 -e --no-plugin-registry -- batch-mode -Dmaven.repo.local=/Users/developer/.m2/repository clean:clean install *** Verifying: fail when [ERROR] detected? true *** Error Stacktrace: org.apache.maven.it.VerificationException: Expected file was not found: /Users/developer/projects/maven-working/maven-core-it/it0065/ target/parent-basedir at org.apache.maven.it.Verifier.verifyExpectedResult (Verifier.java:530) at org.apache.maven.it.Verifier.verify(Verifier.java:117) at org.apache.maven.it.Verifier.main(Verifier.java:759) Error Stacktrace * it0063... FAILED - Standard Out - Command: /Applications/maven-latest/bin/m2 -e --no-plugin-registry -- batch-mode -Dmaven.repo.local=/Users/developer/.m2/repository clean:clean package - Standard Error - Exit code: 1 Error Stacktrace: org.apache.maven.it.VerificationException at org.apache.maven.it.Verifier.executeGoals(Verifier.java:639) at org.apache.maven.it.Verifier.main(Verifier.java:753) Error Stacktrace Log file contents: + Error stacktraces are turned on. [INFO] Searching repository for plugin with prefix: 'clean'. [INFO] [INFO] Building org.apache.maven.it:maven-core-it0063:jar:1.0 [INFO] task-segment: [clean:clean, package] [INFO] [INFO] [clean:clean] [INFO] [resources:resources] [INFO] [INFO] BUILD FAILURE [INFO] [INFO] Main Error: System artifact: jdk-tools:jdk-tools:jar:1.4.2 not found in path: / System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Home/../lib/ tools.jar jdk-tools:jdk-tools:1.4.2:jar Path to dependency: 1) org.apache.maven.it:maven-core-it0063:jar:1.0 2) jdk-tools:jdk-tools:jar:1.4.2 Root error: System artifact: jdk-tools:jdk-tools:jar:1.4.2 not found in path: / System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Home/../lib/ tools.jar jdk-tools:jdk-tools:1.4.2:jar Path to dependency: 1) org.apache.maven.it:maven-core-it0063:jar:1.0 2) jdk-tools:jdk-tools:jar:1.4.2 On 12 Sep 2005, at 14:43, Brett Porter wrote: That's the safest option, but I also do this: m2 install cp target/*.jar $M2_HOME/lib for a single lib. For all libs, you can do m2 install at the root, then m2 assembly:assembly in maven-core and use the temp directory in target as your M2_HOME. We expect to add something more useful in the near future. -Dmaven.test.skip=true skips test, if you must. But they are pretty fast - its the integration tests that are slow. - Brett On 9/12/05, Emmanuel Venisse [EMAIL PROTECTED] wrote: you need to run m2-bootstrap.sh Emmanuel Ashley Williams wrote: First of all what's the quickest way to update my maven installation? I'm very keen to avoid running the tests so I was hoping to do something like svn update, followed by m2 clean:clean install at the maven-components level. This would update my repository artifacts, but obviously I wouldn't get a new maven/bin directory. Is this direction workable? - 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]
Problems with ant typedef
Hi, I am in the process of moving some ant scripts into my maven.xml. Everything is going smoothly other than the fact that I think Maven/Jelly is treating my attempt to use a type I created with typedef as a task invocation. I get ClassCastExceptions. All of my taskdef's work with no problems at all. Any Ideas? I am using Maven 1.0.2 (but ran into the same issue with 1.1) and JDK 1.4. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] using deployed plugin snapshots with new metadata
Hmm, still having probs with this, albeit slightly different. The remote artifact metadata now reads: metadata groupIdorg.codehaus.mojo/groupId artifactIdmaven-tomcat-plugin/artifactId versioning release1.0-SNAPSHOT/release versions version1.0-SNAPSHOT/version /versions /versioning /metadata Which compared to the previous one is missing the latest version tag. Now it's looking for org.apache.maven.plugins:maven-tomcat-plugin:pom:RELEASE and failing when it can't find it. Any ideas? Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] using deployed plugin snapshots with new metadata
ugh. My last fix was a bit short sighted - sorry about that. I'll keep looking into it. - Brett On 9/13/05, Mark Hobson [EMAIL PROTECTED] wrote: Hmm, still having probs with this, albeit slightly different. The remote artifact metadata now reads: metadata groupIdorg.codehaus.mojo/groupId artifactIdmaven-tomcat-plugin/artifactId versioning release1.0-SNAPSHOT/release versions version1.0-SNAPSHOT/version /versions /versioning /metadata Which compared to the previous one is missing the latest version tag. Now it's looking for org.apache.maven.plugins:maven-tomcat-plugin:pom:RELEASE and failing when it can't find it. Any ideas? Mark
Re: [m2] quick update question, Mac OS X build failure
the tools.jar bug is now in jira. On 12 Sep 2005, at 15:24, Brett Porter wrote: 65 was only created in the last couple of hours and I broke it - fixing now. 63 is a bug on Mac OS X - it would be great if you could file that in JIRA as it will mean you can't use anything wanting tools.jar as a dependency. Thanks, Brett On 9/12/05, Ashley Williams [EMAIL PROTECTED] wrote: Ok thanks, useful property to know. Also at last I've noticed I get an integration test countdown! Worth pointing out is that for the last four svn updates over a week and a half I consistently get: Failed tests: [it0065, it0063]. You should know that it doesn't (seem to) affect day to day maven usage though. Here are the details of the two failures on Mac OS X tiger: ** it0065... FAILED - Standard Out - Command: /Applications/maven-latest/bin/m2 -e --no-plugin-registry -- batch-mode -Dmaven.repo.local=/Users/developer/.m2/repository clean:clean install *** Verifying: fail when [ERROR] detected? true *** Error Stacktrace: org.apache.maven.it.VerificationException: Expected file was not found: /Users/developer/projects/maven-working/maven-core-it/it0065/ target/parent-basedir at org.apache.maven.it.Verifier.verifyExpectedResult (Verifier.java:530) at org.apache.maven.it.Verifier.verify(Verifier.java:117) at org.apache.maven.it.Verifier.main(Verifier.java:759) Error Stacktrace * it0063... FAILED - Standard Out - Command: /Applications/maven-latest/bin/m2 -e --no-plugin-registry -- batch-mode -Dmaven.repo.local=/Users/developer/.m2/repository clean:clean package - Standard Error - Exit code: 1 Error Stacktrace: org.apache.maven.it.VerificationException at org.apache.maven.it.Verifier.executeGoals(Verifier.java:639) at org.apache.maven.it.Verifier.main(Verifier.java:753) Error Stacktrace Log file contents: + Error stacktraces are turned on. [INFO] Searching repository for plugin with prefix: 'clean'. [INFO] - --- [INFO] Building org.apache.maven.it:maven-core-it0063:jar:1.0 [INFO] task-segment: [clean:clean, package] [INFO] - --- [INFO] [clean:clean] [INFO] [resources:resources] [INFO] - --- [INFO] BUILD FAILURE [INFO] - --- [INFO] Main Error: System artifact: jdk-tools:jdk-tools:jar:1.4.2 not found in path: / System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Home/../ lib/ tools.jar jdk-tools:jdk-tools:1.4.2:jar Path to dependency: 1) org.apache.maven.it:maven-core-it0063:jar:1.0 2) jdk-tools:jdk-tools:jar:1.4.2 Root error: System artifact: jdk-tools:jdk-tools:jar:1.4.2 not found in path: / System/Library/Frameworks/JavaVM.framework/Versions/1.4.2/Home/../ lib/ tools.jar jdk-tools:jdk-tools:1.4.2:jar Path to dependency: 1) org.apache.maven.it:maven-core-it0063:jar:1.0 2) jdk-tools:jdk-tools:jar:1.4.2 On 12 Sep 2005, at 14:43, Brett Porter wrote: That's the safest option, but I also do this: m2 install cp target/*.jar $M2_HOME/lib for a single lib. For all libs, you can do m2 install at the root, then m2 assembly:assembly in maven-core and use the temp directory in target as your M2_HOME. We expect to add something more useful in the near future. -Dmaven.test.skip=true skips test, if you must. But they are pretty fast - its the integration tests that are slow. - Brett On 9/12/05, Emmanuel Venisse [EMAIL PROTECTED] wrote: you need to run m2-bootstrap.sh Emmanuel Ashley Williams wrote: First of all what's the quickest way to update my maven installation? I'm very keen to avoid running the tests so I was hoping to do something like svn update, followed by m2 clean:clean install at the maven-components level. This would update my repository artifacts, but obviously I wouldn't get a new maven/bin directory. Is this direction workable? -- -- - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [M2] maven-ear-plugin
This is what I have in my pom.xml: project modelVersion4.0.0/modelVersion groupIdcom.tokuii.serverside.baseapp/groupId artifactIdbsp-ear/artifactId version1.0-SNAPSHOT/version nameBaseapp - EAR/name urlhttp://www.tokuii.com/url packagingear/packaging parent groupIdcom.tokuii.serverside/groupId artifactIdbaseapp/artifactId version1.0-SNAPSHOT/version /parent build plugins plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-ear-plugin/artifactId configuration archive manifest addClasspathtrue/addClasspath /manifest /archive generateApplicationXmltrue/generateApplicationXml /configuration /plugin /plugins /build dependencies dependency groupIdcom.tokuii.serverside.baseapp.presentation.flash/groupId artifactIdbsp-pl-fls-ejb/artifactId version1.0-SNAPSHOT/version typeejb/type /dependency dependency groupIdcom.tokuii.serverside.baseapp.presentation.flash/groupId artifactIdbsp-pl-fls-web/artifactId version1.0-SNAPSHOT/version typewar/type /dependency /dependencies /project and maven 2 produce the ear accordingly. Regards, Edward Yakop On 9/12/05, Adam Hardy [EMAIL PROTECTED] wrote: It seems I didn't send my reply, so if it arrives twice, my apologies. garg-ejb is declared as ejb packaging. No modules declarations at all appear in the application xml. This is what it has: ?xml version=1.0 encoding=UTF-8? application xmlns=http://java.sun.com/xml/ns/j2ee; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://java.sun.com/xml/ns/j2ee http://java.sun.com/xml/ns/j2ee/application_1_4.xsd; version=1.4 display-namegarg-ear/display-name descriptionGarg Application EAR Package with EJBs and Jars/description /application Edward Yakop on 12/09/05 08:06, wrote: what is garg-ejb packaging? an ejb packaging? regards, Edward Yakop Note: By default, all dependency will not be generated inside application.xml unless if it is either ejb-client, ejb or war. On 9/11/05, Adam Hardy [EMAIL PROTECTED] wrote: I'm bootstrapping m2 from svn source and I cannot work out how to get maven-ear-plugin to enter the module list into the application.xml. My application.xml contains only the project description and that's it. I've looked in the source code and it seems that the GenerateApplicationXmlMojo is not getting any modules in its modules collection - but if you look at my pom below, you'll see that the modules are all set up there (and the .ear file looks good apart from this application.xml). Any help would be gladly received! Here's my pom.xml: ?xml version=1.0 encoding=UTF-8? project xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd; modelVersion4.0.0/modelVersion groupIdorg.garg/groupId artifactIdgarg-ear/artifactId packagingear/packaging version1.0-SNAPSHOT/version nameGarg EAR/name descriptionGarg Application EAR Package with EJBs and Jars/description urlhttp://www.garg.com/url dependencies dependency groupIdorg.garg/groupId artifactIdgarg-delegate/artifactId version1.0-SNAPSHOT/version scopecompile/scope /dependency dependency groupIdorg.garg/groupId artifactIdgarg-ejb/artifactId version1.0-SNAPSHOT/version scopecompile/scope /dependency /dependencies build plugins plugin artifactIdmaven-ear-plugin/artifactId version2.0-beta-1-SNAPSHOT/version configuration version1.4/version archive manifest addClasspathtrue/addClasspath /manifest /archive /configuration executions execution goals goalgenerate-application-xml/goal goalear/goal /goals /execution /executions /plugin /plugins /build modules module../garg-dto/module module../garg-subdto/module module../garg-remote/module module../garg-delegate/module module../garg-ejb/module /modules /project - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] properties
Heard that there is a new properties tag underneath root project, but can't guess the syntax - anyone know? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] using deployed plugin snapshots with new metadata
On 12/09/05, Brett Porter [EMAIL PROTECTED] wrote: ugh. My last fix was a bit short sighted - sorry about that. I'll keep looking into it. That's working now thanks. Cheers, Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Applets as WAR dependencies
Hi there, I've got an applet that I'd like to be included in a war - both of which are m2 projects. Is there any current or proposed way for the war pom to specify a non-WEB-INF jar dependency? Cheers, Mark - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2] packaging
What's the different possible values for packaging in the POM? I've seen examples of jar, war, ear - any others? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] packaging
maven-plugin is another. On 9/12/05, Matthew Smalley [EMAIL PROTECTED] wrote: What's the different possible values for packaging in the POM? I've seen examples of jar, war, ear - any others? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[OT] eclipse maven plugin to run without system install
Hello all, I've grabbed an eclipse plugin of maven-1.0.2 (the one that is available from MevenIDE's update site) and been tweaking with it to try to run Maven from within the Eclipse environment without requiring a system install of maven. *plugin/repo issue: The separate external maven plugins can also be defined and downloaded within the project.xml and project.properties file that are stored with *each project*: Project.properties == maven.repo.remote = http://www.ibiblio.org/maven/,http://cvs.apache.org/repository/ = Project.xml = dependency groupIdmaven-plugins/groupId artifactIdmaven-cobertura-plugin/artifactId version1.1/version typeplugin/type /dependency Default is the users homedir, which for now is fine. MevenIDE also defines a repo location in it's preferences. This issue has an acceptable solution/workaround for now. *end plugin/repo issue ##the problem I've modified my local maven-1.0.2 eclipse plugin as follows: *added forehead.conf from a standard maven install into the plugin/org.apache.maven_1.0.2/lib dir. *added log4j library to plugin/org.apache.maven_1.0.2/lib dir. *added the lib/endorsed directory from a maven install with all jars to plugin/org.apache.maven_1.0.2/lib/endorsed dir. Now up to this point: == org.apache.maven.MavenException: Maven was badly installed. Please reinstall it. at org.apache.maven.plugin.PluginManager.initialize(PluginManager.java:264) at org.apache.maven.MavenSession.initializePluginManager(MavenSession.java: 204) at org.apache.maven.MavenSession.initialize(MavenSession.java:171) at org.apache.maven.cli.App.doMain(App.java:475) at org.apache.maven.cli.App.main(App.java:1239) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.jav a:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessor Impl.java:25) at java.lang.reflect.Method.invoke(Method.java:585) at com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) == Some searching brings up http://jira.codehaus.org/browse/MAVEN-1420 . Tried just adding an empty ./bin dir with no results, and a /bin from an existing maven install with no results. Setting up a Windows environment MAVEN_HOME to this location does not change it either. The run command is coming from MevenIDE, but the way MevenIDE is setup is you usually point to a system install of Maven; is there a way to make the eclipse plugin of maven look like a system install or another option to have Maven run with just the eclipse plugin without a system install? Kinda stumped here, but looks like only one more hurdle to the finish line -D - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: [m2] packaging
Is there a definitive list somewhere, or ... What does this information get used for? -Original Message- From: Wendell Beckwith [mailto:[EMAIL PROTECTED] Sent: 12 September 2005 21:15 To: Maven Users List Subject: Re: [m2] packaging maven-plugin is another. On 9/12/05, Matthew Smalley [EMAIL PROTECTED] wrote: What's the different possible values for packaging in the POM? I've seen examples of jar, war, ear - any others? - 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] Multiple remote repositories
Hi, In your pom.xml insert this segment project ... repositories repository idcentral/id nameMaven Repository Switchboard/name urlhttp://repo1.maven.org/maven2/url /repository repository idmy-repo/id nameyour custom repo/name urlhttp://jarsm2.dyndns.dk/url /repository /repositories ... /project Regards, -allan Sverre Eplov wrote: I'm currently looking at the task ahead of us, migrating from Maven 1 to Maven 2. Transitive dependency resolving will cure many of our current ill's But: I'm having trouble getting M2 to work with multiple repositories. I wish M2 to first look at ibiblio (http://www.ibiblio.org/maven2) and secondary at my own repository (http://jarsm2.dyndns.dk). I attempt to achieve this by defining a profile which is referenced in the alwaysActive part of the POM. Only, the repositories I define in the profile seems to be completely ignored. I can't locate any documentation on remote repositories apart from the ones listed in the profiles sections. Have I missed something ? A small sample of how to address multiple remote repositories would make me a happy man *S*. br, /Sverre Eplov - 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] properties
-BEGIN PGP SIGNED MESSAGE- Hash: SHA1 Actually, no. It's *like* the properties defined in profiles in syntax, but this is a properties section that is specified as a direct child of the project element. So: project ~ ... ~ properties ~namevalue/name ~ /properties /project Cheers, john Allan Ramirez wrote: | I guess your'e referring with the profiles, here's a link for your | reference | | http://maven.apache.org/maven2/profiles-overview.html | | hope this helps, | | Regards, | -allan | | Ashley Williams wrote: | | Heard that there is a new properties tag underneath root project, but | can't guess the syntax - anyone know? | | - | 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] -BEGIN PGP SIGNATURE- Version: GnuPG v1.2.6 (GNU/Linux) iD8DBQFDJjEwK3h2CZwO/4URAiApAJ9e9gYTPqSCvHs27kTim2tB5BM3GACgmGS/ nl9MEBBYZBn7X2A0MwpvzSI= =AINP -END PGP SIGNATURE- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] properties
HI John, what can we do with these properties. Can I use it in as expression
to replace some common configurations:
buiild
some plugin
configuration
field1${my.property}somethingelse/field1
field2${my.property}somethingelse2/field2
/configuration
some plugin
...
/build
-Dan
On 9/12/05, John Casey [EMAIL PROTECTED] wrote:
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Actually, no. It's *like* the properties defined in profiles in syntax,
but this is a properties section that is specified as a direct child of
the project element. So:
project
~ ...
~ properties
~ namevalue/name
~ /properties
/project
Cheers,
john
Allan Ramirez wrote:
| I guess your'e referring with the profiles, here's a link for your
| reference
|
| http://maven.apache.org/maven2/profiles-overview.html
|
| hope this helps,
|
| Regards,
| -allan
|
| Ashley Williams wrote:
|
| Heard that there is a new properties tag underneath root project, but
| can't guess the syntax - anyone know?
|
| -
| 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]
-BEGIN PGP SIGNATURE-
Version: GnuPG v1.2.6 (GNU/Linux)
iD8DBQFDJjEwK3h2CZwO/4URAiApAJ9e9gYTPqSCvHs27kTim2tB5BM3GACgmGS/
nl9MEBBYZBn7X2A0MwpvzSI=
=AINP
-END PGP SIGNATURE-
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
