Re: filePermissions ignored during site-deploy with SCP
There is a guide for testing snapshots here [1], but your problem seems related to archiva, you should get better help on the corresponding list. -Lukas [1] http://maven.apache.org/guides/development/guide-testing-development-plugins.html JeremieB wrote: Hi and thanks for reply, I'm trying to test this but fail since now. I added repository for apache snapshots in my archiva proxy connectors list, but now it seems nothing works anymore ... My build downloads .pom and metadata for maven-site-plugin 2.1-SNAPSHOT, but it's not able to download the jar in any way. Installing manually the .jar seem to make things progress, but still my build is not able to download any SNAPSHOT dependency of site-plugin from my archiva server. Logs show only a bunch of Read time out. I really do not understand a thing of what's happening :/ ltheussl wrote: The permission settings in server are not used anymore since maven 2.1 [1]. The chmod command is optional and configurable in the current site-plugin-2.1-SNAPSHOT [2], you can test it eg like chmodModeg+w,a+rX/chmodMode chmodOptions-Rf/chmodOptions Note however that there are some pitholes [3]. HTH, -Lukas [1] http://jira.codehaus.org/browse/MNG-3600 [2] http://jira.codehaus.org/browse/MSITE-141 [3] http://jira.codehaus.org/browse/MSITE-330 - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: filePermissions ignored during site-deploy with SCP
It works now I declared a separate repository in archiva for plugins snapshots. Not sure it was from Archiva, maybe what was missing also is that it was not declared as a pluginRepository in maven. BTW now as expected permissions are managed the way I wanted by site plugin :) -- View this message in context: http://www.nabble.com/filePermissions-ignored-during-site-deploy-with-SCP-tp24804640p24823841.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Profile activation based on current plugin?
Hi all, I'm wondering — is there a way to activate a profile based on the plugin specified on the command line? The reason for this is that I'm working with a cocoon project. Normally, the cocoon plugin gets bound to compile: plugin groupIdorg.apache.cocoon/groupId artifactIdcocoon-maven-plugin/artifactId version1.0.0-M2/version executions execution idprepare/id phasecompile/phase goals goalprepare/goal /goals /execution /executions configuration customLog4jXconfetc/log4j.xml/customLog4jXconf /configuration /plugin However, I only really care that this happens when I invoke mvn jetty:run on the command line. Otherwise, it's just wasted effort. I was thinking that I could make this into a profile, but I'm not sure how. Or if that's even possible. Thanks, -Dom
Re: Profile activation based on current plugin?
Hi, You could activate a profile by -Pprofile flag in comman line. Wont help you? [?] 2009/8/5 Dominic Mitchell d...@semantico.com Hi all, I'm wondering — is there a way to activate a profile based on the plugin specified on the command line? The reason for this is that I'm working with a cocoon project. Normally, the cocoon plugin gets bound to compile: plugin groupIdorg.apache.cocoon/groupId artifactIdcocoon-maven-plugin/artifactId version1.0.0-M2/version executions execution idprepare/id phasecompile/phase goals goalprepare/goal /goals /execution /executions configuration customLog4jXconfetc/log4j.xml/customLog4jXconf /configuration /plugin However, I only really care that this happens when I invoke mvn jetty:run on the command line. Otherwise, it's just wasted effort. I was thinking that I could make this into a profile, but I'm not sure how. Or if that's even possible. Thanks, -Dom -- Alexander
Re: Profile activation based on current plugin?
if you think about this a bit more you will realise that what you are asking for does not make sense (unless you are trying to configure the plugin that you are executing. if you specify a plugin:mojo, then only that plugin:mojo will get executed. Adding other executions of other plugins to a profile and activating that profile will have ZERO effect on what happens, as only the plugin:mojo that you specified will be executed. try telling us a bit more about what your problem is and perhaps somebody can point you towards a solution but it sounds like you really want maven to be more like ant... maven is not ant, if you want ant use ant ;-) -Stephen 2009/8/5 Dominic Mitchell d...@semantico.com Hi all, I'm wondering — is there a way to activate a profile based on the plugin specified on the command line? The reason for this is that I'm working with a cocoon project. Normally, the cocoon plugin gets bound to compile: plugin groupIdorg.apache.cocoon/groupId artifactIdcocoon-maven-plugin/artifactId version1.0.0-M2/version executions execution idprepare/id phasecompile/phase goals goalprepare/goal /goals /execution /executions configuration customLog4jXconfetc/log4j.xml/customLog4jXconf /configuration /plugin However, I only really care that this happens when I invoke mvn jetty:run on the command line. Otherwise, it's just wasted effort. I was thinking that I could make this into a profile, but I'm not sure how. Or if that's even possible. Thanks, -Dom
Re: Profile activation based on current plugin?
On 5 Aug 2009, at 14:10, Stephen Connolly wrote: if you think about this a bit more you will realise that what you are asking for does not make sense (unless you are trying to configure the plugin that you are executing. if you specify a plugin:mojo, then only that plugin:mojo will get executed. Adding other executions of other plugins to a profile and activating that profile will have ZERO effect on what happens, as only the plugin:mojo that you specified will be executed. That's not actually the case. For jetty:run, it executes all phases up to compile before executing jetty:run. try telling us a bit more about what your problem is and perhaps somebody can point you towards a solution but it sounds like you really want maven to be more like ant... maven is not ant, if you want ant use ant ;-) Sorry, I thought I'd been clearer in my original email. -Dom -Stephen 2009/8/5 Dominic Mitchell d...@semantico.com Hi all, I'm wondering — is there a way to activate a profile based on the plugin specified on the command line? The reason for this is that I'm working with a cocoon project. Normally, the cocoon plugin gets bound to compile: plugin groupIdorg.apache.cocoon/groupId artifactIdcocoon-maven-plugin/artifactId version1.0.0-M2/version executions execution idprepare/id phasecompile/phase goals goalprepare/goal /goals /execution /executions configuration customLog4jXconfetc/log4j.xml/customLog4jXconf /configuration /plugin However, I only really care that this happens when I invoke mvn jetty:run on the command line. Otherwise, it's just wasted effort. I was thinking that I could make this into a profile, but I'm not sure how. Or if that's even possible. Thanks, -Dom - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Deployment of classified jar fails to add timestamp
Hello, I have the following use case: 1. artifact is packaging jar 2. jar plugin is configured to add classifier 3. install plugin is forced to version 2.3 because of known issue with installing POMs and attached artifacts MINSTALL-41 4. use custom built 2.5 version of deploy plugin because of MDEPLOY-78 5. pom gets deployed with timestamp 6. artifact with classifier gets deployed with no timestamp (ie. only SNAPSHOT) 7. dependent projects fail getting the artifact Issue is fixed (ie. irrelevant) if uniqueVersion is false on target deployment repository. I could not find a similar issue on jira. WDYT ? Shall I file one ? Am I missing something ? Thanks in advance -- Arnaud Bailly -- OQube software engineering http://www.oqube.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Profile activation based on current plugin?
Sorry — hit send by accident. On 5 Aug 2009, at 14:43, Dominic Mitchell wrote: On 5 Aug 2009, at 14:10, Stephen Connolly wrote: if you think about this a bit more you will realise that what you are asking for does not make sense (unless you are trying to configure the plugin that you are executing. Ok… That does make sense. if you specify a plugin:mojo, then only that plugin:mojo will get executed. Adding other executions of other plugins to a profile and activating that profile will have ZERO effect on what happens, as only the plugin:mojo that you specified will be executed. That's not actually the case. For jetty:run, it executes all phases up to compile before executing jetty:run. Thinking about this, the jetty plugin must be somehow manually be invoking the compile phase. And if I use help:describe, I see: …The plugin forks a parallel lifecycle to ensure that the 'compile' phase has been completed before invoking Jetty. This means that you do not need to explicity execute a 'mvn compile' first… Before this mojo executes, it will call: Phase: 'test-compile' That explains it. try telling us a bit more about what your problem is and perhaps somebody can point you towards a solution but it sounds like you really want maven to be more like ant... maven is not ant, if you want ant use ant ;-) Sorry, I thought I'd been clearer in my original email. I'm trying to avoid calling cocoon:prepare, except in the case of jetty:run. Now I could just not bind cocoon:prepare to the compile phase, but then I have to remember to type two things on the command line. It's not a big deal overall (saving seconds on the non-jetty builds) but it would be nice if I could do it. -Dom
Re: Exploding a ZIP in a resource directory
On Tue, Aug 4, 2009 at 6:57 PM, Alexander the.malk...@gmail.com wrote: You could declare these documentaion as dependecy. Then use dependency plugin for unpacking this module. [?] See http://maven.apache.org/plugins/maven-dependency-plugin/unpack-mojo.html On Tue, Aug 4, 2009 at 8:39 PM, Brian Fox bri...@infinity.nu wrote: http://www.sonatype.com/people/2008/04/how-to-share-resources-across-projects-in-maven/ Well, this isn't quite a shared dependency. The documentation is only for this particular module and is irrelevant anywhere else. Do I need to have the techwriters zip up the documentation and download it into our Maven repository, and then when I do a build, download it, and unzip it? Is it possible to use the maven-dependency-plugin just to merely do the unzipping? Otherwise, I'll have to give our techwriters access to the repository, and let the developers know they have to coordinate the version numbering of the documentation in the pom.xml. Maybe I am better off just using the antrun mojo to do the unzipping during the packing phase. -- David Weintraub qazw...@gmail.com
Re: Exploding a ZIP in a resource directory
Maybe you sould try this http://www.pohlidame.cz/insolvencni-rejstrik/maven-unzip-plugin.html? 2009/8/5 David Weintraub qazw...@gmail.com On Tue, Aug 4, 2009 at 6:57 PM, Alexander the.malk...@gmail.com wrote: You could declare these documentaion as dependecy. Then use dependency plugin for unpacking this module. [?] See http://maven.apache.org/plugins/maven-dependency-plugin/unpack-mojo.html On Tue, Aug 4, 2009 at 8:39 PM, Brian Fox bri...@infinity.nu wrote: http://www.sonatype.com/people/2008/04/how-to-share-resources-across-projects-in-maven/ Well, this isn't quite a shared dependency. The documentation is only for this particular module and is irrelevant anywhere else. Do I need to have the techwriters zip up the documentation and download it into our Maven repository, and then when I do a build, download it, and unzip it? Is it possible to use the maven-dependency-plugin just to merely do the unzipping? Otherwise, I'll have to give our techwriters access to the repository, and let the developers know they have to coordinate the version numbering of the documentation in the pom.xml. Maybe I am better off just using the antrun mojo to do the unzipping during the packing phase. -- David Weintraub qazw...@gmail.com -- Alexander
Re: How to delete a directory?
Thanks. It was a version error. 2.3 did the trick. Alexander wrote: Oh, you right. But you already answered your question! Use excludeDefaultDirectories. It works fine, really. Be sure you use 2.3 version of maven-clean-plugin. (as it mentioned in documentation this option work only since 2.3) plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-clean-plugin/artifactId version2.3/version configuration excludeDefaultDirectoriestrue/excludeDefaultDirectories /configuration /plugin 2009/8/5 Chris she...@yahoo.com mailto:she...@yahoo.com I can delete the directories ok. What I can't do is prevent it from deleting the target directory. Alexander wrote: No maven-clean-plugin is more flexible. Read there http://maven.apache.org/plugins/maven-clean-plugin/examples/delete_additional_files.html 2009/8/5 Chris she...@yahoo.com mailto:she...@yahoo.com mailto:she...@yahoo.com mailto:she...@yahoo.com I'm using maven-dependency-plugin to make a custom directory of dependencies. The trouble is that I can't find a way to delete the outputDirectory before the plugin runs so I can be sure there aren't any old files left over in it. I tried to use maven-clean-plugin to do it, but it insists on deleting the entire /target directory, which I don't want. It looks like there is an excludeDefaultDirectories option available on the command line, but putting excludeDefaultDirectoriestrue/excludeDefaultDirectories in the configuration section doesn't work. Any other suggestions? - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org mailto:users-unsubscr...@maven.apache.org mailto:users-unsubscr...@maven.apache.org mailto:users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org mailto:users-h...@maven.apache.org mailto:users-h...@maven.apache.org mailto:users-h...@maven.apache.org -- Alexander - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org mailto:users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org mailto:users-h...@maven.apache.org -- Alexander - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
validate changes document
Hello all - I'd like to leverage the validate-changes part of the maven-changes-plugin, but no matter what I do, I get this: Caused by: org.apache.maven.plugin.changes.schema.SchemaValidatorException: SAXException : cvc-elt.1: Cannot find the declaration of element 'document'. Even when clearly it has a document element. Any ideas?
Re: validate changes document
Hi, Do you have declared namespaces ? As this : document xmlns=http://maven.apache.org/changes/1.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/changes/1.0.0 http://maven.apache.org/xsd/changes-1.0.0.xsd; -- Olivier 2009/8/5 EJ Ciramella ecirame...@upromise.com: Hello all - I'd like to leverage the validate-changes part of the maven-changes-plugin, but no matter what I do, I get this: Caused by: org.apache.maven.plugin.changes.schema.SchemaValidatorException: SAXException : cvc-elt.1: Cannot find the declaration of element 'document'. Even when clearly it has a document element. Any ideas? -- Olivier - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: validate changes document
Nope, is that needed? And if it is, that should be called out in the site output for the changes plugin... -Original Message- From: Olivier Lamy [mailto:ol...@apache.org] Sent: Wednesday, August 05, 2009 11:28 AM To: Maven Users List Subject: Re: validate changes document Hi, Do you have declared namespaces ? As this : document xmlns=http://maven.apache.org/changes/1.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/changes/1.0.0 http://maven.apache.org/xsd/changes-1.0.0.xsd; -- Olivier 2009/8/5 EJ Ciramella ecirame...@upromise.com: Hello all - I'd like to leverage the validate-changes part of the maven-changes-plugin, but no matter what I do, I get this: Caused by: org.apache.maven.plugin.changes.schema.SchemaValidatorException: SAXException : cvc-elt.1: Cannot find the declaration of element 'document'. Even when clearly it has a document element. Any ideas? -- Olivier - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: validate changes document
Sure namespace declaration is needed if you use validation. 2009/8/5 EJ Ciramella ecirame...@upromise.com: Nope, is that needed? And if it is, that should be called out in the site output for the changes plugin... -Original Message- From: Olivier Lamy [mailto:ol...@apache.org] Sent: Wednesday, August 05, 2009 11:28 AM To: Maven Users List Subject: Re: validate changes document Hi, Do you have declared namespaces ? As this : document xmlns=http://maven.apache.org/changes/1.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/changes/1.0.0 http://maven.apache.org/xsd/changes-1.0.0.xsd; -- Olivier 2009/8/5 EJ Ciramella ecirame...@upromise.com: Hello all - I'd like to leverage the validate-changes part of the maven-changes-plugin, but no matter what I do, I get this: Caused by: org.apache.maven.plugin.changes.schema.SchemaValidatorException: SAXException : cvc-elt.1: Cannot find the declaration of element 'document'. Even when clearly it has a document element. Any ideas? -- Olivier - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Olivier - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [PLEASE TEST] Maven 2.2.1-RC2
I've updated the mavenVersion property on the 2.2.x branch. -john Brett Randall wrote: On Wed, Aug 5, 2009 at 12:21 PM, Brian Fox bri...@infinity.nu wrote: That's an ld bug in the release plugin. It bumps the property to the being released version but doesn't bump it to the next dev version. On Tue, Aug 4, 2009 at 8:41 PM, Brett Randalljavabr...@gmail.com wrote: On Tue, Aug 4, 2009 at 9:49 AM, John Casey jdca...@commonjava.org wrote: Hi again, After Brett sorted out some issues that got lost in the source-control mess on my localhost, and I resolved a couple more stragglers that came up as a result of testing out RC1, I think we're in better shape to attempt a release again. Before we do, I'd like to get as many eyes as possible on this latest release candidate: https://repository.apache.org/content/repositories/maven-staging-008/org/apache/maven/apache-maven/2.2.1-RC2 Please file JIRA issues for anything you come across that still seems broken. The list of issues we've resolved so far for this release is here: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=15328 Thanks! -john --- John Casey Developer and PMC Member, Apache Maven (http://maven.apache.org) Member, Apache Software Foundation What we have to learn to do, we learn by doing. -Aristotle - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org Hi John, in the post 2.2.1-RC2 [maven-release-plugin] prepare for next development iteration, @800602, it looks like the maven-release-plugin has not bumped properties mavenVersion2.2.1-RC2/mavenVersion ... to RC3-SNAPSHOT. Is this a deploy-regression, or am I missing something? This leaves me unable to build 2.2.1-RC3-SNAPSHOT from a clean repo using Maven 2.2.0, due to missing reactor deps on 2.2.1-RC2 https://svn.apache.org/viewvc/maven/maven-2/branches/maven-2.2.x/pom.xml?r1=800600r2=800602diff_format=h https://svn.apache.org/viewvc/maven/maven-2/branches/maven-2.2.x/pom.xml?revision=800602content-type=text%2Fplain Cheers Brett - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org Thanks Brian - I'll bug the current state of the 2.2.x branch then, and see if I can find the release plugin bug you refer to and whether it has regressed or is still open. Cheers BRett - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: Removing: jar from forked lifecycle, to prevent recursive invocation
Removing: jar from forked lifecycle, to prevent recursive invocation I don't know if you are still looking for an answer to how to fix this problem but what I found to fix the problem for me was to change the maven-source-plugin goal from jar to jar-no-fork. I also had to add version2.1/version as well. You may also need to change test-jar to test-jar-no-fork. The information was not immediately obvious to me but http://maven.apache.org/plugins/maven-source-plugin/ Maven Source Plugin Help was where I found the information. Chris McMillan -- View this message in context: http://www.nabble.com/Removing%3A-jar-from-forked-lifecycle%2C-to-prevent-recursive-invocation-tp22054923p24831242.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Default index.html from Site plugin?
Is there some way to get the Site plugin to create an index.html if one is not supplied? I really don't want to have to go set up src/site for every module in my project, but it seems like the site that gets generated won't work if I don't. When I click on one of the module links, I'm taken to the proper URL, only there is no index.html there to be downloaded and displayed. Thanks, Dave - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: [PLEASE TEST] Maven 2.2.1-RC2
http://jira.codehaus.org/browse/MRELEASE-297 On Tue, Aug 4, 2009 at 10:45 PM, Brett Randalljavabr...@gmail.com wrote: On Wed, Aug 5, 2009 at 12:21 PM, Brian Fox bri...@infinity.nu wrote: That's an ld bug in the release plugin. It bumps the property to the being released version but doesn't bump it to the next dev version. On Tue, Aug 4, 2009 at 8:41 PM, Brett Randalljavabr...@gmail.com wrote: On Tue, Aug 4, 2009 at 9:49 AM, John Casey jdca...@commonjava.org wrote: Hi again, After Brett sorted out some issues that got lost in the source-control mess on my localhost, and I resolved a couple more stragglers that came up as a result of testing out RC1, I think we're in better shape to attempt a release again. Before we do, I'd like to get as many eyes as possible on this latest release candidate: https://repository.apache.org/content/repositories/maven-staging-008/org/apache/maven/apache-maven/2.2.1-RC2 Please file JIRA issues for anything you come across that still seems broken. The list of issues we've resolved so far for this release is here: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10500styleName=Htmlversion=15328 Thanks! -john --- John Casey Developer and PMC Member, Apache Maven (http://maven.apache.org) Member, Apache Software Foundation What we have to learn to do, we learn by doing. -Aristotle - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org Hi John, in the post 2.2.1-RC2 [maven-release-plugin] prepare for next development iteration, @800602, it looks like the maven-release-plugin has not bumped properties mavenVersion2.2.1-RC2/mavenVersion ... to RC3-SNAPSHOT. Is this a deploy-regression, or am I missing something? This leaves me unable to build 2.2.1-RC3-SNAPSHOT from a clean repo using Maven 2.2.0, due to missing reactor deps on 2.2.1-RC2 https://svn.apache.org/viewvc/maven/maven-2/branches/maven-2.2.x/pom.xml?r1=800600r2=800602diff_format=h https://svn.apache.org/viewvc/maven/maven-2/branches/maven-2.2.x/pom.xml?revision=800602content-type=text%2Fplain Cheers Brett - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org Thanks Brian - I'll bug the current state of the 2.2.x branch then, and see if I can find the release plugin bug you refer to and whether it has regressed or is still open. Cheers BRett - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Release from branch - Subversion is not happy.
I am getting this error when attempting to release:prepare from a branch: Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Commit failed (details follow): svn: Source url 'svn://svn.enttek.com/allureglobal/dm/branches/salient-0.9.22' is from different repository I've seen Subversion complain about URLs not matching before, but that was always when checking into the same portion of the repository. In this case, I assume that the maven-release-plugin is attempting to create a new tag in the tags area. My command line is: mvn --batch-mode -DpreparationGoals=clean install release:prepare Any ideas how I can get this working? I'm unable to release a branch for testing because of this error. Thanks, Dave - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: archetype plug-in vs custom plug-in
Search around a lot for this type of functionality but I ended up writing my own plugin to do this. Murali Pottlapelli wrote: Hi All, While searching through mailing list I found archetypes to add files to an existing project, http://www.nabble.com/Using-Archetypes-to-Add-to-an-Existing-Project-(Maven-2)-ts1274662.html#a1274662 This message is at least 3 years old, did this feature evolve? This feature might help in my work. I need to generate/add artifact(s) to a module based on the meta data user configures. I like to define an archetype to generate multi-module project, when project is created from this archetype it creates parent project with POM file and meta data/configuration file. Meta data in configuration file determine number of submodules, and artifacts created in the parent project. Let us look at my request using an example. maven-archetype-j2ee-simple creates JavaEE multi module project with sub modules ear, ejbs, servelets etc. by default all the sub-modules are empty. I need little variation of it, like to generate configuration file in src\main\resources. This file is edited/configured by user, configuration is input to create/edit/add artifacts to sub-modules. Does archetype plug-in help? or shall I write my own plug-in? Regards Murali -- View this message in context: http://www.nabble.com/archetype-plug-in-vs-custom-plug-in-tp24765503p24837613.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Help with multimodule app
Oh, already solved. [?] 2009/8/6 Alexander the.malk...@gmail.com My project X have three modules A, B, C. Module C depends on A and B. I declared A, B, C pom files inherit X pom file. I declared A, B, C as modules in X pom file. Declared A and B as dependencies for C. Cant generate idea project with mvn idea:idea - seems like C cant find A and B dependencies and tries to resolve them from repo. Maybe Im doing something wrong? -- Alexander -- Alexander
Re: Default index.html from Site plugin?
Are you running into this? http://maven.apache.org/plugins/maven-site-plugin/faq.html#Why_dont_the_links_between_parent_and_child_modules_work_when_I_run_mvn_site David C. Hicks wrote: Is there some way to get the Site plugin to create an index.html if one is not supplied? I really don't want to have to go set up src/site for every module in my project, but it seems like the site that gets generated won't work if I don't. When I click on one of the module links, I'm taken to the proper URL, only there is no index.html there to be downloaded and displayed. Thanks, Dave - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Dennis Lundberg - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Default index.html from Site plugin?
No, I'm actually looking at a deployed site. mvn site site:deploy There are simply no index.html files in any of the modules' directories. Dennis Lundberg wrote: Are you running into this? http://maven.apache.org/plugins/maven-site-plugin/faq.html#Why_dont_the_links_between_parent_and_child_modules_work_when_I_run_mvn_site David C. Hicks wrote: Is there some way to get the Site plugin to create an index.html if one is not supplied? I really don't want to have to go set up src/site for every module in my project, but it seems like the site that gets generated won't work if I don't. When I click on one of the module links, I'm taken to the proper URL, only there is no index.html there to be downloaded and displayed. Thanks, Dave - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Maven Webstart Plugin - unprocessed POM in WAR
I have a Webstart application that I'm generating a WAR file to deploy on JBoss using the Maven Webstart plugin. I have included the JBoss client POM in my application POM to grab the JBoss client dependencies for JNDI and EJB. When the plugin creates the WAR file, it is including the POM with unprocessed_ prepended to the file name. The plugin is also putting the POM in as a jar dependency in the JNLP file. So when the JNLP download servlet goes to pull the JAR dependencies for my webstart application, it tries to grab the POM, which has been renamed, and fails. Does anyone know why that file is getting renamed? I saw some emails about JARs getting unprocessed stuck in the name when signing is turned off. It appears that the plugin isn't designed for POM dependencies. Here's the JBoss client dependency in my webstart application's POM: dependency groupIdorg.jboss.jbossas/groupId artifactIdjboss-as-client/artifactId version5.0.1.GA/version scopecompile/scope typepom/type /dependency I included that POM because it has dependencies to the client JARs I need to call over to JBoss. Reference - https://jira.jboss.org/jira/browse/JBAS-6320 Here's the webstart plugin config from my WAR POM: plugins plugin groupIdorg.codehaus.mojo.webstart/groupId artifactIdwebstart-maven-plugin/artifactId executions execution phaseprocess-resources/phase goals goaljnlp-download-servlet/goal /goals /execution /executions configuration outputDirectoryNameapplication/outputDirectoryName outputFilenamelaunch.jnlp/outputFilename jnlpFiles jnlpFile templateFilenamejnlp-template.vm/templateFilename jarResources jarResource groupIdcom.usairways.cbro/groupId artifactIdreal-time-departure-swing/artifactId version1.0.0.a2/version mainClasscom.usairways.cbro.rtd.swing.Main/mainClass /jarResource /jarResources /jnlpFile /jnlpFiles /configuration /plugin /plugins How can I get it to not rename the jboss-as-client POM to unprocessed_jboss-as-client? Or alternatively, how do I keep it from adding the jboss-as-client POM as a JAR dependency in the JNLP, but keep the transitive dependencies of the jboss-as-client POM in there? -- View this message in context: http://www.nabble.com/Maven-Webstart-Plugin---unprocessed-POM-in-WAR-tp24838690p24838690.html Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
RE: validate changes document
That should be clarified in the documentation and in the error. Saying it can't find the document element is NOT enough to diagnose this error. -Original Message- From: Olivier Lamy [mailto:ol...@apache.org] Sent: Wednesday, August 05, 2009 11:36 AM To: Maven Users List Subject: Re: validate changes document Sure namespace declaration is needed if you use validation. 2009/8/5 EJ Ciramella ecirame...@upromise.com: Nope, is that needed? And if it is, that should be called out in the site output for the changes plugin... -Original Message- From: Olivier Lamy [mailto:ol...@apache.org] Sent: Wednesday, August 05, 2009 11:28 AM To: Maven Users List Subject: Re: validate changes document Hi, Do you have declared namespaces ? As this : document xmlns=http://maven.apache.org/changes/1.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/changes/1.0.0 http://maven.apache.org/xsd/changes-1.0.0.xsd; -- Olivier 2009/8/5 EJ Ciramella ecirame...@upromise.com: Hello all - I'd like to leverage the validate-changes part of the maven-changes-plugin, but no matter what I do, I get this: Caused by: org.apache.maven.plugin.changes.schema.SchemaValidatorException: SAXException : cvc-elt.1: Cannot find the declaration of element 'document'. Even when clearly it has a document element. Any ideas? -- Olivier - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org -- Olivier - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Release from branch - Subversion is not happy.
On Thu, Aug 6, 2009 at 5:53 AM, David C. Hicks dhi...@i-hicks.org wrote: I am getting this error when attempting to release:prepare from a branch: Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Commit failed (details follow): svn: Source url 'svn://svn.enttek.com/allureglobal/dm/branches/salient-0.9.22' is from different repository I've seen Subversion complain about URLs not matching before, but that was always when checking into the same portion of the repository. In this case, I assume that the maven-release-plugin is attempting to create a new tag in the tags area. My command line is: mvn --batch-mode -DpreparationGoals=clean install release:prepare Any ideas how I can get this working? I'm unable to release a branch for testing because of this error. Thanks, Dave - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org What are your SCM URLs? This has come up before when a username was included in the SCM URL. Google finds this: http://www.mail-archive.com/users@maven.apache.org/msg74843.html . Best Brett
Re: Exploding a ZIP in a resource directory
2009/8/5 David Weintraub qazw...@gmail.com: On Tue, Aug 4, 2009 at 6:57 PM, Alexander the.malk...@gmail.com wrote: You could declare these documentaion as dependecy. Then use dependency plugin for unpacking this module. See http://maven.apache.org/plugins/maven-dependency-plugin/unpack-mojo.html On Tue, Aug 4, 2009 at 8:39 PM, Brian Fox bri...@infinity.nu wrote: http://www.sonatype.com/people/2008/04/how-to-share-resources-across-projects-in-maven/ Well, this isn't quite a shared dependency. The documentation is only for this particular module and is irrelevant anywhere else. Doesn't matter really, the process is still the same... Do I need to have the techwriters zip up the documentation and download it into our Maven repository, and then when I do a build, download it, and unzip it? If they zip it and publish it to the repo yes...but they will probably do that using the assembly plugin like I showed in the blog... Is it possible to use the maven-dependency-plugin just to merely do the unzipping? Otherwise, I'll have to give our techwriters access to the repository, and let the developers know they have to coordinate the version numbering of the documentation in the pom.xml. Yes, that's what the dependency plugin does, it either copies the file or unpacks it. Maybe I am better off just using the antrun mojo to do the unzipping during the packing phase. The dependency plugin does the same thing without ant. -- David Weintraub qazw...@gmail.com - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Re: Release from branch - Subversion is not happy.
Thanks, Brett. That's exactly what the problem was. I found it about an hour after I left the original email. I thought I had cleared all of them out a week or two ago. Turns out that the branch was taken prior to that. It certainly was not easy to spot. Dave Brett Randall wrote: On Thu, Aug 6, 2009 at 5:53 AM, David C. Hicks dhi...@i-hicks.org wrote: I am getting this error when attempting to release:prepare from a branch: Unable to tag SCM Provider message: The svn tag command failed. Command output: svn: Commit failed (details follow): svn: Source url 'svn://svn.enttek.com/allureglobal/dm/branches/salient-0.9.22' is from different repository I've seen Subversion complain about URLs not matching before, but that was always when checking into the same portion of the repository. In this case, I assume that the maven-release-plugin is attempting to create a new tag in the tags area. My command line is: mvn --batch-mode -DpreparationGoals=clean install release:prepare Any ideas how I can get this working? I'm unable to release a branch for testing because of this error. Thanks, Dave - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org What are your SCM URLs? This has come up before when a username was included in the SCM URL. Google finds this: http://www.mail-archive.com/users@maven.apache.org/msg74843.html . Best Brett
