| [m2e-users] Version ranges, resolving workspace projects |
|
When using maven 3.0.3 in M2E version ranges works to some extent
and is sufficient for our needs. However how it resolves snapshots when taking into account projects in your workspace I think could be better. For some reason in Maven 3 you cannot setup non-unique snapshots. Snapshots installed/deployed always have a timestamp attached to the artifact name regardless if you specify in distribution management that the snapshot repo should create <uniqeVersion>false</uniqueVersion> So... I have a project "A" in my workspace at version 1.0.0-SNAPSHOT I have another project "B" in my workspace that depends on project "A" [1.0.0-SNAPSHOT,2.0.0-SNAPSHOT) M2E correctly gives me project "A" as a dependency for project "B" However, if I install/deploy project "A" then M2E will always give me the timestamped version of project "A" as a dependency for project "B". I believe it should continue to give you the SNAPSHOT version from your workspace, since if I make code changes to project "A" I have to keep installing it so project "B" picks up the latest. Your thoughts anyone? --
Paul French Kirona Solutions Ltd Tel: 07803 122 058 E-Mail: paul.french@xxxxxxxxxx Web: www.kirona.com
This email and any attachments are confidential and should only
be read by those to whom they are addressed. If you are not the
intended recipient, please contact us on 01625 585511, delete
the email (including any attachment) from your computer and
destroy any copies. Any distribution or copying without our
prior permission is prohibited.
Internet communications are not always secure and may be subject
to delays, non-delivery and unauthorised alterations. Therefore,
information expressed in this message is not given or endorsed
by Kirona Solutions Limited ("Kirona") unless otherwise notified
by our duly authorised representative independent of this
message. No warranty is given that this email (including any
attachment) is virus free. Any views or opinions presented are
solely those of the author and do not necessarily represent
those of Kirona.
|