[PATCH] JxrTask - a new Hope

[josh lucas <lu...@collab.net>]

So, I have been trying to make sense of the current Alexandria proper
code base and trust me, it wasn't easy.  So, I've written a new JxrTask
which doesn't have anything to do with Castor-related API's or xml
description of project files.  I realize this isn't exactly compatible
with the existing AlexandriaTask but I think that's ok.  

Unfortunately, some of my code changes will break what is there.  I
don't really know what to do about this because Alexandria itself has
been dead for quite a bit and the only 'stuff' going on right now is
Gump.  Because of that, I'm not sure how to handle this or actually who
I'm really sending this into since I've sent in other Alexandria-related
patches which haven't been committed.  I have a feeling that Sam doesn't
feel comfortable committing there and that's fine.  So what do we do ?

Anyways, here are my patches, including a patch to the build.xml to show
how easy running the task is.

One caveat of the task is that it is made more for individual projects
to run as opposed to a large group of projects.  The reason for this is
because now that the xml files are taken out of play, we don't have
access to the src directories of all the projects.  I don't necessarily
think that it is a bad thing since you could just output all of the html
files to a central location and have the same effect.


josh

Re: [PATCH] JxrTask - a new Hope

[josh lucas <lu...@collab.net>]

It would help to actually send the new file as well...


josh

On Thu, 2001-08-23 at 18:57, josh lucas wrote:
> So, I have been trying to make sense of the current Alexandria proper
> code base and trust me, it wasn't easy.  So, I've written a new JxrTask
> which doesn't have anything to do with Castor-related API's or xml
> description of project files.  I realize this isn't exactly compatible
> with the existing AlexandriaTask but I think that's ok.  
> 
> Unfortunately, some of my code changes will break what is there.  I
> don't really know what to do about this because Alexandria itself has
> been dead for quite a bit and the only 'stuff' going on right now is
> Gump.  Because of that, I'm not sure how to handle this or actually who
> I'm really sending this into since I've sent in other Alexandria-related
> patches which haven't been committed.  I have a feeling that Sam doesn't
> feel comfortable committing there and that's fine.  So what do we do ?
> 
> Anyways, here are my patches, including a patch to the build.xml to show
> how easy running the task is.
> 
> One caveat of the task is that it is made more for individual projects
> to run as opposed to a large group of projects.  The reason for this is
> because now that the xml files are taken out of play, we don't have
> access to the src directories of all the projects.  I don't necessarily
> think that it is a bad thing since you could just output all of the html
> files to a central location and have the same effect.
> 
> 
> josh
> 
> 
> --=-L3lTi4R2GXKGGk/drkY9
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: alexandria-dev-unsubscribe@jakarta.apache.org

Re: [PATCH] JxrTask - a new Hope

[Daniel Rall <dl...@finemaltcoding.com>]

josh lucas <lu...@collab.net> writes:

> So, I have been trying to make sense of the current Alexandria proper
> code base and trust me, it wasn't easy.  So, I've written a new JxrTask
> which doesn't have anything to do with Castor-related API's or xml
> description of project files.  I realize this isn't exactly compatible
> with the existing AlexandriaTask but I think that's ok.  

I think it's okay, too.  If no one is actively maintaining the code
base, it would be great to see someone step up and take it over.

> Unfortunately, some of my code changes will break what is there.  I
> don't really know what to do about this because Alexandria itself has
> been dead for quite a bit and the only 'stuff' going on right now is
> Gump.  Because of that, I'm not sure how to handle this or actually who
> I'm really sending this into since I've sent in other Alexandria-related
> patches which haven't been committed.  I have a feeling that Sam doesn't
> feel comfortable committing there and that's fine.  So what do we do ?

IMO, the old codebase should be branched, and the current repository
should be allowed to be revitalized by Josh.

---------------------------------------------------------------------
To unsubscribe, e-mail: alexandria-dev-unsubscribe@jakarta.apache.org
For additional commands, e-mail: alexandria-dev-help@jakarta.apache.org