I would like to propose the following changes:
1. The `parent`, `core`, `client`, `website`, and `stylecheck` source trees
shall be consolidated into a single Git repository for all of Apache
HttpComponents 5.
2. All artifacts contained in this repository shall be co-versioned (i.e.
released in co
On Fri, 2019-12-13 at 12:49 -0800, Ryan Schmitt wrote:
> I would like to propose the following changes:
>
> 1. The `parent`, `core`, `client`, `website`, and `stylecheck` source
> trees
> shall be consolidated into a single Git repository for all of Apache
> HttpComponents 5.
> 2. All artifacts co
I don't think core is special in this regard, but I *do* think it is
special in having a separate release cycle. Most Java projects these days
use version alignment (and usually a unified repository as well), despite
featuring many distinct components that all move at different speeds.
Examples inc
On Fri, 2019-12-13 at 15:04 -0800, Ryan Schmitt wrote:
> I don't think core is special in this regard, but I *do* think it is
> special in having a separate release cycle. Most Java projects these
> days
> use version alignment (and usually a unified repository as well),
> despite
> featuring many
Am 2019-12-13 um 22:57 schrieb Oleg Kalnichevski:
On Fri, 2019-12-13 at 12:49 -0800, Ryan Schmitt wrote:
I would like to propose the following changes:
1. The `parent`, `core`, `client`, `website`, and `stylecheck` source
trees
shall be consolidated into a single Git repository for all of Apach
It sounds like these changes aren't going to happen, but I'm going to press
the point anyway because I think this is important.
> I am not sure I can agree with that. Usually one should care about the
> top level library such as HttpClient or HttpAsyncClient only. One needs
> to manually override
On Tue, 2019-12-17 at 23:32 -0800, Ryan Schmitt wrote:
> It sounds like these changes aren't going to happen, but I'm going to
> press
> the point anyway because I think this is important.
>
> > I am not sure I can agree with that. Usually one should care about
> > the
> > top level library such a
I have a few thoughts here, with the TL;DR that I like the idea of one repo
for core and client.
My background is that I spent a long time working with HttpCore5 to build a
proprietary reverse proxy (which has since been rewritten on top of Jetty
but that's a different and unrelated story and has
>
> I do not know what IDE you use but IntelliJ IDEA makes it completely
> effortless to run SNAPSHOT versions of multiple modules within the same
> project.
I don't know how to develop separate Maven projects as if they were a
single project. I do know how to do this with Gradle, which has a fea
On Fri, 2019-12-20 at 23:14 -0800, Ryan Schmitt wrote:
> >
> > I do not know what IDE you use but IntelliJ IDEA makes it
> > completely
> > effortless to run SNAPSHOT versions of multiple modules within the
> > same
> > project.
>
>
> I don't know how to develop separate Maven projects as if the
Am 2019-12-21 um 08:14 schrieb Ryan Schmitt:
I do not know what IDE you use but IntelliJ IDEA makes it completely
effortless to run SNAPSHOT versions of multiple modules within the same
project.
I don't know how to develop separate Maven projects as if they were a
single project. I do know ho
11 matches
Mail list logo
