Re: [orbit-dev] EBR / Recipes Update

["David M Williams" <david_williams@xxxxxxxxxx>]

Doug, according to the aggregator build
log, it is coming from your repository, and, I checked, and can easily
see it in 
..../tools/cdt/builds/neon/milestones/m5

So ... are you asking us how your build
works? :) 





From:      
 Doug Schaefer <cdtdoug@xxxxxxxxx>
To:      
 Orbit Developer discussion
<orbit-dev@xxxxxxxxxxx>, 
Date:      
 02/20/2016 01:20 PM
Subject:    
   Re: [orbit-dev]
EBR / Recipes Update
Sent by:    
   orbit-dev-bounces@xxxxxxxxxxx

---

I see we are actually re-exporting it through the CDT
repo via our category.xml file. Just seemed odd I guess.

On Sat, Feb 20, 2016 at 1:14 PM, Doug Schaefer <cdtdoug@xxxxxxxxx>
wrote:
I'm going through a bunch of clean up today with CDT builds
et al. One thing I'm lost on, and I guess I haven't had to deal with it
with CDT before, but how does all this get into the simrel repo? We've
started depending on org.freemarker and it seems to get into the simrel
repo. Maybe someone else is doing it for us. What is the recommended practice?

Sorry for the newbie question from one of the old guys.
Doug.

On Fri, Feb 19, 2016 at 2:27 PM, David M Williams <david_williams@xxxxxxxxxx>
wrote:
This sounds like some good work, Gunnar.
I hope to take a closer look soon, but thought in parallel I would ask
some questions. 

Does it literally have to be "one at a time"? I am think about
when several packages that "go together" (such as Lucene). 

I assume that when a bundle has some prereqs, those are still resolved
from our current repositories? And that would be how we would 
know a bundle was "completely" in Orbit. 

None of this excludes the concept of having I-builds, S-builds and eventually
R-builds, right? I would assume the "tiny repos" would be mirrored
into the larger repos? 
That is, we can still "increment" towards the final R-build repository,
instead of everything going in the R-build, even if it was wrong the first
build or two? 
[I ask since R-builds are forever ... where as we I-builds and S-builds
are temporary.] 

I assume "moving to the new system" does not depend on this being
done first, right? Though, it would be nice. 
Any outlook on when this work would be done? (Does it eventually belong
in Tycho?) 

I think the thing that is blocking us now is having a place at Eclipse.org
for the original artifacts to live. 
Any progress or word on setting up an "original artifact database"?
(Instead of pulling things live from maven. central). 

Thanks for letting us know the current state of things. 





From:        Gunnar
Wagenknecht <gunnar@xxxxxxxxxxxxxxx>
To:        Orbit
Developer discussion <orbit-dev@xxxxxxxxxxx>,
Cc:        Discussion
channel for EBR developers and recipe contributors <ebr-dev@xxxxxxxxxxx>
Date:        02/18/2016
08:48 AM
Subject:        [orbit-dev]
EBR / Recipes Update
Sent by:        orbit-dev-bounces@xxxxxxxxxxx

---

FYI,

I've started to try something different for how the p2 repository is generated.
Instead of using a feature and aggregating every recipe into a giant p2
repository, I wanted to explore the possibility of creating individual,
small p2 repository just containing a single recipe bundle (and its source
bundle).

It seems that all this is possible in a single reactor with EBR and Tycho.
After the bundle was generated by bnd I called into some Tycho code to
contribute the bundle to dependency resolution and the target platform.
As a result, I able to extend a mojo in the tycho-p2-repository-plugin
to create a p2 repository.

If you want to try this, you can consume the Maven plugin from a branch:
https://github.com/eclipse/ebr/tree/dev/tycho_extras_plugin/releng/maven-plugins/ebr-tycho-extras-plugin

- build it locally and install into the local repository
- update Tycho version used in your recipes to Tycho 0.25.0-SNAPSHOT

For the Orbit build this opens a create opportunity to just build modified
recipes - and not having to build all the recipes all the time.

The code is still in a branch because it needs some review and cleanup.
It's really just a prototype. 

-Gunnar

-- 
Gunnar Wagenknecht
gunnar@xxxxxxxxxxxxxxx,
http://guw.io/






_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/orbit-dev




_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/orbit-dev

_______________________________________________
orbit-dev mailing list
orbit-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/orbit-dev