commons-sandbox/vfs Failure

[email protected]
Newsgroups gmane.comp.jakarta.alexandria.devel
Message-ID <OF7A6B4772.091B2631-ONCA256C7D.00128A48-CA256C7D.0013796A@multitask.com.au>
Sam Ruby Writes:
> dIon Gillard wrote:

>  >> I believe that the information that a pure bootstrapping approach
>  >> provides is quite valuable.
>  > I agree.

>  >> I don't know how to get this dones across all of the various
>  >> codebases, but I am willing to do my part.  Are there maven and/or
>  >> centipede developers out there who share this goal?
>  > I'm happy to do my part.

> dIon, can you take a look at 
> http://cvs.apache.org/builds/gump/2002-11-24/commons-vfs.html ?  This 
> built successfully on 2002-11-20, but failed on 2002-11-21.
Sure...I'm talking to Adam about how he managed to do it now :)

> It seems that the build.xml is generated, and has a hardcoded path in it 


> that makes no sense on my Linux box.  I could override it in the project 


> definition, but that too is generated and in the jakarta-commons/vfs cvs 


> tree.

> One solution would be to correct the maven.xml and/or maven itself and 
> check in a corrected build.xml and/or gump.xml.
Once I know what the cause is, I'll fix it in Maven.

> Another solution would be to ignore the generated gump.xml and construct 


> one by hand that works, perhaps checking it into gump/project directory.

> What would you suggest?

I'd prefer that it gets fixed in Maven.


> P.S.  To compound this problem, there was a problem whereby the nag 
> messages were not being sent for this component.  This is now fixed.
Is this because of the descriptor?
--
dIon Gillard, Multitask Consulting
Blog:      http://www.freeroller.net/page/dion/Weblog
Work:      http://www.multitask.com.au
lmpx.com only provides a reader for public news (NNTP) servers. It is not affiliated with the servers or forums shown here and is not responsible for the content of articles, which is written by their respective authors.