You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@turbine.apache.org by Roger I Martin PhD <hy...@hypernexinc.com> on 2002/08/17 14:13:30 UTC
maven enabled torque?
Hi,
I cvs'd jakarta-turbine-maven and jakarta-turbine-torque this morning. Built maven the boot strap way successfully.
The readme.txt that came from cvs'ing jakarta-turbine-torque says:
Building the decoupled version of Torque from CVS is now very easy. Torque
has been Maven-enabled. Please refer to the Maven Getting Started document
for instructions on building. This document is available here:
http://jakarta.apache.org/turbine/maven/getting-started.html
I did this. Then http://jakarta.apache.org/turbine/maven/start/use.html says:
Congratulations! Now that you have installed Maven and/or integrated with your project, you are now ready to start reaping the benefits of Maven. The rest of this document will be a guided tour through the basic operation of Maven's build system. You will learn how to build any of the following Maven-enabled Turbine projects: Torque, Stratum, Fulcrum, and Turbine. The process for each project is the identical thanks to Maven (as are the results).
First, checkout the source for any of the above Turbine projects. If you do not know how to do this, please refer to the CVS Repositories document. For those familiar with the growing family of Jakarta projects, several of the projects include all of the JAR files required to build and distribute the projects in their CVS repositories. Maven eliminates this practice altogether because it provides facilities to automatically download all dependencies from one or more central repositories. Thus, before any Maven goal is executed, Maven will automatically download all of the required dependencies from the remote repositories defined by the ${maven.repo.remote} property.
After Maven has automatically downloaded your dependencies, they are stored in your local repository. Recall, Maven uses this directory to store all JAR files. There are two exceptions: 1) non-distributable JARs will result in a message pointing you to the location where you can download the JAR yourself, and 2) JARs that don't exist in the local or remote repositories will result in an error. In either case, you'll have to download those yourself and manually place them in $MAVEN_HOME/repository. After you have downloaded all of the dependent JARs, generating a JAR for a Maven-enabled Turbine project is easy. Type the following:
maven java:jar
You'll notice that all of the code is compiled, and then unit tested, before it is packaged into a JAR file. The unit tests generate reports that are later parsed to create an HTML report that is part of the generated site documentation. The JAR file can also be automatically distributed.
...
What I see is:
__ __
| \/ |__ Jakarta _ ___
| |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
|_| |_\__,_|\_/\___|_||_| v. 1.0-b5-dev
jakarta-turbine-torque (torque) 3.0-b4-dev
C:\apache\jakarta-turbine-torque
java:jar:
[ERROR] INTERNAL ERROR
[ERROR] Reference made to goal 'java:jar' which has no definition.
Don't see any compiles, no nothing! For all the yadda such as "Building the decoupled version of Torque from CVS is now very easy", "Torque
has been Maven-enabled", "Congratulation!", "reaping the benefits", "generating a JAR for a Maven-enabled Turbine project is easy." and "biggest bang for you buck ", thats it?
May I suggest that all your documentation be stripped of the above kinds of phrases? Documentation should never be cute or exuberant 'cause when the results aren't cute or exuberant, any person or persons who has waded through such documentation looking for some meat and not finding any, gets the urge to strangle the documentation's author ;-)
--Roger
Re: maven enabled torque?
Posted by Jason van Zyl <ja...@zenplex.com>.
On Sat, 2002-08-17 at 08:13, Roger I Martin PhD wrote:
> Hi,
>
> I cvs'd jakarta-turbine-maven and jakarta-turbine-torque this morning. Built maven the boot strap way successfully.
What you are seeing is an error that I introduced last night. Some
plugin were not being built for about a 2 hour window last night.
At any rate I just did a clean co of maven and bootstrapped and fresh co
of torque:
...
test:test:
[junit] dir attribute ignored if running in the same VM
[junit] Running
org.apache.torque.engine.database.model.NameFactoryTest
[junit] Tests run: 1, Failures: 0, Errors: 0, Time elapsed: 0.317
sec
[junit] dir attribute ignored if running in the same VM
[junit] Running org.apache.torque.om.NumberKeyTest
[junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0.018
sec
[junit] dir attribute ignored if running in the same VM
[junit] Running org.apache.torque.util.CriteriaTest
[junit] Tests run: 5, Failures: 0, Errors: 0, Time elapsed: 0.834
sec
java:jar:
[jar] Building jar:
/home/jvanzyl/js/jakarta-turbine-torque/target/torque-3.0-b4-dev.jar
BUILD SUCCESSFUL
You sure you don't actually have a copy from last night?
--
jvz.
Jason van Zyl
jason@apache.org
http://tambora.zenplex.org
In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
-- Jacques Ellul, The Technological Society
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: maven enabled torque?
Posted by Jason van Zyl <ja...@zenplex.com>.
On Sat, 2002-08-17 at 10:09, James Taylor wrote:
> On Sat, 2002-08-17 at 09:34, Jason van Zyl wrote:
> > On Sat, 2002-08-17 at 09:23, Roger I Martin PhD wrote:
> > > Nope, maven.xml does not have a java:jar goal defined.
> >
> > Doesn't need to, it's the default goal baked into the maven defaults.
>
> Right, but the point is that the docs are out of date, and do not
> reflect the changes in b5/b6
I updated them for the getting started. Which are minimal but enough to
get you started at least.
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
--
jvz.
Jason van Zyl
jason@apache.org
http://tambora.zenplex.org
In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
-- Jacques Ellul, The Technological Society
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: maven enabled torque?
Posted by James Taylor <jt...@4lane.com>.
On Sat, 2002-08-17 at 09:34, Jason van Zyl wrote:
> On Sat, 2002-08-17 at 09:23, Roger I Martin PhD wrote:
> > Nope, maven.xml does not have a java:jar goal defined.
>
> Doesn't need to, it's the default goal baked into the maven defaults.
Right, but the point is that the docs are out of date, and do not
reflect the changes in b5/b6
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: maven enabled torque?
Posted by Jason van Zyl <ja...@zenplex.com>.
On Sat, 2002-08-17 at 09:23, Roger I Martin PhD wrote:
> Nope, maven.xml does not have a java:jar goal defined.
>
Doesn't need to, it's the default goal baked into the maven defaults.
--
jvz.
Jason van Zyl
jason@apache.org
http://tambora.zenplex.org
In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
-- Jacques Ellul, The Technological Society
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: maven enabled torque?
Posted by Roger I Martin PhD <hy...@hypernexinc.com>.
Nope, maven.xml does not have a java:jar goal defined.
Roger
----- Original Message -----
From: "Jason van Zyl" <ja...@zenplex.com>
To: "Turbine Developers List" <tu...@jakarta.apache.org>
Sent: Saturday, August 17, 2002 8:51 AM
Subject: Re: maven enabled torque?
> On Sat, 2002-08-17 at 08:53, Scott Eade wrote:
> > Roger,
> >
> > I happened to be doing the exact same thing at the same time as you and
ran
> > into the same problem.
> >
> > It looks to me like maven is not finding maven.xml because it is not
finding
> > any of the goals ("maven -g" is pretty sparse).
> >
> > "ant -f build-legacy.xml" is next to useless and it still refers to the
> > pre-maven-b4 "lib.repo" property.
> >
> > I'm wondering if the maven b5 distribution (as opposed to cvs head) will
> > work.
>
> The distribution should work and I just tried with clean checkouts of
> both Maven and Torque and built successfully.
>
> > Cheers,
> >
> > Scott
> > --
> > Scott Eade
> > Backstage Technologies Pty. Ltd.
> > http://www.backstagetech.com.au
> >
> >
> > > From: "Roger I Martin PhD" <hy...@hypernexinc.com>
> > > Reply-To: "Turbine Developers List" <tu...@jakarta.apache.org>
> > > Date: Sat, 17 Aug 2002 08:13:30 -0400
> > > To: <tu...@jakarta.apache.org>
> > > Subject: maven enabled torque?
> > >
> > > Hi,
> > >
> > > I cvs'd jakarta-turbine-maven and jakarta-turbine-torque this morning.
Built
> > > maven the boot strap way successfully.
> > >
> > > The readme.txt that came from cvs'ing jakarta-turbine-torque says:
> > >
> > > Building the decoupled version of Torque from CVS is now very easy.
Torque
> > > has been Maven-enabled. Please refer to the Maven Getting Started
document
> > > for instructions on building. This document is available here:
> > >
> > > http://jakarta.apache.org/turbine/maven/getting-started.html
> > >
> > > I did this. Then
http://jakarta.apache.org/turbine/maven/start/use.html says:
> > >
> > > Congratulations! Now that you have installed Maven and/or integrated
with your
> > > project, you are now ready to start reaping the benefits of Maven. The
rest of
> > > this document will be a guided tour through the basic operation of
Maven's
> > > build system. You will learn how to build any of the following
Maven-enabled
> > > Turbine projects: Torque, Stratum, Fulcrum, and Turbine. The process
for each
> > > project is the identical thanks to Maven (as are the results).
> > >
> > > First, checkout the source for any of the above Turbine projects. If
you do
> > > not know how to do this, please refer to the CVS Repositories
document. For
> > > those familiar with the growing family of Jakarta projects, several of
the
> > > projects include all of the JAR files required to build and distribute
the
> > > projects in their CVS repositories. Maven eliminates this practice
altogether
> > > because it provides facilities to automatically download all
dependencies from
> > > one or more central repositories. Thus, before any Maven goal is
executed,
> > > Maven will automatically download all of the required dependencies
from the
> > > remote repositories defined by the ${maven.repo.remote} property.
> > >
> > > After Maven has automatically downloaded your dependencies, they are
stored in
> > > your local repository. Recall, Maven uses this directory to store all
JAR
> > > files. There are two exceptions: 1) non-distributable JARs will result
in a
> > > message pointing you to the location where you can download the JAR
yourself,
> > > and 2) JARs that don't exist in the local or remote repositories will
result
> > > in an error. In either case, you'll have to download those yourself
and
> > > manually place them in $MAVEN_HOME/repository. After you have
downloaded all
> > > of the dependent JARs, generating a JAR for a Maven-enabled Turbine
project is
> > > easy. Type the following:
> > >
> > > maven java:jar
> > > You'll notice that all of the code is compiled, and then unit tested,
before
> > > it is packaged into a JAR file. The unit tests generate reports that
are later
> > > parsed to create an HTML report that is part of the generated site
> > > documentation. The JAR file can also be automatically distributed.
> > >
> > > ...
> > >
> > > What I see is:
> > >
> > > __ __
> > > | \/ |__ Jakarta _ ___
> > > | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
> > > |_| |_\__,_|\_/\___|_||_| v. 1.0-b5-dev
> > >
> > > jakarta-turbine-torque (torque) 3.0-b4-dev
> > > C:\apache\jakarta-turbine-torque
> > >
> > > java:jar:
> > > [ERROR] INTERNAL ERROR
> > > [ERROR] Reference made to goal 'java:jar' which has no definition.
> > >
> > > Don't see any compiles, no nothing! For all the yadda such as
"Building the
> > > decoupled version of Torque from CVS is now very easy", "Torque
> > > has been Maven-enabled", "Congratulation!", "reaping the benefits",
> > > "generating a JAR for a Maven-enabled Turbine project is easy." and
"biggest
> > > bang for you buck ", thats it?
> > >
> > > May I suggest that all your documentation be stripped of the above
kinds of
> > > phrases? Documentation should never be cute or exuberant 'cause when
the
> > > results aren't cute or exuberant, any person or persons who has waded
through
> > > such documentation looking for some meat and not finding any, gets the
urge to
> > > strangle the documentation's author ;-)
> > >
> > > --Roger
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> > >
> >
> >
> > --
> > To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> > For additional commands, e-mail:
<ma...@jakarta.apache.org>
> --
> jvz.
>
> Jason van Zyl
> jason@apache.org
> http://tambora.zenplex.org
>
> In short, man creates for himself a new religion of a rational
> and technical order to justify his work and to be justified in it.
>
> -- Jacques Ellul, The Technological Society
>
>
> --
> To unsubscribe, e-mail:
<ma...@jakarta.apache.org>
> For additional commands, e-mail:
<ma...@jakarta.apache.org>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: maven enabled torque?
Posted by Jason van Zyl <ja...@zenplex.com>.
On Sat, 2002-08-17 at 08:53, Scott Eade wrote:
> Roger,
>
> I happened to be doing the exact same thing at the same time as you and ran
> into the same problem.
>
> It looks to me like maven is not finding maven.xml because it is not finding
> any of the goals ("maven -g" is pretty sparse).
>
> "ant -f build-legacy.xml" is next to useless and it still refers to the
> pre-maven-b4 "lib.repo" property.
>
> I'm wondering if the maven b5 distribution (as opposed to cvs head) will
> work.
The distribution should work and I just tried with clean checkouts of
both Maven and Torque and built successfully.
> Cheers,
>
> Scott
> --
> Scott Eade
> Backstage Technologies Pty. Ltd.
> http://www.backstagetech.com.au
>
>
> > From: "Roger I Martin PhD" <hy...@hypernexinc.com>
> > Reply-To: "Turbine Developers List" <tu...@jakarta.apache.org>
> > Date: Sat, 17 Aug 2002 08:13:30 -0400
> > To: <tu...@jakarta.apache.org>
> > Subject: maven enabled torque?
> >
> > Hi,
> >
> > I cvs'd jakarta-turbine-maven and jakarta-turbine-torque this morning. Built
> > maven the boot strap way successfully.
> >
> > The readme.txt that came from cvs'ing jakarta-turbine-torque says:
> >
> > Building the decoupled version of Torque from CVS is now very easy. Torque
> > has been Maven-enabled. Please refer to the Maven Getting Started document
> > for instructions on building. This document is available here:
> >
> > http://jakarta.apache.org/turbine/maven/getting-started.html
> >
> > I did this. Then http://jakarta.apache.org/turbine/maven/start/use.html says:
> >
> > Congratulations! Now that you have installed Maven and/or integrated with your
> > project, you are now ready to start reaping the benefits of Maven. The rest of
> > this document will be a guided tour through the basic operation of Maven's
> > build system. You will learn how to build any of the following Maven-enabled
> > Turbine projects: Torque, Stratum, Fulcrum, and Turbine. The process for each
> > project is the identical thanks to Maven (as are the results).
> >
> > First, checkout the source for any of the above Turbine projects. If you do
> > not know how to do this, please refer to the CVS Repositories document. For
> > those familiar with the growing family of Jakarta projects, several of the
> > projects include all of the JAR files required to build and distribute the
> > projects in their CVS repositories. Maven eliminates this practice altogether
> > because it provides facilities to automatically download all dependencies from
> > one or more central repositories. Thus, before any Maven goal is executed,
> > Maven will automatically download all of the required dependencies from the
> > remote repositories defined by the ${maven.repo.remote} property.
> >
> > After Maven has automatically downloaded your dependencies, they are stored in
> > your local repository. Recall, Maven uses this directory to store all JAR
> > files. There are two exceptions: 1) non-distributable JARs will result in a
> > message pointing you to the location where you can download the JAR yourself,
> > and 2) JARs that don't exist in the local or remote repositories will result
> > in an error. In either case, you'll have to download those yourself and
> > manually place them in $MAVEN_HOME/repository. After you have downloaded all
> > of the dependent JARs, generating a JAR for a Maven-enabled Turbine project is
> > easy. Type the following:
> >
> > maven java:jar
> > You'll notice that all of the code is compiled, and then unit tested, before
> > it is packaged into a JAR file. The unit tests generate reports that are later
> > parsed to create an HTML report that is part of the generated site
> > documentation. The JAR file can also be automatically distributed.
> >
> > ...
> >
> > What I see is:
> >
> > __ __
> > | \/ |__ Jakarta _ ___
> > | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
> > |_| |_\__,_|\_/\___|_||_| v. 1.0-b5-dev
> >
> > jakarta-turbine-torque (torque) 3.0-b4-dev
> > C:\apache\jakarta-turbine-torque
> >
> > java:jar:
> > [ERROR] INTERNAL ERROR
> > [ERROR] Reference made to goal 'java:jar' which has no definition.
> >
> > Don't see any compiles, no nothing! For all the yadda such as "Building the
> > decoupled version of Torque from CVS is now very easy", "Torque
> > has been Maven-enabled", "Congratulation!", "reaping the benefits",
> > "generating a JAR for a Maven-enabled Turbine project is easy." and "biggest
> > bang for you buck ", thats it?
> >
> > May I suggest that all your documentation be stripped of the above kinds of
> > phrases? Documentation should never be cute or exuberant 'cause when the
> > results aren't cute or exuberant, any person or persons who has waded through
> > such documentation looking for some meat and not finding any, gets the urge to
> > strangle the documentation's author ;-)
> >
> > --Roger
> >
> >
> >
> >
> >
> >
> >
> >
>
>
> --
> To unsubscribe, e-mail: <ma...@jakarta.apache.org>
> For additional commands, e-mail: <ma...@jakarta.apache.org>
--
jvz.
Jason van Zyl
jason@apache.org
http://tambora.zenplex.org
In short, man creates for himself a new religion of a rational
and technical order to justify his work and to be justified in it.
-- Jacques Ellul, The Technological Society
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: maven enabled torque?
Posted by John McNally <jm...@collab.net>.
On Sat, 2002-08-17 at 05:53, Scott Eade wrote:
> Roger,
>
> I happened to be doing the exact same thing at the same time as you and ran
> into the same problem.
>
> It looks to me like maven is not finding maven.xml because it is not finding
> any of the goals ("maven -g" is pretty sparse).
>
> "ant -f build-legacy.xml" is next to useless and it still refers to the
> pre-maven-b4 "lib.repo" property.
>
it is not useless. it is the main way i build torque to use within
scarab. the maven build of torque does not work for scarab.
john mcnally
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>
Re: maven enabled torque?
Posted by Scott Eade <se...@backstagetech.com.au>.
Roger,
I happened to be doing the exact same thing at the same time as you and ran
into the same problem.
It looks to me like maven is not finding maven.xml because it is not finding
any of the goals ("maven -g" is pretty sparse).
"ant -f build-legacy.xml" is next to useless and it still refers to the
pre-maven-b4 "lib.repo" property.
I'm wondering if the maven b5 distribution (as opposed to cvs head) will
work.
Cheers,
Scott
--
Scott Eade
Backstage Technologies Pty. Ltd.
http://www.backstagetech.com.au
> From: "Roger I Martin PhD" <hy...@hypernexinc.com>
> Reply-To: "Turbine Developers List" <tu...@jakarta.apache.org>
> Date: Sat, 17 Aug 2002 08:13:30 -0400
> To: <tu...@jakarta.apache.org>
> Subject: maven enabled torque?
>
> Hi,
>
> I cvs'd jakarta-turbine-maven and jakarta-turbine-torque this morning. Built
> maven the boot strap way successfully.
>
> The readme.txt that came from cvs'ing jakarta-turbine-torque says:
>
> Building the decoupled version of Torque from CVS is now very easy. Torque
> has been Maven-enabled. Please refer to the Maven Getting Started document
> for instructions on building. This document is available here:
>
> http://jakarta.apache.org/turbine/maven/getting-started.html
>
> I did this. Then http://jakarta.apache.org/turbine/maven/start/use.html says:
>
> Congratulations! Now that you have installed Maven and/or integrated with your
> project, you are now ready to start reaping the benefits of Maven. The rest of
> this document will be a guided tour through the basic operation of Maven's
> build system. You will learn how to build any of the following Maven-enabled
> Turbine projects: Torque, Stratum, Fulcrum, and Turbine. The process for each
> project is the identical thanks to Maven (as are the results).
>
> First, checkout the source for any of the above Turbine projects. If you do
> not know how to do this, please refer to the CVS Repositories document. For
> those familiar with the growing family of Jakarta projects, several of the
> projects include all of the JAR files required to build and distribute the
> projects in their CVS repositories. Maven eliminates this practice altogether
> because it provides facilities to automatically download all dependencies from
> one or more central repositories. Thus, before any Maven goal is executed,
> Maven will automatically download all of the required dependencies from the
> remote repositories defined by the ${maven.repo.remote} property.
>
> After Maven has automatically downloaded your dependencies, they are stored in
> your local repository. Recall, Maven uses this directory to store all JAR
> files. There are two exceptions: 1) non-distributable JARs will result in a
> message pointing you to the location where you can download the JAR yourself,
> and 2) JARs that don't exist in the local or remote repositories will result
> in an error. In either case, you'll have to download those yourself and
> manually place them in $MAVEN_HOME/repository. After you have downloaded all
> of the dependent JARs, generating a JAR for a Maven-enabled Turbine project is
> easy. Type the following:
>
> maven java:jar
> You'll notice that all of the code is compiled, and then unit tested, before
> it is packaged into a JAR file. The unit tests generate reports that are later
> parsed to create an HTML report that is part of the generated site
> documentation. The JAR file can also be automatically distributed.
>
> ...
>
> What I see is:
>
> __ __
> | \/ |__ Jakarta _ ___
> | |\/| / _` \ V / -_) ' \ ~ intelligent projects ~
> |_| |_\__,_|\_/\___|_||_| v. 1.0-b5-dev
>
> jakarta-turbine-torque (torque) 3.0-b4-dev
> C:\apache\jakarta-turbine-torque
>
> java:jar:
> [ERROR] INTERNAL ERROR
> [ERROR] Reference made to goal 'java:jar' which has no definition.
>
> Don't see any compiles, no nothing! For all the yadda such as "Building the
> decoupled version of Torque from CVS is now very easy", "Torque
> has been Maven-enabled", "Congratulation!", "reaping the benefits",
> "generating a JAR for a Maven-enabled Turbine project is easy." and "biggest
> bang for you buck ", thats it?
>
> May I suggest that all your documentation be stripped of the above kinds of
> phrases? Documentation should never be cute or exuberant 'cause when the
> results aren't cute or exuberant, any person or persons who has waded through
> such documentation looking for some meat and not finding any, gets the urge to
> strangle the documentation's author ;-)
>
> --Roger
>
>
>
>
>
>
>
>
--
To unsubscribe, e-mail: <ma...@jakarta.apache.org>
For additional commands, e-mail: <ma...@jakarta.apache.org>