How to tell a plugin not to load older builds because of (backwards) incompatibility

[Ognjen Bubalo]

Hi,

I refactored the JaCoCo plugin and now I get exceptions like:

com.thoughtworks.xstream.converters.reflection.NonExistentFieldException: No such field hudson.plugins.jacoco.JacocoBuildAction.build.

This was a bigger refactor so I don't think it should be clever to put back the old fields.

Is there a solution for not loading older builds?

Thanks,

Ogi

[nicolas de loof-2]

general practice is to keep old attribute (deprecated) set as transient and use readResolve() to translate them to the new model.

2012/11/3 Ognjen Bubalo <[hidden email]>

Hi,

I refactored the JaCoCo plugin and now I get exceptions like:

com.thoughtworks.xstream.converters.reflection.NonExistentFieldException: No such field hudson.plugins.jacoco.JacocoBuildAction.build.

This was a bigger refactor so I don't think it should be clever to put back the old fields.

Is there a solution for not loading older builds?

Thanks,

Ogi

[Ognjen Bubalo]

Thank you!

As I see this is the only way :( It is a hard one.

On Saturday, November 3, 2012 8:58:48 AM UTC+1, nicolas de loof wrote:

general practice is to keep old attribute (deprecated) set as transient and use readResolve() to translate them to the new model.

2012/11/3 Ognjen Bubalo <<a href="javascript:" target="_blank" gdf-obfuscated-mailto="flTDML311PAJ">ognjen...@...>

Hi,

I refactored the JaCoCo plugin and now I get exceptions like:

com.thoughtworks.xstream.converters.reflection.NonExistentFieldException: No such field hudson.plugins.jacoco.JacocoBuildAction.build.

This was a bigger refactor so I don't think it should be clever to put back the old fields.

Is there a solution for not loading older builds?

Thanks,

Ogi

[nicolas de loof-2]

I've been looking for a better syntax, but can't find.

2012/11/10 Ognjen Bubalo <[hidden email]>

Thank you!

As I see this is the only way :( It is a hard one.

On Saturday, November 3, 2012 8:58:48 AM UTC+1, nicolas de loof wrote:

general practice is to keep old attribute (deprecated) set as transient and use readResolve() to translate them to the new model.

2012/11/3 Ognjen Bubalo <[hidden email]>

Hi,

I refactored the JaCoCo plugin and now I get exceptions like:

com.thoughtworks.xstream.converters.reflection.NonExistentFieldException: No such field hudson.plugins.jacoco.JacocoBuildAction.build.

This was a bigger refactor so I don't think it should be clever to put back the old fields.

Is there a solution for not loading older builds?

Thanks,

Ogi