Re: All projects stuck in In progress
Doesn't build all repair this? Can we put a reset state button in the admin section of Continuum 1.0.2? On 11/25/05, Emmanuel Venisse [EMAIL PROTECTED] wrote: This problem appears when you stop continuum during a build. We'll fix it in next version. You have 2 solutions for fix it : - stop continuum, delete $CONTINUUM_HOME/apps/continuum/database and restart continuum. You'll obtain a fresh continuum without projects - download derby database tools and modify project state in project table The more easy is the first solution, but you'll need to re-add all your projects. Emmanuel Chris Poulsen a écrit : Hi, We are currently evaluating continuum inhouse. The install/setup of continuum went smoothly. After a reboot of the server both projects are stuck in In progress. It is not possible to delete the projects. We are using windows, java 1.4, ant, subversion and the newest release of continuum. Continuum is running as a service using the supplied java wrapper. How do we fix the state of the projects so we can get the builds up and running again? If it isn't possible, then how do we delete the projects so we can start over? TIA. -- Regards Chris
RE: maven 2 ear -plug in
Dear all, Folder: sample --pom.xml (ear) |__src\main\application\meta-inf\application.xml | |---primary-source-|--pom.xml(java jar) | |--src\main\java\ We try to package an ear with java jar. under sample directory, mvn compile is ok .However,package wrong. groupIdcom.hactl/groupId artifactIdjavatest/artifactId version1.0/version the artifactId javatest exists sample\primary-source\pom.xml 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; xmlns:artifact =urn:maven-artifact-ant modelVersion4.0.0/modelVersion groupIdcom.hactl/groupId artifactIdjavatest/artifactId packagingjar/packaging version1.0/version namecore project classes/name dependencies dependency groupIdjunit/groupId artifactIdjunit/artifactId version3.8.1/version scopetest/scope /dependency /dependencies build /build /project --- sample\ pom.xml: project modelVersion4.0.0/modelVersion groupIdcom.hactl/groupId version1.0/version artifactIdxxxproject/artifactId packagingpom/packaging namexxxproject/name build plugins plugin artifactIdmaven-ear-plugin/artifactId executions execution idear1/id phasepackage/phase configuration archive manifest addClasspathtrue/addClasspath /manifest /archive outputDirectoryeardir/outputDirectory modules module groupIdcom.hactl/groupId artifactIdjavatest/artifactId version1.0/version /module /modules !--includescommons-logging.jar/includes-- /configuration goals goalear/goal /goals /execution /executions /plugin /plugins /build /project -mvn -X package- + Error stacktraces are turned on. [DEBUG] Building Maven user-level plugin registry from: 'C:\Documents and Settings\gz-clark_rao\.m2\plugin-registry.xml' [DEBUG] Building Maven global-level plugin registry from: 'd: \maven-2.0-bin\conf\plugin-registry.xml' [INFO] Scanning for projects... [INFO] [INFO] Building xxxproject [INFO]task-segment: [package] [INFO] [DEBUG] maven-ear-plugin: resolved to version 2.0 from repository central [DEBUG] Retrieving parent-POM from the repository for project: null:maven-ear-plugin:maven-plugin:2.0 [DEBUG] com.hactl:xxxproject:pom:1.0 (selected for null) [DEBUG] org.apache.maven.plugins:maven-ear-plugin:maven-plugin:2.0 (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (selected for runtime) [DEBUG] Retrieving parent-POM from the repository for project: null:maven-archiver:jar:2.0 [DEBUG] org.apache.maven:maven-archiver:jar:2.0 (selected for runtime) [DEBUG] Retrieving parent-POM from the repository for project: null:maven-project:jar:2.0 [DEBUG] org.apache.maven:maven-project:jar:2.0 (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8 (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (selected for runtime) [DEBUG] classworlds:classworlds:jar:1.1-alpha-2 (selected for runtime) [DEBUG] junit:junit:jar:3.8.1 (selected for runtime) [DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-artifact:jar:2.0 [DEBUG] org.apache.maven:maven-artifact:jar:2.0 (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (selected for runtime) [DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-model:jar:2.0 [DEBUG] org.apache.maven:maven-model:jar:2.0 (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (selected for runtime) [DEBUG] Retrieving parent-POM from the repository for project: org.apache.maven:maven-artifact-manager:jar:2.0 [DEBUG] org.apache.maven:maven-artifact-manager:jar:2.0 (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-utils:jar:1.0.4 (selected for runtime) [DEBUG] org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-8 (selected for runtime) [DEBUG] org.apache.maven:maven-artifact:jar:2.0 (selected for runtime) [DEBUG] Retrieving
[m2] configuring war plugin
Hi
Before I file a jira issue is there some way of configuring the war
plugin so that it essentially does the bare minimum of jaring up my
classes directory and using a .war extension? Currently I don't need
any of the bells and whistles such as autogenerating the web.xml file
as I use xdoclet to do this sort of stuff for me.
Currently I have to configure war like this as a result of the last
discussion I had, which involves a hardcoded value that is subject to
change in order to fool it into copying over a web.xml file that I
have already generated with xdoclet:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.0-beta-2/version
configuration
webXml${project.build.directory}/generated/src/main/
resources/WEB-INF/web.xml/webXml
/configuration
/plugin
Additionally I can't figure out
how to make it copy over everything else under WEB-INF such as the
jboss web dd so it's actually a blocker.
And even if I eventually figure it out, I would say that the config
options aren't very suitable for working with xdoclet.
Thanks
- Ashley
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] configuring war plugin
Ok, I have managed to come up with a workaround like so:
configuration
warSourceDirectory${project.build.directory}/generated/
src/main/resources/warSourceDirectory
/configuration
In other words I've told it to copy everything from under generated
resources - that just happens to be the
xdoclet generated WEB-INF dir.
Hardcoding not ideal but no blocker - I'm happy.
- Ashley
On 26 Nov 2005, at 11:10, Ashley Williams wrote:
Hi
Before I file a jira issue is there some way of configuring the war
plugin so that it essentially does the bare minimum of jaring up my
classes directory and using a .war extension? Currently I don't
need any of the bells and whistles such as autogenerating the
web.xml file as I use xdoclet to do this sort of stuff for me.
Currently I have to configure war like this as a result of the last
discussion I had, which involves a hardcoded value that is subject
to change in order to fool it into copying over a web.xml file that
I have already generated with xdoclet:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.0-beta-2/version
configuration
webXml${project.build.directory}/generated/src/main/
resources/WEB-INF/web.xml/webXml
/configuration
/plugin
Additionally I can't figure out
how to make it copy over everything else under WEB-INF such as the
jboss web dd so it's actually a blocker.
And even if I eventually figure it out, I would say that the config
options aren't very suitable for working with xdoclet.
Thanks
- Ashley
-
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] configuring war plugin
Hi,
Look at the issue http://jira.codehaus.org/browse/MNG-1683.
I'm actually working to implements this feature (war plugin modification
+ a maven-zip-plugin to implements packagezip/package) (It's due to
a company use case).
With the feature I propose you just need to add this in the
configuration (Instead of using some other stuffs like embeded ant
scripts in the pom to copy resources) :
configuration
warSourceDirectory${baseDir}/src/main/webapp/warSourceDirectory
webappDirectory
implementation=java.io.File${basedir}/webappdir/webappDirectory
resources
!-- adding generating web.xml --
resource
directory${project.build.directory}/generated/xdoclet/directory
targetPath${basedir}/webappdir/WEB-INF/targetPath
/resource
!-- adding generating classes by some binding tools --
resource
directory${project.build.directory}/generated/xbeans/directory
targetPath${basedir}/webappdir/WEB-INF/classes/targetPath
/resource
!--
adding html content coming from an other artifact zip
type or anything else
jar + unpack true will be honored but doesn't make sense
;-)
--
resource
targetPath${basedir}/webappdir/targetPath
dependencies
dependency
groupIdgroupId/groupId
artifactIdartifactId/artifactId
versionversion/version
unpacktrue/unpack
typezip/type
/dependency
/dependencies
/resource
/resources
/configuration
I don't know if this will be integrated in the svn (If not the patch
will be attached to the issue).
If you're interested just push a vote ;-)
- Olivier
-Message d'origine-
De : Ashley Williams [mailto:[EMAIL PROTECTED]
Envoyé : samedi 26 novembre 2005 12:40
À : Maven Users List
Cc : [EMAIL PROTECTED]
Objet : Re: [m2] configuring war plugin
Ok, I have managed to come up with a workaround like so:
configuration
warSourceDirectory${project.build.directory}/generated/
src/main/resources/warSourceDirectory
/configuration
In other words I've told it to copy everything from under generated
resources - that just happens to be the
xdoclet generated WEB-INF dir.
Hardcoding not ideal but no blocker - I'm happy.
- Ashley
On 26 Nov 2005, at 11:10, Ashley Williams wrote:
Hi
Before I file a jira issue is there some way of configuring the war
plugin so that it essentially does the bare minimum of jaring up my
classes directory and using a .war extension? Currently I don't
need any of the bells and whistles such as autogenerating the
web.xml file as I use xdoclet to do this sort of stuff for me.
Currently I have to configure war like this as a result of the last
discussion I had, which involves a hardcoded value that is subject
to change in order to fool it into copying over a web.xml file that
I have already generated with xdoclet:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.0-beta-2/version
/configuration
/plugin
Additionally I can't figure out
how to make it copy over everything else under WEB-INF such as the
jboss web dd so it's actually a blocker.
And even if I eventually figure it out, I would say that the config
options aren't very suitable for working with xdoclet.
Thanks
- Ashley
-
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]
This e-mail, any attachments and the information contained therein (this
message) are confidential and intended solely for the use of the addressee(s).
If you have received this message in error please send it back to the sender
and delete it. Unauthorized publication, use, dissemination or disclosure of
this message, either in whole or in part is strictly prohibited.
--
Ce message électronique et tous les fichiers joints ainsi que les informations
contenues dans ce message ( ci après le message ), sont confidentiels et
destinés exclusivement à l'usage de la personne à laquelle ils sont adressés.
Si vous avez reçu ce message par erreur, merci de le renvoyer à son émetteur
et de le détruire. Toutes diffusion, publication, totale ou partielle ou
divulgation sous quelque forme que se soit non expressément autorisées de ce
message, sont interdites.
Re: RE : [m2] configuring war plugin
I look forward to trying out the patch.
On 26 Nov 2005, at 13:30, Olivier Lamy wrote:
Hi,
Look at the issue http://jira.codehaus.org/browse/MNG-1683.
I'm actually working to implements this feature (war plugin
modification
+ a maven-zip-plugin to implements packagezip/package) (It's
due to
a company use case).
With the feature I propose you just need to add this in the
configuration (Instead of using some other stuffs like embeded ant
scripts in the pom to copy resources) :
configuration
warSourceDirectory${baseDir}/src/main/webapp/warSourceDirectory
webappDirectory
implementation=java.io.File${basedir}/webappdir/webappDirectory
resources
!-- adding generating web.xml --
resource
directory${project.build.directory}/generated/xdoclet/directory
targetPath${basedir}/webappdir/WEB-INF/targetPath
/resource
!-- adding generating classes by some binding tools --
resource
directory${project.build.directory}/generated/xbeans/directory
targetPath${basedir}/webappdir/WEB-INF/classes/targetPath
/resource
!--
adding html content coming from an other artifact zip
type or anything else
jar + unpack true will be honored but doesn't make sense
;-)
--
resource
targetPath${basedir}/webappdir/targetPath
dependencies
dependency
groupIdgroupId/groupId
artifactIdartifactId/artifactId
versionversion/version
unpacktrue/unpack
typezip/type
/dependency
/dependencies
/resource
/resources
/configuration
I don't know if this will be integrated in the svn (If not the patch
will be attached to the issue).
If you're interested just push a vote ;-)
- Olivier
-Message d'origine-
De : Ashley Williams [mailto:[EMAIL PROTECTED]
Envoyé : samedi 26 novembre 2005 12:40
À : Maven Users List
Cc : [EMAIL PROTECTED]
Objet : Re: [m2] configuring war plugin
Ok, I have managed to come up with a workaround like so:
configuration
warSourceDirectory${project.build.directory}/generated/
src/main/resources/warSourceDirectory
/configuration
In other words I've told it to copy everything from under generated
resources - that just happens to be the
xdoclet generated WEB-INF dir.
Hardcoding not ideal but no blocker - I'm happy.
- Ashley
On 26 Nov 2005, at 11:10, Ashley Williams wrote:
Hi
Before I file a jira issue is there some way of configuring the war
plugin so that it essentially does the bare minimum of jaring up my
classes directory and using a .war extension? Currently I don't
need any of the bells and whistles such as autogenerating the
web.xml file as I use xdoclet to do this sort of stuff for me.
Currently I have to configure war like this as a result of the last
discussion I had, which involves a hardcoded value that is subject
to change in order to fool it into copying over a web.xml file that
I have already generated with xdoclet:
plugin
groupIdorg.apache.maven.plugins/groupId
artifactIdmaven-war-plugin/artifactId
version2.0-beta-2/version
/configuration
/plugin
Additionally I can't figure out
how to make it copy over everything else under WEB-INF such as the
jboss web dd so it's actually a blocker.
And even if I eventually figure it out, I would say that the config
options aren't very suitable for working with xdoclet.
Thanks
- Ashley
-
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]
This e-mail, any attachments and the information contained therein
(this message) are confidential and intended solely for the use
of the addressee(s). If you have received this message in error
please send it back to the sender and delete it. Unauthorized
publication, use, dissemination or disclosure of this message,
either in whole or in part is strictly prohibited.
--
Ce message électronique et tous les fichiers joints ainsi que les
informations contenues dans ce message ( ci après le message ),
sont confidentiels et destinés exclusivement à l'usage de la
personne à laquelle ils sont adressés. Si vous avez reçu ce message
par erreur, merci de le renvoyer à son émetteur et de le détruire.
Toutes diffusion, publication, totale ou partielle ou divulgation
sous quelque forme que se soit non expressément
[m2] xml-apis warning
I'm getting the following warning when using M2's Ant tasks: [artifact:dependencies] [WARNING] [artifact:dependencies] This artifact has been relocated to xml-apis:xml-apis:1.0.b2. I turned on verbose logging and it appears to be coming from commons-digester. springmodules:springmodules-validator:jar:0.1 (selected) commons-validator:commons-validator:jar:1.1.3 (selected) commons-digester:commons-digester:jar:1.5 (selected) commons-beanutils:commons-beanutils:jar:1.6 (removed - nearer found: 1.6.1) commons-beanutils:commons-beanutils:jar:1.6 (selected) commons-logging:commons-logging:jar:1.0 (removed - nearer found: 1.0.4) commons-logging:commons-logging:jar:1.0 (selected) [artifact:dependencies] [WARNING] [artifact:dependencies] This artifact has been relocated to xml-apis:xml-apis:1.0.b2. xml-apis:xml-apis:jar:1.0.b2 (selected) commons-collections:commons-collections:jar:2.1 (removed - nearer found: 2.1.1) commons-collections:commons-collections:jar:2.1 (selected) However, if I look at commons-digester-1.5.pom, it all looks fine: dependency groupIdxml-apis/groupId artifactIdxml-apis/artifactId version2.0.2/version /dependency Any ideas? Thanks, Matt - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] xml-apis warning
That's fine, xml-apis 2.0.2 should be 1.0.b2 On 11/26/05, Matt Raible [EMAIL PROTECTED] wrote: I'm getting the following warning when using M2's Ant tasks: [artifact:dependencies] [WARNING] [artifact:dependencies] This artifact has been relocated to xml-apis:xml-apis:1.0.b2. I turned on verbose logging and it appears to be coming from commons-digester. springmodules:springmodules-validator:jar:0.1 (selected) commons-validator:commons-validator:jar:1.1.3 (selected) commons-digester:commons-digester:jar:1.5 (selected) commons-beanutils:commons-beanutils:jar:1.6 (removed - nearer found: 1.6.1) commons-beanutils:commons-beanutils:jar:1.6 (selected) commons-logging:commons-logging:jar:1.0 (removed - nearer found: 1.0.4) commons-logging:commons-logging:jar:1.0 (selected) [artifact:dependencies] [WARNING] [artifact:dependencies] This artifact has been relocated to xml-apis:xml-apis:1.0.b2. xml-apis:xml-apis:jar:1.0.b2 (selected) commons-collections:commons-collections:jar:2.1 (removed - nearer found: 2.1.1) commons-collections:commons-collections:jar:2.1 (selected) However, if I look at commons-digester-1.5.pom, it all looks fine: dependency groupIdxml-apis/groupId artifactIdxml-apis/artifactId version2.0.2/version /dependency Any ideas? Thanks, Matt - 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] Is it possible to prevent warnings from a custom repository
On 11/24/05, Carlos Sanchez [EMAIL PROTECTED] wrote: I don't think you should go down that path, as you will introduce confusion for your users. Poms in ibiblio have to be suitable for everybody, any customization needed can be added to your own pom as exclusions, overriding,... I agree that it's not the best solution, and I'd *love* to upload all my dependencies to ibiblio, but I don't know if there's an issue with some of them. For instance, here's a list of custom JARs/POMs I have and why: OJB (http://static.appfuse.org/repository/ojb/db-ojb/1.0.3/), b/c the POM hasn't been updated yet: http://jira.codehaus.org/browse/MEV-231 Spring+XWork Integration (http://static.appfuse.org/repository/opensymphony/spring-xwork-integration/1.0/), b/c there was never a release. * Doh - now that I check, there is a release (https://xwork-optional.dev.java.net/servlets/ProjectDocumentList?folderID=1425). I'll create an upload request. I'll go with a groupId of xwork-optional and artifactId of spring-xwork-integration. Tapestry Mock (http://static.appfuse.org/repository/tapestry/tapestry-mock/3.0/), this is a custom JAR I created from Tapestry's testing framework in their CVS tree. It seems it would be inappropriate to create a JAR in their namespace that's not part of their distribution. Maybe I could create a request to upload this under the org.appfuse groupId? DWR (http://static.appfuse.org/repository/uk/ltd/getahead/dwr/1.0/), b/c the POM hasn't been updated for M2 yet (http://jira.codehaus.org/browse/MEV-232). Matt On 11/24/05, Matt Raible [EMAIL PROTECTED] wrote: It is possible to make ibiblio correct, I'm just looking for a workaround in the meantime. ;-) I've been entering invalid POM bugs into JIRA as I see them (20+ so far). However, there might be times where Maven developers and I don't agree, and it'd be nice to customize the POMs when that happens. Hopefully it won't happen that often. Matt On 11/24/05, Wim Deblauwe [EMAIL PROTECTED] wrote: Is it not possible to make ibibio correct or do you have special needs for your pom that others do not have? regards, Wim 2005/11/24, Matt Raible [EMAIL PROTECTED]: I've established my own repository for overriding POMs in ibiblio. This seems to work great, but I still get a warning when M2 can't find the JAR in my repo. It still goes to ibiblio and gets the correct one, so I'd like to turn off the warning - especially since I'm only overriding a few POMs and JARs. Developers will end up seeing a whole bunch of errors like the following. [artifact:dependencies] Downloading: ojb/db-ojb/1.0.3/db-ojb-1.0.3.pom [artifact:dependencies] Transferring 0K [artifact:dependencies] Downloading: ojb/db-ojb/1.0.3/db-ojb-1.0.3.jar [artifact:dependencies] [WARNING] Unable to get resource from repository remote (http://static.appfuse.org/repository) [artifact:dependencies] Downloading: ojb/db-ojb/1.0.3/db-ojb-1.0.3.jar [artifact:dependencies] Transferring 1141K Is it possible to turn off this warning? Thanks, Matt - 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] new hibernate+ejbdoclet+webdoclet plugin announcement
I should write the tasks using the CDATA to delimit them? Ashley Williams wrote: Srepfler, make sure you build mant first of all - it's in the same directory as hibernate. Also your plugin config should look something like this: plugin groupIdorg.codehaus.mojo/groupId artifactIdhibernatedoclet-maven-plugin/artifactId version1.0-beta-1/version executions execution goals goalhibernatedoclet/goal /goals phasegenerate-sources/phase configuration task![CDATA[ hibernatedoclet fileset includes=**/bo/*.java/ hibernate version=3.0/ /hibernatedoclet ]]/task /configuration /execution /executions /plugin Let me know how you get on. - Ashley - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] xml-apis warning
I've created an issue for that MNG-1689 On 11/26/05, Matt Raible [EMAIL PROTECTED] wrote: On 11/26/05, Carlos Sanchez [EMAIL PROTECTED] wrote: That's fine, xml-apis 2.0.2 should be 1.0.b2 What do you mean by that's fine? I realize that this WARNING doesn't cause any issues, but I'd like to do 1 of the following 2 things: 1. Change logging from WARNING to ERROR so I don't see these warnings. 2. Update the POM so the warning disappears. Is it possible to do one of the above? Thanks, Matt On 11/26/05, Matt Raible [EMAIL PROTECTED] wrote: I'm getting the following warning when using M2's Ant tasks: [artifact:dependencies] [WARNING] [artifact:dependencies] This artifact has been relocated to xml-apis:xml-apis:1.0.b2. I turned on verbose logging and it appears to be coming from commons-digester. springmodules:springmodules-validator:jar:0.1 (selected) commons-validator:commons-validator:jar:1.1.3 (selected) commons-digester:commons-digester:jar:1.5 (selected) commons-beanutils:commons-beanutils:jar:1.6 (removed - nearer found: 1.6.1) commons-beanutils:commons-beanutils:jar:1.6 (selected) commons-logging:commons-logging:jar:1.0 (removed - nearer found: 1.0.4) commons-logging:commons-logging:jar:1.0 (selected) [artifact:dependencies] [WARNING] [artifact:dependencies] This artifact has been relocated to xml-apis:xml-apis:1.0.b2. xml-apis:xml-apis:jar:1.0.b2 (selected) commons-collections:commons-collections:jar:2.1 (removed - nearer found: 2.1.1) commons-collections:commons-collections:jar:2.1 (selected) However, if I look at commons-digester-1.5.pom, it all looks fine: dependency groupIdxml-apis/groupId artifactIdxml-apis/artifactId version2.0.2/version /dependency Any ideas? Thanks, Matt - 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] Is it possible to prevent warnings from a custom repository
It's fine to have your own repo with snapshots and needed things like ojb until is fixed in ibiblio, knowing that those things are temporal and avoiding a release depending on them, eg. removing that repo before making a relese and be sure that everything is fine. For your custom jars you can upload them to your namespace in ibiblio (org.appfuse or any other of your domains) About xwork-optional.dev.java.nen the groupId should be net.java.dev.xwork-optional or an y other domain they own. Regards On 11/26/05, Matt Raible [EMAIL PROTECTED] wrote: On 11/24/05, Carlos Sanchez [EMAIL PROTECTED] wrote: I don't think you should go down that path, as you will introduce confusion for your users. Poms in ibiblio have to be suitable for everybody, any customization needed can be added to your own pom as exclusions, overriding,... I agree that it's not the best solution, and I'd *love* to upload all my dependencies to ibiblio, but I don't know if there's an issue with some of them. For instance, here's a list of custom JARs/POMs I have and why: OJB (http://static.appfuse.org/repository/ojb/db-ojb/1.0.3/), b/c the POM hasn't been updated yet: http://jira.codehaus.org/browse/MEV-231 Spring+XWork Integration (http://static.appfuse.org/repository/opensymphony/spring-xwork-integration/1.0/), b/c there was never a release. * Doh - now that I check, there is a release (https://xwork-optional.dev.java.net/servlets/ProjectDocumentList?folderID=1425). I'll create an upload request. I'll go with a groupId of xwork-optional and artifactId of spring-xwork-integration. Tapestry Mock (http://static.appfuse.org/repository/tapestry/tapestry-mock/3.0/), this is a custom JAR I created from Tapestry's testing framework in their CVS tree. It seems it would be inappropriate to create a JAR in their namespace that's not part of their distribution. Maybe I could create a request to upload this under the org.appfuse groupId? DWR (http://static.appfuse.org/repository/uk/ltd/getahead/dwr/1.0/), b/c the POM hasn't been updated for M2 yet (http://jira.codehaus.org/browse/MEV-232). Matt On 11/24/05, Matt Raible [EMAIL PROTECTED] wrote: It is possible to make ibiblio correct, I'm just looking for a workaround in the meantime. ;-) I've been entering invalid POM bugs into JIRA as I see them (20+ so far). However, there might be times where Maven developers and I don't agree, and it'd be nice to customize the POMs when that happens. Hopefully it won't happen that often. Matt On 11/24/05, Wim Deblauwe [EMAIL PROTECTED] wrote: Is it not possible to make ibibio correct or do you have special needs for your pom that others do not have? regards, Wim 2005/11/24, Matt Raible [EMAIL PROTECTED]: I've established my own repository for overriding POMs in ibiblio. This seems to work great, but I still get a warning when M2 can't find the JAR in my repo. It still goes to ibiblio and gets the correct one, so I'd like to turn off the warning - especially since I'm only overriding a few POMs and JARs. Developers will end up seeing a whole bunch of errors like the following. [artifact:dependencies] Downloading: ojb/db-ojb/1.0.3/db-ojb-1.0.3.pom [artifact:dependencies] Transferring 0K [artifact:dependencies] Downloading: ojb/db-ojb/1.0.3/db-ojb-1.0.3.jar [artifact:dependencies] [WARNING] Unable to get resource from repository remote (http://static.appfuse.org/repository) [artifact:dependencies] Downloading: ojb/db-ojb/1.0.3/db-ojb-1.0.3.jar [artifact:dependencies] Transferring 1141K Is it possible to turn off this warning? Thanks, Matt - 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] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] xml-apis warning
Thanks Carlos - much appreciated. Matt On 11/26/05, Carlos Sanchez [EMAIL PROTECTED] wrote: I've created an issue for that MNG-1689 On 11/26/05, Matt Raible [EMAIL PROTECTED] wrote: On 11/26/05, Carlos Sanchez [EMAIL PROTECTED] wrote: That's fine, xml-apis 2.0.2 should be 1.0.b2 What do you mean by that's fine? I realize that this WARNING doesn't cause any issues, but I'd like to do 1 of the following 2 things: 1. Change logging from WARNING to ERROR so I don't see these warnings. 2. Update the POM so the warning disappears. Is it possible to do one of the above? Thanks, Matt On 11/26/05, Matt Raible [EMAIL PROTECTED] wrote: I'm getting the following warning when using M2's Ant tasks: [artifact:dependencies] [WARNING] [artifact:dependencies] This artifact has been relocated to xml-apis:xml-apis:1.0.b2. I turned on verbose logging and it appears to be coming from commons-digester. springmodules:springmodules-validator:jar:0.1 (selected) commons-validator:commons-validator:jar:1.1.3 (selected) commons-digester:commons-digester:jar:1.5 (selected) commons-beanutils:commons-beanutils:jar:1.6 (removed - nearer found: 1.6.1) commons-beanutils:commons-beanutils:jar:1.6 (selected) commons-logging:commons-logging:jar:1.0 (removed - nearer found: 1.0.4) commons-logging:commons-logging:jar:1.0 (selected) [artifact:dependencies] [WARNING] [artifact:dependencies] This artifact has been relocated to xml-apis:xml-apis:1.0.b2. xml-apis:xml-apis:jar:1.0.b2 (selected) commons-collections:commons-collections:jar:2.1 (removed - nearer found: 2.1.1) commons-collections:commons-collections:jar:2.1 (selected) However, if I look at commons-digester-1.5.pom, it all looks fine: dependency groupIdxml-apis/groupId artifactIdxml-apis/artifactId version2.0.2/version /dependency Any ideas? Thanks, Matt - 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] new hibernate+ejbdoclet+webdoclet plugin announcement
Sorry, yes - for the time being ;) Not sure how to inject config xml into a mojo so for now it's got to be a string - and all the angled brackets would cause trouble without the CDATA section. As soon as I can work it out I will definitely change this though! On 26 Nov 2005, at 22:43, Srepfler Srgjan wrote: I should write the tasks using the CDATA to delimit them? Ashley Williams wrote: Srepfler, make sure you build mant first of all - it's in the same directory as hibernate. Also your plugin config should look something like this: plugin groupIdorg.codehaus.mojo/groupId artifactIdhibernatedoclet-maven-plugin/artifactId version1.0-beta-1/version executions execution goals goalhibernatedoclet/goal /goals phasegenerate-sources/phase configuration task![CDATA[ hibernatedoclet fileset includes=**/bo/*.java/ hibernate version=3.0/ /hibernatedoclet ]]/task /configuration /execution /executions /plugin Let me know how you get on. - Ashley - 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] new hibernate+ejbdoclet+webdoclet plugin announcement
Ashley Williams wrote: Sorry, yes - for the time being ;) Not sure how to inject config xml into a mojo so for now it's got to be a string - and all the angled brackets would cause trouble without the CDATA section. As soon as I can work it out I will definitely change this though! I think I've noted that the antrun plugin allows such a functionality. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] custom plugin parameters on site?
Yes, please. - Brett On 11/25/05, Wim Deblauwe [EMAIL PROTECTED] wrote: ok, that works fine. Should I file a JIRA improvement issue to have this documented on http://maven.apache.org/guides/plugin/guide-java-plugin-development.html? regards, Wim 2005/11/25, Brett Porter [EMAIL PROTECTED]: Include maven-plugin-plugin as a report. Cheers, Brett On 11/24/05, Wim Deblauwe [EMAIL PROTECTED] wrote: Hi, The site's of the plugins of Maven have a page with an overview of the goals and the parameters of the plugin. How is this generated? I looked at http://maven.apache.org/guides/plugin/guide-java-plugin-development.htmlto find this, but I could not find that info there. regards, Wim - 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 taken into account in install
Yep, that's the idea. One of two things ends up occuring: 1) you have to copy it from the local repository to a staging directory to prepare it, in which case you rename it on the way 2) you include it sourced directly from the local repo, but specify a filename it will use in the target, where you rename it You might also be interested in the recent enhancements to the assembly plugin and discussions on JIRA for creating NSIS installers - the same interface should be used for your installshield plugin I imagine. Cheers, Brett On 11/25/05, Wim Deblauwe [EMAIL PROTECTED] wrote: ok, I understand. The better way is probably to rename them in the project that needs them unversioned (my InstallShield merge module) when downloading the dependencies. 2005/11/25, Brett Porter [EMAIL PROTECTED]: Sorry, I've closed this as won't fix. http://maven.apache.org/maven-1.x/faq.html#unversioned-jars On 11/25/05, Wim Deblauwe [EMAIL PROTECTED] wrote: Done: http://jira.codehaus.org/browse/MNG-1676 Wim 2005/11/24, Jason van Zyl [EMAIL PROTECTED]: Wim Deblauwe wrote: Hi, when I set finalName/ in my pom.xml, the install plugin does not take this name into account. Just for testing I added finalNametest.jar/finalName to the pom.xmlof a custom plugin of mine. When doing 'mvn install', I get this: [INFO] Installing Y:\wimd_test_vob\modules\maven-plugins\maven-nmake-plugin\target\test.jar.jar to C:\Documents and Settings\WIMD\.m2\repository\com\barcoview\mavenplugin\maven-nmake-plugin\1.0-SNAPSHOT\maven- nmake-plugin-1.0-SNAPSHOT.jar I was hoping it would install to the directory it does, but as test.jar. Can you raise an issue in JIRA? -- jvz. Jason van Zyl jason at maven.org http://maven.apache.org First, the taking in of scattered particulars under one Idea, so that everyone understands what is being talked about ... Second, the separation of the Idea into parts, by dividing it at the joints, as nature directs, not breaking any limb in half as a bad carver might. -- Plato, Phaedrus (Notes on the Synthesis of Form by C. Alexander) - 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-antrun-plugin classloading issues?
How do you define your ant task? I think this is just a matter of how the classpaths are defined and can be fixed - check that it is not in JIRA and if not, please add it. Thanks, Brett On 11/25/05, Henry Isidro [EMAIL PROTECTED] wrote: Hi. I'm trying to run an ant task from the antrun plugin. When I try to define some dependencies as provided so that the packaging won't include them, the build stops and complains that the ant task can't find classes found in those provided dependencies. Everything works fine if I specify compile but that includes the dependency in the package which is what I do not want. Is there a workaround to this or do I just have to live with the dependencies being bundled in with my package? Regards, Henry - 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: Maven 1.x Repository
Thanks Geoffrey, I'd forgotten that limitation of M1. This wouldn't affect the final conversion, but I'm looking into a way to test it. Cheers, Brett On 11/25/05, Geoffrey [EMAIL PROTECTED] wrote: Brett, I am currently still using m1.1-beta2 (although already experimenting with m2). I did the following things: 1) moved user_home/.maven/repository to user_home/.maven/repository_backup 2) Changed in my parent pom's project.properties: maven.repo.remote = http://repo1.maven.org/maven,http://myInternalRepo (orginally had the Ibiblio in it) 3) Do a cleanBuildProductionDeploy, but it failed immediatly: __ __ | \/ |__ _Apache__ ___ | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~ |_| |_\__,_|\_/\___|_||_| v. 1.1-beta-2 Directory C:\Documents and Settings\GEOFFREY.DESMET\.maven\repository does not exist. Attempting to create. Attempting to download dom4j-1.4-dev-8.jar. Error getting URI host org.apache.commons.httpclient.HttpException: Redirect from host repo1.maven.org to www.ibiblio.org is not supported at org.apache.commons.httpclient.HttpMethodBase.checkValidRedirect(HttpMethodBase.java:1237) at org.apache.commons.httpclient.HttpMethodBase.processRedirectResponse(HttpMethodBase.java:1185) at org.apache.commons.httpclient.HttpMethodBase.isRetryNeeded(HttpMethodBase.java:967) at org.apache.commons.httpclient.HttpMethodBase.execute(HttpMethodBase.java:1089) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:643) at org.apache.commons.httpclient.HttpClient.executeMethod(HttpClient.java:497) at org.apache.maven.wagon.providers.http.HttpWagon.get(HttpWagon.java:287) at org.apache.maven.wagon.providers.http.HttpWagon.getIfNewer(HttpWagon.java:234) at org.apache.maven.verifier.DependencyVerifier.getRemoteArtifact(DependencyVerifier.java:391) at org.apache.maven.verifier.DependencyVerifier.getDependencies(DependencyVerifier.java:291) at org.apache.maven.verifier.DependencyVerifier.satisfyDependencies(DependencyVerifier.java:182) at org.apache.maven.verifier.DependencyVerifier.verify(DependencyVerifier.java:99) at org.apache.maven.project.Project.verifyDependencies(Project.java:569) at org.apache.maven.plugin.PluginManager.loadScript(PluginManager.java:1116) at org.apache.maven.plugin.PluginManager.runScript(PluginManager.java:1161) at org.apache.maven.plugin.PluginManager.initialiseHousingPluginContext(PluginManager.java:792) at org.apache.maven.plugin.PluginManager.prepAttainGoal(PluginManager.java:747) at org.apache.maven.jelly.tags.werkz.MavenAttainGoalTag.doTag(MavenAttainGoalTag.java:108) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:247) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) at org.apache.maven.jelly.tags.werkz.MavenGoalTag.runBodyTag(MavenGoalTag.java:78) at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:109) at org.apache.maven.werkz.Goal.fire(Goal.java:656) at org.apache.maven.werkz.Goal.attain(Goal.java:592) at org.apache.maven.werkz.WerkzProject.attainGoal(WerkzProject.java:210) at org.apache.maven.jelly.tags.werkz.MavenAttainGoalTag.doTag(MavenAttainGoalTag.java:114) at org.apache.commons.jelly.impl.TagScript.run(TagScript.java:247) at org.apache.commons.jelly.impl.ScriptBlock.run(ScriptBlock.java:95) $ at org.apache.maven.jelly.tags.werkz.MavenGoalTag$MavenGoalAction.performAction(MavenGoalTag.java:109) at org.apache.maven.werkz.Goal.fire(Goal.java:656) at org.apache.maven.werkz.Goal.attain(Goal.java:592) at org.apache.maven.plugin.PluginManager.attainGoals(PluginManager.java:693) at org.apache.maven.MavenSession.attainGoals(MavenSession.java:263) at org.apache.maven.cli.App.doMain(App.java:511) at org.apache.maven.cli.App.main(App.java:1258) 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 com.werken.forehead.Forehead.run(Forehead.java:551) at com.werken.forehead.Forehead.main(Forehead.java:581) Invalid Redirect URI from: http://repo1.maven.org:80/maven//dom4j/jars/dom4j-1.4-dev-8.jar to: http://www.ibiblio.org/ma ven2/dom4j/dom4j/1.4-dev-8/dom4j-1.4-dev-8.jar Error retrieving artifact from [http://repo1.maven.org/maven]: org.apache.maven.wagon.TransferFailedException: Failed to trasfer file: http://repo1.maven.org/maven//dom4j/jars/dom4j-1.4-dev-8.jar. Return code is: 301
[m2] question about pom and namespaces
Hi, This is something I never understood so I'd like to know what was the reasoning behind the choices that were made although some weren't made by the maven project itself. First, as I didn't misunderstood this wrong, the ant xml format itself doesn't have a schema? I saw it can get extended using taskdef and loading a class and after that you can use new targets. Which makes a schema useless I suppose. Now, there's a possibility to insert some ant code inside the pom itself. Wouldn't be better if when we call an external tool that uses some xml based format that it's code should use namespaces? I mean you must let tools be able to analyze the document, validate the content and offer code completion. Without namespaces I don't see these documents very xml-friendly. Also other path would be that the editors would have to know the various formats used and be able to do reflection run-time, but in which timespan can that be achieved? - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] new hibernate+ejbdoclet+webdoclet plugin announcement
Thanks for the pointer, I've seen it too - however the code looked very time consuming to reverse engineer so I spent my time elsewhere. Patches welcome of course! On 26 Nov 2005, at 23:22, Srepfler Srgjan wrote: Ashley Williams wrote: Sorry, yes - for the time being ;) Not sure how to inject config xml into a mojo so for now it's got to be a string - and all the angled brackets would cause trouble without the CDATA section. As soon as I can work it out I will definitely change this though! I think I've noted that the antrun plugin allows such a functionality. - 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: inheriting from plugins
The field metadata when creating plugins is read from source files, so
is not available when the original source is not. The metadata is
available in the plugin in {{META-INF/maven/plugin.xml}}, but at this
point there is no way to incorporate it when building a new plugin.
We currently recommend building your plugins using composition instead
of inheritence.
Cheers,
Brett
On 11/25/05, Anuerin Diaz [EMAIL PROTECTED] wrote:
hi,
i am planning to develop a plugin similar to the assembly:directory
goal so i am looking at extending the AbstractAssemblyMojo to re-use
some of its properties and code. the configuration is similar to that
of the assemblies but we would like to rewrite and add some more
project features. my problem is that the properties in the parent
class is not being initialized properly in our custom classes. as an
example the descriptor variable is always set to null, but the
configuration properties that we added are initialized properly.
anybody have a clue what we missed? i am looking at the
DirectoryMojo source code and it is implemented the same way. thanks.
ciao!
--
Programming, an artform that fights back
Anuerin G. Diaz
Registered Linux User #246176
Friendly Linux Board @ http://mandrivausers.org/index.php
http://capsule.ramfree17.org , when you absolutely have nothing else
better to do
-
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]
Maven2 antrun ant jar update problem
Hello,
I have an ant script that I run during install for a project which
essentially unjars the created WAR file, extracting out *.xml and *.properties
files and doing a mass replacement for various tokens and then updates the WAR
file with the modified files. This ant script invokes other ant scripts, one
of which is the Tokenize.xml script I wrote which unjars the desired files,
does the token replacement, and then updates the WAR file. When I run this
script directly from the command line (i.e., ant -buildfile=...) it works every
time. When I invoke this same script from Maven2 using the AntRun plugin, it
works the first time and from then on until something magical happens
everything works except the updating of the jar file.
The Tokenize.xml file is listed below. It simply unjars three types of files
out of whatever JAR (or WAR) file it is given into a specified working
directory. Then it does token replacement on the files in that working
directory. Then it simply updates the original JAR file with any modified
files. Not very complicated. If I run this set of scripts from Maven2, it
works once, then if I rebuild immediately the jar update fails. If I wait ten
or fifteen minutes and then run again, it often will work. I have not figured
out how to turn on the verbose ant option from within AntRun, so I can't get to
any meaningful diagnostic output. I have run in the verbose mode from ant, but
of course the script always works within ant!
If anyone has any ideas, I would be appreciative.
Thanks!
Walt Barrow
?xml version=1.0?
!DOCTYPE project
!--
Tokenize.xml
Description: Tokenize an archive file (e.g., war, jar, sar).
Targets: tokenizeFile, tokenizeDir
--
project name=ArchitectureProject default= basedir=.
!-- Read all the environment variables into env.xxx type properties --
property environment=env/
property name=m.default.replace.filter.file
value=./DefaultReplaceFilter.xml /
!-- =
TARGET: tokenizeFile (main target)
DESC: Perform token substitution on the contents of a jar.
1. unjar to temporary folder
2. replacing tokens
3. jar that temporary folder into single *.jar file
PARAMS: jar.path - path to jar file to tokenize, in place
working.dir - temporary directory to use
replace.filter.file (set to NONE if not used)
==--
target name=tokenizeFile
echo message= /
echo message=jar.path is ${jar.path} /
echo message=working.dir is ${working.dir} /
condition property=m.do.other
not
equals arg1=${replace.filter.file} arg2=NONE /
/not
/condition
!-- unjar files into the temporary directory --
antcall target=unjar
param name=p.jar.path value=${jar.path}/
param name=p.dest.dir value=${working.dir}/
/antcall
!-- replacing tokens --
antcall target=defaultReplaceToken
param name=p.working.dir value=${working.dir}/
/antcall
antcall target=replaceToken
param name=p.working.dir value=${working.dir}/
/antcall
!-- jar folder/files --
antcall target=jar
param name=p.src.dir value=${working.dir}/
param name=p.jar.path value=${jar.path}/
/antcall
!-- delete the temp folder --
!--
delete dir=${working.dir}/
--
/target
!-- =
TARGET: tokenizeDir (main target)
DESC: Perform token substitution on a specified directory.
PARAMS: working.dir
replace.filter.file (set to NONE if not used)
==--
target name=tokenizeDir
echo message= /
echo message=working.dir is ${working.dir} /
condition property=m.do.other
not
equals arg1=${replace.filter.file} arg2=NONE /
/not
/condition
!-- replacing tokens --
antcall target=defaultReplaceToken
param name=p.working.dir value=${working.dir}/
/antcall
antcall target=replaceToken
param name=p.working.dir value=${working.dir}/
/antcall
/target
!-- =
TARGET: unjar
DESC: unjar filepathname - file to unjar
PARAMS: p.jar.path - source file path
p.dest.dir - destination directory
==--
target name=unjar
!-- delete the temp folder --
delete dir=${p.dest.dir}/
!-- create temporary folder for unjar --
mkdir dir=${p.dest.dir}/
unjar src=${p.jar.path} dest=${p.dest.dir}
patternset
include name=**/*.xml /
include name=**/*.properties /
include name=**/*.txt /
/patternset
/unjar
/target
!-- =
TARGET:
Re: [m2] dependency graph
http://docs.codehaus.org/display/MAVEN/Dependency+Graphing On 11/25/05, Wim Deblauwe [EMAIL PROTECTED] wrote: Just for the record, here are 2 links that might ease the work: http://www.xml.com/pub/a/2004/09/08/tree.html http://www.linguiste.org/syntax/tree/drawer/ They show how to convert an xml tree structure to a SVG image. regards, Wim 2005/11/25, Wim Deblauwe [EMAIL PROTECTED]: Well, maybe we need to bundle to effort to know where we are standing on some wiki page? regards, Wim 2005/11/25, Brett Porter [EMAIL PROTECTED]: Yes, its planned. We just have a very long todo list :) It is quite simple, as the artifact resolver has a listener with nodes that can be used to get all the information, once a way is provided to hook into the process. I think some others have worked on some related experiements (Joakim?) Cheers, Brett On 11/25/05, Wim Deblauwe [EMAIL PROTECTED] wrote: Hi, it would be really cool to have a plugin that shows all the dependencies of your project in a graph. This graph could be in SVG or png or whatever. Is there already such a plugin or plans for such a plugin? What graphing library do you think would be best to implement this kind of thing (must be open source ofcourse)? With the maven 2 dependency mechanism, this can't be that hard. Get your dependencies, then get the dependencies of your dependencies and so on. Put all that in some kind of model that some library can turn into a nice graph et voila! :) regards, Wim - 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: Antrun plugin and the war:war phases
It looks right (I assume your deploy goal is to deploy into a running appserver rather than to a repository, so this is a reasonble phase to do it in). Are you actually running mvn package, or mvn war:war? - Brett On 11/26/05, Jean-Sebastien Bournival [EMAIL PROTECTED] wrote: Hi, I am trying to trigger an ant task after I used the maven war:war goal. The problem I have is that nothing ever happens regarding the antrun plugin. I do not see any trace of execution besides the war:war plugin. Am I doing something wrong? Am I targeting the right phase? What are the lifecycle involved in the war:war plugin? How can I know this? Here is my build / block in my pom.xml: build finalNamemy-webapp/finalName plugins plugin artifactIdmaven-antrun-plugin/artifactId executions execution phasepackage/phase configuration tasks ant antfile=build.xml target=deploy / /tasks /configuration goals goalrun/goal /goals /execution /executions /plugin /plugins /build Thanx, JS. - 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: Dependencies
On 11/26/05, John Tolentino [EMAIL PROTECTED] wrote: You can use a combination of: 1. Defining versions on the root pom through the dependency management section. Skip the dependency versions in your modules since they will inherit the parent pom's. 2. Use SNAPSHOTS for modules that you change often because they're still under development. Other projects that depends on your project using the SNAPSHOT will download the latest copy you upload (timestamp based). 3. Use version ranges, which will use the best version matching all required ranges - eg [2.0,) means = 2.0. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
writing a new plugin
I'm about to embark on writing a maven 2 plugin for Antenna. Antenna has existing Ant tasks defined (in fact its an Ant task lib). In Maven 1 it was fairly easy to implement a Maven plugin using ant tasks because you could simple call them int he plugin... how would that type of conversion be done for Maven 2? So far the best I can see is to create a new Mojo that mirrors the Ant task(s). Is there documentation some place on converting an Ant task to a maven goal?
Re: Pom for repository jars necessary?
Frank, the POM is not generated automatically. In fact, it will cause dependencies to fail if you run it in offline mode unless you have the patch described here: http://jira.codehaus.org/browse/MNG-1443 Brian On 11/25/05, ir. ing. Jan Dockx [EMAIL PROTECTED] wrote: On 25 Nov 2005, at 15:22, Ido M. Tamir wrote: Hi, I am trying to migrate from maven 1 to maven 2. I specified my old repository in the maven 2 pom as an accessible repository. Maven 2 then tries to find poms there e.g. ~/.maven/repository/hibernate/poms/hibernate-3.1rc3.pom Do I have to write a pom for each jar that I put into the maven2 repository or into the m1 repository? No, but you might want to, to enable transitive dependencies. Thank you very much for your answer ido - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] Met vriendelijke groeten, Jan Dockx PeopleWare NV - Head Office Cdt.Weynsstraat 85 B-2660 Hoboken Tel: +32 3 448.33.38 Fax: +32 3 448.32.66 PeopleWare NV - Branch Office Geel Kleinhoefstraat 5 B-2440 Geel Tel: +32 14 57.00.90 Fax: +32 14 58.13.25 http://www.peopleware.be/ http://www.mobileware.be/ - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
