Gentlemen,

First off, if there is any blame to go around, then it mine.  I'm the one
who committed the code, Niclas only submitted patches.  It's my
responsibility to go through them.  That is the whole difference between
committers and contributors.

Secondly, I think that Gump integration is crucial for the long term success
of Fulcrum.  Fulcrum by it's very nature as a collection of components means
it has lots of dependencies.  And with out a system like Gump providing a
Contious Integration environment, over time, Fulcrum will become a
collecition of out of date components that no one will want to use.

I am afraid I took a bit of a "playground" approach to the Fulcrum
components.  It was my first time learning Gump, and so I was making changes
to Fulcrum builds that maybe where not appropriate.  For example the
javamail change in dependency from 1.3.1 to 1.3.  I will file a request with
Gump to get the 1.3.1 version installed.

A couple of things..   An issue has been opened up in Maven
(http://jira.codehaus.org/browse/MAVEN-1472) to create a document
standardizing on some groupId/artifactId names.  Specifially those that
aren't available online.  The two that come to mind are Javamail and
Activiation.  Both of these are setup differently by different groups.  But,
if we are using Maven builds, we should look to following what will become
the "suggested" standard.  This will over time lower the bar to entry for
new folks in turbine land..

Currently Excaliber and Avalon use: activation:activation for the
Activiation jar, I think we should follow along.  The other suggestion is
javamail:mail for the javamail jar.  Again, while it may be a change for us,
it gets us into line with other projects.

At this point I am working on getting everythign sorted out, including some
recent errors that I let into the project.xml files.  Once I have things
workign right, and Gump building nicely, then I'll be interested in calling
for a vote for some of the components to be released officially.

Eric



---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]

Reply via email to