Re: [c-1.1] Can't edit project notifiers?
On Dec 3, 2007 6:08 PM, Mick Knutson [EMAIL PROTECTED] wrote: I have had to add an additional project notifier because the default one does not allow me to edit it. How can I edit, or how does Continuum assign the recipient to the default notifier? PROJECT NAME Type Recipient Events Tools http://rc-sun66e.ut.dentegra.lab:8080/continuum/projectView.action?projectId=61 mail unknown Error/Failure/Success/Warning [image: Edit] [image: Delete] Tools http://rc-sun66e.ut.dentegra.lab:8080/continuum/projectView.action?projectId=61 mail [EMAIL PROTECTED], latest committers Error/Failure/Success/Warning [image: Edit] http://rc-sun66e.ut.dentegra.lab:8080/continuum/editProjectNotifier.action?projectId=61notifierType=mailfromGroupPage=trueprojectGroupId=6notifierId=408 [image: Delete] http://rc-sun66e.ut.dentegra.lab:8080/continuum/deleteProjectNotifier.action?projectId=61confirmed=falsefromGroupPage=trueprojectGroupId=6notifierId=408 WAR Archetype http://rc-sun66e.ut.dentegra.lab:8080/continuum/projectView.action?projectId=67 mail unknown Error/Failure/Success/Warning [image: Edit] [image: Delete] I also added this to my master pom: ciManagement systemcontinuum/system urlhttp://rc-sun66e.ut.dentegra.lab:8080/continuum/url notifiers notifier typemail/type sendOnErrortrue/sendOnError sendOnFailuretrue/sendOnFailure sendOnSuccesstrue/sendOnSuccess sendOnWarningtrue/sendOnWarning address[EMAIL PROTECTED]/address /notifier /notifiers /ciManagement But that did not seem to help Or must I restart Continuum for that to take affect? -- Thanks, Mick Knutson http://www.baselogic.com http://www.blincmagazine.com http://www.djmick.com http://www.myspace.com/mickknutson http://www.myspace.com/BLiNCMagazine http://tahoe.baselogic.com --- There are two groups of notifiers, first that can be defined in project POM and could not be edited in Continuum, and second that can be defined in Continuum. That is probably the reason that you was not able to edit the notifier - it was defined in you POM. If make any changes into any POM, it is necessary to remove appropriate POM from maven repository used by Continuum. When Continuum updates project from SCM it will update all informations from project POM. Tonda Faltynek
Re: Upgrade from Continuum 1.0.3 to 1.1
Toli, Let me know if you've figured out a way to migrate from 1.0.3 to 1.1. i'd be interested to know. Well I gave up pretty quickly, and worked around the problem by having both versions up at the same time, and copy/pasted all the info from 1.0.3 to 1.1. Fortunately this wasn't a big job for me because I've only got about 12 builds. It does of course mean that I have lost all my history, but that's not too serious. You can fairly easily look at the underlying databases, using for example, SQuirrel SQL Client, and you might be able to figure out a way of transferring the data from 1.0.3 to 1.1 using SQL. Good luck! Ken -- View this message in context: http://www.nabble.com/Upgrade-from-Continuum-1.0.3-to-1.1-tf4897583.html#a14187547 Sent from the Continuum - Users mailing list archive at Nabble.com.
Re: [m2] activeProfile overriding
Mick Knutson [EMAIL PROTECTED] writes: Is there a way to activate a profile only if there was not one specified on the command line? ActiveByDefault seems to always be active no matter what. I vaguely recall that you could use -P+profile et -P-profile to forcefully include/exclude profiles. Is this something I dreamt of (I cannot reproduce it in 2.0.7)? -- OQube software engineering \ génie logiciel Arnaud Bailly, Dr. \web http://www.oqube.com - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: custom manifest file still using dependencies
Aha! rooting around for a bit, there is classpathprefix which prepends the lib part to each dependency. I'd have hoped that would be on the plugin homepage :( Cheers, Rich From: Richard Chamberlain [mailto:[EMAIL PROTECTED] Sent: Tue 04/12/2007 19:58 To: users@maven.apache.org Subject: custom manifest file still using dependencies Hi, I'm packaging my app in a zip. However if i want to use java -jar myapp.jar i have to include the dependencies in my manifest file. I've done this using: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId configuration archive manifest mainClass myapp.MainClass /mainClass addClasspathtrue/addClasspath /manifest /archive /configuration /plugin However there are 20 dependencies and the manifest file requires them to be in the same directory. I'd like to put all my dependencies in a lib folder and have my manifest file locate them. It's neat that the manifest file gets generated from the dependecies, so i dont want to maintain my own manifest file. Ialso like the way that the dependencies are external to the jar. Can anyone help? Thanks, Rich - 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]
How to easily determine all the versions of plugins that are being used.
I remember seeing something (perhaps in a dream) about a nice easy way to get a list of all the versions of the plugins that are being resolved currently. I know the enforcer plugin has the ability (in theory) of locking down plugin versions. But given that the last released version of that plugin does not include the requirePluginVersions rule (as far as I can see... i.e. blows up every time!) I am at a loss as to how to easily lock down the plugin versions... Perhaps somebody could push a release of the enforcer plugin and the working version will produce a list like: the following versions are resolving but not specified. Or perhaps there's some magic plugin elsewhere that gives this info -Stephen - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: New to Maven, and got frustrated the first time to use it...HELP...
Kevin Tse wrote: Below there are the messages I got when trying to create a Maven project. Please help, your reply will be greatly appreciated. -- D:\Workspace\MavenPrjmvn archetype:create -DgroupId=org.kevin.mavendemo -Dartif act=app [snip] [INFO] Parameter: artifactId, Value: null [snip] Embedded error: Artifact ID must be specified when creating a new project from a n archetype. Looks like maven doesn't see the artifact ID you specified. Looking at your command line, I suspect the command line option is supposed to be -DartifactId=app, double check the docs for the archetype plugin to be sure. Regards, Graham -- smime.p7s Description: S/MIME Cryptographic Signature
Re: New to Maven, and got frustrated the first time to use it...HELP...
On 05/12/2007, Kevin Tse [EMAIL PROTECTED] wrote: Below there are the messages I got when trying to create a Maven project. Please help, your reply will be greatly appreciated. try -DartifactId=app rather than -Dartifact=app -- D:\Workspace\MavenPrjmvn archetype:create -DgroupId=org.kevin.mavendemo -Dartif act=app [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] [INFO] Building Maven Default Project [INFO]task-segment: [archetype:create] (aggregator-style) [INFO] [INFO] Setting property: classpath.resource.loader.class = 'org.codehaus.plexus .velocity.ContextClassLoaderResourceLoader'. [INFO] Setting property: velocimacro.messages.on = 'false'. [INFO] Setting property: resource.loader = 'classpath'. [INFO] Setting property: resource.manager.logwhenfound = 'false'. [INFO] ** [INFO] Starting Jakarta Velocity v1.4 [INFO] RuntimeInstance initializing. [INFO] Default Properties File: org\apache\velocity\runtime\defaults\velocity.pr operties [INFO] Default ResourceManager initializing. (class org.apache.velocity.runtime. resource.ResourceManagerImpl) [INFO] Resource Loader Instantiated: org.codehaus.plexus.velocity.ContextClassLo aderResourceLoader [INFO] ClasspathResourceLoader : initialization starting. [INFO] ClasspathResourceLoader : initialization complete. [INFO] ResourceCache : initialized. (class org.apache.velocity.runtime.resource. ResourceCacheImpl) [INFO] Default ResourceManager initialization complete. [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Literal [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Macro [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Parse [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Include [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Foreach [INFO] Created: 20 parsers. [INFO] Velocimacro : initialization starting. [INFO] Velocimacro : adding VMs from VM library template : VM_global_library.vm [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in any resource loader. [INFO] Velocimacro : error using VM library template VM_global_library.vm : org .apache.velocity.exception.ResourceNotFoundException: Unable to find resource 'V M_global_library.vm' [INFO] Velocimacro : VM library template macro registration complete. [INFO] Velocimacro : allowInline = true : VMs can be defined inline in templates [INFO] Velocimacro : allowInlineToOverride = false : VMs defined inline may NOT replace previous VM definitions [INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will be glob al in scope if allowed. [INFO] Velocimacro : initialization complete. [INFO] Velocity successfully started. [INFO] [archetype:create] [INFO] Defaulting package to group ID: org.kevin.mavendemo [INFO] - --- [INFO] Using following parameters for creating Archetype: maven-archetype-quicks tart:RELEASE [INFO] - --- [INFO] Parameter: groupId, Value: org.kevin.mavendemo [INFO] Parameter: packageName, Value: org.kevin.mavendemo [INFO] Parameter: package, Value: org.kevin.mavendemo [INFO] Parameter: artifactId, Value: null [INFO] Parameter: basedir, Value: D:\Workspace\MavenPrj [INFO] Parameter: version, Value: 1.0-SNAPSHOT [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error creating from archetype Embedded error: Artifact ID must be specified when creating a new project from a n archetype. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Wed Dec 05 18:37:46 CST 2007 [INFO] Final Memory: 5M/9M [INFO] -- View this message in context: http://www.nabble.com/New-to-Maven%2C-and-got-frustrated-the-first-time-to-use-it...HELP...-tf4948806s177.html#a14169257 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Cheers, Stuart
New to Maven, and got frustrated the first time to use it...HELP...
Below there are the messages I got when trying to create a Maven project. Please help, your reply will be greatly appreciated. -- D:\Workspace\MavenPrjmvn archetype:create -DgroupId=org.kevin.mavendemo -Dartif act=app [INFO] Scanning for projects... [INFO] Searching repository for plugin with prefix: 'archetype'. [INFO] [INFO] Building Maven Default Project [INFO]task-segment: [archetype:create] (aggregator-style) [INFO] [INFO] Setting property: classpath.resource.loader.class = 'org.codehaus.plexus .velocity.ContextClassLoaderResourceLoader'. [INFO] Setting property: velocimacro.messages.on = 'false'. [INFO] Setting property: resource.loader = 'classpath'. [INFO] Setting property: resource.manager.logwhenfound = 'false'. [INFO] ** [INFO] Starting Jakarta Velocity v1.4 [INFO] RuntimeInstance initializing. [INFO] Default Properties File: org\apache\velocity\runtime\defaults\velocity.pr operties [INFO] Default ResourceManager initializing. (class org.apache.velocity.runtime. resource.ResourceManagerImpl) [INFO] Resource Loader Instantiated: org.codehaus.plexus.velocity.ContextClassLo aderResourceLoader [INFO] ClasspathResourceLoader : initialization starting. [INFO] ClasspathResourceLoader : initialization complete. [INFO] ResourceCache : initialized. (class org.apache.velocity.runtime.resource. ResourceCacheImpl) [INFO] Default ResourceManager initialization complete. [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Literal [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Macro [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Parse [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Include [INFO] Loaded System Directive: org.apache.velocity.runtime.directive.Foreach [INFO] Created: 20 parsers. [INFO] Velocimacro : initialization starting. [INFO] Velocimacro : adding VMs from VM library template : VM_global_library.vm [ERROR] ResourceManager : unable to find resource 'VM_global_library.vm' in any resource loader. [INFO] Velocimacro : error using VM library template VM_global_library.vm : org .apache.velocity.exception.ResourceNotFoundException: Unable to find resource 'V M_global_library.vm' [INFO] Velocimacro : VM library template macro registration complete. [INFO] Velocimacro : allowInline = true : VMs can be defined inline in templates [INFO] Velocimacro : allowInlineToOverride = false : VMs defined inline may NOT replace previous VM definitions [INFO] Velocimacro : allowInlineLocal = false : VMs defined inline will be glob al in scope if allowed. [INFO] Velocimacro : initialization complete. [INFO] Velocity successfully started. [INFO] [archetype:create] [INFO] Defaulting package to group ID: org.kevin.mavendemo [INFO] - --- [INFO] Using following parameters for creating Archetype: maven-archetype-quicks tart:RELEASE [INFO] - --- [INFO] Parameter: groupId, Value: org.kevin.mavendemo [INFO] Parameter: packageName, Value: org.kevin.mavendemo [INFO] Parameter: package, Value: org.kevin.mavendemo [INFO] Parameter: artifactId, Value: null [INFO] Parameter: basedir, Value: D:\Workspace\MavenPrj [INFO] Parameter: version, Value: 1.0-SNAPSHOT [INFO] [ERROR] BUILD ERROR [INFO] [INFO] Error creating from archetype Embedded error: Artifact ID must be specified when creating a new project from a n archetype. [INFO] [INFO] For more information, run Maven with the -e switch [INFO] [INFO] Total time: 1 second [INFO] Finished at: Wed Dec 05 18:37:46 CST 2007 [INFO] Final Memory: 5M/9M [INFO] -- View this message in context: http://www.nabble.com/New-to-Maven%2C-and-got-frustrated-the-first-time-to-use-it...HELP...-tf4948806s177.html#a14169257 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
site.xml absolute href are replaced by relative path.
Hi, all There is a behavior of maven that I don't understand. If I put a non relative href for menu item of the site.xml file, like this : menu name=test-menu item name=Fractal Homepage href=http://test-url.com/; / /menu I don't know why, when I generate the site (mvn site), the href is replaced by the relative path ../../../. Is it possible, and if yes how can I put external item with external href in the menu section and display it correcly on the pages generated during the mvn site phase ? (ps: I don't want to use the site:stage) Thanks. Yann -- View this message in context: http://www.nabble.com/site.xml-absolute-href-are-replaced-by-relative-path.-tf4949277s177.html#a14170497 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: New to Maven, and got frustrated the first time to use it...HELP...
Graham Leggett wrote: Kevin Tse wrote: Below there are the messages I got when trying to create a Maven project. Please help, your reply will be greatly appreciated. -- D:\Workspace\MavenPrjmvn archetype:create -DgroupId=org.kevin.mavendemo -Dartif act=app [snip] [INFO] Parameter: artifactId, Value: null [snip] Embedded error: Artifact ID must be specified when creating a new project from a n archetype. Looks like maven doesn't see the artifact ID you specified. Looking at your command line, I suspect the command line option is supposed to be -DartifactId=app, double check the docs for the archetype plugin to be sure. Regards, Graham -- Thank you so much, Graham, the problem solved, it is the command line option that I typed incorrectly...Thanks. -- View this message in context: http://www.nabble.com/New-to-Maven%2C-and-got-frustrated-the-first-time-to-use-it...HELP...-tf4948806s177.html#a14170495 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How can I include pom.xml dependencies in output jar???
I'm trying to create a SAR file, and like to include some of dependency, is it possible ? as the assembly did not recognize 'sar' format. I'm using maven-sar-plugin Ali Sakebi wrote: Hi Can some one plz guide me how can I make maven to include dependencies defined in pom.xml in output jar file??? Regards, Ali - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/How-can-I-include-pom.xml-dependencies-in-output-jartf3839626s177.html#a14168479 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Dashboard plugin/aggregate report and site plugin.
HI, i'm the dashboard project leader. Your experience is very valuable. To improve the usage documentation, you can post a JIRA issue with your experience and share your problem and your solution to solve it ? No? Thxs David emerson cargnin wrote: Hi guys, after a long while I got the dashboard to work, although the usage page is really misleading. I put here ( http://echofloripa.blogspot.com/2007/12/maven2-dashboard-plugin.html ) a how-to on how make the basic feature of it to work, as in there the plugin version is missing on the pom and on the dashboard maven command. The dashboard plugin when using aggragate report, the link to submodules doesn't work when they have a '.' on it. Aparently it gets clipped after the dot. Also, I got a bit deceptive as I expected the site and dashboard plugin to be stable enough in maven2. The site plugin for multimodules projects don't work as expected/advertised, for example, the command : -mvn site:stage Alright that site:site doesn't work as m1, it's said in the faq also. But the site:stage command, which the faq tells is the right way to get the muilti-module site structure together. Well it just doesn't happen and someone on the maven IRC channel said it has issues. Don't want to start fud here, I'm just a bit down as I've been advertising a lot maven 2 to substitute maven1 where I work, using as main arguments that maven 2 is much more stable and mature. But i see it's not quite the case. I really hope I'm wrong. Emerson - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Dashboard-plugin-aggregate-report-and-site-plugin.-tf4949325s177.html#a14171947 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
auto-deploy 3rd party files
Hi, I see that people use mvn deploy:deploy-file to put ONE jar into a remote repository. Or with an ant task, can say the path of some file to deploy too. But what happend if a proyect have 100 3rd party jars? we must do 100 deploy-file ?? There is some way..to tell maven that must find the necessary jars to run a project and deploy all the same time? thanks a lot -- View this message in context: http://www.nabble.com/auto-deploy-3rd-party-files-tf4949608s177.html#a14171500 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Dashboard plugin/aggregate report and site plugin.
Hi guys, after a long while I got the dashboard to work, although the usage page is really misleading. I put here ( http://echofloripa.blogspot.com/2007/12/maven2-dashboard-plugin.html ) a how-to on how make the basic feature of it to work, as in there the plugin version is missing on the pom and on the dashboard maven command. The dashboard plugin when using aggragate report, the link to submodules doesn't work when they have a '.' on it. Aparently it gets clipped after the dot. Also, I got a bit deceptive as I expected the site and dashboard plugin to be stable enough in maven2. The site plugin for multimodules projects don't work as expected/advertised, for example, the command : -mvn site:stage Alright that site:site doesn't work as m1, it's said in the faq also. But the site:stage command, which the faq tells is the right way to get the muilti-module site structure together. Well it just doesn't happen and someone on the maven IRC channel said it has issues. Don't want to start fud here, I'm just a bit down as I've been advertising a lot maven 2 to substitute maven1 where I work, using as main arguments that maven 2 is much more stable and mature. But i see it's not quite the case. I really hope I'm wrong. Emerson - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Include library (jar file) in sar
Use the copy goal from the dependency plugin: http://maven.apache.org/plugins/maven-dependency-plugin/usage.html ferry97 wrote: Hi, I need to put a jar file in a sar file, myfile.sar +-- com (classes) +-- lib +-- mylib.jar +-- META-INF +-- jboss-service.xml I have search everywhere but I can not find a plug-in that can do the job (adding a jar file). Does anyone know how to do it ? Perhaps I miss something. Thanks. Regards, Ferry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
dashboard and site plugin
Hi guys, after a long while I got the dashboard to work, although the usage page is really misleading. I put here ( http://echofloripa.blogspot.com/2007/12/maven2-dashboard-plugin.html ) a how-to on how make the basic feature of it to work, as in there the plugin version is missing on the pom and on the dashboard maven command. The dashboard plugin when using aggragate report, the link to submodules doesn't work when they have a '.' on it. Aparently it gets clipped after the dot. Also, I got a bit deceptive as I expected the site and dashboard plugin to be stable enough in maven2. The site plugin for multimodules projects don't work as expected/advertised, for example, the command : -mvn site:stage Alright that site:site doesn't work as m1, it's said in the faq also. But the site:stage command, which the faq tells is the right way to get the muilti-module site structure together. Well it just doesn't happen and someone on the maven IRC channel said it has issues. Don't want to start fud here, I'm just a bit down as I've been advertising a lot maven 2 to substitute maven1 where I work, using as main arguments that maven 2 is much more stable and mature. But i see it's not quite the case. I really hope I'm wrong. Emerson - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
URL's from master POM
Hello,
i am managing multiple projects form y company using maven 2.0.7. For
that purpose I have created a master pom, that contains the following
section: (Pom A)
...
modelVersion4.0.0/modelVersion
groupIdcom.sonicsw.pso/groupId
artifactIdsonic-maven-parent/artifactId
version1.0/version
packagingpom/packaging
nameMaven Definitions for all Sonic PSO projects/name
urlhttps://www.soa-knowledge.net/projects/${urlGroup}/${urlId}/${proje
ct.version}/${urlId}/url
properties
urlGroup${project.groupId}/urlGroup
urlId${project.artifactId}/urlId
/properties
...
From that I have inherited another pom (POM B), that does not specify
anything for an URL and serves as a base for a part of my projects. That
pom has the following coordinates:
...
modelVersion4.0.0/modelVersion
groupIdcom.sonicsw.pso/groupId
artifactIdservices-maven-parent/artifactId
version1.0/version
packagingpom/packaging
nameMaven Definitions for all Sonic ESB Services/name
parent
groupIdcom.sonicsw.pso/groupId
artifactIdsonic-maven-parent/artifactId
version1.0/version
/parent
...
My project now inherits from POM B, which in turn inherits from POM A.
parent
groupIdcom.sonicsw.pso/groupId
artifactIdservices-maven-parent/artifactId
version1.0/version
/parent
groupIdcom.sonicsw.pso.services/groupId
artifactIdWSMQService/artifactId
packagingjar/packaging
version1.0-SNAPSHOT/version
nameWebsphere MQ connectivity services/name
My problem is now in the definition of URLS (for automatically
generating web urls, scm urls, ftp urls etc...)
When I define no url in my project, the generated url is:
https://www.soa-knowledge.net/projects/com.sonicsw.pso.services/WSMQServ
ice/1.0-SNAPSHOT/WSMQService/services-maven-parent/WSMQService
However, if I add the url definition into my project
parent
groupIdcom.sonicsw.pso/groupId
artifactIdservices-maven-parent/artifactId
version1.0/version
/parent
groupIdcom.sonicsw.pso.services/groupId
artifactIdWSMQService/artifactId
packagingjar/packaging
version1.0-SNAPSHOT/version
nameWebsphere MQ connectivity services/name
urlhttps://www.soa-knowledge.net/projects/${urlGroup}/${urlId}/${proje
ct.version}/${urlId}/url
the url is
https://www.soa-knowledge.net/projects/com.sonicsw.pso.services/WSMQServ
ice/1.0-SNAPSHOT/WSMQService
which is what I intended.
I would like to avoid repeating the URL definitions in each sub project
since this is what I had created the masters for in the first place.
Could somebody explain the behaviour here ? - Can the append be avoided
?
Thank you very much in advance
Andreas
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: custom manifest file still using dependencies
You are welcome to post a bug in JIRA or offer up a documentation patch if you feel this would be beneficial for other users. Wayne On 12/5/07, Richard Chamberlain [EMAIL PROTECTED] wrote: Aha! rooting around for a bit, there is classpathprefix which prepends the lib part to each dependency. I'd have hoped that would be on the plugin homepage :( Cheers, Rich From: Richard Chamberlain [mailto:[EMAIL PROTECTED] Sent: Tue 04/12/2007 19:58 To: users@maven.apache.org Subject: custom manifest file still using dependencies Hi, I'm packaging my app in a zip. However if i want to use java -jar myapp.jar i have to include the dependencies in my manifest file. I've done this using: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-jar-plugin/artifactId configuration archive manifest mainClass myapp.MainClass /mainClass addClasspathtrue/addClasspath /manifest /archive /configuration /plugin However there are 20 dependencies and the manifest file requires them to be in the same directory. I'd like to put all my dependencies in a lib folder and have my manifest file locate them. It's neat that the manifest file gets generated from the dependecies, so i dont want to maintain my own manifest file. Ialso like the way that the dependencies are external to the jar. Can anyone help? Thanks, Rich - 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: Maven 2.0.6 - Windows - SVN question
Hello AFAIK, on windows if a file is opened (in editor or IDE) the write access to it is denied, and release plugin needs write access. Did you have the file below opened in some editor? The permission denied insinuates that. ~t~ On Dec 4, 2007 4:41 PM, Váry Péter [EMAIL PROTECTED] wrote: Hi, I have a setup, where I use maven 2.0.6 with svn for source control. I have a project which I want to release. The effective pom attached at the bottom. I can release it with: 'mvn release:prepare;mvn release:preform' on a debian linux box, but on Windows XP machines the 'mvn release:prepare' fails with the following message: [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Unable to commit files Provider message: The svn command failed. Command output: svn: Commit succeeded, but other errors follow: svn: Error bumping revisions post-commit (details follow): svn: In directory 'C:\temp\kl\modules\util\trunk' svn: Error processing command 'committed' in 'C:\temp\kl\modules\util\trunk' svn: Error replacing text-base of 'pom.xml' svn: Can't move 'C:\temp\kl\modules\util\trunk\.svn\tmp\pom.xml.tmp' to 'C:\temp\kl\modules\util\trunk\pom.xml': A hozzáférés megtagadva. The last part A hozzáférés megtagadva. means - permission denied. If I run the 'mvn release:prepare' again, I get the following message: [INFO] [ERROR] BUILD FAILURE [INFO] [INFO] Unable to commit files Provider message: The svn command failed. Command output: svn: Working copy 'C:\temp\kl\modules\util\trunk' locked svn: run 'svn cleanup' to remove locks (type 'svn help cleanup' for details) Type 'svn help' for usage. If I run the 'svn cleanup' again, and then 'mvn release:prepare' then everything seems ok. Can anybody help me, what is the problem with my settings? Thanks, Peter
Maven pulling down the wrong plugin
Greetings First off apologies if this sort of issue has been answered before. I did as thorough a search as I could and couldn't find anything resembling it. Am attempting to use Clover for code coverage. I've set up the pom and settings as instructed by the atlassian folks (http://confluence.atlassian.com/display/CLOVER/Clover-for-Maven+2+Use r%27s+Guide). Details of this are at the end of this email. Atlassian support has verified that things are set up correctly. When I do a myriad of maven tasks (clean, package, whatever), the correct Clover maven plugin (3.6) is pulled down from their repository from the atlassian repository from the correct directory(com\atlassian\maven\plugins). However, when I attempt to perform a Clover goal (in this case, clover:instrument), maven goes thru all sorts of machinations and then pulls down an old plugin (2.4.1) from the wrong directory (org/apache/maven/plugins). It then horks. The ultimate reason why this is happening seems to be the metadata.xml files that are in org/apache/maven/plugins. They reference a clover plugin plugin nameMaven Clover Plugin/name prefixclover/prefix artifactIdmaven-clover-plugin/artifactId /plugin When I remove this block from the metadata files, it does not attempt to download nor use this old plugin. 1) Why is this happening? 2) Is there a way to get maven to change the order in which it looks for plugins (so it will find the new version first), or at least ignore the old version? Here is the -X output from the build. [INFO] Searching repository for plugin with prefix: 'clover'. [INFO] com.atlassian.maven.plugins: checking for updates from atlassian-m2-repository [INFO] com.atlassian.maven.plugins: checking for updates from Home Plugin Repository [DEBUG] repository metadata for: 'com.atlassian.maven.plugins' could not be found on repository: Home Plugin Repository [INFO] com.atlassian.maven.plugins: checking for updates from central [DEBUG] repository metadata for: 'com.atlassian.maven.plugins' could not be found on repository: central [INFO] com.express-scripts.ccs.framework: checking for updates from atlassian-m2-repository [DEBUG] repository metadata for: 'com.express-scripts.ccs.framework' could not be found on repository: atlassian-m2-repository [INFO] com.express-scripts.ccs.framework: checking for updates from Home Plugin Repository [INFO] com.express-scripts.ccs.framework: checking for updates from central [DEBUG] repository metadata for: 'com.express-scripts.ccs.framework' could not be found on repository: central [INFO] org.apache.maven.plugins: checking for updates from atlassian-m2-repository [INFO] org.apache.maven.plugins: checking for updates from Home Plugin Repository [DEBUG] repository metadata for: 'org.apache.maven.plugins' could not be found on repository: Home Plugin Repository [INFO] org.apache.maven.plugins: checking for updates from central [INFO] org.codehaus.mojo: checking for updates from atlassian-m2-repository [DEBUG] repository metadata for: 'org.codehaus.mojo' could not be found on repository: atlassian-m2-repository [INFO] org.codehaus.mojo: checking for updates from Home Plugin Repository [DEBUG] repository metadata for: 'org.codehaus.mojo' could not be found on repository: Home Plugin Repository [INFO] org.codehaus.mojo: checking for updates from central [INFO] artifact org.apache.maven.plugins:maven-clover-plugin: checking for updates from atlassian-m2-repository [INFO] artifact org.apache.maven.plugins:maven-clover-plugin: checking for updates from Home Plugin Repository [DEBUG] repository metadata for: 'artifact org.apache.maven.plugins:maven-clover-plugin' could not be found on repository: Home Plugin Repository [INFO] artifact org.apache.maven.plugins:maven-clover-plugin: checking for updates from central [DEBUG] maven-clover-plugin: resolved to version 2.4.1 from repository central [DEBUG] Trying repository central Downloading: http://[our mirror of the maven central repository]/maven/org/apache/maven/plugins/maven-clover-plugin/2.4.1/m aven-clover-plugin-2.4.1.pom [DEBUG] Artifact not found - using stub model: Unable to locate resource in repository org.apache.maven.plugins:maven-clover-plugin:pom:2.4.1 from the specified remote repositories: central (http://[our mirror of the maven central repository]/maven-repository/maven), atlassian-m2-repository (http://repository.atlassian.com/maven2), ESI CCS Plugin Repository (http://[Home]/maven-repository/ccs) [DEBUG] Using defaults for missing POM org.apache.maven.plugins:maven-clover-plugin:pom:2.4.1 [DEBUG] Trying repository atlassian-m2-repository Downloading: http://repository.atlassian.com/maven2/org/apache/maven/plugins/maven- clover-plugin/2.4.1/maven-clover-plugin-2.4.1.jar 30K downloaded Here is my setup In settings.xml pluginRepositories
Re: dashboard and site plugin
So am I. Like every other 1.0-SNAPSHOT, there are things to improve, but still, greate work. Erez. P.S. it works for us on a multi module project with no issues. On Dec 5, 2007 7:16 PM, Mick Knutson [EMAIL PROTECTED] wrote: http://mojo.codehaus.org/dashboard-maven-plugin/index.html I love the plugin and it works great On Dec 5, 2007 6:00 AM, emerson cargnin [EMAIL PROTECTED] wrote: Hi guys, after a long while I got the dashboard to work, although the usage page is really misleading. I put here ( http://echofloripa.blogspot.com/2007/12/maven2-dashboard-plugin.html ) a how-to on how make the basic feature of it to work, as in there the plugin version is missing on the pom and on the dashboard maven command. The dashboard plugin when using aggragate report, the link to submodules doesn't work when they have a '.' on it. Aparently it gets clipped after the dot. Also, I got a bit deceptive as I expected the site and dashboard plugin to be stable enough in maven2. The site plugin for multimodules projects don't work as expected/advertised, for example, the command : -mvn site:stage Alright that site:site doesn't work as m1, it's said in the faq also. But the site:stage command, which the faq tells is the right way to get the muilti-module site structure together. Well it just doesn't happen and someone on the maven IRC channel said it has issues. Don't want to start fud here, I'm just a bit down as I've been advertising a lot maven 2 to substitute maven1 where I work, using as main arguments that maven 2 is much more stable and mature. But i see it's not quite the case. I really hope I'm wrong. Emerson - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks, Mick Knutson http://www.baselogic.com http://www.blincmagazine.com http://www.djmick.com http://www.myspace.com/mickknutson http://www.myspace.com/BLiNCMagazine http://tahoe.baselogic.com ---
mvn site:site run maven-antrun-plugin, why?
Hi, I have being trying to ask this question in the past, searched for forum and read documentation, but, no answer yet. I'll try again hopefully I will get an answer (or maybe just hints) what is going on. So, we have a multi module project with some antrun configuration running in some modules during the build. None of the ant tasks is configure to run in the site lifecycle, all are during standard lifecycle. However, after we do mvn clean install, when we run mvn site:site the antrun plugin runs again, also rpm plugin and andromda plugin run again. We have pluginManagement defined in the parent pom and we use profiles to distinguish dev builds and Continuous Integration builds (the later also copy the artifacts to images area, generate some nice reports etc), but nothing tricky. Maybe someone on this list has any idea why it happens or how can I try to debug it? Many many thanks, Erez. We use maven 2.0.7 on Linux, jdk1.5_10 (but we had this issue also with maven 2.0.5)
Re: mvn site:site run maven-antrun-plugin, why?
On Dec 5, 2007 12:01 PM, Erez Nahir [EMAIL PROTECTED] wrote: I have being trying to ask this question in the past, searched for forum and read documentation, but, no answer yet. I'll try again hopefully I will get an answer (or maybe just hints) what is going on. So, we have a multi module project with some antrun configuration running in some modules during the build. None of the ant tasks is configure to run in the site lifecycle, all are during standard lifecycle. Without seeing the poms it's really hard to tell. The best thing you can do is construct the simplest possible example that demonstrates the problem. Often you'll figure it out yourself while doing that, but if not, you can zip it up and post a link for someone to look at, or attach it to a JIRA issue if it seems like there's bug. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: dashboard and site plugin
http://mojo.codehaus.org/dashboard-maven-plugin/index.html I love the plugin and it works great On Dec 5, 2007 6:00 AM, emerson cargnin [EMAIL PROTECTED] wrote: Hi guys, after a long while I got the dashboard to work, although the usage page is really misleading. I put here ( http://echofloripa.blogspot.com/2007/12/maven2-dashboard-plugin.html ) a how-to on how make the basic feature of it to work, as in there the plugin version is missing on the pom and on the dashboard maven command. The dashboard plugin when using aggragate report, the link to submodules doesn't work when they have a '.' on it. Aparently it gets clipped after the dot. Also, I got a bit deceptive as I expected the site and dashboard plugin to be stable enough in maven2. The site plugin for multimodules projects don't work as expected/advertised, for example, the command : -mvn site:stage Alright that site:site doesn't work as m1, it's said in the faq also. But the site:stage command, which the faq tells is the right way to get the muilti-module site structure together. Well it just doesn't happen and someone on the maven IRC channel said it has issues. Don't want to start fud here, I'm just a bit down as I've been advertising a lot maven 2 to substitute maven1 where I work, using as main arguments that maven 2 is much more stable and mature. But i see it's not quite the case. I really hope I'm wrong. Emerson - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks, Mick Knutson http://www.baselogic.com http://www.blincmagazine.com http://www.djmick.com http://www.myspace.com/mickknutson http://www.myspace.com/BLiNCMagazine http://tahoe.baselogic.com ---
Maven and Ant
Newbie here .. .pretty much ... appreciate help with basic question or pointers to finding help ;-) How does Maven know which version of Ant to use ? We're using Maven to build for Weblogic, and I'm wondering how it finds the various taskdefs BEA provides ... I'm puzzled. thanks in advance for any help ! Ethan Allen Extension 7563 (desk) 414.467.9185 (mobile) [EMAIL PROTECTED] (paging) [EMAIL PROTECTED] (paging) CONFIDENTIALITY NOTICE: This is a transmission from Kohl's Department Stores, Inc. and may contain information which is confidential and proprietary. If you are not the addressee, any disclosure, copying or distribution or use of the contents of this message is expressly prohibited. If you have received this transmission in error, please destroy it and notify us immediately at 262-703-7000. CAUTION: Internet and e-mail communications are Kohl's property and Kohl's reserves the right to retrieve and read any message created, sent and received. Kohl's reserves the right to monitor messages by authorized Kohl's Associates at any time without any further consent.
Does wagon-webdav support Digest authentication
Hi, I have been trying to get WAGON-WEBDAV working with an Apache WebDAV provider and can only see that BASIC authentication is attempted. Am I missing something in the following configuration sections: pom.xml extensions extension groupIdorg.apache.maven.wagon/groupId artifactIdwagon-webdav/artifactId version1.0-beta-2/version /extension /extensions . distributionManagement !-- use the following if you're not using a snapshot version. -- repository idmaven-repository/id name Maven Repository/name urldav:http://hostname.domain/maven/repository//url /repository !-- use the following if you ARE using a snapshot version. -- snapshotRepository idmaven-repository/id name Maven Repository/name urldav:http://hostname.domain /maven/repository//url /snapshotRepository /distributionManagement settings.xml server idmaven-repository/id usernamejohn.smith/username passwordpassword/password configuration/configuration /server /servers In the error_log on Apache I am getting: Digest: client used wrong authentication scheme `Basic': /maven/repository/ I saw this message : http://www.mail-archive.com/users@maven.apache.org/msg72316.html referring to Digest authentication but the Apache configuration does not look like it is using Digest. The user here: http://www.nabble.com/WebDav,-Wagon-and-Digest-Authentication-t4653580s1 77.html is having the same issue and no replies yet so I am wondering has anybody got this working? Regards, Pj. *** Department of Agriculture, Fisheries and Food ** The information contained in this email and in any attachments is confidential and is designated solely for the attention and use of the intended recipient(s). This information may be subject to legal and professional privilege. If you are not an intended recipient of this email, you must not use, disclose, copy, distribute or retain this message or any part of it. If you have received this email in error, please notify the sender immediately and delete all copies of this email from your computer system(s). An Roinn Talmhaíochta, Iascaigh agus Bia *** Tá an t-eolais san ríomhphost seo, agus in aon ceangláin leis, faoi phribhléid agus faoi rún agus le h-aghaigh an seolaí amháin. D’fhéadfadh ábhar an seoladh seo bheith faoi phribhléid profisiúnta nó dlíthiúil. Mura tusa an seolaí a bhí beartaithe leis an ríomhphost seo a fháil, tá cosc air, nó aon chuid de, a úsáid, a chóipeál, nó a scaoileadh. Má tháinig sé chugat de bharr dearmad, téigh i dteagmháil leis an seoltóir agus scrios an t-ábhar ó do ríomhaire le do thoil.
Re: mvn site:site run maven-antrun-plugin, why?
Thanks Mick and Wendy for your prompt reply, Mick, unfortunately I can not use this (good) idea, my antrun is running in many modules processing different tasks. I'll try On Dec 5, 2007 9:20 PM, Mick Knutson [EMAIL PROTECTED] wrote: I had this issue, and filtered out the module that used the ant-run like: profiles profile iddocumentation/id modules modulebusiness-services/module modulecommon-c2/module /modules /profile profile idno-documentation/id activation property namebuild.type/name value!documentation/value /property /activation modules modulebpel/module modulebusiness-services/module modulecommon-c2/module /modules /profile /profiles and I just run mvn -P documentation site:site On Dec 5, 2007 11:17 AM, Wendy Smoak [EMAIL PROTECTED] wrote: On Dec 5, 2007 12:01 PM, Erez Nahir [EMAIL PROTECTED] wrote: I have being trying to ask this question in the past, searched for forum and read documentation, but, no answer yet. I'll try again hopefully I will get an answer (or maybe just hints) what is going on. So, we have a multi module project with some antrun configuration running in some modules during the build. None of the ant tasks is configure to run in the site lifecycle, all are during standard lifecycle. Without seeing the poms it's really hard to tell. The best thing you can do is construct the simplest possible example that demonstrates the problem. Often you'll figure it out yourself while doing that, but if not, you can zip it up and post a link for someone to look at, or attach it to a JIRA issue if it seems like there's bug. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks, Mick Knutson http://www.baselogic.com http://www.blincmagazine.com http://www.djmick.com http://www.myspace.com/mickknutson http://www.myspace.com/BLiNCMagazine http://tahoe.baselogic.com ---
Re: mvn site:site run maven-antrun-plugin, why?
I had this issue, and filtered out the module that used the ant-run like: profiles profile iddocumentation/id modules modulebusiness-services/module modulecommon-c2/module /modules /profile profile idno-documentation/id activation property namebuild.type/name value!documentation/value /property /activation modules modulebpel/module modulebusiness-services/module modulecommon-c2/module /modules /profile /profiles and I just run mvn -P documentation site:site On Dec 5, 2007 11:17 AM, Wendy Smoak [EMAIL PROTECTED] wrote: On Dec 5, 2007 12:01 PM, Erez Nahir [EMAIL PROTECTED] wrote: I have being trying to ask this question in the past, searched for forum and read documentation, but, no answer yet. I'll try again hopefully I will get an answer (or maybe just hints) what is going on. So, we have a multi module project with some antrun configuration running in some modules during the build. None of the ant tasks is configure to run in the site lifecycle, all are during standard lifecycle. Without seeing the poms it's really hard to tell. The best thing you can do is construct the simplest possible example that demonstrates the problem. Often you'll figure it out yourself while doing that, but if not, you can zip it up and post a link for someone to look at, or attach it to a JIRA issue if it seems like there's bug. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks, Mick Knutson http://www.baselogic.com http://www.blincmagazine.com http://www.djmick.com http://www.myspace.com/mickknutson http://www.myspace.com/BLiNCMagazine http://tahoe.baselogic.com ---
Re: mvn site:site run maven-antrun-plugin, why?
If I may have a guess, you're using the surefire reports? And all the antruns are in or before the test phase? The surefire-report:report goal runs also the mvn test lifecycle. If this is the case, you can use the surefire-report:report-only goal. Only make sure that the surefire xml files are already in place, because those aren't generated in this case. Hth, Nick Stolwijk Erez Nahir wrote: Thanks Mick and Wendy for your prompt reply, Mick, unfortunately I can not use this (good) idea, my antrun is running in many modules processing different tasks. I'll try On Dec 5, 2007 9:20 PM, Mick Knutson [EMAIL PROTECTED] wrote: I had this issue, and filtered out the module that used the ant-run like: profiles profile iddocumentation/id modules modulebusiness-services/module modulecommon-c2/module /modules /profile profile idno-documentation/id activation property namebuild.type/name value!documentation/value /property /activation modules modulebpel/module modulebusiness-services/module modulecommon-c2/module /modules /profile /profiles and I just run mvn -P documentation site:site On Dec 5, 2007 11:17 AM, Wendy Smoak [EMAIL PROTECTED] wrote: On Dec 5, 2007 12:01 PM, Erez Nahir [EMAIL PROTECTED] wrote: I have being trying to ask this question in the past, searched for forum and read documentation, but, no answer yet. I'll try again hopefully I will get an answer (or maybe just hints) what is going on. So, we have a multi module project with some antrun configuration running in some modules during the build. None of the ant tasks is configure to run in the site lifecycle, all are during standard lifecycle. Without seeing the poms it's really hard to tell. The best thing you can do is construct the simplest possible example that demonstrates the problem. Often you'll figure it out yourself while doing that, but if not, you can zip it up and post a link for someone to look at, or attach it to a JIRA issue if it seems like there's bug. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks, Mick Knutson http://www.baselogic.com http://www.blincmagazine.com http://www.djmick.com http://www.myspace.com/mickknutson http://www.myspace.com/BLiNCMagazine http://tahoe.baselogic.com --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
use assembly to create distributable zip with javadocs and sources?
Hallo i currently try to understand how the assembly plugin works. i have a multi-module build (lets say m1 to m5) which creates sources and javadocs when a release is done. from this point i want to create different zip files - one which contains the jars of m1, m2, m3 - one which contains both jars and javadocs from m1, m2, m3 - one that contains everything (jar, sources, javadocs) - and the same variants for modules m1, m2, m4, m5 normally i use the flags: -DdownloadSources=true -DdownloadJavadocs=true to let maven download both sources and javadocs. but both dependency plugin and assembly plugin seem to ignore that. only the jars are copied to the target folder. is there some trick or would an ant script do a better job here? thanks for any input :) regards ossi - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: mvn site:site run maven-antrun-plugin, why?
Thanks Nick, Nope we do not use surefire reporst, but, maybe another plugin is doing similar thing. One of my guesses was that it has to do with plugins the forks the VM, but, that's also just a guess at this time. Erez. On Dec 5, 2007 10:02 PM, Nick Stolwijk [EMAIL PROTECTED] wrote: If I may have a guess, you're using the surefire reports? And all the antruns are in or before the test phase? The surefire-report:report goal runs also the mvn test lifecycle. If this is the case, you can use the surefire-report:report-only goal. Only make sure that the surefire xml files are already in place, because those aren't generated in this case. Hth, Nick Stolwijk Erez Nahir wrote: Thanks Mick and Wendy for your prompt reply, Mick, unfortunately I can not use this (good) idea, my antrun is running in many modules processing different tasks. I'll try On Dec 5, 2007 9:20 PM, Mick Knutson [EMAIL PROTECTED] wrote: I had this issue, and filtered out the module that used the ant-run like: profiles profile iddocumentation/id modules modulebusiness-services/module modulecommon-c2/module /modules /profile profile idno-documentation/id activation property namebuild.type/name value!documentation/value /property /activation modules modulebpel/module modulebusiness-services/module modulecommon-c2/module /modules /profile /profiles and I just run mvn -P documentation site:site On Dec 5, 2007 11:17 AM, Wendy Smoak [EMAIL PROTECTED] wrote: On Dec 5, 2007 12:01 PM, Erez Nahir [EMAIL PROTECTED] wrote: I have being trying to ask this question in the past, searched for forum and read documentation, but, no answer yet. I'll try again hopefully I will get an answer (or maybe just hints) what is going on. So, we have a multi module project with some antrun configuration running in some modules during the build. None of the ant tasks is configure to run in the site lifecycle, all are during standard lifecycle. Without seeing the poms it's really hard to tell. The best thing you can do is construct the simplest possible example that demonstrates the problem. Often you'll figure it out yourself while doing that, but if not, you can zip it up and post a link for someone to look at, or attach it to a JIRA issue if it seems like there's bug. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks, Mick Knutson http://www.baselogic.com http://www.blincmagazine.com http://www.djmick.com http://www.myspace.com/mickknutson http://www.myspace.com/BLiNCMagazine http://tahoe.baselogic.com --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Maven pulling down the wrong plugin
Greetings First off apologies if this sort of issue has been answered before. I did as thorough a search as I could and couldn't find anything resembling it. Am attempting to use Clover for code coverage. I've set up the pom and settings as instructed by the atlassian folks (http://confluence.atlassian.com/display/CLOVER/Clover-for-Maven+2+User% 27s+Guide). Details of this are at the end of this email. Atlassian support has verified that things are set up correctly. When I do a myriad of maven tasks (clean, package, whatever), the correct Clover maven plugin (3.6) is pulled down from their repository from the atlassian repository from the correct directory(com\atlassian\maven\plugins). However, when I attempt to perform a Clover goal (in this case, clover:instrument), maven goes thru all sorts of machinations and then pulls down an old plugin (2.4.1) from the wrong directory (org/apache/maven/plugins). It then horks. The ultimate reason why this is happening seems to be the metadata.xml files that are in org/apache/maven/plugins. They reference a clover plugin plugin nameMaven Clover Plugin/name prefixclover/prefix artifactIdmaven-clover-plugin/artifactId /plugin When I remove this block from the metadata files, it does not attempt to download nor use this old plugin. 1) Why is this happening? 2) Is there a way to get maven to change the order in which it looks for plugins (so it will find the new version first), or at least ignore the old version? Here is the -X output from the build. [INFO] Searching repository for plugin with prefix: 'clover'. [INFO] com.atlassian.maven.plugins: checking for updates from atlassian-m2-repository [INFO] com.atlassian.maven.plugins: checking for updates from Home Plugin Repository [DEBUG] repository metadata for: 'com.atlassian.maven.plugins' could not be found on repository: Home Plugin Repository [INFO] com.atlassian.maven.plugins: checking for updates from central [DEBUG] repository metadata for: 'com.atlassian.maven.plugins' could not be found on repository: central [INFO] com.express-scripts.ccs.framework: checking for updates from atlassian-m2-repository [DEBUG] repository metadata for: 'com.express-scripts.ccs.framework' could not be found on repository: atlassian-m2-repository [INFO] com.express-scripts.ccs.framework: checking for updates from Home Plugin Repository [INFO] com.express-scripts.ccs.framework: checking for updates from central [DEBUG] repository metadata for: 'com.express-scripts.ccs.framework' could not be found on repository: central [INFO] org.apache.maven.plugins: checking for updates from atlassian-m2-repository [INFO] org.apache.maven.plugins: checking for updates from Home Plugin Repository [DEBUG] repository metadata for: 'org.apache.maven.plugins' could not be found on repository: Home Plugin Repository [INFO] org.apache.maven.plugins: checking for updates from central [INFO] org.codehaus.mojo: checking for updates from atlassian-m2-repository [DEBUG] repository metadata for: 'org.codehaus.mojo' could not be found on repository: atlassian-m2-repository [INFO] org.codehaus.mojo: checking for updates from Home Plugin Repository [DEBUG] repository metadata for: 'org.codehaus.mojo' could not be found on repository: Home Plugin Repository [INFO] org.codehaus.mojo: checking for updates from central [INFO] artifact org.apache.maven.plugins:maven-clover-plugin: checking for updates from atlassian-m2-repository [INFO] artifact org.apache.maven.plugins:maven-clover-plugin: checking for updates from Home Plugin Repository [DEBUG] repository metadata for: 'artifact org.apache.maven.plugins:maven-clover-plugin' could not be found on repository: Home Plugin Repository [INFO] artifact org.apache.maven.plugins:maven-clover-plugin: checking for updates from central [DEBUG] maven-clover-plugin: resolved to version 2.4.1 from repository central [DEBUG] Trying repository central Downloading: http://[our mirror of the maven central repository]/maven/org/apache/maven/plugins/maven-clover-plugin/2.4.1/mav en-clover-plugin-2.4.1.pom [DEBUG] Artifact not found - using stub model: Unable to locate resource in repository org.apache.maven.plugins:maven-clover-plugin:pom:2.4.1 from the specified remote repositories: central (http://[our mirror of the maven central repository]/maven-repository/maven), atlassian-m2-repository (http://repository.atlassian.com/maven2), ESI CCS Plugin Repository (http://[Home]/maven-repository/ccs) [DEBUG] Using defaults for missing POM org.apache.maven.plugins:maven-clover-plugin:pom:2.4.1 [DEBUG] Trying repository atlassian-m2-repository Downloading: http://repository.atlassian.com/maven2/org/apache/maven/plugins/maven-cl over-plugin/2.4.1/maven-clover-plugin-2.4.1.jar 30K downloaded Here is my setup In settings.xml pluginRepositories pluginRepository idatlassian-m2-repository/id
Re: auto-deploy 3rd party files
Generally, people would write a script (Bash, Ksh, Perl, Python, Ruby, etc) to do this for them. I seem to recall reading one that someone wrote some time -- it was either posted on this list, or on the Internet. Try Googling for it, or write it yourself from scratch -- should be pretty simple. Wayne On 12/5/07, javijava [EMAIL PROTECTED] wrote: Hi, I see that people use mvn deploy:deploy-file to put ONE jar into a remote repository. Or with an ant task, can say the path of some file to deploy too. But what happend if a proyect have 100 3rd party jars? we must do 100 deploy-file ?? There is some way..to tell maven that must find the necessary jars to run a project and deploy all the same time? thanks a lot -- View this message in context: http://www.nabble.com/auto-deploy-3rd-party-files-tf4949608s177.html#a14171500 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: dependencies / is there a smart way to declare it?
You can always wrap certain sets of dependencies up in another POM with 'pom' packaging type to keep the dependencies aspect of your pom isolated from whatever else you're having it do. One thing I wish the pom had was a way to perform composition from common components instead of having to use inheritance. Rigid inheritance hierarchies are more difficult to maintain than delegation IMHO. For example, let's say I want a lot of my modules to use certain settings for the maven-compiler-plugin. I could just wrap those settings into a pom and inherit from it, but then if there are other common settings i want to isolate I have to put them in the same pom, or have the compiler pom inherit from the source pom or vice-versa. Perhaps I've missed something but I can't find a way to perform this sort of 'composition' as Michael has proposed within maven. Please let me know what I'm missing ! Kallin Nagelberg Consulting Architect On Dec 5, 2007 4:02 PM, Michael McCallum [EMAIL PROTECTED] wrote: refactoring, composition, encasulation, aggregation standard techniques for making complex systems easier to understand... On Thu, 06 Dec 2007 09:42:49 Marco Mistroni wrote: hi all, just a quick question to see best practices with maven projects. i have a pom which contains lot of dependencies... so my pom end up being huge.. i was wondering if there is a smart way to declare them so that i don' t end up with a 300 lines pom.. again, it's not a real problem, i was wondering how peoples on the list were dealing with it.. regards marco -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: dependencies / is there a smart way to declare it?
refactoring, composition, encasulation, aggregation standard techniques for making complex systems easier to understand... On Thu, 06 Dec 2007 09:42:49 Marco Mistroni wrote: hi all, just a quick question to see best practices with maven projects. i have a pom which contains lot of dependencies... so my pom end up being huge.. i was wondering if there is a smart way to declare them so that i don' t end up with a 300 lines pom.. again, it's not a real problem, i was wondering how peoples on the list were dealing with it.. regards marco -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [m2] eclipse plugin and WTP generating warnings in Europa
So I did others tests using each times new Eclipse workspace: 1) If I try to generate with wtpversion=1.5 and maven-eclipse-plugin version 2.5-SNAPSHOT = I get the same behaviour in EUROPA 2) If I try to generate with wtpversion=1.5 and maven-eclipse-plugin version 2.4 = I get the same behaviour in EUROPA 3) I then try using Eclipse 3.2.2 with WTP 1.5.3 (instead of Eclipse 3.3.1.1 and WTP 2.0.1) with maven-eclipse-plugin version 2.4 or 2.5-SNAPSHOT = Everything is perfect, no more warnings Arnaud, I will create a simple test case and open an issue... Yann. Arnaud HERITIER a écrit : Can you create a little test case and open an issue please ? I didn't yet found this problem but it's perhaps a bug in one change I made to add the support of WTP 2.0. Another test that you can do : - generates WTP settings for version 1.5 - import your project into eclipse (it should convert them in 2.0) - check that you have the same error. It will help us to analyze the problem. arnaud On Dec 4, 2007 10:55 PM, Yann Albou [EMAIL PROTECTED] wrote: I just tried with the latest snapshot and I get the same behaviour. I see these warnings during import. on the Warning it exists a Quick fix that says :Mark the associated raw classpath entry as a publish/export dependency. So I execued it And then I get an error that says Invalid classpath publish/export dependency... Siarhei Dudzin a écrit : Do you get the same from getting the latest snapshot instead of the trunk? Where do you see this waring? During import or after import in the problems view? On 12/4/07, Yann Albou [EMAIL PROTECTED] wrote: Is someone facing the same issue ? Yann. Yann Albou a écrit : Hello, After generating my eclipse projects with mvn -Dwtpversion=2.0 eclipse:eclipse and importing these projects into an europa workspace I get the following Warning: Claspath entry M2_REPO/commons-logging/commons-logging/1.0.4/commons-loggin-1.0.4.jar will not be exported or published. Runtime ClassNotFound Exceptions may result. All my dependencies get this warning. I use the last version of the maven eclipse plugin (from trunks) and I use the Eclipse JEE Europa that includes Eclipse 3.3.1.1 and WTP 2.0.1 any Idea ? Thanks Yann. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
dependencies / is there a smart way to declare it?
hi all, just a quick question to see best practices with maven projects. i have a pom which contains lot of dependencies... so my pom end up being huge.. i was wondering if there is a smart way to declare them so that i don' t end up with a 300 lines pom.. again, it's not a real problem, i was wondering how peoples on the list were dealing with it.. regards marco
Re: [m2] eclipse plugin and WTP generating warnings in Europa
Ok, thanks a lot for your feedback. I'll try to fix it before the release of the 2.5 Arnaud On Dec 5, 2007 8:51 PM, Yann Albou [EMAIL PROTECTED] wrote: So I did others tests using each times new Eclipse workspace: 1) If I try to generate with wtpversion=1.5 and maven-eclipse-plugin version 2.5-SNAPSHOT = I get the same behaviour in EUROPA 2) If I try to generate with wtpversion=1.5 and maven-eclipse-plugin version 2.4 = I get the same behaviour in EUROPA 3) I then try using Eclipse 3.2.2 with WTP 1.5.3 (instead of Eclipse 3.3.1.1 and WTP 2.0.1) with maven-eclipse-plugin version 2.4 or 2.5-SNAPSHOT = Everything is perfect, no more warnings Arnaud, I will create a simple test case and open an issue... Yann. Arnaud HERITIER a écrit : Can you create a little test case and open an issue please ? I didn't yet found this problem but it's perhaps a bug in one change I made to add the support of WTP 2.0. Another test that you can do : - generates WTP settings for version 1.5 - import your project into eclipse (it should convert them in 2.0) - check that you have the same error. It will help us to analyze the problem. arnaud On Dec 4, 2007 10:55 PM, Yann Albou [EMAIL PROTECTED] wrote: I just tried with the latest snapshot and I get the same behaviour. I see these warnings during import. on the Warning it exists a Quick fix that says :Mark the associated raw classpath entry as a publish/export dependency. So I execued it And then I get an error that says Invalid classpath publish/export dependency... Siarhei Dudzin a écrit : Do you get the same from getting the latest snapshot instead of the trunk? Where do you see this waring? During import or after import in the problems view? On 12/4/07, Yann Albou [EMAIL PROTECTED] wrote: Is someone facing the same issue ? Yann. Yann Albou a écrit : Hello, After generating my eclipse projects with mvn -Dwtpversion=2.0 eclipse:eclipse and importing these projects into an europa workspace I get the following Warning: Claspath entry M2_REPO/commons-logging/commons-logging/1.0.4/commons- loggin-1.0.4.jar will not be exported or published. Runtime ClassNotFound Exceptions may result. All my dependencies get this warning. I use the last version of the maven eclipse plugin (from trunks) and I use the Eclipse JEE Europa that includes Eclipse 3.3.1.1 and WTP 2.0.1 any Idea ? Thanks Yann. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- .. Arnaud HERITIER .. OCTO Technology - aheritier AT octo DOT com www.octo.com | blog.octo.com .. ASF - aheritier AT apache DOT org www.apache.org | maven.apache.org ...
Re: auto-deploy 3rd party files
Hi, If you don't use any maven proxy, you could simply copy all of the libraries across to your repository and write a script to generate basic pom.xmls and the checksums. You just need to understand how he repoitory is structured. Alternatively, you could also write a script to run deploy-file for all your jars.Shouldn't be too hard at all if you dont care too much about dependencies in side each of the pom file. Cheers, rOnn c. javijava [EMAIL PROTECTED] 12/06/2007 12:30 AM Please respond to Maven Users List users@maven.apache.org To users@maven.apache.org cc Subject auto-deploy 3rd party files Hi, I see that people use mvn deploy:deploy-file to put ONE jar into a remote repository. Or with an ant task, can say the path of some file to deploy too. But what happend if a proyect have 100 3rd party jars? we must do 100 deploy-file ?? There is some way..to tell maven that must find the necessary jars to run a project and deploy all the same time? thanks a lot -- View this message in context: http://www.nabble.com/auto-deploy-3rd-party-files-tf4949608s177.html#a14171500 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ## DISCLAIMER: This email and any attachment may contain confidential information. If you are not the intended recipient you are not authorized to copy or disclose all or any part of it without the prior written consent of Toyota. Opinions expressed in this email and any attachments are those of the sender and not necessarily the opinions of Toyota. Please scan this email and any attachment(s) for viruses. Toyota does not accept any responsibility for problems caused by viruses, whether it is Toyota's fault or not. ##
Re: URL's from master POM
Hi Jim,
thanks for your answer.
1) This is how I am working around it today. I have a property
defined in master pom that resolves to the correct urls. However, I have
to redefine the setting of the url in each project.
Otherwise I have the appendix to the URL I have described.
2) I have redefined the groupId and artifactId simply to clarify
for me whether the problem was a bug related to resolving those
properties. With the approach I have now that redefinition would be
obsolete.
Best regards
Andreas
Jim Sellers schrieb:
A couple of questions:
1) Why don't you specify
https://www.soa-knowledge.net/projects/https://www.soa-knowledge.net/projects/$%7BurlGroup%7D/$%7BurlId%7D/$%7Bprojeas
a property?
2) Why did you redefine the groupId and artifact id?
I think (unfortunately) that the groupId and artifact id are resolved to the
pom where they are declared. You may have to re-define it in all the
sub-projects (which was your original question).
It could be something like:
url${serverUrl}${project.groupId}/${project.artifactId}/${project.version
}/${project.artifactId}/url
:-/
On 12/5/07, Andreas Gies [EMAIL PROTECTED] wrote:
Hello,
i am managing multiple projects form y company using maven 2.0.7. For
that purpose I have created a master pom, that contains the following
section: (Pom A)
...
modelVersion4.0.0/modelVersion
groupIdcom.sonicsw.pso/groupId
artifactIdsonic-maven-parent/artifactId
version1.0/version
packagingpom/packaging
nameMaven Definitions for all Sonic PSO projects/name
urlhttps://www.soa-knowledge.net/projects/${urlGroup}/${urlId}/${proje
ct.version}/${urlId}/url
properties
urlGroup${project.groupId}/urlGroup
urlId${project.artifactId}/urlId
/properties
...
From that I have inherited another pom (POM B), that does not specify
anything for an URL and serves as a base for a part of my projects. That
pom has the following coordinates:
...
modelVersion4.0.0/modelVersion
groupIdcom.sonicsw.pso/groupId
artifactIdservices-maven-parent/artifactId
version1.0/version
packagingpom/packaging
nameMaven Definitions for all Sonic ESB Services/name
parent
groupIdcom.sonicsw.pso/groupId
artifactIdsonic-maven-parent/artifactId
version1.0/version
/parent
...
My project now inherits from POM B, which in turn inherits from POM A.
parent
groupIdcom.sonicsw.pso/groupId
artifactIdservices-maven-parent/artifactId
version1.0/version
/parent
groupIdcom.sonicsw.pso.services/groupId
artifactIdWSMQService/artifactId
packagingjar/packaging
version1.0-SNAPSHOT/version
nameWebsphere MQ connectivity services/name
My problem is now in the definition of URLS (for automatically
generating web urls, scm urls, ftp urls etc...)
When I define no url in my project, the generated url is:
https://www.soa-knowledge.net/projects/com.sonicsw.pso.services/WSMQServ
ice/1.0-SNAPSHOT/WSMQService/services-maven-parent/WSMQService
However, if I add the url definition into my project
parent
groupIdcom.sonicsw.pso/groupId
artifactIdservices-maven-parent/artifactId
version1.0/version
/parent
groupIdcom.sonicsw.pso.services/groupId
artifactIdWSMQService/artifactId
packagingjar/packaging
version1.0-SNAPSHOT/version
nameWebsphere MQ connectivity services/name
urlhttps://www.soa-knowledge.net/projects/${urlGroup}/${urlId}/${proje
ct.version}/${urlId}/url
the url is
https://www.soa-knowledge.net/projects/com.sonicsw.pso.services/WSMQServ
ice/1.0-SNAPSHOT/WSMQService
which is what I intended.
I would like to avoid repeating the URL definitions in each sub project
since this is what I had created the masters for in the first place.
Could somebody explain the behaviour here ? - Can the append be avoided
?
Thank you very much in advance
Andreas
-
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 and Ant
I may be totally off on this but I'm pretty sure that when using the maven-antrun-plugin maven uses ant artifacts from the maven repo. IE some of these guys: http://www.mvnrepository.com/artifact/org.apache.ant On Dec 5, 2007 11:41 AM, [EMAIL PROTECTED] wrote: Newbie here .. .pretty much ... appreciate help with basic question or pointers to finding help ;-) How does Maven know which version of Ant to use ? We're using Maven to build for Weblogic, and I'm wondering how it finds the various taskdefs BEA provides ... I'm puzzled. thanks in advance for any help ! Ethan Allen Extension 7563 (desk) 414.467.9185 (mobile) [EMAIL PROTECTED] (paging) [EMAIL PROTECTED] (paging) CONFIDENTIALITY NOTICE: This is a transmission from Kohl's Department Stores, Inc. and may contain information which is confidential and proprietary. If you are not the addressee, any disclosure, copying or distribution or use of the contents of this message is expressly prohibited. If you have received this transmission in error, please destroy it and notify us immediately at 262-703-7000. CAUTION: Internet and e-mail communications are Kohl's property and Kohl's reserves the right to retrieve and read any message created, sent and received. Kohl's reserves the right to monitor messages by authorized Kohl's Associates at any time without any further consent.
Re: mvn site:site run maven-antrun-plugin, why?
Then try a mvn -X build, capture the output with a pipe or tee and start searching which plugin is executed before the antruns. Hth, Nick S. Erez Nahir wrote: Thanks Nick, Nope we do not use surefire reporst, but, maybe another plugin is doing similar thing. One of my guesses was that it has to do with plugins the forks the VM, but, that's also just a guess at this time. Erez. On Dec 5, 2007 10:02 PM, Nick Stolwijk [EMAIL PROTECTED] wrote: If I may have a guess, you're using the surefire reports? And all the antruns are in or before the test phase? The surefire-report:report goal runs also the mvn test lifecycle. If this is the case, you can use the surefire-report:report-only goal. Only make sure that the surefire xml files are already in place, because those aren't generated in this case. Hth, Nick Stolwijk Erez Nahir wrote: Thanks Mick and Wendy for your prompt reply, Mick, unfortunately I can not use this (good) idea, my antrun is running in many modules processing different tasks. I'll try On Dec 5, 2007 9:20 PM, Mick Knutson [EMAIL PROTECTED] wrote: I had this issue, and filtered out the module that used the ant-run like: profiles profile iddocumentation/id modules modulebusiness-services/module modulecommon-c2/module /modules /profile profile idno-documentation/id activation property namebuild.type/name value!documentation/value /property /activation modules modulebpel/module modulebusiness-services/module modulecommon-c2/module /modules /profile /profiles and I just run mvn -P documentation site:site On Dec 5, 2007 11:17 AM, Wendy Smoak [EMAIL PROTECTED] wrote: On Dec 5, 2007 12:01 PM, Erez Nahir [EMAIL PROTECTED] wrote: I have being trying to ask this question in the past, searched for forum and read documentation, but, no answer yet. I'll try again hopefully I will get an answer (or maybe just hints) what is going on. So, we have a multi module project with some antrun configuration running in some modules during the build. None of the ant tasks is configure to run in the site lifecycle, all are during standard lifecycle. Without seeing the poms it's really hard to tell. The best thing you can do is construct the simplest possible example that demonstrates the problem. Often you'll figure it out yourself while doing that, but if not, you can zip it up and post a link for someone to look at, or attach it to a JIRA issue if it seems like there's bug. -- Wendy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Thanks, Mick Knutson http://www.baselogic.com http://www.blincmagazine.com http://www.djmick.com http://www.myspace.com/mickknutson http://www.myspace.com/BLiNCMagazine http://tahoe.baselogic.com --- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: site.xml absolute href are replaced by relative path.
Maybe related to faq #2: http://maven.apache.org/plugins/maven-site-plugin/faq.html ? HTH, -Lukas Yann Davin wrote: Hi, all There is a behavior of maven that I don't understand. If I put a non relative href for menu item of the site.xml file, like this : menu name=test-menu item name=Fractal Homepage href=http://test-url.com/; / /menu I don't know why, when I generate the site (mvn site), the href is replaced by the relative path ../../../. Is it possible, and if yes how can I put external item with external href in the menu section and display it correcly on the pages generated during the mvn site phase ? (ps: I don't want to use the site:stage) Thanks. Yann - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: UnsatisfiedDependencyException
Yes, it is still supported, but it's not needed in your case. Does it work now? -Lukas Rice Yeh wrote: is jar not supported? Rice On Dec 4, 2007 5:29 PM, Lukas Theussl [EMAIL PROTECTED] wrote: You have to add the 'tags' part in both artifactId's and you can remove the jar tags eg: dependency groupIdcommons-jelly/groupId artifactIdcommons-jelly-tags-interaction/artifactId version1.0/version /dependency HTH, -Lukas Rice Yeh wrote: Hi Lukas, In the project.xml, the dependencies are as follows: dependency artifactIdcommons-jelly-interaction/artifactId groupIdcommons-jelly/groupId jarcommons-jelly-tags-interaction-1.0.jar/jar version1.0/version url/ /dependency dependency artifactIdcommons-jelly-http/artifactId groupIdcommons-jelly/groupId jarcommons-jelly-tags-http-1.0.jar/jar version1.0/version url/ /dependency In the repository, two files commons-jelly-tags-http-1.0.jar and commons-jelly-tags-interaction-1.0.jar are under commons-jelly directory. I do not know much about maven 1.x. What is going wrong? Regards, Rice On Dec 4, 2007 5:01 PM, Lukas Theussl [EMAIL PROTECTED] wrote: Shouldn't it be jelly-tags-interaction and jelly-tags-http? HTH, -Lukas Rice Yeh wrote: Hi, I am using maven to build glassfish. I get the errors below. I check my local repositories. I do have these 2 artifacts in it. I am using maven 1.1. Any clue? Exception stack traces : org.apache.maven.verifier.UnsatisfiedDependencyException : The build cannot conti nue because of the following unsatisfied dependencies: - commons-jelly:commons-jelly-interaction:1.0:jar - commons-jelly:commons-jelly-http:1.0:jar Regards, Rice - 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: UnsatisfiedDependencyException
is jar not supported? Rice On Dec 4, 2007 5:29 PM, Lukas Theussl [EMAIL PROTECTED] wrote: You have to add the 'tags' part in both artifactId's and you can remove the jar tags eg: dependency groupIdcommons-jelly/groupId artifactIdcommons-jelly-tags-interaction/artifactId version1.0/version /dependency HTH, -Lukas Rice Yeh wrote: Hi Lukas, In the project.xml, the dependencies are as follows: dependency artifactIdcommons-jelly-interaction/artifactId groupIdcommons-jelly/groupId jarcommons-jelly-tags-interaction-1.0.jar/jar version1.0/version url/ /dependency dependency artifactIdcommons-jelly-http/artifactId groupIdcommons-jelly/groupId jarcommons-jelly-tags-http-1.0.jar/jar version1.0/version url/ /dependency In the repository, two files commons-jelly-tags-http-1.0.jar and commons-jelly-tags-interaction-1.0.jar are under commons-jelly directory. I do not know much about maven 1.x. What is going wrong? Regards, Rice On Dec 4, 2007 5:01 PM, Lukas Theussl [EMAIL PROTECTED] wrote: Shouldn't it be jelly-tags-interaction and jelly-tags-http? HTH, -Lukas Rice Yeh wrote: Hi, I am using maven to build glassfish. I get the errors below. I check my local repositories. I do have these 2 artifacts in it. I am using maven 1.1. Any clue? Exception stack traces : org.apache.maven.verifier.UnsatisfiedDependencyException : The build cannot conti nue because of the following unsatisfied dependencies: - commons-jelly:commons-jelly-interaction:1.0:jar - commons-jelly:commons-jelly-http:1.0:jar Regards, Rice - 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: Buggy version range ?
That's interesting. Would this version range work [1.2,-!) i.e., to match 1.2 or anything later ? don't put [X.X] ranges in things that will resolve transitively.. that gives NPE have not figure out why yet... i suspect broken metadata Not sure what you mean, but when we use version range we use it all the way (from the most common denominator libraries that are reused every where at several levels right to the bespoke end product applications). Here's a scenario that we have. Three reusable artifacts that depends on each other. * projecta - project b (version range) -project c (version range) Bespoke application that may imports the above reusable artifacts * project d may explictly declare depenencies on project a (version range), project b (version rage) and project c (version range)! Version range is certainly very useful but I think one can always work around it, especially if it is buggy. Can you elaborate on what you mean by make complex project possible and makes parallel development possible ? Regards, rOnn c. Michael McCallum [EMAIL PROTECTED] 12/05/2007 04:14 PM Please respond to Maven Users List users@maven.apache.org To Maven Users List users@maven.apache.org cc Subject Re: Buggy version range ? I use version ranges... make complex projects possible... makes parallel development possible too there are a few gotchas... * [3,4) will match 4.0-SNAPSHOT should use [3,4-!) * [3,4) will not match 3.0-SNAPSHOT * don't use - any in ranges just causes trouble make regular use of releases and where you have a breaking change increment the major version don't put [X.X] ranges in things that will resolve transitively.. that gives NPE have not figure out why yet... i suspect broken metadata broken metadata for external projects can be very anoyying... i wrap them in local projects I call composites that give the power of ranges with decent metadata and let me use ranges for projects with funny versions that don't work with ranges we use eclipse with the m2eclipse plugin which works very well with ranges using 2.0.7 and 2.0.8 we don't use modules have over 113 artifacts have both java4 and java6 repositories On Wed, 05 Dec 2007 17:26:32 [EMAIL PROTECTED] wrote: Hi All, I'd like to get an idea if there are many people using the version range feature in the community. For those users using/relying version range, do you find any problems with it? In our organisation, some people advocate the usage of version range but personally, I don't think it is robust enough for real world usage. Following problems are my main gripes that often stop me from runing maven on a day to day basis. * idea plugin errors (can't resolve artifacts with obscure errors). * dependencies resolution errors (various obscure NPE errors). * release plugin errors (can't release because we do clean install first and it will resolve to snapshot). * release plugin does not crystalise the actual version that has been resolved in the release pom that has been tagged. * version range depends on maven-metadata.xml the content of the file which can be errorneous. This is mainly based on Maven 2.0.6, because 2.0.7 gave us more NPE on resolving transitive dependencies. The problem also seems to happen with some projects and not others. Generally, we have about three or more layers of inhouse artifacts that are imported as dependencies across several maven modules. Like to hear any success/failure stories about this. Cheers, rOnn c. ## DISCLAIMER: This email and any attachment may contain confidential information. If you are not the intended recipient you are not authorized to copy or disclose all or any part of it without the prior written consent of Toyota. Opinions expressed in this email and any attachments are those of the sender and not necessarily the opinions of Toyota. Please scan this email and any attachment(s) for viruses. Toyota does not accept any responsibility for problems caused by viruses, whether it is Toyota's fault or not. ## -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] ## DISCLAIMER: This email and any attachment may contain confidential information. If you are not the intended recipient you are not authorized to copy or disclose all or any part of it without the prior written consent of Toyota. Opinions expressed in this email and any attachments are those of the sender and not necessarily the opinions of Toyota. Please scan this email and any attachment(s) for viruses. Toyota does not accept any responsibility for problems
Re: Maven pulling down the wrong plugin
Use the fully qualified name (or whatever its called) of the plugin when calling the instrument goal: mvn com.atlassian.maven.plugins:maven-clover-plugin:3.6:instrument Wayne On 12/5/07, Tripp, Matt (STL) [EMAIL PROTECTED] wrote: Greetings First off apologies if this sort of issue has been answered before. I did as thorough a search as I could and couldn't find anything resembling it. Am attempting to use Clover for code coverage. I've set up the pom and settings as instructed by the atlassian folks (http://confluence.atlassian.com/display/CLOVER/Clover-for-Maven+2+Use r%27s+Guide). Details of this are at the end of this email. Atlassian support has verified that things are set up correctly. When I do a myriad of maven tasks (clean, package, whatever), the correct Clover maven plugin (3.6) is pulled down from their repository from the atlassian repository from the correct directory(com\atlassian\maven\plugins). However, when I attempt to perform a Clover goal (in this case, clover:instrument), maven goes thru all sorts of machinations and then pulls down an old plugin (2.4.1) from the wrong directory (org/apache/maven/plugins). It then horks. The ultimate reason why this is happening seems to be the metadata.xml files that are in org/apache/maven/plugins. They reference a clover plugin plugin nameMaven Clover Plugin/name prefixclover/prefix artifactIdmaven-clover-plugin/artifactId /plugin When I remove this block from the metadata files, it does not attempt to download nor use this old plugin. 1) Why is this happening? 2) Is there a way to get maven to change the order in which it looks for plugins (so it will find the new version first), or at least ignore the old version? Here is the -X output from the build. [INFO] Searching repository for plugin with prefix: 'clover'. [INFO] com.atlassian.maven.plugins: checking for updates from atlassian-m2-repository [INFO] com.atlassian.maven.plugins: checking for updates from Home Plugin Repository [DEBUG] repository metadata for: 'com.atlassian.maven.plugins' could not be found on repository: Home Plugin Repository [INFO] com.atlassian.maven.plugins: checking for updates from central [DEBUG] repository metadata for: 'com.atlassian.maven.plugins' could not be found on repository: central [INFO] com.express-scripts.ccs.framework: checking for updates from atlassian-m2-repository [DEBUG] repository metadata for: 'com.express-scripts.ccs.framework' could not be found on repository: atlassian-m2-repository [INFO] com.express-scripts.ccs.framework: checking for updates from Home Plugin Repository [INFO] com.express-scripts.ccs.framework: checking for updates from central [DEBUG] repository metadata for: 'com.express-scripts.ccs.framework' could not be found on repository: central [INFO] org.apache.maven.plugins: checking for updates from atlassian-m2-repository [INFO] org.apache.maven.plugins: checking for updates from Home Plugin Repository [DEBUG] repository metadata for: 'org.apache.maven.plugins' could not be found on repository: Home Plugin Repository [INFO] org.apache.maven.plugins: checking for updates from central [INFO] org.codehaus.mojo: checking for updates from atlassian-m2-repository [DEBUG] repository metadata for: 'org.codehaus.mojo' could not be found on repository: atlassian-m2-repository [INFO] org.codehaus.mojo: checking for updates from Home Plugin Repository [DEBUG] repository metadata for: 'org.codehaus.mojo' could not be found on repository: Home Plugin Repository [INFO] org.codehaus.mojo: checking for updates from central [INFO] artifact org.apache.maven.plugins:maven-clover-plugin: checking for updates from atlassian-m2-repository [INFO] artifact org.apache.maven.plugins:maven-clover-plugin: checking for updates from Home Plugin Repository [DEBUG] repository metadata for: 'artifact org.apache.maven.plugins:maven-clover-plugin' could not be found on repository: Home Plugin Repository [INFO] artifact org.apache.maven.plugins:maven-clover-plugin: checking for updates from central [DEBUG] maven-clover-plugin: resolved to version 2.4.1 from repository central [DEBUG] Trying repository central Downloading: http://[our mirror of the maven central repository]/maven/org/apache/maven/plugins/maven-clover-plugin/2.4.1/m aven-clover-plugin-2.4.1.pom [DEBUG] Artifact not found - using stub model: Unable to locate resource in repository org.apache.maven.plugins:maven-clover-plugin:pom:2.4.1 from the specified remote repositories: central (http://[our mirror of the maven central repository]/maven-repository/maven), atlassian-m2-repository (http://repository.atlassian.com/maven2), ESI CCS Plugin Repository (http://[Home]/maven-repository/ccs) [DEBUG] Using defaults for missing POM
Re: URL's from master POM
A couple of questions:
1) Why don't you specify
https://www.soa-knowledge.net/projects/https://www.soa-knowledge.net/projects/$%7BurlGroup%7D/$%7BurlId%7D/$%7Bprojeas
a property?
2) Why did you redefine the groupId and artifact id?
I think (unfortunately) that the groupId and artifact id are resolved to the
pom where they are declared. You may have to re-define it in all the
sub-projects (which was your original question).
It could be something like:
url${serverUrl}${project.groupId}/${project.artifactId}/${project.version
}/${project.artifactId}/url
:-/
On 12/5/07, Andreas Gies [EMAIL PROTECTED] wrote:
Hello,
i am managing multiple projects form y company using maven 2.0.7. For
that purpose I have created a master pom, that contains the following
section: (Pom A)
...
modelVersion4.0.0/modelVersion
groupIdcom.sonicsw.pso/groupId
artifactIdsonic-maven-parent/artifactId
version1.0/version
packagingpom/packaging
nameMaven Definitions for all Sonic PSO projects/name
urlhttps://www.soa-knowledge.net/projects/${urlGroup}/${urlId}/${proje
ct.version}/${urlId}/url
properties
urlGroup${project.groupId}/urlGroup
urlId${project.artifactId}/urlId
/properties
...
From that I have inherited another pom (POM B), that does not specify
anything for an URL and serves as a base for a part of my projects. That
pom has the following coordinates:
...
modelVersion4.0.0/modelVersion
groupIdcom.sonicsw.pso/groupId
artifactIdservices-maven-parent/artifactId
version1.0/version
packagingpom/packaging
nameMaven Definitions for all Sonic ESB Services/name
parent
groupIdcom.sonicsw.pso/groupId
artifactIdsonic-maven-parent/artifactId
version1.0/version
/parent
...
My project now inherits from POM B, which in turn inherits from POM A.
parent
groupIdcom.sonicsw.pso/groupId
artifactIdservices-maven-parent/artifactId
version1.0/version
/parent
groupIdcom.sonicsw.pso.services/groupId
artifactIdWSMQService/artifactId
packagingjar/packaging
version1.0-SNAPSHOT/version
nameWebsphere MQ connectivity services/name
My problem is now in the definition of URLS (for automatically
generating web urls, scm urls, ftp urls etc...)
When I define no url in my project, the generated url is:
https://www.soa-knowledge.net/projects/com.sonicsw.pso.services/WSMQServ
ice/1.0-SNAPSHOT/WSMQService/services-maven-parent/WSMQService
However, if I add the url definition into my project
parent
groupIdcom.sonicsw.pso/groupId
artifactIdservices-maven-parent/artifactId
version1.0/version
/parent
groupIdcom.sonicsw.pso.services/groupId
artifactIdWSMQService/artifactId
packagingjar/packaging
version1.0-SNAPSHOT/version
nameWebsphere MQ connectivity services/name
urlhttps://www.soa-knowledge.net/projects/${urlGroup}/${urlId}/${proje
ct.version}/${urlId}/url
the url is
https://www.soa-knowledge.net/projects/com.sonicsw.pso.services/WSMQServ
ice/1.0-SNAPSHOT/WSMQService
which is what I intended.
I would like to avoid repeating the URL definitions in each sub project
since this is what I had created the masters for in the first place.
Could somebody explain the behaviour here ? - Can the append be avoided
?
Thank you very much in advance
Andreas
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Re: Buggy version range ?
On Thu, 06 Dec 2007 11:26:53 [EMAIL PROTECTED] wrote: That's interesting. indeed Would this version range work [1.2,-!) i.e., to match 1.2 or anything later ? don't know good guess though Version range is certainly very useful but I think one can always work around it, especially if it is buggy. Can you elaborate on what you mean by make complex project possible when you get complex depedencies it is quite often very difficult to get a consistent set of know good artifacts in release assemblies... think dependency depths 7 with lots of common deps by encasulating third party and even internal components in dependency compositions you can easily manage links to external projects... consider hibernate... we have a composite dependecy with version 1.X that any of our projects using hibernate use, they have a range [1,2-)... in order to upgrade hibernate i can release a new composite in the 1.x range and all projects will pick it up or i can increment the composite range to 2.x - e.g. for move from 3.1.X hibernate to 3.2.X. - and only project where i update the range to [2,3-!) will be affected... as a bonus its not possible to now aggregate components that a depedent on different versions of hibernate... this leads into your next question... and makes parallel development possible ? so with composites its possible to have a portion of artifacts using a particular version of a third party library upgraded in isolation... for example... a new deliverable is being built but needs the latest and greatest spring... however a bug stops it from being used for some other deliverables I can have two deliverables that use spring composite 1.x which is spring 2.0.7 and the new deliverable use composite 2.x which is spring 2.0.8 i only use spring and hibernate to illustrate the point as they tend to be ubiquitous across my projects... both are very high quality ;-) Obviously the same is true for artifacts reused across 'my own' projects. I can have two teams working in the most recent example on different versions of java... the 1.x versions of our libraries are java4 and the 2.x are java6... the appropriate use of ranges will mean that no java4 aggregation will ever accidentally pull in a java6 jar I would recommend a little research into linux and package management... in particular Gentoo's portage. -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to easily determine all the versions of plugins that are being used.
The enforcer will tell you the current version of plugins not locked down. I've been working towards a release very soon... I just need to wrap up documenting a few new rules I've added and then it's coming out. Ultimately I want to roll this code into a help:current-plugins goal to simply display the plugin revs, but that will come later. -Original Message- From: Stephen Connolly [mailto:[EMAIL PROTECTED] Sent: Wednesday, December 05, 2007 2:57 AM To: Maven Users List Subject: How to easily determine all the versions of plugins that are being used. I remember seeing something (perhaps in a dream) about a nice easy way to get a list of all the versions of the plugins that are being resolved currently. I know the enforcer plugin has the ability (in theory) of locking down plugin versions. But given that the last released version of that plugin does not include the requirePluginVersions rule (as far as I can see... i.e. blows up every time!) I am at a loss as to how to easily lock down the plugin versions... Perhaps somebody could push a release of the enforcer plugin and the working version will produce a list like: the following versions are resolving but not specified. Or perhaps there's some magic plugin elsewhere that gives this info -Stephen - 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 / is there a smart way to declare it?
On Thu, 06 Dec 2007 10:12:27 Kallin Nagelberg wrote: You can always wrap certain sets of dependencies up in another POM with 'pom' packaging type to keep the dependencies aspect of your pom isolated from whatever else you're having it do. yes this is the way to do it... however i use jars as that way i get the pom and pom.properties in unpacked aggregations which is very handy for figuring out whats actually deployed on various environments this has more significant uses in terms of the closest first resolution mechanism this gives an easy way to force particular versions and exclusions... for example i have replaced commons logging with slf4j... but lots of things depend on commons-logging so i put exclusions in my compositions... another good example could be ehcache and hibernate... they have circular depedencies... so i use the composites to exclude each other and enforce particular versions of things One thing I wish the pom had was a way to perform composition from common components instead of having to use inheritance. Rigid inheritance hierarchies are more difficult to maintain than delegation IMHO. For i only have 2 deep hierachies the parent of all for distribution managment and then group parents... all repository definitions are in settings.xml to avoid the chicken and egg of parent resolution the thing i would like most would be to promote/demote released artifacts in the repository... i wonder if archiva does this... that way you can easily use ranges and remove a broken artifact from the resolution graph... -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Include library (jar file) in sar
I have tried the dependency-plugin with copy goal, it copy my dependency to a directory, while what I need is to have the dependency bundled together in my SAR file. Is there any specific configuration that I need to be aware of ? Thank you. Ian Springer-2 wrote: Use the copy goal from the dependency plugin: http://maven.apache.org/plugins/maven-dependency-plugin/usage.html ferry97 wrote: Hi, I need to put a jar file in a sar file, myfile.sar +-- com (classes) +-- lib +-- mylib.jar +-- META-INF +-- jboss-service.xml I have search everywhere but I can not find a plug-in that can do the job (adding a jar file). Does anyone know how to do it ? Perhaps I miss something. Thanks. Regards, Ferry - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- View this message in context: http://www.nabble.com/Include-library-%28jar-file%29-in-sar-tf4947837s177.html#a14184655 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: POM file does not exist. Either the POM you specified or one of its modules does not exist.
Good idea. I just switched log level to debug and it appears is that Continuum is not able to add a project via file protocol if the pom is on another drive (windows) even if the url is correct. Looks like a bug to me. -- View this message in context: http://www.nabble.com/POM-file-does-not-exist.-Either-the-POM-you-specified-or-one-of-its-modules-does-not-exist.-tf4752353.html#a14167998 Sent from the Continuum - Users mailing list archive at Nabble.com.
Re: URL's from master POM
I only define the absolute web url once in my parent, in child modules I
have something like:
url/mychildmodule/url
which works fine for me. SCM and distribution urls I only define once in the
parent and use SVN as the SCM with a standard directory layout, with
everything working perfectly.
Kalle
On 12/5/07, Andreas Gies [EMAIL PROTECTED] wrote:
Hi Jim,
thanks for your answer.
1) This is how I am working around it today. I have a property
defined in master pom that resolves to the correct urls. However, I have
to redefine the setting of the url in each project.
Otherwise I have the appendix to the URL I have described.
2) I have redefined the groupId and artifactId simply to clarify
for me whether the problem was a bug related to resolving those
properties. With the approach I have now that redefinition would be
obsolete.
Best regards
Andreas
Jim Sellers schrieb:
A couple of questions:
1) Why don't you specify
https://www.soa-knowledge.net/projects/
https://www.soa-knowledge.net/projects/$%7BurlGroup%7D/$%7BurlId%7D/$%7Bproje
as
a property?
2) Why did you redefine the groupId and artifact id?
I think (unfortunately) that the groupId and artifact id are resolved to
the
pom where they are declared. You may have to re-define it in all the
sub-projects (which was your original question).
It could be something like:
url${serverUrl}${project.groupId}/${project.artifactId}/${
project.version
}/${project.artifactId}/url
:-/
On 12/5/07, Andreas Gies [EMAIL PROTECTED] wrote:
Hello,
i am managing multiple projects form y company using maven 2.0.7. For
that purpose I have created a master pom, that contains the following
section: (Pom A)
...
modelVersion4.0.0/modelVersion
groupIdcom.sonicsw.pso/groupId
artifactIdsonic-maven-parent/artifactId
version1.0/version
packagingpom/packaging
nameMaven Definitions for all Sonic PSO projects/name
url
https://www.soa-knowledge.net/projects/${urlGroup}/${urlId}/${proje
ct.version}/${urlId}/url
properties
urlGroup${project.groupId}/urlGroup
urlId${project.artifactId}/urlId
/properties
...
From that I have inherited another pom (POM B), that does not specify
anything for an URL and serves as a base for a part of my projects.
That
pom has the following coordinates:
...
modelVersion4.0.0/modelVersion
groupIdcom.sonicsw.pso/groupId
artifactIdservices-maven-parent/artifactId
version1.0/version
packagingpom/packaging
nameMaven Definitions for all Sonic ESB Services/name
parent
groupIdcom.sonicsw.pso/groupId
artifactIdsonic-maven-parent/artifactId
version1.0/version
/parent
...
My project now inherits from POM B, which in turn inherits from POM A.
parent
groupIdcom.sonicsw.pso/groupId
artifactIdservices-maven-parent/artifactId
version1.0/version
/parent
groupIdcom.sonicsw.pso.services/groupId
artifactIdWSMQService/artifactId
packagingjar/packaging
version1.0-SNAPSHOT/version
nameWebsphere MQ connectivity services/name
My problem is now in the definition of URLS (for automatically
generating web urls, scm urls, ftp urls etc...)
When I define no url in my project, the generated url is:
https://www.soa-knowledge.net/projects/com.sonicsw.pso.services/WSMQServ
ice/1.0-SNAPSHOT/WSMQService/services-maven-parent/WSMQService
However, if I add the url definition into my project
parent
groupIdcom.sonicsw.pso/groupId
artifactIdservices-maven-parent/artifactId
version1.0/version
/parent
groupIdcom.sonicsw.pso.services/groupId
artifactIdWSMQService/artifactId
packagingjar/packaging
version1.0-SNAPSHOT/version
nameWebsphere MQ connectivity services/name
url
https://www.soa-knowledge.net/projects/${urlGroup}/${urlId}/${proje
ct.version}/${urlId}/url
the url is
https://www.soa-knowledge.net/projects/com.sonicsw.pso.services/WSMQServ
ice/1.0-SNAPSHOT/WSMQService
which is what I intended.
I would like to avoid repeating the URL definitions in each sub project
since this is what I had created the masters for in the first place.
Could somebody explain the behaviour here ? - Can the append be avoided
?
Thank you very much in advance
Andreas
-
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: Migrating to 1.1 NullPointerException
All I can say from the output is that it's related to your log4j properties/setup. Note that properties that start with 'log4j' are interpreted as log4j properties by the maven core, I would rename 'log4j.jarfile' first. Otherwise I'd need more info about your sub-projects setup (use jira to attach a reproducible test case if possible: http://jira.codehaus.org/browse/MAVEN ). Cheers, -Lukas Craig L Russell wrote: Hi, Please reply directly; I'm not subscribed to this list. Some more information on this situation. This is a multiproject and when run from the parent directory, it works. If I go into the subdirectory and run maven, some but not all projects throw NPE. For example, I can run maven tck2.build and it works fine. If I cd tck2; maven build it fails with the NPE. But cd api2; maven jar:install works fine. Thanks, Craig On Dec 4, 2007, at 9:48 AM, Craig L Russell wrote: Hi, Please reply directly; I'm not subscribed to this list. I'm trying to migrate from 1.0.2 to 1.1 and have a problem that I can't figure out. Some of the subprojects build fine; others throw NPE: [Bruiser:~/apache/jdo/trunk] clr% which maven /Users/clr/maven-1.1/bin/maven [Bruiser:jdo/trunk/tck2-legacy] clr% maven java.lang.NullPointerException at java.util.Hashtable.put(Hashtable.java:396) at org.apache.maven.cli.App.customizeLogging(App.java:703) at org.apache.maven.cli.App.initialize(App.java:433) at org.apache.maven.cli.App.initializeMain(App.java:1188) at org.apache.maven.cli.App.doMain(App.java:271) at org.apache.maven.cli.App.main(App.java:217) 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) Any clues where to look for the problem? I expect it's a user error, but I can't figure out where it might be... Craig Russell Architect, Sun Java Enterprise System http://java.sun.com/products/jdo 408 276-5638 mailto:[EMAIL PROTECTED] P.S. A good JDO? O, Gasp! - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
release of maven jar plugin 2.2 in the near future ?
Hei, The latest maven jar plugin release was in August 2006. Is there any plan to make a release this year ? :) http://jira.codehaus.org/browse/MJAR/fixforversion/12878 I see 5 issues still targeted for 2.2 (among which 2 MJAR-78, MJAR-84 have a patch). There are also many issues that are waiting, some with patches. I can help triaging/fixing the remaining issues as long as there's a plan for the release. Otherwise I will have to temporarily fork the sign mojo into the webstart plugin to be able to properly release it. Any takers ? Cheers, -- Jerome Lacoste
how can I just create java files without compiling?
Hallo, I'm a maven newbie :) I have a WSDL file and I'm using the axistools-maven-plugin with the goal wsdl2java to create the associated java files. My problem: I need a command to create the java files only. At the moment I'm using the mvn compile or the mvn install command. Can anyone help me? -- View this message in context: http://www.nabble.com/how-can-I-just-create-java-files-without-compiling--tf4954517s177.html#a14187822 Sent from the Maven - Users mailing list archive at Nabble.com. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
deploy jar with dependencies
Hi I need to build on a machine and deploy the jar on another machine. Now there are dependencies in my jar are to be supplied with this jar, as it is no the build machine the classpath. How should I create a single distributable comprising all the jars? Like Myjar.jar |---com.myapp.app |---lib |--dependent jars Regards, Nishant Sonar
