You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@avalon.apache.org by Berin Loritsch <bl...@apache.org> on 2003/06/16 19:10:47 UTC
Maven Integration Quick Study (was Re: New Event needed....)
Berin Loritsch wrote:
> One thing the changeover to Avalon/Fortress proved is that we need a new
> Event released, or at least a snapshot released. The new failure
> handler is what is causing the maven build to crash, which makes
> development difficult.
>
Ok, I have found out that in the short period of time since Fortress was
released that a few things were altered in dependent libraries which
caused compilation issues in Fortress:
1) Excalibur-Logger and its Log4J integration. Some of the integration
changes were specific to the new Excalibur-Logger.
2) Avalon Framework. Framework's DefaultConfigurationBuilder has a new
method so that we can provide a "SystemID" value so that error
messages are a little more friendly.
3) Excalibur Event and the CommandFailureHandler.
This is all well and good, but with Maven it adds some complications.
In order for things to continue to build, we need to upload a snapshot
jar, and modify the project.xml to depend on that snapshot.
There are three things that come out of this:
1) We know which dependent libraries need to be updated (i.e. the ones
with a snapshot version [yyyymmdd])
2) The new version of Fortress is dependent on these new versions of
the libraries.
3) Maven encourages you to only work with released JARs instead of the
latest and greatest--although you can work around it easily enough).
If we are all OK with this, I would like to remind all that we need to
be careful with how many JARs we force our users to upgrade at one time.
Lastly, what about creating the "BIG JAR" where all of Fortress's
dependencies were included?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Maven Integration Quick Study (was Re: New Event needed....)
Posted by Leo Simons <le...@apache.org>.
Berin Loritsch wrote:
> Can we do [fortress-complete with snapshots]?
sure! (at least I cannot think of a reason why it would stop working)
- LSD
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Maven Integration Quick Study (was Re: New Event needed....)
Posted by Berin Loritsch <bl...@apache.org>.
Leo Simons wrote:
>
>> Lastly, what about creating the "BIG JAR" where all of Fortress's
>> dependencies were included?
>
>
> what about it?
>
Can we still do it?
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
Re: Maven Integration Quick Study (was Re: New Event needed....)
Posted by Leo Simons <le...@apache.org>.
Berin Loritsch wrote:
> Berin Loritsch wrote:
>
>> One thing the changeover to Avalon/Fortress proved is that we need a new
>> Event released, or at least a snapshot released. The new failure
>> handler is what is causing the maven build to crash, which makes
>> development difficult.
>
> Ok, I have found out that in the short period of time since Fortress was
> released that a few things were altered in dependent libraries which
> caused compilation issues in Fortress:
>
> In order for things to continue to build, we need to upload a snapshot
> jar, and modify the project.xml to depend on that snapshot.
I think there's functionality in maven for "SNAPSHOT" dependency of some
kind. Not exactly sure how that works. We don't actually need to upload
a snapshot: the alternative is to install locally using 'jar:install'. A
quick check of
http://maven.apache.org/reference/plugins/jar/goals.html
revealed a 'jar:install-snapshot'. When excalibur is mavenized I believe
this might look like:
cd ~/cvs/avalon-excalibur
cvs -z3 up -P -d
# reactor that does jar:install-snapshot for all subprojects
maven avalon:install-snapshots
cd ~/cvs/avalon
# reactor that does jar:install-snapshot for all subprojects
maven avalon:install-snapshots
additional docs are at
http://maven.apache.org/reference/user-guide.html#Overriding%20Stated%20Dependencies
http://maven.apache.org/reference/user-guide.html#Using%20SNAPSHOT%20Dependencies
> There are three things that come out of this:
>
> 1) We know which dependent libraries need to be updated (i.e. the ones
> with a snapshot version [yyyymmdd])
>
> 2) The new version of Fortress is dependent on these new versions of
> the libraries.
>
> 3) Maven encourages you to only work with released JARs instead of the
> latest and greatest--although you can work around it easily enough).
yep. By making it painful to have minor version coupling you reduce
coupling :D
> Lastly, what about creating the "BIG JAR" where all of Fortress's
> dependencies were included?
what about it?
- LSD
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org
RE: Maven Integration Quick Study (was Re: New Event needed....)
Posted by "Noel J. Bergman" <no...@devtech.com>.
> If we are all OK with this, I would like to remind all that we need to
> be careful with how many JARs we force our users to upgrade at one time.
True, but most importantly, we really need a unified release, and less of a
Chinese menu. Just tell us that for a particular container, the release
includes the following jars: ...
--- Noel
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@avalon.apache.org
For additional commands, e-mail: dev-help@avalon.apache.org