Yes. A global patch would be better instead of separate patches.
I tried your 2 patches and updated locally jpox-* to 1.1.3 in continuum parent
pom. With them, all tests works fine, but continuum doesn't start.
Emmanuel
Marcelo Fukushima a écrit :
Hello dear devs.
After everyone's help, ive noticed that jpox was saving the
BuildDefinition with wrong values (the buildFresh and arguments and
possibly others too)... since i dont know how jpox work, the first
thing i tried was to update to a more recent version of it (namely
1.1.3) and everything worked fine...
im going to attach the test case to jira (actually a patch to the
testcase to check those things too), but should i attach a patch to
the pom too?
On 1/9/07, Brett Porter <[EMAIL PROTECTED]> wrote:
The metadata file (and enhanced classes) are generated when you use
Maven to build the project. As long as eclipse doesn't overwrite the
class files it should be fine. Alternatively, you can use the eclipse
plugin for jpox to make sure the classes get enhanced and just run
maven once to generate the metadata file. I've never used that
plugin, but it is available from the jpox site.
Thanks!
- Brett
On 09/01/2007, at 2:27 PM, Marcelo Fukushima wrote:
> hello folks! i sent a couple of emails to the user list, but i guess i
> could help a little too, right? so i just checked out the code from
> SVN and wanted to tackle
> http://jira.codehaus.org/browse/CONTINUUM-1103
> while i could isolate the bug (the property is not getting persisted
> on the db) but since i know almost nothing about jdo, i cant run the
> tests inside eclipse to try to figure out the solution and i couldnt
> find where the metadata file or the enhanced version of the classes
> are found...
> is there any doc that can help me with that kinda of info? thanks
> in advance
> --
> []'s
> Marcelo Takeshi Fukushima
