Ok, that makes sense. Thanks for the quick answer!
On 11/3/05, Brett Porter <[EMAIL PROTECTED]> wrote:
>
> When the SCM URL is inherited, it automatically appends the artifact
> ID by default.
>
> - Brett
>
> On 11/4/05, Mark Langley <[EMAIL PROTECTED]
Hi,
First, congratulations to the m2 developers for a great release. I've been a
maven user since 1.0-beta-4 with embedded ant scripts, through beta-10, 1.0and
1.1, and am truly impressed with the leap forward that m2 provides.
I'm trying to migrate to m2 and have encountered an apparent glitch.
Here's the maven.xml fragment that we use. I'm afraid I can't help any
further if this doesn't work - after several failed attempts this is the
approach that finally worked for us with Tomcat 5.0.28.
Mark Langley
CaseBank Technologies Inc.
htt
We had the same problem two weeks ago. Upgrading Tomcat to 5.0.28 made it go
away.
Mark Langley
CaseBank Technologies Inc.
http://www.casebank.com
-Original Message-
From: Darren Hartford [mailto:[EMAIL PROTECTED]
Sent: November 8, 2004 10:54 AM
To: Maven Users List
Subject: Class
Subject: RE: Maven and Development Process
On Thu, 2004-04-15 at 14:38, Mark Langley wrote:
> If you use XML entities to define your version numbers rather than hard
> coding them in the project.xml files, the process of switching between
> snapshot and release versions becomes much easier.
&g
If you use XML entities to define your version numbers rather than hard
coding them in the project.xml files, the process of switching between
snapshot and release versions becomes much easier.
See http://wiki.codehaus.org/maven/EnsureProjectConsistencyWithEntities for
more details.
-Origina
We also desire to make test utility classes (primarily Mock Objects)
available for use in testing of dependent projects. The approach of creating
XYZ.jar and XYZ-tests.jar artifacts from project XYZ seems to be the best
approach to this. Subsequent projects could then prescribe XYX-tests.jar as
a t
