That works, you can download the source release using maven ("source" config)
and patch it (not automatically, but it's possible!).
-----
Uwe Schindler
H.-H.-Meier-Allee 63, D-28213 Bremen
http://www.thetaphi.de
eMail: [email protected]
> -----Original Message-----
> From: Robert Muir [mailto:[email protected]]
> Sent: Monday, April 23, 2012 11:50 PM
> To: [email protected]
> Subject: Re: [DISCUSS] Build/deploy Maven artifacts outside of Lucene/Solr
>
> On Mon, Apr 23, 2012 at 5:47 PM, Benson Margulies
> <[email protected]> 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" ?
>
> 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: [email protected] For additional
> commands, e-mail: [email protected]
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
