Hi,
bad news from the modeling package.
The CDO team introduced, by mistake, a new action only meaningfull
in debug scenarios : "EFS TEST". Any end user clicking it ends up
with an Eclipse which get stuck for about one minute and ends up
with timeout errors. It is contributed in every perspective.
It has been introduced in CDO very late (2012-06-12) explaining how
we missed it before RC4.
I don't think this would qualify as a ship-stop bug, but it is quite
bad from a modeling package point of view.
I see two feasable options, maybe three:
1 - removing the CDO contribution from the package and rebuilding
the modeling package (we can even use the very same update-site used
to build the RC4 packages as we won't depend on some changes in the
Juno repository). I did commit the disablement of CDO
(05290c9852f9d7ac21e240b0aedc01560e5fdb52) . Using the discovery UI
we will be able to make CDO installable from an update-site
containing a fixed build, without impacting the Juno one.
2 - live with it, but as I said before the result is quite bad, so
if you feel option 1 is doable that would be great!
3 - any plugin_customization magic ? in any case It would require
the package to be rebuilt so I feel option 1 would be safer.
Can we do something ? any opinion ?
Cédric
Bug tracked on the CDO project :
https://bugs.eclipse.org/bugs/show_bug.cgi?id=383063
Le 14/06/2012 22:28, Markus Knauer a écrit :
Hi package maintainers,
now we've got a build available that I think could be the final
RC4 build:
http://build.eclipse.org/technology/epp/epp_build/juno/download/20120614-1725/
Upgrades etc. can be tested with the RC4 p2 repositories at
http://build.eclipse.org/technology/epp/epp_build/juno/download/20120614-1725/repository
and
http://download.eclipse.org/releases/staging
There are some 'special' things that I should mention:
(1) Bug 382574
- An internal error occurred
during: "Indexing help...".
The workaround that we came up with includes adding a new Java
property to the eclipse.ini file. With this property set, the
search in the Eclipse Help system should work even in case someone
installs the higher version of the Apache Lucene library from the
Juno repository at a later time. But it is important that you test
the search in your package to make sure there are no bad side
effects.
(2) There won't be the usual 'release' of the packages from eclipse.org/downloads
tomorrow/Friday. RC4 has always been a 'quiet' release. If you
send your +1's these packages will be the final ones that will be
released on June 27th.
Huh, it's going to be a longer list... I hate such lists... :)
(3) Test the packages... if you find errors, try to find a
workaround and document it. If you find a stop-ship bug, well, in
that case we need to find a solution. In most cases this means
that we need to rebuild (and test!) all packages again.
(4) Test the packages early... and send your vote to the list as
usual. I'd like to push them to the Eclipse mirror servers
beginning of next week to give them enough time to sync. And
before doing so, I need your votes...
Good, I'll stop for now...
Thanks,
Markus
_______________________________________________
epp-dev mailing list
epp-dev@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/epp-dev
|
