I've noticed that the pom.xml generated by the upload task and placed in the target maven repository doesn't include dependency information, which is kind of a pain when my maven-using colleagues want to use libraries I've built with buildr and they have to go and list all of my dependencies explicitly. Can the pom generation include a list of artifacts and, if so, how can I specify it? I'd be fine with handcrafting a pom.xml and having the task use that instead of a generated one but doing it in the buildfile would be nicer.

Thanks,
 Jeremy

Reply via email to