Matt,
While it's true that M1 provides a jar override mechanism via
properties, I've found I've used it very infrequently (I still use m1
day in and day out).
Regarding version numbers in artifact names, if you find that you're
trying to circumvent this, you'll be fighting an uphill battle with
*any* version of maven.
It sounds like you're struggling with 3rd party artifacts that don't
have versions in their names. There's a lot of talk about dealing with
this in the list archives.
HTH,
DD
Osborne, Matthew wrote:
Sorry I forgot to note the version. I have been using version 2.0.
However, I just realized that version 2.0 only allows for artifacts to
come from a central repository, and gives no leeway whatsoever with how
the dependencies are named (eg artifactname-1.0.jar must have the
version number in the filename no matter what). So I may have to use
version 1.0, btu I haven't decided for sure yet
Matt Osborne
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
