Hi Will, > Could you clarify why this is needed?
Simple answer: _I_ want to use it until Velocity-1.5 and VelocityTools-1.2 gets released. At least my source won't work against the current ones up. :) > What's the benefit to the effort of uploading the latest dev version of > Velocity? Are there other maven-using projects that depend on having SVN > head? I don't know how many other maven-using projects there are that uses unreleased versions of Velocity, but they would all benefit from it. It doesn't have to be a once-every-commit activity, but it would be nice if recent changes were included. As an alternative (which I am using right now), you can set the dependency to Velocity 1.5 and VelocityTools 1.2 and override the jars with those compiled from the SVN repos. But I don't like that because the build get's more dependent on the local directory structure. ## Of course, I just noticed that I can set up a local repository and host the SNAPSHOTs there. Best regards, -- Shinobu -- Shinobu Kawai <[EMAIL PROTECTED]> --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
