Hi,
I think it would also make a lot of sense to ship WindowBuilder (at
least SWT Designer) in the RCP/Plugin developer EPP package, if it
is not already planed and if it is not too late.
My 2c.
Le 22/04/2011 12:54, Mark Russell a écrit :
HI David:
I'm the build person for the WindowBuilder component. In
your email you said:
In fact, what is the status of WindowBuilder? I've heard
rumors they would like to be part of the Java EPP package, but
don't recall seeing a bugzilla open there to discuss, and
initiate the work required to make that happen, so ... did I
miss it?
I'm new to this release train and was wondering what I had
to do to be part of the Jave EPP package? Can you point me to
some documentation or describe the process?
On Thu, Apr 21, 2011 at 3:21 PM, David
M Williams <david_williams@xxxxxxxxxx>
wrote:
What ... M7 status already?!
Yeah, it is a little early, but there are a few timely
reminders and early issues.
First, I have promoted a warmup staging repo with
everything that's been updated since M6.
http://download.eclipse.org/releases/staging/
One of the big ones updated is WindowBuilder ... try it
out. I haven't yet, so hope the WindowBuilder team is
really ready? I just saw the contribution file change
and the aggregation build still worked.
In fact, what is the status of WindowBuilder? I've heard
rumors they would like to be part of the Java EPP
package, but don't recall seeing a bugzilla open there
to discuss, and initiate the work required to make that
happen, so ... did I miss it?
[I'm partially asking openly, here on cross-project, to
emphasize that one thing that's really important for the
Simultaneous Release is lots of communication, so
everyone knows what's going on ... even if key players
already know, or it "seems obvious" to some, it's often
not so obvious to others. And, who know, maybe they were
only rumors and not really, or no longer, true?]
The second "early issue": there's several features or
repositories that (still) have enabled="false". I
don't recall any history about a few of them, so will
ask here in case I've missed something. But, if I don't
hear anything soon, I'll assume they should be removed
from aggregation. Apologies if this was all explained to
me before and I've forgotten.
dsdp-sequoyah.b3aggrcon (2 features disabled: org.eclipse.sequoyah.device.examples.feature
and org.eclipse.sequoyah.vnc.protocol.examples.feature)
emft-eef.b3aggrcon (here, whole repo/contribution is
disabled)
gmp-gmf-tooling.b3aggrcon (I do recall this one ...
Anthony's said before it should be removed, so I will).
Third, I suggest the Platform contribute a "warm up"
repository early next week, before their final
contribution on +0 day on Friday (4/29). While that will
likely "break the build" (for a few, dependent projects)
it is an easy way to get an early indication of
problems, that projects might need to react to, so there
is more time to react, and not such a ripple effect the
following week (5/2 to 5/4) when everyone is
contributing everything final for M7. It does help
others contribute "warm-up" deliveries, so they can
sanity check things before their final contribution.
Thanks everyone ... everything has been going well this
release, and I'm sure it'll be an easy few weeks leading
up to a solid M7!
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
--
Mark R Russell
(724) 473-3140
Release Engineer
Google Pittsburgh
_______________________________________________
cross-project-issues-dev mailing list
cross-project-issues-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/cross-project-issues-dev
--
Mickael Istria
R&D Engineer
Best
Eclipse Modeling Tool 2011
This message and any attachment (the "message")
is intended solely for
the addressees and is confidential. If you receive this
message by
mistake, please delete it and notify the sender immediately.
Any use
not in accordance with its purpose, any out-spread or
disclosure,
either as a whole or partially, is prohibited except with
formal
approval. Internet cannot guarantee the integrity of this
message,
therefore BonitaSoft will not be liable for the message if
modified.
|
