Locally built artifacts
Just like in a normal Maven build, a Tycho build can use artifacts that
have been built locally and installed (e.g. withmvn clean install) into
the local Maven repository. In terms of the target platform, this means
that these artifacts are implicitly added to the target platform. This
is for example useful if you want to rebuild a part of a Tycho reactor,
or if you want to build against a locally built, newer version of an
upstream project.
There are the following options to disable this feature:
* Setting the CLI option-Dtycho.localArtifacts=ignoreexcludes locally
built artifacts in one build. (tycho.localArtifacts=ignoremay also
be configured in thesettings.xml; in this case, the default
behaviour can be temporarily re-enabled with the CLI
option-Dtycho.localArtifacts=default. Since Tycho 0.16.0.)
* Deleting~/.m2/repository/.meta/p2-local-metadata.propertiesresets
Tycho's list of locally build artifacts, and therefore these
artifacts will not be added to target platforms (unless, of course,
the artifacts are installed again).
Le 01/02/2013 16:01, Max Rydahl Andersen a écrit :
Hey,
We talked about this 'sideeffect' in tycho where you see things like:
[WARNING] The following locally built units have been used to resolve project
dependencies:
[WARNING] org.jboss.tools.common.text.ext/3.4.0.Beta2-v20121028-1355
[WARNING] org.jboss.tools.usage/1.2.0.Beta2-v20121028-1355
[WARNING] org.jboss.tools.common.el.ui/3.4.0.Beta2-v20121028-1355
[WARNING] org.jboss.tools.common.el.core/3.4.0.Beta2-v20121028-1355
Even when I got a repository with even newer bits on it.
Was there a flag for tycho to make it choose the latest instead or somehow ignore my
local built ones ?
(even better I would like to just remove all local built stuff without having to
guess/list all the names)
/max
_______________________________________________
jbosstools-dev mailing list
jbosstools-dev(a)lists.jboss.org
https://lists.jboss.org/mailman/listinfo/jbosstools-dev