To make clear to all maven users, this is the current repository policy:
We don't allow pom changes that can alter reproducibility, which means DEPENDENCIES IN POMS WILL NOT BE CHANGED. The repo is only a way to distribute other people work. We don't repackage their work, only exceptions are for distribution of sources or javadocs when the original project don't provide them. You CAN NOT PROVIDE YOUR OWN BUILT VERSION OF ANOTHER PROJECT. As an example if fop adds anything to he manifest that you don't like or think is wrong it's not our problem, ask them if they want to change. You can always as for an upload of anything you want to a group under your project/domain name, as long as the license allows it. Eg. I want to provide my own version of fop, created by my project hosted in foobar.org. I can request an upload under org.foobar group. I can upload to org.foobar anything I want as long as it follows the maven conventions. In case a pom is clearly bad, broken or unmanageable, a new pom can be uploaded for users convenience, under same version appending -1. The pom description must clearly state it's just for maven users convenience and the originating project must be asked to provide the pom improvements in next version (in case they provided the bad one) Eg. http://repo1.maven.org/maven2/groovy/groovy/1.0-jsr-05-1/ -- I could give you my word as a Spaniard. No good. I've known too many Spaniards. -- The Princess Bride --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
