Le ven. 16 août 2024 à 09:51, Andreas Sewe
a écrit :
>
> Hi,
>
> just a long term Maven user here, but I'd like to chime, as I don't
> think renaming module to subproject is that big an improvement. In fact,
> it may actually lead to *more* confusion. Here's why:
>
> Maven has two *orthogonal* way
+1 non-binding from me.
--
"Great artists are extremely selfish and arrogant things" — Steven Wilson,
Porcupine Tree
On 17 Aug 2024 at 4:35:57 PM, Olivier Lamy wrote:
> +1
>
>
>
+1
On Wed, 14 Aug 2024 at 7:01 PM, Tamás Cservenák wrote:
> Howdy,
>
> Respin #1: mvn shell script fix, removal of "bashism":
> https://github.com/apache/maven/pull/1653
>
> We solved 13 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12354823
>
> Th
+1
We should add info about migration, like requirement for Fluido 2.x
But can be as first step
śr., 14 sie 2024 o 18:06 Michael Osipov napisał(a):
> Hi,
>
> NOTE: Read the details on this release here:
>
> https://cwiki.apache.org/confluence/display/MAVEN/Towards+Doxia+2.0.0+Stack#TowardsDoxia
Am 2024-08-16 um 21:08 schrieb Slawomir Jaranowski:
Ok, with Fluido 2.0.0-M9 is better ...
But with Maven 4 I have:
[DEBUG] Looking for site descriptor of level 1 parent project:
org.apache.maven.plugins:maven-plugins:pom:44-SNAPSHOT
[DEBUG] No parent level 1 site descriptor
[DEBUG] Looking for
Ok, with Fluido 2.0.0-M9 is better ...
But with Maven 4 I have:
[DEBUG] Looking for site descriptor of level 1 parent project:
org.apache.maven.plugins:maven-plugins:pom:44-SNAPSHOT
[DEBUG] No parent level 1 site descriptor
[DEBUG] Looking for site descriptor of level 2 parent project:
org.apache
Am 2024-08-15 um 19:36 schrieb Michael Osipov:
Hi,
we solved 3 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317926&version=12354803
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20MSKINS%20AND%20resolution
Am 2024-08-15 um 22:06 schrieb Michael Osipov:
Hi,
we solved 3 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317927&version=12354945
There are still a couple of issues left in JIRA:
https://issues.apache.org/jira/issues/?jql=project%20%3D%20SUREFIRE%20AND%20resoluti
Am 2024-08-14 um 11:00 schrieb Tamás Cservenák:
Howdy,
Respin #1: mvn shell script fix, removal of "bashism":
https://github.com/apache/maven/pull/1653
We solved 13 issues:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12354823
There are still a couple of is
Just an outsider here, but I agree with Guillaume. Also I think Tamas'
proposal is to merge the existing plugins, so the repo of the old plugins
will be probably archived and the old plugins code will be moved to the new
plugin repo.
Since the old plugins will not evolve and maintained by ASF, and
+1
śr., 14 sie 2024 o 11:01 Tamás Cservenák napisał(a):
> Howdy,
>
> Respin #1: mvn shell script fix, removal of "bashism":
> https://github.com/apache/maven/pull/1653
>
> We solved 13 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12316922&version=12354823
>
> Ther
+1
On Thu, Aug 15, 2024 at 2:11 PM Slawomir Jaranowski
wrote:
> Hi,
>
> We solved 9 issues:
>
> https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12317922&version=12344384
>
> There are still a couple of issues left in JIRA:
>
> https://issues.apache.org/jira/issues/?jql=project%2
> On 16. Aug 2024, at 10:24, Christoph Läubrich wrote:
>
>> I would hence restrict the use of "sub-something" to inheritance (think
>> "sub-class") and never use it to discussion aggregation. In particular,
>> "submodule" is really redundant, as a module is always below an
>> aggregator by defi
I agree that subproject is odd and even more confusing, because the real
project (== those with packaging != pom) can't contain
Of course a parent can also include but this is not required
and often separated also a single project might occur in different
aggregators and so on.
Am 16.08.24
Hi Andreas,
it took me some years to find relevant articles and documentation on the maven
site.
And still it is not easy to find documentation in the depth needed.
I would regret if "module" was changed. It is, as it is now, the best
description and semantics of what it is.
Maybe we should pr
Guillaume Nodet wrote:
Maybe now is the time to re(de)fine our terminology:
https://maven.apache.org/glossary.html.
Yes, please!
In fact, I didn't even know about the glossary (after 10+ years of using
Maven). It's not linked from the POM Reference, for example.
At any rate, I have just pro
Hi,
just a long term Maven user here, but I'd like to chime, as I don't
think renaming module to subproject is that big an improvement. In fact,
it may actually lead to *more* confusion. Here's why:
Maven has two *orthogonal* ways how to projects can relate to each
other: aggregation and inherit
17 matches
Mail list logo