You are viewing a plain text version of this content. The canonical link for it is here.
Posted to torque-dev@db.apache.org by "Jean T. Anderson" <jt...@bristowhill.com> on 2005/10/06 20:36:39 UTC
Torque test project can't find torque-gen-templates-3.2-rc3-dev.jar
Greetings, all, I'm working on running the Torque test project
(http://db.apache.org/torque/tests.html) with Derby 10.1.1.0 and the
Derby Network Client.
References to torque-3.2-rc3-dev.jar and torque-gen-3.2-rc3-dev.jar
assembled from common/project.xml and generator/project.xml caused an
initial failure, which I managed to resolve, but now the run fails on an
attempt to find torque-gen-templates-3.2-rc3-dev.jar :
[jta@gertie3 trunks]$ maven -Dtorque.test.profile=derby
__ __
| \/ |__ _Apache__ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0.2
build:start:
...
+----------------------------------------
| Executing multiproject:artifact-callback Torque generator
| Memory: 5M/8M
+----------------------------------------
Attempting to download torque-gen-templates-3.2-rc3-dev.jar.
WARNING: Failed to download torque-gen-templates-3.2-rc3-dev.jar.
BUILD FAILED
File......
/home/jta/.maven/cache/maven-multiproject-plugin-1.4.1/plugin.jelly
Element... maven:reactor
Line...... 218
Column.... 9
The build cannot continue because of the following unsatisfied
dependency:
torque-gen-templates-3.2-rc3-dev.jar (try downloading from
http://db.apache.org/torque/generator/templates/)
Total time: 5 seconds
Finished at: Thu Oct 06 11:25:04 PDT 2005
I tried going to http://db.apache.org/torque/generator/templates/ , but
that page gets a 404 not found error. Any suggestions on how I should
fix this?
thanks,
-jean
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org
Re: Followup on DERBY-142 (Was Torque test project can't find torque-gen-templates-3.2-rc3-dev.jar)
Posted by "Jean T. Anderson" <jt...@bristowhill.com>.
Thomas Fischer wrote:
>
> Jean,
>
> Thanks a lot for pushing this Bug to the surface again.
Torque has been on my list for quite a while to work with, but it was a
user's post to derby-user@db.apache.org that provided the push.
> All I can say to this discussion is that from my experience with Torque,
> the other database drivers I have worked with (Mysq, Postgresql, Oracle,
> Firebird, HSQLDB) return that the column is _NOT_ readonly if it is an
> ordinary table, so if the Network driver behaviour would be retained, derby
> would be the only database with that behaviour.
And possibly DB2 has that behaviour as well because you originally
encountered the problem with the DB2 Universal JDBC driver.
It'll be interesting to see how this all works out.
> Also, regarding your other remarks about the tutorial, I'll check them in
> as soon as I can grasp some time. I'm glad you found the tutorial useful.
I put a page up for derby users here, so you might get some more
hits/feedback on the tutorial:
http://db.apache.org/derby/integrate/db_torque.html
cheers,
-jean
>
> Thomas
>
>
> "Jean T. Anderson" <jt...@bristowhill.com> schrieb am 10.10.2005 17:50:30:
>
>
>>To quickly summarize, given "SELECT id, name FROM readonlytest", the
>>Derby embedded driver says that the columns are writeable while the
>>Derby Network Client (and the DB2 Universal JDBC driver) say the columns
>>are readonly. Village refuses to insert data for columns that are marked
>>"readonly".
>>
>>If you add a "FOR UPDATE" clause to the statement, the Derby Network
>>Client now says that the columns are writeable, sparking some debate as
>>to what the correct behavior should be in the both the embedded and
>>client drivers:
>>
>>http://mail-archives.apache.org/mod_mbox/db-derby-dev/200510.mbox/%
>>3c434926AE.6080702@sun.com%3e
>>
>>If a "resolution" comes out of this, I'll post it.
>>
>> -jean
>>
>>Jean T. Anderson wrote:
>>
>>>Thomas Fischer wrote:
>>>
>>>
>>>>... By the way, last time I tried it, Torque did not work with Derby
>>>>and the
>>>>network driver. The problem was that the network driver in the
>
> meta-info
>
>>>>declared all columns to be read-only, which causes a library used
>>>>internally in Torque (village) to refuse to write any datasets into
>
> the
>
>>>>table. The problem is described in the Bug DERBY-142 in Derby's Jira.
>>>
>>>
>>>That explains the many test failures I saw yesterday. :-) I just
>>>updated DERBY-142 with an additional test based on one of the sample
>>>Derby apps that reproduces the problem with the 10.1 Derby Network
>
> Client.
>
>>>By the way, there's a typo in
>
> trunks/test/profile/derby/project.properties:
>
>>> torque.database.buildUrl = jjdbc:derby:net://localhost/test
>>>
>>>Should be 'jdbc' instead of 'jjdbc':
>>>
>>> torque.database.buildUrl = jdbc:derby:net://localhost/test
>>>
>>>
>>>>However, in future releases of Torque, it is quite probable that
>>>>village is
>>>>removed, so this will not be problematic any longer.
>>>
>>>...
>>>
>>>I'll try the embedded driver, which worked great for the torque
>
> tutorial.
>
>>>One problem I discovered in the tutorial (and that repeats in the
>
> tests)
>
>>>is Derby doesn't support creating a table that references another table
>
>
>>>that doesn't exist yet. For example, this BOOK create statement fails
>>>because the author table doesn't exist yet (this from
>>>trunks/test/test-project/target/sql/bookstore-schema.sql):
>>>
>>>CREATE TABLE book
>>>(
>>> book_id INTEGER NOT NULL,
>>> isbn VARCHAR(15) NOT NULL,
>>> author_id INTEGER NOT NULL,
>>> title VARCHAR(255) NOT NULL,
>>> PRIMARY KEY(book_id),
>>> FOREIGN KEY (author_id) REFERENCES author (author_id)
>>> );
>>>
>>>My solution for this for the tutorial was to modify the
>>>src/schema/project-schema.xml to place the BOOK definition at the end,
>>>then it worked great.
>>>
>>> -jean
>>>
>>>
>>>
>>>---------------------------------------------------------------------
>>>To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
>>>For additional commands, e-mail: torque-dev-help@db.apache.org
>>>
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
>>For additional commands, e-mail: torque-dev-help@db.apache.org
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-dev-help@db.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org
RE: Followup on DERBY-142 (Was Torque test project can't find
torque-gen-templates-3.2-rc3-dev.jar)
Posted by Thomas Fischer <fi...@seitenbau.net>.
Jean,
Thanks a lot for pushing this Bug to the surface again.
All I can say to this discussion is that from my experience with Torque,
the other database drivers I have worked with (Mysq, Postgresql, Oracle,
Firebird, HSQLDB) return that the column is _NOT_ readonly if it is an
ordinary table, so if the Network driver behaviour would be retained, derby
would be the only database with that behaviour.
Also, regarding your other remarks about the tutorial, I'll check them in
as soon as I can grasp some time. I'm glad you found the tutorial useful.
Thomas
"Jean T. Anderson" <jt...@bristowhill.com> schrieb am 10.10.2005 17:50:30:
> To quickly summarize, given "SELECT id, name FROM readonlytest", the
> Derby embedded driver says that the columns are writeable while the
> Derby Network Client (and the DB2 Universal JDBC driver) say the columns
> are readonly. Village refuses to insert data for columns that are marked
> "readonly".
>
> If you add a "FOR UPDATE" clause to the statement, the Derby Network
> Client now says that the columns are writeable, sparking some debate as
> to what the correct behavior should be in the both the embedded and
> client drivers:
>
> http://mail-archives.apache.org/mod_mbox/db-derby-dev/200510.mbox/%
> 3c434926AE.6080702@sun.com%3e
>
> If a "resolution" comes out of this, I'll post it.
>
> -jean
>
> Jean T. Anderson wrote:
> > Thomas Fischer wrote:
> >
> >> ... By the way, last time I tried it, Torque did not work with Derby
> >> and the
> >> network driver. The problem was that the network driver in the
meta-info
> >> declared all columns to be read-only, which causes a library used
> >> internally in Torque (village) to refuse to write any datasets into
the
> >> table. The problem is described in the Bug DERBY-142 in Derby's Jira.
> >
> >
> > That explains the many test failures I saw yesterday. :-) I just
> > updated DERBY-142 with an additional test based on one of the sample
> > Derby apps that reproduces the problem with the 10.1 Derby Network
Client.
> >
> > By the way, there's a typo in
trunks/test/profile/derby/project.properties:
> >
> > torque.database.buildUrl = jjdbc:derby:net://localhost/test
> >
> > Should be 'jdbc' instead of 'jjdbc':
> >
> > torque.database.buildUrl = jdbc:derby:net://localhost/test
> >
> >> However, in future releases of Torque, it is quite probable that
> >> village is
> >> removed, so this will not be problematic any longer.
> >
> > ...
> >
> > I'll try the embedded driver, which worked great for the torque
tutorial.
> >
> > One problem I discovered in the tutorial (and that repeats in the
tests)
> > is Derby doesn't support creating a table that references another table
> > that doesn't exist yet. For example, this BOOK create statement fails
> > because the author table doesn't exist yet (this from
> > trunks/test/test-project/target/sql/bookstore-schema.sql):
> >
> > CREATE TABLE book
> > (
> > book_id INTEGER NOT NULL,
> > isbn VARCHAR(15) NOT NULL,
> > author_id INTEGER NOT NULL,
> > title VARCHAR(255) NOT NULL,
> > PRIMARY KEY(book_id),
> > FOREIGN KEY (author_id) REFERENCES author (author_id)
> > );
> >
> > My solution for this for the tutorial was to modify the
> > src/schema/project-schema.xml to place the BOOK definition at the end,
> > then it worked great.
> >
> > -jean
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
> > For additional commands, e-mail: torque-dev-help@db.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-dev-help@db.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org
Followup on DERBY-142 (Was Torque test project can't find torque-gen-templates-3.2-rc3-dev.jar)
Posted by "Jean T. Anderson" <jt...@bristowhill.com>.
To quickly summarize, given "SELECT id, name FROM readonlytest", the
Derby embedded driver says that the columns are writeable while the
Derby Network Client (and the DB2 Universal JDBC driver) say the columns
are readonly. Village refuses to insert data for columns that are marked
"readonly".
If you add a "FOR UPDATE" clause to the statement, the Derby Network
Client now says that the columns are writeable, sparking some debate as
to what the correct behavior should be in the both the embedded and
client drivers:
http://mail-archives.apache.org/mod_mbox/db-derby-dev/200510.mbox/%3c434926AE.6080702@sun.com%3e
If a "resolution" comes out of this, I'll post it.
-jean
Jean T. Anderson wrote:
> Thomas Fischer wrote:
>
>> ... By the way, last time I tried it, Torque did not work with Derby
>> and the
>> network driver. The problem was that the network driver in the meta-info
>> declared all columns to be read-only, which causes a library used
>> internally in Torque (village) to refuse to write any datasets into the
>> table. The problem is described in the Bug DERBY-142 in Derby's Jira.
>
>
> That explains the many test failures I saw yesterday. :-) I just
> updated DERBY-142 with an additional test based on one of the sample
> Derby apps that reproduces the problem with the 10.1 Derby Network Client.
>
> By the way, there's a typo in trunks/test/profile/derby/project.properties:
>
> torque.database.buildUrl = jjdbc:derby:net://localhost/test
>
> Should be 'jdbc' instead of 'jjdbc':
>
> torque.database.buildUrl = jdbc:derby:net://localhost/test
>
>> However, in future releases of Torque, it is quite probable that
>> village is
>> removed, so this will not be problematic any longer.
>
> ...
>
> I'll try the embedded driver, which worked great for the torque tutorial.
>
> One problem I discovered in the tutorial (and that repeats in the tests)
> is Derby doesn't support creating a table that references another table
> that doesn't exist yet. For example, this BOOK create statement fails
> because the author table doesn't exist yet (this from
> trunks/test/test-project/target/sql/bookstore-schema.sql):
>
> CREATE TABLE book
> (
> book_id INTEGER NOT NULL,
> isbn VARCHAR(15) NOT NULL,
> author_id INTEGER NOT NULL,
> title VARCHAR(255) NOT NULL,
> PRIMARY KEY(book_id),
> FOREIGN KEY (author_id) REFERENCES author (author_id)
> );
>
> My solution for this for the tutorial was to modify the
> src/schema/project-schema.xml to place the BOOK definition at the end,
> then it worked great.
>
> -jean
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-dev-help@db.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org
Re: Torque test project can't find torque-gen-templates-3.2-rc3-dev.jar
Posted by Thomas Fischer <tf...@apache.org>.
Jean
Thanks for pointing out the error. Just committed the fix, it will be
fixed in 3.2-RC3
Thomas
On Fri, 7 Oct 2005, Jean T. Anderson wrote:
> One problem I discovered in the tutorial (and that repeats in the tests) is
> Derby doesn't support creating a table that references another table that
> doesn't exist yet. For example, this BOOK create statement fails because the
> author table doesn't exist yet (this from
> trunks/test/test-project/target/sql/bookstore-schema.sql):
>
> CREATE TABLE book
> (
> book_id INTEGER NOT NULL,
> isbn VARCHAR(15) NOT NULL,
> author_id INTEGER NOT NULL,
> title VARCHAR(255) NOT NULL,
> PRIMARY KEY(book_id),
> FOREIGN KEY (author_id) REFERENCES author (author_id)
> );
>
> My solution for this for the tutorial was to modify the
> src/schema/project-schema.xml to place the BOOK definition at the end, then
> it worked great.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org
Re: Torque test project can't find torque-gen-templates-3.2-rc3-dev.jar
Posted by "Jean T. Anderson" <jt...@bristowhill.com>.
Thomas Fischer wrote:
> ...
> By the way, last time I tried it, Torque did not work with Derby and the
> network driver. The problem was that the network driver in the meta-info
> declared all columns to be read-only, which causes a library used
> internally in Torque (village) to refuse to write any datasets into the
> table. The problem is described in the Bug DERBY-142 in Derby's Jira.
That explains the many test failures I saw yesterday. :-) I just
updated DERBY-142 with an additional test based on one of the sample
Derby apps that reproduces the problem with the 10.1 Derby Network Client.
By the way, there's a typo in trunks/test/profile/derby/project.properties:
torque.database.buildUrl = jjdbc:derby:net://localhost/test
Should be 'jdbc' instead of 'jjdbc':
torque.database.buildUrl = jdbc:derby:net://localhost/test
> However, in future releases of Torque, it is quite probable that village is
> removed, so this will not be problematic any longer.
...
I'll try the embedded driver, which worked great for the torque tutorial.
One problem I discovered in the tutorial (and that repeats in the tests)
is Derby doesn't support creating a table that references another table
that doesn't exist yet. For example, this BOOK create statement fails
because the author table doesn't exist yet (this from
trunks/test/test-project/target/sql/bookstore-schema.sql):
CREATE TABLE book
(
book_id INTEGER NOT NULL,
isbn VARCHAR(15) NOT NULL,
author_id INTEGER NOT NULL,
title VARCHAR(255) NOT NULL,
PRIMARY KEY(book_id),
FOREIGN KEY (author_id) REFERENCES author (author_id)
);
My solution for this for the tutorial was to modify the
src/schema/project-schema.xml to place the BOOK definition at the end,
then it worked great.
-jean
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org
Re: Torque test project can't find torque-gen-templates-3.2-rc3-dev.jar
Posted by Thomas Fischer <fi...@seitenbau.net>.
Hi,
Running Maven in the "templates" directory is the "official" way to create
the Templates jar. If the "trunks" directory is used, one can also run
"maven multiproject:install" in the trunks directory to build all Torque
components at once .
By the way, last time I tried it, Torque did not work with Derby and the
network driver. The problem was that the network driver in the meta-info
declared all columns to be read-only, which causes a library used
internally in Torque (village) to refuse to write any datasets into the
table. The problem is described in the Bug DERBY-142 in Derby's Jira.
However, in future releases of Torque, it is quite probable that village is
removed, so this will not be problematic any longer.
Thomas
"Jean T. Anderson" <jt...@bristowhill.com> schrieb am 06.10.2005 21:16:22:
> this way worked -- thanks!
>
> -jean
>
>
> Hilco Wijbenga wrote:
> > I ran into this too.
> >
> > My solution was to just run Maven in the 'templates' directory. It will
> > create the torque-gen-templates-3.2-rc3-dev.jar file in the target
> > directory. This is assuming you've checked out the sources, of
course...
> >
> > After it's been created just copy it to .maven/repository/torque/jars.
> >
> > I don't know if there is a smarter way to do it. :-)
> >
> > On Thu, 2005-10-06 at 11:36 -0700, Jean T. Anderson wrote:
> >
> >>Greetings, all, I'm working on running the Torque test project
> >>(http://db.apache.org/torque/tests.html) with Derby 10.1.1.0 and the
> >>Derby Network Client.
> >>
> >>References to torque-3.2-rc3-dev.jar and torque-gen-3.2-rc3-dev.jar
> >>assembled from common/project.xml and generator/project.xml caused an
> >>initial failure, which I managed to resolve, but now the run fails on
an
> >>attempt to find torque-gen-templates-3.2-rc3-dev.jar :
> >>
> >>
> >> [jta@gertie3 trunks]$ maven -Dtorque.test.profile=derby
> >> __ __
> >> | \/ |__ _Apache__ ___
> >> | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
> >> |_| |_\__,_|\_/\___|_||_| v. 1.0.2
> >>
> >> build:start:
> >>
> >> ...
> >>
> >> +----------------------------------------
> >> | Executing multiproject:artifact-callback Torque generator
> >> | Memory: 5M/8M
> >> +----------------------------------------
> >> Attempting to download torque-gen-templates-3.2-rc3-dev.jar.
> >> WARNING: Failed to download torque-gen-templates-3.2-rc3-dev.jar.
> >>
> >> BUILD FAILED
> >> File......
> >>/home/jta/.maven/cache/maven-multiproject-plugin-1.4.1/plugin.jelly
> >> Element... maven:reactor
> >> Line...... 218
> >> Column.... 9
> >> The build cannot continue because of the following unsatisfied
> >>dependency:
> >>
> >> torque-gen-templates-3.2-rc3-dev.jar (try downloading from
> >>http://db.apache.org/torque/generator/templates/)
> >>
> >> Total time: 5 seconds
> >> Finished at: Thu Oct 06 11:25:04 PDT 2005
> >>
> >>
> >>I tried going to http://db.apache.org/torque/generator/templates/ , but
> >>that page gets a 404 not found error. Any suggestions on how I should
> >>fix this?
> >>
> >>thanks,
> >>
> >> -jean
> >>
> >>
> >>---------------------------------------------------------------------
> >>To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
> >>For additional commands, e-mail: torque-dev-help@db.apache.org
> >>
> >
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
> > For additional commands, e-mail: torque-dev-help@db.apache.org
> >
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-dev-help@db.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org
Re: Torque test project can't find torque-gen-templates-3.2-rc3-dev.jar
Posted by "Jean T. Anderson" <jt...@bristowhill.com>.
this way worked -- thanks!
-jean
Hilco Wijbenga wrote:
> I ran into this too.
>
> My solution was to just run Maven in the 'templates' directory. It will
> create the torque-gen-templates-3.2-rc3-dev.jar file in the target
> directory. This is assuming you've checked out the sources, of course...
>
> After it's been created just copy it to .maven/repository/torque/jars.
>
> I don't know if there is a smarter way to do it. :-)
>
> On Thu, 2005-10-06 at 11:36 -0700, Jean T. Anderson wrote:
>
>>Greetings, all, I'm working on running the Torque test project
>>(http://db.apache.org/torque/tests.html) with Derby 10.1.1.0 and the
>>Derby Network Client.
>>
>>References to torque-3.2-rc3-dev.jar and torque-gen-3.2-rc3-dev.jar
>>assembled from common/project.xml and generator/project.xml caused an
>>initial failure, which I managed to resolve, but now the run fails on an
>>attempt to find torque-gen-templates-3.2-rc3-dev.jar :
>>
>>
>> [jta@gertie3 trunks]$ maven -Dtorque.test.profile=derby
>> __ __
>> | \/ |__ _Apache__ ___
>> | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
>> |_| |_\__,_|\_/\___|_||_| v. 1.0.2
>>
>> build:start:
>>
>> ...
>>
>> +----------------------------------------
>> | Executing multiproject:artifact-callback Torque generator
>> | Memory: 5M/8M
>> +----------------------------------------
>> Attempting to download torque-gen-templates-3.2-rc3-dev.jar.
>> WARNING: Failed to download torque-gen-templates-3.2-rc3-dev.jar.
>>
>> BUILD FAILED
>> File......
>>/home/jta/.maven/cache/maven-multiproject-plugin-1.4.1/plugin.jelly
>> Element... maven:reactor
>> Line...... 218
>> Column.... 9
>> The build cannot continue because of the following unsatisfied
>>dependency:
>>
>> torque-gen-templates-3.2-rc3-dev.jar (try downloading from
>>http://db.apache.org/torque/generator/templates/)
>>
>> Total time: 5 seconds
>> Finished at: Thu Oct 06 11:25:04 PDT 2005
>>
>>
>>I tried going to http://db.apache.org/torque/generator/templates/ , but
>>that page gets a 404 not found error. Any suggestions on how I should
>>fix this?
>>
>>thanks,
>>
>> -jean
>>
>>
>>---------------------------------------------------------------------
>>To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
>>For additional commands, e-mail: torque-dev-help@db.apache.org
>>
>
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-dev-help@db.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org
Re: Torque test project can't find
torque-gen-templates-3.2-rc3-dev.jar
Posted by Hilco Wijbenga <hi...@elasticpath.com>.
I ran into this too.
My solution was to just run Maven in the 'templates' directory. It will
create the torque-gen-templates-3.2-rc3-dev.jar file in the target
directory. This is assuming you've checked out the sources, of course...
After it's been created just copy it to .maven/repository/torque/jars.
I don't know if there is a smarter way to do it. :-)
On Thu, 2005-10-06 at 11:36 -0700, Jean T. Anderson wrote:
> Greetings, all, I'm working on running the Torque test project
> (http://db.apache.org/torque/tests.html) with Derby 10.1.1.0 and the
> Derby Network Client.
>
> References to torque-3.2-rc3-dev.jar and torque-gen-3.2-rc3-dev.jar
> assembled from common/project.xml and generator/project.xml caused an
> initial failure, which I managed to resolve, but now the run fails on an
> attempt to find torque-gen-templates-3.2-rc3-dev.jar :
>
>
> [jta@gertie3 trunks]$ maven -Dtorque.test.profile=derby
> __ __
> | \/ |__ _Apache__ ___
> | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
> |_| |_\__,_|\_/\___|_||_| v. 1.0.2
>
> build:start:
>
> ...
>
> +----------------------------------------
> | Executing multiproject:artifact-callback Torque generator
> | Memory: 5M/8M
> +----------------------------------------
> Attempting to download torque-gen-templates-3.2-rc3-dev.jar.
> WARNING: Failed to download torque-gen-templates-3.2-rc3-dev.jar.
>
> BUILD FAILED
> File......
> /home/jta/.maven/cache/maven-multiproject-plugin-1.4.1/plugin.jelly
> Element... maven:reactor
> Line...... 218
> Column.... 9
> The build cannot continue because of the following unsatisfied
> dependency:
>
> torque-gen-templates-3.2-rc3-dev.jar (try downloading from
> http://db.apache.org/torque/generator/templates/)
>
> Total time: 5 seconds
> Finished at: Thu Oct 06 11:25:04 PDT 2005
>
>
> I tried going to http://db.apache.org/torque/generator/templates/ , but
> that page gets a 404 not found error. Any suggestions on how I should
> fix this?
>
> thanks,
>
> -jean
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
> For additional commands, e-mail: torque-dev-help@db.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: torque-dev-unsubscribe@db.apache.org
For additional commands, e-mail: torque-dev-help@db.apache.org