I agree, I plan repeat build and run integration test on my computer, report for issues, and then see what else can I do then. I'm also open to other suggestions.
Can you please confirm that the information on http://servicemix.apache.org/community/contributing.html is up to date, eventually review them and if something is inefficient, suggest some pragmatical exceptions to those rule that we can take into account? Also please confirm that the official repository for SMX 5 is this one: http://svn.apache.org/repos/asf/servicemix/smx5/trunk/ or point us toward the right URL on which you will work. Thank you again Gert, Cristiano 2014-02-13 9:53 GMT+01:00 Gert Vanthienen <[email protected]>: > L.S., > > > Moving the discussion from the users@ to dev@ mailing list, it would > be good to figure out how to go about things. > > For now, I would propose we avoid adding any extra complexity and just > focus on getting a simple assembly project in place that combines the > latest and greatest bits of ActiveMQ, CXF, Camel, Karaf, ... > > How about we start with the ServiceMix 5 codebase, remove the new > Camel interceptor bits for now and just focus on getting the assembly > itself, the examples and the integration tests working? That way, we > should have a fairly manageable amount of work to perform before we > can get to a new release. > > We have a board report coming up in March, so we can convey this new > direction in that. Perhaps we should use the next board report after > that as a checkpoint to see if we are making any progress: by then, I > think we should have been able to do at least one or two releases and > we should have found a few people that are willing/able to help out > with the work. If we have not made any progress on the community > aspect by then, it may be a good time to reflect on how to gracefully > move people over to a plain Karaf/CXF/Camel/... solution instead. > > > Wdyt? > > Gert Vanthienen >
