Hi,
The best way to go IMO will be to get a GitHub account, fork the repo you
want, and create PRs from there.
All projects are rooted under https://github.com/apache/
For example https://github.com/apache/commons-logging
Gary
On Fri, Nov 30, 2018 at 8:01 AM Hannes H. wrote:
> At the moment
). In your case you can just delete the Apache classes in the
spring jar.
Gruß
Bernd
--
https://Bernd.eckenfels.net
Von: Hannes H.
Gesendet: Freitag, November 30, 2018 4:01 PM
An: dev@commons.apache.org
Betreff: Re: Modular version/edition of Apache Commons
At
On Fri, 30 Nov 2018 16:01:15 +0100, Hannes H. wrote:
At the moment I am not even able to clone the git repository since I
do not
have sufficient credentials .. .do I need to register somewhere?
No.
Repository is:
https://git-wip-us.apache.org/repos/asf?p=commons-dbcp.git
This command shoul
At the moment I am not even able to clone the git repository since I do not
have sufficient credentials .. .do I need to register somewhere?
Am Fr., 30. Nov. 2018 um 15:46 Uhr schrieb Gary Gregory <
garydgreg...@gmail.com>:
> Patches are always welcome :-)
>
> Gary
>
> On Fri, Nov 30, 2018, 07:44
Patches are always welcome :-)
Gary
On Fri, Nov 30, 2018, 07:44 Hannes H. My precise problem is that some Spring Framework modules reading classes
> from the package ' org.apache.commons.logging from both commons.logging'
> and so does 'commons.dbcp2' (which seems to be a module of DBCP). That i
My precise problem is that some Spring Framework modules reading classes
from the package ' org.apache.commons.logging from both commons.logging'
and so does 'commons.dbcp2' (which seems to be a module of DBCP). That is
apparently a condition called "split package" which is not allowed in
modulariz
On Fri, 30 Nov 2018 15:01:57 +0100, Hannes H. wrote:
So there is no common approach planned for Apache Commons?
Recently released components probably have an
Automatic-Module-Name
defined for each artefact.
Is there a precise question?
Do you have a suggestion?
Regards,
Gilles
Am Fr., 30
So there is no common approach planned for Apache Commons?
Am Fr., 30. Nov. 2018 um 14:50 Uhr schrieb A. Soroka :
> Since each Commons component is released separately, each can have its own
> plan.
>
> ajs6f
>
> On Fri, Nov 30, 2018, 8:46 AM Hannes H.
> > Hi,
> >
> > I am talking about Apache
Since each Commons component is released separately, each can have its own
plan.
ajs6f
> On Fri, Nov 30, 2018, 8:46 AM Hannes H.
>> Hi,
>>
>> I am talking about Apache Commons in general and its approach to Java
>> modules which came with JDK 9 (project Jigsaw).
>>
>> Hannes
>>
>> Am Fr., 30. N
Since each Commons component is released separately, each can have its own
plan.
ajs6f
On Fri, Nov 30, 2018, 8:46 AM Hannes H. Hi,
>
> I am talking about Apache Commons in general and its approach to Java
> modules which came with JDK 9 (project Jigsaw).
>
> Hannes
>
> Am Fr., 30. Nov. 2018 um
Hi,
I am talking about Apache Commons in general and its approach to Java
modules which came with JDK 9 (project Jigsaw).
Hannes
Am Fr., 30. Nov. 2018 um 13:22 Uhr schrieb Gary Gregory <
garydgreg...@gmail.com>:
> Hi,
>
> Apache Common is a single project but is made up of Components that are
>
Hi,
Apache Common is a single project but is made up of Components that are
developed and released individually.
Can you be more specific? Which Components are you talking about?
Gary
On Fri, Nov 30, 2018, 01:52 Hannes H. Good day,
>
> while migrating a code base which depends on Apache Common
Good day,
while migrating a code base which depends on Apache Commons from Java 8 to
Java 11 the problem with 'split packages' crossed my efforts to do so.
I did some research but I could not find anything, so I try by asking here:
Is there a modularized version/edition of Apache Commons availabl
13 matches
Mail list logo
