Proposal for BATCH-1674

[snicoll]

Candidate fix for BATCH-1674

[dsyer]

Stephane, thanks for the suggestion. Which dependencies actually require these repositories?

I'm not sure if this is the best solution because in principle we want to keep repository declarations out of the public poms in Maven Central (best practice for public libraries). I could imagine maybe adding the declarations to a profile. Maybe we could figure out a way to change the profile activation when the pom is deployed? (In fact I'm not sure there isn't already a "bootstrap" profile with repository declarations in it - I agree that it is nice to build out of the box, so activation is something I would like to hear your views on.)

[snicoll]

From what I recall, one repository was necessary for the springsource's bundler plugin. The other repository was needed for the tool you use to generate SQL files (vpp or something).

Agreed, repository declarations should go out of the public pom because once they are in, they affect how Maven resolve all dependencies for the project. Central currently rejects poms containing such repositories definition.

I would go for

1. a profile that you could activate if needed
2. a page on the website declaring the repositories you want. I had to search a bit to find them

There is no nice way to handle this issue at the moment as far as I know.

[dsyer]

You can use -P bootstrap as per the instructions: http://static.springsource.org/spring-batch/building.html. Does that not work? I don't think we can do much better.

[snicoll]

yep, I agree.