Issue Details (XML | Word | Printable)

Type: Improvement Improvement
Status: Closed Closed
Resolution: Won't Fix
Priority: Major Major
Assignee: Unassigned
Reporter: Emmanuel Poitier
Votes: 0
Watchers: 0

If you were logged in you would be able to see more operations.
DataNucleus Enhancer (ARCHIVED)

Future of Enhancer

Created: 06/Jan/13 09:45 PM   Updated: 10/Jan/13 12:39 PM   Resolved: 10/Jan/13 07:24 AM
Component/s: None
Affects Version/s: 3.1.0.release
Fix Version/s: None

 Description  « Hide

It seems the enhancer will be removed in the future. The version stored on svn ( is v3.1.0.release and not sure where the v3.1.1 can be found.

After fixing the JDOClassLoaderResolver, I can have it compiled, but the tests fails. In fact, I do not really need the enhancer as it is now included in the core (tell me if I am wrong, and possibly a page to do the transition would help), but I do need the enhancer task for ant, which is not part of the core.

How can I get the enhancer task for ant separately from the enhancer ?

Best regards,
Emmanuel Poitier

Sort Order: Ascending order - Click to sort in descending order
Chris Colman added a comment - 07/Jan/13 08:20 AM
The trick here is that as the enhancer was moved to the core it's package name was changed which is why ant can't find it.

Remove the '.tools' segment from the package name. The patch to your ant build file(s) might look like this:

- <taskdef name="enhancer" classname="">
+ <taskdef name="enhancer" classname="org.datanucleus.enhancer.EnhancerTask">

Emmanuel Poitier added a comment - 07/Jan/13 09:48 PM

it does work. Thanks for your help.

Best regards,
Emmanuel Poitier

Andy Jefferson added a comment - 10/Jan/13 11:02 AM
Obviously the DN docs (for v3.2) say very clearly what is needed to upgrade to v3.2, and say what the enhancer task class name is.

In addition, the DN forum is for asking questions, not JIRA.

Emmanuel Poitier added a comment - 10/Jan/13 12:39 PM

Sorry if I should not have logged a bug, but as I was unable to find the information, it is the reason why I did log this issue to enhance documentation, but if you say that it is documented, then accept my apologies in this matter.

I will check in the 3.2 documentation to see if I can locate this information.

Best regards,
Emmanuel Poitier