Hi Jukka, Welcome to Maven Central and manage the com.adobe artifacts.
The easiest way to control com.adobe artifacts in central is using our OSS Repository Hosting Service [1]. So once you create a ticket, we will prepare repository for you and make sure nobody else deploy com.adobe artifacts into maven central. Regarding the currently uploaded BlazeDS artifacts in central, sorry we can't simply delete them or place a pointer to your official download page. It's because: * It will break people's build, and we have no idea how many people are using them. * These artifacts were already mirrored a lot. So, in principle we don't delete/change any file in central, unless the artifact is totally wrong. People usually need to deploy a new version if they find something wrong with their deployed artifacts. So you can deploy a new version as well. [1] https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide On Thu, May 19, 2011 at 6:05 AM, Jukka Zitting <[email protected]> wrote: > Hi Ryan, > > From Ryan Heaton: > > Just for the record, I'm glad that Adobe is taking this on and > > I'd be happy to relinquish my "unofficial maintainer" role. > > Great to hear that, and thanks for your work so far! > > > Why don't you guys just open up a JIRA issue explaining the request? > > I'd be happy to comment on it with my approval. > > We'll probably do that soon. I wanted to contact repo-maintainers@ first > to figure out what's the best way to proceed with this. > > Best regards, > > Jukka Zitting > > -- - Juven Xu
