Hi David
Eclipse SOA's JWT project here...
Obviously we'd want to stay in the Kepler release train !!
I guess for that we'd have to get your "green" build, solve whatever
problems JWT has with it, make our own build work, and then put back
enabled="true" in jwt.b3aggrcon in the simrel git project (*), am I
right ?
And what deadline would there be for that ? (ASAP I suppose, but you
know this period of the year...)
I'm putting our release engineer Chris in cc.
And thanks to Mickael for pointing that out !
Regards,
Marc Dutoo
Eclipse JWT co-lead
Open Wide
(*)
http://wiki.eclipse.org/Simrel/Contributing_to_Simrel_Aggregation_Build
-------- Original Message --------
We finally got a green build!
Though, I did have to disable a few things, either there was a
conflict, such as for ICU4J v50 vs 4.2, and many others
because something else was disabled.
There's the current status of
enabled flag:
Whole contribution disabled ...
never enabled for Kepler. I'll remove these if I don't hear
something soon.
emf-query2.b3aggrcon -
org.eclipse.simrel.build
jwt.b3aggrcon -
org.eclipse.simrel.build
These have a feature or
repository disabled, some disabled by "owners", since they
knew they needed some work still, and a few disabled by me,
based on what I could see using the b3 aggregator editor's
"validate aggregation" function. Feel free to re-enable
if/when you think ready.
amp.b3aggrcon -
org.eclipse.simrel.build
birt.b3aggrcon -
org.eclipse.simrel.build
dltk.b3aggrcon -
org.eclipse.simrel.build (2 matches)
egit.b3aggrcon -
org.eclipse.simrel.build
gmp-gmf-tooling.b3aggrcon -
org.eclipse.simrel.build (2 matches)
mat.b3aggrcon -
org.eclipse.simrel.build
mdt-papyrus.b3aggrcon -
org.eclipse.simrel.build
mmt-qvto.b3aggrcon -
org.eclipse.simrel.build
soa-bpel.b3aggrcon -
org.eclipse.simrel.build
webtools.b3aggrcon -
org.eclipse.simrel.build
I've promoted what we had from
this first green build to .../releases/staging.
Don't forget to check the
reports occasionally:
http://build.eclipse.org/simrel/kepler/reporeports/
Thanks,
|
