| Re: [ecf-dev] jms provider build |
Thanks gentlemen. The JMS build is back to green.I'll be sending out a more detailed update WRT the current status of 3.8.0 release planning today/Sunday (pacific)...but for everyone's info before that...
The latest integration release of Eclipse [1] has the restructured ECF and platform features [2]. This is a very big deal, as it gets ECF out from under the restrictions imposed by the Equinox use of the core+filetransfer plugins.
Here's the most recent build of the ECF SDK [3]. I've started testing the install (i.e. installing 3 into 1) and yesterday fixed a couple of very small things.
People on this mailing list can help out with 3.8.0 release preparation by installing some/all of the features in [3] into [1] and verify that they install correctly (by running some examples, etc). If you find problems, please open a new bug, and make bug 2a dependent upon it.
Thanks, Scott [1] http://download.eclipse.org/eclipse/downloads/drops4/I20140227-1100/ [2a] https://bugs.eclipse.org/bugs/show_bug.cgi?id=409787 [2b] https://bugs.eclipse.org/bugs/show_bug.cgi?id=429341[3] http://build.ecf-project.org/repo/C-HEAD-sdk.feature/lastSuccessful/archive/site.p2/
On 3/2/2014 6:03 AM, Markus Alexander Kuppe wrote:
On 03/02/2014 02:21 PM, Wim Jongman wrote:Pff I have been looking at this for some time. Cannot find it. I see that M. did a large update on github 4 days ago. I'm not sure if that is related. What did you change to jms?I didn't do anything. All commits are attributed to me because it's my github account that is used. It seems to me that Github has changed something on the HTTP layer that breaks Bucky. [1] fixes it. M. [1] https://github.com/ECF/JMS/commit/a187b3bd51ff25239746f55276ba7b1f15edf069 _______________________________________________ ecf-dev mailing list ecf-dev@xxxxxxxxxxx https://dev.eclipse.org/mailman/listinfo/ecf-dev