I was using antrun before but realized that the maven-exec plugin is better
because maven is executing nsis directly instead of via an ant build.xml.
Ken
On Mon, Sep 14, 2009 at 10:55 AM, James Russo j...@halo3.net wrote:
Will check those out. Thanks Stephen.
-jr
Stephen Connolly wrote:
Julien -
When you did this, did you encounter a problem where test dependencies (e.g.
Junit) were also copied?
Ken
On Tue, Sep 15, 2009 at 2:20 AM, Julien Graglia jgrag...@netceler.comwrote:
Le lundi 14 septembre 2009 à 16:17 -0400, James Russo a écrit :
Hello Julien,
In your
I've been looking at the same plugin recently and I think you can use the
maven dependency plugin to copy the jars to an output directory that will be
picked up by nsis.
Your nsis maven project will have to declare your wars as dependencies.
This is basically how I do it now without the NSIS
The date on the release page is wrong, it says November 23, 2007.
Ken
On Mon, Sep 22, 2008 at 3:37 PM, Olivier Lamy [EMAIL PROTECTED] wrote:
The Apache Continuum team is pleased to announce Apache Continuum 1.2.
The latest release is now available here:
The best practice is to externalize all environment specific configuration.
A single ear should be deployable to any environment without rebuilding.
This is not just to simplify configuration, it is also beneficial from a QA
standpoint because a binary can be moved between different environments
parameters.
Something like this takes a lot of commitment across development teams, but
maybe something like this would work for you.
On 8/6/08, Ken Liu [EMAIL PROTECTED] wrote:
The best practice is to externalize all environment specific configuration.
A single ear should be deployable to any
Hi all -
Is there any easy way to have maven generate a cmd or bat file with the java
command line populated with the classpath from the maven dependencies?
Ken
This is a great question...I have wondered the same thing myself.
I am working on a complex project that involves simultaneously releasing 6
ears. The whole build consists of 25+ maven projects (not counting
modules) that are built and released together (relax, many of them are
purely
Hi all -
Is there any way that the scm connection URL can automatically be read using
svn info instead of putting it into the pom?
For example, instead of writing:
scm
connectionscm:svn:http://my.svn.server/trunk/connection
/scm
You could just write something like:
scm
Maven scm does not implement the svn client software, it calls the
command-line svn executable instead. You will need to install the command
line client available at http://subversion.tigris.org, and have it available
in the path.
Ken
On 3/11/08, [EMAIL PROTECTED] [EMAIL PROTECTED] wrote:
Hi all -
I am looking for a plugin that can query a jira repository and produce a
report. I found an existing plugin, but that appears to be for maven 1.
Anyone know of a plugin that is compatible with maven2?
Ken
I'm sort of in the same boat, but for different reasons. The maven version
is considered to be part of the configuration for each project, so projects
are tied to whatever version of Maven was used at release time. Upgrades
are considered to be changes to the build environment, which are out of
, Jason Chaffee [EMAIL PROTECTED] wrote:
maven-enforcer-plugin
you might have to build the latest from source to get all the documented
functionality as the current released one doesn't support everything on
the Web site.
-Original Message-
From: Ken Liu [mailto:[EMAIL PROTECTED
shares and you would just put the config in that one place.
-Original Message-
From: Ken Liu [mailto:[EMAIL PROTECTED]
Sent: Friday, February 29, 2008 11:19 AM
To: Maven Users List
Subject: Re: SNAPSHOT checking plugin?
This looks great, but I would prefer not to add additional
Hi all -
I really like that the release-plugin checks the project for any SNAPSHOT
dependencies, but I am not so crazy about the release-plugin itself. Is
there any plugin available that will only do the check for SNAPSHOT
dependencies, or is there any other way to do this?
Thanks,
Ken
Dan -
Do you know if that bug was introduced in 2.0.7 (or some other earlier
release)? My team is using 2.0.4 and we encountered a problem with the
classpath ordering recently that caused builds to that were previously
working to suddenly start failing.
Thanks,
Ken
On 2/15/08, Dan Fabulich
I experienced the same problem with Maven 2.0.4 and Surefire 2.3 and 2.4. I
solved the problem by reverting the Surefire plugin version back to 2.2.
I believe the latest version of Maven 2.0.8 and Surefire 2.3 and 2.4 do not
have this problem.
Ken
On 1/29/08, Andrew Seales [EMAIL PROTECTED]
Hi all -
I am getting close to releasing a project and am trying to nail down all the
SNAPSHOT dependencies. I have one plugin (jboss-sar), which was never
released, and only has a 2.0-SNAPSHOT version available. I want to take
this jar and assign a release number to it to be installed in our
as you'd like.
Just my €0.02
On Jan 22, 2008 7:54 PM, Ken Liu [EMAIL PROTECTED] wrote:
Hi all -
I am getting close to releasing a project and am trying to nail down all
the
SNAPSHOT dependencies. I have one plugin (jboss-sar), which was never
released, and only has a 2.0-SNAPSHOT
Eric,
I agree with this procedure. I would not recommend handing over a SNAPSHOT
build to a QA group as a release candidate. It is safer to build off of a
branch and treat that branch as a release candidate if there is
ongoing development work in the trunk. If developers are putting
changes into
20 matches
Mail list logo
