Mailing-List: contact commons-dev-help@jakarta.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Jakarta Commons Developers List" <commons-dev@jakarta.apache.org>
Date: Sun, 3 Nov 2002 20:29:40 -0500
Message-Id: <200211040129.gA41Tesf025426@copa.pajato.com>
From: Paul Michael Reilly <pmr@pajato.com>
To: martin.cooper@tumbleweed.com
CC: commons-user@jakarta.apache.org, commons-dev@jakarta.apache.org
In-reply-to: <7382FCA44E27D411BD4A00508BD68F95053CD522@pigeon.tumbleweed.com>
	(martin.cooper@tumbleweed.com)
Subject: Re: [jelly] Building from CVS sources
Reply-to: pmr@pajato.com
References: <7382FCA44E27D411BD4A00508BD68F95053CD522@pigeon.tumbleweed.com>

 > > The README says that Jelly is built using Ant and Maven and to just
 > > invoke ant to build it.  I tried that and got many compilation
 > > errors.  But what bothers me is that ant will find build.xml and
 > > maven is not in the picture.  So why does the README even mention
 > > Maven?
 > 
 > Jelly should be buildable by running either Ant *or* Maven, although Maven
 > is the preferred tool. To build using Ant, type 'ant'; to build using Maven,
 > type 'maven'.

Sounds like your sentence should replace the content of the README.
Can you take care of committing a fix for the README file?

Using `maven' I get:

[pmr@copa jelly]$ maven
 __  __
|  \/  |__ Jakarta _ ___
| |\/| / _` \ V / -_) ' \  ~ intelligent projects ~
|_|  |_\__,_|\_/\___|_||_|   v. 1.0-beta-7

/storage/home/pmr/projects/jakarta-commons-sandbox/jelly

[ERROR] BUILD FAILED
[ERROR] Goal "java:jar" does not exist in this project.
Total time:  13 seconds

[pmr@copa jelly]$


Using `ant' has a lot more problems.  I'll defer reporting those till
later.

 > > 
 > > I have a suspicion that build.xml is out of date wrt the jar files
 > > that one needs in order to build Jelly.  Could this be correct?
 > > Please tell me I'm missing some fundamental piece of information.
 > 
 > Yes, that's possible. The Ant build.xml file is generated by Maven, so if
 > somebody made changes to the Maven build file, but forgot to regenerate the
 > Ant build file and check it in, you might see the kind of thing you are
 > seeing.

If the Ant build.xml file is generated by Maven then perhaps it
should be removed from CVS, or a comment added to the generation that
indicates to someone trying to read and contribute to Jelly might
have a clue.  Can you commit a fix for this too?

How does Maven generate the build.xml file?  I don't seen anything
in the .../jelly/maven.xml file.  Am I looking in the right place?

 > I would recommend using Maven instead of Ant - then you'll avoid any issues
 > like this.

I must be doing something basically wrong.  Here's what I did on my
RedHat 8.0 system running Sun's 1.4.1 JVM:

1) got maven-1.0-beta-7 and installed it.
2) added the beta-7 maven bin directory to my PATH env variable.
3) set MAVEN_HOME to the root of the beta-7 tree where I installed it.
4) used anonymous CVS access to get the latest Jelly
(jakarta-commmons-sandbox) sources.
5) executed maven like above.

Thanks,

-pmr

--
To unsubscribe, e-mail:   <mailto:commons-dev-unsubscribe@jakarta.apache.org>
For additional commands, e-mail: <mailto:commons-dev-help@jakarta.apache.org>