I think we’re heading towards the need for a release of beanutils 1.10. Does
anyone agree or disagree?
-Rob
-
To unsubscribe, e-mail: dev-unsubscr...@commons.apache.org
For additional commands, e-mail:
So, if the migration from JUnit 4 to JUnit 5 has to happen
instantaneously, how about creating a new branch for the migration? It's
a lot of files that have to be refactored, which is going to take some
time, and since the changes will need to be reviewed, it would probably
be easier if the
> On 4 Jun 2019, at 22:43, Gilles Sadowski wrote:
>
> Hi.
>
> Is there a purpose to having mails from "WIP" commits?
> It's difficult to know when/what to comment about.
>
> Regards,
> Gilles
>
> P.S. In the below commits, I don't understand the purpose of
> "UNKNOWN". Also, I'd say that
Hi.
Is there a purpose to having mails from "WIP" commits?
It's difficult to know when/what to comment about.
Regards,
Gilles
P.S. In the below commits, I don't understand the purpose of
"UNKNOWN". Also, I'd say that having a named constant ZERO
for the value "0" is overkill.
Le mar. 4 juin
This sounds like a shade feature, yes. However, in order to
automatically extract the version extra data and detect a version
keyword like "alpha" may require some additional code, though maybe
the shade plugin already supports that.
Alternatively, JUnit 5.x uses a tool called API Guardian for
The JDK is the only source allowed to modify java.lang.String, so
they'd likely add static methods to that directly like String.join()
and the others. The plural name thing was more of an issue with an
interface Thing and utility class Things. As of Java 8, there's
typically no need to have a
Hi.
Le mar. 4 juin 2019 à 03:49, Heinrich Bohne a écrit :
>
> I have been advised to raise this improvement suggestion on the
> developers' mailing list. It is about the trial division algorithm in
> the method SmallPrimes.boundedTrialDivision(int, int, List) in
> the primes module. Currently,
Then 10 years later JDK has its own Strings, and users get confused then.
Emmanuel Bourg 于2019年6月4日周二 下午6:58写道：
> Le 28/05/2019 à 13:46, Gary Gregory a écrit :
>
> > Thoughts?
>
> Maybe we could make a more ambitious 'Strings' class with methods taken
> from StringUtils and refactored with a
Le 28/05/2019 à 13:46, Gary Gregory a écrit :
> Thoughts?
Maybe we could make a more ambitious 'Strings' class with methods taken
from StringUtils and refactored with a fluent API to avoid the
combinatorial explosion of StringUtils? Just a wild idea.
Emmanuel Bourg
Hello.
Does someone see a practical way to automate package names
and source files conversions so that each all alpha/beta releases
can be used together (e.g. to compare their behaviours).
I mean, for release version "1.0-alpha1", the top-level package
name "o.a.c.compid" would be turned into
+1 to skipping Clirr until 1.0.
Gary
On Tue, Jun 4, 2019, 06:24 Bruno P. Kinoshita wrote:
> I had a look at ways to skip just this error... but we are not maintaining
> BC with sanselan-0.97, which means that we may change more in the API, and
> have one or many more alpha releases.
> So
I had a look at ways to skip just this error... but we are not maintaining BC
with sanselan-0.97, which means that we may change more in the API, and have
one or many more alpha releases.
So instead of manually adding each entry to be ignored, I thought it would make
more sense to use clirr
Why not just exclude this method using ignored differences? [1]
That will allow you to keep clirr:check active.
[1]
https://www.mojohaus.org/clirr-maven-plugin/examples/ignored-differences.html
On Tue, 4 Jun 2019, 09:22 Bruno P. Kinoshita, wrote:
> Hi,
>
>
> There is a user PR [1] and
Hi,
There is a user PR [1] and another PR that I created yesterday [2] failing in
Travis-CI due to clirr:check.
Clirr is checking the current snapshot 1.0-alpha2-SNAPSHOT against 1.0-alpha1.
And is failing as we have renamed a public method (getFilename -> getFileName).
I believe backward
14 matches
Mail list logo
