4:01 p.m.
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
4:12 p.m.
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
12:14 a.m.
Thats interesting and a bit surprising...
Tested this key in relation to
https://issues.jboss.org/browse/JBIDE-13411 and it looks like adding to buuld command
makes build (w/o running tests) twice faster for me.
Denis
On 02/01/2013 07:12 AM, Fred Bricon wrote:
> From http://wiki.eclipse.org/Tycho/Target_Platform#Locally_built_artifacts
>
> 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. with mvn 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=ignore excludes locally built
artifacts in one build. (tycho.localArtifacts=ignore may also be configured in the
settings.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.properties resets 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
>
>
>
> _______________________________________________
> jbosstools-dev mailing list
>
> jbosstools-dev(a)lists.jboss.org
> https://lists.jboss.org/mailman/listinfo/jbosstools-dev
7:52 a.m.
> Tested this key in relation to
https://issues.jboss.org/browse/JBIDE-13411 and it looks like adding to buuld command
makes build (w/o running tests) twice faster for me.
Beware that this does not
disable local p2 cache, so if your first build
did redownload most dependencies, and the second could get them from
cache, it could be a reason why you save time, independently of
-Dtycho.localArtifacts=ignore.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
10:12 a.m.
On 02/11/2013 08:19 PM, Denis Golovin wrote:
Both those builds were taking dependencies from cache, I ams sure it
is not a reason.
It could the fact of adding local repository metadata to the
resolution
requests which makes it twice longer to compute dependencies.
Not sure we can do anything to improve that.
--
Mickael Istria
Eclipse developer at JBoss, by Red Hat <http://www.jboss.org/tools>
My blog <http://mickaelistria.wordpress.com> - My Tweets
<http://twitter.com/mickaelistria>
7:15 p.m.
There are two approaches said to work:
a) override temporarily when building, using -Dtycho.localArtifacts=ignore
b) delete ~/.m2/repository/.meta/p2-local-metadata.properties
---
Magic trick added to the wiki here:
https://community.jboss.org/wiki/HowToBuildJBossTools40WithMaven3#Verify_...
On 02/01/2013 10:01 AM, Max Rydahl Andersen wrote:
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
--
Nick Boldt :: JBoss by Red Hat
Productization Lead :: JBoss Tools & Dev Studio
http://nick.divbyzero.com
4099
days inactive
4110
days old
jbosstools-dev@lists.jboss.org
7 comments
5 participants
participants (5)
-
Denis Golovin -
Fred Bricon -
Max Rydahl Andersen -
Mickael Istria -
Nick Boldt