Maven Users Archive Page
Has something changed on the Maven Users Archive Page? I can see the page at http://www.mail-archive.com/users%40maven.apache.org/ But when I try to search for something I always get a page saying "Not Found: The document you were looking for was not found". It's a site-generated page, not the standard browser 404. It's not working on any of my machines Kevan. Kevan Dunsmore Senior Software Engineer SABRIX Inc t: 503.924.4908 f: 503.620.5756 This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information that is protected from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and any attachments.
RE: Deploy to repository | Windows network file url
Brian, This works for me: file:host/share/path Kevan. -Original Message- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 13, 2007 1:10 PM To: users@maven.apache.org Subject: RE: Deploy to repository | Windows network file url Thanks Gaute, I tried the following combinations with no luck: file:///\\host/path file:/host/path As well as mapping \\host\path\to\my\Shared%20Drive to drive letter B: and using the following URL file:///B:/Maven/... None of which worked. Any other ideas? -Original Message- From: Gaute Lote [mailto:[EMAIL PROTECTED] Sent: Tuesday, February 13, 2007 3:31 PM To: Maven Users List Subject: Re: Deploy to repository | Windows network file url I've had the same problem. If you check your local disc you'll probably have a catalog named host/path/to/my/Shared%20Drive/Maven/repository/com/ubs/eq/tas/na/tasna/ 1.0-SNAPSHOT/ You need to add more slashes so that maven understand that the tagert directory is on another machine. If I remeber correctly file:/host/path will do the trick... Gaute On 2/13/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: > > So I'm trying to setup a repository on a Windows shared drive. I > configured my POM as: > > > > tasna > > file://host/path/to/my/Shared%20Drive/Maven/repository > > > > > I run "mvn deploy" and get the following output: > > [INFO] Scanning for projects... > [INFO] > -- > -- [INFO] Building Trade and Asset Services > [INFO]task-segment: [deploy] > [INFO] > -- > -- > [INFO] [site:attach-descriptor] > [INFO] [install:install] > [INFO] Installing C:\Projects\Commons\tasna\pom.xml to C:\Documents > and > Settings\jacksoba.UBSW\.m2\repository\com\ubs\eq\tas\na\tasna\1.0-SNAP > SHOT\tasna- > 1.0-SNAPSHOT.pom > > [INFO] [deploy:deploy] > altDeploymentRepository = null > [INFO] Retrieving previous build number from tasna > Uploading: * > file://host/path/to/my/Shared%20Drive/Maven/repository/com/ubs/eq/tas/ > na/tasna/1.0-SNAPSHOT/tasna-1.0-20070213.192326-10.pom > * > > 4/6K > 6/6K > 6K uploaded > [INFO] Retrieving previous metadata from tasna [INFO] Uploading > repository metadata for: 'snapshot > com.ubs.eq.tas.na:tasna:1.0-SNAPSHOT' > [INFO] Retrieving previous metadata from tasna [INFO] Uploading > repository metadata for: 'artifact com.ubs.eq.tas.na:tasna' > [INFO] > -- > -- > [INFO] BUILD SUCCESSFUL > [INFO] > -- > -- > [INFO] Total time: 3 seconds > [INFO] Finished at: Tue Feb 13 14:23:26 EST 2007 [INFO] Final Memory: > 5M/10M [INFO] > -- > -- > > But when I check my repository, the POM hasn't been updated. Any idea > what is going on? I know the URL is right because I can hit * > file://host/path/to/my/Shared%20Drive/Maven/repository/com/ubs/eq/tas/ > na/tasna/1.0-SNAPSHOT/ > * in the Windows Explorer without issue. > > Thanks, > Brian > > > Visit our website at http://www.ubs.com > > This message contains confidential information and is intended only > for the individual named. If you are not the named addressee you > should not disseminate, distribute or copy this e-mail. Please notify > the sender immediately by e-mail if you have received this e-mail by > mistake and delete this e-mail from your system. > > E-mail transmission cannot be guaranteed to be secure or error-free as > information could be intercepted, corrupted, lost, destroyed, arrive > late or incomplete, or contain viruses. The sender therefore does not > accept liability for any errors or omissions in the contents of this > message which arise as a result of e-mail transmission. If > verification is required please request a hard-copy version. This > message is provided for informational purposes and should not be > construed as a solicitation or offer to buy or sell any securities or > related financial instruments. > > > - > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > Visit our website at http://www.ubs.com This message contains confidential information and is intended only for the individual named. If you are not the named addressee you should not disseminate, distribute or copy this e-mail. Please notify the sender immediately by e-mail if you have received this e-mail by mistake and delete this e-mail from your system. E-mail transmission cannot be guaranteed to be secure or error-free as information could be intercepted, corrupted, lost, destroyed, arrive late or incomplete, or contain viruses. The sender therefore does not accept liability for
RE: Maven 2 can't find plugins
I've had a similar problem. It appears that Maven is able to download
the pom for a plugin but not the plugin itself if you don't have
defined but do have . If you clear
everything from your local repo then attempt to download the plugin as a
side-effect of your build you'll see the repo directory created and the
correct pom pulled down to that directory. Maven will then fail saying
that it can't find the jar. You'll see a message saying that Maven is
trying to load the jar from a different repository from the one in which
it found the pom (usually "central").
I found this problem with plugins I had written myself. It might also be
something you'll see with external plugins
Kevan.
-Original Message-
From: Wayne Fay [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 13, 2007 4:02 PM
To: Maven Users List
Subject: Re: Maven 2 can't find plugins
Without knowing anything more about your project or seeing your
pom.xml files, I assume you've declared but not
to match.
Wayne
On 2/13/07, Rod Mclaughlin <[EMAIL PROTECTED]> wrote:
> I have an even more basic issue. Whenever I have a plugin in a POM.xml
> file, and try to use it, eg.
> *$ mvn xfire:wsdlgen *
> Maven 2 says*
> 'Scanning for projects... Searching repository for plugin with prefix:
> 'xfire'. org.apache.maven.plugins: checking for updates
> org.codehaus.mojo: checking for updates from central artifact
> org.apache.maven.plugins:maven-xfire-plugin: checking for updates from
> central
> [ERROR] BUILD ERROR
> The plugin 'org.apache.maven.plugins:maven-xfire-plugin' does not
exist
> or no valid version could be found'*
> This is true whatever the plugin. It's not a proxy issue: it can
> download ordinary jars from the repository, just not plugins. For
> example, here is a simple bit of a POM referring to
xfire-maven-plugin:
>
>
>
>
>
>org.codehaus.mojo
>xfire-maven-plugin
>
>
> test-compile
>
> wsdlgen
>
>
>
>
>
>
>
${project.build.directory}/generated-sources/xfire/wsdl
gen
>
>
> ${basedir}/src/main/resources/META-INF/xfire/services.xml
>
>
>
>
>
>
>
>
>
>
> Again, I've searched the web, the mailing lists etc.. Thanks for any
> advice...
>
>
>
> -
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
>
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This e-mail message, including any attachments, is for the sole use of the
intended recipient(s) and may contain confidential and privileged information
that is protected from disclosure. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message and any attachments.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Question on Ant Plugins
I wrote an ant plugin for Maven. As per documentation I have two files: deebee.build.xml deebee.mojos.xml I have two questions. 1. I would like to have all of my mojos in different files, importing them into the main deebee.build.xml file, something like this: This syntax doesn't work. Everything builds and installs but at runtime I get an error saying that "afile.xml" and "anotherfile.xml" cannot be found. 2. I can't get to work. If I have this: Then again everything installs correctly but I get a "file not found" error when execution hits the line. Any ideas? Thanks, Kevan. Kevan Dunsmore Senior Software Engineer SABRIX Inc t: 503.924.4908 f: 503.620.5756 This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information that is protected from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and any attachments.
RE: Skipping Tests but Still Compiling
Can you point me to the mechanism you use to search the archives? Thanks, Kevan. -Original Message- From: Wayne Fay [mailto:[EMAIL PROTECTED] Sent: Tuesday, January 30, 2007 10:42 PM To: Maven Users List Subject: Re: Skipping Tests but Still Compiling This "compile tests but don't run" issue was covered just 2 weeks ago... Please search the archive before posting next time. from jp4 <[EMAIL PROTECTED]> to users@maven.apache.org date Jan 15, 2007 11:34 AM subject Can you compile test cases without running them Wayne On 1/30/07, Bashar Abdul Jawad <[EMAIL PROTECTED]> wrote: > Try to add the compile plugin if it isn't there already: > > > org.apache.maven.plugins > > maven-compiler-plugin > > > Bashar > > > -Original Message- > From: Mark Hewett [mailto:[EMAIL PROTECTED] > Sent: Tuesday, January 30, 2007 4:13 PM > To: Maven Users List > Subject: Re: Skipping Tests but Still Compiling > > On 1/30/07, Bashar Abdul Jawad <[EMAIL PROTECTED]> wrote: > > That is not true. Maven will still compile the test classes, but only if > > they have changed since the last compilation. To force maven to compile > even > > if there were no changes run a clean first. > > > > Bashar > > > Doesn't seem to for me... > > >mvn -Dmaven.test.skip=true clean install > > [INFO] [compiler:testCompile] > [INFO] Not compiling test sources > [INFO] [surefire:test] > [INFO] Tests are skipped. > > > - > 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] This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information that is protected from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and any attachments. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Skipping Tests but Still Compiling
So I just discovered that if I kick off a build using mvn -Dmaven.test.skip=true install then Maven will not even bother compiling the test classes. Is there any way to force Maven to compile the test classes but not run the tests? Thanks, Kevan. Kevan Dunsmore Senior Software Engineer SABRIX Inc t: 503.924.4908 f: 503.620.5756 This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information that is protected from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and any attachments.
RE: Maven-surefire qurious problem when extending it
I had similar problems with extension in my own plugins. It may be
related to the process Maven uses to set private member variables with
bound project properties. From what I've seen, it analyzes the source of
your plugin when you build and install it but not that of the
superclass. It doesn't know that the "testClassesDirectory" member must
be set, which causes the Surefire layer to fail with the NPE.
Check to see if there is a setter for that member and define a property
mapping for it. You may be able to coax it into doing the right thing.
I never found a (good) solution for this. Perhaps someone else out there
has bridged this gap before.
BTW, my solution, which is not available to you since you can't modify
the source easily, was to place abstract methods in my base class to
access the values I needed. I then bound private members in my subclass
plugin in the usual way and implemented the abstract methods to return
the relevant values. That meant that for each plugin that extended the
base class I had to re-write that boilerplate code. See what I mean
about not being a good solution :-)
-Original Message-
From: Petar Tahchiev [mailto:[EMAIL PROTECTED]
Sent: Thursday, January 25, 2007 12:52 PM
To: Maven Users List
Subject: Maven-surefire qurious problem when extending it
Hi guys,
I have a very unusual problem with the maven-surefire-plugin ver. 2.2
I want to write my own plugin, and as part of it's functionality is to
run a
couple of junit tests.
So I extend the MavenSurefirePlugin and my plugin looks like this:
public class MyMojo extends SurefirePlugin {}
Later I map my plugin and try to run it. The problem is that whenever I
run
it I get the following
error:
[ERROR] FATAL ERROR
[INFO]
[INFO] null
[INFO]
[INFO] Trace
java.lang.NullPointerException
at org.apache.maven.plugin.surefire.SurefirePlugin.execute(
SurefirePlugin.java:355)
at org.apache.maven.plugin.DefaultPluginManager.executeMojo(
DefaultPluginManager.java:412)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoals(
DefaultLifecycleExecutor.java:534)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeStandaloneGoa
l(
DefaultLifecycleExecutor.java:488)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(
DefaultLifecycleExecutor.java:458)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoalAndHandle
Failures
(DefaultLifecycleExecutor.java:306)
at
org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(
DefaultLifecycleExecutor.java:273)
at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(
DefaultLifecycleExecutor.java:140)
at
org.apache.maven.DefaultMaven.doExecute(DefaultMaven.java:322)
at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:115)
at org.apache.maven.cli.MavenCli.main(MavenCli.java:256)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(
NativeMethodAccessorImpl.java:39)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(
DelegatingMethodAccessorImpl.java:25)
at java.lang.reflect.Method.invoke(Method.java:585)
at
org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java
:315)
at org.codehaus.classworlds.Launcher.launch(Launcher.java:255)
at
org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java
:430)
at org.codehaus.classworlds.Launcher.main(Launcher.java:375)
On line 355 of the maven-surefire plugin stays the following line:
else if ( !testClassesDirectory.exists() )
And when debugging it - YES, indeed the the testClassesDirectory is
indeed
null !!!
I know I am missing something really fundamental, but I am not sure what
it
is, so any help would be greatly appretiated.
Thank you all.
--
Regards, Petar!
Karlovo, Bulgaria.
This e-mail message, including any attachments, is for the sole use of the
intended recipient(s) and may contain confidential and privileged information
that is protected from disclosure. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message and any attachments.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: How to customize artifact name with the current timestamp?
Sorry - I just re-read what I sent and it's not too clear. Let's say you
have an externally-governed final artifact name, comprised of a
constant, your department's name (I know, stretching it a bit but it's
just an example) and a build number:
my-thingy-${department-name}-${buildNumber}
These can be passed in to maven on the command line:
mvn -Ddepartment-name=TheDepartmentOfTheMachineThatGoesPing
-DbuildNumber=4
Which would result in a final artifact called
my-thingy-TheDepartmentOfTheMachineThatGoesPing-4
Whatever you use to kick off your install or deploy (Cruise Control,
Pulse, TeamCity, etc) would have to supply these values somehow.
Kevan.
-Original Message-
From: Kevan Dunsmore [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 24, 2007 11:13 AM
To: Maven Users List
Subject: RE: How to customize artifact name with the current timestamp?
The thing that springs to mind is for you to provide a final name that
contains your custom values. Cruise Control, for example, passes the
environment variable "label" to maven builds. You could customize the
output by doing this:
my-thingy-${project.version}-${label}
If you couple that with this:
0
Then anything that builds with no supplied label value will be defaulted
to 0. Otherwise you could invoke it with this:
mvn -Dlabel= clean install
Is that what you're looking for?
Kevan.
-Original Message-
From: Aliaksandr Radzivanovich [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 24, 2007 10:52 AM
To: users@maven.apache.org
Subject: How to customize artifact name with the current timestamp?
Is it possible with Maven 2 to install/deploy artifact snapshots with
customized version number '${project.id}-MMDD.hhmmss.jar' as
described in http://maven.apache.org/maven-1.x/plugins/jar/goals.html
?
Cheers,
ARa
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This e-mail message, including any attachments, is for the sole use of
the intended recipient(s) and may contain confidential and privileged
information that is protected from disclosure. Any unauthorized review,
use, disclosure or distribution is prohibited. If you are not the
intended recipient, please contact the sender by reply e-mail and
destroy all copies of the original message and any attachments.
-
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 customize artifact name with the current timestamp?
The thing that springs to mind is for you to provide a final name that
contains your custom values. Cruise Control, for example, passes the
environment variable "label" to maven builds. You could customize the
output by doing this:
my-thingy-${project.version}-${label}
If you couple that with this:
0
Then anything that builds with no supplied label value will be defaulted
to 0. Otherwise you could invoke it with this:
mvn -Dlabel= clean install
Is that what you're looking for?
Kevan.
-Original Message-
From: Aliaksandr Radzivanovich [mailto:[EMAIL PROTECTED]
Sent: Wednesday, January 24, 2007 10:52 AM
To: users@maven.apache.org
Subject: How to customize artifact name with the current timestamp?
Is it possible with Maven 2 to install/deploy artifact snapshots with
customized version number '${project.id}-MMDD.hhmmss.jar' as
described in http://maven.apache.org/maven-1.x/plugins/jar/goals.html
?
Cheers,
ARa
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
This e-mail message, including any attachments, is for the sole use of the
intended recipient(s) and may contain confidential and privileged information
that is protected from disclosure. Any unauthorized review, use, disclosure or
distribution is prohibited. If you are not the intended recipient, please
contact the sender by reply e-mail and destroy all copies of the original
message and any attachments.
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
RE: Process Question
Patrick, The other project executes the release plugin in batch mode so it just uses default values (it increments the last number in the build and chooses fairly sensible defaults for the other values). I also thought about the nice tagging feature of the release plugin and realized that, since we're using SVN, the repository revision number is good enough for nightly builds. I plan to look for something (or write it if I can't find it) that gets a hold of the revision number after Cruise Control synchs the source. Shoving that in an artifact would be enough, I think. It would let me pull back everything in the relevant project for that revision and build it. It's not as thorough as the tagging / no snapshot policy of the release plugin but I think it is good enough for such common builds. Other SCM systems work differently (Perforce, I believe, keeps a unique number for each file and not a global revision number) so to get the same effect a tagging plugin would be required, either executed by Maven or by the CI tool you use. Incidentally, on my project, we need the build number from the output of the deploy plugin. As far as I could see, there was no way to get a hold of that so I wrote my own plugin that will read the remote repository metadata and extract the number from it, making it available as a project property to the rest of the build. Thanks for the info, Patrick. Anybody else out there care to share their thoughts? Kevan. -Original Message- From: Patrick Schneider [mailto:[EMAIL PROTECTED] Sent: Wednesday, January 24, 2007 10:59 AM To: Maven Users List Subject: Re: Process Question Interestingly, my organization is trying to figure out the same issue at the moment. The big problem that I see with the 'mvn clean deploy' is that, while the build is numbered, you don't really have any way of reproducing that specific build. That is, the deploy plugin doesn't tag anything in your SCM system. So, even though your SNAPSHOT is unique by virtue of the fact you have a timestamped/numbered artifact, you really don't have a good way to "see" the differences between two uniquely numbered SNAPSHOT builds... maybe this isn't really important, I'm not sure. The nicest thing about a 'clean deploy' is what you brought up -- you can have SNAPSHOT dependencies, whereas in order to do a release, you must remove any such dependencies. This can be a huge undertaking if your project is sufficiently large. I think you are on the right track re: your assessment of the "right" way to use these two plugins. The release plugin is a weightier process -- doing it nightly seems overkill, IMO. Out of curiosity, are they doing the release manually? As far as I know, releasing is generally a somewhat manual process. There is interaction that has to occur with the user, such as determining the next version number, whereas a 'clean deploy' could be automated... Patrick On 1/24/07, Kevan Dunsmore < [EMAIL PROTECTED]> wrote: > > I'm trying to determine the "right" way to use Maven in our continuous > integration environment. Here's our basic process: > > > > 1. Code changes are made and checked in to SVN. > 2. Cruise Control detects the change and kicks off a build, > executing all the tests. This is a local build (maven clean install). > 3. Once a day, or on demand, CC kicks off a numbered build (maven > clean deploy). This numbered build is tested by QA. > > > > So much for the good; now for the bad: We have opposing camps. One camp > uses the deploy plugin as illustrated above. The other camp, on a > separate project, is executing the above process except that instead of > using the deploy plugin, they are using the release plugin. As far as I > can see, the use of the release plugin in step 3 goes against its > intent. The release plugin is meant for a release to a customer, not for > something that happens frequently like a nightly build. Further, the use > of the release plugin in this manner restricts the use of cross-project > libraries to released versions, since the release plugin enforces that > the pom does not depend on any snapshots. > > > > I'd like to get the thoughts of the group on this. I may be missing > something but I'd far rather use the deploy plugin for nightly builds > and the release plugin for packaging the application for release to our > customers. Am I wrong? > > > > Thanks, > Kevan. > > > > > > > > Kevan Dunsmore > > Senior Software Engineer > > SABRIX Inc > > t: 503.924.4908 > > f: 503.620.5756 > > > > > This e-mail message, including any attachments, is for the sole use of the > intended recipient(s) and may contain co
Process Question
I'm trying to determine the "right" way to use Maven in our continuous integration environment. Here's our basic process: 1. Code changes are made and checked in to SVN. 2. Cruise Control detects the change and kicks off a build, executing all the tests. This is a local build (maven clean install). 3. Once a day, or on demand, CC kicks off a numbered build (maven clean deploy). This numbered build is tested by QA. So much for the good; now for the bad: We have opposing camps. One camp uses the deploy plugin as illustrated above. The other camp, on a separate project, is executing the above process except that instead of using the deploy plugin, they are using the release plugin. As far as I can see, the use of the release plugin in step 3 goes against its intent. The release plugin is meant for a release to a customer, not for something that happens frequently like a nightly build. Further, the use of the release plugin in this manner restricts the use of cross-project libraries to released versions, since the release plugin enforces that the pom does not depend on any snapshots. I'd like to get the thoughts of the group on this. I may be missing something but I'd far rather use the deploy plugin for nightly builds and the release plugin for packaging the application for release to our customers. Am I wrong? Thanks, Kevan. Kevan Dunsmore Senior Software Engineer SABRIX Inc t: 503.924.4908 f: 503.620.5756 This e-mail message, including any attachments, is for the sole use of the intended recipient(s) and may contain confidential and privileged information that is protected from disclosure. Any unauthorized review, use, disclosure or distribution is prohibited. If you are not the intended recipient, please contact the sender by reply e-mail and destroy all copies of the original message and any attachments.
