lucene-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Benson Margulies <bimargul...@gmail.com>
Subject Re: [DISCUSS] Build/deploy Maven artifacts outside of Lucene/Solr
Date Mon, 23 Apr 2012 22:13:01 GMT
On Mon, Apr 23, 2012 at 5:49 PM, Robert Muir <rcmuir@gmail.com> wrote:
> On Mon, Apr 23, 2012 at 5:47 PM, Benson Margulies <bimargulies@gmail.com> wrote:
>
>> b) Create a patching process that grabs their release package, fixes
>> it, and builds it, renaming packages. Include the patching process in
>> your source release.
>>
>
> I would *love* to be able to have this option available, but how will
> the maven artifacts work? Can maven artifacts say "i depend on x.y.z
> but i need to download its source and patch it first" ?

You publish it. No one objects to the process of changing the packages
and publishing it under a suitable descriptive name. Or, as Uwe
pointed out, it entirely possible to use a couple of maven plugins to
pull this off dynamically.


>
> See with ant/ivy, i feel this is still an option, but when we support
> maven artifacts, I feel that it shackles us, and removes options like
> this.
>
>
>
> --
> lucidimagination.com
>
> ---------------------------------------------------------------------
> To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
> For additional commands, e-mail: dev-help@lucene.apache.org
>

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@lucene.apache.org
For additional commands, e-mail: dev-help@lucene.apache.org


Mime
View raw message