Re: [m2eclipse-user] Workspace Resolution and LATEST Tag

[Brian Towles]

Ok Thanks.... thats what i kinda figured..

I agree completely about it being a fragile practice.   Im trying to  
my steer my team to using a direct version or numbered snapshot  
practice but it is slow going.

-=Brian

On Sep 19, 2008, at 2:13 PM, Eugene Kuleshov wrote:


 Versions like LATEST and RELEASE are not supported in workspace
dependency resolver. So, there is probably no workaround for that.
 Please submit bug report for that to the project issue tracker.  
Though
it is unclear what kind of resolution rules should be applied in this
case. Eg. should workspace project resolved before any artifacts
available from all maven repositories, or should it resolve repository
artifacts and only then compare resolved version with workspace  
project?
It is also unclear how to compare snapshot versions. Please feel  
free to
post your thoughts on that on the bug report.
 On a side note, it seem like using such versions is quite fragile
practice.

 Thanks

 Eugene


Brian Towles wrote:
Howdy all

Im trying to run the m2eclipse plugin and do workspace resolution
between projects but it only seems to work when the explicit version
of the associated other projects in the workspace as defined, not
using the LATEST tag even if the latest is a SNAPSHOT.

Example

Project1 Version 1.0.1-SNAPSHOT

Project 2
<dependency>
     <groupId>Projects</groupId>
     <artifactId>Project1/artifactId>
     <version>LATEST</version>
</dependency>

This will only resolve the latest SNAPSHOT in the repository  (ie
Project1-1.0.1-20080916.190644-6) instead of resolving in the
workspace to the 1.0.1-SNAPSHOT version.

I know that latest would also resolve to the latest release, but if
the latest is a time-stamped snapshot shouldn't the m2eclipse plugin
resolve to a snapshot definition of the same version if that is the
latest in the repository?

Is there a way to get around this other then defining the explicit
snap-shot version on every project (I have 63 individual artifacts
that managing the rev for each we are trying to only do at release  
time)

Thanks

-=Brian


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

   http://xircles.codehaus.org/manage_email





-=Brian

--
Brian Towles
Application Architect
Technology Consortium, LLC
[EMAIL PROTECTED]
tel: 512.415.8105

<<inline: image.jpg>>


---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email