[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index]
Re: [ecf-dev] Neon aggregation build
- From: Scott Lewis <slewis@xxxxxxxxxxxxx>
- Date: Wed, 4 May 2016 11:51:30 -0700
- Delivered-to: firstname.lastname@example.org
- User-agent: Mozilla/5.0 (Windows NT 6.3; WOW64; rv:45.0) Gecko/20100101 Thunderbird/45.0
So it's not a surprise for the community:
Based upon the discussion/comments described on  it's looking more
likely that ECF will withdraw from the Neon simultaneous release. As I
state in this comment
I'm going to take a couple of days to decide whether I have the time
next week to try any of the proposed solutions. If not then I don't
see any option but to withdraw ECF from the simultaneous release.
On 5/3/2016 9:29 AM, Scott Lewis wrote:
I tried to update ECF's contribution to Neon to our latest release
(3.13.1) and it resulted in a very strange build failure in the neon
aggregation build...see ). The problem isn't apparently with any
of our bundles, but the Apache Zookeeper 3.3.3 dependency that we get
from Orbit and distribute in our repository.
The problem is not at all clear to me, since we've been using this
Orbit bundle for several years, and we haven't made any substantial
changes to our builder...wrt to this part of things...for > 8 months.
In any event, I just want to make clear that if we/David/others can't
get this fixed in time for Neon that we will be forced to leave the
Neon simultaneous release.
If you have any insight about what's going on with this, and/or have
some bandwidth to help, please join and contribute to the effort via .
ecf-dev mailing list
To change your delivery options, retrieve your password, or
unsubscribe from this list, visit