I'm using 2.0.4 with the most recent plugin versions. I'm trying to
configure JBoss 4.0.5 prior to running an integration test from my
build. I'm trying to run the following goals in these phases:
pre-integration-test:
cargo:install
antrun:run
cargo:start
post-integration-test:
-Original Message-
From: Crossley, Jim [mailto:[EMAIL PROTECTED]
Sent: Tuesday, January 30, 2007 3:59 PM
To: users@maven.apache.org
Subject: Execution order in pre-integration-test phase for Cargo/Antrun
I'm using 2.0.4 with the most recent plugin versions. I'm trying to
configure JBoss 4.0.5 prior
I'm close to having a beautiful maven (2.0.4) build using 3 handy
plugins: appassembler, assembly, and rpm.
My app is a simple command line thing. I use appassembler to create
wrapper shell scripts, and assembly to package it as a tarball.
I occasionally need to build an RPM, so I added a
Do I really have to write an entire plugin just to make a timestamp
available as a maven property? That's what Google is telling me, but I
wanted to make sure before I went to all that trouble.
Thanks,
Jim
-
To unsubscribe,
/addTimestamp
tagbuild/tag
timestampFormatMMddHHmm/timestampFormat
/configuration
/plugin
-Original Message-
From: Crossley, Jim [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 06, 2007 3:57 PM
To: Maven Users List
Subject: Can I get a timestamp?
Do I really have
-in will allow you to use timestamp tagging to tag your builds.
I am sorry but I don't think you can access the timestamp property
directly in the pom itself. Why do you need to do that anyway?
Bashar
-Original Message-
From: Crossley, Jim [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 06
to tag your
builds. I am sorry but I don't think you can access the timestamp
property directly in the pom itself. Why do you need to do that
anyway?
Bashar
-Original Message-
From: Crossley, Jim [mailto:[EMAIL PROTECTED]
Sent: Tuesday, February 06, 2007 4:43 PM
To: Maven Users
Hi.
I'm looking to take advantage of hibernate-tools' abililty to generate a
graph of my entity relationships. After looking at MOJO-544 and
MOJO-530, I thought it might be as easy as applying the attached patch
to the source and setting the dotExecutable property, but that didn't
work.
I
of the plugin.
Right now the plugin is in the process of being voted to be released so
I won't be doing any changes until the vote process finishes.
Regards
Johann Reyes
-Original Message-
From: Crossley, Jim [mailto:[EMAIL PROTECTED]
Sent: Wednesday, February 21, 2007 10:31 AM
To: Maven Users
All (but Brett in particular, I think),
I'm trying to test some SQL queries in my EJB3/JPA app. To do this, I'd
like for my unit tests to run against an in-memory Hypersonic database.
I configured a persistence unit appropriately in
src/test/resources/META-INF/persistence.xml, but alas Surefire
So nobody here requires additional classpath resources in their tests?
Surprising.
I created http://jira.codehaus.org/browse/SUREFIRE-294 to track the
problem.
Thanks,
Jim
-Original Message-
From: Crossley, Jim [mailto:[EMAIL PROTECTED]
Sent: Friday, February 23, 2007 3:08 PM
To: Maven
Hi all,
I'm currently digging the Maven release plugin, but I'd like to be able
to run it in batch mode, accepting the default values it suggests for
version, scm tag, etc.
Unfortunately, CVS doesn't seem to like dots '.' in a tag name. Is
there any mechanism I can invoke to override the
Hi Dave,
I typically don't want child projects to have a version different from
the parent. If I did, I probably wouldn't organize them as subprojects.
So for my subprojects, I omit the version attribute in their POM. That
way they inherit the version from the parent.
As for dependencies, I do
Or at least, so it seems. Only SNAPSHOT versions of the plugin upon which my
project depends have ever been released, and I need to cut a release of my
project. The release plugin won't let me as long as I depend on a SNAPSHOT
plugin. I understand why, but I'm wondering which best practice
Hi David,
One common trick is to co-locate your continuous integration tool, e.g.
Continuum, CruiseControl, etc, and your internal repository. Say you have
Continuum running as user, 'dave', and you also have Apache running on the same
box. (I'm assuming a Linux environment here). An easy
Subject: Re: My plugin maintainer died
Are you talking about the launch4j plugin? Because I seem to have the same
situation there. I tried emailing the author already 2 times, but no luck.
regards,
Wim
2007/4/20, Crossley, Jim [EMAIL PROTECTED]:
Or at least, so it seems. Only SNAPSHOT
I used the release plugin to successfully release version 2.0.2.1 of our
project. We continued working on the HEAD targeting version 2.0.3 while
QA tested 2.0.2.1. To address bugs reported against that release, we
created a 2.0.2 branch in CVS. We applied our fixes there.
Now it's time to
far.
Wayne
On 4/26/07, Crossley, Jim [EMAIL PROTECTED] wrote:
I used the release plugin to successfully release version 2.0.2.1 of
our
project. We continued working on the HEAD targeting version 2.0.3
while
QA tested 2.0.2.1. To address bugs reported against that release, we
created a 2.0.2
Thanks Roland, Trevor, and Heinrich. The summary below captures the
problem quite concisely.
Roland, perhaps we can work together to implement, or at least come up
with a proposal for one or both of the solutions below.
And anyone else who has a better idea, please speak up.
Jim
-Original
Hi.
Rapha l Pi roni [EMAIL PROTECTED] writes:
[...]
is this dumb?
Nope.
do that need a enhancement jira?
Yep. http://jira.codehaus.org/browse/MRELEASE-226
Thanks,
Jim
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
Thanks for the release, Stephane. After I upgraded, however, I noticed
the release:perform task no longer honors the executable permission bit
set on my some of my files. My SCM is CVS. I looked in Jira but
couldn't find a bug for it, though something makes me think it's a known
problem with
2.0-beta-5 Released
Jim,
the new version use a pure java cvs client by default, instead of the system
cvs executable.
Emmanuel
Crossley, Jim a écrit :
Thanks for the release, Stephane. After I upgraded, however, I
noticed the release:perform task no longer honors the executable
permission
on the command line:
mvn -Dmaven.scm.provider.cvs.implementation=cvs_native release:prepare mvn
-Dmaven.scm.provider.cvs.implementation=cvs_native release:perform
I'll try to improve it in the next version.
Emmanuel
Crossley, Jim a écrit :
So is there no way to make the Java client honor exec permissions
Is Continuum dead? It hasn't been released in over a year. I need for
it to build multi-module project snapshots correctly.
Thanks,
Jim
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL
I upgraded my pom to use 2.2 of the assembly plugin to fix an unrelated
issue, and now I can't seem to get filtering to work. Filtering worked
in 2.1 with the identical descriptor, and it didn't look like its format
changed in any relevant way (according to the docs).
Anyone know anything about
The path of least resistance is to introduce the fourth project 'D' upon
which the others would depend. You might be able to host the resource
in the parent by using relative references, e.g. in each child you'd
have something like this:
resources
resource
26 matches
Mail list logo