Josh Lucas wrote:
>
> Ok, so one thing which I would really like to do with this mail is to
> generate some discussion about something other than Gump. That isn't to
> say that I don't want to include Gump in the future of Alexandria but I
> want to start with what is currently here and move on from there.
+1
> I would also like to make it clear that I'm not trying to 'take over'
> the project and steer it somewhere that people don't want it to go. I
> have some ideas which I think would be cool but there is also plenty of
> things in what is currently here to work on. Also, I'd love to hear
> from either Kevin Burton or Jeff Martin as to their thoughts on these
> things. I'm planning on dropping each of them a note to guage their
> thinking.
IMHO, Alexandria is desparately in need of someone to 'take over' the
project.
> According to the web site, Alexandria was created to:
>
> create a global documentation and source organization system to help
> people understand source code and to share code across projects.
>
> Personally, I think this goal shortchanges Alexandria and limits the use
> by others. I would much rather see Alexandria become a build/test
> system which can be easily integrated into existing projects. There
> would be individual Ant tasks for things like JXR, Changelogs and others
> which would be usable without any additional file creation. The
> task/components could also fit together to create something similar to
> the Gump idea of watching multiple projects.
+1. The reason why Gump is here is that it was envisioned that Alexandria
was going to grow into the direction you state. The hope was that any and
all code that currently exists in Gump, AntGump, and Maven would either be
absorbed or discarded in favor of a unified Alexandria code base.
The only artifacts expected to remain - in one form or another - is the
project definitions. I had some discussions with Jeff Martin about this a
while back, and made a number of changes as a result of these discussions.
> In order to get to the point where Alexandria has components which can
> be used, a decision has to be made to no longer support the idea of the
> XSD files and Castor. If others support this idea (if not, maybe I'll
> just put it under the proposal directory), here area a few things which
> I'll start with:
+1. Use of Castor by Alexandria is overkill (IMHO).
- Sam Ruby
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
