[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [tycho-user] [WARNING] The following locally built units have been used to resolve project dependencies
|
Reactor projects are expected to "mask" locally installed artifacts and
artifacts available from remote repositories. I believe the warning
is only printed for project dependencies installed locally by other builds.
Generally, though, when you run "mvn install", you explicitly tell Maven
to share build results in the local repository. If you don't want to
share the build results, then you run "mvn package". If you want to
share results among some builds but not others, you use separate local
repositories. This is how Maven has worked since at least 2.0 and there
is no reason Tycho should deviate from this. There are some talks among
Maven developers to separate "remote artifact cache" from "locally
installed artifacts" and we may want to implement something similar in
Tycho, but I am not sure if and when this is going to happen.
--
Regards,
Igor
On 12-01-09 6:23 PM, Matthew O'Connor wrote:
Would it be possible for Tycho - when the dependency is in the current
reactor build and in your local Maven repository - to prefer the
components in the current build to alleviate this problem?
Or is the concern that this will preclude Tycho's use of cached
artifacts from previous builds?
Thanks,
Matt
On Wed, Dec 14, 2011 at 3:18 AM, Oberlies, Tobias
<tobias.oberlies@xxxxxxx <mailto:tobias.oberlies@xxxxxxx>> wrote:
Yes, this would prevent cross-talk between the different builds, and
is probably what you want.
Regards
Tobias
> -----Original Message-----
> From: tycho-user-bounces@xxxxxxxxxxx
<mailto:tycho-user-bounces@xxxxxxxxxxx> [mailto:tycho-user-
<mailto:tycho-user->
> bounces@xxxxxxxxxxx <mailto:bounces@xxxxxxxxxxx>] On Behalf Of
motes motes
> Sent: Freitag, 9. Dezember 2011 14:57
> To: Tycho user list
> Subject: Re: [tycho-user] [WARNING] The following locally built
units have
> been used to resolve project dependencies
>
> Could a solution for this problem be to enable "Use private Maven
> repository" on jenkins/hudson? This way tags could be build through
> hudson without other jobs updating the local m2 artifacts.
>
>
>
> On Fri, Oct 14, 2011 at 1:06 PM, Oberlies, Tobias
> <tobias.oberlies@xxxxxxx <mailto:tobias.oberlies@xxxxxxx>> wrote:
> > Sorry, but no. It is never safe to ignore this warning, because the
> build result may depend on the non-reproducible context of your local
> machine.
> > In your particular case, i.e. a warning about what is just
being built,
> it could in fact be safe, but in order to decide this you need to
know
> what install builds you have done on your local machine and what
effect
> these builds have.
> >
> > The feature that locally built content is always part of every
target
> platform can be useful, but it is quite advanced and potentially
dangerous
> so I personally would prefer to have it switched off by default:
> https://bugs.eclipse.org/bugs/show_bug.cgi?id=355367
> >
> > Regards
> > Tobias
> >
> >> -----Original Message-----
> >> From: tycho-user-bounces@xxxxxxxxxxx
<mailto:tycho-user-bounces@xxxxxxxxxxx> [mailto:tycho-user-
<mailto:tycho-user->
> >> bounces@xxxxxxxxxxx <mailto:bounces@xxxxxxxxxxx>] On Behalf Of
motes motes
> >> Sent: Mittwoch, 12. Oktober 2011 14:36
> >> To: Tycho user list
> >> Subject: Re: [tycho-user] [WARNING] The following locally
built units
> have
> >> been used to resolve project dependencies
> >>
> >> All projects in trunk have SNAPSHOT (pom.xml) and qualifiers
> >> (MANIFEST.mf) as version suffix. But I also need to be able
to check
> >> out the code from tag and build a released project (does not have
> >> SNAPSHOT/qualifier since its release code). Since this codes
does not
> >> change it should be safe to ignore the warning in this context
right?
> >>
> >>
> >>
> >> On Mon, Oct 10, 2011 at 2:09 PM, Oberlies, Tobias
> >> <tobias.oberlies@xxxxxxx <mailto:tobias.oberlies@xxxxxxx>> wrote:
> >> > You may get this warning in case you are building artifacts
which you
> >> have built with mvn clean install before, and these artifacts have
> exactly
> >> the same version.
> >> >
> >> > I would strongly encourage to avoid these re-builds without
version
> >> change, because they don't work and may give surprising
results. For
> the
> >> p2 metadata, Tycho does as you propose: it just uses what you are
> >> currently building and ignores what is available in the local
Maven
> >> repository. However, for p2 artifacts, this is not
implemented, which
> >> means that Tycho (or p2 underneath) may use the artifact from your
> >> previous mvn clean install.
> >> >
> >> > Your options are:
> >> > - Clear the .meta/p2-artifacts.properties, and only build
with mvn
> clean
> >> verify therearfter
> >> > - Use an automatic qualifier, i.e. append ".qualifier" to
the Eclipse
> >> versions (and -SNAPSHOT to the Maven versions)
> >> >
> >> > Regards
> >> > Tobias
> >> >
> >> >> -----Original Message-----
> >> >> From: tycho-user-bounces@xxxxxxxxxxx
<mailto:tycho-user-bounces@xxxxxxxxxxx> [mailto:tycho-user-
<mailto:tycho-user->
> >> >> bounces@xxxxxxxxxxx <mailto:bounces@xxxxxxxxxxx>] On Behalf
Of motes motes
> >> >> Sent: Montag, 10. Oktober 2011 11:50
> >> >> To: Tycho user list
> >> >> Subject: [tycho-user] [WARNING] The following locally built
units
> have
> >> >> been used to resolve project dependencies
> >> >>
> >> >> When I build my multi-module project I get this warning:
> >> >>
> >> >> [WARNING] The following locally built units have been used to
> resolve
> >> >> project dependencies
> >> >> ...
> >> >>
> >> >> and then a list of all my bundles/features are written.
Does this
> mean
> >> >> that it uses the previously build jars from the local maven m2
> >> >> repository?
> >> >>
> >> >> All the dependencies that are listed are actually part of
the same
> >> >> project (with a master parent pom) so why does it not use
those to
> >> >> resolve the project dependencies?
> >> >> _______________________________________________
> >> >> tycho-user mailing list
> >> >> tycho-user@xxxxxxxxxxx <mailto:tycho-user@xxxxxxxxxxx>
> >> >> https://dev.eclipse.org/mailman/listinfo/tycho-user
> >> > _______________________________________________
> >> > tycho-user mailing list
> >> > tycho-user@xxxxxxxxxxx <mailto:tycho-user@xxxxxxxxxxx>
> >> > https://dev.eclipse.org/mailman/listinfo/tycho-user
> >> >
> >> _______________________________________________
> >> tycho-user mailing list
> >> tycho-user@xxxxxxxxxxx <mailto:tycho-user@xxxxxxxxxxx>
> >> https://dev.eclipse.org/mailman/listinfo/tycho-user
> > _______________________________________________
> > tycho-user mailing list
> > tycho-user@xxxxxxxxxxx <mailto:tycho-user@xxxxxxxxxxx>
> > https://dev.eclipse.org/mailman/listinfo/tycho-user
> _______________________________________________
> tycho-user mailing list
> tycho-user@xxxxxxxxxxx <mailto:tycho-user@xxxxxxxxxxx>
> https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx <mailto:tycho-user@xxxxxxxxxxx>
https://dev.eclipse.org/mailman/listinfo/tycho-user
_______________________________________________
tycho-user mailing list
tycho-user@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/tycho-user
