Skip instal//deploy

Is there a way to mark an artifact such that the install and deploy are skipped? In my case, there really is no need to have WAR files in my local or public repositories. Sean - To unsubscribe, e-mail: [EMAIL PROTECTED] For

[m2] Nightly build using assembly

I'm trying to publish our project's nightly builds using assembly:assembly publish. The resulting tarballs are published but so are the poms and meta-data.xml. Ideally this would not be published as the end user does not care about such things. They just want to download the tarball. Also, if

Re: [m2] Nightly build using assembly

I'm trying to publish our project's nightly builds using assembly:assembly publish. Actually I'm using assembly:assembly deploy - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]

Re: [m2] Multiprojects and inherited SCM URLs

How about this: scm:svn:svn://host/PROJECT/${pom.artifactId} This should work if you use the same name for the part in your svn repository as their artifactIds. This works. Unfortunately in our case the svn module does not match the artifactId. It would be nice if they could deviate and

Re: Problem with continuum on solaris zone

, 2006-01-13 at 09:14 -0500, Sean Schofield wrote: We're trying to setup continuum for the MyFaces project. We have a solaris zone set up and we're having trouble starting the server. $ bin/solaris/run.sh start Starting continuum... bin/solaris/run.sh: ./wrapper: cannot execute We've tried

Re: unit test fails for 'package' but not 'site' or 'test'

Lee, We're going to be moving the Maven stuff around tomorrow. Over the next few days we should be settling on the final layout. Some of the unit tests do not work (as you discovered) but should be excluded from the build (for the moment.) Hopefully we'll get everything sorted out with lots of

Re: unit test fails for 'package' but not 'site' or 'test'

Lee, Disregard my email. ;-) I thought the message was to myfaces-users. The two folders are next to each other in gmail. Sorry for the confusion. Sean On 1/6/06, Sean Schofield [EMAIL PROTECTED] wrote: Lee, We're going to be moving the Maven stuff around tomorrow. Over the next few

[m2] Dependency scope options

I'm having trouble determining the scope choices for a dependency entry. Right now I have something like: dependency groupIdcommons-codec/groupId artifactIdcommons-codec/artifactId version1.3/version scopecompile/scope

Re: [m2] Dependency scope options

Actually when I did a clean install I discovered that having both scopes listed does not work. Its unable to compile. When I comment out the test scope entry it compiles but I'm getting runtime errors which I believe are coming from the fact that the unit tests can't find the class. Sean On

Re: [m2] Dependency scope options

John, Thanks for the link. That is what I was looking for. I don't know why I couldn't find it on my own but I was having trouble ;-) Sean On 1/2/06, John Fallows [EMAIL PROTECTED] wrote: Sean, On 1/2/06, Sean Schofield [EMAIL PROTECTED] wrote: I'm having trouble determining the scope