Your Torque version will no doubt have also changed so you may need to
review your Torque configuration.
The runtime configuration is also likely to have changed so you will
need to review your TurbineResources.properties.
Scott
sharad singh wrote:
thanks scott .but we are not going to compile turbine .we are only compiling
application.so just putting all the jar of turbine-2.3.3 and compile the
application it should work.
i am doing so but its not creating schema.
what ur opinion in this matter.
sharad
On 7/8/09, Scott Eade <[email protected]> wrote:
I think pretty much everyone who is actively using Turbine now uses Maven 2
for their projects.
While we do have META, this is for producing Maven 1 project descriptors
only. Someone recently expressed an interest in updating META to produce
Maven 2 descriptors, but I don't think any progress has been made on this.
I think your best option will be to set up a Maven 2 pom, add Turbine as a
dependency along with anything else you need. You will most likely have to
either restructure your project directories, or alter a bunch of settings in
your project descriptor in order to get things working.
Perhaps someone will be kind enough to post a stripped down M2 pom to act
as a starting point for you.
Scott
sharad singh wrote:
Hello all,
I want to switch my application from tdk-2.3_01 to turbine-2.3.3 .I was
using ant earliar with tdk-2.3_01 but now turbine-2.3.3
is on maven..any help regarding to this or any doc for it to easily
migrate
from eraliar to new one.
thanks in advance
sharad
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
