jakarta-cactus-user mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Robertson, Jason" <Jason.Robert...@acs-inc.com>
Subject RE: Build Experience Feedback
Date Fri, 13 Sep 2002 15:40:27 GMT
>Thus, if you need to simply build the framework, you can cd in
>framework/ and type "ant dist". If you need the cactus ant tasks, cd in
>antttasks/ and type "ant dist". If you need to simply run the sample
>tests, cd in sample-servlet and type "ant test", etc.

I guess I did notice this was a possibility, but then there was another
build.properties.sample that needed to be modified in that subdirectory,
which seemed like too much of a pain. Is there any way from within the
subprojects to use the one at the root and make this the only one that
exists? Or is there different info in each (I haven't looked)? 

That would solve the problem for me. 

Or actually, could I just copy the one from the root into each? Again, I
guess that depends on the info in each.

Hmmm, if only there were a build tutorial document... ;)

Jason

-----Original Message-----
From: Vincent Massol [mailto:vmassol@octo.com]
Sent: Friday, September 13, 2002 2:37 AM
To: 'Cactus Users List'
Subject: RE: Build Experience Feedback


Thanks Jason,

That's all very useful comments. I really appreciate that. See below my
comments.

> -----Original Message-----
> From: Robertson, Jason [mailto:Jason.Robertson@acs-inc.com]
> Sent: 12 September 2002 22:48
> To: 'Cactus Users List'
> Subject: Build Experience Feedback
> 
> Just a few observation from a guy starting from ground zero trying to
> build
> Cactus (my last build from scratch was around the 1.3dev timeframe):
> 
> The clover.jar definition is way below other jar definitions (on one
hand
> it
> might be nicer if they were together, but keep reading), and the
> clover.jar
> file *must* exist regardless of if you're using clover or not. (If it
> doesn't exist there's a copy that fails.) I guess if the copy gets
fixed
> then you don't have to move up the definition, keeping it with
> clover.enabled seems reasonable.
> 

ok, I'll look into that.

> Next, I got this (I think in the doc target):
> 
> BUILD FAILED
> file:C:/java/jakarta-cactus-src-20020911/documentation/build.xml:200:
> C:\java\ja
> karta-cactus-src-20020911\documentation\docs\xdocs\misc not found.
> 
> Looks like the directory should be created first? But with info from
the
> next issue it seems like it's an empty directory, so maybe it should
be
> pruned from CVS?
> 

strange. I'll look into that too.

> So I then created the directory by hand and got this:
> 
> doc:
>      [copy] Copied 1 empty directory to
> C:\java\jakarta-cactus-src-20020911\docu
> mentation\target\doc\misc
> [stylebook] java.lang.NoClassDefFoundError:
org/apache/stylebook/StyleBook
> [stylebook] Exception in thread "main"
> 
> This I assume is the ant "stylebook" task, which I don't have. Is
there
> any
> documentation of all external stuff that is needed to do a full
compile? I
> did a quick look in a few files but found nothing.

Actually there is. You have 2 options:
- get the prepackaged Ant in the cactus download area (it contains all
the needs libraries) - this is really the easiest.
- there is a Ant howto on the web site with some information as to what
jars you need to drop in anthome/lib
(http://jakarta.apache.org/cactus/howto_ant_install.html). However,
that's for the sample application

In the todo there is an entry that says "write a tutorial that explains
how to build cactus from source". I guess, it is now time to do that ...
so far no one had asked ... :-)

> 
> I've since figured out I only needed to do "ant run.framework" to do
what
> I
> need to do, and this was by examining the build.xml file. BTW, it says
at
> the top of build.xml to do "ant -projecthelp" which I did but I didn't
> feel
> this information was very useful as it was only the "main" targets.

There is a good reason for that. You are not "allowed" to call the other
targets. What you need to understand is that all directories in the top
level cactus directory are subprojects in their own right.

Thus, if you need to simply build the framework, you can cd in
framework/ and type "ant dist". If you need the cactus ant tasks, cd in
antttasks/ and type "ant dist". If you need to simply run the sample
tests, cd in sample-servlet and type "ant test", etc.

The top level one is simply a global wrapper to perform a release (build
it all).

This needs explaining in the building cactus from source tutorial.

> 
> And actually, I ended up making my own run.framework.jar that just
does
> the
> jar task for the framework. Shouldn't this be a little easier to do? I
> don't
> want to build all the docs and such during development - I just want
to
> build the jar.

See above.

> 
> None of this is major stuff, except maybe needing to figure out all
the
> external stuff that is necessary to build, but I thought I'd give the
> feedback.
> 

Thanks Jason. I'll prepare the tutorial soon ... :-)

-Vincent

> Jason
> 
> --
> To unsubscribe, e-mail:   <mailto:cactus-user-
> unsubscribe@jakarta.apache.org>
> For additional commands, e-mail: <mailto:cactus-user-
> help@jakarta.apache.org>



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

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


Mime
View raw message