dIon Gillard wrote:
I'm not sure how it was generated, but a version of build.xml was checked in a few hours ago into commons-vfs... one that works!Once I know what the cause is, I'll fix it in Maven.
Right answer!I'd prefer that it gets fixed in Maven.
My long term vision is that some sort of minimal core of maven be built, followed by components that are normally built using maven being built using the version of maven that was just built.
This will require some cooperation as I would like such builds to also use the latest version of all dependencies instead of the ones the version that the developer declared. There will also be ordering dependencies to deal with.
But that is long term. If we work together and get one or two additional projects to build a week, I'll be pleased.
Note: after tomorrow, I'm going offline until Sunday.
Nope, that was a pure Gump bug. Triggered by the begin and end tags of the nag entry being on separate lines - perfectly legal, but never encountered before.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?
- Sam Ruby
--
To unsubscribe, e-mail: <mailto:[EMAIL PROTECTED]>
For additional commands, e-mail: <mailto:[EMAIL PROTECTED]>
