[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
RE: [orbit-dev] Feature projects for Orbit bundles?
|
Thanks Jeff,
I'm understanding better now, though not fully
yet.
For one, your answer means that our build needs more
modifications than expected.
We didn't use the PDE packager up to now, but packaged from
the features we built
ourselves. Looks like in the future, we'll have to use the
packager.
Second, I believe that the step of downloading the bundles
needs to be automated
somehow, with support from PDE build. Asking the build
master to manually download
and unzip the bundles into the "base location" is not good
enough. Well, perhaps
Buckminster can help here eventually.
Third, if our project is the one who's contributing the
bundles we're in a special situation
and not only consuming them.
Since we are the ones providing the update site, and the
features. I mentioned earlier already that I found it a bit
awkward that the feature and
the bundle is so totally separate, in separate
repositories.
I think I do start getting your point, though. Perhaps we
can clarify finally in tomorrow's
call.
Thanks,
--
Martin
Oberhuber
Wind River Systems, Inc.
Target Management Project Lead, DSDP
PMC Member
http://www.eclipse.org/dsdp/tm
Martin,
This should just work. The Eclipse project gets
(well, will get when we have a chance) its third party stuff from the
pre-built Orbit bits. As minimim it should be as easy as downloading and
unzipping the Orbit zip over the Eclipse base against which you are building
(I assume you don't recompile all of Eclipse). The separate packaging
phase of PDE build will simply get the plugins needed whether they are freshly
compiled or were prebuilt and put them in zips, update sites, whatever.
In a certain sense the point is aesthetic
but I think it is important. You are getting libs from a third party and
have no control over them. What would you do if they started coming as
bundles? Would not rebuild them? Orbit would not. We would
host them somewhere for others to consume. It is more consistent with
the intent, philosophy and reality of Orbit and our consumption of external
code to simply get the prebuilt parts and include them in your
offerings.
Jeff
"Oberhuber, Martin"
<Martin.Oberhuber@xxxxxxxxxxxxx> Sent by: orbit-dev-bounces@xxxxxxxxxxx
01/02/2007 06:00 AM
Please respond
to Orbit Developer discussion
<orbit-dev@xxxxxxxxxxx> |
|
To
| "Orbit Developer discussion"
<orbit-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
| RE: [orbit-dev] Feature projects
for Orbit bundles? |
|
Hi Jeff,
I don't understand this, can you
elaborate?
- My build is supposed to create
features and plugins of orbit-bundles for the update site, since orbit is
not doing an update site itself. So, when I'm only compiling against
prebuilt orbit bundles from a base location, how should I package these for
the update site?
- My build is supposed to create
downloadable ZIPs that include everything needed for TM. Same question, how
would I put Orbit bundles into those zips when I build against something in
a base location?
My
existing build does both these actions properly already. I cannot see why I
should change it. For me, the only difference is that the cvs repository
location is different.
Cheers,
--
Martin Oberhuber
Wind River Systems,
Inc.
Target Management Project Lead, DSDP PMC Member
http://www.eclipse.org/dsdp/tm
From: orbit-dev-bounces@xxxxxxxxxxx
[mailto:orbit-dev-bounces@xxxxxxxxxxx] On Behalf Of Jeff
McAffer
Sent: Friday, December 22, 2006 4:42 PM
To: Orbit
Developer discussion
Subject: Re: [orbit-dev] Feature projects for
Orbit bundles?
Just to be clear, you should be grabbing the *built* versions from
Orbit not grabbing the source and rebuilding. It is true that the build
for these bundles is trivial but the principle is that we consume these as
though the library originator was producing bundles. PDE build has
facilities for defining a "base location" that contains prebuilt pieces for
you to build with. I suggest that people add the Orbit bundles to that
as they would the Eclipse platform etc.
Jeff
Martin Oberhuber
<martin.oberhuber@xxxxxxxxxxxxx> Sent by:
orbit-dev-bounces@xxxxxxxxxxx
12/21/2006 03:14 AM
Please respond
to Orbit Developer discussion
<orbit-dev@xxxxxxxxxxx> |
|
To
| Orbit Developer
discussion <orbit-dev@xxxxxxxxxxx>
|
cc
|
|
Subject
| Re: [orbit-dev] Feature projects
for Orbit bundles? |
|
Ok,
so I'm going to keep my
existing build process and serve the features
out of my project repository
but grab the bundle source from the
Orbit repository.
That makes
migration really simple.
Thanks!
Martin
Jeff McAffer
schrieb:
>
> This was discussed at the first conf call.
Search for "update" in the
> minutes
>
http://www.eclipse.org/orbit/documents/minutes-061024.php
>
> In
particular,
> Conclusion: For now we will
create a download site that
> includes individual JARs as well as one
zip of all bundles.
>
> Some of the reasoning is captured in the
minutes. Basically, Orbit is
> a place not a thing. Orbit
itself will not "release" and as such will
> not technically be part of
Europa. The bundles produced by Orbit will
> however be consumed
by projects that are part of Europa and will
> therefore be included in
their offerings (zips, update sites, ...).
> Basically Orbit is a
place to do the bundling work you would have
> done anyway in your
project. Everything else from the IP process to
> how you deliver
your project remains unchanged.
>
> This may evolve over time but
for now we decided not to create
> features and update
sites.
>
> Jeff
>
>
>
>
>
*"Oberhuber, Martin" <Martin.Oberhuber@xxxxxxxxxxxxx>*
> Sent by:
orbit-dev-bounces@xxxxxxxxxxx
>
> 12/20/2006 02:49 PM
>
Please respond to
> Orbit Developer discussion
<orbit-dev@xxxxxxxxxxx>
>
>
>
> To
>
"Orbit Developer discussion"
<orbit-dev@xxxxxxxxxxx>
> cc
>
> Subject
>
[orbit-dev] Feature projects
for Orbit bundles?
>
>
>
>
>
>
>
>
>
> Hi all,
>
>
I'm sorry if this was discussed previously, but I looked
> throught the
Wiki and mailing list and didn't find an
> answer.
>
> I was
about to start populating the Europa site with the
> Target Management
bits, and I intended to move the
> org.apache stuff we have into Orbit
before doing so.
>
> But when browsing the Orbit repository, I
noticed that
> there are not feature projects whatsoever. Which
would
> mean that on an Update Site it is unclear how the
bundles
> are presented, licensing info is missing, and the
Apache
> License is broken (which requireds the string "This
>
product includes software developed by the Apache
> Software Foundation"
in a prominent place like the About
> Dialog or the Docs, which I'm
doing by means of a
> feature right now.
>
> So -- what is
the plan?
> * I currently have 2 feature projects.
> -
Should I move them into Orbit along with the bundles?
> - Or will
the Orbit Build generate features autmomatically
> at some
time?
>
> * For now, should I populate Europa with bundles from
Orbit
> but Features from my Repository? That seems
awkward.
>
> * What are others doing wrt Europa? Is the Orbit
Repository
> just a copy of the bundles for now, while the real
stuff
> for Europa still comes from the Project's own
repositories?
>
> Thanks for any hints,
> Martin
>
--
> Martin Oberhuber
> Wind River Systems, Inc.
> Target
Management Project Lead, DSDP PMC Member
>
http://www.eclipse.org/dsdp/tm
>
_______________________________________________
> orbit-dev mailing
list
> orbit-dev@xxxxxxxxxxx
>
https://dev.eclipse.org/mailman/listinfo/orbit-dev
>
>
------------------------------------------------------------------------
>
>
_______________________________________________
> orbit-dev mailing
list
> orbit-dev@xxxxxxxxxxx
>
https://dev.eclipse.org/mailman/listinfo/orbit-dev
>
--
Martin Oberhuber
Wind River Systems, Inc.
Target
Management Project Lead, DSDP PMC
Member
http://www.eclipse.org/dsdp/tm
_______________________________________________
orbit-dev
mailing
list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev
_______________________________________________
orbit-dev mailing
list
orbit-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/orbit-dev