FWIW - You can also just delete the *.om.generation file(s) in the
generator output directory. This is slightly better if your
schema.xml file is in a code repository.
But you're right, there should be a clean target for this... but
I can understand the difficulties with this. For example, what
That was the workaround I used after all.
But I prefer the use of an explicit parameter forcing maven to start the
building process from scratch.
Am Do, 25.05.2006, 20:58, schrieb Patrick Carl:
> -BEGIN PGP SIGNED MESSAGE-
> Hash: SHA1
>
>
> Hi,
>
>
> Matthias Klein schrieb
>
>> ...
>> Ho
-BEGIN PGP SIGNED MESSAGE-
Hash: SHA1
Hi,
Matthias Klein schrieb
> ...
> How can I force maven to generate _everything_?
>
What a about a touch on the schema file or save it again without change?
Patrick
> Thanks
>
> Matt
>
>
>
When I call "maven torque" to generate my OM classes, I keep getting a
message such as
"Schema files have not changed since last generation"
Sometimes that is untrue, though, and in some cases I have deleted the OM
directory manually - but maven refuses to re-generate it.
How can I force maven t
Matthias Klein wrote:
Of course, the list of dependencies will have to be resolved first. But
Question 2: Is all I need to do add all required jars and plugins in my
/lib folder?
Maven will resolve dependencies for you, and the built in "eclipse"
plugin for maven will keep eclipse in sync wi
Hi,
I think I've fixed my problems using PreparedStatements.
I've had to add a few cases to the parameter types that seem
to have been missed. I'm unsure if this is the appropriate place
as it seems NumberKey should handle some of this, but I'm
not all that familiar with the Torque code.
I had to
