Re: artifacts not getting indexed?
Hi Joe, The repo indexing and search seems to be working fine to me. It would definitely be helpful if you could provide the logs.. Thanks, Deng On Jan 11, 2008 7:43 AM, Joseph Heck [EMAIL PROTECTED] wrote: Howdy, I've just started digging in to using Archiva. We've been using Proximity for quite a while and we're looking to upgrade/switch out, so I'm taking it a little slow and evaluating what's out there. I dropped our entire artifact set into Archiva (approx 1.8GB of libraries, source, etc) - but afterwards I'm not able to search and find any of those artifacts via the searching function. In the logs, I can see that the repository is scanning them properly, but it just doesn't seem to be picking up the data from our artifacts and adding them to the search index. When I started my experiments, I deployed just a few local things into the archiva repository, and it searched beautifully. I dumped all that out to test out working with the massive library set we've already built up - and that when the search appears to have gotten a little whacked. When I did the big dump, I stopped the process altogether, deleted everything in the data/repository/ directory (including the .index directory) and loaded in the data from my original repository. Does anyone have some suggestions on what I might be doing wrong or overlooking here? I can provide log snippets if that would help illuminate what I'm seeing... -joe
Re: remote repositories verse proxy connectors...??
Hi Mick, I was able to get the dashboard-maven-plugin via a proxy so there must be something wrong with your current configuration.. Anyway, I've detailed below what you need to configure in Archiva and in your settings.xml: 1. Create a local proxy repo (e.g. managed repo) or you could just use Archiva's pre-configured managed repo 'snapshots' as the proxy. 2. Create a remote repository--this is the one you want to proxy. In your case, it's the Codehaus snapshots repo. Let's say you've set it's repo ID as 'codehaus.snapshots'. 3. In the Proxy Connectors page, create a new proxy connector. For the Managed Repo field, set it's value to 'snapshots', and for the Remote Repo field set the value to 'codehaus.snapshots'. Then save the proxy connector. 4. In your settings.xml file, add the following in the pluginRepositories section: pluginRepository idsnapshots/id nameSnapshots Repo/name urlhttp://localhost:8080/archiva/repository/snapshots//url /pluginRepository and if you don't have the 'guest' user account activated for the 'snapshots' repository, you need to specify this in the servers section of your settings.xml file as well: server idsnapshots/id usernameUSERNAME/username passwordPASSWORD/password /server The username and password must be the Archiva user credentials which has either the Repository Manager or Repository Observer role for the 'snapshots' repo. Please verify what you've already got configured with the configuration above.. HTH, Deng On Jan 11, 2008 12:55 AM, Mick Knutson [EMAIL PROTECTED] wrote: I was not able to see the artifact in my browser or on the file system. On Jan 9, 2008 11:04 PM, Maria Odea Ching [EMAIL PROTECTED] wrote: Hi Mick, Sorry, I got a little confused there. You got the The following resource does not exist when you tried browsing the artifact in Archiva? Where you able to see in the file system whether the artifact was actually downloaded in the Proxy Repository? Thanks, Deng On Jan 10, 2008 6:17 AM, Mick Knutson [EMAIL PROTECTED] wrote: I can't even seem to get access to the jar like: http://rc-sun66e.ut.dentegra.lab:8080/archiva/repository/internal/org/codehaus/mojo/dashboard-maven-plugin/1.0-SNAPSHOT/dashboard-maven-plugin-1.0-SNAPSHOT.jar Error 404 Not Found The following resource does not exist: http://rc-sun66e.ut.dentegra.lab:8080/repository/org/codehaus/mojo/dashboard-maven-plugin/1.0-SNAPSHOT/dashboard-maven-plugin-1.0-SNAPSHOT.jar On Jan 9, 2008 1:57 PM, Mick Knutson [EMAIL PROTECTED] wrote: I am trying to crate a project mirror where my team only accesses our repository. But I am now having issues getting http://snapshots.repository.codehaus.org/; resources like dashboard-plugin. Here is my proxy connector setting: Proxy Connector Codehaus-Maven-Snapshot Codehaus-Maven-Snapshot http://snapshots.maven.codehaus.org/maven2 Proxy Connector codehaus Codehaus Snapshots http://snapshots.repository.codehaus.org/ Expand http://rc-sun66e.ut.dentegra.lab:8080/archiva/admin/proxyConnectors.action# THen I still get this error: Reason: Unable to download the artifact from any repository org.codehaus.mojo:dashboard-maven-plugin:pom:1.0-SNAPSHOT from the specified remote repositories: central ( http://repo1.maven.org/maven2), dap.internal ( http://rc-sun66e.ut.dentegra.lab:8080/archiva/repository/internal/ ), dap.snapshots ( http://rc-sun66e.ut.dentegra.lab:8080/archiva/repository/snapshots/) [INFO] [DEBUG] Trace org.apache.maven.lifecycle.LifecycleExecutionException: Unable to build project for plugin 'org.codehaus.mojo:dashboard-maven-plugin': POM ' org.codehaus.mo jo:dashboard-maven-plugin' not found in repository: Unable to download the artifact from any repository org.codehaus.mojo:dashboard-maven-plugin:pom:1.0-SNAPSHOT from the specified remote repositories: central (http://repo1.maven.org/maven2), dap.internal ( http://rc-sun66e.ut.dentegra.lab:8080/archiva/repository/internal/ ), dap.snapshots ( http://rc-sun66e.ut.dentegra.lab:8080/archiva/repository/snapshots/) for project org.codehaus.mojo:dashboard-maven-plugin at org.apache.maven.lifecycle.DefaultLifecycleExecutor.verifyPlugin( DefaultLifecycleExecutor.java:1274) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindPluginToLifecycle( DefaultLifecycleExecutor.java :1221) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings (DefaultLifecycleExecutor.java:987) at
Re: [m1][archiva1.0] Configuring types
What is the physical name for the deployed ejb jar ? It should be EjbXX.jar How did you deploy it on your managed repository ? Archiva support for m1 is limited as legacy (m1) repository path are not as struict as m2 ones, and miss some meta-datas. Nico. 2008/1/15, fabien.dubron [EMAIL PROTECTED]: Hi all, First, congratulations for releasing the 1.0 version of Archiva. I'm working on a multi-project application and i encountered a problem. One of my sub-project is having the type ejb. Also, when i deploy it with maven, it's placed in a folder called ejbs. The problem is that when i'm browsing this folder, i can see the jar created in my ejbs folder but when i try to download it, archiva gives me an error 404 with a message in which the part of the path ejbs is replaced by jars. The url of the page is http://xxx/repository/xxx/ejbs/Ejb-xxx.jar; and the message is : Error 404 Not Found The following resource does not exist: http://xxx/repository/xxx/jars/Ejb-xxx.jar; And the problem happens for the type zip replaced by distribution (???). Is there anything to configure somewhere and if that's the case, where should have i looked in the documentation ? Regards, Fabien. http://www.nabble.com/file/p14840007/error.jpeg -- View this message in context: http://www.nabble.com/-m1--archiva1.0--Configuring-types-tp14840007p14840007.html Sent from the archiva-users mailing list archive at Nabble.com.
[m1][archiva1.0] Configuring types
Hi all, First, congratulations for releasing the 1.0 version of Archiva. I'm working on a multi-project application and i encountered a problem. One of my sub-project is having the type ejb. Also, when i deploy it with maven, it's placed in a folder called ejbs. The problem is that when i'm browsing this folder, i can see the jar created in my ejbs folder but when i try to download it, archiva gives me an error 404 with a message in which the part of the path ejbs is replaced by jars. The url of the page is http://xxx/repository/xxx/ejbs/Ejb-xxx.jar; and the message is : Error 404 Not Found The following resource does not exist: http://xxx/repository/xxx/jars/Ejb-xxx.jar; And the problem happens for the type zip replaced by distribution (???). Is there anything to configure somewhere and if that's the case, where should have i looked in the documentation ? Regards, Fabien. http://www.nabble.com/file/p14840007/error.jpeg -- View this message in context: http://www.nabble.com/-m1--archiva1.0--Configuring-types-tp14840007p14840007.html Sent from the archiva-users mailing list archive at Nabble.com.
Re: [m1][archiva1.0] Configuring types
nicolas de loof-3 wrote: What is the physical name for the deployed ejb jar ? It should be EjbXX.jar How did you deploy it on your managed repository ? /myrepository/myGroupId/ejbs/EjbPFE-0.5-beta-2.jar I deployed it with the maven multiproject:deploy command. Fabien. -- View this message in context: http://www.nabble.com/-m1--archiva1.0--Configuring-types-tp14840007p14842719.html Sent from the archiva-users mailing list archive at Nabble.com.
Re: [archiva 1.0] trying to eliminate external REPO lookups...
On Jan 15, 2008 12:57 PM, Mick Knutson [EMAIL PROTECTED] wrote: I was hoping that my setting up my archiva as a mirror, each developer would not have to go to maven, and codehaus each time they build, but it seems that we are still going out each time: How did you configure your mirrors? (Did you use mirrorOf * to catch any extra repos?) Have you actually watched the network traffic, or are you just basing this on the messages you see? -- Wendy
[c 1.1, archiva 1] Deployment Repository directory parameter
I wnat to know what I should set this to: * Deployment Repository Directory: * * Enter the deployment repository directory of the Continuum web application * Should I set this to the path for my archive repository? http://rc-sun66e.ut.dentegra.lab:8080/archiva/repository/internal/ so continuum would directly put files into the location, then archiva would automatically pick them up? -- 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 ---
[c 1.1] schedule build per svn check-in?
Is it possible to kick off the build each time there is a new update available in svn? -- 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: [c 1.1, archiva 1] Deployment Repository directory parameter
On Jan 15, 2008 12:37 PM, Mick Knutson [EMAIL PROTECTED] wrote: I wnat to know what I should set this to: * Deployment Repository Directory: * * Enter the deployment repository directory of the Continuum web application * Should I set this to the path for my archive repository? http://rc-sun66e.ut.dentegra.lab:8080/archiva/repository/internal/ so continuum would directly put files into the location, then archiva would automatically pick them up? You could, if both Archiva and Continuum happen to be on the same server-- it's meant to be a _directory_ not a url. (Check JIRA, though, I think this feature is broken in Continuum 1.1.) -- Wendy
Re: [c1.1] derby issue with .lck files not being cleaned up
On Jan 15, 2008 12:29 PM, Mick Knutson [EMAIL PROTECTED] wrote: I have been running derby almost file. But when I bounce Tomcat, the db.lckfiles are not removed, thus giving me an error when I re-start Tomcat as the DB is already in use, which it is not. It is only because the lck files are still present. When I delete those 2 files, then re-start tomcat, everything is fine. So you've mentioned. And this seems to happen when using embedded Derby. The suggestion, then, is to use a standalone database. Derby Network Server is one of the options, since your preferred choice of Oracle 10g doesn't work. Here's the page I mentioned earlier. Adjust as necessary... http://docs.codehaus.org/display/MAVENUSER/Archiva+User+DB+on+Derby+Network+Server -- Wendy
Re: [c 1.1] Possible to use the Continuum build number as part of the artifact name?
Continuum define few properties that are sent to the maven process during the build like the current build number, the next, last state and the group name. Look at your logs and you'll see them when a build start the maven process Emmanuel On Jan 15, 2008 10:54 PM, Mick Knutson [EMAIL PROTECTED] wrote: I want to create our war final name appended with the continuum build number: myProject-userwebapp-1.25-build-42.war Is this possible? -- 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: [c 1.1] Possible to use the Continuum build number as part of the artifact name?
Have a look here [1]. -- Olivier [1] http://www.nabble.com/Version-and-build-number-to-Ant-build-process-td14593864.html 2008/1/15, Mick Knutson [EMAIL PROTECTED]: I want to create our war final name appended with the continuum build number: myProject-userwebapp-1.25-build-42.war Is this possible? -- 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 ---
Single directory permissions
In a simple setup using packagingwar/packaging, is there a way to specify permissions for a single directory? I'm developing a small web-app, which has to upload files, so I'm looking for a way to just specify chmod 777 on the uploads directory /src/webapp/uploads. I would really appreciate any help. Thanks. -GC -- View this message in context: http://www.nabble.com/Single-directory-permissions-tp14834452s177p14834452.html 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: Setting Java System property
I still haven't moved forwards with this. Does any one have any ideas? -Original Message- From: Matthew Tordoff [mailto:[EMAIL PROTECTED] Sent: 14 January 2008 17:56 To: Maven Users List Subject: Setting Java System property Hi all, I am having problems setting a Java System Property as part of my build. I have tried setting it in all kinds of places and the only one that I have found to work is setting it as part of the maven command line as follows: mvn compile -Dsystemprop=blah Setting in the above way is the only way in which I appear to be able to access the file at a later stage from one of my MOJOs via System.getProperty(systemprop) . I don't want to have to set this at the command line because I want to minimise what is typed each time mvn is run. The other approaches I have tried are... Within pom.xml - configuration systempropblah/systemprop /configuration also... configuration properties systempropblah/systemprop properties /configuration within settings.xml... properties systempropblah/systemprop properties Any help would be greatly appreciated. Regards, Matt The content of this e-mail is confidential and may be privileged. It may be read, copied and used only by the intended recipient and may not be disclosed, copied or distributed. If you received this email in error, please contact the sender immediately by return e-mail or by telephoning +44 20 7260 2000, delete it and do not disclose its contents to any person. You should take full responsibility for checking this email for viruses. Markit reserves the right to monitor all e-mail communications through its network. Markit and its affiliated companies make no warranty as to the accuracy or completeness of any information contained in this message and hereby exclude any liability of any kind for the information contained herein. Any opinions expressed in this message are those of the author and do not necessarily reflect the opinions of Markit. For full details about Markit, its offerings and legal terms and conditions, please see Markit's website at http://www.markit.com http://www.markit.com/ . The content of this e-mail is confidential and may be privileged. It may be read, copied and used only by the intended recipient and may not be disclosed, copied or distributed. If you received this email in error, please contact the sender immediately by return e-mail or by telephoning +44 20 7260 2000, delete it and do not disclose its contents to any person. You should take full responsibility for checking this email for viruses. Markit reserves the right to monitor all e-mail communications through its network. Markit and its affiliated companies make no warranty as to the accuracy or completeness of any information contained in this message and hereby exclude any liability of any kind for the information contained herein. Any opinions expressed in this message are those of the author and do not necessarily reflect the opinions of Markit. For full details about Markit, its offerings and legal terms and conditions, please see Markit's website at http://www.markit.com http://www.markit.com/ . - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Is there a problem with surefire-junit-2.4?
Ben Lidgey wrote: Thanks for that. How can I see what has changed as something is trying to download 2.4-SNAPSHOT all of a sudden? It is concerning from a build reproducibility point of view if something has changed without us knowing. My thought was that if a pom.xml does not specify a plugin version then maven will look for the latest one. Now that surefire 2.4 is imminent maybe there are some references to it somewhere that are making it the latest version? If no version is specified for a plugin it will by default lookup the latest snapshot. To nail down the version you need to explicitly set it to a released version - in this case 2.3.1 or 2.4 when it will be released later today. In general, IMO it's good pratice to fix versions on plugins and only upgrade when required. Cheers - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Setting Java System property
http://maven.apache.org/ref/current/maven-model/maven.html Search for properties. Matthew Tordoff [EMAIL PROTECTED] schrieb: I still haven't moved forwards with this. Does any one have any ideas? -Original Message- From: Matthew Tordoff [mailto:[EMAIL PROTECTED] Sent: 14 January 2008 17:56 To: Maven Users List Subject: Setting Java System property Hi all, I am having problems setting a Java System Property as part of my build. I have tried setting it in all kinds of places and the only one that I have found to work is setting it as part of the maven command line as follows: mvn compile -Dsystemprop=blah Setting in the above way is the only way in which I appear to be able to access the file at a later stage from one of my MOJOs via System.getProperty(systemprop) . I don't want to have to set this at the command line because I want to minimise what is typed each time mvn is run. The other approaches I have tried are... Within pom.xml - configuration systempropblah/systemprop /configuration also... configuration properties systempropblah/systemprop properties /configuration within settings.xml... properties systempropblah/systemprop properties Any help would be greatly appreciated. Regards, Matt The content of this e-mail is confidential and may be privileged. It may be read, copied and used only by the intended recipient and may not be disclosed, copied or distributed. If you received this email in error, please contact the sender immediately by return e-mail or by telephoning +44 20 7260 2000, delete it and do not disclose its contents to any person. You should take full responsibility for checking this email for viruses. Markit reserves the right to monitor all e-mail communications through its network. Markit and its affiliated companies make no warranty as to the accuracy or completeness of any information contained in this message and hereby exclude any liability of any kind for the information contained herein. Any opinions expressed in this message are those of the author and do not necessarily reflect the opinions of Markit. For full details about Markit, its offerings and legal terms and conditions, please see Markit's website at http://www.markit.com http://www.markit.com/ . The content of this e-mail is confidential and may be privileged. It may be read, copied and used only by the intended recipient and may not be disclosed, copied or distributed. If you received this email in error, please contact the sender immediately by return e-mail or by telephoning +44 20 7260 2000, delete it and do not disclose its contents to any person. You should take full responsibility for checking this email for viruses. Markit reserves the right to monitor all e-mail communications through its network. Markit and its affiliated companies make no warranty as to the accuracy or completeness of any information contained in this message and hereby exclude any liability of any kind for the information contained herein. Any opinions expressed in this message are those of the author and do not necessarily reflect the opinions of Markit. For full details about Markit, its offerings and legal terms and conditions, please see Markit's website at http://www.markit.com http://www.markit.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]
Howto disable a profile when another is enabled ?
Hello, I have used this configuration in a project to select the SOAP stack to use for WSDL - Java code generation profile idrelease/id properties releasetrue/release /properties build // WSDL2Java for Webpshere /profile profile idaxis/id activation property name!release/name /property /activation build // WSDL2Java for Axis /profile I now have upgraded to maven 2.0.8 and this doesn't work anymore : mvn help:active-profiles -Prelease The following profiles are active: - release (source: pom) - axis (source: pom) Is there another way to DISABLE a profile, when another is enabled ?
RE: Setting Java System property
Hi Matthew, For my unittest I included the following to set system properties: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-plugin/artifactId configuration forkModeonce/forkMode systemProperties property name java.util.prefs.PreferencesFactory /name value nl.xup.prefs.memoryprefs.MemoryPreferencesFactory /value /property /systemProperties /configuration /plugin I hope this helps. Kind regards, Minto van der Sluis -Oorspronkelijk bericht- Van: Matthew Tordoff [mailto:[EMAIL PROTECTED] Verzonden: dinsdag 15 januari 2008 10:43 Aan: Maven Users List Onderwerp: RE: Setting Java System property I still haven't moved forwards with this. Does any one have any ideas? -Original Message- From: Matthew Tordoff [mailto:[EMAIL PROTECTED] Sent: 14 January 2008 17:56 To: Maven Users List Subject: Setting Java System property Hi all, I am having problems setting a Java System Property as part of my build. I have tried setting it in all kinds of places and the only one that I have found to work is setting it as part of the maven command line as follows: mvn compile -Dsystemprop=blah Setting in the above way is the only way in which I appear to be able to access the file at a later stage from one of my MOJOs via System.getProperty(systemprop) . I don't want to have to set this at the command line because I want to minimise what is typed each time mvn is run. The other approaches I have tried are... Within pom.xml - configuration systempropblah/systemprop /configuration also... configuration properties systempropblah/systemprop properties /configuration within settings.xml... properties systempropblah/systemprop properties Any help would be greatly appreciated. Regards, Matt The content of this e-mail is confidential and may be privileged. It may be read, copied and used only by the intended recipient and may not be disclosed, copied or distributed. If you received this email in error, please contact the sender immediately by return e-mail or by telephoning +44 20 7260 2000, delete it and do not disclose its contents to any person. You should take full responsibility for checking this email for viruses. Markit reserves the right to monitor all e-mail communications through its network. Markit and its affiliated companies make no warranty as to the accuracy or completeness of any information contained in this message and hereby exclude any liability of any kind for the information contained herein. Any opinions expressed in this message are those of the author and do not necessarily reflect the opinions of Markit. For full details about Markit, its offerings and legal terms and conditions, please see Markit's website at http://www.markit.com http://www.markit.com/ . The content of this e-mail is confidential and may be privileged. It may be read, copied and used only by the intended recipient and may not be disclosed, copied or distributed. If you received this email in error, please contact the sender immediately by return e-mail or by telephoning +44 20 7260 2000, delete it and do not disclose its contents to any person. You should take full responsibility for checking this email for viruses. Markit reserves the right to monitor all e-mail communications through its network. Markit and its affiliated companies make no warranty as to the accuracy or completeness of any information contained in this message and hereby exclude any liability of any kind for the information contained herein. Any opinions expressed in this message are those of the author and do not necessarily reflect the opinions of Markit. For full details about Markit, its offerings and legal terms and conditions, please see Markit's website at http://www.markit.com http://www.markit.com/ . - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] DISCLAIMER De informatie in deze e-mail is vertrouwelijk en uitsluitend bestemd voor de geadresseerde. Indien u niet de geadresseerde bent, wordt u er hierbij op gewezen, dat u geen recht heeft kennis te nemen van de rest van deze e-mail, deze te gebruiken, te kopieren of te verstrekken aan andere personen dan de geadresseerde. Indien u deze e-mail abusievelijk hebt ontvangen, brengt u dan alstublieft de afzender op de
RE: Setting Java System property
Thanks for that but I have already looked at the appropriate documentation. I have tried setting the system property in all of those locations and for some reason none of the settings are passed through. I did find a JIRA bug opened against this problem somewhere, and thus am guessing this functionality isn't yet available. -Original Message- From: Simon Kitching [mailto:[EMAIL PROTECTED] Sent: 15 January 2008 09:53 To: Maven Users List Cc: Matthew Tordoff Subject: RE: Setting Java System property http://maven.apache.org/ref/current/maven-model/maven.html Search for properties. Matthew Tordoff [EMAIL PROTECTED] schrieb: I still haven't moved forwards with this. Does any one have any ideas? -Original Message- From: Matthew Tordoff [mailto:[EMAIL PROTECTED] Sent: 14 January 2008 17:56 To: Maven Users List Subject: Setting Java System property Hi all, I am having problems setting a Java System Property as part of my build. I have tried setting it in all kinds of places and the only one that I have found to work is setting it as part of the maven command line as follows: mvn compile -Dsystemprop=blah Setting in the above way is the only way in which I appear to be able to access the file at a later stage from one of my MOJOs via System.getProperty(systemprop) . I don't want to have to set this at the command line because I want to minimise what is typed each time mvn is run. The other approaches I have tried are... Within pom.xml - configuration systempropblah/systemprop /configuration also... configuration properties systempropblah/systemprop properties /configuration within settings.xml... properties systempropblah/systemprop properties Any help would be greatly appreciated. Regards, Matt The content of this e-mail is confidential and may be privileged. It may be read, copied and used only by the intended recipient and may not be disclosed, copied or distributed. If you received this email in error, please contact the sender immediately by return e-mail or by telephoning +44 20 7260 2000, delete it and do not disclose its contents to any person. You should take full responsibility for checking this email for viruses. Markit reserves the right to monitor all e-mail communications through its network. Markit and its affiliated companies make no warranty as to the accuracy or completeness of any information contained in this message and hereby exclude any liability of any kind for the information contained herein. Any opinions expressed in this message are those of the author and do not necessarily reflect the opinions of Markit. For full details about Markit, its offerings and legal terms and conditions, please see Markit's website at http://www.markit.com http://www.markit.com/ . The content of this e-mail is confidential and may be privileged. It may be read, copied and used only by the intended recipient and may not be disclosed, copied or distributed. If you received this email in error, please contact the sender immediately by return e-mail or by telephoning +44 20 7260 2000, delete it and do not disclose its contents to any person. You should take full responsibility for checking this email for viruses. Markit reserves the right to monitor all e-mail communications through its network. Markit and its affiliated companies make no warranty as to the accuracy or completeness of any information contained in this message and hereby exclude any liability of any kind for the information contained herein. Any opinions expressed in this message are those of the author and do not necessarily reflect the opinions of Markit. For full details about Markit, its offerings and legal terms and conditions, please see Markit's website at http://www.markit.com http://www.markit.com/ . - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] The content of this e-mail is confidential and may be privileged. It may be read, copied and used only by the intended recipient and may not be disclosed, copied or distributed. If you received this email in error, please contact the sender immediately by return e-mail or by telephoning +44 20 7260 2000, delete it and do not disclose its contents to any person. You should take full responsibility for checking this email for viruses. Markit reserves the right to monitor all e-mail communications through its network. Markit and its affiliated companies make no warranty as to the accuracy or completeness of any information contained in this message and hereby exclude any liability of any kind for the information contained herein. Any opinions expressed in this message are those of the author and do not necessarily reflect the opinions of Markit. For full details about Markit, its offerings and
RE: Setting Java System property
Hi Minto, The reason that this works for this plugin, is because inside of the plugin it will explicitly execute a System.setProperty(key, value) operation with the name value pair that was passed. This is not however, standard functionality across all plugins. I am essentially having to write this same functionality into each of my plugins, where actually I just wanted to set this property one time in my pom or settings.xml, which would be applied across all plugins, however, at this stage this does not seem to be available. Thanks for the response. Matt -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: 15 January 2008 10:56 To: users@maven.apache.org Subject: RE: Setting Java System property Hi Matthew, For my unittest I included the following to set system properties: plugin groupIdorg.apache.maven.plugins/groupId artifactIdmaven-surefire-plugin/artifactId configuration forkModeonce/forkMode systemProperties property name java.util.prefs.PreferencesFactory /name value nl.xup.prefs.memoryprefs.MemoryPreferencesFactory /value /property /systemProperties /configuration /plugin I hope this helps. Kind regards, Minto van der Sluis -Oorspronkelijk bericht- Van: Matthew Tordoff [mailto:[EMAIL PROTECTED] Verzonden: dinsdag 15 januari 2008 10:43 Aan: Maven Users List Onderwerp: RE: Setting Java System property I still haven't moved forwards with this. Does any one have any ideas? -Original Message- From: Matthew Tordoff [mailto:[EMAIL PROTECTED] Sent: 14 January 2008 17:56 To: Maven Users List Subject: Setting Java System property Hi all, I am having problems setting a Java System Property as part of my build. I have tried setting it in all kinds of places and the only one that I have found to work is setting it as part of the maven command line as follows: mvn compile -Dsystemprop=blah Setting in the above way is the only way in which I appear to be able to access the file at a later stage from one of my MOJOs via System.getProperty(systemprop) . I don't want to have to set this at the command line because I want to minimise what is typed each time mvn is run. The other approaches I have tried are... Within pom.xml - configuration systempropblah/systemprop /configuration also... configuration properties systempropblah/systemprop properties /configuration within settings.xml... properties systempropblah/systemprop properties Any help would be greatly appreciated. Regards, Matt The content of this e-mail is confidential and may be privileged. It may be read, copied and used only by the intended recipient and may not be disclosed, copied or distributed. If you received this email in error, please contact the sender immediately by return e-mail or by telephoning +44 20 7260 2000, delete it and do not disclose its contents to any person. You should take full responsibility for checking this email for viruses. Markit reserves the right to monitor all e-mail communications through its network. Markit and its affiliated companies make no warranty as to the accuracy or completeness of any information contained in this message and hereby exclude any liability of any kind for the information contained herein. Any opinions expressed in this message are those of the author and do not necessarily reflect the opinions of Markit. For full details about Markit, its offerings and legal terms and conditions, please see Markit's website at http://www.markit.com http://www.markit.com/ . The content of this e-mail is confidential and may be privileged. It may be read, copied and used only by the intended recipient and may not be disclosed, copied or distributed. If you received this email in error, please contact the sender immediately by return e-mail or by telephoning +44 20 7260 2000, delete it and do not disclose its contents to any person. You should take full responsibility for checking this email for viruses. Markit reserves the right to monitor all e-mail communications through its network. Markit and its affiliated companies make no warranty as to the accuracy or completeness of any information contained in this message and hereby exclude any liability of any kind for the information contained herein. Any opinions expressed in this message are those of the author and do not necessarily reflect the opinions of Markit. For full
RE: Setting Java System property
Matthew Tordoff [EMAIL PROTECTED] schrieb: Thanks for that but I have already looked at the appropriate documentation. I have tried setting the system property in all of those locations and for some reason none of the settings are passed through. I did find a JIRA bug opened against this problem somewhere, and thus am guessing this functionality isn't yet available. Are you trying to set a global property, or one specific to just a particular plugin? You appear to be trying to do the latter by nesting your properties info inside a configuration tag. However the page I referred you to says about configuration: The configuration as DOM object. which strongly implies to me that this is only interpreted by the plugin, and you cannot assume that maven looks in here, ie the plugin alone is responsible for interpreting the contents. I could be wrong here, but don't think so.. Setting properties in a pom which are global to all stuff in the pom (and child poms) is trivial, and definitely works when *not* nested within a configuration element (as documented in the page I referred you to): project ... properties foofooval/foo /properties /project It also works in settings.xml, but you do need to be sure that the profile it is defined within is active.. Regards, Simon - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Setting Java System property
Hi Simon, Sorry for the confusion, but I am not trying to set a basic property, but a JVM System Property. A property which would be accessible from the Java code using System.getProperty(PropertyName); I then want that property to be available to every plugin I execute. Matt -Original Message- From: Simon Kitching [mailto:[EMAIL PROTECTED] Sent: 15 January 2008 12:39 To: Maven Users List; Matthew Tordoff Subject: RE: Setting Java System property Matthew Tordoff [EMAIL PROTECTED] schrieb: Thanks for that but I have already looked at the appropriate documentation. I have tried setting the system property in all of those locations and for some reason none of the settings are passed through. I did find a JIRA bug opened against this problem somewhere, and thus am guessing this functionality isn't yet available. Are you trying to set a global property, or one specific to just a particular plugin? You appear to be trying to do the latter by nesting your properties info inside a configuration tag. However the page I referred you to says about configuration: The configuration as DOM object. which strongly implies to me that this is only interpreted by the plugin, and you cannot assume that maven looks in here, ie the plugin alone is responsible for interpreting the contents. I could be wrong here, but don't think so.. Setting properties in a pom which are global to all stuff in the pom (and child poms) is trivial, and definitely works when *not* nested within a configuration element (as documented in the page I referred you to): project ... properties foofooval/foo /properties /project It also works in settings.xml, but you do need to be sure that the profile it is defined within is active.. Regards, Simon The content of this e-mail is confidential and may be privileged. It may be read, copied and used only by the intended recipient and may not be disclosed, copied or distributed. If you received this email in error, please contact the sender immediately by return e-mail or by telephoning +44 20 7260 2000, delete it and do not disclose its contents to any person. You should take full responsibility for checking this email for viruses. Markit reserves the right to monitor all e-mail communications through its network. Markit and its affiliated companies make no warranty as to the accuracy or completeness of any information contained in this message and hereby exclude any liability of any kind for the information contained herein. Any opinions expressed in this message are those of the author and do not necessarily reflect the opinions of Markit. For full details about Markit, its offerings and legal terms and conditions, please see Markit's website at http://www.markit.com http://www.markit.com/ . - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Migrate a J2ME Ant build?
I'm not new to Maven at all. I'm new to J2ME but not as much anymore. Basically I'm trying to build a super project that encompasses everything from the client to the server(s) which are all currently managed by Maven. I'd build a parent pom that sits ontop of these pieces and builds and pushes them all to a QA box. Like I said everything else is already managed by Maven, it's just this one piece that's handled by Ant. The result of the Ant build is a simple Jar and Jad file. It should be trivial to include these as part of the master build. Wayne Fay wrote: Can I ask why you're looking to migrate? If you're completely new to Maven, it may be challenging to meet your requirements (4-6hrs etc), especially if plugins aren't working. I haven't done much with J2ME much less with Maven, so I'm going to be zero help. Wayne On 1/14/08, Clifton [EMAIL PROTECTED] wrote: Can somebody help me find the quickest easiest way to migrate a custom J2ME Ant build to Maven? We have deliverable in two weeks and I have roughly 4-6hrs top to devote to this. (Maybe more if I work off clock.) I tried the pyx4me plugin but had no luck running it. There's a bug somewhere around the cal to preverify that seems to pass the name of a non-existant jar file as a param. Also we are building RIM specific .cod files for blackberry. Any help/guidance/assistance would be helpful. I have some ideas revolving around calling directly into our current ant build from the deploy phase (binding ant-run) but I'm looking to do whatever works best and I'm not sure how to include the jad file this way. -- View this message in context: http://www.nabble.com/Migrate-a-J2ME-Ant-build--tp14829001s177p14829001.html 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] -- View this message in context: http://www.nabble.com/Migrate-a-J2ME-Ant-build--tp14829001s177p14839848.html 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: Setting Java System property
Simon Kitching [EMAIL PROTECTED] schrieb:
Matthew Tordoff [EMAIL PROTECTED] schrieb:
Thanks for that but I have already looked at the appropriate
documentation. I have tried setting the system property in all of those
locations and for some reason none of the settings are passed through. I
did find a JIRA bug opened against this problem somewhere, and thus am
guessing this functionality isn't yet available.
Are you trying to set a global property, or one specific to just a
particular plugin?
You appear to be trying to do the latter by nesting your properties info
inside a configuration tag. However the page I referred you to says about
configuration:
The configuration as DOM object.
which strongly implies to me that this is only interpreted by the plugin, and
you cannot assume that maven looks in here, ie the plugin alone is
responsible for interpreting the contents. I could be wrong here, but don't
think so..
Setting properties in a pom which are global to all stuff in the pom (and
child poms) is trivial, and definitely works when *not* nested within a
configuration element (as documented in the page I referred you to):
project
...
properties
foofooval/foo
/properties
/project
It also works in settings.xml, but you do need to be sure that the profile it
is defined within is active..
Ah..hang on a minute. Your original mail said:
quote
Setting in the above way is the only way in which I appear to be able to
access the file at a later stage from one of my MOJOs via
System.getProperty(systemprop) .
/quote
So your problem is not setting properties that you then reference via
${propname} in your pom, but that you want to access them from a custom maven
plugin?
I don't think that maven properties get stored into the system properties
object. I haven't written any custom maven plugins myself, but expect your
custom plugin code will need to look up maven properties using a maven api (or
have plexus inject it) rather than using System.getProperty.
Regards, Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Running javadoc:javadoc with site:site causes problems
Hi Michael, I haven't tried to use javadoc:javadoc but do get javadoc output with my pom configured like below and running site:site or even site:run reporting ... plugins plugin artifactIdmaven-javadoc-plugin/artifactId /plugin /plugins ... /reporting I'm not sure if that's what you're after, but does crank out javadoc in the Maven generated site. Regards, Randall -Original Message- From: Michael [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 15, 2008 7:14 AM To: users@maven.apache.org Subject: Running javadoc:javadoc with site:site causes problems Hi, I configured my pom reporting to run javadoc:javadoc within the site generation. Running javadoc:javadoc outputs no errors, running site:site gives me tonnes of errors telling that some packages cannot be resolved. I don't understand that since the doc site of javadoc plugins says site:site runs javadoc:javadoc too. Did I something wrong? Any necessary resource can be provided. Thx in advance, Mike -- NO OOXML - Say NO To Microsoft Office broken standard http://www.noooxml.org - 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]
mojo cookbook; resolving transitively
The Mojo Developer Cookbook (http://docs.codehaus.org/display/MAVENUSER/Mojo+Developer+Cookbook) is great. In it, there's a section on Resolving Transitively. This works great - however, the artifact set that is resolved is based on Maven's idea of which graph edges ought to be considered for resolution. For example, if I have a WAR file, then any declared dependencies that are JARs (and POM I think) are included, and those artifacts have their dependencies added to the list (and so on, recursively). The end result resolves to a single version for each JAR artifact. However - if the WAR file has a WAR dependency, then it will not be considered, and any JAR files in there won't be included in the set that the version is resolved in. This is the behaviour that I want, where I have a WAR of WARs, and I want to calculate the resolved set of dependencies. a) How can I interject my own requirements for dependency traversal? b) Is / how is this changed in 2.1 - all the methods on ArtifactResolver have been condensed down into 1.. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Running javadoc:javadoc with site:site causes problems
Hi, I configured my pom reporting to run javadoc:javadoc within the site generation. Running javadoc:javadoc outputs no errors, running site:site gives me tonnes of errors telling that some packages cannot be resolved. I don't understand that since the doc site of javadoc plugins says site:site runs javadoc:javadoc too. Did I something wrong? Any necessary resource can be provided. Thx in advance, Mike -- NO OOXML - Say NO To Microsoft Office broken standard http://www.noooxml.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m1][archiva1.0] Configuring types
Hi all, First, congratulations for releasing the 1.0 version of Archiva. I'm working on a multi-project application and i encountered a problem. One of my sub-project is having the type ejb. Also, when i deploy it with maven, it's placed in a folder called ejbs. The problem is that when i'm browsing this folder, i can see the jar created in my ejbs folder but when i try to download it, archiva gives me an error 404 with a message in which the part of the path ejbs is replaced by jars. The url of the page is http://xxx/repository/xxx/ejbs/Ejb-xxx.jar; and the message is : Error 404 Not Found The following resource does not exist: http://xxx/repository/xxx/jars/Ejb-xxx.jar; And the problem happens for the type zip replaced by distribution (???). Regards, Fabien. http://www.nabble.com/file/p14840007/error.jpeg -- View this message in context: http://www.nabble.com/-m1--archiva1.0--Configuring-types-tp14840007p14840007.html Sent from the archiva-users mailing list archive at Nabble.com.
Re: Running javadoc:javadoc with site:site causes problems
Randall Fidler wrote: What's your project file structure? Nothing in your POM stuck out as being obviously wrong at a quick glance... browse the source: http://dev.fckeditor.net/browser/FCKeditor.Java/branches/2.4 Also, what version of the plugin are you using? Perhaps you've got an older version of the javadoc plugin. Not sure if there have been any new releases but might be worth running with -up (I think that's the switch) to see if there is a new JavaDoc plugin. version 2.3 One more thing, what version of Maven? I took a quick peek but didn't see it in your log files. version 2.0.6 -Original Message- From: Michael [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 15, 2008 7:34 AM To: Maven Users List Subject: Re: Running javadoc:javadoc with site:site causes problems Randall Fidler wrote: Hi Michael, I haven't tried to use javadoc:javadoc but do get javadoc output with my pom configured like below and running site:site or even site:run reporting ... plugins plugin artifactIdmaven-javadoc-plugin/artifactId /plugin /plugins ... /reporting I'm not sure if that's what you're after, but does crank out javadoc in the Maven generated site. Hi Randall, let's make it clearer: This is my pom.xml: http://rafb.net/p/Ox0fS259.html this is what I get when I run mvn javadoc:javadoc: http://rafb.net/p/U0KqMb29.html this is what I get when I run mvn site:site: http://rafb.net/p/7xREXc27.html Do you see the diffrence? 1. It generates testdocs for some reason 2. it says it can't resolve types and classes which did not happen with javadoc:javadoc Any idea? -- NO OOXML - Say NO To Microsoft Office broken standard http://www.noooxml.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to make assembly:assembly depend on goals?
[EMAIL PROTECTED] wrote: This can be be perfectly done by using the lifecycle of maven. In short, don't site:site, but call the phase site (thus mvn site instead of mvn site:site). Also, you could bind the assembly plugin to the package phase and thus run mvn package instead of mvn assembly:assembly. Try reading this page for more informatin: http://www.sonatype.com/book/lifecycle.html Still seems like a riddle to me. I am aware about the attached mojo but I cannot say depends on, site, package but only on one of these too. I guess, I still don't understand the lifecycle system Mike -Original Message- From: Michael [mailto:[EMAIL PROTECTED] Sent: Tue 1/15/2008 3:37 PM To: users@maven.apache.org Subject: How to make assembly:assembly depend on goals? Hi, I kinda miss task dependencies like in Ant. My basic idea is provide a bin distro which easily can be done with assembly plugin. But I want assembly:assembly depend on site:site since running assembly:assembly runs package only in advance. Is this possible? Thx, Mike -- NO OOXML - Say NO To Microsoft Office broken standard http://www.noooxml.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
How to make assembly:assembly depend on goals?
Hi, I kinda miss task dependencies like in Ant. My basic idea is provide a bin distro which easily can be done with assembly plugin. But I want assembly:assembly depend on site:site since running assembly:assembly runs package only in advance. Is this possible? Thx, Mike -- NO OOXML - Say NO To Microsoft Office broken standard http://www.noooxml.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Running javadoc:javadoc with site:site causes problems
Randall Fidler wrote: Hi Michael, I haven't tried to use javadoc:javadoc but do get javadoc output with my pom configured like below and running site:site or even site:run reporting ... plugins plugin artifactIdmaven-javadoc-plugin/artifactId /plugin /plugins ... /reporting I'm not sure if that's what you're after, but does crank out javadoc in the Maven generated site. Hi Randall, let's make it clearer: This is my pom.xml: http://rafb.net/p/Ox0fS259.html this is what I get when I run mvn javadoc:javadoc: http://rafb.net/p/U0KqMb29.html this is what I get when I run mvn site:site: http://rafb.net/p/7xREXc27.html Do you see the diffrence? 1. It generates testdocs for some reason 2. it says it can't resolve types and classes which did not happen with javadoc:javadoc Any idea? -- NO OOXML - Say NO To Microsoft Office broken standard http://www.noooxml.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to make assembly:assembly depend on goals?
This can be be perfectly done by using the lifecycle of maven. In short, don't site:site, but call the phase site (thus mvn site instead of mvn site:site). Also, you could bind the assembly plugin to the package phase and thus run mvn package instead of mvn assembly:assembly. Try reading this page for more informatin: http://www.sonatype.com/book/lifecycle.html Hth, Nick Stolwijk -Original Message- From: Michael [mailto:[EMAIL PROTECTED] Sent: Tue 1/15/2008 3:37 PM To: users@maven.apache.org Subject: How to make assembly:assembly depend on goals? Hi, I kinda miss task dependencies like in Ant. My basic idea is provide a bin distro which easily can be done with assembly plugin. But I want assembly:assembly depend on site:site since running assembly:assembly runs package only in advance. Is this possible? Thx, Mike -- NO OOXML - Say NO To Microsoft Office broken standard http://www.noooxml.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Running javadoc:javadoc with site:site causes problems
What's your project file structure? Nothing in your POM stuck out as being obviously wrong at a quick glance... Also, what version of the plugin are you using? Perhaps you've got an older version of the javadoc plugin. Not sure if there have been any new releases but might be worth running with -up (I think that's the switch) to see if there is a new JavaDoc plugin. One more thing, what version of Maven? I took a quick peek but didn't see it in your log files. Regards, Randall -Original Message- From: Michael [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 15, 2008 7:34 AM To: Maven Users List Subject: Re: Running javadoc:javadoc with site:site causes problems Randall Fidler wrote: Hi Michael, I haven't tried to use javadoc:javadoc but do get javadoc output with my pom configured like below and running site:site or even site:run reporting ... plugins plugin artifactIdmaven-javadoc-plugin/artifactId /plugin /plugins ... /reporting I'm not sure if that's what you're after, but does crank out javadoc in the Maven generated site. Hi Randall, let's make it clearer: This is my pom.xml: http://rafb.net/p/Ox0fS259.html this is what I get when I run mvn javadoc:javadoc: http://rafb.net/p/U0KqMb29.html this is what I get when I run mvn site:site: http://rafb.net/p/7xREXc27.html Do you see the diffrence? 1. It generates testdocs for some reason 2. it says it can't resolve types and classes which did not happen with javadoc:javadoc Any idea? -- NO OOXML - Say NO To Microsoft Office broken standard http://www.noooxml.org - 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: How to make assembly:assembly depend on goals?
Looking at your post again and I think I understand what you want to accomplish. You want to include inside the assembly the generated site? Take a look at the Assembly mojo [1] and especially this parameter: includeSite boolean Set to true to include the site generated by site:site goal. Default value is false. I guess that is what you want. With regards, Nick Stolwijk [1]http://maven.apache.org/plugins/maven-assembly-plugin/assembly-mojo.html -Original Message- From: Michael [mailto:[EMAIL PROTECTED] Sent: Tue 1/15/2008 3:53 PM To: Maven Users List Subject: Re: How to make assembly:assembly depend on goals? [EMAIL PROTECTED] wrote: This can be be perfectly done by using the lifecycle of maven. In short, don't site:site, but call the phase site (thus mvn site instead of mvn site:site). Also, you could bind the assembly plugin to the package phase and thus run mvn package instead of mvn assembly:assembly. Try reading this page for more informatin: http://www.sonatype.com/book/lifecycle.html Still seems like a riddle to me. I am aware about the attached mojo but I cannot say depends on, site, package but only on one of these too. I guess, I still don't understand the lifecycle system Mike -Original Message- From: Michael [mailto:[EMAIL PROTECTED] Sent: Tue 1/15/2008 3:37 PM To: users@maven.apache.org Subject: How to make assembly:assembly depend on goals? Hi, I kinda miss task dependencies like in Ant. My basic idea is provide a bin distro which easily can be done with assembly plugin. But I want assembly:assembly depend on site:site since running assembly:assembly runs package only in advance. Is this possible? Thx, Mike -- NO OOXML - Say NO To Microsoft Office broken standard http://www.noooxml.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to make assembly:assembly depend on goals?
[EMAIL PROTECTED] wrote: Looking at your post again and I think I understand what you want to accomplish. You want to include inside the assembly the generated site? Take a look at the Assembly mojo [1] and especially this parameter: includeSite boolean Set to true to include the site generated by site:site goal. Default value is false. I guess that is what you want. Unfortunately, it isn't for 2 reasons: 1. is is deprecated in favor of includeSiteDirectory in the descriptor file 2. setting to true does *not* run site:site, it just says include it if you did not run site:site it says: [INFO] org.apache.maven.plugin.MojoFailureException: site did not exist in the target directory - please run site:site before creating the assembly at org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:261) -Original Message- From: Michael [mailto:[EMAIL PROTECTED] Sent: Tue 1/15/2008 3:53 PM To: Maven Users List Subject: Re: How to make assembly:assembly depend on goals? [EMAIL PROTECTED] wrote: This can be be perfectly done by using the lifecycle of maven. In short, don't site:site, but call the phase site (thus mvn site instead of mvn site:site). Also, you could bind the assembly plugin to the package phase and thus run mvn package instead of mvn assembly:assembly. Try reading this page for more informatin: http://www.sonatype.com/book/lifecycle.html Still seems like a riddle to me. I am aware about the attached mojo but I cannot say depends on, site, package but only on one of these too. I guess, I still don't understand the lifecycle system Mike -Original Message- From: Michael [mailto:[EMAIL PROTECTED] Sent: Tue 1/15/2008 3:37 PM To: users@maven.apache.org Subject: How to make assembly:assembly depend on goals? Hi, I kinda miss task dependencies like in Ant. My basic idea is provide a bin distro which easily can be done with assembly plugin. But I want assembly:assembly depend on site:site since running assembly:assembly runs package only in advance. Is this possible? Thx, Mike -- NO OOXML - Say NO To Microsoft Office broken standard http://www.noooxml.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Setting Java System property
Due to the way Maven forks builds etc, I don't think you can ever safely assume that System properties are going to be available to a specific plugin in your build. Instead, you should be passing properties into plugins directly, or writing code in your plugin to access Maven properties using the Maven API. I could be wrong here, but I have written some plugins, and I've never assumed that System properties would be around for my plugins to use. You could also try downloading the org.apache.maven.plugins.* code and grepping for System.getProperty, but I doubt you'll find any references to it. This is a good indication that you probably don't want to be doing this or you're doing something wrong. Wayne On 1/15/08, Matthew Tordoff [EMAIL PROTECTED] wrote: Hi Simon, Sorry for the confusion, but I am not trying to set a basic property, but a JVM System Property. A property which would be accessible from the Java code using System.getProperty(PropertyName); I then want that property to be available to every plugin I execute. Matt -Original Message- From: Simon Kitching [mailto:[EMAIL PROTECTED] Sent: 15 January 2008 12:39 To: Maven Users List; Matthew Tordoff Subject: RE: Setting Java System property Matthew Tordoff [EMAIL PROTECTED] schrieb: Thanks for that but I have already looked at the appropriate documentation. I have tried setting the system property in all of those locations and for some reason none of the settings are passed through. I did find a JIRA bug opened against this problem somewhere, and thus am guessing this functionality isn't yet available. Are you trying to set a global property, or one specific to just a particular plugin? You appear to be trying to do the latter by nesting your properties info inside a configuration tag. However the page I referred you to says about configuration: The configuration as DOM object. which strongly implies to me that this is only interpreted by the plugin, and you cannot assume that maven looks in here, ie the plugin alone is responsible for interpreting the contents. I could be wrong here, but don't think so.. Setting properties in a pom which are global to all stuff in the pom (and child poms) is trivial, and definitely works when *not* nested within a configuration element (as documented in the page I referred you to): project ... properties foofooval/foo /properties /project It also works in settings.xml, but you do need to be sure that the profile it is defined within is active.. Regards, Simon The content of this e-mail is confidential and may be privileged. It may be read, copied and used only by the intended recipient and may not be disclosed, copied or distributed. If you received this email in error, please contact the sender immediately by return e-mail or by telephoning +44 20 7260 2000, delete it and do not disclose its contents to any person. You should take full responsibility for checking this email for viruses. Markit reserves the right to monitor all e-mail communications through its network. Markit and its affiliated companies make no warranty as to the accuracy or completeness of any information contained in this message and hereby exclude any liability of any kind for the information contained herein. Any opinions expressed in this message are those of the author and do not necessarily reflect the opinions of Markit. For full details about Markit, its offerings and legal terms and conditions, please see Markit's website at http://www.markit.com http://www.markit.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: Disk Space Optimization with Snapshots
You rock, Rob. Thanks for following up. I'm sure this will be appreciated by other current and future users of Maven. Wayne On 1/14/08, Robert Winch [EMAIL PROTECTED] wrote: As requested I have included two postings in addition to the Archiva issue provided by Wayne. Artifactory (artifactory.sf.net) - for proxies http://www.nabble.com/forum/ViewPost.jtp?post=9574480framed=y The forum posting about the script Wayne mentioned (deletes files older than x number of days) http://www.nabble.com/forum/ViewPost.jtp?post=10654418framed=yskin=177 A direct link to the script http://lifehacker.com/software/geek-to-live/geek-to-live-hard-drive-janitor-133190.php On Jan 14, 2008 6:39 PM, Wayne Fay [EMAIL PROTECTED] wrote: I know someone posted a bash script at some point... You'll need to check the mail list archives (check Nabble.com). If you find it, reply back with the subject and date, or a direct link, so other people can find it too. ;-) Wayne On 1/14/08, Robert Winch [EMAIL PROTECTED] wrote: Thank you for your quick reply. Is there a way to do this for a local repository as well? Thanks in advance, Rob On Jan 14, 2008 4:40 PM, Wayne Fay [EMAIL PROTECTED] wrote: Archiva has support for this, see: http://jira.codehaus.org/browse/MRM-275 Wayne On 1/14/08, Robert Winch [EMAIL PROTECTED] wrote: I currently experience disk space issues because build are frequent within my company. This happens on our build boxes which use a CI Server to build and then deploy our projects to a maven repository. The build box's local repository contains a lot of old snapshot builds which we no longer need. In addition, the remote maven repository contains unneeded snapshot jars. Is there a way to make it so that we only contain the most recent snapshot in our local and remote repositories, but still ensure that users will download the most recent snapshot version? Thanks in advance, Rob - 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: Disk Space Optimization with Snapshots
Robert: We use a combination of distributionManagement snapshotRepository uniqueVersionfalse/uniqueVersion /snapshotRepository /distributionManagement and Archiva. Both have worked well for us. Barrett Barrett Nuzum Sr. Consultant [EMAIL PROTECTED] Mobile: 918-640-4414 Valtech 5080 Spectrum Drive, Ste 700W Addison, TX 75001 USA Tel: 972-789-1200 Fax: 972-789-1340 www.valtech.us From: Robert Winch [mailto:[EMAIL PROTECTED] Sent: Mon 1/14/2008 6:18 PM To: Maven Users List Subject: Re: Disk Space Optimization with Snapshots Thank you for your quick reply. Is there a way to do this for a local repository as well? Thanks in advance, Rob On Jan 14, 2008 4:40 PM, Wayne Fay [EMAIL PROTECTED] wrote: Archiva has support for this, see: http://jira.codehaus.org/browse/MRM-275 Wayne On 1/14/08, Robert Winch [EMAIL PROTECTED] wrote: I currently experience disk space issues because build are frequent within my company. This happens on our build boxes which use a CI Server to build and then deploy our projects to a maven repository. The build box's local repository contains a lot of old snapshot builds which we no longer need. In addition, the remote maven repository contains unneeded snapshot jars. Is there a way to make it so that we only contain the most recent snapshot in our local and remote repositories, but still ensure that users will download the most recent snapshot version? Thanks in advance, Rob - 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: How to make assembly:assembly depend on goals?
[EMAIL PROTECTED] wrote: Please explain then what your intended result is, maybe I can help you better then. I want to creae a bin distibution which should contain: site/ my.jar LICENSE.txt README.txt I set you the bin.xml descriptor and set includeSiteDirectory to true since we know assembly:assembly automaticalla runs package I only have to run: mvn clean assembly:assembly but this will fail because site is not present, I have to run: mvn clean site assembly:assembly I want assembly:assembly automatically call site just like it calls package -Original Message- From: Michael [mailto:[EMAIL PROTECTED] Sent: Tue 1/15/2008 4:09 PM To: Maven Users List Subject: Re: How to make assembly:assembly depend on goals? [EMAIL PROTECTED] wrote: Looking at your post again and I think I understand what you want to accomplish. You want to include inside the assembly the generated site? Take a look at the Assembly mojo [1] and especially this parameter: includeSite boolean Set to true to include the site generated by site:site goal. Default value is false. I guess that is what you want. Unfortunately, it isn't for 2 reasons: 1. is is deprecated in favor of includeSiteDirectory in the descriptor file 2. setting to true does *not* run site:site, it just says include it if you did not run site:site it says: [INFO] org.apache.maven.plugin.MojoFailureException: site did not exist in the target directory - please run site:site before creating the assembly at org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:261) -Original Message- From: Michael [mailto:[EMAIL PROTECTED] Sent: Tue 1/15/2008 3:53 PM To: Maven Users List Subject: Re: How to make assembly:assembly depend on goals? [EMAIL PROTECTED] wrote: This can be be perfectly done by using the lifecycle of maven. In short, don't site:site, but call the phase site (thus mvn site instead of mvn site:site). Also, you could bind the assembly plugin to the package phase and thus run mvn package instead of mvn assembly:assembly. Try reading this page for more informatin: http://www.sonatype.com/book/lifecycle.html Still seems like a riddle to me. I am aware about the attached mojo but I cannot say depends on, site, package but only on one of these too. I guess, I still don't understand the lifecycle system Mike -Original Message- From: Michael [mailto:[EMAIL PROTECTED] Sent: Tue 1/15/2008 3:37 PM To: users@maven.apache.org Subject: How to make assembly:assembly depend on goals? Hi, I kinda miss task dependencies like in Ant. My basic idea is provide a bin distro which easily can be done with assembly plugin. But I want assembly:assembly depend on site:site since running assembly:assembly runs package only in advance. Is this possible? Thx, Mike -- NO OOXML - Say NO To Microsoft Office broken standard http://www.noooxml.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to make assembly:assembly depend on goals?
Please explain then what your intended result is, maybe I can help you better then. With regards, Nick Stolwijk -Original Message- From: Michael [mailto:[EMAIL PROTECTED] Sent: Tue 1/15/2008 4:09 PM To: Maven Users List Subject: Re: How to make assembly:assembly depend on goals? [EMAIL PROTECTED] wrote: Looking at your post again and I think I understand what you want to accomplish. You want to include inside the assembly the generated site? Take a look at the Assembly mojo [1] and especially this parameter: includeSite boolean Set to true to include the site generated by site:site goal. Default value is false. I guess that is what you want. Unfortunately, it isn't for 2 reasons: 1. is is deprecated in favor of includeSiteDirectory in the descriptor file 2. setting to true does *not* run site:site, it just says include it if you did not run site:site it says: [INFO] org.apache.maven.plugin.MojoFailureException: site did not exist in the target directory - please run site:site before creating the assembly at org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:261) -Original Message- From: Michael [mailto:[EMAIL PROTECTED] Sent: Tue 1/15/2008 3:53 PM To: Maven Users List Subject: Re: How to make assembly:assembly depend on goals? [EMAIL PROTECTED] wrote: This can be be perfectly done by using the lifecycle of maven. In short, don't site:site, but call the phase site (thus mvn site instead of mvn site:site). Also, you could bind the assembly plugin to the package phase and thus run mvn package instead of mvn assembly:assembly. Try reading this page for more informatin: http://www.sonatype.com/book/lifecycle.html Still seems like a riddle to me. I am aware about the attached mojo but I cannot say depends on, site, package but only on one of these too. I guess, I still don't understand the lifecycle system Mike -Original Message- From: Michael [mailto:[EMAIL PROTECTED] Sent: Tue 1/15/2008 3:37 PM To: users@maven.apache.org Subject: How to make assembly:assembly depend on goals? Hi, I kinda miss task dependencies like in Ant. My basic idea is provide a bin distro which easily can be done with assembly plugin. But I want assembly:assembly depend on site:site since running assembly:assembly runs package only in advance. Is this possible? Thx, Mike -- NO OOXML - Say NO To Microsoft Office broken standard http://www.noooxml.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Setting Java System property
From: Simon Kitching [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 15, 2008 7:39 AM To: Maven Users List; Matthew Tordoff Subject: RE: Setting Java System property Setting properties in a pom which are global to all stuff in the pom (and child poms) is trivial, and definitely works when *not* nested within a configuration element (as documented in the page I referred you to): project ... properties foofooval/foo /properties /project It also works in settings.xml, but you do need to be sure that the profile it is defined within is active.. I wish this would work, from what I've tried the properties will not get passed to child modules. The only way I can get a property to be seen by all poms is to -Dparm=val or use settings.xml. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Disk Space Optimization with Snapshots
Barrett, Thanks for the response. Does your solution take care of the local repository? I have seen the uniqueVersion=false before and seem to recall (possibly mistakenly) this causing issues with developers having the most recent snapshot build. Have you experienced problems with this or was this just my imagination? Thanks! Rob On Jan 15, 2008 9:10 AM, Barrett Nuzum [EMAIL PROTECTED] wrote: Robert: We use a combination of distributionManagement snapshotRepository uniqueVersionfalse/uniqueVersion /snapshotRepository /distributionManagement and Archiva. Both have worked well for us. Barrett Barrett Nuzum Sr. Consultant [EMAIL PROTECTED] Mobile: 918-640-4414 Valtech 5080 Spectrum Drive, Ste 700W Addison, TX 75001 USA Tel: 972-789-1200 Fax: 972-789-1340 www.valtech.us From: Robert Winch [mailto:[EMAIL PROTECTED] Sent: Mon 1/14/2008 6:18 PM To: Maven Users List Subject: Re: Disk Space Optimization with Snapshots Thank you for your quick reply. Is there a way to do this for a local repository as well? Thanks in advance, Rob On Jan 14, 2008 4:40 PM, Wayne Fay [EMAIL PROTECTED] wrote: Archiva has support for this, see: http://jira.codehaus.org/browse/MRM-275 Wayne On 1/14/08, Robert Winch [EMAIL PROTECTED] wrote: I currently experience disk space issues because build are frequent within my company. This happens on our build boxes which use a CI Server to build and then deploy our projects to a maven repository. The build box's local repository contains a lot of old snapshot builds which we no longer need. In addition, the remote maven repository contains unneeded snapshot jars. Is there a way to make it so that we only contain the most recent snapshot in our local and remote repositories, but still ensure that users will download the most recent snapshot version? Thanks in advance, Rob - 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: How to make assembly:assembly depend on goals?
Ok, I'll understand what you want. Let's find a solution. :) Try it the other way around, bind the assembly:assembly goal to the post-site phase and call mvn post-site. If you don't want it to always run when calling mvn site-deploy (which is after post-site) add a profile and call mvn post-site -Passembly Hth, Nick Stolwijk -Original Message- From: Michael [mailto:[EMAIL PROTECTED] Sent: Tue 1/15/2008 4:30 PM To: Maven Users List Subject: Re: How to make assembly:assembly depend on goals? [EMAIL PROTECTED] wrote: Please explain then what your intended result is, maybe I can help you better then. I want to creae a bin distibution which should contain: site/ my.jar LICENSE.txt README.txt I set you the bin.xml descriptor and set includeSiteDirectory to true since we know assembly:assembly automaticalla runs package I only have to run: mvn clean assembly:assembly but this will fail because site is not present, I have to run: mvn clean site assembly:assembly I want assembly:assembly automatically call site just like it calls package -Original Message- From: Michael [mailto:[EMAIL PROTECTED] Sent: Tue 1/15/2008 4:09 PM To: Maven Users List Subject: Re: How to make assembly:assembly depend on goals? [EMAIL PROTECTED] wrote: Looking at your post again and I think I understand what you want to accomplish. You want to include inside the assembly the generated site? Take a look at the Assembly mojo [1] and especially this parameter: includeSite boolean Set to true to include the site generated by site:site goal. Default value is false. I guess that is what you want. Unfortunately, it isn't for 2 reasons: 1. is is deprecated in favor of includeSiteDirectory in the descriptor file 2. setting to true does *not* run site:site, it just says include it if you did not run site:site it says: [INFO] org.apache.maven.plugin.MojoFailureException: site did not exist in the target directory - please run site:site before creating the assembly at org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:261) -Original Message- From: Michael [mailto:[EMAIL PROTECTED] Sent: Tue 1/15/2008 3:53 PM To: Maven Users List Subject: Re: How to make assembly:assembly depend on goals? [EMAIL PROTECTED] wrote: This can be be perfectly done by using the lifecycle of maven. In short, don't site:site, but call the phase site (thus mvn site instead of mvn site:site). Also, you could bind the assembly plugin to the package phase and thus run mvn package instead of mvn assembly:assembly. Try reading this page for more informatin: http://www.sonatype.com/book/lifecycle.html Still seems like a riddle to me. I am aware about the attached mojo but I cannot say depends on, site, package but only on one of these too. I guess, I still don't understand the lifecycle system Mike -Original Message- From: Michael [mailto:[EMAIL PROTECTED] Sent: Tue 1/15/2008 3:37 PM To: users@maven.apache.org Subject: How to make assembly:assembly depend on goals? Hi, I kinda miss task dependencies like in Ant. My basic idea is provide a bin distro which easily can be done with assembly plugin. But I want assembly:assembly depend on site:site since running assembly:assembly runs package only in advance. Is this possible? Thx, Mike -- NO OOXML - Say NO To Microsoft Office broken standard http://www.noooxml.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Solving generic dependencies
I would like to use Maven in order to create a generic dependency resolver. My intention is creating a maven repository that is capable of solving dependency questions related to internal logical resources included into the artifacts. Java packages is an example of the type of resources I am thinking of, but the system would be able to include any kind of resource, such as a Web Service, an OSGi service, a business process or whatever else that might be meaningful. Including these information would turn a maven artifact repository into something else, a generic asset repository. That would be a tool that could be used not only for build management, but also for aiding in change management, runtime deployment and many other things. I don't know if this has already been done somewhere else, or if Maven is not the best choice for creating something like this. Anyway, I would appreciate your advice. Thanks,
Re: How to make assembly:assembly depend on goals?
[EMAIL PROTECTED] wrote: Ok, I'll understand what you want. Let's find a solution. :) Try it the other way around, bind the assembly:assembly goal to the post-site phase and call mvn post-site. If you don't want it to always run when calling mvn site-deploy (which is after post-site) add a profile and call mvn post-site -Passembly This is exactly what I have expected. :-( It can't be done like in Ant. Actually I don't want to bind assembly to site. But thanks pointing me into some direction. I will write to the plugins author adding site and as pre goal if site should be eincluded thx -Original Message- From: Michael [mailto:[EMAIL PROTECTED] Sent: Tue 1/15/2008 4:30 PM To: Maven Users List Subject: Re: How to make assembly:assembly depend on goals? [EMAIL PROTECTED] wrote: Please explain then what your intended result is, maybe I can help you better then. I want to creae a bin distibution which should contain: site/ my.jar LICENSE.txt README.txt I set you the bin.xml descriptor and set includeSiteDirectory to true since we know assembly:assembly automaticalla runs package I only have to run: mvn clean assembly:assembly but this will fail because site is not present, I have to run: mvn clean site assembly:assembly I want assembly:assembly automatically call site just like it calls package -Original Message- From: Michael [mailto:[EMAIL PROTECTED] Sent: Tue 1/15/2008 4:09 PM To: Maven Users List Subject: Re: How to make assembly:assembly depend on goals? [EMAIL PROTECTED] wrote: Looking at your post again and I think I understand what you want to accomplish. You want to include inside the assembly the generated site? Take a look at the Assembly mojo [1] and especially this parameter: includeSite boolean Set to true to include the site generated by site:site goal. Default value is false. I guess that is what you want. Unfortunately, it isn't for 2 reasons: 1. is is deprecated in favor of includeSiteDirectory in the descriptor file 2. setting to true does *not* run site:site, it just says include it if you did not run site:site it says: [INFO] org.apache.maven.plugin.MojoFailureException: site did not exist in the target directory - please run site:site before creating the assembly at org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:261) -Original Message- From: Michael [mailto:[EMAIL PROTECTED] Sent: Tue 1/15/2008 3:53 PM To: Maven Users List Subject: Re: How to make assembly:assembly depend on goals? [EMAIL PROTECTED] wrote: This can be be perfectly done by using the lifecycle of maven. In short, don't site:site, but call the phase site (thus mvn site instead of mvn site:site). Also, you could bind the assembly plugin to the package phase and thus run mvn package instead of mvn assembly:assembly. Try reading this page for more informatin: http://www.sonatype.com/book/lifecycle.html Still seems like a riddle to me. I am aware about the attached mojo but I cannot say depends on, site, package but only on one of these too. I guess, I still don't understand the lifecycle system Mike -Original Message- From: Michael [mailto:[EMAIL PROTECTED] Sent: Tue 1/15/2008 3:37 PM To: users@maven.apache.org Subject: How to make assembly:assembly depend on goals? Hi, I kinda miss task dependencies like in Ant. My basic idea is provide a bin distro which easily can be done with assembly plugin. But I want assembly:assembly depend on site:site since running assembly:assembly runs package only in advance. Is this possible? Thx, Mike -- NO OOXML - Say NO To Microsoft Office broken standard http://www.noooxml.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Setting Java System property
That's pretty much the same as what I found. What did you do in settings.xml? -Original Message- From: Labanca, Rick [mailto:[EMAIL PROTECTED] Sent: 15 January 2008 15:32 To: Maven Users List Subject: RE: Setting Java System property From: Simon Kitching [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 15, 2008 7:39 AM To: Maven Users List; Matthew Tordoff Subject: RE: Setting Java System property Setting properties in a pom which are global to all stuff in the pom (and child poms) is trivial, and definitely works when *not* nested within a configuration element (as documented in the page I referred you to): project ... properties foofooval/foo /properties /project It also works in settings.xml, but you do need to be sure that the profile it is defined within is active.. I wish this would work, from what I've tried the properties will not get passed to child modules. The only way I can get a property to be seen by all poms is to -Dparm=val or use settings.xml. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] The content of this e-mail is confidential and may be privileged. It may be read, copied and used only by the intended recipient and may not be disclosed, copied or distributed. If you received this email in error, please contact the sender immediately by return e-mail or by telephoning +44 20 7260 2000, delete it and do not disclose its contents to any person. You should take full responsibility for checking this email for viruses. Markit reserves the right to monitor all e-mail communications through its network. Markit and its affiliated companies make no warranty as to the accuracy or completeness of any information contained in this message and hereby exclude any liability of any kind for the information contained herein. Any opinions expressed in this message are those of the author and do not necessarily reflect the opinions of Markit. For full details about Markit, its offerings and legal terms and conditions, please see Markit's website at http://www.markit.com http://www.markit.com/ . - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to make assembly:assembly depend on goals?
Yes, the reason is that It would call assembly even if I want just run site for upload to my space or just for my development verification if my site is really fine. It would be just some unnecessary overhead. To avoid this, use a profile for now. Hth, Nick Stolwijk
Deployed artifcat names
Hi, When I deploy my artifacts, the file names change from xxx-ver-SNAPSHOT.jar to xxx-ver-date time-n.jar. I just want to retain the latest snapshot versions with the usual SNAPSHOT suffix. Is that possible or ok? Or is it just better to let the deployment put on a data and time - is this what allows any SNAPSHOT dependencies in Maven to get the latest version? I want to include snapshots in ant builds which will be hard coded to specific snapshot versions. TIA, John Eurobase International Limited and its subsidiaries (Eurobase) are unable to exercise control over the content of information in E-Mails. Any views and opinions expressed may be personal to the sender and are not necessarily those of Eurobase. Eurobase will not enter into any contractual obligations in respect of any part of its business in any E-mail. Privileged / confidential information may be contained in this message and /or any attachments. This E-mail is intended for the use of the addressee(s) only and may contain confidential information. If you are not the / an intended recipient, you are hereby notified that any use or dissemination of this communication is strictly prohibited. If you receive this transmission in error, please notify us immediately, and then delete this E-mail. Neither the sender nor Eurobase accepts any liability whatsoever for any defects of any kind either in or arising from this E-mail transmission. E-Mail transmission cannot be guaranteed to be secure or error-free, as messages can be intercepted, lost, corrupted, destroyed, contain viruses, or arrive late or incomplete. Eurobase does not accept any responsibility for viruses and it is your responsibility to scan any attachments. Eurobase Systems Limited is the main trading company in the Eurobase International Group; registered in England and Wales as company number 02251162; registered address: Essex House, 2 County Place, Chelmsford, Essex CM2 0RE, UK. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to make assembly:assembly depend on goals?
I guess the author is already aware of it: http://jira.codehaus.org/browse/MASSEMBLY-22 And have been aware of it for a long time (Hence it is an early issue number), but the problem seems with maven can not optionally execute other phases. Hth, Nick Stolwijk ps. If I may ask, what are your reasons to not bind it to the post-site phase? -Original Message- From: Michael [mailto:[EMAIL PROTECTED] Sent: Tue 1/15/2008 4:51 PM To: Maven Users List Subject: Re: How to make assembly:assembly depend on goals? [EMAIL PROTECTED] wrote: Ok, I'll understand what you want. Let's find a solution. :) Try it the other way around, bind the assembly:assembly goal to the post-site phase and call mvn post-site. If you don't want it to always run when calling mvn site-deploy (which is after post-site) add a profile and call mvn post-site -Passembly This is exactly what I have expected. :-( It can't be done like in Ant. Actually I don't want to bind assembly to site. But thanks pointing me into some direction. I will write to the plugins author adding site and as pre goal if site should be eincluded thx -Original Message- From: Michael [mailto:[EMAIL PROTECTED] Sent: Tue 1/15/2008 4:30 PM To: Maven Users List Subject: Re: How to make assembly:assembly depend on goals? [EMAIL PROTECTED] wrote: Please explain then what your intended result is, maybe I can help you better then. I want to creae a bin distibution which should contain: site/ my.jar LICENSE.txt README.txt I set you the bin.xml descriptor and set includeSiteDirectory to true since we know assembly:assembly automaticalla runs package I only have to run: mvn clean assembly:assembly but this will fail because site is not present, I have to run: mvn clean site assembly:assembly I want assembly:assembly automatically call site just like it calls package -Original Message- From: Michael [mailto:[EMAIL PROTECTED] Sent: Tue 1/15/2008 4:09 PM To: Maven Users List Subject: Re: How to make assembly:assembly depend on goals? [EMAIL PROTECTED] wrote: Looking at your post again and I think I understand what you want to accomplish. You want to include inside the assembly the generated site? Take a look at the Assembly mojo [1] and especially this parameter: includeSite boolean Set to true to include the site generated by site:site goal. Default value is false. I guess that is what you want. Unfortunately, it isn't for 2 reasons: 1. is is deprecated in favor of includeSiteDirectory in the descriptor file 2. setting to true does *not* run site:site, it just says include it if you did not run site:site it says: [INFO] org.apache.maven.plugin.MojoFailureException: site did not exist in the target directory - please run site:site before creating the assembly at org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:261) -Original Message- From: Michael [mailto:[EMAIL PROTECTED] Sent: Tue 1/15/2008 3:53 PM To: Maven Users List Subject: Re: How to make assembly:assembly depend on goals? [EMAIL PROTECTED] wrote: This can be be perfectly done by using the lifecycle of maven. In short, don't site:site, but call the phase site (thus mvn site instead of mvn site:site). Also, you could bind the assembly plugin to the package phase and thus run mvn package instead of mvn assembly:assembly. Try reading this page for more informatin: http://www.sonatype.com/book/lifecycle.html Still seems like a riddle to me. I am aware about the attached mojo but I cannot say depends on, site, package but only on one of these too. I guess, I still don't understand the lifecycle system Mike -Original Message- From: Michael [mailto:[EMAIL PROTECTED] Sent: Tue 1/15/2008 3:37 PM To: users@maven.apache.org Subject: How to make assembly:assembly depend on goals? Hi, I kinda miss task dependencies like in Ant. My basic idea is provide a bin distro which easily can be done with assembly plugin. But I want assembly:assembly depend on site:site since running assembly:assembly runs package only in advance. Is this possible? Thx, Mike -- NO OOXML - Say NO To Microsoft Office broken standard http://www.noooxml.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to make assembly:assembly depend on goals?
[EMAIL PROTECTED] wrote: Yes, the reason is that It would call assembly even if I want just run site for upload to my space or just for my development verification if my site is really fine. It would be just some unnecessary overhead. To avoid this, use a profile for now. I guess I have to :-( Did not dig into profiles yet Thx anyway! -- NO OOXML - Say NO To Microsoft Office broken standard http://www.noooxml.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: How to make assembly:assembly depend on goals?
[EMAIL PROTECTED] wrote: I guess the author is already aware of it: http://jira.codehaus.org/browse/MASSEMBLY-22 found it after I filed mine. And have been aware of it for a long time (Hence it is an early issue number), but the problem seems with maven can not optionally execute other phases. Hth, Nick Stolwijk ps. If I may ask, what are your reasons to not bind it to the post-site phase? Yes, the reason is that It would call assembly even if I want just run site for upload to my space or just for my development verification if my site is really fine. It would be just some unnecessary overhead. -Original Message- From: Michael [mailto:[EMAIL PROTECTED] Sent: Tue 1/15/2008 4:51 PM To: Maven Users List Subject: Re: How to make assembly:assembly depend on goals? [EMAIL PROTECTED] wrote: Ok, I'll understand what you want. Let's find a solution. :) Try it the other way around, bind the assembly:assembly goal to the post-site phase and call mvn post-site. If you don't want it to always run when calling mvn site-deploy (which is after post-site) add a profile and call mvn post-site -Passembly This is exactly what I have expected. :-( It can't be done like in Ant. Actually I don't want to bind assembly to site. But thanks pointing me into some direction. I will write to the plugins author adding site and as pre goal if site should be eincluded thx -Original Message- From: Michael [mailto:[EMAIL PROTECTED] Sent: Tue 1/15/2008 4:30 PM To: Maven Users List Subject: Re: How to make assembly:assembly depend on goals? [EMAIL PROTECTED] wrote: Please explain then what your intended result is, maybe I can help you better then. I want to creae a bin distibution which should contain: site/ my.jar LICENSE.txt README.txt I set you the bin.xml descriptor and set includeSiteDirectory to true since we know assembly:assembly automaticalla runs package I only have to run: mvn clean assembly:assembly but this will fail because site is not present, I have to run: mvn clean site assembly:assembly I want assembly:assembly automatically call site just like it calls package -Original Message- From: Michael [mailto:[EMAIL PROTECTED] Sent: Tue 1/15/2008 4:09 PM To: Maven Users List Subject: Re: How to make assembly:assembly depend on goals? [EMAIL PROTECTED] wrote: Looking at your post again and I think I understand what you want to accomplish. You want to include inside the assembly the generated site? Take a look at the Assembly mojo [1] and especially this parameter: includeSite boolean Set to true to include the site generated by site:site goal. Default value is false. I guess that is what you want. Unfortunately, it isn't for 2 reasons: 1. is is deprecated in favor of includeSiteDirectory in the descriptor file 2. setting to true does *not* run site:site, it just says include it if you did not run site:site it says: [INFO] org.apache.maven.plugin.MojoFailureException: site did not exist in the target directory - please run site:site before creating the assembly at org.apache.maven.plugin.assembly.mojos.AbstractAssemblyMojo.execute(AbstractAssemblyMojo.java:261) -Original Message- From: Michael [mailto:[EMAIL PROTECTED] Sent: Tue 1/15/2008 3:53 PM To: Maven Users List Subject: Re: How to make assembly:assembly depend on goals? [EMAIL PROTECTED] wrote: This can be be perfectly done by using the lifecycle of maven. In short, don't site:site, but call the phase site (thus mvn site instead of mvn site:site). Also, you could bind the assembly plugin to the package phase and thus run mvn package instead of mvn assembly:assembly. Try reading this page for more informatin: http://www.sonatype.com/book/lifecycle.html Still seems like a riddle to me. I am aware about the attached mojo but I cannot say depends on, site, package but only on one of these too. I guess, I still don't understand the lifecycle system Mike -Original Message- From: Michael [mailto:[EMAIL PROTECTED] Sent: Tue 1/15/2008 3:37 PM To: users@maven.apache.org Subject: How to make assembly:assembly depend on goals? Hi, I kinda miss task dependencies like in Ant. My basic idea is provide a bin distro which easily can be done with assembly plugin. But I want assembly:assembly depend on site:site since running assembly:assembly runs package only in advance. Is this possible? Thx, Mike -- NO OOXML - Say NO To Microsoft Office broken standard http://www.noooxml.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Maven 2.1 release
On Sun, January 13, 2008 1:31 am, Brian E. Fox wrote: I think John is wrapping up a few issues before an alpha goes out. Are there any showstoppers outstanding that prevent a release? Regards, Graham -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Deployed artifcat names
use distributionManagement snapshotRepository url.../url uniqueVersionfalse/uniqueVersion /snapshotRepository /distributionManagement This will deploy only SNAPSHOT jars, with no history (timsetamp) versions. Nico. 2008/1/15, John Coleman [EMAIL PROTECTED]: Hi, When I deploy my artifacts, the file names change from xxx-ver-SNAPSHOT.jar to xxx-ver-date time-n.jar. I just want to retain the latest snapshot versions with the usual SNAPSHOT suffix. Is that possible or ok? Or is it just better to let the deployment put on a data and time - is this what allows any SNAPSHOT dependencies in Maven to get the latest version? I want to include snapshots in ant builds which will be hard coded to specific snapshot versions. TIA, John Eurobase International Limited and its subsidiaries (Eurobase) are unable to exercise control over the content of information in E-Mails. Any views and opinions expressed may be personal to the sender and are not necessarily those of Eurobase. Eurobase will not enter into any contractual obligations in respect of any part of its business in any E-mail. Privileged / confidential information may be contained in this message and /or any attachments. This E-mail is intended for the use of the addressee(s) only and may contain confidential information. If you are not the / an intended recipient, you are hereby notified that any use or dissemination of this communication is strictly prohibited. If you receive this transmission in error, please notify us immediately, and then delete this E-mail. Neither the sender nor Eurobase accepts any liability whatsoever for any defects of any kind either in or arising from this E-mail transmission. E-Mail transmission cannot be guaranteed to be secure or error-free, as messages can be intercepted, lost, corrupted, destroyed, contain viruses, or arrive late or incomplete. Eurobase does not accept any responsibility for viruses and it is your responsibility to scan any attachments. Eurobase Systems Limited is the main trading company in the Eurobase International Group; registered in England and Wales as company number 02251162; registered address: Essex House, 2 County Place, Chelmsford, Essex CM2 0RE, UK. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
RE: Setting Java System property
I made a settings.xml in my project's root area, my goal was to have a variable for all version tags because I don't want to go changing all those and risking them being out of sync. So settings.xml looks like the following, and I do mvn -s settings.xml so it uses this instead of any user one I have locally: settings xmlns=http://maven.apache.org/POM/4.0.0; xmlns:xsi=http://www.w3.org/2001/XMLSchema-instance; xsi:schemaLocation=http://maven.apache.org/POM/4.0.0 http://maven.apache.org/xsd/settings-1.0.0.xsd; profiles profile iddefault/id activation activeByDefault / /activation properties globalVersion1/globalVersion /properties /profile /profiles activeProfiles activeProfiledefault/activeProfile /activeProfiles /settings -Original Message- From: Matthew Tordoff [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 15, 2008 10:41 AM To: Maven Users List Subject: RE: Setting Java System property That's pretty much the same as what I found. What did you do in settings.xml? -Original Message- From: Labanca, Rick [mailto:[EMAIL PROTECTED] Sent: 15 January 2008 15:32 To: Maven Users List Subject: RE: Setting Java System property From: Simon Kitching [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 15, 2008 7:39 AM To: Maven Users List; Matthew Tordoff Subject: RE: Setting Java System property Setting properties in a pom which are global to all stuff in the pom (and child poms) is trivial, and definitely works when *not* nested within a configuration element (as documented in the page I referred you to): project ... properties foofooval/foo /properties /project It also works in settings.xml, but you do need to be sure that the profile it is defined within is active.. I wish this would work, from what I've tried the properties will not get passed to child modules. The only way I can get a property to be seen by all poms is to -Dparm=val or use settings.xml. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] The content of this e-mail is confidential and may be privileged. It may be read, copied and used only by the intended recipient and may not be disclosed, copied or distributed. If you received this email in error, please contact the sender immediately by return e-mail or by telephoning +44 20 7260 2000, delete it and do not disclose its contents to any person. You should take full responsibility for checking this email for viruses. Markit reserves the right to monitor all e-mail communications through its network. Markit and its affiliated companies make no warranty as to the accuracy or completeness of any information contained in this message and hereby exclude any liability of any kind for the information contained herein. Any opinions expressed in this message are those of the author and do not necessarily reflect the opinions of Markit. For full details about Markit, its offerings and legal terms and conditions, please see Markit's website at http://www.markit.com http://www.markit.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]
Ant exception
hello, i read this tutorial to use Ant http://maven.apache.org/ant-tasks.html the exception is on this build line: [...] artifact:pom file=pom.xml id=my.maven.project/ [...] exception... Caused by: The following error occurred while executing this line: java.lang.NoSuchMethodError: org.apache.maven.settings.Settings.setRuntimeInfo(Lorg/apache/maven/settings/RuntimeInfo;)V at org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:539) at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:384) at org.apache.tools.ant.UnknownElement.execute(UnknownElement.java:275) .. is anybody has any clue?? supareno - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
org.codehaus.mojo:jaxws-maven-plugin Random order of generated sourceCode ?
Hi,
I´m using the jaxws-maven-plugin.
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdjaxws-maven-plugin/artifactId
executions
execution
idserver-bindings/id
goals
goalwsimport/goal
/goals
/execution
/executions
configuration
bindingDirectory${basedir}/src/main/config/bindingDirectory
bindingFiles
bindingFilejaxws-ts-server-bindings.xml/bindingFile
/bindingFiles
destDir${project.build.directory}/classes/destDir
keeptrue/keep
staleFile${project.build.directory}/staleFlag/staleFile
wsdlDirectory${basedir}/src/main/wsdl//wsdlDirectory
wsdlFiles
wsdlFileTelematikTransport.wsdl/wsdlFile
/wsdlFiles
wsdlLocation/wsdlLocation
/configuration
/plugin
In the generated sourcecode, the method order changes, each time I execute
the build.
The source is correct, but the random behaviour makes it difficult to
compare jars from different builds.
Has anyone an idea of the base problem? I guess it´s not in the plugin,
but in the underlaying stuff (XJC, JAXB .)
Thanx,
Torsten
Re: mojo cookbook; resolving transitively
On Jan 15, 2008 3:15 PM, Nigel Magnay [EMAIL PROTECTED] wrote: The Mojo Developer Cookbook (http://docs.codehaus.org/display/MAVENUSER/Mojo+Developer+Cookbook) is great. In it, there's a section on Resolving Transitively. This works great - however, the artifact set that is resolved is based on Maven's idea of which graph edges ought to be considered for resolution. For example, if I have a WAR file, then any declared dependencies that are JARs (and POM I think) are included, and those artifacts have their dependencies added to the list (and so on, recursively). The end result resolves to a single version for each JAR artifact. However - if the WAR file has a WAR dependency, then it will not be considered, and any JAR files in there won't be included in the set that the version is resolved in. This is not what I have from my experience. If a WAR POM has a dependency of type war, then then content of this dependency will be copied verbatim to the target folder. Jeff This is the behaviour that I want, where I have a WAR of WARs, and I want to calculate the resolved set of dependencies. a) How can I interject my own requirements for dependency traversal? b) Is / how is this changed in 2.1 - all the methods on ArtifactResolver have been condensed down into 1.. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- La mélancolie c'est communiste Tout le monde y a droit de temps en temps La mélancolie n'est pas capitaliste C'est même gratuit pour les perdants La mélancolie c'est pacifiste On ne lui rentre jamais dedans La mélancolie oh tu sais ça existe Elle se prend même avec des gants La mélancolie c'est pour les syndicalistes Il faut juste sa carte de permanent Miossec (2006) http://www.jeffmaury.com http://riadiscuss.jeffmaury.com
Re: Resources from classpath in JAR
Heinrich Nirschl wrote: Put them into src/main/resources. I want them to be in same folder that classes are. -- View this message in context: http://www.nabble.com/Resources-from-classpath-in-JAR-tp14814993s177p14844214.html 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: Sources in JAR
Michael McCallum-3 wrote: why would you want to? I nead them in JAR for GWT compiler. -- View this message in context: http://www.nabble.com/Sources-in-JAR-tp14814994s177p14844218.html 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: Resources from classpath in JAR
On Jan 15, 2008 7:31 PM, dddzzz [EMAIL PROTECTED] wrote: Heinrich Nirschl wrote: Put them into src/main/resources. I want them to be in same folder that classes are. Which folder do you mean, the one with the .class files or with the .java files? The final jar will have the .class files and the resources side by side. Maven uses certain conventions about structuring the source of a project. If you follow them, there is little to configure. If you decide not to follow the conventions, more configuration in the POM is necessary. It is usually a good idea to use the conventions because it is much easier for the developers to join a new project. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
assembly plugin - dependency jars
I need to include all internal and external jars that my submodules depend on. The code below is what use in my descriptor. This however does not include and of the dependency jars included in the depenedencyManagement section of my parent pom file. Does anyone know how to include these dependency jars? dependencySets dependencySet outputDirectory/lib/outputDirectory unpackfalse/unpack scoperuntime/scope /dependencySet /dependencySets -- View this message in context: http://www.nabble.com/assembly-plugin---dependency-jars-tp14844941s177p14844941.html 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: [c1.1] derby issue with .lck files not being cleaned up
Trust me, I do NOT want to use Derby, but there is an Oracle bug: http://jira.codehaus.org/browse/CONTINUUM-1622 Thus I am forced to use Derby for now until that is fixed. So, any help to get this fixed on Derby until the above bug is fixed would be great On Jan 15, 2008 12:16 AM, Emmanuel Venisse [EMAIL PROTECTED] wrote: Do you use an embedded Derby db? It would be better to use a standalone db. Emmanuel On Jan 15, 2008 12:41 AM, Mick Knutson [EMAIL PROTECTED] wrote: I am running tomcat 5.5.25 with continuum-1.1.war and a Derby DB. Now I am also running archiva 1.0 pointing to my Oracle DB. I am not using Oracle for both as there seems to still be a defect with continuum on Oracle 10g. But, Every time run shutdown.sh to stop tomcat, then try to restart running startup.sh, the following files where not cleaned up: /home/dapadmin/apache-tomcat-5.5.25/data/continuum/database/db.lck /home/dapadmin/apache-tomcat-5.5.25/data/continuum/database/dbex.lck So I get an error that there is already a lock on the current database. I can manually delete the locks, and restart and everything works fine. NOTE: When this issue occurs, Archiva still functions as it points to Oracle, and does not seem to have a tomcat issue. -- 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 --- -- 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 ---
Eclipse plugin and project references
Hello, my question is about whether it is possible to let the Maven Eclipse plugin create the .classpath file in a way that it will directly reference dependency projects instead of referencing the JAR artifact from the local repository. The following example .classpath file for a project named foo illustrates this: ?xml version=1.0 encoding=UTF-8? classpath classpathentry kind=src path=src/main/java/ classpathentry kind=src output=target/test-classes path=src/test/java/ classpathentry kind=con path=org.eclipse.jdt.launching.JRE_CONTAINER/ classpathentry combineaccessrules=false kind=src path=/common/ classpathentry combineaccessrules=false kind=src path=/system/ classpathentry combineaccessrules=false kind=src path=/api/ classpathentry kind=output path=target/classes/ /classpath The version above has three direct references to projects common, system, and api which are all sibling projects, i.e., are located in the same folder than project foo. Regarding Maven all four projects are modules of a parent project. When I now start mvn eclipse:eclipse in project foo it will create a .classpath file that looks like this: ?xml version=1.0 encoding=UTF-8? classpath classpathentry kind=src path=src/main/java/ classpathentry kind=src path=src/test/java output=target/test-classes/ classpathentry kind=output path=target/classes/ classpathentry kind=con path=org.eclipse.jdt.launching.JRE_CONTAINER/ classpathentry kind=var path=M2_REPO/org/blahh/common/1.0/common-1.0.jar/ classpathentry kind=var path=M2_REPO/org/blahh/system/2.0/system-2.0.jar/ classpathentry kind=var path=M2_REPO/org/blahh/api/1.2/api-1.2.jar/ /classpath The three projects are now referenced by the JAR artifact from the repository. This is not optimal for me since changes to the code in one of the three projects are not instantly visible to project foo (provided that Eclipse' auto build is turned on); only after a Maven install rebuild. Is there any option that I can use to force the Eclipse plugin to reference dependency projects directly? If it doesn't exist yet, then take this as a feature request. Thanks, Thorsten -- View this message in context: http://www.nabble.com/Eclipse-plugin-and-project-references-tp14844945s177p14844945.html 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: [c1.1] derby issue with .lck files not being cleaned up
On Jan 15, 2008 12:13 PM, Mick Knutson [EMAIL PROTECTED] wrote: Trust me, I do NOT want to use Derby, but there is an Oracle bug: http://jira.codehaus.org/browse/CONTINUUM-1622 Thus I am forced to use Derby for now until that is fixed. So, any help to get this fixed on Derby until the above bug is fixed would be great You can run Derby in standalone mode as Derby Network Server. I think there are some instructions on either the Archiva or Continuum wiki. If it's Archiva, the instructions will be very similar for Continuum. -- Wendy
Re: [c1.1] derby issue with .lck files not being cleaned up
I have been running derby almost file. But when I bounce Tomcat, the db.lckfiles are not removed, thus giving me an error when I re-start Tomcat as the DB is already in use, which it is not. It is only because the lck files are still present. When I delete those 2 files, then re-start tomcat, everything is fine. On Jan 15, 2008 11:22 AM, Wendy Smoak [EMAIL PROTECTED] wrote: On Jan 15, 2008 12:13 PM, Mick Knutson [EMAIL PROTECTED] wrote: Trust me, I do NOT want to use Derby, but there is an Oracle bug: http://jira.codehaus.org/browse/CONTINUUM-1622 Thus I am forced to use Derby for now until that is fixed. So, any help to get this fixed on Derby until the above bug is fixed would be great You can run Derby in standalone mode as Derby Network Server. I think there are some instructions on either the Archiva or Continuum wiki. If it's Archiva, the instructions will be very similar for Continuum. -- Wendy -- 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: Eclipse plugin and project references
On Jan 15, 2008 8:14 PM, TM [EMAIL PROTECTED] wrote: Hello, my question is about whether it is possible to let the Maven Eclipse plugin create the .classpath file in a way that it will directly reference dependency projects instead of referencing the JAR artifact from the local repository. The following example .classpath file for a project named foo Yes, when mvn eclipse:eclipse is run for a multi module project, the dependencies between the modules will be project dependencies. If you have some independent projects, you can come up with an artificial top level pom that has the projects as modules and start mvn eclipse:eclipse from there. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[archiva 1.0] trying to eliminate external REPO lookups...
I was hoping that my setting up my archiva as a mirror, each developer would not have to go to maven, and codehaus each time they build, but it seems that we are still going out each time: Number of imports: 0 - WAGON_VERSION: 1.0-beta-2 [INFO] [INFO] Building Utilities: Common: 837-bindings [INFO]task-segment: [clean, deploy] [INFO] [DEBUG] Skipping disabled repository dap.snapshots [DEBUG] maven-clean-plugin: resolved to version 2.2 from repository central [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins::10for project: null:maven-clean-plugin:maven-plugin: 2.2 from the repository. [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::7 for project: org.apache.maven.plugins:maven-plugins:pom:10 from the repository. [DEBUG] Retrieving parent-POM: org.apache:apache::4 for project: org.apache.maven:maven-parent:pom:7 from the repository. [DEBUG] Retrieving parent-POM: org.codehaus.mojo:mojo::16 for project: org.codehaus.mojo:buildnumber-maven-plugin:maven-plugin:1.0-beta-1 from the rep ository. [DEBUG] Adding managed dependencies for org.codehaus.mojo:buildnumber-maven-plugin [DEBUG] org.apache.maven:maven-plugin-api:jar:2.0 [DEBUG] junit:junit:jar:3.8.1:test [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugin-parent::2.0-beta-1 for project: null:maven-compiler-plugin:maven-plugin:2.0-beta- 1 from the repository. [DEBUG] Adding managed dependencies for unknown:maven-compiler-plugin [DEBUG] org.apache.maven:maven-project:jar:2.0-beta-1 [DEBUG] plexus:plexus-container-default:jar:1.0-alpha-6 [DEBUG] plexus:plexus-utils:jar:1.0.2 [DEBUG] Skipping disabled repository dap.snapshots [DEBUG] maven-eclipse-plugin: resolved to version 2.4 from repository central [DEBUG] Retrieving parent-POM: org.apache.maven.plugins:maven-plugins::8 for project: org.apache.maven.plugins:maven-eclipse-plugin:maven-plugin:2.4 f rom the repository. [DEBUG] Retrieving parent-POM: org.apache.maven:maven-parent::5 for project: org.apache.maven.plugins:maven-plugins:pom:8 from the repository. [DEBUG] Skipping disabled repository dap.snapshots [DEBUG] maven-ejb-plugin: resolved to version 2.1 from repository central [DEBUG] Skipping disabled repository central [DEBUG] Skipping disabled repository central [DEBUG] dashboard-maven-plugin: resolved to version 1.0-20070907.172709-15from repository dap.snapshots [DEBUG] Retrieving parent-POM: org.codehaus.mojo:mojo-sandbox::3-SNAPSHOTfor project: org.codehaus.mojo:dashboard-maven-plugin:maven-plugin:1.0-SNAPS HOT from the repository. *[INFO] snapshot org.codehaus.mojo:mojo-sandbox:3-SNAPSHOT: checking for updates from Codehaus Snapshots [INFO] snapshot org.codehaus.mojo:mojo-sandbox:3-SNAPSHOT: checking for updates from dap.internal [INFO] snapshot org.codehaus.mojo:mojo-sandbox:3-SNAPSHOT: checking for updates from dap.snapshots* Dap.internal snapshots are our REPO's. -- 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: [archiva 1] issue with repository location on disk.
If you want it to resolve the appserver.base property, you need to set it.
This wiki entry explains
http://docs.codehaus.org/display/MAVENUSER/Archiva+on+Tomcat
Wendy Smoak-3 wrote:
On Jan 14, 2008 4:31 PM, Mick Knutson [EMAIL PROTECTED] wrote:
In my repository setup page I have this declaration:
Identifier internal Name Archiva Managed Internal Repository Directory
${
appserver.base}/data/repositories/internal
I was assuming that ${appserver.base} would get translated on the fly,
but
instead, my repository is located at:
/home/dapadmin/apache-tomcat-5.5.25/bin/*${appserver.base}*
/data/repositories/internal/
when I would assume that it should be at:
*/home/dapadmin/apache-tomcat-5.5.25/bin/*data/repositories/internal/
${appserver.base} and ${appserver.home} are Plexus-related properties.
You seem to be running the Archiva war in Tomcat, so I would suggest
configuring it with the full path to the location you want to use.
(Somewhere outside the Tomcat installation would be better...)
--
Wendy
--
View this message in context:
http://www.nabble.com/-archiva-1--issue-with-repository-location-on-disk.-tp14819846p14845576.html
Sent from the archiva-users mailing list archive at Nabble.com.
Re: assembly plugin - dependency jars
You will need to list those jars in your modules' pom.xml files as well, in the dependencies section. DepMgmt is really simply a place to manage things. It does not imply actual dependencies on anything. You will need to explicitly declare your dependencies in the various modules, and then assembly should include them automatically. Wayne On 1/15/08, tadamski [EMAIL PROTECTED] wrote: I need to include all internal and external jars that my submodules depend on. The code below is what use in my descriptor. This however does not include and of the dependency jars included in the depenedencyManagement section of my parent pom file. Does anyone know how to include these dependency jars? dependencySets dependencySet outputDirectory/lib/outputDirectory unpackfalse/unpack scoperuntime/scope /dependencySet /dependencySets -- View this message in context: http://www.nabble.com/assembly-plugin---dependency-jars-tp14844941s177p14844941.html 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: Eclipse plugin and project references
the dev version of the m2eclipse plugin will automatically resolve project references when the depedency resolves to a snapshot... you can run mvn eclipse:m2eclipse to generate the project files for the m2eclipse plugin update site... http://m2eclipse.codehaus.org/update-dev/ On Wed, 16 Jan 2008 08:14:29 TM wrote: Hello, my question is about whether it is possible to let the Maven Eclipse plugin create the .classpath file in a way that it will directly reference dependency projects instead of referencing the JAR artifact from the local repository. The following example .classpath file for a project named foo illustrates this: ?xml version=1.0 encoding=UTF-8? classpath classpathentry kind=src path=src/main/java/ classpathentry kind=src output=target/test-classes path=src/test/java/ classpathentry kind=con path=org.eclipse.jdt.launching.JRE_CONTAINER/ classpathentry combineaccessrules=false kind=src path=/common/ classpathentry combineaccessrules=false kind=src path=/system/ classpathentry combineaccessrules=false kind=src path=/api/ classpathentry kind=output path=target/classes/ /classpath The version above has three direct references to projects common, system, and api which are all sibling projects, i.e., are located in the same folder than project foo. Regarding Maven all four projects are modules of a parent project. When I now start mvn eclipse:eclipse in project foo it will create a .classpath file that looks like this: ?xml version=1.0 encoding=UTF-8? classpath classpathentry kind=src path=src/main/java/ classpathentry kind=src path=src/test/java output=target/test-classes/ classpathentry kind=output path=target/classes/ classpathentry kind=con path=org.eclipse.jdt.launching.JRE_CONTAINER/ classpathentry kind=var path=M2_REPO/org/blahh/common/1.0/common-1.0.jar/ classpathentry kind=var path=M2_REPO/org/blahh/system/2.0/system-2.0.jar/ classpathentry kind=var path=M2_REPO/org/blahh/api/1.2/api-1.2.jar/ /classpath The three projects are now referenced by the JAR artifact from the repository. This is not optimal for me since changes to the code in one of the three projects are not instantly visible to project foo (provided that Eclipse' auto build is turned on); only after a Maven install rebuild. Is there any option that I can use to force the Eclipse plugin to reference dependency projects directly? If it doesn't exist yet, then take this as a feature request. Thanks, Thorsten -- Michael McCallum Enterprise Engineer mailto:[EMAIL PROTECTED] - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Maven 2.1 release
Graham Leggett wrote: On Sun, January 13, 2008 1:31 am, Brian E. Fox wrote: I think John is wrapping up a few issues before an alpha goes out. Are there any showstoppers outstanding that prevent a release? http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=truemode=hidesorter/order=DESCsorter/field=priorityresolution=-1pid=10500fixfor=13143 Regards, Graham -- - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED] -- Dennis Lundberg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Run plugin on some goal execution
Hi, I'd like to bind the antrun plugin to the jetty:run goal. I have noticed it is only possible to bind against phases only. Does that mean, that I can't do that? My intention is to copy some temporary resources to the webapp dir during jetty:run thx -- NO OOXML - Say NO To Microsoft Office broken standard http://www.noooxml.org - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: [c 1.1] schedule build per svn check-in?
you can have svn push a request to continuum to do a build using the xmlrpc interface to continuum jesse On Jan 15, 2008 1:38 PM, Mick Knutson [EMAIL PROTECTED] wrote: Is it possible to kick off the build each time there is a new update available in svn? -- 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 --- -- jesse mcconnell [EMAIL PROTECTED]
Re: [c 1.1] schedule build per svn check-in?
Is there a wiki or something that can show me how to do that? I am not very good with svn On Jan 15, 2008 12:44 PM, Jesse McConnell [EMAIL PROTECTED] wrote: you can have svn push a request to continuum to do a build using the xmlrpc interface to continuum jesse On Jan 15, 2008 1:38 PM, Mick Knutson [EMAIL PROTECTED] wrote: Is it possible to kick off the build each time there is a new update available in svn? -- 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 --- -- jesse mcconnell [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: org.codehaus.mojo:jaxws-maven-plugin Random order of generated sourceCode ?
It is best to ask this question at java.net ws-common.
-D
On Jan 15, 2008 8:57 AM, [EMAIL PROTECTED] wrote:
Hi,
I´m using the jaxws-maven-plugin.
plugin
groupIdorg.codehaus.mojo/groupId
artifactIdjaxws-maven-plugin/artifactId
executions
execution
idserver-bindings/id
goals
goalwsimport/goal
/goals
/execution
/executions
configuration
bindingDirectory${basedir}/src/main/config/bindingDirectory
bindingFiles
bindingFilejaxws-ts-server-bindings.xml/bindingFile
/bindingFiles
destDir${project.build.directory}/classes/destDir
keeptrue/keep
staleFile${project.build.directory}/staleFlag/staleFile
wsdlDirectory${basedir}/src/main/wsdl//wsdlDirectory
wsdlFiles
wsdlFileTelematikTransport.wsdl/wsdlFile
/wsdlFiles
wsdlLocation/wsdlLocation
/configuration
/plugin
In the generated sourcecode, the method order changes, each time I execute
the build.
The source is correct, but the random behaviour makes it difficult to
compare jars from different builds.
Has anyone an idea of the base problem? I guess it´s not in the plugin,
but in the underlaying stuff (XJC, JAXB .)
Thanx,
Torsten
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
[m2] Off-topic: Has anyone gotten Cargo plugin to deploy to Oc4j 10.1.3 ?
I see the docs talk about oc4j 9.x but we are running 10.1.3 and want to deploy to a running container. -- 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: [m2] Off-topic: Has anyone gotten Cargo plugin to deploy to Oc4j 10.1.3 ?
The deployment process changed a bit from 9.x to 10.1.3, and I don't believe anyone has written any new Cargo plugin/updates for 10.1.3, so I don't believe this will happen without some work on your end. Wayne On 1/15/08, Mick Knutson [EMAIL PROTECTED] wrote: I see the docs talk about oc4j 9.x but we are running 10.1.3 and want to deploy to a running container. -- 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]
[c 1.1] Possible to use the Continuum build number as part of the artifact name?
I want to create our war final name appended with the continuum build number: myProject-userwebapp-1.25-build-42.war Is this possible? -- 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: [c 1.1] Possible to use the Continuum build number as part of the artifact name?
On Jan 15, 2008 2:54 PM, Mick Knutson [EMAIL PROTECTED] wrote: I want to create our war final name appended with the continuum build number: myProject-userwebapp-1.25-build-42.war Is this possible? Just a guess, but since unsuccessful builds don't get a number, I bet the number isn't assigned until after the build finishes. Take a look at the buildnumber plugin (actually there are two, I'm not sure which is preferred) * http://mojo.codehaus.org/buildnumber-maven-plugin/ * http://commons.ucalgary.ca/projects/maven-buildnumber-plugin/introduction.html -- Wendy
release-plugin: additional options for automation
We're about to start using the maven-release-plugin on a large project, and found a few things that would be nice to pass in as arguments on the command line. I looked to see if this was already possible, and came up blank. Does anyone know if it's possible to... 1) release:branch needs two pieces of information: (a) the branch name and (b) the new working copy version. The former can be specified using -DbranchName but the latter isn't documented. Is there a way to specify the new working copy version on the command line? Ideally I'd be able to do something like this: $ mvn release:branch -DbranchName=release-3.1 -DdevelopmentVersion= 3.2-SNAPSHOT 2) release:prepare needs three pieces of information: (a) the release version, (b) the release scm tag, and (c) the new development version. According to the documentation, only the tag can be specified on the command line using -Dtag=wombat. What about the others? $ mvn release:prepare -DreleaseVersion=3.1 -Dtag=release-3.1.0-DdevelopmentVersion= 3.1.1-SNAPSHOT Tell me there's already a way to do this? If not, what do you think... I can log some issues and submit some patches if the consensus is that it's a good idea. Also, a few minor notes on consistency of naming: 1) When prompting the user for the next version, the branch goal asks new working copy version and the prepare goal asks new development version. It seems these two questions are the same and should be framed the same. 2) The branch goal asks for a branchName and prepare asks for a tag, both of these are the same type of thing (at least in SVN). Either the Name part of branchName shoudl be removed or Name added to tag, resulting in branchName and tagName *or* branch and tag. Christian -- Christian Nelson -- (e) [EMAIL PROTECTED] -- (m) 415-378-3988
[m2] continuum dashboard integration?
http://mojo.codehaus.org/dashboard-maven-plugin/continuum.html I do not understand what is meant by first goal, second goal and third goal. DO I need to setup a seperate Maven2 project in my default project group for each goal? -- 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: [m2] continuum dashboard integration?
On 1/15/08, Mick Knutson [EMAIL PROTECTED] wrote: http://mojo.codehaus.org/dashboard-maven-plugin/continuum.html I do not understand what is meant by first goal, second goal and third goal. DO I need to setup a seperate Maven2 project in my default project group for each goal? No. Open your project definition in Continuum (as admin or as user with proper rights) and add the three build definitions as explained. Kalle -- 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: [m2] dashboard report not printing Cobertura overview anymore
Looking through my mvn site:site logs, I notice: Cobertura: Error reading file C:\viewstore\esp_lynx_dap\esp\dap\utilities\common\common-a3\target\cobertura\cobertura.ser: net.sourceforge.cobertura.covera gedata.CoverageDataContainer; local class incompatible: stream classdesc serialVersionUID = 2, local class serialVersionUID = 2152686494816595840 Cobertura: Error reading file C:\viewstore\esp_lynx_dap\esp\dap\utilities\common\common-exception\target\cobertura\cobertura.ser: net.sourceforge.cobertura .coveragedata.CoverageDataContainer; local class incompatible: stream classdesc serialVersionUID = 2, local class serialVersionUID = 2152686494816595840 Cobertura: Error reading file C:\viewstore\esp_lynx_dap\esp\dap\utilities\common\common-jar\target\cobertura\cobertura.ser: net.sourceforge.cobertura.cover agedata.CoverageDataContainer; local class incompatible: stream classdesc serialVersionUID = 2, local class serialVersionUID = 2152686494816595840 Cobertura: Error reading file C:\viewstore\esp_lynx_dap\esp\dap\utilities\common\common-logging\target\cobertura\cobertura.ser: net.sourceforge.cobertura.c overagedata.CoverageDataContainer; local class incompatible: stream classdesc serialVersionUID = 2, local class serialVersionUID = 2152686494816595840 Cobertura: Error reading file C:\viewstore\esp_lynx_dap\esp\dap\utilities\services\logging\target\cobertura\cobertura.ser: net.sourceforge.cobertura.covera gedata.CoverageDataContainer; local class incompatible: stream classdesc serialVersionUID = 2, local class serialVersionUID = 2152686494816595840 Cobertura: Error reading file C:\viewstore\esp_lynx_dap\esp\dap\utilities\services\logging-mdb\target\cobertura\cobertura.ser: net.sourceforge.cobertura.co veragedata.CoverageDataContainer; local class incompatible: stream classdesc serialVersionUID = 2, local class serialVersionUID = 2152686494816595840 On Jan 15, 2008 9:48 PM, Mick Knutson [EMAIL PROTECTED] wrote: I have a multi-module project and before I upgraded to cobertura 2.3, the main page aggregate all my modules. But now they all come up as zero: Afferent Coupling Average = 0.44 Nb Packages = 25 PackageAfferent CouplingLine CoverageBranch Coverage org.delta.esp.dap.c2.claim20%0%org.delta.esp.dap.c2.claim 10%0% org.delta.esp.dap.c2.claim.runtime10%0% org.delta.esp.dap.c2.generateclaimidproxy.proxy.runtime1 0%0% org.delta.esp.dap.c2.quadrant.codes10%0%org.delta.esp.dap.c2.splitclaim10% 0% org.delta.esp.dap.c2.splitclaim.util10%0% org.delta.esp.dap.c2.transform.util10%0% org.delta.esp.dap.c2.transform.util 10%0%org.delta.esp.dap.c2.util10%0% But when I go directly to the cobertura test link under project reports, I see the generated report fine: http://rc-sun66e.ut.dentegra.lab/site/1.0.1/c2/business-services/generate-claim-id/cobertura/frame-summary-org.delta.esp.dap.c2.claim.html org.delta.esp.dap.c2.claimhttp://rc-sun66e.ut.dentegra.lab/site/1.0.1/c2/business-services/generate-claim-id/cobertura/frame-summary-org.delta.esp.dap.c2.claim.html 5 29% 41/143 0%0/54 plugin groupIdorg.codehaus.mojo/groupId artifactIdcobertura-maven-plugin/artifactId version2.2/version configuration formats formatxml/format formathtml/format /formats instrumentation ignores ignorecom/**/*Exception.class/ignore ignoreorg/**/*Exception.class/ignore ignorecom/**/BaseObject.class/ignore ignore org.apache.commons.logging.* /ignore /ignores excludes excludecom/**/*Test.class/exclude excludeorg/**/*Test.class/exclude excludecom/**/*Exception.class/exclude excludeorg/**/* Exception.class /exclude excludecom/**/BaseObject.class/exclude excludeorg.apache.commons.logging.* /exclude /excludes /instrumentation . plugin groupIdorg.codehaus.mojo/groupId artifactIddashboard-maven-plugin/artifactId version1.0-SNAPSHOT/version /plugin -- 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 --- -- 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
[m2] dashboard report not printing Cobertura overview anymore
I have a multi-module project and before I upgraded to cobertura 2.3, the main page aggregate all my modules. But now they all come up as zero: Afferent Coupling Average = 0.44 Nb Packages = 25PackageAfferent CouplingLine CoverageBranch Coverage org.delta.esp.dap.c2.claim20%0%org.delta.esp.dap.c2.claim10%0% org.delta.esp.dap.c2.claim.runtime10%0% org.delta.esp.dap.c2.generateclaimidproxy.proxy.runtime10%0% org.delta.esp.dap.c2.quadrant.codes10%0%org.delta.esp.dap.c2.splitclaim10%0% org.delta.esp.dap.c2.splitclaim.util10%0%org.delta.esp.dap.c2.transform.util 10%0%org.delta.esp.dap.c2.transform.util10%0%org.delta.esp.dap.c2.util10%0% But when I go directly to the cobertura test link under project reports, I see the generated report fine: http://rc-sun66e.ut.dentegra.lab/site/1.0.1/c2/business-services/generate-claim-id/cobertura/frame-summary-org.delta.esp.dap.c2.claim.html org.delta.esp.dap.c2.claimhttp://rc-sun66e.ut.dentegra.lab/site/1.0.1/c2/business-services/generate-claim-id/cobertura/frame-summary-org.delta.esp.dap.c2.claim.html 529% 41/143 0%0/54 plugin groupIdorg.codehaus.mojo/groupId artifactIdcobertura-maven-plugin/artifactId version2.2/version configuration formats formatxml/format formathtml/format /formats instrumentation ignores ignorecom/**/*Exception.class/ignore ignoreorg/**/*Exception.class/ignore ignorecom/**/BaseObject.class/ignore ignoreorg.apache.commons.logging.* /ignore /ignores excludes excludecom/**/*Test.class/exclude excludeorg/**/*Test.class/exclude excludecom/**/*Exception.class/exclude excludeorg/**/*Exception.class/exclude excludecom/**/BaseObject.class/exclude excludeorg.apache.commons.logging.* /exclude /excludes /instrumentation . plugin groupIdorg.codehaus.mojo/groupId artifactIddashboard-maven-plugin/artifactId version1.0-SNAPSHOT/version /plugin -- 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: mojo cookbook; resolving transitively
Jeff MAURY wrote: On Jan 15, 2008 3:15 PM, Nigel Magnay [EMAIL PROTECTED] wrote: The Mojo Developer Cookbook (http://docs.codehaus.org/display/MAVENUSER/Mojo+Developer+Cookbook) is great. In it, there's a section on Resolving Transitively. This works great - however, the artifact set that is resolved is based on Maven's idea of which graph edges ought to be considered for resolution. For example, if I have a WAR file, then any declared dependencies that are JARs (and POM I think) are included, and those artifacts have their dependencies added to the list (and so on, recursively). The end result resolves to a single version for each JAR artifact. However - if the WAR file has a WAR dependency, then it will not be considered, and any JAR files in there won't be included in the set that the version is resolved in. This is not what I have from my experience. If a WAR POM has a dependency of type war, then then content of this dependency will be copied verbatim to the target folder. This was not about a *copy* it was about *resolution*. If the dependend war contains foo-1.2 and the local one depends on foo-1.3 you end up with both. This is the behaviour that I want, where I have a WAR of WARs, and I want to calculate the resolved set of dependencies. We always exclude WEB-INF/lib/*.* from the dependend wars and redeclare the deps. a) How can I interject my own requirements for dependency traversal? b) Is / how is this changed in 2.1 - all the methods on ArtifactResolver have been condensed down into 1.. See also MWAR-33 for discussion and workarounds. - Jörg - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
[m2]Want to have regex user packageLineRate
I want to use something liek this: regex patterncom.baselogic.*/pattern packageLineRate70/packageLineRate packageBranchRate80/packageBranchRate /regex instead of this: regex patterncom.baselogic.*/pattern lineRate60/lineRate branchRate50/branchRate /regex Is there something I can use like this as the top does not work? -- 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: [m2] dashboard report not printing Cobertura overview anymore
Hi Mich, Have a look at: http://www.nabble.com/dashboard---code-coverage-not-not-included-with-cobertura-2.2-to14354623s177.html#a14359864 Might be your case too. Erez. On Jan 16, 2008 7:50 AM, Mick Knutson [EMAIL PROTECTED] wrote: Looking through my mvn site:site logs, I notice: Cobertura: Error reading file C:\viewstore\esp_lynx_dap\esp\dap\utilities\common\common-a3\target\cobertura\cobertura.ser: net.sourceforge.cobertura.covera gedata.CoverageDataContainer; local class incompatible: stream classdesc serialVersionUID = 2, local class serialVersionUID = 2152686494816595840 Cobertura: Error reading file C:\viewstore\esp_lynx_dap\esp\dap\utilities\common\common-exception\target\cobertura\cobertura.ser: net.sourceforge.cobertura .coveragedata.CoverageDataContainer; local class incompatible: stream classdesc serialVersionUID = 2, local class serialVersionUID = 2152686494816595840 Cobertura: Error reading file C:\viewstore\esp_lynx_dap\esp\dap\utilities\common\common-jar\target\cobertura\cobertura.ser: net.sourceforge.cobertura.cover agedata.CoverageDataContainer; local class incompatible: stream classdesc serialVersionUID = 2, local class serialVersionUID = 2152686494816595840 Cobertura: Error reading file C:\viewstore\esp_lynx_dap\esp\dap\utilities\common\common-logging\target\cobertura\cobertura.ser: net.sourceforge.cobertura.c overagedata.CoverageDataContainer; local class incompatible: stream classdesc serialVersionUID = 2, local class serialVersionUID = 2152686494816595840 Cobertura: Error reading file C:\viewstore\esp_lynx_dap\esp\dap\utilities\services\logging\target\cobertura\cobertura.ser: net.sourceforge.cobertura.covera gedata.CoverageDataContainer; local class incompatible: stream classdesc serialVersionUID = 2, local class serialVersionUID = 2152686494816595840 Cobertura: Error reading file C:\viewstore\esp_lynx_dap\esp\dap\utilities\services\logging-mdb\target\cobertura\cobertura.ser: net.sourceforge.cobertura.co veragedata.CoverageDataContainer; local class incompatible: stream classdesc serialVersionUID = 2, local class serialVersionUID = 2152686494816595840 On Jan 15, 2008 9:48 PM, Mick Knutson [EMAIL PROTECTED] wrote: I have a multi-module project and before I upgraded to cobertura 2.3, the main page aggregate all my modules. But now they all come up as zero: Afferent Coupling Average = 0.44 Nb Packages = 25 PackageAfferent CouplingLine CoverageBranch Coverage org.delta.esp.dap.c2.claim20%0%org.delta.esp.dap.c2.claim 10%0% org.delta.esp.dap.c2.claim.runtime10%0% org.delta.esp.dap.c2.generateclaimidproxy.proxy.runtime1 0%0% org.delta.esp.dap.c2.quadrant.codes10%0%org.delta.esp.dap.c2.splitclaim10% 0% org.delta.esp.dap.c2.splitclaim.util10%0% org.delta.esp.dap.c2.transform.util10%0% org.delta.esp.dap.c2.transform.util 10%0%org.delta.esp.dap.c2.util10%0% But when I go directly to the cobertura test link under project reports, I see the generated report fine: http://rc-sun66e.ut.dentegra.lab/site/1.0.1/c2/business-services/generate-claim-id/cobertura/frame-summary-org.delta.esp.dap.c2.claim.html org.delta.esp.dap.c2.claim http://rc-sun66e.ut.dentegra.lab/site/1.0.1/c2/business-services/generate-claim-id/cobertura/frame-summary-org.delta.esp.dap.c2.claim.html 5 29% 41/143 0%0/54 plugin groupIdorg.codehaus.mojo/groupId artifactIdcobertura-maven-plugin/artifactId version2.2/version configuration formats formatxml/format formathtml/format /formats instrumentation ignores ignorecom/**/*Exception.class/ignore ignoreorg/**/*Exception.class/ignore ignorecom/**/BaseObject.class/ignore ignore org.apache.commons.logging.* /ignore /ignores excludes excludecom/**/*Test.class/exclude excludeorg/**/*Test.class/exclude excludecom/**/*Exception.class /exclude excludeorg/**/* Exception.class /exclude excludecom/**/BaseObject.class/exclude excludeorg.apache.commons.logging.* /exclude /excludes /instrumentation . plugin groupIdorg.codehaus.mojo/groupId artifactIddashboard-maven-plugin/artifactId version1.0-SNAPSHOT/version /plugin -- Thanks, Mick Knutson http://www.baselogic.com
