One thought I mentioned awhile ago on this list was that I would like to
have the ability to monitor multiple builds, say on different platforms
with different versions of the jdk. Similar to the way tinderbox from
mozilla is used. I have the mozilla toolchain here I work, but I would
like to move to a better system then a bunch of perl scripts. Don't get
me wrong, I love perl...prolley my best language, but I am interested in
what can be done with Alexandria in terms of a native java system.
Seems like a lot of people are using junit for a lot of the testing
needs, so that can be better integrated into the whole of alexandria.
But I digress, a central server type system that receives the build
information from various sources would be a big selling feature for me.
I don't know how others feel on that.
Josh, I applaude your efforts to revitalize this project and eagerly
await a list of tasks that I may contribute to.
Jesse
P.S. I would think that getting the demo of what currently exists
working on the main apache page would be pretty important...I for one
have not even seen this thing working. Could be what I mention above
exists.. :)
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.
>
> 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.
>
> 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.
>
> 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) Take stock of what is currently here
> 2) Starting with the JXR task, begin to componentize other pieces
> 3) Redocument the new path and the new ideas
> 4) Figure out the best way to move someone from 'old' Alexandria to the
> new thinking
>
> Ok, I think this mail gives the list enough things to discuss. I look
> forward to your feedback.
>
>
>
> josh
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: [EMAIL PROTECTED]
> For additional commands, e-mail: [EMAIL PROTECTED]
>
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
