You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@maven.apache.org by Giorgio Gallo <gi...@allos.it> on 2006/03/01 13:23:22 UTC
[M2 REPO] mess in /servicemix
Hi!
I'm sorry to write at an inappropriate address (got this from
http://maven.apache.org/project-faq.html) - I just couldn't find
anything like repo-mantainer@maven.apache.org or similar.
Please forward to a more appropriate one (if there is one).
This email is to let you know i stumbled into
http://www.ibiblio.org/maven2/servicemix/ and - I fear - there is far
too mutch stuff in there (eg: eclipse components, xalan, xerces, ...).
I would also like to suggest creating some kind of facility to mantain
and "moderate" the m2 repo (I'm ready to help if needed).
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [M2 REPO] mess in /servicemix
Posted by Carlos Sanchez <ca...@apache.org>.
we'll make sure they don't do ;) the version in svn is becoming clear
On 3/5/06, Brett Porter <br...@apache.org> wrote:
> Sure, but they don't really need to redistribute half of eclipse themselves.
>
> - Brett
>
> Carlos Sanchez wrote:
> > servicemix is in progress of migrating to m2 and theri artifacts will
> > be at org.apache.servicemix groupid
> >
> > On 3/5/06, Brett Porter <br...@apache.org> wrote:
> >> Moderation is something we'd all like. Getting there.
> >>
> >> This is not pretty. I will find out what's going on.
> >>
> >> - Brett
> >>
> >> Giorgio Gallo wrote:
> >>> Hi!
> >>>
> >>> I'm sorry to write at an inappropriate address (got this from
> >>> http://maven.apache.org/project-faq.html) - I just couldn't find
> >>> anything like repo-mantainer@maven.apache.org or similar.
> >>>
> >>> Please forward to a more appropriate one (if there is one).
> >>>
> >>> This email is to let you know i stumbled into
> >>> http://www.ibiblio.org/maven2/servicemix/ and - I fear - there is far
> >>> too mutch stuff in there (eg: eclipse components, xalan, xerces, ...).
> >>>
> >>> I would also like to suggest creating some kind of facility to mantain
> >>> and "moderate" the m2 repo (I'm ready to help if needed).
> >>>
> >>>
> >>> ---------------------------------------------------------------------
> >>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >>> For additional commands, e-mail: dev-help@maven.apache.org
> >>>
> >> ---------------------------------------------------------------------
> >> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> >> For additional commands, e-mail: dev-help@maven.apache.org
> >>
> >>
> >
> >
> > --
> > I could give you my word as a Spaniard.
> > No good. I've known too many Spaniards.
> > -- The Princess Bride
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [M2 REPO] mess in /servicemix
Posted by Jason van Zyl <ja...@maven.org>.
Brett Porter wrote:
> When we implement something like <provides>, so that these can say
> "treat me like the real one if it ever turns up", then this is probably
> a reasonably expedient way.
The meaning of <provides/> is really "i am the real one, but an
equivalent _will_ show up".
> I'd much rather they use a private repo where they can do what they want
> until they get it into ibiblio. I think that's a better solution. WDYT?
That's probably the best solution. Anyone can still build against a
project hosted repository and it stays out of the ibiblio population.
Then the project can take whatever measures to get the real dependencies
to ibiblio but everything can still function. Sounds like a good concept
to promote.
> - Brett
>
> Jason van Zyl wrote:
>> Brett Porter wrote:
>>> That's exactly the problem in this case - they're all in the servicemix
>>> groupId.
>>>
>>> This becomes harmful in transitive dependencies, as there's no way to
>>> express equivalence. So if you depend on OSGi and ServiceMix, you get
>>> two copies of OSGi, and all its dependencies.
>> Projects are always going to do this for the sake of expediency and
>> under the license they can.
>>
>> They obviously did this as not to claim to have provided the official
>> JARs which I think is correct and being a good citizen. This is going to
>> happen again I'm sure because projects don't want to push the official
>> project JARs into the repository. For highly used components do we just
>> push them in, maybe a flag on the dependency to indicate this scenerio?
>>
>> We definitely prefer that projects themselves issue to the repository
>> but this isn't always going to happen and we should probably account for
>> it.
>>
>> Jason van Zyl
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [M2 REPO] mess in /servicemix
Posted by Brett Porter <br...@apache.org>.
When we implement something like <provides>, so that these can say
"treat me like the real one if it ever turns up", then this is probably
a reasonably expedient way.
I'd much rather they use a private repo where they can do what they want
until they get it into ibiblio. I think that's a better solution. WDYT?
- Brett
Jason van Zyl wrote:
> Brett Porter wrote:
>> That's exactly the problem in this case - they're all in the servicemix
>> groupId.
>>
>> This becomes harmful in transitive dependencies, as there's no way to
>> express equivalence. So if you depend on OSGi and ServiceMix, you get
>> two copies of OSGi, and all its dependencies.
>
> Projects are always going to do this for the sake of expediency and
> under the license they can.
>
> They obviously did this as not to claim to have provided the official
> JARs which I think is correct and being a good citizen. This is going to
> happen again I'm sure because projects don't want to push the official
> project JARs into the repository. For highly used components do we just
> push them in, maybe a flag on the dependency to indicate this scenerio?
>
> We definitely prefer that projects themselves issue to the repository
> but this isn't always going to happen and we should probably account for
> it.
>
> Jason van Zyl
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [M2 REPO] mess in /servicemix
Posted by Jason van Zyl <ja...@maven.org>.
Brett Porter wrote:
> That's exactly the problem in this case - they're all in the servicemix
> groupId.
>
> This becomes harmful in transitive dependencies, as there's no way to
> express equivalence. So if you depend on OSGi and ServiceMix, you get
> two copies of OSGi, and all its dependencies.
Projects are always going to do this for the sake of expediency and
under the license they can.
They obviously did this as not to claim to have provided the official
JARs which I think is correct and being a good citizen. This is going to
happen again I'm sure because projects don't want to push the official
project JARs into the repository. For highly used components do we just
push them in, maybe a flag on the dependency to indicate this scenerio?
We definitely prefer that projects themselves issue to the repository
but this isn't always going to happen and we should probably account for it.
Jason van Zyl
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [M2 REPO] mess in /servicemix
Posted by Brett Porter <br...@apache.org>.
That's exactly the problem in this case - they're all in the servicemix
groupId.
This becomes harmful in transitive dependencies, as there's no way to
express equivalence. So if you depend on OSGi and ServiceMix, you get
two copies of OSGi, and all its dependencies.
- Brett
Jason van Zyl wrote:
> Brett Porter wrote:
>> Sure, but they don't really need to redistribute half of eclipse
>> themselves.
>
> How about a simple rule of not allowing the deployment of anything
> outside that projects groupId. In the case of external dependencies I'm
> not sure what the best route is because one project could potentially
> harm another project where snapshots are involved or simply accidentally
> where an artifact is named incorrectly and overwrites a correctly
> deployed version.
>
> In this case we could make projects use their groupId so those
> externally pulled in deps can't pollute the repository it only affects
> that project. I think this would be a decent compromise as it lets
> projects redistribute according to the license covering the artifacts
> but they can't harm others. I'm not sure we can easily enforce this now
> but something the repository manager could do.
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [M2 REPO] mess in /servicemix
Posted by Jason van Zyl <ja...@maven.org>.
Brett Porter wrote:
> Sure, but they don't really need to redistribute half of eclipse themselves.
How about a simple rule of not allowing the deployment of anything
outside that projects groupId. In the case of external dependencies I'm
not sure what the best route is because one project could potentially
harm another project where snapshots are involved or simply accidentally
where an artifact is named incorrectly and overwrites a correctly
deployed version.
In this case we could make projects use their groupId so those
externally pulled in deps can't pollute the repository it only affects
that project. I think this would be a decent compromise as it lets
projects redistribute according to the license covering the artifacts
but they can't harm others. I'm not sure we can easily enforce this now
but something the repository manager could do.
> - Brett
>
> Carlos Sanchez wrote:
>> servicemix is in progress of migrating to m2 and theri artifacts will
>> be at org.apache.servicemix groupid
>>
>> On 3/5/06, Brett Porter <br...@apache.org> wrote:
>>> Moderation is something we'd all like. Getting there.
>>>
>>> This is not pretty. I will find out what's going on.
>>>
>>> - Brett
>>>
>>> Giorgio Gallo wrote:
>>>> Hi!
>>>>
>>>> I'm sorry to write at an inappropriate address (got this from
>>>> http://maven.apache.org/project-faq.html) - I just couldn't find
>>>> anything like repo-mantainer@maven.apache.org or similar.
>>>>
>>>> Please forward to a more appropriate one (if there is one).
>>>>
>>>> This email is to let you know i stumbled into
>>>> http://www.ibiblio.org/maven2/servicemix/ and - I fear - there is far
>>>> too mutch stuff in there (eg: eclipse components, xalan, xerces, ...).
>>>>
>>>> I would also like to suggest creating some kind of facility to mantain
>>>> and "moderate" the m2 repo (I'm ready to help if needed).
>>>>
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>>>
>>
>> --
>> I could give you my word as a Spaniard.
>> No good. I've known too many Spaniards.
>> -- The Princess Bride
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [M2 REPO] mess in /servicemix
Posted by Brett Porter <br...@apache.org>.
Sure, but they don't really need to redistribute half of eclipse themselves.
- Brett
Carlos Sanchez wrote:
> servicemix is in progress of migrating to m2 and theri artifacts will
> be at org.apache.servicemix groupid
>
> On 3/5/06, Brett Porter <br...@apache.org> wrote:
>> Moderation is something we'd all like. Getting there.
>>
>> This is not pretty. I will find out what's going on.
>>
>> - Brett
>>
>> Giorgio Gallo wrote:
>>> Hi!
>>>
>>> I'm sorry to write at an inappropriate address (got this from
>>> http://maven.apache.org/project-faq.html) - I just couldn't find
>>> anything like repo-mantainer@maven.apache.org or similar.
>>>
>>> Please forward to a more appropriate one (if there is one).
>>>
>>> This email is to let you know i stumbled into
>>> http://www.ibiblio.org/maven2/servicemix/ and - I fear - there is far
>>> too mutch stuff in there (eg: eclipse components, xalan, xerces, ...).
>>>
>>> I would also like to suggest creating some kind of facility to mantain
>>> and "moderate" the m2 repo (I'm ready to help if needed).
>>>
>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>>> For additional commands, e-mail: dev-help@maven.apache.org
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
>> For additional commands, e-mail: dev-help@maven.apache.org
>>
>>
>
>
> --
> I could give you my word as a Spaniard.
> No good. I've known too many Spaniards.
> -- The Princess Bride
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [M2 REPO] mess in /servicemix
Posted by Carlos Sanchez <ca...@apache.org>.
servicemix is in progress of migrating to m2 and theri artifacts will
be at org.apache.servicemix groupid
On 3/5/06, Brett Porter <br...@apache.org> wrote:
> Moderation is something we'd all like. Getting there.
>
> This is not pretty. I will find out what's going on.
>
> - Brett
>
> Giorgio Gallo wrote:
> > Hi!
> >
> > I'm sorry to write at an inappropriate address (got this from
> > http://maven.apache.org/project-faq.html) - I just couldn't find
> > anything like repo-mantainer@maven.apache.org or similar.
> >
> > Please forward to a more appropriate one (if there is one).
> >
> > This email is to let you know i stumbled into
> > http://www.ibiblio.org/maven2/servicemix/ and - I fear - there is far
> > too mutch stuff in there (eg: eclipse components, xalan, xerces, ...).
> >
> > I would also like to suggest creating some kind of facility to mantain
> > and "moderate" the m2 repo (I'm ready to help if needed).
> >
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> > For additional commands, e-mail: dev-help@maven.apache.org
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
--
I could give you my word as a Spaniard.
No good. I've known too many Spaniards.
-- The Princess Bride
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [M2 REPO] mess in /servicemix
Posted by Brett Porter <br...@apache.org>.
Moderation is something we'd all like. Getting there.
This is not pretty. I will find out what's going on.
- Brett
Giorgio Gallo wrote:
> Hi!
>
> I'm sorry to write at an inappropriate address (got this from
> http://maven.apache.org/project-faq.html) - I just couldn't find
> anything like repo-mantainer@maven.apache.org or similar.
>
> Please forward to a more appropriate one (if there is one).
>
> This email is to let you know i stumbled into
> http://www.ibiblio.org/maven2/servicemix/ and - I fear - there is far
> too mutch stuff in there (eg: eclipse components, xalan, xerces, ...).
>
> I would also like to suggest creating some kind of facility to mantain
> and "moderate" the m2 repo (I'm ready to help if needed).
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org
Re: [M2 REPO] mess in /servicemix
Posted by Wayne Fay <wa...@gmail.com>.
The Codehaus Jira, Project Maven Evangelism (MEV) is the place to file
bugs with comments like these: http://jira.codehaus.org/browse/MEV
"This is a mess" is probably not going to result in a good fix. From
the page: "Please note that we don't have full knowledge of the
projects whose jars are in the repository, so if you don't provide a
solution we won't be able to fix issues that require project knowledge
and we'll be forced to close your issue as incomplete."
As for wishing you could "moderate" the m2 repo, I'm sure you're not alone.
Wayne
On 3/1/06, Giorgio Gallo <gi...@allos.it> wrote:
> Hi!
>
> I'm sorry to write at an inappropriate address (got this from
> http://maven.apache.org/project-faq.html) - I just couldn't find
> anything like repo-mantainer@maven.apache.org or similar.
>
> Please forward to a more appropriate one (if there is one).
>
> This email is to let you know i stumbled into
> http://www.ibiblio.org/maven2/servicemix/ and - I fear - there is far
> too mutch stuff in there (eg: eclipse components, xalan, xerces, ...).
>
> I would also like to suggest creating some kind of facility to mantain
> and "moderate" the m2 repo (I'm ready to help if needed).
>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
> For additional commands, e-mail: dev-help@maven.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@maven.apache.org
For additional commands, e-mail: dev-help@maven.apache.org