Re: [cbi-dev] Bug 398201 - [CBI] Issues with org.eclipse.osgi (3.9?) and

[David M Williams <david_williams@xxxxxxxxxx>]

Thanks for the pointers. I'll try the first
one now. For the last one, I have opened 

Bug 398440
- [CBI] Eclipse builds are not cycle free 

For the middle one, I'll have to read
up on it to understand what you are saying :) 

For the cycles, I assume you are saying
that makes the build "indeterminate"? I know for PDE builds,
it would simply take the "old" version if it was already in the
target, but I'd think someone would have notice that in the test builds?


Thanks again, 





From:      
 "Sievers, Jan"
<jan.sievers@xxxxxxx>
To:      
 Common-build Developers
discussion <cbi-dev@xxxxxxxxxxx>, 
Date:      
 01/17/2013 04:55 AM
Subject:    
   Re: [cbi-dev]
Bug 398201 - [CBI] Issues with org.eclipse.osgi (3.9?) and org.eclipse.equinox.ip
in N builds
Sent by:    
   cbi-dev-bounces@xxxxxxxxxxx

---

> warning: 'includeantruntime' was not set, defaulting
to build.sysclasspath=last; set to false for repeatable builds 

this looks like it's from ant; we would need more context (links to full
logs) to be able explain what this means and how to get rid of the warning.
Maybe Krzysztof can chime in here.

>Any one have any pointers to how to make your builds more reliable
and repeatable? 

One thing I can recommend is to set property tycho.localArtifacts=ignore
[1] for full builds.

Maven has the behaviour to include artifacts installed into the local repo
by previous builds into the dependency resolution space.
While this is required for partial rebuilds of multi-module builds, it
may cause unexpected locally installed versions of artifacts being picked
by the p2 resolver.
Set this property on the commandline (-Dtycho.localArtifacts=ignore) or
globally in settings.xml so that artifacts installed into the local repo
are not considered by the p2 resolver.

Also, if you want more precise control over the binary target platform,
using a PDE target file will let you pick which IUs from which repo you
want to be visible to the build [2].
Just adding the whole p2 repo in pom.xml will make any IU in that repo
available to the build which may not be what you want.

Another thing, I have some doubts whether the eclipse platform build is
currently cycle-free in the sense that there are artifacts being built
from source but there are also older versions of the same artifact in the
target platform.  Example:

org.eclipse.equinox.concurrent is being built in the platfrom build http://git.eclipse.org/c/equinox/rt.equinox.bundles.git/tree/bundles
, but it's also referenced binary in http://git.eclipse.org/c/platform/eclipse.platform.releng.aggregator.git/tree/eclipse-parent/pom.xml?h=R4_2_maintenance
as apart of the ECF p2 repo 
http://download.eclipse.org/rt/ecf/3.5.6/site.p2

This is something tycho can't fix and I wonder if there is a bug open in
CBI for this?

Regards,
Jan

[1] http://wiki.eclipse.org/Tycho/Release_Notes/0.16
[2] http://wiki.eclipse.org/Tycho/Target_Platform#Target_platform_configuration






From: cbi-dev-bounces@xxxxxxxxxxx [mailto:cbi-dev-bounces@xxxxxxxxxxx]
On Behalf Of David M Williams
Sent: Donnerstag, 17. Januar 2013 07:39
To: Common-build Developers discussion
Subject: Re: [cbi-dev] Bug 398201 - [CBI] Issues with org.eclipse.osgi
(3.9?) and org.eclipse.equinox.ip in N builds

Besides solving this specific issue, I'd appreciate any quick tips on how
to make builds more repeatable .... across machines, environments, etc.
For one example, occasionally I see messages in the log that says 

warning: 'includeantruntime' was not set, defaulting to build.sysclasspath=last;
set to false for repeatable builds 

What? 

I've also heard people say things like "yeah, sometimes if things
act funny I have wipe out my local repos and start fresh and then its ok".
That's certainly understandable for the phase we (Platform) are in, but
is that a common practice? Any one have any pointers to how to make your
builds more reliable and repeatable? 

Thanks, 





From:        Thanh Ha <thanh.ha@xxxxxxxxxxx>
To:        Common-build Developers discussion <cbi-dev@xxxxxxxxxxx>,
Date:        01/16/2013 09:51 PM 
Subject:        [cbi-dev] Bug 398201 - [CBI] Issues
with org.eclipse.osgi (3.9?) and org.eclipse.equinox.ip in N builds 
Sent by:        cbi-dev-bounces@xxxxxxxxxxx 
________________________________________



Hi Everyone,

I'm a little stumped on Bug 398201 [1] an was hoping maybe someone on this
list might have any ideas.

What's strange about this issue is that when I run this same build on my
laptop it works just fine. I'm using maven 3.0.4 and Oracle JDK 1.6 (also
tried 1.7). Strangely when building on build.eclipse.org we encounter the
issue described in Bug 398201. It seems to have issues resolving 2 packages:

[ERROR] Bundle org.eclipse.equinox.ip - Missing Constraint: Import-Package:
javax.servlet; version="2.1.0"
[ERROR] Bundle org.eclipse.equinox.ip - Missing Constraint: Import-Package:
javax.servlet.http; version="2.1.0"


I've even tried copying over my JDK from my laptop to build.eclipse.org
but the failure persists. The fact that it works on my laptop but not on
build.eclipse.org makes me suspect environment but other than maven and
JDK I'm not sure what else could be different.


Thanh

[1] https://bugs.eclipse.org/bugs/show_bug.cgi?id=398201
_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cbi-dev
_______________________________________________
cbi-dev mailing list
cbi-dev@xxxxxxxxxxx
http://dev.eclipse.org/mailman/listinfo/cbi-dev