On Tue, 11 Feb 2025 at 23:52, Melloware Inc wrote:
>
> Can’t you do “mvn -U clean package” the -U ignores the local cache timing.
It's not a question of cache timing: the missing jar does not yet
exist in any repo.
However, I did just try that, and it makes no difference; 'mvn
dependency:list' s
Can’t you do “mvn -U clean package” the -U ignores the local cache timing.
Melloware
@melloware on GitHub
> On Feb 11, 2025, at 6:47 PM, sebb wrote:
>
> Commons weaver seems to have an issue with its pom module settings.
>
> One symptom is that the following fails:
>
> $ mvn dependency:lis
Commons weaver seems to have an issue with its pom module settings.
One symptom is that the following fails:
$ mvn dependency:list
with
Could not resolve dependencies for project
org.apache.commons:commons-weaver-maven-plugin:maven-plugin:2.1-SNAPSHOT:
Failure to find
org.apache.commons:commons
Welcome to the first OpenJDK Quality Outreach update of 2025!
The first Release Candidate builds of JDK 24 are now available [1] and tt this
stage, only P1 issues will be evaluated. With the JDK 24 General Availability
set for March 18th, the attention is now turning to JDK 25.
JDK 24 will offi
Hi Arnout and all.
Le lun. 10 févr. 2025 à 12:11, Arnout Engelen a écrit :
>
> On Mon, Feb 10, 2025 at 11:45 AM Gilles Sadowski
> wrote:
>
> > Le lun. 10 févr. 2025 à 11:25, Arnout Engelen a
> > écrit :
> > > Do you mean we should leave out the whole line or just the "Thanks to
> > > Dependabot
If an API is deprecated, please make sure the @deprecated comment
states clearly with an @link what the replacement is.
This will allow people who use OpenRewrite to configure their wares
accordingly. IOW, don't give users a headache ;-)
Gary
On Tue, Feb 11, 2025 at 7:18 AM Gilles Sadowski wrot
Hi.
Le mar. 11 févr. 2025 à 12:56, Elliotte Rusty Harold
a écrit :
>
> I am not surprised you've found issues with FastDateFormat. I'd be
> more surprised if you didn't. Handling time zones is *hard* and almost
> everyone gets it wrong, at least at first. In 2025 I wouldn't use
> either SimpleDat
I am not surprised you've found issues with FastDateFormat. I'd be
more surprised if you didn't. Handling time zones is *hard* and almost
everyone gets it wrong, at least at first. In 2025 I wouldn't use
either SimpleDateFormat or FastDateFormat. Use java.time and
java.time.formatter instead. These
I started using FastDateFormat.parser() while expanding some internal tests
of an old custom date parser, and killing usages of
SimpleDateFormat.parse(). Since FastDateFormat uses Calendar internally to
keep state, I was surprised that I got unexpected results when using
"generic" timezones. Gene
