Hi Marcel Nice to hear that you are going to prepare the new release.
Yesterday I saw that you changed a little bit the ConfigurationHandler on the agent. The put method has been removed and the AgentConstants.CONFIG_CONTROLLER_DISABLED has been set to deprecated. I'm fine with this in principle. But I'm using this to switch the ACE agent on/off in my Custom Controller. And thus, I will have to deactivate the polling of the DefaultController directly by setting the corresponding Syst. Prop at startup. In my current custom controller implementation I use the same property (AgentConstants.CONFIG_CONTROLLER_DISABLED) for enabling/disabling the polling, but when my custom controller is checking for updates, I disable the ACE agent by forwarding disbled=true to the ACE agent. Do I have to adjust my implementation or is there another option to stop polling within the ACE Agent? Thx in advance Greetings Wilfried > -----Ursprüngliche Nachricht----- > Von: Marcel Offermans [mailto:[email protected]] > Gesendet: Donnerstag, 10. April 2014 19:36 > An: ACE-dev Apache ACE developers > Cc: ACE-users Apache ACE users > Betreff: Preparing for a new release... > > Hello all, > > Over the last couple of weeks we have been working towards a new release. > Baselining is in place, the code moved to Java 7, we upgraded to the latest > versions of some of our dependencies and fixed lots of issues. Overall, I > think it is time we cut a new release. Since we are now using semantic > versioning, I propose we use that to version our overall release as well. We > have some major changes, which means our release should be 2.0.0. > > I would like to know if there are things that anybody would absolutely like to > have in the upcoming release. If not, I propose we "feature freeze" the > repository and start a vote soon. As always there is some work to be done on > the website, so if anybody wants to help out with that, let me know. > > Greetings, Marcel
