Howdy,
just a heads up, that Maven 3.9.9 is about to happen soon:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.9
Until then, please grab latest Maven 3.9.9-SNAPSHOT and test it:
https://repository.apache.org/service/local/artifact/maven/redirect?r=
Tested locally with Trino on JDK 22.0.2 - builds just fine :)
On Tue, Aug 13, 2024 at 11:55 AM Tamás Cservenák
wrote:
> Howdy,
>
> just a heads up, that Maven 3.9.9 is about to happen soon:
>
> https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20fixVersion%20%3D%203.9.9
>
> Un
Howdy,
We solved 13 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12354823
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MNG%20AND%20resolution%20%3D%20Unresolved
Staging repo:
https://repos
+1 (nb)
On Tue, Aug 13, 2024, 18:13 Tamás Cservenák wrote:
> Howdy,
>
> We solved 13 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12354823
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%
-1
I'm getting the following error when I run Maven 3.9.9 in a directory
that does not have a ".mvn" sub-directory. Does anyone else get these
errors?
.../maven/bin/mvn: 136: [: /home/john: unexpected operator
.../maven/bin/mvn: 136: [: /home: unexpected operator
.../maven/bin/mvn: 136:
I think the errors I'm getting in my previous message are from Maven
3.9.9 using a Bash construct in a normal '/bin/sh' shell script, which
is dash on my Ubuntu system.
Dash prints the "unexpected operator" error message when '==' is used
instead of '=' in a test. I think you can also use '-eq
line 136 has:
if [ "$wdir" == '/' ] ; then
there is a wrong operator
wt., 13 sie 2024 o 22:29 John Neffenger napisał(a):
> -1
>
> I'm getting the following error when I run Maven 3.9.9 in a directory
> that does not have a ".mvn" sub-directory. Does anyone else get these
> errors?
>
>.
I agree this is a problem. Not the first time that a new Java language
feature has caused problems for much existing code. Who else remembers
that JUnit's assertTrue used to be simply assert? That was an ugly
one.
In this case, I'm not yet sold that the cure isn't worse than the
disease. In partic
Le mar. 13 août 2024 à 23:43, Elliotte Rusty Harold
a écrit :
>
> I agree this is a problem. Not the first time that a new Java language
> feature has caused problems for much existing code. Who else remembers
> that JUnit's assertTrue used to be simply assert? That was an ugly
> one.
>
> In this
I agree with Guillaume. This is just an alias with a deprecation warning or
a plain rename. Either way would be OK with me.
Gary
On Tue, Aug 13, 2024, 5:49 PM Guillaume Nodet wrote:
> Le mar. 13 août 2024 à 23:43, Elliotte Rusty Harold
> a écrit :
> >
> > I agree this is a problem. Not the fir
shellcheck SC3014: In POSIX sh, == in place of = is undefined.
On Wed, Aug 14, 2024 at 4:49 AM Slawomir Jaranowski
wrote:
> line 136 has:
>
> if [ "$wdir" == '/' ] ; then
>
> there is a wrong operator
>
> wt., 13 sie 2024 o 22:29 John Neffenger napisał(a):
>
> > -1
> >
> > I'm getting the
มันคืออะไร ทำไมฉันถึงยังไม่ได้รับความเข้าใจอย่างชัดเจน รบกวนอธิบาย
อย่างละเอียด
ในวันที่ อ. 13 ส.ค. 2024 23:13 Tamás Cservenák
เขียนว่า:
> Howdy,
>
> We solved 13 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12354823
>
> There are still a couple o
+0, from my window module is a generic term whereas project brings a
semantic which is regularly wrong for maven. Build-segment is ugly but more
accurate.
For me there is no real ambiguity with jpms since we cant use "module" for
jpms since it is not specific enough and would be worse and ambiguous
13 matches
Mail list logo
