[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [tycho-dev] property to control usage of locally installed artifacts
|
It's not Import-Package as much as widespread use of version ranges that
make it is more like for Tycho pick up locally installed artifacts.
--
Regards,
Igor
On 12-08-22 3:12 AM, Sievers, Jan wrote:
regarding https://bugs.eclipse.org/bugs/show_bug.cgi?id=355367
take a look at my new patchset
https://git.eclipse.org/r/#/c/7325/
which provides access to reactor-global properties from CLI and settings.xml only.
Regarding the general point that the user may want control about usage of locally installed SNAPSHOTS/releases separate from the rest of the local repo:
This is not possible as of maven 3.0.x and I agree support for this should be in maven core.
IIRC tesla tried to adress this with the "split local repo" (local snapshots, local releases, remote snapshots, remote releases in different root folders) .
As a user I simply don't want to pay the price of deleting my whole local repo/using a temp one every time just to make sure I'm only using remote artifacts.
With p2 and Import-Package, the problem is augmented with a higher probability to inadvertently use a locally installed artifact providing the package instead of a remote one. We have various reports of users which complain about the "builds on my PC" effect this causes as they keep working on the same local repo with "mvn clean install" all the time and aggregate lots of locally installed p2 artifacts that may go into any tycho build on their local machine.
So IMHO as long as maven core does not allow to control the usage of locally installed artifacts, we can provide a workaround in tycho.
Regards,
Jan
_______________________________________________
tycho-dev mailing list
tycho-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-dev
