You are viewing a plain text version of this content. The canonical link for it is here.
Posted to repo-maintainers@maven.apache.org by Jukka Zitting <jz...@adobe.com> on 2011/05/18 23:44:16 UTC
Managing com.adobe on Maven Central
Hi,
I work for Adobe and would like to figure out how we can best start managing the com.adobe space on Maven central [1].
Currently the com.adobe space contains some bits and pieces based on upload requests made by our users (including myself before I joined Adobe), and we’d now like to take better control over this space. What would be the best way to do this?
As a related matter, the BlazeDS artifacts uploaded from Ryan Heaton's repository [2] are neither up to date nor approved by Adobe. We appreciate the initiative, but at this point we'd appreciate if the currently uploaded BlazeDS artifacts could be replaced with pointers to the official BlazeDS download page [3]. How should we do this?
[1] http://repo1.maven.org/maven2/com/adobe/
[2] http://jira.codehaus.org/browse/MAVENUPLOAD-1998
[3] http://opensource.adobe.com/wiki/display/blazeds/Downloads
Best regards,
Jukka Zitting
Re: Managing com.adobe on Maven Central
Posted by Damon Cooper <dc...@adobe.com>.
Yes, nothing we can do about that except change the licensing terms to prevent redistribution of the original distributions....
On May 19, 2011, at 7:53 AM, "Carlos Sanchez" <ca...@apache.org> wrote:
> Based on previous experiences if you don't distribute them officially
> in a Maven repo people will do themselves, creating separate Maven
> repos that will have different metadata and versions.
> Other people will relay on them for convenience, instead of
> downloading from your website and putting them in their maven repos by
> hand.
>
> That happened before at least for Sun, JBoss, Google,...
>
>
> On Thu, May 19, 2011 at 1:34 PM, Damon Cooper <dc...@adobe.com> wrote:
>> Hi, unfortunately we will not be updating the BlazeDS bits there, as the only place we distribute the builds is from our website, and that is a conscious business decision.
>>
>> So they will remain stale on the repo, which means users are using bits with security holes, etc.
>>
>> But if that's your decision, that's fine.
>>
>> On May 19, 2011, at 3:50 AM, "Carlos Sanchez" <ca...@apache.org> wrote:
>>
>>> You'd need to create your own repository for com/adobe/* and then work
>>> on sync'ing it with central through Sonatype.
>>>
>>> You can't/shouldn't remove anything from central, people already have
>>> local copies.
>>>
>>>
>>> On Wed, May 18, 2011 at 11:44 PM, Jukka Zitting <jz...@adobe.com> wrote:
>>>> Hi,
>>>>
>>>> I work for Adobe and would like to figure out how we can best start managing the com.adobe space on Maven central [1].
>>>>
>>>> Currently the com.adobe space contains some bits and pieces based on upload requests made by our users (including myself before I joined Adobe), and we’d now like to take better control over this space. What would be the best way to do this?
>>>>
>>>> As a related matter, the BlazeDS artifacts uploaded from Ryan Heaton's repository [2] are neither up to date nor approved by Adobe. We appreciate the initiative, but at this point we'd appreciate if the currently uploaded BlazeDS artifacts could be replaced with pointers to the official BlazeDS download page [3]. How should we do this?
>>>>
>>>> [1] http://repo1.maven.org/maven2/com/adobe/
>>>> [2] http://jira.codehaus.org/browse/MAVENUPLOAD-1998
>>>> [3] http://opensource.adobe.com/wiki/display/blazeds/Downloads
>>>>
>>>> Best regards,
>>>>
>>>> Jukka Zitting
>>>>
>>>>
>>
Re: Managing com.adobe on Maven Central
Posted by Carlos Sanchez <ca...@apache.org>.
Based on previous experiences if you don't distribute them officially
in a Maven repo people will do themselves, creating separate Maven
repos that will have different metadata and versions.
Other people will relay on them for convenience, instead of
downloading from your website and putting them in their maven repos by
hand.
That happened before at least for Sun, JBoss, Google,...
On Thu, May 19, 2011 at 1:34 PM, Damon Cooper <dc...@adobe.com> wrote:
> Hi, unfortunately we will not be updating the BlazeDS bits there, as the only place we distribute the builds is from our website, and that is a conscious business decision.
>
> So they will remain stale on the repo, which means users are using bits with security holes, etc.
>
> But if that's your decision, that's fine.
>
> On May 19, 2011, at 3:50 AM, "Carlos Sanchez" <ca...@apache.org> wrote:
>
>> You'd need to create your own repository for com/adobe/* and then work
>> on sync'ing it with central through Sonatype.
>>
>> You can't/shouldn't remove anything from central, people already have
>> local copies.
>>
>>
>> On Wed, May 18, 2011 at 11:44 PM, Jukka Zitting <jz...@adobe.com> wrote:
>>> Hi,
>>>
>>> I work for Adobe and would like to figure out how we can best start managing the com.adobe space on Maven central [1].
>>>
>>> Currently the com.adobe space contains some bits and pieces based on upload requests made by our users (including myself before I joined Adobe), and we’d now like to take better control over this space. What would be the best way to do this?
>>>
>>> As a related matter, the BlazeDS artifacts uploaded from Ryan Heaton's repository [2] are neither up to date nor approved by Adobe. We appreciate the initiative, but at this point we'd appreciate if the currently uploaded BlazeDS artifacts could be replaced with pointers to the official BlazeDS download page [3]. How should we do this?
>>>
>>> [1] http://repo1.maven.org/maven2/com/adobe/
>>> [2] http://jira.codehaus.org/browse/MAVENUPLOAD-1998
>>> [3] http://opensource.adobe.com/wiki/display/blazeds/Downloads
>>>
>>> Best regards,
>>>
>>> Jukka Zitting
>>>
>>>
>
Re: Managing com.adobe on Maven Central
Posted by Damon Cooper <dc...@adobe.com>.
Hi, unfortunately we will not be updating the BlazeDS bits there, as the only place we distribute the builds is from our website, and that is a conscious business decision.
So they will remain stale on the repo, which means users are using bits with security holes, etc.
But if that's your decision, that's fine.
On May 19, 2011, at 3:50 AM, "Carlos Sanchez" <ca...@apache.org> wrote:
> You'd need to create your own repository for com/adobe/* and then work
> on sync'ing it with central through Sonatype.
>
> You can't/shouldn't remove anything from central, people already have
> local copies.
>
>
> On Wed, May 18, 2011 at 11:44 PM, Jukka Zitting <jz...@adobe.com> wrote:
>> Hi,
>>
>> I work for Adobe and would like to figure out how we can best start managing the com.adobe space on Maven central [1].
>>
>> Currently the com.adobe space contains some bits and pieces based on upload requests made by our users (including myself before I joined Adobe), and we’d now like to take better control over this space. What would be the best way to do this?
>>
>> As a related matter, the BlazeDS artifacts uploaded from Ryan Heaton's repository [2] are neither up to date nor approved by Adobe. We appreciate the initiative, but at this point we'd appreciate if the currently uploaded BlazeDS artifacts could be replaced with pointers to the official BlazeDS download page [3]. How should we do this?
>>
>> [1] http://repo1.maven.org/maven2/com/adobe/
>> [2] http://jira.codehaus.org/browse/MAVENUPLOAD-1998
>> [3] http://opensource.adobe.com/wiki/display/blazeds/Downloads
>>
>> Best regards,
>>
>> Jukka Zitting
>>
>>
Re: Managing com.adobe on Maven Central
Posted by Carlos Sanchez <ca...@apache.org>.
You'd need to create your own repository for com/adobe/* and then work
on sync'ing it with central through Sonatype.
You can't/shouldn't remove anything from central, people already have
local copies.
On Wed, May 18, 2011 at 11:44 PM, Jukka Zitting <jz...@adobe.com> wrote:
> Hi,
>
> I work for Adobe and would like to figure out how we can best start managing the com.adobe space on Maven central [1].
>
> Currently the com.adobe space contains some bits and pieces based on upload requests made by our users (including myself before I joined Adobe), and we’d now like to take better control over this space. What would be the best way to do this?
>
> As a related matter, the BlazeDS artifacts uploaded from Ryan Heaton's repository [2] are neither up to date nor approved by Adobe. We appreciate the initiative, but at this point we'd appreciate if the currently uploaded BlazeDS artifacts could be replaced with pointers to the official BlazeDS download page [3]. How should we do this?
>
> [1] http://repo1.maven.org/maven2/com/adobe/
> [2] http://jira.codehaus.org/browse/MAVENUPLOAD-1998
> [3] http://opensource.adobe.com/wiki/display/blazeds/Downloads
>
> Best regards,
>
> Jukka Zitting
>
>
Re: Managing com.adobe on Maven Central
Posted by Juven Xu <ju...@sonatype.com>.
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 <jz...@adobe.com> 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
RE: Managing com.adobe on Maven Central
Posted by Jukka Zitting <jz...@adobe.com>.
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
Re: Managing com.adobe on Maven Central
Posted by Ryan Heaton <ry...@webcohesion.com>.
Just for the record, I'm glad that Adobe is taking this on and I'd be happy
to relinquish my "unofficial maintainer" role.
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.
-Ryan
On Wed, May 18, 2011 at 3:44 PM, Jukka Zitting <jz...@adobe.com> wrote:
> Hi,
>
> I work for Adobe and would like to figure out how we can best start
> managing the com.adobe space on Maven central [1].
>
> Currently the com.adobe space contains some bits and pieces based on upload
> requests made by our users (including myself before I joined Adobe), and
> we’d now like to take better control over this space. What would be the best
> way to do this?
>
> As a related matter, the BlazeDS artifacts uploaded from Ryan Heaton's
> repository [2] are neither up to date nor approved by Adobe. We appreciate
> the initiative, but at this point we'd appreciate if the currently uploaded
> BlazeDS artifacts could be replaced with pointers to the official BlazeDS
> download page [3]. How should we do this?
>
> [1] http://repo1.maven.org/maven2/com/adobe/
> [2] http://jira.codehaus.org/browse/MAVENUPLOAD-1998
> [3] http://opensource.adobe.com/wiki/display/blazeds/Downloads
>
> Best regards,
>
> Jukka Zitting
>
>