[EMAIL PROTECTED] wrote:
I want to use Avalon in a servlet and database based application, and from reading the docs, it seemed that Fortress is the appropriate tool. However, I'm having trouble getting it.
I first tried grabbing the cvs modules so I could build it myself - no luck, CVS responds with a 'permission denied' response when I try to grab it using my apache account.
you can only use non-public cvs for those modules you're a committer to.
When I try using 'anoncvs' I'm told there's no such user. Just for the record, I am able to checkout other projects, such as jakarta-site2 and jmeter.
Can you be more precise as to the error message?
the below:
bash-2.05b$ cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic login (Logging in to [EMAIL PROTECTED]) CVS password: bash-2.05b$ cvs -d :pserver:[EMAIL PROTECTED]:/home/cvspublic co avalon
works for me.
So then I tried grabbing source releases, but there appears to be no less than a billion separate files. Is this necessary?
uhm....yes!
How do I know what I need?
that depends on what you want to do. What do you want to do?
So, what's the secret to getting fortress and everything it needs to function?
http://avalon.apache.org/download.cgi provides sources and binaries. The source distributions for fortress and most other excalibur projects are not geared for easy recompilation, but rather for getting view access to the sources (handy for use in IDEs etc). The binaries normally suffice.
To recompile fortress from sources, you will indeed need to download quite a few dependencies as well unless you do a cvs checkout. A list of fortress 1.0 dependencies can be found from the maven.xml file CVS:
<dependency>
<id>avalon-framework</id>
<version>4.1.4</version>
<groupId>framework</groupId>
</dependency>
<dependency>
<id>logkit</id>
<version>1.2.2</version>
</dependency>
<dependency>
<id>commons-collections</id>
<version>2.1</version>
</dependency>
<dependency>
<id>concurrent</id>
<version>1.3.1</version>
</dependency>
<dependency>
<id>excalibur-instrument</id>
<version>1.0</version>
</dependency>
<dependency>
<id>excalibur-instrument-manager</id>
<version>1.0</version>
<groupId>excalibur-instrument-manager</groupId>
</dependency>
<dependency>
<id>excalibur-instrument-manager-interfaces</id>
<version>1.0</version>
<groupId>excalibur-instrument-manager</groupId>
</dependency>
<dependency>
<id>excalibur-event</id>
<version>1.0.1</version>
</dependency>
<dependency>
<id>bcel</id>
<version>5.1</version>
</dependency>
<dependency>
<id>excalibur-logger</id>
<version>1.0.1</version>
</dependency>
<dependency>
<id>excalibur-sourceresolve</id>
<version>1.0.1</version>
</dependency>
<dependency>
<id>excalibur-lifecycle</id>
<version>1.0</version>
</dependency>
<dependency>
<id>xml-apis</id>
<version>2.0.2</version>
</dependency> <!-- test -->
<dependency>
<id>excalibur-i18n</id>
<version>1.0</version>
</dependency>
<dependency>
<id>xalan</id>
<version>2.5.1</version>
</dependency>
<dependency>
<id>xerces</id>
<version>2.3.0</version>
</dependency> <!-- circular! -->
<dependency>
<id>avalon-fortress-tools</id>
<version>1.1-dev</version>
<groupId>avalon-fortress</groupId>
</dependency> <!-- dependencies for tools -->
<dependency>
<id>qdox</id>
<version>1.2</version>
</dependency>
<dependency>
<id>ant</id>
<version>1.5.1</version>The hassle of figuring all this out was solved soon after the fortress 1.0 release by moving to maven, so building from current cvs is about as simple as:
cd ~/cvs/avalon/fortress/container maven dist
For recompiling the actual 1.0 release, you will need to do a cvs checkout of the avalon-excalibur cvs as of about 2 months ago. Getting exactly the same result as with the official releases will be nontrivial.
If you can tell us what exactly you need to do we can help :D
cheers!
- Leo
--------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
