Hello.
On Sat, 22 Apr 2017 22:31:13 +0100, Bernd Porr wrote:
Hi all,
sorry for the long silence. I've been just too busy with my main
(paying) jobs which also involve two startups. I'd love to help that
realistically I just don't have the time just now. So I should be
upfront. I'd say from Aug
Hello.
On Sat, 22 Apr 2017 18:30:46 + (UTC), Eyal Allweil wrote:
Hi Gilles,
It looks like there is no "edit" feature in Help Wanted.
https://lists.apache.org/thread.html/8ae808862f07ca8fb005ec95cbe9dc4bc8c6cd012dbe141cf2b47d2b@%3Cdev.community.apache.org%3E
Editing is done by deleting the
With regards to Log4j 1, just making v2 as compatible as possible with v1
should hopefully be enough.
As for lang v2, is there nothing stopping us from releasing a 2.7 artifact
with Java 9 support? Same goes for older major versions of Commons projects.
On 22 April 2017 at 13:03, Gary Gregory
Hi all,
sorry for the long silence. I've been just too busy with my main
(paying) jobs which also involve two startups. I'd love to help that
realistically I just don't have the time just now. So I should be
upfront. I'd say from Aug things will have calmed down and happy to join
back in. I'm
Hi Gilles,
It looks like there is no "edit" feature in Help Wanted.
https://lists.apache.org/thread.html/8ae808862f07ca8fb005ec95cbe9dc4bc8c6cd012dbe141cf2b47d2b@%3Cdev.community.apache.org%3E
Editing is done by deleting the old item and recreating - any Apache committer
can do this by marking
What a mess. I wonder if we should do something more official with log4j1.
I guess we can wait and see...
On Apr 22, 2017 10:59 AM, "Ralph Goers" wrote:
> Gary, if you are transitioning to use Java 9 modules I think it is
> appropriate that it be expected that only
Gary, if you are transitioning to use Java 9 modules I think it is appropriate
that it be expected that only the latest versions will support them. Upgrading
to Java 9 is not going to be as simple as just replacing the java runtime and
running. They have removed lots of deprecated classes. See
On Sat, Apr 22, 2017 at 10:46 AM, Pascal Schumacher <
pascalschumac...@gmx.net> wrote:
> Is this really necessary?
>
> Imho people who use (update to) java 9 should not use these "ancient"
> versions but update.
>
Sadly this is unrealistic and at times impossible due to transitive
dependencies.
Is this really necessary?
Imho people who use (update to) java 9 should not use these "ancient"
versions but update.
Am 22.04.2017 um 10:00 schrieb Emmanuel Bourg:
Le 22/04/2017 à 01:02, Stephen Colebourne a écrit :
I've started a page here:
Hi Rob.
On Sat, 22 Apr 2017 10:26:39 -0400, Rob Tompkins wrote:
Hello all,
I have attempted a sorting of the open/reopened issues in Jira. I’ve
simply sorted them into 4.0 and 4.X (which I think gives us a solid
amount of leeway here). Regardless of that, if someone wants to run
through the
Avoid references to auto modules. Here's the official advice:
- Strongly advise developers never to publish, for broad use, explicit
modules that require automatic modules. That's risky: An automatic
module is unreliable, since it can depend on types on the class path,
and its
K
On Apr 21, 2017 6:21 AM, "Emmanuel Bourg" wrote:
Le 21/04/2017 à 15:12, sebb a écrit :
> Agreed?
I don't mind, but IntelliJ will highlight the groupId and suggest to
remove it :)
Same in Eclipse. POMs are big enough as it is, I prefer to keep the config
by exception
Hello all,
I have attempted a sorting of the open/reopened issues in Jira. I’ve simply
sorted them into 4.0 and 4.X (which I think gives us a solid amount of leeway
here). Regardless of that, if someone wants to run through the list of 4.X
issues:
Hm, never had the idea this is needed. I can see that new projects want a pure
modules setting, for existing code (using older artifacts) that is less of an
requirement. Hm, let's hope people who want modules versions will contribute.
But the hint with automatic modules (file name based) is a
Github user bodewig commented on a diff in the pull request:
https://github.com/apache/commons-compress/pull/20#discussion_r112810573
--- Diff:
src/test/java/org/apache/commons/compress/compressors/DetectCompressorTestCase.java
---
@@ -167,6 +171,26 @@ private String
Github user kinow commented on a diff in the pull request:
https://github.com/apache/commons-compress/pull/20#discussion_r112810239
--- Diff:
src/test/java/org/apache/commons/compress/compressors/DetectCompressorTestCase.java
---
@@ -167,6 +171,26 @@ private String detect(String
> On Apr 22, 2017, at 8:44 AM, Pascal Schumacher
> wrote:
>
> Hello everybody,
>
> the copy of commons-lang WordUtils removed from commons-text a few months
> ago, because Duncan Jones wanted to split/refactor it.
>
> As there was no new of the refactoring until
Hello everybody,
the copy of commons-lang WordUtils removed from commons-text a few
months ago, because Duncan Jones wanted to split/refactor it.
As there was no new of the refactoring until now I guess it could not be
completed. Maybe we should just add the copy back?
Cheers,
Pascal
Hello everybody,
I have just closed close java.util.Date related enhancement requests I
could find.
Cheers,
Pascal
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail:
On 22 April 2017 at 09:00, Emmanuel Bourg wrote:
> Le 22/04/2017 à 01:02, Stephen Colebourne a écrit :
>> I've started a page here:
>> https://github.com/jodastephen/jpms-module-names/blob/master/README.md
>> Feel free to raise a PR with more projects at commons or elsewhere in
Le 22/04/2017 à 01:02, Stephen Colebourne a écrit :
> I've started a page here:
> https://github.com/jodastephen/jpms-module-names/blob/master/README.md
> Feel free to raise a PR with more projects at commons or elsewhere in
> Apache - I'm just checking the Javadoc and releases to ensure there
>
21 matches
Mail list logo