Mailing-List: contact users-help@ace.apache.org; run by ezmlm
Precedence: bulk
Reply-To: users@ace.apache.org
Received-SPF: pass (nike.apache.org: local policy)
From: Sibla Wilfried <Wilfried.Sibla@bosch-si.com>
To: "users@ace.apache.org" <users@ace.apache.org>
Subject: AW: Preparing for a new release...
Thread-Topic: Preparing for a new release...
Thread-Index: AQHPVON8ewg+O1rR3EWx/kaO7FU7fpsLOUpA
Date: Thu, 10 Apr 2014 19:35:50 +0000
Message-ID: <83CCD4C6D2018F4A9E31ABD2C253281C1379CD@imbpw2exd01.bosch-si.com>
References: <9BADC33F-B4E9-4F25-8CA4-1D95CF108B37@luminis.nl>
In-Reply-To: <9BADC33F-B4E9-4F25-8CA4-1D95CF108B37@luminis.nl>
Accept-Language: de-DE, en-US
Content-Language: de-DE
Content-Type: text/plain; charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable
MIME-Version: 1.0

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 t=
he agent.
The put method has been removed and the AgentConstants.CONFIG_CONTROLLER_DI=
SABLED has been set to deprecated.
I'm fine with this in principle.=20
But I'm using this to switch the ACE agent on/off in my Custom Controller.=
=20
And thus, I will have to deactivate the polling of the DefaultController di=
rectly by setting the corresponding Syst. Prop at startup.

In my current custom controller implementation I use the same property (Age=
ntConstants.CONFIG_CONTROLLER_DISABLED) for enabling/disabling the polling,=
 but when my custom controller is checking for updates, I disable the ACE a=
gent by forwarding disbled=3Dtrue to the ACE agent.
Do I have to adjust my implementation or is there another option to stop po=
lling within the ACE Agent?

Thx in advance

Greetings
Wilfried

> -----Urspr=FCngliche Nachricht-----
> Von: Marcel Offermans [mailto:marcel.offermans@luminis.nl]
> 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...
>=20
> Hello all,
>=20
> 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 late=
st
> 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.
>=20
> I would like to know if there are things that anybody would absolutely li=
ke 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.
>=20
> Greetings, Marcel