You are viewing a plain text version of this content. The canonical link for it is here.
Posted to general@incubator.apache.org by kelvin goodson <ke...@gmail.com> on 2007/06/25 11:37:15 UTC
3rd party dependencies that don't provide maven binary artifacts
How can an Apache project robustly handle the situation where 3rd
party dependencies don't provide maven binary artifacts? In
particular, when an Apache release is made, we need to be sure that
the 3rd party dependencies are available for as long as the release is
available.
Regards, Kelvin.
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: 3rd party dependencies that don't provide maven binary artifacts
Posted by Guillaume Nodet <gn...@gmail.com>.
This one is mainly for fixes on existing metadata.
The one for uploading new artifacts is available at
http://jira.codehaus.org/browse/MAVENUPLOAD
See also the instructions available at:
http://maven.apache.org/guides/mini/guide-central-repository-upload.html
Cheers,
Guillaume
Guillaume Nodet wrote:
> Sorry.
> Here it is: http://jira.codehaus.org/browse/MEV
>
> kelvin goodson wrote:
>
>> Hi Guillame,
>> thanks for the tip. Could you post the reference [1] that you
>> referred to please?
>>
>> Regards, Kelvin.
>>
>> On 25/06/07, Guillaume Nodet <gn...@gmail.com> wrote:
>>
>>> I think you can just create a JIRA at [1] so that your dependencies
>>> will be uploaded in the public repository.
>>> The public maven repository is handled by the maven guys.
>>>
>>> I guess another way is to make an archive of your local repository
>>> and store it in a publicly available location so that one can always
>>> rebuild the release if needed. I know maven has a feature to create
>>> this zip file, but I can't recall where.
>>>
>>> Cheers,
>>> Guillaume Nodet
>>>
>>> kelvin goodson wrote:
>>>
>>>> How can an Apache project robustly handle the situation where 3rd
>>>> party dependencies don't provide maven binary artifacts? In
>>>> particular, when an Apache release is made, we need to be sure that
>>>> the 3rd party dependencies are available for as long as the release is
>>>> available.
>>>>
>>>> Regards, Kelvin.
>>>>
>>>> ---------------------------------------------------------------------
>>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>>
>>>>
>>>>
>>>>
>>> ---------------------------------------------------------------------
>>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>>> For additional commands, e-mail: general-help@incubator.apache.org
>>>
>>>
>>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: 3rd party dependencies that don't provide maven binary artifacts
Posted by Guillaume Nodet <gn...@gmail.com>.
Sorry.
Here it is: http://jira.codehaus.org/browse/MEV
kelvin goodson wrote:
> Hi Guillame,
> thanks for the tip. Could you post the reference [1] that you
> referred to please?
>
> Regards, Kelvin.
>
> On 25/06/07, Guillaume Nodet <gn...@gmail.com> wrote:
>> I think you can just create a JIRA at [1] so that your dependencies
>> will be uploaded in the public repository.
>> The public maven repository is handled by the maven guys.
>>
>> I guess another way is to make an archive of your local repository
>> and store it in a publicly available location so that one can always
>> rebuild the release if needed. I know maven has a feature to create
>> this zip file, but I can't recall where.
>>
>> Cheers,
>> Guillaume Nodet
>>
>> kelvin goodson wrote:
>> > How can an Apache project robustly handle the situation where 3rd
>> > party dependencies don't provide maven binary artifacts? In
>> > particular, when an Apache release is made, we need to be sure that
>> > the 3rd party dependencies are available for as long as the release is
>> > available.
>> >
>> > Regards, Kelvin.
>> >
>> > ---------------------------------------------------------------------
>> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> > For additional commands, e-mail: general-help@incubator.apache.org
>> >
>> >
>> >
>>
>> ---------------------------------------------------------------------
>> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
>> For additional commands, e-mail: general-help@incubator.apache.org
>>
>>
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: 3rd party dependencies that don't provide maven binary artifacts
Posted by kelvin goodson <ke...@gmail.com>.
Hi Guillame,
thanks for the tip. Could you post the reference [1] that you
referred to please?
Regards, Kelvin.
On 25/06/07, Guillaume Nodet <gn...@gmail.com> wrote:
> I think you can just create a JIRA at [1] so that your dependencies
> will be uploaded in the public repository.
> The public maven repository is handled by the maven guys.
>
> I guess another way is to make an archive of your local repository
> and store it in a publicly available location so that one can always
> rebuild the release if needed. I know maven has a feature to create
> this zip file, but I can't recall where.
>
> Cheers,
> Guillaume Nodet
>
> kelvin goodson wrote:
> > How can an Apache project robustly handle the situation where 3rd
> > party dependencies don't provide maven binary artifacts? In
> > particular, when an Apache release is made, we need to be sure that
> > the 3rd party dependencies are available for as long as the release is
> > available.
> >
> > Regards, Kelvin.
> >
> > ---------------------------------------------------------------------
> > To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> > For additional commands, e-mail: general-help@incubator.apache.org
> >
> >
> >
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org
Re: 3rd party dependencies that don't provide maven binary artifacts
Posted by Guillaume Nodet <gn...@gmail.com>.
I think you can just create a JIRA at [1] so that your dependencies
will be uploaded in the public repository.
The public maven repository is handled by the maven guys.
I guess another way is to make an archive of your local repository
and store it in a publicly available location so that one can always
rebuild the release if needed. I know maven has a feature to create
this zip file, but I can't recall where.
Cheers,
Guillaume Nodet
kelvin goodson wrote:
> How can an Apache project robustly handle the situation where 3rd
> party dependencies don't provide maven binary artifacts? In
> particular, when an Apache release is made, we need to be sure that
> the 3rd party dependencies are available for as long as the release is
> available.
>
> Regards, Kelvin.
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
> For additional commands, e-mail: general-help@incubator.apache.org
>
>
>
---------------------------------------------------------------------
To unsubscribe, e-mail: general-unsubscribe@incubator.apache.org
For additional commands, e-mail: general-help@incubator.apache.org