[jira] [Closed] (MNGSITE-536) Link to Reference "Maven Plugin Tools and annotations" wrong
[
https://issues.apache.org/jira/browse/MNGSITE-536?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MNGSITE-536.
---
Resolution: Fixed
> Link to Reference "Maven Plugin Tools and annotations" wrong
>
>
> Key: MNGSITE-536
> URL: https://issues.apache.org/jira/browse/MNGSITE-536
> Project: Maven Project Web Site
> Issue Type: Bug
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
>
> The link on the page https://maven.apache.org/plugin-developers/index.html to
> the annotation {{Maven Plugin Tools and annotations}} is wrong.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MNGSITE-536) Link to Reference "Maven Plugin Tools and annotations" wrong
Karl Heinz Marbaise created MNGSITE-536:
---
Summary: Link to Reference "Maven Plugin Tools and annotations"
wrong
Key: MNGSITE-536
URL: https://issues.apache.org/jira/browse/MNGSITE-536
Project: Maven Project Web Site
Issue Type: Bug
Reporter: Karl Heinz Marbaise
Assignee: Karl Heinz Marbaise
The link on the page https://maven.apache.org/plugin-developers/index.html to
the annotation {{Maven Plugin Tools and annotations}} is wrong.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MNGSITE-532) Move plugin-report to Reporting Plugin table
[
https://issues.apache.org/jira/browse/MNGSITE-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MNGSITE-532.
---
Resolution: Fixed
> Move plugin-report to Reporting Plugin table
>
>
> Key: MNGSITE-532
> URL: https://issues.apache.org/jira/browse/MNGSITE-532
> Project: Maven Project Web Site
> Issue Type: Task
>Reporter: Michael Osipov
>Assignee: Karl Heinz Marbaise
>Priority: Major
>
> In https://maven.apache.org/plugins/index.html {{plugin-report}} is a pure
> reporting plugin, like {{surefire-report}}, it should be in reporting...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Assigned] (MNGSITE-532) Move plugin-report to Reporting Plugin table
[
https://issues.apache.org/jira/browse/MNGSITE-532?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise reassigned MNGSITE-532:
---
Assignee: Karl Heinz Marbaise
> Move plugin-report to Reporting Plugin table
>
>
> Key: MNGSITE-532
> URL: https://issues.apache.org/jira/browse/MNGSITE-532
> Project: Maven Project Web Site
> Issue Type: Task
>Reporter: Michael Osipov
>Assignee: Karl Heinz Marbaise
>Priority: Major
>
> In https://maven.apache.org/plugins/index.html {{plugin-report}} is a pure
> reporting plugin, like {{surefire-report}}, it should be in reporting...
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNGSITE-535) Improve the Release Notes about 3.9.2 - related to topDirectory/rootDirectory
[
https://issues.apache.org/jira/browse/MNGSITE-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836661#comment-17836661
]
Karl Heinz Marbaise commented on MNGSITE-535:
-
Done in [7d8d3c187215da8137e6ff7a174a741d59c8a3e7|.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
http://localhost:8081/nexus/content/groups
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
(/Users/khm/ws-git-maven/maven-site
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
http://localhost:8081/nexus/content/groups
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.?p=1.0:
The
following
artifacts
could
not
be
resolved:
org.apache.maven:maven-parent:pom:42-SNAPSHOT
(absent):
org.apache.maven:maven-parent:pom:42-SNAPSHOT
was
not
found
in
public
during
a
previous
attempt.
This
failure
was
cached
in
the
local
repository
and
resolution
is
not
reattempted
until
the
update
interval
of
nexus
has
elapsed
or
updates
are
forced
and
'parent.relativePath'
points
at
no
local
POM
@
line
23,
column
11
@
[ERROR]
The
build
could
not
read
1
project
->
[Help
1]
[ERROR]
1.0
pom.xml)
has
1
error
1.0:
The
following
artifacts
could
not
be
resolved:
org.apache.maven:maven-parent:pom:42-SNAPSHOT
(absent):
org.apache.maven:maven-parent:pom:42-SNAPSHOT
was
not
found
in
public
during
a
previous
attempt.
This
failure
was
cached
in
the
local
repository
and
resolution
is
not
reattempted
until
the
update
interval
of
nexus
has
elapsed
or
updates
are
forced
and
'parent.relativePath'
points
at
no
local
POM
@
line
23,
column
11
->
[Help
2]
[ERROR]
[ERROR]
To
see
the
full
stack
trace
of
the
errors,
re-run
Maven
with
the
-e
switch.
[ERROR]
Re-run
Maven
using
the
-X
switch
to
enable
full
debug
logging.
[ERROR];a=commitdiff;h=7d8d3c187215da8137e6ff7a174a741d59c8a3e7]
> Improve the Release Notes about 3.9.2 - related to topDirectory/rootDirectory
> -
>
> Key: MNGSITE-535
> URL: https://issues.apache.org/jira/browse/MNGSITE-535
> Project: Maven Project Web Site
> Issue Type: Improvement
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
>
> Related to this: MNG-8095 there should more clear wording when the following
> properties can be used and when not:
> * {{$session.topDirectory}}
> * {{$session.rootDirectory}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MNGSITE-535) Improve the Release Notes about 3.9.2 - related to topDirectory/rootDirectory
[
https://issues.apache.org/jira/browse/MNGSITE-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MNGSITE-535.
---
Resolution: Done
> Improve the Release Notes about 3.9.2 - related to topDirectory/rootDirectory
> -
>
> Key: MNGSITE-535
> URL: https://issues.apache.org/jira/browse/MNGSITE-535
> Project: Maven Project Web Site
> Issue Type: Improvement
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
>
> Related to this: MNG-8095 there should more clear wording when the following
> properties can be used and when not:
> * {{$session.topDirectory}}
> * {{$session.rootDirectory}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MNGSITE-535) Improve the Release Notes about 3.9.2 - related to topDirectory/rootDirectory
[
https://issues.apache.org/jira/browse/MNGSITE-535?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836661#comment-17836661
]
Karl Heinz Marbaise edited comment on MNGSITE-535 at 4/12/24 3:48 PM:
--
Done in [7d8d3c187215da8137e6ff7a174a741d59c8a3e7|
was (Author: khmarbaise):
Done in [7d8d3c187215da8137e6ff7a174a741d59c8a3e7|.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
http://localhost:8081/nexus/content/groups
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
(/Users/khm/ws-git-maven/maven-site
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
http://localhost:8081/nexus/content/groups
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.
.?p=1.0:
The
following
artifacts
could
not
be
resolved:
org.apache.maven:maven-parent:pom:42-SNAPSHOT
(absent):
org.apache.maven:maven-parent:pom:42-SNAPSHOT
was
not
found
in
public
during
a
previous
attempt.
This
failure
was
cached
in
the
local
repository
and
resolution
is
not
reattempted
until
the
update
interval
of
nexus
has
elapsed
or
updates
are
forced
and
'parent.relativePath'
points
at
no
local
POM
@
line
23,
column
11
@
[ERROR]
The
build
could
not
read
1
project
->
[Help
1]
[ERROR]
1.0
pom.xml)
has
1
error
1.0:
The
following
artifacts
could
not
be
resolved:
org.apache.maven:maven-parent:pom:42-SNAPSHOT
(absent):
org.apache.maven:maven-parent:pom:42-SNAPSHOT
was
not
found
in
public
during
a
previous
attempt.
This
failure
was
cached
in
the
local
repository
and
resolution
is
not
reattempted
until
the
update
interval
of
nexus
has
elapsed
or
updates
are
forced
and
'parent.relativePath'
points
at
no
local
POM
@
line
23,
column
11
->
[Help
2]
[ERROR]
[ERROR]
To
see
the
full
stack
trace
of
the
errors,
re-run
Maven
with
the
-e
switch.
[ERROR]
Re-run
Maven
using
the
-X
switch
to
enable
full
debug
logging.
[ERROR];a=commitdiff;h=7d8d3c187215da8137e6ff7a174a741d59c8a3e7]
> Improve the Release Notes about 3.9.2 - related to topDirectory/rootDirectory
> -
>
> Key: MNGSITE-535
> URL: https://issues.apache.org/jira/browse/MNGSITE-535
> Project: Maven Project Web Site
> Issue Type: Improvement
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
>
> Related to this: MNG-8095 there should more clear wording when the following
> properties can be used and when not:
> * {{$session.topDirectory}}
> * {{$session.rootDirectory}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNGSITE-535) Improve the Release Notes about 3.9.2 - related to topDirectory/rootDirectory
[
https://issues.apache.org/jira/browse/MNGSITE-535?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MNGSITE-535:
Description:
Related to this: MNG-8095 there should more clear wording when the following
properties can be used and when not:
* {{$session.topDirectory}}
* {{$session.rootDirectory}}
was:
Related to this: MNG-8095 there should be hint where the following:
* {{$session.topDirectory}}
* {{$session.rootDirectory}}
can be used an can not being used.
> Improve the Release Notes about 3.9.2 - related to topDirectory/rootDirectory
> -
>
> Key: MNGSITE-535
> URL: https://issues.apache.org/jira/browse/MNGSITE-535
> Project: Maven Project Web Site
> Issue Type: Improvement
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
>
> Related to this: MNG-8095 there should more clear wording when the following
> properties can be used and when not:
> * {{$session.topDirectory}}
> * {{$session.rootDirectory}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MNG-8095) Usage of session.rootDirectory / session.topDirectory does not work
[
https://issues.apache.org/jira/browse/MNG-8095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MNG-8095.
Assignee: Karl Heinz Marbaise
Resolution: Not A Problem
> Usage of session.rootDirectory / session.topDirectory does not work
> ---
>
> Key: MNG-8095
> URL: https://issues.apache.org/jira/browse/MNG-8095
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 3.9.2, 3.9.3, 3.9.4, 3.9.5, 3.9.6
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
>
> I have setup a project which uses the following parts
> (https://maven.apache.org/docs/3.9.2/release-notes.html)
> * {{$session.topDirectory}}
> * {{$session.rootDirectory}}
> * {{$project.rootDirectory}}
> but unfortately they are not being replaced during the run of the project...
> A small excerpt from the project... using the following simple configuration:
> {code:xml}
>
> com.soebes.maven.plugins
> echo-maven-plugin
> 0.5.0
>
>
> initialize
>
> echo
>
>
>
>
> project.rootDirectory: '${project.rootDirectory}'
> session.rootDirectory: '${session.rootDirectory}'
> session.topDirectory: '${session.topDirectory}'
> project.basedir: '${project.basedir}'
> project.build.directory:
> '${project.build.directory}'
>
>
>
>
>
>
> {code}
> My expectation is that during the build the values should be replaced with
> the appropriate values which works with Maven 4 (Tested with Maven
> 4-alpha-13) like this:
> {code}
> [INFO] --- echo:0.5.0:echo (default) @ sub-mod-2 ---
> [INFO] =
> [INFO] project.rootDirectory: '/projects/props'
> [INFO] session.rootDirectory: '/projects/props'
> [INFO] session.topDirectory: '/projects/props'
> [INFO] project.basedir: '/projects/props/sub-mod-2'
> [INFO] project.build.directory: '/projects/props/sub-mod-2/target'
> [INFO] =
> {code}
> But the run with Maven 3.9.X it looks like this:
> {code}
> [INFO] --- echo:0.5.0:echo (default) @ sub-mod-2 ---
> [INFO] =
> [INFO] project.rootDirectory: '${project.rootDirectory}'
> [INFO] session.rootDirectory: '${session.rootDirectory}'
> [INFO] session.topDirectory: '${session.topDirectory}'
> [INFO] project.basedir: '/projects/props/sub-mod-2'
> [INFO] project.build.directory: '/projects/props/sub-mod-2/target'
> [INFO] =
> {code}
> I have setup a full working example here:
> https://github.com/khmarbaise/maven-bugs/tree/master/MNG-8095
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MNGSITE-535) Improve the Release Notes about 3.9.2 - related to topDirectory/rootDirectory
Karl Heinz Marbaise created MNGSITE-535:
---
Summary: Improve the Release Notes about 3.9.2 - related to
topDirectory/rootDirectory
Key: MNGSITE-535
URL: https://issues.apache.org/jira/browse/MNGSITE-535
Project: Maven Project Web Site
Issue Type: Improvement
Reporter: Karl Heinz Marbaise
Assignee: Karl Heinz Marbaise
Related to this: MNG-8095 there should be hint where the following:
* {{$session.topDirectory}}
* {{$session.rootDirectory}}
can be used an can not being used.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-8095) Usage of session.rootDirectory / session.topDirectory does not work
[
https://issues.apache.org/jira/browse/MNG-8095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836648#comment-17836648
]
Karl Heinz Marbaise commented on MNG-8095:
--
Ok I have feared such a thing. That means we have to make the release notes
more clear on that part... If I read "properties" and "configuration" which
could be mistaken with the configuration of the plugins... Ok...
> Usage of session.rootDirectory / session.topDirectory does not work
> ---
>
> Key: MNG-8095
> URL: https://issues.apache.org/jira/browse/MNG-8095
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 3.9.2, 3.9.3, 3.9.4, 3.9.5, 3.9.6
>Reporter: Karl Heinz Marbaise
>Priority: Minor
>
> I have setup a project which uses the following parts
> (https://maven.apache.org/docs/3.9.2/release-notes.html)
> * {{$session.topDirectory}}
> * {{$session.rootDirectory}}
> * {{$project.rootDirectory}}
> but unfortately they are not being replaced during the run of the project...
> A small excerpt from the project... using the following simple configuration:
> {code:xml}
>
> com.soebes.maven.plugins
> echo-maven-plugin
> 0.5.0
>
>
> initialize
>
> echo
>
>
>
>
> project.rootDirectory: '${project.rootDirectory}'
> session.rootDirectory: '${session.rootDirectory}'
> session.topDirectory: '${session.topDirectory}'
> project.basedir: '${project.basedir}'
> project.build.directory:
> '${project.build.directory}'
>
>
>
>
>
>
> {code}
> My expectation is that during the build the values should be replaced with
> the appropriate values which works with Maven 4 (Tested with Maven
> 4-alpha-13) like this:
> {code}
> [INFO] --- echo:0.5.0:echo (default) @ sub-mod-2 ---
> [INFO] =
> [INFO] project.rootDirectory: '/projects/props'
> [INFO] session.rootDirectory: '/projects/props'
> [INFO] session.topDirectory: '/projects/props'
> [INFO] project.basedir: '/projects/props/sub-mod-2'
> [INFO] project.build.directory: '/projects/props/sub-mod-2/target'
> [INFO] =
> {code}
> But the run with Maven 3.9.X it looks like this:
> {code}
> [INFO] --- echo:0.5.0:echo (default) @ sub-mod-2 ---
> [INFO] =
> [INFO] project.rootDirectory: '${project.rootDirectory}'
> [INFO] session.rootDirectory: '${session.rootDirectory}'
> [INFO] session.topDirectory: '${session.topDirectory}'
> [INFO] project.basedir: '/projects/props/sub-mod-2'
> [INFO] project.build.directory: '/projects/props/sub-mod-2/target'
> [INFO] =
> {code}
> I have setup a full working example here:
> https://github.com/khmarbaise/maven-bugs/tree/master/MNG-8095
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-8095) Usage of session.rootDirectory / session.topDirectory does not work
[
https://issues.apache.org/jira/browse/MNG-8095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836633#comment-17836633
]
Karl Heinz Marbaise commented on MNG-8095:
--
Yes the implementation between Maven 4 and Maven 3.X is different...
> Usage of session.rootDirectory / session.topDirectory does not work
> ---
>
> Key: MNG-8095
> URL: https://issues.apache.org/jira/browse/MNG-8095
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 3.9.2, 3.9.3, 3.9.4, 3.9.5, 3.9.6
>Reporter: Karl Heinz Marbaise
>Priority: Minor
>
> I have setup a project which uses the following parts
> (https://maven.apache.org/docs/3.9.2/release-notes.html)
> * {{$session.topDirectory}}
> * {{$session.rootDirectory}}
> * {{$project.rootDirectory}}
> but unfortately they are not being replaced during the run of the project...
> A small excerpt from the project... using the following simple configuration:
> {code:xml}
>
> com.soebes.maven.plugins
> echo-maven-plugin
> 0.5.0
>
>
> initialize
>
> echo
>
>
>
>
> project.rootDirectory: '${project.rootDirectory}'
> session.rootDirectory: '${session.rootDirectory}'
> session.topDirectory: '${session.topDirectory}'
> project.basedir: '${project.basedir}'
> project.build.directory:
> '${project.build.directory}'
>
>
>
>
>
>
> {code}
> My expectation is that during the build the values should be replaced with
> the appropriate values which works with Maven 4 (Tested with Maven
> 4-alpha-13) like this:
> {code}
> [INFO] --- echo:0.5.0:echo (default) @ sub-mod-2 ---
> [INFO] =
> [INFO] project.rootDirectory: '/projects/props'
> [INFO] session.rootDirectory: '/projects/props'
> [INFO] session.topDirectory: '/projects/props'
> [INFO] project.basedir: '/projects/props/sub-mod-2'
> [INFO] project.build.directory: '/projects/props/sub-mod-2/target'
> [INFO] =
> {code}
> But the run with Maven 3.9.X it looks like this:
> {code}
> [INFO] --- echo:0.5.0:echo (default) @ sub-mod-2 ---
> [INFO] =
> [INFO] project.rootDirectory: '${project.rootDirectory}'
> [INFO] session.rootDirectory: '${session.rootDirectory}'
> [INFO] session.topDirectory: '${session.topDirectory}'
> [INFO] project.basedir: '/projects/props/sub-mod-2'
> [INFO] project.build.directory: '/projects/props/sub-mod-2/target'
> [INFO] =
> {code}
> I have setup a full working example here:
> https://github.com/khmarbaise/maven-bugs/tree/master/MNG-8095
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-8095) Usage of session.rootDirectory / session.topDirectory does not work
[
https://issues.apache.org/jira/browse/MNG-8095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836628#comment-17836628
]
Karl Heinz Marbaise commented on MNG-8095:
--
Apart from that the branch on 3.9.X contains refererences like this:
{code:java}
@Test
public void testPropertiesInterpolation() throws Exception {
// Arrange
CliRequest request = new CliRequest(
new String[] {
"-Dfoo=bar",
"-DvalFound=s${foo}i",
"-DvalNotFound=s${foz}i",
"-DvalRootDirectory=${session.rootDirectory}/.mvn/foo",
"-DvalTopDirectory=${session.topDirectory}/pom.xml",
"-f",
"${session.rootDirectory}/my-child",
"prefix:3.0.0:${foo}",
"validate"
},
null);
request.rootDirectory = Paths.get("myRootDirectory");
request.topDirectory = Paths.get("myTopDirectory");
{code}
and also the code in {{MavenCli.java}} contains
((https://github.com/apache/maven/blob/maven-3.9.x/maven-embedder/src/main/java/org/apache/maven/cli/MavenCli.java#L1563):
{code:java}
protected static StringSearchInterpolator createInterpolator(CliRequest
cliRequest, Properties... properties) {
StringSearchInterpolator interpolator = new StringSearchInterpolator();
interpolator.addValueSource(new AbstractValueSource(false) {
@Override
public Object getValue(String expression) {
if ("session.topDirectory".equals(expression)) {
Path topDirectory = cliRequest.topDirectory;
if (topDirectory != null) {
return topDirectory.toString();
} else {
throw new IllegalUseOfUndefinedProperty(expression);
}
} else if ("session.rootDirectory".equals(expression)) {
Path rootDirectory = cliRequest.rootDirectory;
if (rootDirectory != null) {
return rootDirectory.toString();
} else {
throw new IllegalUseOfUndefinedProperty(expression);
}
}
return null;
}
});
...
{code}
> Usage of session.rootDirectory / session.topDirectory does not work
> ---
>
> Key: MNG-8095
> URL: https://issues.apache.org/jira/browse/MNG-8095
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 3.9.2, 3.9.3, 3.9.4, 3.9.5, 3.9.6
>Reporter: Karl Heinz Marbaise
>Priority: Minor
>
> I have setup a project which uses the following parts
> (https://maven.apache.org/docs/3.9.2/release-notes.html)
> * {{$session.topDirectory}}
> * {{$session.rootDirectory}}
> * {{$project.rootDirectory}}
> but unfortately they are not being replaced during the run of the project...
> A small excerpt from the project... using the following simple configuration:
> {code:xml}
>
> com.soebes.maven.plugins
> echo-maven-plugin
> 0.5.0
>
>
> initialize
>
> echo
>
>
>
>
> project.rootDirectory: '${project.rootDirectory}'
> session.rootDirectory: '${session.rootDirectory}'
> session.topDirectory: '${session.topDirectory}'
> project.basedir: '${project.basedir}'
> project.build.directory:
> '${project.build.directory}'
>
>
>
>
>
>
> {code}
> My expectation is that during the build the values should be replaced with
> the appropriate values which works with Maven 4 (Tested with Maven
> 4-alpha-13) like this:
> {code}
> [INFO] --- echo:0.5.0:echo (default) @ sub-mod-2 ---
> [INFO] =
> [INFO] project.rootDirectory: '/projects/props'
> [INFO] session.rootDirectory: '/projects/props'
> [INFO] session.topDirectory: '/projects/props'
> [INFO] project.basedir: '/projects/props/sub-mod-2'
> [INFO] project.build.directory: '/projects/props/sub-mod-2/target'
> [INFO] =
> {code}
> But the run with Maven 3.9.X it looks like this:
> {code}
> [INFO] --- echo:0.5.0:echo (default) @ sub-mod-2 ---
> [INFO] =
> [INFO] project.rootDirectory: '${project.rootDirectory}'
> [INFO] session.rootDirectory: '${session.rootDirectory}'
> [INFO] session.topDirectory: '${session.topDirectory}'
> [INFO] project.basedir: '/projects/props/sub-mod-2'
> [INFO]
[jira] [Commented] (MNG-8095) Usage of session.rootDirectory / session.topDirectory does not work
[
https://issues.apache.org/jira/browse/MNG-8095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836624#comment-17836624
]
Karl Heinz Marbaise commented on MNG-8095:
--
The release notes of Maven 3.9.2 on
https://maven.apache.org/docs/3.9.2/release-notes.html saying something
different..
> Usage of session.rootDirectory / session.topDirectory does not work
> ---
>
> Key: MNG-8095
> URL: https://issues.apache.org/jira/browse/MNG-8095
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 3.9.2, 3.9.3, 3.9.4, 3.9.5, 3.9.6
>Reporter: Karl Heinz Marbaise
>Priority: Minor
>
> I have setup a project which uses the following parts
> (https://maven.apache.org/docs/3.9.2/release-notes.html)
> * {{$session.topDirectory}}
> * {{$session.rootDirectory}}
> * {{$project.rootDirectory}}
> but unfortately they are not being replaced during the run of the project...
> A small excerpt from the project... using the following simple configuration:
> {code:xml}
>
> com.soebes.maven.plugins
> echo-maven-plugin
> 0.5.0
>
>
> initialize
>
> echo
>
>
>
>
> project.rootDirectory: '${project.rootDirectory}'
> session.rootDirectory: '${session.rootDirectory}'
> session.topDirectory: '${session.topDirectory}'
> project.basedir: '${project.basedir}'
> project.build.directory:
> '${project.build.directory}'
>
>
>
>
>
>
> {code}
> My expectation is that during the build the values should be replaced with
> the appropriate values which works with Maven 4 (Tested with Maven
> 4-alpha-13) like this:
> {code}
> [INFO] --- echo:0.5.0:echo (default) @ sub-mod-2 ---
> [INFO] =
> [INFO] project.rootDirectory: '/projects/props'
> [INFO] session.rootDirectory: '/projects/props'
> [INFO] session.topDirectory: '/projects/props'
> [INFO] project.basedir: '/projects/props/sub-mod-2'
> [INFO] project.build.directory: '/projects/props/sub-mod-2/target'
> [INFO] =
> {code}
> But the run with Maven 3.9.X it looks like this:
> {code}
> [INFO] --- echo:0.5.0:echo (default) @ sub-mod-2 ---
> [INFO] =
> [INFO] project.rootDirectory: '${project.rootDirectory}'
> [INFO] session.rootDirectory: '${session.rootDirectory}'
> [INFO] session.topDirectory: '${session.topDirectory}'
> [INFO] project.basedir: '/projects/props/sub-mod-2'
> [INFO] project.build.directory: '/projects/props/sub-mod-2/target'
> [INFO] =
> {code}
> I have setup a full working example here:
> https://github.com/khmarbaise/maven-bugs/tree/master/MNG-8095
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MNG-8095) Usage of session.rootDirectory / session.topDirectory does not work
[
https://issues.apache.org/jira/browse/MNG-8095?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836624#comment-17836624
]
Karl Heinz Marbaise edited comment on MNG-8095 at 4/12/24 2:16 PM:
---
The release notes of Maven 3.9.2 on
https://maven.apache.org/docs/3.9.2/release-notes.html#notable-new-features
saying something different..
was (Author: khmarbaise):
The release notes of Maven 3.9.2 on
https://maven.apache.org/docs/3.9.2/release-notes.html saying something
different..
> Usage of session.rootDirectory / session.topDirectory does not work
> ---
>
> Key: MNG-8095
> URL: https://issues.apache.org/jira/browse/MNG-8095
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 3.9.2, 3.9.3, 3.9.4, 3.9.5, 3.9.6
>Reporter: Karl Heinz Marbaise
>Priority: Minor
>
> I have setup a project which uses the following parts
> (https://maven.apache.org/docs/3.9.2/release-notes.html)
> * {{$session.topDirectory}}
> * {{$session.rootDirectory}}
> * {{$project.rootDirectory}}
> but unfortately they are not being replaced during the run of the project...
> A small excerpt from the project... using the following simple configuration:
> {code:xml}
>
> com.soebes.maven.plugins
> echo-maven-plugin
> 0.5.0
>
>
> initialize
>
> echo
>
>
>
>
> project.rootDirectory: '${project.rootDirectory}'
> session.rootDirectory: '${session.rootDirectory}'
> session.topDirectory: '${session.topDirectory}'
> project.basedir: '${project.basedir}'
> project.build.directory:
> '${project.build.directory}'
>
>
>
>
>
>
> {code}
> My expectation is that during the build the values should be replaced with
> the appropriate values which works with Maven 4 (Tested with Maven
> 4-alpha-13) like this:
> {code}
> [INFO] --- echo:0.5.0:echo (default) @ sub-mod-2 ---
> [INFO] =
> [INFO] project.rootDirectory: '/projects/props'
> [INFO] session.rootDirectory: '/projects/props'
> [INFO] session.topDirectory: '/projects/props'
> [INFO] project.basedir: '/projects/props/sub-mod-2'
> [INFO] project.build.directory: '/projects/props/sub-mod-2/target'
> [INFO] =
> {code}
> But the run with Maven 3.9.X it looks like this:
> {code}
> [INFO] --- echo:0.5.0:echo (default) @ sub-mod-2 ---
> [INFO] =
> [INFO] project.rootDirectory: '${project.rootDirectory}'
> [INFO] session.rootDirectory: '${session.rootDirectory}'
> [INFO] session.topDirectory: '${session.topDirectory}'
> [INFO] project.basedir: '/projects/props/sub-mod-2'
> [INFO] project.build.directory: '/projects/props/sub-mod-2/target'
> [INFO] =
> {code}
> I have setup a full working example here:
> https://github.com/khmarbaise/maven-bugs/tree/master/MNG-8095
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-8095) Usage of session.rootDirectory / session.topDirectory does not work
[
https://issues.apache.org/jira/browse/MNG-8095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MNG-8095:
-
Affects Version/s: (was: 3.9.0)
(was: 3.9.1)
> Usage of session.rootDirectory / session.topDirectory does not work
> ---
>
> Key: MNG-8095
> URL: https://issues.apache.org/jira/browse/MNG-8095
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 3.9.2, 3.9.3, 3.9.4, 3.9.5, 3.9.6
>Reporter: Karl Heinz Marbaise
>Priority: Minor
>
> I have setup a project which uses the following parts
> (https://maven.apache.org/docs/3.9.2/release-notes.html)
> * {{$session.topDirectory}}
> * {{$session.rootDirectory}}
> * {{$project.rootDirectory}}
> but unfortately they are not being replaced during the run of the project...
> A small excerpt from the project... using the following simple configuration:
> {code:xml}
>
> com.soebes.maven.plugins
> echo-maven-plugin
> 0.5.0
>
>
> initialize
>
> echo
>
>
>
>
> project.rootDirectory: '${project.rootDirectory}'
> session.rootDirectory: '${session.rootDirectory}'
> session.topDirectory: '${session.topDirectory}'
> project.basedir: '${project.basedir}'
> project.build.directory:
> '${project.build.directory}'
>
>
>
>
>
>
> {code}
> My expectation is that during the build the values should be replaced with
> the appropriate values which works with Maven 4 (Tested with Maven
> 4-alpha-13) like this:
> {code}
> [INFO] --- echo:0.5.0:echo (default) @ sub-mod-2 ---
> [INFO] =
> [INFO] project.rootDirectory: '/projects/props'
> [INFO] session.rootDirectory: '/projects/props'
> [INFO] session.topDirectory: '/projects/props'
> [INFO] project.basedir: '/projects/props/sub-mod-2'
> [INFO] project.build.directory: '/projects/props/sub-mod-2/target'
> [INFO] =
> {code}
> But the run with Maven 3.9.X it looks like this:
> {code}
> [INFO] --- echo:0.5.0:echo (default) @ sub-mod-2 ---
> [INFO] =
> [INFO] project.rootDirectory: '${project.rootDirectory}'
> [INFO] session.rootDirectory: '${session.rootDirectory}'
> [INFO] session.topDirectory: '${session.topDirectory}'
> [INFO] project.basedir: '/projects/props/sub-mod-2'
> [INFO] project.build.directory: '/projects/props/sub-mod-2/target'
> [INFO] =
> {code}
> I have setup a full working example here:
> https://github.com/khmarbaise/maven-bugs/tree/master/MNG-8095
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-8095) Usage of session.rootDirectory / session.topDirectory does not work
[
https://issues.apache.org/jira/browse/MNG-8095?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MNG-8095:
-
Description:
I have setup a project which uses the following parts
(https://maven.apache.org/docs/3.9.2/release-notes.html)
* {{$session.topDirectory}}
* {{$session.rootDirectory}}
* {{$project.rootDirectory}}
but unfortately they are not being replaced during the run of the project... A
small excerpt from the project... using the following simple configuration:
{code:xml}
com.soebes.maven.plugins
echo-maven-plugin
0.5.0
initialize
echo
project.rootDirectory: '${project.rootDirectory}'
session.rootDirectory: '${session.rootDirectory}'
session.topDirectory: '${session.topDirectory}'
project.basedir: '${project.basedir}'
project.build.directory:
'${project.build.directory}'
{code}
My expectation is that during the build the values should be replaced with the
appropriate values which works with Maven 4 (Tested with Maven 4-alpha-13) like
this:
{code}
[INFO] --- echo:0.5.0:echo (default) @ sub-mod-2 ---
[INFO] =
[INFO] project.rootDirectory: '/projects/props'
[INFO] session.rootDirectory: '/projects/props'
[INFO] session.topDirectory: '/projects/props'
[INFO] project.basedir: '/projects/props/sub-mod-2'
[INFO] project.build.directory: '/projects/props/sub-mod-2/target'
[INFO] =
{code}
But the run with Maven 3.9.X it looks like this:
{code}
[INFO] --- echo:0.5.0:echo (default) @ sub-mod-2 ---
[INFO] =
[INFO] project.rootDirectory: '${project.rootDirectory}'
[INFO] session.rootDirectory: '${session.rootDirectory}'
[INFO] session.topDirectory: '${session.topDirectory}'
[INFO] project.basedir: '/projects/props/sub-mod-2'
[INFO] project.build.directory: '/projects/props/sub-mod-2/target'
[INFO] =
{code}
I have setup a full working example here:
https://github.com/khmarbaise/maven-bugs/tree/master/MNG-8095
was:
I have setup a project which uses the following parts
(https://maven.apache.org/docs/3.9.2/release-notes.html)
* {{$session.topDirectory}}
* {{$session.rootDirectory}}
* {{$project.rootDirectory}}
but unfortately they are not being replaced during the run of the project... A
small excerpt from the project... using the following simple configuration:
{code:xml}
com.soebes.maven.plugins
echo-maven-plugin
0.5.0
initialize
echo
project.rootDirectory: '${project.rootDirectory}'
session.rootDirectory: '${session.rootDirectory}'
session.topDirectory: '${session.topDirectory}'
project.basedir: '${project.basedir}'
project.build.directory:
'${project.build.directory}'
{code}
My expectation is that during the build the values should be replaced with the
appropriate values which works with Maven 4 (Tested with Maven 4-alpha-13) like
this:
{code}
[INFO] --- echo:0.5.0:echo (default) @ sub-mod-2 ---
[INFO] =
[INFO] project.rootDirectory: '/projects/props'
[INFO] session.rootDirectory: '/projects/props'
[INFO] session.topDirectory: '/projects/props'
[INFO] project.basedir: '/projects/props/sub-mod-2'
[INFO] project.build.directory: '/projects/props/sub-mod-2/target'
[INFO] =
{code}
But the run with Maven 3.9.X it looks like this:
{code}
[INFO] --- echo:0.5.0:echo (default) @ sub-mod-2 ---
[INFO] =
[INFO] project.rootDirectory: '${project.rootDirectory}'
[INFO] session.rootDirectory: '${session.rootDirectory}'
[INFO] session.topDirectory: '${session.topDirectory}'
[INFO] project.basedir: '/projects/props/sub-mod-2'
[INFO] project.build.directory: '/projects/props/sub-mod-2/target'
[INFO] =
{code}
> Usage of session.rootDirectory / session.topDirectory does not work
> ---
>
> Key: MNG-8095
> URL: https://issues.apache.org/jira/browse/MNG-8095
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 3.9.0, 3.9.1, 3.9.2, 3.9.3, 3.9.4, 3.9.5, 3.9.6
>Reporter: Karl Heinz
[jira] [Created] (MNG-8095) Usage of session.rootDirectory / session.topDirectory does not work
Karl Heinz Marbaise created MNG-8095:
Summary: Usage of session.rootDirectory / session.topDirectory
does not work
Key: MNG-8095
URL: https://issues.apache.org/jira/browse/MNG-8095
Project: Maven
Issue Type: Bug
Components: Core
Affects Versions: 3.9.6, 3.9.5, 3.9.4, 3.9.3, 3.9.2, 3.9.1, 3.9.0
Reporter: Karl Heinz Marbaise
I have setup a project which uses the following parts
(https://maven.apache.org/docs/3.9.2/release-notes.html)
* {{$session.topDirectory}}
* {{$session.rootDirectory}}
* {{$project.rootDirectory}}
but unfortately they are not being replaced during the run of the project... A
small excerpt from the project... using the following simple configuration:
{code:xml}
com.soebes.maven.plugins
echo-maven-plugin
0.5.0
initialize
echo
project.rootDirectory: '${project.rootDirectory}'
session.rootDirectory: '${session.rootDirectory}'
session.topDirectory: '${session.topDirectory}'
project.basedir: '${project.basedir}'
project.build.directory:
'${project.build.directory}'
{code}
My expectation is that during the build the values should be replaced with the
appropriate values which works with Maven 4 (Tested with Maven 4-alpha-13) like
this:
{code}
[INFO] --- echo:0.5.0:echo (default) @ sub-mod-2 ---
[INFO] =
[INFO] project.rootDirectory: '/projects/props'
[INFO] session.rootDirectory: '/projects/props'
[INFO] session.topDirectory: '/projects/props'
[INFO] project.basedir: '/projects/props/sub-mod-2'
[INFO] project.build.directory: '/projects/props/sub-mod-2/target'
[INFO] =
{code}
But the run with Maven 3.9.X it looks like this:
{code}
[INFO] --- echo:0.5.0:echo (default) @ sub-mod-2 ---
[INFO] =
[INFO] project.rootDirectory: '${project.rootDirectory}'
[INFO] session.rootDirectory: '${session.rootDirectory}'
[INFO] session.topDirectory: '${session.topDirectory}'
[INFO] project.basedir: '/projects/props/sub-mod-2'
[INFO] project.build.directory: '/projects/props/sub-mod-2/target'
[INFO] =
{code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-8025) API incompatibility with m-remote-resources-p
[
https://issues.apache.org/jira/browse/MNG-8025?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17836611#comment-17836611
]
Karl Heinz Marbaise commented on MNG-8025:
--
Is this still relevant? Or can it simply being "solved" by using a more recent
version of maven-resources-plugin (3.3.1)?
> API incompatibility with m-remote-resources-p
> -
>
> Key: MNG-8025
> URL: https://issues.apache.org/jira/browse/MNG-8025
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-alpha-12
>Reporter: Guillaume Nodet
>Priority: Major
> Fix For: 4.0.x-candidate
>
>
> {code:java}
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-remote-resources-plugin:3.1.0:process
> (default) on project sshd: Execution default of goal
> org.apache.maven.plugins:maven-remote-resources-plugin:3.1.0:process failed:
> An API incompatibility was encountered while executing
> org.apache.maven.plugins:maven-remote-resources-plugin:3.1.0:process:
> java.lang.NoSuchMethodError: 'void
> org.apache.maven.model.Plugin.unsetInheritanceApplied()'
> [ERROR] -
> [ERROR] realm =
> plugin>org.apache.maven.plugins:maven-remote-resources-plugin:3.1.0
> [ERROR] strategy = org.codehaus.plexus.classworlds.strategy.SelfFirstStrategy
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNGSITE-534) There is no hint about Maven Daemon - https://maven.apache.org/
[ https://issues.apache.org/jira/browse/MNGSITE-534?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MNGSITE-534: Description: Currently on the Maven site itself (maven.apache.org) there is no hint at all, reference to the Maven Daemon .. We should add a reference for downloading it on the page https://maven.apache.org/ The Maven Daemon site on Github https://github.com/apache/maven-mvnd references explicit https://maven.apache.org.. was:Currently on the Maven site itself (maven.apache.org) there is no hint at all, reference to the Maven Daemon .. We should add a reference for downloading it on the page https://maven.apache.org/ > There is no hint about Maven Daemon - https://maven.apache.org/ > --- > > Key: MNGSITE-534 > URL: https://issues.apache.org/jira/browse/MNGSITE-534 > Project: Maven Project Web Site > Issue Type: Improvement >Reporter: Karl Heinz Marbaise >Priority: Minor > > Currently on the Maven site itself (maven.apache.org) there is no hint at > all, reference to the Maven Daemon .. We should add a reference for > downloading it on the page https://maven.apache.org/ > The Maven Daemon site on Github https://github.com/apache/maven-mvnd > references explicit https://maven.apache.org.. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-8071) Build in parallel by default
Karl Heinz Marbaise created MNG-8071:
Summary: Build in parallel by default
Key: MNG-8071
URL: https://issues.apache.org/jira/browse/MNG-8071
Project: Maven
Issue Type: Improvement
Components: Command Line, Core
Affects Versions: 4.0.0
Reporter: Karl Heinz Marbaise
Fix For: Issues to be reviewed for 4.x
Currently to build in parallel you have to explicitly define {{-T ..}}. What
about just doing that by default in Maven 4?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MNGSITE-534) There is no hint about Maven Daemon - https://maven.apache.org/
Karl Heinz Marbaise created MNGSITE-534: --- Summary: There is no hint about Maven Daemon - https://maven.apache.org/ Key: MNGSITE-534 URL: https://issues.apache.org/jira/browse/MNGSITE-534 Project: Maven Project Web Site Issue Type: Improvement Reporter: Karl Heinz Marbaise Currently on the Maven site itself (maven.apache.org) there is no hint at all, reference to the Maven Daemon .. We should add a reference for downloading it on the page https://maven.apache.org/ -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MINVOKER-352) Remove usage commons-lang3
[ https://issues.apache.org/jira/browse/MINVOKER-352?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MINVOKER-352. Resolution: Fixed Done with https://github.com/apache/maven-invoker-plugin/commit/f61e240ed7eed015aac82fc9e121922febb43b16 > Remove usage commons-lang3 > -- > > Key: MINVOKER-352 > URL: https://issues.apache.org/jira/browse/MINVOKER-352 > Project: Maven Invoker Plugin > Issue Type: Improvement >Affects Versions: 3.6.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.x > > > Currently methods / classes of commons-lang3 are used only very few. We can > get rid of the usage. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MINVOKER-352) Remove usage commons-lang3
Karl Heinz Marbaise created MINVOKER-352: Summary: Remove usage commons-lang3 Key: MINVOKER-352 URL: https://issues.apache.org/jira/browse/MINVOKER-352 Project: Maven Invoker Plugin Issue Type: Improvement Affects Versions: 3.6.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.x Currently methods / classes of commons-lang3 are used only very few. We can get rid of the usage. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-7986) Spurious JUnit 4.12 jar on boot classpath
[
https://issues.apache.org/jira/browse/MNG-7986?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MNG-7986:
-
Fix Version/s: waiting-for-feedback
> Spurious JUnit 4.12 jar on boot classpath
> -
>
> Key: MNG-7986
> URL: https://issues.apache.org/jira/browse/MNG-7986
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 4.0.0-alpha-9
>Reporter: Jean Gauthier
>Priority: Major
> Fix For: waiting-for-feedback
>
> Attachments: output-maven-4.0.0-alpha8-surefire-2.22.2.txt,
> output-maven-4.0.0-alpha9-surefire-2.22.2.txt,
> output-maven-4.0.0-alpha9-surefire-3.0.0-M4.txt, reproducer.zip
>
>
> We noticed a regression in Maven 4.0.0-alpha9 for Surefire versions
> 2.21.0-3.0.0-M3: when specifying a dependency to JUnit 4.13, JUnit 4.12 gets
> added before it on the boot classpath.
> This causes issues e.g. when defining a custom JUnit 4 RunListener in a
> project: because JUnit 4.12 is listed first, the new {{testSuiteStarted}}
> callback that was added in 4.13 does not get invoked anymore.
> This can be reproduced by running {{./mvnw clean test
> -Dorg.slf4j.simpleLogger.log.org.apache.maven.plugin.surefire.SurefirePlugin=debug}}
> on the attached project (and setting the Maven/Surefire versions
> accordingly).
> I have also added the output logs for the following version combinations as
> attachment to the ticket:
> * Maven 4.0.0-alpha8 + Surefire 2.22.2 => works correctly (contains
> {{RunListener - testSuiteStarted}})
> * Maven 4.0.0-alpha9 + Surefire 2.22.2 => broken (does not contain
> {{RunListener - testSuiteStarted}})
> * Maven 4.0.0-alpha9 + Surefire 3.0.0-M4 => works correctly (contains
> {{RunListener - testSuiteStarted}})
> Please let me know in case additional information is needed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7986) Spurious JUnit 4.12 jar on boot classpath
[
https://issues.apache.org/jira/browse/MNG-7986?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17801370#comment-17801370
]
Karl Heinz Marbaise commented on MNG-7986:
--
That reproducer example contains a lot of far outdated plugins (apart from
usign Java 7 as target). I have updated all the plugins in the example in
relationship to https://maven.apache.org/plugins/ (most recent versions).
I tested with Maven 4.0.0-alpha-10, 3.9.6, 3.8.8, 3.6.3, 3.5.4, 3.3.9 and as
[~michael-o] suggest using Surefire 3.2.3 and it shows the expected output:
{code}
[INFO] --- maven-surefire-plugin:3.2.3:test (default-test) @ reproducer ---
[INFO] Using auto detected provider
org.apache.maven.surefire.junit4.JUnit4Provider
[INFO]
[INFO] ---
[INFO] T E S T S
[INFO] ---
Creation of Run Listener...
[INFO] Running org.example.SimpleTest
RunListener - testSuiteStarted
RunListener - testStarted
[INFO] Tests run: 1, Failures: 0, Errors: 0, Skipped: 0, Time elapsed: 0.021 s
-- in org.example.SimpleTest
[INFO]
{code}
That means in consequence you should upgrade all the plugins you are using
including the Maven version... We have a new alpha-10 version of Maven 4
available... https://maven.apache.org/docs/history.html
it's great to see people are testing with the new Maven 4.0.0 alpha versions,
but I recommend to test with most recent version of the plugins. Also I
recommend to take into account that JUnit 4.X might be out-of-date as well and
should be replaced it with JUnit Jupiter (aka JUnit 5) https://junit.org/junit5/
> Spurious JUnit 4.12 jar on boot classpath
> -
>
> Key: MNG-7986
> URL: https://issues.apache.org/jira/browse/MNG-7986
> Project: Maven
> Issue Type: Bug
> Components: Core
>Affects Versions: 4.0.0-alpha-9
>Reporter: Jean Gauthier
>Priority: Major
> Attachments: output-maven-4.0.0-alpha8-surefire-2.22.2.txt,
> output-maven-4.0.0-alpha9-surefire-2.22.2.txt,
> output-maven-4.0.0-alpha9-surefire-3.0.0-M4.txt, reproducer.zip
>
>
> We noticed a regression in Maven 4.0.0-alpha9 for Surefire versions
> 2.21.0-3.0.0-M3: when specifying a dependency to JUnit 4.13, JUnit 4.12 gets
> added before it on the boot classpath.
> This causes issues e.g. when defining a custom JUnit 4 RunListener in a
> project: because JUnit 4.12 is listed first, the new {{testSuiteStarted}}
> callback that was added in 4.13 does not get invoked anymore.
> This can be reproduced by running {{./mvnw clean test
> -Dorg.slf4j.simpleLogger.log.org.apache.maven.plugin.surefire.SurefirePlugin=debug}}
> on the attached project (and setting the Maven/Surefire versions
> accordingly).
> I have also added the output logs for the following version combinations as
> attachment to the ticket:
> * Maven 4.0.0-alpha8 + Surefire 2.22.2 => works correctly (contains
> {{RunListener - testSuiteStarted}})
> * Maven 4.0.0-alpha9 + Surefire 2.22.2 => broken (does not contain
> {{RunListener - testSuiteStarted}})
> * Maven 4.0.0-alpha9 + Surefire 3.0.0-M4 => works correctly (contains
> {{RunListener - testSuiteStarted}})
> Please let me know in case additional information is needed.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MINVOKER-350) Upgrade maven-plugin parent to 41
[ https://issues.apache.org/jira/browse/MINVOKER-350?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MINVOKER-350. Resolution: Done > Upgrade maven-plugin parent to 41 > - > > Key: MINVOKER-350 > URL: https://issues.apache.org/jira/browse/MINVOKER-350 > Project: Maven Invoker Plugin > Issue Type: Improvement >Affects Versions: 3.6.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.x > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MINVOKER-350) Upgrade maven-plugin parent to 41
[ https://issues.apache.org/jira/browse/MINVOKER-350?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17801338#comment-17801338 ] Karl Heinz Marbaise commented on MINVOKER-350: -- Done in [d3a7592143f48d260536b0d8acfa9f9d878c7d7c|https://gitbox.apache.org/repos/asf?p=maven-invoker-plugin.git;a=commitdiff;h=d3a7592143f48d260536b0d8acfa9f9d878c7d7c] > Upgrade maven-plugin parent to 41 > - > > Key: MINVOKER-350 > URL: https://issues.apache.org/jira/browse/MINVOKER-350 > Project: Maven Invoker Plugin > Issue Type: Improvement >Affects Versions: 3.6.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.x > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7989) Making this build non-interactive, because the environment variable CI equals "true".
[
https://issues.apache.org/jira/browse/MNG-7989?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17799906#comment-17799906
]
Karl Heinz Marbaise commented on MNG-7989:
--
Done in
[23d13fb322b8d66f03f02ece57d75e154f847367|https://gitbox.apache.org/repos/asf?p=maven.git;a=commitdiff;h=23d13fb322b8d66f03f02ece57d75e154f847367]
> Making this build non-interactive, because the environment variable CI equals
> "true".
> -
>
> Key: MNG-7989
> URL: https://issues.apache.org/jira/browse/MNG-7989
> Project: Maven
> Issue Type: Improvement
> Components: Command Line, Core
>Affects Versions: 4.0.0-alpha-10
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 4.0.0, 4.0.0-alpha-11
>
>
> I'm running Maven 4.0.0-alpha-10 on CI (GitHub action) and the output shows
> me the information line:
> {code:java}
> [INFO] Making this build non-interactive, because the environment variable CI
> equals "true". Disable this detection by removing that variable or adding
> --force-interactive.
> {code}
> The output at the beginning of my build:
> {code:java}
> Run mvn verify -Prun-its -e -B -V --no-transfer-progress
> Apache Maven 4.0.0-alpha-10 (89d3c0321dda868c432edf504f1884e6fd706f00)
> Maven home: /opt/hostedtoolcache/maven/4.0.0/x64
> Java version: 21.0.1, vendor: Eclipse Adoptium, runtime:
> /usr/lib/jvm/temurin-21-jdk-amd64
> Default locale: en, platform encoding: UTF-8
> OS name: "linux", version: "6.2.0-1018-azure", arch: "amd64", family: "unix"
> [INFO] Error stacktraces are turned on.
> [INFO] Making this build non-interactive, because the environment variable CI
> equals "true". Disable this detection by removing that variable or adding
> --force-interactive.
> [INFO] Scanning for projects...
> [INFO] -
> {code}
> As I already set the non-interactive mode via {{-B}} (batch-mode) it would
> make sense in such case not to show the message.
> My opinion is to check for {{env.CI}} after the check for running
> non-interactive.. so in my case the message will not being printed. If I
> don't set the non-interactive mode it will exactly do this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MNG-7989) Making this build non-interactive, because the environment variable CI equals "true".
[
https://issues.apache.org/jira/browse/MNG-7989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MNG-7989.
Resolution: Done
> Making this build non-interactive, because the environment variable CI equals
> "true".
> -
>
> Key: MNG-7989
> URL: https://issues.apache.org/jira/browse/MNG-7989
> Project: Maven
> Issue Type: Improvement
> Components: Command Line, Core
>Affects Versions: 4.0.0-alpha-10
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 4.0.0-alpha-11, 4.0.0
>
>
> I'm running Maven 4.0.0-alpha-10 on CI (GitHub action) and the output shows
> me the information line:
> {code:java}
> [INFO] Making this build non-interactive, because the environment variable CI
> equals "true". Disable this detection by removing that variable or adding
> --force-interactive.
> {code}
> The output at the beginning of my build:
> {code:java}
> Run mvn verify -Prun-its -e -B -V --no-transfer-progress
> Apache Maven 4.0.0-alpha-10 (89d3c0321dda868c432edf504f1884e6fd706f00)
> Maven home: /opt/hostedtoolcache/maven/4.0.0/x64
> Java version: 21.0.1, vendor: Eclipse Adoptium, runtime:
> /usr/lib/jvm/temurin-21-jdk-amd64
> Default locale: en, platform encoding: UTF-8
> OS name: "linux", version: "6.2.0-1018-azure", arch: "amd64", family: "unix"
> [INFO] Error stacktraces are turned on.
> [INFO] Making this build non-interactive, because the environment variable CI
> equals "true". Disable this detection by removing that variable or adding
> --force-interactive.
> [INFO] Scanning for projects...
> [INFO] -
> {code}
> As I already set the non-interactive mode via {{-B}} (batch-mode) it would
> make sense in such case not to show the message.
> My opinion is to check for {{env.CI}} after the check for running
> non-interactive.. so in my case the message will not being printed. If I
> don't set the non-interactive mode it will exactly do this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MNG-7989) Making this build non-interactive, because the environment variable CI equals "true".
[
https://issues.apache.org/jira/browse/MNG-7989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MNG-7989:
-
Description:
I'm running Maven 4.0.0-alpha-10 on CI (GitHub action) and the output shows me
the information line:
{code:java}
[INFO] Making this build non-interactive, because the environment variable CI
equals "true". Disable this detection by removing that variable or adding
--force-interactive.
{code}
The output at the beginning of my build:
{code:java}
Run mvn verify -Prun-its -e -B -V --no-transfer-progress
Apache Maven 4.0.0-alpha-10 (89d3c0321dda868c432edf504f1884e6fd706f00)
Maven home: /opt/hostedtoolcache/maven/4.0.0/x64
Java version: 21.0.1, vendor: Eclipse Adoptium, runtime:
/usr/lib/jvm/temurin-21-jdk-amd64
Default locale: en, platform encoding: UTF-8
OS name: "linux", version: "6.2.0-1018-azure", arch: "amd64", family: "unix"
[INFO] Error stacktraces are turned on.
[INFO] Making this build non-interactive, because the environment variable CI
equals "true". Disable this detection by removing that variable or adding
--force-interactive.
[INFO] Scanning for projects...
[INFO] -
{code}
As I already set the non-interactive mode via {{-B}} (batch-mode) it would make
sense in such case not to show the message.
My opinion is to check for {{env.CI}} after the check for running
non-interactive.. so in my case the message will not being printed. If I don't
set the non-interactive mode it will exactly do this.
was:
I'm running Maven 4.0.0-alpha-10 on CI (GitHub action) and the output shows me
the information line:
{code:java}
15[INFO] Making this build non-interactive, because the environment variable CI
equals "true". Disable this detection by removing that variable or adding
--force-interactive.
{code}
The output at the beginning of my build:
{code:java}
Run mvn verify -Prun-its -e -B -V --no-transfer-progress
9Apache Maven 4.0.0-alpha-10 (89d3c0321dda868c432edf504f1884e6fd706f00)
10Maven home: /opt/hostedtoolcache/maven/4.0.0/x64
11Java version: 21.0.1, vendor: Eclipse Adoptium, runtime:
/usr/lib/jvm/temurin-21-jdk-amd64
12Default locale: en, platform encoding: UTF-8
13OS name: "linux", version: "6.2.0-1018-azure", arch: "amd64", family: "unix"
14[INFO] Error stacktraces are turned on.
15[INFO] Making this build non-interactive, because the environment variable CI
equals "true". Disable this detection by removing that variable or adding
--force-interactive.
16[INFO] Scanning for projects...
17[INFO] -
{code}
As I already set the non-interactive mode via {{-B}} (batch-mode) it would make
sense in such case not to show the message.
My opinion is to check for {{env.CI}} after the check for running
non-interactive.. so in my case the message will not being printed. If I don't
set the non-interactive mode it will exactly do this.
> Making this build non-interactive, because the environment variable CI equals
> "true".
> -
>
> Key: MNG-7989
> URL: https://issues.apache.org/jira/browse/MNG-7989
> Project: Maven
> Issue Type: Improvement
> Components: Command Line, Core
>Affects Versions: 4.0.0-alpha-10
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 4.0.0, 4.0.0-alpha-11
>
>
> I'm running Maven 4.0.0-alpha-10 on CI (GitHub action) and the output shows
> me the information line:
> {code:java}
> [INFO] Making this build non-interactive, because the environment variable CI
> equals "true". Disable this detection by removing that variable or adding
> --force-interactive.
> {code}
> The output at the beginning of my build:
> {code:java}
> Run mvn verify -Prun-its -e -B -V --no-transfer-progress
> Apache Maven 4.0.0-alpha-10 (89d3c0321dda868c432edf504f1884e6fd706f00)
> Maven home: /opt/hostedtoolcache/maven/4.0.0/x64
> Java version: 21.0.1, vendor: Eclipse Adoptium, runtime:
> /usr/lib/jvm/temurin-21-jdk-amd64
> Default locale: en, platform encoding: UTF-8
> OS name: "linux", version: "6.2.0-1018-azure", arch: "amd64", family: "unix"
> [INFO] Error stacktraces are turned on.
> [INFO] Making this build non-interactive, because the environment variable CI
> equals "true". Disable this detection by removing that variable or adding
> --force-interactive.
> [INFO] Scanning for projects...
> [INFO] -
> {code}
> As I already set the non-interactive mode via {{-B}} (batch-mode) it would
> make sense in such case not to show the message.
> My opinion is to check for {{env.CI}} after the check for running
> non-interactive.. so in my case the message will not being printed. If I
> don't set the non-interactive mode it will exactly do this.
--
This
[jira] [Updated] (MNG-7989) Making this build non-interactive, because the environment variable CI equals "true".
[
https://issues.apache.org/jira/browse/MNG-7989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MNG-7989:
-
Description:
I'm running Maven 4.0.0-alpha-10 on CI (GitHub action) and the output shows me
the information line:
{code:java}
15[INFO] Making this build non-interactive, because the environment variable CI
equals "true". Disable this detection by removing that variable or adding
--force-interactive.
{code}
The output at the beginning of my build:
{code:java}
Run mvn verify -Prun-its -e -B -V --no-transfer-progress
9Apache Maven 4.0.0-alpha-10 (89d3c0321dda868c432edf504f1884e6fd706f00)
10Maven home: /opt/hostedtoolcache/maven/4.0.0/x64
11Java version: 21.0.1, vendor: Eclipse Adoptium, runtime:
/usr/lib/jvm/temurin-21-jdk-amd64
12Default locale: en, platform encoding: UTF-8
13OS name: "linux", version: "6.2.0-1018-azure", arch: "amd64", family: "unix"
14[INFO] Error stacktraces are turned on.
15[INFO] Making this build non-interactive, because the environment variable CI
equals "true". Disable this detection by removing that variable or adding
--force-interactive.
16[INFO] Scanning for projects...
17[INFO] -
{code}
As I already set the non-interactive mode via {{-B}} (batch-mode) it would make
sense in such case not to show the message.
My opinion is to check for {{env.CI}} after the check for running
non-interactive.. so in my case the message will not being printed. If I don't
set the non-interactive mode it will exactly do this.
was:
I'm running Maven 4.0.0-alpha-10 in CI (github action) and the output shows me
the information line:
{code}
15[INFO] Making this build non-interactive, because the environment variable CI
equals "true". Disable this detection by removing that variable or adding
--force-interactive.
{code}
The output at the beginning of my build:
{code}
Run mvn verify -Prun-its -e -B -V --no-transfer-progress
9Apache Maven 4.0.0-alpha-10 (89d3c0321dda868c432edf504f1884e6fd706f00)
10Maven home: /opt/hostedtoolcache/maven/4.0.0/x64
11Java version: 21.0.1, vendor: Eclipse Adoptium, runtime:
/usr/lib/jvm/temurin-21-jdk-amd64
12Default locale: en, platform encoding: UTF-8
13OS name: "linux", version: "6.2.0-1018-azure", arch: "amd64", family: "unix"
14[INFO] Error stacktraces are turned on.
15[INFO] Making this build non-interactive, because the environment variable CI
equals "true". Disable this detection by removing that variable or adding
--force-interactive.
16[INFO] Scanning for projects...
17[INFO] -
{code}
As I already set the non-interactive mode via {{-B}} (batch-mode) it would make
sense in such case not to show the message.
My opinion is to check for {{env.CI}} after the check for running
non-interactive.. so in my case the message will not being printed. If I don't
set the non-interactive mode it will exactly do this.
> Making this build non-interactive, because the environment variable CI equals
> "true".
> -
>
> Key: MNG-7989
> URL: https://issues.apache.org/jira/browse/MNG-7989
> Project: Maven
> Issue Type: Improvement
> Components: Command Line, Core
>Affects Versions: 4.0.0-alpha-10
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 4.0.0, 4.0.0-alpha-11
>
>
> I'm running Maven 4.0.0-alpha-10 on CI (GitHub action) and the output shows
> me the information line:
> {code:java}
> 15[INFO] Making this build non-interactive, because the environment variable
> CI equals "true". Disable this detection by removing that variable or adding
> --force-interactive.
> {code}
> The output at the beginning of my build:
> {code:java}
> Run mvn verify -Prun-its -e -B -V --no-transfer-progress
> 9Apache Maven 4.0.0-alpha-10 (89d3c0321dda868c432edf504f1884e6fd706f00)
> 10Maven home: /opt/hostedtoolcache/maven/4.0.0/x64
> 11Java version: 21.0.1, vendor: Eclipse Adoptium, runtime:
> /usr/lib/jvm/temurin-21-jdk-amd64
> 12Default locale: en, platform encoding: UTF-8
> 13OS name: "linux", version: "6.2.0-1018-azure", arch: "amd64", family: "unix"
> 14[INFO] Error stacktraces are turned on.
> 15[INFO] Making this build non-interactive, because the environment variable
> CI equals "true". Disable this detection by removing that variable or adding
> --force-interactive.
> 16[INFO] Scanning for projects...
> 17[INFO] -
> {code}
> As I already set the non-interactive mode via {{-B}} (batch-mode) it would
> make sense in such case not to show the message.
> My opinion is to check for {{env.CI}} after the check for running
> non-interactive.. so in my case the message will not being printed. If I
> don't set the non-interactive mode it will
[jira] [Updated] (MNG-7989) Making this build non-interactive, because the environment variable CI equals "true".
[
https://issues.apache.org/jira/browse/MNG-7989?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MNG-7989:
-
Description:
I'm running Maven 4.0.0-alpha-10 in CI (github action) and the output shows me
the information line:
{code}
15[INFO] Making this build non-interactive, because the environment variable CI
equals "true". Disable this detection by removing that variable or adding
--force-interactive.
{code}
The output at the beginning of my build:
{code}
Run mvn verify -Prun-its -e -B -V --no-transfer-progress
9Apache Maven 4.0.0-alpha-10 (89d3c0321dda868c432edf504f1884e6fd706f00)
10Maven home: /opt/hostedtoolcache/maven/4.0.0/x64
11Java version: 21.0.1, vendor: Eclipse Adoptium, runtime:
/usr/lib/jvm/temurin-21-jdk-amd64
12Default locale: en, platform encoding: UTF-8
13OS name: "linux", version: "6.2.0-1018-azure", arch: "amd64", family: "unix"
14[INFO] Error stacktraces are turned on.
15[INFO] Making this build non-interactive, because the environment variable CI
equals "true". Disable this detection by removing that variable or adding
--force-interactive.
16[INFO] Scanning for projects...
17[INFO] -
{code}
As I already set the non-interactive mode via {{-B}} (batch-mode) it would make
sense in such case not to show the message.
My opinion is to check for {{env.CI}} after the check for running
non-interactive.. so in my case the message will not being printed. If I don't
set the non-interactive mode it will exactly do this.
was:
I'm running Maven 4.0.0-alpha-10 in CI (github action) and the output shows me
the information line:
{code}
15[INFO] Making this build non-interactive, because the environment variable CI
equals "true". Disable this detection by removing that variable or adding
--force-interactive.
{code}
The run output:
{code:java}
Run mvn verify -Prun-its -e -B -V --no-transfer-progress
9Apache Maven 4.0.0-alpha-10 (89d3c0321dda868c432edf504f1884e6fd706f00)
10Maven home: /opt/hostedtoolcache/maven/4.0.0/x64
11Java version: 21.0.1, vendor: Eclipse Adoptium, runtime:
/usr/lib/jvm/temurin-21-jdk-amd64
12Default locale: en, platform encoding: UTF-8
13OS name: "linux", version: "6.2.0-1018-azure", arch: "amd64", family: "unix"
14[INFO] Error stacktraces are turned on.
15[INFO] Making this build non-interactive, because the environment variable CI
equals "true". Disable this detection by removing that variable or adding
--force-interactive.
16[INFO] Scanning for projects...
17[INFO] - {code}
{code}
As I already set the non-interactive mode via {{-B}} (batch-mode) it would make
sense in such case not to show the message.
My opinion is to check for {{env.CI}} after the check for running
non-interactive.. so in my case the message will not being printed. If I don't
set the non-interactive mode it will exactly do this.
> Making this build non-interactive, because the environment variable CI equals
> "true".
> -
>
> Key: MNG-7989
> URL: https://issues.apache.org/jira/browse/MNG-7989
> Project: Maven
> Issue Type: Improvement
> Components: Command Line, Core
>Affects Versions: 4.0.0-alpha-10
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 4.0.0, 4.0.0-alpha-11
>
>
> I'm running Maven 4.0.0-alpha-10 in CI (github action) and the output shows
> me the information line:
> {code}
> 15[INFO] Making this build non-interactive, because the environment variable
> CI equals "true". Disable this detection by removing that variable or adding
> --force-interactive.
> {code}
> The output at the beginning of my build:
> {code}
> Run mvn verify -Prun-its -e -B -V --no-transfer-progress
> 9Apache Maven 4.0.0-alpha-10 (89d3c0321dda868c432edf504f1884e6fd706f00)
> 10Maven home: /opt/hostedtoolcache/maven/4.0.0/x64
> 11Java version: 21.0.1, vendor: Eclipse Adoptium, runtime:
> /usr/lib/jvm/temurin-21-jdk-amd64
> 12Default locale: en, platform encoding: UTF-8
> 13OS name: "linux", version: "6.2.0-1018-azure", arch: "amd64", family: "unix"
> 14[INFO] Error stacktraces are turned on.
> 15[INFO] Making this build non-interactive, because the environment variable
> CI equals "true". Disable this detection by removing that variable or adding
> --force-interactive.
> 16[INFO] Scanning for projects...
> 17[INFO] -
> {code}
> As I already set the non-interactive mode via {{-B}} (batch-mode) it would
> make sense in such case not to show the message.
> My opinion is to check for {{env.CI}} after the check for running
> non-interactive.. so in my case the message will not being printed. If I
> don't set the non-interactive mode it will exactly do this.
--
This
[jira] [Created] (MNG-7989) Making this build non-interactive, because the environment variable CI equals "true".
Karl Heinz Marbaise created MNG-7989:
Summary: Making this build non-interactive, because the
environment variable CI equals "true".
Key: MNG-7989
URL: https://issues.apache.org/jira/browse/MNG-7989
Project: Maven
Issue Type: Improvement
Components: Command Line, Core
Affects Versions: 4.0.0-alpha-10
Reporter: Karl Heinz Marbaise
Assignee: Karl Heinz Marbaise
Fix For: 4.0.0, 4.0.0-alpha-11
I'm running Maven 4.0.0-alpha-10 in CI (github action) and the output shows me
the information line:
{code}
15[INFO] Making this build non-interactive, because the environment variable CI
equals "true". Disable this detection by removing that variable or adding
--force-interactive.
{code}
The run output:
{code:java}
Run mvn verify -Prun-its -e -B -V --no-transfer-progress
9Apache Maven 4.0.0-alpha-10 (89d3c0321dda868c432edf504f1884e6fd706f00)
10Maven home: /opt/hostedtoolcache/maven/4.0.0/x64
11Java version: 21.0.1, vendor: Eclipse Adoptium, runtime:
/usr/lib/jvm/temurin-21-jdk-amd64
12Default locale: en, platform encoding: UTF-8
13OS name: "linux", version: "6.2.0-1018-azure", arch: "amd64", family: "unix"
14[INFO] Error stacktraces are turned on.
15[INFO] Making this build non-interactive, because the environment variable CI
equals "true". Disable this detection by removing that variable or adding
--force-interactive.
16[INFO] Scanning for projects...
17[INFO] - {code}
{code}
As I already set the non-interactive mode via {{-B}} (batch-mode) it would make
sense in such case not to show the message.
My opinion is to check for {{env.CI}} after the check for running
non-interactive.. so in my case the message will not being printed. If I don't
set the non-interactive mode it will exactly do this.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7944) Execution default of goal org.apache.maven.plugins:maven-assembly-plugin:3.6.0:single failed: Index 2 out of bounds for length 2
[
https://issues.apache.org/jira/browse/MNG-7944?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795074#comment-17795074
]
Karl Heinz Marbaise commented on MNG-7944:
--
Please create a full reproducer...
> Execution default of goal
> org.apache.maven.plugins:maven-assembly-plugin:3.6.0:single failed: Index 2
> out of bounds for length 2
>
>
> Key: MNG-7944
> URL: https://issues.apache.org/jira/browse/MNG-7944
> Project: Maven
> Issue Type: Bug
>Affects Versions: 4.0.0-alpha-8
>Reporter: Filipe Roque
>Priority: Major
>
> It only affects apache-maven-4.0.0-alpha-8
> pom.xml
> {code:java}
>
> http://maven.apache.org/POM/4.0.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
> http://maven.apache.org/xsd/maven-4.0.0.xsd;>
> 4.0.0
> org.example
> mvn4-assembly-index
> 1.0-SNAPSHOT
>
> 17
> 17
> UTF-8
>
>
>
> org.ehcache
> ehcache
> 3.10.8
>
>
>
>
>
> org.apache.maven.plugins
> maven-assembly-plugin
> 3.6.0
>
>
>
> src/main/assembly/descriptor.xml
>
> false
>
>
>
> package
>
> single
>
>
>
>
>
>
> {code}
> descriptor.xml
> {code:java}
> http://maven.apache.org/ASSEMBLY/2.1.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/ASSEMBLY/2.1.0
> http://maven.apache.org/xsd/assembly-2.1.0.xsd;>
> assembly
>
> dir
>
> false
> .
>
>
> /
> false
> runtime
>
>
>
> {code}
> {code:java}
> ❯ /opt/maven/apache-maven-4.0.0-alpha-8/bin/mvn -q package
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-assembly-plugin:3.6.0:single (default) on
> project mvn4-assembly-index: Execution default of goal
> org.apache.maven.plugins:maven-assembly-plugin:3.6.0:single failed: Index 2
> out of bounds for length 2 -> [Help 1]
> [ERROR]
> [ERROR] To see the full stack trace of the errors, re-run Maven with the '-e'
> switch
> [ERROR] Re-run Maven using the '-X' switch to enable verbose output
> [ERROR]
> [ERROR] For more information about the errors and possible solutions, please
> read the following articles:
> [ERROR] [Help 1]
> http://cwiki.apache.org/confluence/display/MAVEN/PluginExecutionException
> {code}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MINSTALL-196) Maven 3.9.x install:install-file doesn't recognize -Dpackaging
[
https://issues.apache.org/jira/browse/MINSTALL-196?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17795073#comment-17795073
]
Karl Heinz Marbaise commented on MINSTALL-196:
--
Can you please show the log output and expliclty write which version of the
maven-install-plugin you are using? Unfortunately you have written about the
Maven verison but not about the plugin version...
Based on the default bindings
[https://maven.apache.org/ref/3.8.8/maven-core/default-bindings.html] I assume
your version of the maven-install-plugin is 2.4 (assumed that you have not
defined the version yourself) and for Maven 3.9.6
(https://maven.apache.org/ref/3.9.6/maven-core/default-bindings.html) the
plugin version is 3.1.1 ... ?
> Maven 3.9.x install:install-file doesn't recognize -Dpackaging
> --
>
> Key: MINSTALL-196
> URL: https://issues.apache.org/jira/browse/MINSTALL-196
> Project: Maven Install Plugin
> Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: Wei-Chiu Chuang
>Priority: Major
>
> Hi there is a behavior change between Maven 3.8.8 and 3.9.6 where mvn
> install:install-file doesn't recognize -Dpackaging=exe
> Reproducible on Apple Mac M3
> {noformat}
> PROTOBUF_VERSION="3.7.1"
> curl -LO
> https://github.com/protocolbuffers/protobuf/releases/download/v${PROTOBUF_VERSION}/protobuf-all-${PROTOBUF_VERSION}.tar.gz
> tar xzf protobuf-all-${PROTOBUF_VERSION}.tar.gz
> cd protobuf-${PROTOBUF_VERSION}
> ./configure --disable-shared
> make -j
> mvn install:install-file -DgroupId=com.google.protobuf -DartifactId=protoc
> -Dversion=${PROTOBUF_VERSION} -Dclassifier=osx-aarch_64 -Dpackaging=exe
> -Dfile=src/protoc
> {noformat}
> Expected result (Maven 3.8 and below):
> artifact installed at
> ~/.m2/repository/com/google/protobuf/protoc/3.7.1/protoc-3.7.1-osx-aarch_64.exe
> Incorrect result (Maven 3.9.x)
> artifact installed at
> ~/.m2/repository/com/google/protobuf/protoc/3.7.1/protoc-3.7.1-osx-aarch_64
>
> Because of the missing suffix ".exe", Apache Ozone is not able to build on
> Apple Mac M3 using Maven 3.9.x. It works fine with Maven 3.8.x
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Moved] (MINSTALL-196) Maven 3.9.x install:install-file doesn't recognize -Dpackaging
[
https://issues.apache.org/jira/browse/MINSTALL-196?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise moved MNG-7952 to MINSTALL-196:
---
Key: MINSTALL-196 (was: MNG-7952)
Affects Version/s: 3.0.1
(was: 3.9.6)
Project: Maven Install Plugin (was: Maven)
> Maven 3.9.x install:install-file doesn't recognize -Dpackaging
> --
>
> Key: MINSTALL-196
> URL: https://issues.apache.org/jira/browse/MINSTALL-196
> Project: Maven Install Plugin
> Issue Type: Bug
>Affects Versions: 3.0.1
>Reporter: Wei-Chiu Chuang
>Priority: Major
>
> Hi there is a behavior change between Maven 3.8.8 and 3.9.6 where mvn
> install:install-file doesn't recognize -Dpackaging=exe
> Reproducible on Apple Mac M3
> {noformat}
> PROTOBUF_VERSION="3.7.1"
> curl -LO
> https://github.com/protocolbuffers/protobuf/releases/download/v${PROTOBUF_VERSION}/protobuf-all-${PROTOBUF_VERSION}.tar.gz
> tar xzf protobuf-all-${PROTOBUF_VERSION}.tar.gz
> cd protobuf-${PROTOBUF_VERSION}
> ./configure --disable-shared
> make -j
> mvn install:install-file -DgroupId=com.google.protobuf -DartifactId=protoc
> -Dversion=${PROTOBUF_VERSION} -Dclassifier=osx-aarch_64 -Dpackaging=exe
> -Dfile=src/protoc
> {noformat}
> Expected result (Maven 3.8 and below):
> artifact installed at
> ~/.m2/repository/com/google/protobuf/protoc/3.7.1/protoc-3.7.1-osx-aarch_64.exe
> Incorrect result (Maven 3.9.x)
> artifact installed at
> ~/.m2/repository/com/google/protobuf/protoc/3.7.1/protoc-3.7.1-osx-aarch_64
>
> Because of the missing suffix ".exe", Apache Ozone is not able to build on
> Apple Mac M3 using Maven 3.9.x. It works fine with Maven 3.8.x
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MJAR-299) Upgrade maven-plugin parent to 41
[ https://issues.apache.org/jira/browse/MJAR-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MJAR-299. Resolution: Done > Upgrade maven-plugin parent to 41 > - > > Key: MJAR-299 > URL: https://issues.apache.org/jira/browse/MJAR-299 > Project: Maven JAR Plugin > Issue Type: Improvement >Affects Versions: 3.3.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MJAR-299) Upgrade maven-plugin parent to 41
[ https://issues.apache.org/jira/browse/MJAR-299?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17787506#comment-17787506 ] Karl Heinz Marbaise commented on MJAR-299: -- Done in [0cbcfd42e26207331cc3ad831a3888cb04591f07|https://gitbox.apache.org/repos/asf?p=maven-jar-plugin.git;a=commitdiff;h=0cbcfd42e26207331cc3ad831a3888cb04591f07] > Upgrade maven-plugin parent to 41 > - > > Key: MJAR-299 > URL: https://issues.apache.org/jira/browse/MJAR-299 > Project: Maven JAR Plugin > Issue Type: Improvement >Affects Versions: 3.3.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MJAVADOC-779) Upgrade maven-plugin parent to 41
[ https://issues.apache.org/jira/browse/MJAVADOC-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MJAVADOC-779. Resolution: Done > Upgrade maven-plugin parent to 41 > - > > Key: MJAVADOC-779 > URL: https://issues.apache.org/jira/browse/MJAVADOC-779 > Project: Maven Javadoc Plugin > Issue Type: Improvement >Affects Versions: 3.6.2 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.6.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MJAVADOC-779) Upgrade maven-plugin parent to 41
[ https://issues.apache.org/jira/browse/MJAVADOC-779?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17787504#comment-17787504 ] Karl Heinz Marbaise commented on MJAVADOC-779: -- Done in [692d7a8a9918efd24633a44f0f3d4dfd22d0fec4|https://gitbox.apache.org/repos/asf?p=maven-javadoc-plugin.git;a=commitdiff;h=692d7a8a9918efd24633a44f0f3d4dfd22d0fec4] > Upgrade maven-plugin parent to 41 > - > > Key: MJAVADOC-779 > URL: https://issues.apache.org/jira/browse/MJAVADOC-779 > Project: Maven Javadoc Plugin > Issue Type: Improvement >Affects Versions: 3.6.2 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.6.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Comment Edited] (MNG-7920) Usage of packaging BOM fails in maven-install-plugin
[
https://issues.apache.org/jira/browse/MNG-7920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17787385#comment-17787385
]
Karl Heinz Marbaise edited comment on MNG-7920 at 11/18/23 2:14 PM:
So after diving a bit deeper into this... it looks like the resulting
{{pom.xml}} should be made the main artifact of the {{bom}} packaged project
because in the end it's the main artifact of the module. For example if we have
a normal pom packaged module it works the same. The {{maven-install-plugin}}
already WARNs exactly about that. Furthermore is my opinion that the
{{maven-install-plugin}} should not needed to be changed because the main
artifact is the resulting {{{}pom{}}}.
So the core should assign the interpolated (bom) as the main artifact
(packaging: pom) while the {{pom-build}} is already attached as classifier
based artifacts.
I created a full reproducer to look more in detail on the problems:
Lets start with the {{bom}} packaging module which contains the following
(original pom):
{code:xml}
maven.four.bug.7920
bom-example
bom
bom
Maven Bug :: 7920 :: BOM
maven.four.bug.7920
mod-1
maven.four.bug.7920
mod-2
..
{code}
So the above {{pom.xml}} is converted into {{pom}} packaging based
{{{}pom.xml{}}}.. it looks like this:
{code:xml}
http://maven.apache.org/POM/4.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
https://maven.apache.org/xsd/maven-4.0.0.xsd;>
4.0.0
maven.four.bug.7920
bom
1.0.0-SNAPSHOT
pom
Maven Bug :: 7920 :: BOM
maven.four.bug.7920
mod-1
maven.four.bug.7920
mod-2
org.junit.jupiter
junit-jupiter
5.10.1
org.assertj
assertj-core
3.24.2
org.assertj
assertj-guava
3.24.2
...
{code}
The list of issues I found from my point of view:
# So the first issue I can identify is that the integrated artifacts:
{code:xml}
maven.four.bug.7920
mod-1
maven.four.bug.7920
mod-2
{code}
do not contain a version number.
# The second issue I can identify is that it contains all bom's resolved which
are from the module parent (see junit-jupiter, assertj, mockito), but *not* the
test scoped dependencies of the {{mod-1}} (added a dependency to
{{junit:junit:4.13.2}} and a non test scoped dependency
{{{}commons-collections:commons-collections:3.2.2{}}}.
>From my point of view the resulting {{pom.xml}} should look like this:
{code:xml}
http://maven.apache.org/POM/4.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
https://maven.apache.org/xsd/maven-4.0.0.xsd;>
4.0.0
maven.four.bug.7920
bom
1.0.0-SNAPSHOT
pom
Maven Bug :: 7920 :: BOM
maven.four.bug.7920
mod-1
1.0.0-SNAPSHOT
maven.four.bug.7920
mod-2
1.0.0-SNAPSHOT
{code}
It should contain things like: URL, name, organization, developers, licenses,
issueManagement, ciManagement(no),distributionManagement(no), repositories (no)
The link to the full repoducer:
[https://github.com/khmarbaise/maven-bugs/tree/master/MNG-7920]
was (Author: khmarbaise):
So after diving a bit deeper into this... it looks like the resulting
{{pom.xml}} should be made the main artifact of the {{bom}} packaged project
because in the end it's the main artifact of the module. For example if we have
a normal pom packaged module it works the same. The {{maven-install-plugin}}
already WARNs exactly about that. Furthermore is my opinion that the
{{maven-install-plugin}} should not needed to be changed because the main
artifact is the resulting {{{}pom{}}}.
So the core should assign the interpolated (bom) as the main artifact
(packaging: pom) while the {{pom-build}} is already attached as classifier
based artifacts.
I created a full reproducer to look more in detail on the problems:
Lets start with the {{bom}} packaging module which contains the following
(original pom):
{code:xml}
maven.four.bug.7920
bom-example
bom
bom
Maven Bug :: 7920 :: BOM
maven.four.bug.7920
mod-1
maven.four.bug.7920
mod-2
..
{code}
So the above {{pom.xml}} is converted into {{pom}} packaging based
{{{}pom.xml{}}}.. it looks like this:
{code:xml}
http://maven.apache.org/POM/4.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
https://maven.apache.org/xsd/maven-4.0.0.xsd;>
4.0.0
maven.four.bug.7920
bom
1.0.0-SNAPSHOT
pom
[jira] [Commented] (MNG-7920) Usage of packaging BOM fails in maven-install-plugin
[
https://issues.apache.org/jira/browse/MNG-7920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17787494#comment-17787494
]
Karl Heinz Marbaise commented on MNG-7920:
--
[~crazyhzm] where have I wrote about parse and include the version? I have
added the resulting pom file in my comment also you can use my repo as a test
to reproduce it.. as you can see it's the original pom and not the
interpolated and translated pom file...
And to your second point. Yes I expect that only the information is part of it
as I described in my "From my point of view the resulting {{pom.xml}} should
look like this:" ...
> Usage of packaging BOM fails in maven-install-plugin
>
>
> Key: MNG-7920
> URL: https://issues.apache.org/jira/browse/MNG-7920
> Project: Maven
> Issue Type: Bug
> Components: Deployment
>Affects Versions: 4.0.0-alpha-8
>Reporter: Karl Heinz Marbaise
>Priority: Critical
> Fix For: 4.0.0, 4.0.0-alpha-9
>
>
> Using to use the {{bom}} packaging in a module it will fail with:
> {code}
> [INFO]
> --
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-install-plugin:3.1.1:install (default-install)
> on project bom: The packaging plugin for this project did not assign a main
> file to the project but it has attachments. Change packaging to 'pom'. ->
> [Help 1]
> {code}
> The bom module looks like this:
> {code:xml}
>xmlns="http://maven.apache.org/POM/4.1.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.1.0
> http://maven.apache.org/maven-v4_1_0.xsd;>
> 4.1.0
>
> maven4
> bom-example
>
> bom
> bom
>
>
>
> ...maven4
> mod-1
>
>
> maven4
> mod-2
>
>
>
>
> {code}
> I would assume that I need to upgrade the maven-install-plugin which is
> capable of handling that...but I assumed that this conversion is done by core?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Comment Edited] (MNG-7920) Usage of packaging BOM fails in maven-install-plugin
[
https://issues.apache.org/jira/browse/MNG-7920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17787385#comment-17787385
]
Karl Heinz Marbaise edited comment on MNG-7920 at 11/18/23 2:10 PM:
So after diving a bit deeper into this... it looks like the resulting
{{pom.xml}} should be made the main artifact of the {{bom}} packaged project
because in the end it's the main artifact of the module. For example if we have
a normal pom packaged module it works the same. The {{maven-install-plugin}}
already WARNs exactly about that. Furthermore is my opinion that the
{{maven-install-plugin}} should not needed to be changed because the main
artifact is the resulting {{{}pom{}}}.
So the core should assign the interpolated (bom) as the main artifact
(packaging: pom) while the {{pom-build}} is already attached as classifier
based artifacts.
I created a full reproducer to look more in detail on the problems:
Lets start with the {{bom}} packaging module which contains the following
(original pom):
{code:xml}
maven.four.bug.7920
bom-example
bom
bom
Maven Bug :: 7920 :: BOM
maven.four.bug.7920
mod-1
maven.four.bug.7920
mod-2
..
{code}
So the above {{pom.xml}} is converted into {{pom}} packaging based
{{{}pom.xml{}}}.. it looks like this:
{code:xml}
http://maven.apache.org/POM/4.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
https://maven.apache.org/xsd/maven-4.0.0.xsd;>
4.0.0
maven.four.bug.7920
bom
1.0.0-SNAPSHOT
pom
Maven Bug :: 7920 :: BOM
maven.four.bug.7920
mod-1
maven.four.bug.7920
mod-2
org.junit.jupiter
junit-jupiter
5.10.1
org.assertj
assertj-core
3.24.2
org.assertj
assertj-guava
3.24.2
...
{code}
The list of issues I found from my point of view:
# So the first issue I can identify is that the integrated artifacts:
{code:xml}
maven.four.bug.7920
mod-1
maven.four.bug.7920
mod-2
{code}
do not contain a version number.
# The second issue I can identify is that it contains all bom's resolved which
are from the module parent (see junit-jupiter, assertj, mockito), but
*{*}not{*}* the test scoped dependencies of the {{mod-1}} (added a dependency
to {{junit:junit:4.13.2}} and a non test scoped dependency
{{{}commons-collections:commons-collections:3.2.2{}}}.
>From my point of view the resulting {{pom.xml}} should look like this:
{code:xml}
http://maven.apache.org/POM/4.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
https://maven.apache.org/xsd/maven-4.0.0.xsd;>
4.0.0
maven.four.bug.7920
bom
1.0.0-SNAPSHOT
pom
Maven Bug :: 7920 :: BOM
maven.four.bug.7920
mod-1
1.0.0-SNAPSHOT
maven.four.bug.7920
mod-2
1.0.0-SNAPSHOT
{code}
It should contain things like: URL, name, organization, developers, licenses,
issueManagement, ciManagement(no),distributionManagement(no), repositories (no)
The link to the full repoducer:
[https://github.com/khmarbaise/maven-bugs/tree/master/MNG-7920]
was (Author: khmarbaise):
So after diving a bit deeper into this... it looks like the resulting
{{pom.xml}} should be made the main artifact of the {{bom}} packaged project
because in the end it's the main artifact of the module. For example if we have
a normal pom packaged module it works the same. The {{maven-install-plugin}}
already WARNs exactly about that. Furthermore is my opinion that the
{{maven-install-plugin}} should not needed to be changed because the main
artifact is the resulting {{pom}}.
So the core should assign the interpolated (bom) as the main artifact
(packaging: pom) while the {{pom-build}} is already attached as classifier
based artifacts.
I created a full reproducer to look more in detail on the problems:
Lets start with the {{bom}} packaging module which contains the following
(original pom):
{code:xml}
maven.four.bug.7920
bom-example
bom
bom
Maven Bug :: 7920 :: BOM
maven.four.bug.7920
mod-1
maven.four.bug.7920
mod-2
..
{code}
So the above {{pom.xml}} is converted into {{pom}} packaging based
{{pom.xml}}.. it looks like this:
{code:xml}
http://maven.apache.org/POM/4.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
https://maven.apache.org/xsd/maven-4.0.0.xsd;>
4.0.0
maven.four.bug.7920
bom
1.0.0-SNAPSHOT
pom
[jira] [Updated] (MNG-7941) Meaning of -ntp CLI Option vs. --batch-mode
[
https://issues.apache.org/jira/browse/MNG-7941?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MNG-7941:
-
Description:
If you run a maven build while not downloaded all deps or even not downloaded
any dependency at all you will see something like this on the console:
{code}
Downloading from nexus:
http://localhost:8081/nexus/content/groups/public/org/apache/apache/31/apache-31.pom
Progress (1): 7.9/24 kB
Progress (1): 24 kB
...
Downloading from nexus:
http://localhost:8081/nexus/content/groups/public/org/eclipse/jetty/jetty-security/9.4.46.v20220331/jetty-security-9.4.46.v20220331.jar
Progress (3): 106/733 kB | 73/225 kB | 73/184 kB
Progress (3): 139/733 kB | 73/225 kB | 73/184 kB
Progress (3): 139/733 kB | 106/225 kB | 73/184 kB
Progress (3): 172/733 kB | 106/225 kB | 73/184 kB
Progress (3): 172/733 kB | 106/225 kB | 106/184 kB
Progress (3): 204/733 kB | 106/225 kB | 106/184 kB
Progress (3): 204/733 kB | 139/225 kB | 106/184 kB
Progress (3): 204/733 kB | 139/225 kB | 139/184 kB
Progress (3): 237/733 kB | 139/225 kB | 139/184 kB
Progress (3): 237/733 kB | 172/225 kB | 139/184 kB
Progress (3): 237/733 kB | 172/225 kB | 172/184 kB
Progress (3): 237/733 kB | 172/225 kB | 184 kB
Progress (3): 270/733 kB | 172/225 kB | 184 kB
Progress (3): 270/733 kB | 204/225 kB | 184 kB
Progress (3): 270/733 kB | 225 kB | 184 kB
Progress (4): 270/733 kB | 225 kB | 184 kB | 7.9/147 kB
Progress (4): 303/733 kB | 225 kB | 184 kB | 7.9/147 kB
...
{code}
So far as usual..
What you can do to prevent the long outputs is just use: {{--batch-mode}} which
prevents the output of the progress and the result looks like this:
{code}
[INFO] Downloaded from nexus:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/doxia/doxia-module-twiki/1.11.1/doxia-module-twiki-1.11.1.jar
(73 kB at 1.4 MB/s)
[INFO] Downloading from nexus:
http://localhost:8081/nexus/content/groups/public/org/eclipse/jetty/jetty-security/9.4.46.v20220331/jetty-security-9.4.46.v20220331.jar
[INFO] Downloaded from nexus:
http://localhost:8081/nexus/content/groups/public/org/eclipse/jetty/jetty-io/9.4.46.v20220331/jetty-io-9.4.46.v20220331.jar
(184 kB at 3.4 MB/s)
[INFO] Downloading from nexus:
http://localhost:8081/nexus/content/groups/public/org/eclipse/jetty/jetty-util-ajax/9.4.46.v20220331/jetty-util-ajax-9.4.46.v20220331.jar
...
{code}
So finally you can use {{-no-transfer-progress}} (or {{-ntp}}) and the output
looks like this:
{code}
[INFO]
[INFO] --- site:3.12.1:attach-descriptor (attach-descriptor) @
maven-dependency-plugin ---
[INFO] Skipping because packaging 'maven-plugin' is not pom.
[INFO]
[INFO] --- install:3.1.1:install (default-install) @ maven-dependency-plugin ---
..
{code}
So based on the naming of {{\-\-no-transfer-progress}} which is a bit
misleading because the transfer progress output has already been supressed by
using {{--batch-mode}}.
For Maven 4 we could think about a more cleaner way:
* {{--batch-mode}} will not change anything
* {{--no-transfer-progress}} will prevent the output of {{Progress (3): 237/733
kB | 172/225 kB | 172/184 kB}} (which will really represent the function
related to the name).
* {{--no-download-output}} could suppress the output as of using {{-ntp}} in
Maven 3.X
That would be a bit more consistent
was:
If you run a maven build while not downloaded all deps or even not downloaded
any dependency at all you will see something like this on the console:
{code}
Downloading from nexus:
http://localhost:8081/nexus/content/groups/public/org/apache/apache/31/apache-31.pom
Progress (1): 7.9/24 kB
Progress (1): 24 kB
...
Downloading from nexus:
http://localhost:8081/nexus/content/groups/public/org/eclipse/jetty/jetty-security/9.4.46.v20220331/jetty-security-9.4.46.v20220331.jar
Progress (3): 106/733 kB | 73/225 kB | 73/184 kB
Progress (3): 139/733 kB | 73/225 kB | 73/184 kB
Progress (3): 139/733 kB | 106/225 kB | 73/184 kB
Progress (3): 172/733 kB | 106/225 kB | 73/184 kB
Progress (3): 172/733 kB | 106/225 kB | 106/184 kB
Progress (3): 204/733 kB | 106/225 kB | 106/184 kB
Progress (3): 204/733 kB | 139/225 kB | 106/184 kB
Progress (3): 204/733 kB | 139/225 kB | 139/184 kB
Progress (3): 237/733 kB | 139/225 kB | 139/184 kB
Progress (3): 237/733 kB | 172/225 kB | 139/184 kB
Progress (3): 237/733 kB | 172/225 kB | 172/184 kB
Progress (3): 237/733 kB | 172/225 kB | 184 kB
Progress (3): 270/733 kB | 172/225 kB | 184 kB
Progress (3): 270/733 kB | 204/225 kB | 184 kB
Progress (3): 270/733 kB | 225 kB | 184 kB
Progress (4): 270/733 kB | 225 kB | 184 kB | 7.9/147 kB
Progress (4): 303/733 kB | 225 kB | 184 kB | 7.9/147 kB
...
{code}
So far as usual..
What you can do to prevent the long outputs is just use: {{--batch-mode}} which
prevents the output of the progress and the result looks like this:
{code}
[INFO] Downloaded from nexus:
[jira] [Commented] (MNG-7940) Maven embedder CLI output contains nulls.
[
https://issues.apache.org/jira/browse/MNG-7940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17787489#comment-17787489
]
Karl Heinz Marbaise commented on MNG-7940:
--
Done in
[b08b62f8de059d155dc05cea308dec0a0b2946b6|https://gitbox.apache.org/repos/asf?p=maven.git;a=commitdiff;h=b08b62f8de059d155dc05cea308dec0a0b2946b6]
> Maven embedder CLI output contains nulls.
> -
>
> Key: MNG-7940
> URL: https://issues.apache.org/jira/browse/MNG-7940
> Project: Maven
> Issue Type: Improvement
>Affects Versions: 4.0.0-alpha-8
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 4.0.0, 4.0.0-alpha-9
>
>
> Checking the
> https://maven.apache.org/ref/4.0.0-alpha-8/maven-embedder/cli.html you will
> see a number of entries which contain {{-null}} which is not correct.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MNG-7940) Maven embedder CLI output contains nulls.
[
https://issues.apache.org/jira/browse/MNG-7940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise closed MNG-7940.
Resolution: Done
> Maven embedder CLI output contains nulls.
> -
>
> Key: MNG-7940
> URL: https://issues.apache.org/jira/browse/MNG-7940
> Project: Maven
> Issue Type: Improvement
>Affects Versions: 4.0.0-alpha-8
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 4.0.0-alpha-9, 4.0.0
>
>
> Checking the
> https://maven.apache.org/ref/4.0.0-alpha-8/maven-embedder/cli.html you will
> see a number of entries which contain {{-null}} which is not correct.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MNG-7941) Meaning of -ntp CLI Option vs. --batch-mode
Karl Heinz Marbaise created MNG-7941:
Summary: Meaning of -ntp CLI Option vs. --batch-mode
Key: MNG-7941
URL: https://issues.apache.org/jira/browse/MNG-7941
Project: Maven
Issue Type: Improvement
Affects Versions: 3.9.5, 4.0.0-alpha-8
Reporter: Karl Heinz Marbaise
Fix For: 4.0.0, 3.9.6, 4.0.0-alpha-9
If you run a maven build while not downloaded all deps or even not downloaded
any dependency at all you will see something like this on the console:
{code}
Downloading from nexus:
http://localhost:8081/nexus/content/groups/public/org/apache/apache/31/apache-31.pom
Progress (1): 7.9/24 kB
Progress (1): 24 kB
...
Downloading from nexus:
http://localhost:8081/nexus/content/groups/public/org/eclipse/jetty/jetty-security/9.4.46.v20220331/jetty-security-9.4.46.v20220331.jar
Progress (3): 106/733 kB | 73/225 kB | 73/184 kB
Progress (3): 139/733 kB | 73/225 kB | 73/184 kB
Progress (3): 139/733 kB | 106/225 kB | 73/184 kB
Progress (3): 172/733 kB | 106/225 kB | 73/184 kB
Progress (3): 172/733 kB | 106/225 kB | 106/184 kB
Progress (3): 204/733 kB | 106/225 kB | 106/184 kB
Progress (3): 204/733 kB | 139/225 kB | 106/184 kB
Progress (3): 204/733 kB | 139/225 kB | 139/184 kB
Progress (3): 237/733 kB | 139/225 kB | 139/184 kB
Progress (3): 237/733 kB | 172/225 kB | 139/184 kB
Progress (3): 237/733 kB | 172/225 kB | 172/184 kB
Progress (3): 237/733 kB | 172/225 kB | 184 kB
Progress (3): 270/733 kB | 172/225 kB | 184 kB
Progress (3): 270/733 kB | 204/225 kB | 184 kB
Progress (3): 270/733 kB | 225 kB | 184 kB
Progress (4): 270/733 kB | 225 kB | 184 kB | 7.9/147 kB
Progress (4): 303/733 kB | 225 kB | 184 kB | 7.9/147 kB
...
{code}
So far as usual..
What you can do to prevent the long outputs is just use: {{--batch-mode}} which
prevents the output of the progress and the result looks like this:
{code}
[INFO] Downloaded from nexus:
http://localhost:8081/nexus/content/groups/public/org/apache/maven/doxia/doxia-module-twiki/1.11.1/doxia-module-twiki-1.11.1.jar
(73 kB at 1.4 MB/s)
[INFO] Downloading from nexus:
http://localhost:8081/nexus/content/groups/public/org/eclipse/jetty/jetty-security/9.4.46.v20220331/jetty-security-9.4.46.v20220331.jar
[INFO] Downloaded from nexus:
http://localhost:8081/nexus/content/groups/public/org/eclipse/jetty/jetty-io/9.4.46.v20220331/jetty-io-9.4.46.v20220331.jar
(184 kB at 3.4 MB/s)
[INFO] Downloading from nexus:
http://localhost:8081/nexus/content/groups/public/org/eclipse/jetty/jetty-util-ajax/9.4.46.v20220331/jetty-util-ajax-9.4.46.v20220331.jar
...
{code}
So finally you can use {{-no-transfer-progress}} (or {{-ntp}}) and the output
looks like this:
{code}
[INFO]
[INFO] --- site:3.12.1:attach-descriptor (attach-descriptor) @
maven-dependency-plugin ---
[INFO] Skipping because packaging 'maven-plugin' is not pom.
[INFO]
[INFO] --- install:3.1.1:install (default-install) @ maven-dependency-plugin ---
..
{code}
So based on the naming of {{--no-transfer-progress}} which is a bit misleading
because the transfer progress output has already been supressed by using
{{--batch-mode}}.
For Maven 4 we could think about a more cleaner way:
* {{--batch-mode}} will not change anything
* {{--no-transfer-progress}} will prevent the output of {{Progress (3): 237/733
kB | 172/225 kB | 172/184 kB}} (which will really represent the function
related to the name).
* {{--no-download-output}} could suppress the output as of using {{-ntp}} in
Maven 3.X
That would be a bit more consistent
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MNG-7940) Maven embedder CLI output contains nulls.
Karl Heinz Marbaise created MNG-7940:
Summary: Maven embedder CLI output contains nulls.
Key: MNG-7940
URL: https://issues.apache.org/jira/browse/MNG-7940
Project: Maven
Issue Type: Improvement
Affects Versions: 4.0.0-alpha-8
Reporter: Karl Heinz Marbaise
Assignee: Karl Heinz Marbaise
Fix For: 4.0.0, 4.0.0-alpha-9
Checking the https://maven.apache.org/ref/4.0.0-alpha-8/maven-embedder/cli.html
you will see a number of entries which contain {{-null}} which is not correct.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MNG-7938) Upgrade plexus classworlds to 2.7.0
Karl Heinz Marbaise created MNG-7938: Summary: Upgrade plexus classworlds to 2.7.0 Key: MNG-7938 URL: https://issues.apache.org/jira/browse/MNG-7938 Project: Maven Issue Type: Improvement Affects Versions: 4.0.0-alpha-8 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 4.0.0, 4.0.0-alpha-9 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MNG-7920) Usage of packaging BOM fails in maven-install-plugin
[
https://issues.apache.org/jira/browse/MNG-7920?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MNG-7920:
-
Description:
Using to use the {{bom}} packaging in a module it will fail with:
{code}
[INFO]
--
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-install-plugin:3.1.1:install (default-install)
on project bom: The packaging plugin for this project did not assign a main
file to the project but it has attachments. Change packaging to 'pom'. -> [Help
1]
{code}
The bom module looks like this:
{code:xml}
http://maven.apache.org/POM/4.1.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.1.0
http://maven.apache.org/maven-v4_1_0.xsd;>
4.1.0
maven4
bom-example
bom
bom
...maven4
mod-1
maven4
mod-2
{code}
I would assume that I need to upgrade the maven-install-plugin which is capable
of handling that...but I assumed that this conversion is done by core?
was:
Using to use the `bom` packaging in a module it will fail with:
{code}
[INFO]
--
[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-install-plugin:3.1.1:install (default-install)
on project bom: The packaging plugin for this project did not assign a main
file to the project but it has attachments. Change packaging to 'pom'. -> [Help
1]
{code}
The bom module looks like this:
{code:xml}
http://maven.apache.org/POM/4.1.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.1.0
http://maven.apache.org/maven-v4_1_0.xsd;>
4.1.0
maven4
bom-example
bom
bom
...maven4
mod-1
maven4
mod-2
{code}
I would assume that I need to upgrade the maven-install-plugin which is capable
of handling that...but I assumed that this conversion is done by core?
> Usage of packaging BOM fails in maven-install-plugin
>
>
> Key: MNG-7920
> URL: https://issues.apache.org/jira/browse/MNG-7920
> Project: Maven
> Issue Type: Bug
> Components: Deployment
>Affects Versions: 4.0.0-alpha-8
>Reporter: Karl Heinz Marbaise
>Priority: Critical
> Fix For: 4.0.0, 4.0.0-alpha-9
>
>
> Using to use the {{bom}} packaging in a module it will fail with:
> {code}
> [INFO]
> --
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-install-plugin:3.1.1:install (default-install)
> on project bom: The packaging plugin for this project did not assign a main
> file to the project but it has attachments. Change packaging to 'pom'. ->
> [Help 1]
> {code}
> The bom module looks like this:
> {code:xml}
>xmlns="http://maven.apache.org/POM/4.1.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.1.0
> http://maven.apache.org/maven-v4_1_0.xsd;>
> 4.1.0
>
> maven4
> bom-example
>
> bom
> bom
>
>
>
> ...maven4
> mod-1
>
>
> maven4
> mod-2
>
>
>
>
> {code}
> I would assume that I need to upgrade the maven-install-plugin which is
> capable of handling that...but I assumed that this conversion is done by core?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7920) Usage of packaging BOM fails in maven-install-plugin
[
https://issues.apache.org/jira/browse/MNG-7920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17787394#comment-17787394
]
Karl Heinz Marbaise commented on MNG-7920:
--
So [~crazyhzm] I have tested the given PR and run the same setup with my
reproducer setup. The result is unfortunately not correct either.
One thing is better, it cleans up the WARNING for {{maven-install-plugin}}, but
on the other hand it results in the following {{pom.xml}} file:
{code:xml}
http://maven.apache.org/POM/4.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
https://maven.apache.org/xsd/maven-4.0.0.xsd;>
4.0.0
maven.four.bug.7920
bom-example
${revision}
bom
bom
Maven Bug :: 7920 :: BOM
maven.four.bug.7920
mod-1
maven.four.bug.7920
mod-2
{code}
This contains even the whole parent including not resolved {{$\{revision\}}}.
> Usage of packaging BOM fails in maven-install-plugin
>
>
> Key: MNG-7920
> URL: https://issues.apache.org/jira/browse/MNG-7920
> Project: Maven
> Issue Type: Bug
> Components: Deployment
>Affects Versions: 4.0.0-alpha-8
>Reporter: Karl Heinz Marbaise
>Priority: Critical
> Fix For: 4.0.0, 4.0.0-alpha-9
>
>
> Using to use the `bom` packaging in a module it will fail with:
> {code}
> [INFO]
> --
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-install-plugin:3.1.1:install (default-install)
> on project bom: The packaging plugin for this project did not assign a main
> file to the project but it has attachments. Change packaging to 'pom'. ->
> [Help 1]
> {code}
> The bom module looks like this:
> {code:xml}
>xmlns="http://maven.apache.org/POM/4.1.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.1.0
> http://maven.apache.org/maven-v4_1_0.xsd;>
> 4.1.0
>
> maven4
> bom-example
>
> bom
> bom
>
>
>
> ...maven4
> mod-1
>
>
> maven4
> mod-2
>
>
>
>
> {code}
> I would assume that I need to upgrade the maven-install-plugin which is
> capable of handling that...but I assumed that this conversion is done by core?
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MNG-7920) Usage of packaging BOM fails in maven-install-plugin
[
https://issues.apache.org/jira/browse/MNG-7920?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17787385#comment-17787385
]
Karl Heinz Marbaise commented on MNG-7920:
--
So after diving a bit deeper into this... it looks like the resulting
{{pom.xml}} should be made the main artifact of the {{bom}} packaged project
because in the end it's the main artifact of the module. For example if we have
a normal pom packaged module it works the same. The {{maven-install-plugin}}
already WARNs exactly about that. Furthermore is my opinion that the
{{maven-install-plugin}} should not needed to be changed because the main
artifact is the resulting {{pom}}.
So the core should assign the interpolated (bom) as the main artifact
(packaging: pom) while the {{pom-build}} is already attached as classifier
based artifacts.
I created a full reproducer to look more in detail on the problems:
Lets start with the {{bom}} packaging module which contains the following
(original pom):
{code:xml}
maven.four.bug.7920
bom-example
bom
bom
Maven Bug :: 7920 :: BOM
maven.four.bug.7920
mod-1
maven.four.bug.7920
mod-2
..
{code}
So the above {{pom.xml}} is converted into {{pom}} packaging based
{{pom.xml}}.. it looks like this:
{code:xml}
http://maven.apache.org/POM/4.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
https://maven.apache.org/xsd/maven-4.0.0.xsd;>
4.0.0
maven.four.bug.7920
bom
1.0.0-SNAPSHOT
pom
Maven Bug :: 7920 :: BOM
maven.four.bug.7920
mod-1
maven.four.bug.7920
mod-2
org.junit.jupiter
junit-jupiter
5.10.1
org.assertj
assertj-core
3.24.2
org.assertj
assertj-guava
3.24.2
...
{code}
The list of issues I found from my point of view:
# So the first issue I can identify is that the integrated artifacts:
{code:xml}
maven.four.bug.7920
mod-1
maven.four.bug.7920
mod-2
{code}
do not contain a version number.
# The second issue I can identify is that it contains all bom's resolved which
are from the module parent (see junit-jupiter, assertj, mockito), but **not**
the test scoped dependencies of the {{mod-1}} (added a dependency to
{{junit:junit:4.13.2}} and a non test scoped dependency
{{commons-collections:commons-collections:3.2.2}.
>From my point of view the resulting {{pom.xml}} should look like this:
{code:xml}
http://maven.apache.org/POM/4.0.0;
xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
xsi:schemaLocation="http://maven.apache.org/POM/4.0.0
https://maven.apache.org/xsd/maven-4.0.0.xsd;>
4.0.0
maven.four.bug.7920
bom
1.0.0-SNAPSHOT
pom
Maven Bug :: 7920 :: BOM
maven.four.bug.7920
mod-1
1.0.0-SNAPSHOT
maven.four.bug.7920
mod-2
1.0.0-SNAPSHOT
{code}
It should contain things like: URL, name, organization, developers, licenses,
issueManagement, ciManagement(no),distributionManagement(no), repositories (no)
The link to the full repoducer:
https://github.com/khmarbaise/maven-bugs/tree/master/MNG-7920
> Usage of packaging BOM fails in maven-install-plugin
>
>
> Key: MNG-7920
> URL: https://issues.apache.org/jira/browse/MNG-7920
> Project: Maven
> Issue Type: Bug
> Components: Deployment
>Affects Versions: 4.0.0-alpha-8
>Reporter: Karl Heinz Marbaise
>Priority: Critical
> Fix For: 4.0.0, 4.0.0-alpha-9
>
>
> Using to use the `bom` packaging in a module it will fail with:
> {code}
> [INFO]
> --
> [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-install-plugin:3.1.1:install (default-install)
> on project bom: The packaging plugin for this project did not assign a main
> file to the project but it has attachments. Change packaging to 'pom'. ->
> [Help 1]
> {code}
> The bom module looks like this:
> {code:xml}
>xmlns="http://maven.apache.org/POM/4.1.0;
> xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance;
> xsi:schemaLocation="http://maven.apache.org/POM/4.1.0
> http://maven.apache.org/maven-v4_1_0.xsd;>
> 4.1.0
>
> maven4
> bom-example
>
> bom
> bom
>
>
>
> ...maven4
> mod-1
>
>
> maven4
> mod-2
>
>
>
>
> {code}
> I would assume that I need to upgrade the maven-install-plugin
[jira] [Created] (MJDEPRSCAN-10) Upgrade maven-plugin parent to 41
Karl Heinz Marbaise created MJDEPRSCAN-10: - Summary: Upgrade maven-plugin parent to 41 Key: MJDEPRSCAN-10 URL: https://issues.apache.org/jira/browse/MJDEPRSCAN-10 Project: Maven JDeprScan Plugin Issue Type: Improvement Affects Versions: 3.0.0-alpha-1 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.0.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MPH-211) Upgrade maven-plugin parent to 41
[ https://issues.apache.org/jira/browse/MPH-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MPH-211. --- Resolution: Done > Upgrade maven-plugin parent to 41 > - > > Key: MPH-211 > URL: https://issues.apache.org/jira/browse/MPH-211 > Project: Maven Help Plugin > Issue Type: Improvement >Affects Versions: 3.4.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPH-211) Upgrade maven-plugin parent to 41
[ https://issues.apache.org/jira/browse/MPH-211?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17785935#comment-17785935 ] Karl Heinz Marbaise commented on MPH-211: - Done in [8098d42b2f1582fcb2f5f1dcacc90e7da1997a18|https://gitbox.apache.org/repos/asf?p=maven-help-plugin.git;a=commitdiff;h=8098d42b2f1582fcb2f5f1dcacc90e7da1997a18] > Upgrade maven-plugin parent to 41 > - > > Key: MPH-211 > URL: https://issues.apache.org/jira/browse/MPH-211 > Project: Maven Help Plugin > Issue Type: Improvement >Affects Versions: 3.4.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MPLUGIN-495) WARNINGs based on usage of @Component for session/MavenProject instead of @Parameter
[
https://issues.apache.org/jira/browse/MPLUGIN-495?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17785921#comment-17785921
]
Karl Heinz Marbaise commented on MPLUGIN-495:
-
Thanks for reopening ... clicked on the wrong one.
> WARNINGs based on usage of @Component for session/MavenProject instead of
> @Parameter
>
>
> Key: MPLUGIN-495
> URL: https://issues.apache.org/jira/browse/MPLUGIN-495
> Project: Maven Plugin Tools
> Issue Type: Improvement
>Affects Versions: 3.10.2
>Reporter: Karl Heinz Marbaise
>Assignee: Guillaume Nodet
>Priority: Critical
>
> A change of parameters like this:
> {code:java}
> @Parameter(defaultValue = "${project}", readonly = true, required = true)
> {code}
> into:
> {code:java}
> @Component
> {code}
> This will result in WARNINGs like this:
> {code}
> Warning: Deprecated @Component annotation for 'session' field in
> org.apache.maven.plugins.dependency.GetMojo: replace with @Parameter(
> defaultValue = "${session}", readonly = true )
> {code}
> The shown deprecation message is wrong. It is fine to use that for components
> to be injected.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MJLINK-76) Upgrade maven-plugin parent to 41
Karl Heinz Marbaise created MJLINK-76: - Summary: Upgrade maven-plugin parent to 41 Key: MJLINK-76 URL: https://issues.apache.org/jira/browse/MJLINK-76 Project: Maven JLink Plugin Issue Type: Improvement Affects Versions: 3.1.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.2.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MJDEPS-31) Upgrade maven-plugin parent to 41
[ https://issues.apache.org/jira/browse/MJDEPS-31?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned MJDEPS-31: - Assignee: Karl Heinz Marbaise > Upgrade maven-plugin parent to 41 > - > > Key: MJDEPS-31 > URL: https://issues.apache.org/jira/browse/MJDEPS-31 > Project: Maven JDeps Plugin > Issue Type: Improvement >Affects Versions: 3.1.2 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.1.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MJDEPS-31) Upgrade maven-plugin parent to 41
Karl Heinz Marbaise created MJDEPS-31: - Summary: Upgrade maven-plugin parent to 41 Key: MJDEPS-31 URL: https://issues.apache.org/jira/browse/MJDEPS-31 Project: Maven JDeps Plugin Issue Type: Improvement Affects Versions: 3.1.2 Reporter: Karl Heinz Marbaise Fix For: 3.1.3 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MJAVADOC-779) Upgrade maven-plugin parent to 41
[ https://issues.apache.org/jira/browse/MJAVADOC-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned MJAVADOC-779: Assignee: Karl Heinz Marbaise > Upgrade maven-plugin parent to 41 > - > > Key: MJAVADOC-779 > URL: https://issues.apache.org/jira/browse/MJAVADOC-779 > Project: Maven Javadoc Plugin > Issue Type: Improvement >Affects Versions: 3.6.2 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.6.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MJAVADOC-779) Upgrade maven-plugin parent to 41
[ https://issues.apache.org/jira/browse/MJAVADOC-779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MJAVADOC-779: - Fix Version/s: 3.6.3 (was: 4.0.0) > Upgrade maven-plugin parent to 41 > - > > Key: MJAVADOC-779 > URL: https://issues.apache.org/jira/browse/MJAVADOC-779 > Project: Maven Javadoc Plugin > Issue Type: Improvement >Affects Versions: 3.6.2 >Reporter: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.6.3 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MJAVADOC-779) Upgrade maven-plugin parent to 41
Karl Heinz Marbaise created MJAVADOC-779: Summary: Upgrade maven-plugin parent to 41 Key: MJAVADOC-779 URL: https://issues.apache.org/jira/browse/MJAVADOC-779 Project: Maven Javadoc Plugin Issue Type: Improvement Affects Versions: 3.6.2 Reporter: Karl Heinz Marbaise Fix For: 4.0.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MJAR-299) Upgrade maven-plugin parent to 41
[ https://issues.apache.org/jira/browse/MJAR-299?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned MJAR-299: Assignee: Karl Heinz Marbaise > Upgrade maven-plugin parent to 41 > - > > Key: MJAR-299 > URL: https://issues.apache.org/jira/browse/MJAR-299 > Project: Maven JAR Plugin > Issue Type: Improvement >Affects Versions: 3.3.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.4.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MJAR-299) Upgrade maven-plugin parent to 41
Karl Heinz Marbaise created MJAR-299: Summary: Upgrade maven-plugin parent to 41 Key: MJAR-299 URL: https://issues.apache.org/jira/browse/MJAR-299 Project: Maven JAR Plugin Issue Type: Improvement Affects Versions: 3.3.0 Reporter: Karl Heinz Marbaise Fix For: 3.4.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MINVOKER-350) Upgrade maven-plugin parent to 41
Karl Heinz Marbaise created MINVOKER-350: Summary: Upgrade maven-plugin parent to 41 Key: MINVOKER-350 URL: https://issues.apache.org/jira/browse/MINVOKER-350 Project: Maven Invoker Plugin Issue Type: Improvement Affects Versions: 3.6.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.x -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MPH-211) Upgrade maven-plugin parent to 41
[ https://issues.apache.org/jira/browse/MPH-211?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned MPH-211: --- Assignee: Karl Heinz Marbaise > Upgrade maven-plugin parent to 41 > - > > Key: MPH-211 > URL: https://issues.apache.org/jira/browse/MPH-211 > Project: Maven Help Plugin > Issue Type: Improvement >Affects Versions: 3.4.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MPH-211) Upgrade maven-plugin parent to 41
Karl Heinz Marbaise created MPH-211: --- Summary: Upgrade maven-plugin parent to 41 Key: MPH-211 URL: https://issues.apache.org/jira/browse/MPH-211 Project: Maven Help Plugin Issue Type: Improvement Affects Versions: 3.4.0 Reporter: Karl Heinz Marbaise Fix For: next-release -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MEAR-328) Upgrade maven-plugin parent to 41
Karl Heinz Marbaise created MEAR-328: Summary: Upgrade maven-plugin parent to 41 Key: MEAR-328 URL: https://issues.apache.org/jira/browse/MEAR-328 Project: Maven EAR Plugin Issue Type: Improvement Affects Versions: 3.3.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: next-release -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MARTIFACT-56) Upgrade maven-plugin parent to 41
[ https://issues.apache.org/jira/browse/MARTIFACT-56?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17785665#comment-17785665 ] Karl Heinz Marbaise commented on MARTIFACT-56: -- Done in [94f0ad4cb33524a5dbd4a9904cbfe2124480c105|https://gitbox.apache.org/repos/asf?p=maven-artifact-plugin.git;a=commitdiff;h=94f0ad4cb33524a5dbd4a9904cbfe2124480c105] > Upgrade maven-plugin parent to 41 > - > > Key: MARTIFACT-56 > URL: https://issues.apache.org/jira/browse/MARTIFACT-56 > Project: Maven Artifact Plugin > Issue Type: Improvement >Affects Versions: 3.5.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.5.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MARTIFACT-56) Upgrade maven-plugin parent to 41
[ https://issues.apache.org/jira/browse/MARTIFACT-56?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MARTIFACT-56. Resolution: Done > Upgrade maven-plugin parent to 41 > - > > Key: MARTIFACT-56 > URL: https://issues.apache.org/jira/browse/MARTIFACT-56 > Project: Maven Artifact Plugin > Issue Type: Improvement >Affects Versions: 3.5.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.5.1 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MDEPLOY-313) Upgrade maven-plugin parent to 41
[ https://issues.apache.org/jira/browse/MDEPLOY-313?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise updated MDEPLOY-313: Fix Version/s: next-release (was: 4.0.0) > Upgrade maven-plugin parent to 41 > - > > Key: MDEPLOY-313 > URL: https://issues.apache.org/jira/browse/MDEPLOY-313 > Project: Maven Deploy Plugin > Issue Type: Improvement >Affects Versions: 3.1.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MDEPLOY-313) Upgrade maven-plugin parent to 41
Karl Heinz Marbaise created MDEPLOY-313: --- Summary: Upgrade maven-plugin parent to 41 Key: MDEPLOY-313 URL: https://issues.apache.org/jira/browse/MDEPLOY-313 Project: Maven Deploy Plugin Issue Type: Improvement Affects Versions: 3.1.1 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 4.0.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MARTIFACT-56) Upgrade maven-plugin parent to 41
Karl Heinz Marbaise created MARTIFACT-56: Summary: Upgrade maven-plugin parent to 41 Key: MARTIFACT-56 URL: https://issues.apache.org/jira/browse/MARTIFACT-56 Project: Maven Artifact Plugin Issue Type: Improvement Affects Versions: 3.5.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.5.1 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MCOMPILER-557) Upgrade maven-plugin parent to 41
[ https://issues.apache.org/jira/browse/MCOMPILER-557?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17785659#comment-17785659 ] Karl Heinz Marbaise commented on MCOMPILER-557: --- Done in [a322465885f6443062b3fb99aeab16ac09e419cc|https://github.com/apache/maven-compiler-plugin/commit/a322465885f6443062b3fb99aeab16ac09e419cc] > Upgrade maven-plugin parent to 41 > - > > Key: MCOMPILER-557 > URL: https://issues.apache.org/jira/browse/MCOMPILER-557 > Project: Maven Compiler Plugin > Issue Type: Improvement >Affects Versions: 3.11.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.12.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Resolved] (MCOMPILER-557) Upgrade maven-plugin parent to 41
[ https://issues.apache.org/jira/browse/MCOMPILER-557?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise resolved MCOMPILER-557. --- Resolution: Fixed > Upgrade maven-plugin parent to 41 > - > > Key: MCOMPILER-557 > URL: https://issues.apache.org/jira/browse/MCOMPILER-557 > Project: Maven Compiler Plugin > Issue Type: Improvement >Affects Versions: 3.11.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.12.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MNG-7932) Upgrade maven-parent to v41
[ https://issues.apache.org/jira/browse/MNG-7932?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17785658#comment-17785658 ] Karl Heinz Marbaise commented on MNG-7932: -- Done in [a68443f4e93de27fa72f08c462b2937244ab96d4|https://gitbox.apache.org/repos/asf?p=maven.git;a=commitdiff;h=a68443f4e93de27fa72f08c462b2937244ab96d4] > Upgrade maven-parent to v41 > --- > > Key: MNG-7932 > URL: https://issues.apache.org/jira/browse/MNG-7932 > Project: Maven > Issue Type: Improvement >Affects Versions: 4.0.0-alpha-8 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 4.0.0, 4.0.0-alpha-9 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MNG-7932) Upgrade maven-parent to v41
[ https://issues.apache.org/jira/browse/MNG-7932?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MNG-7932. Resolution: Done > Upgrade maven-parent to v41 > --- > > Key: MNG-7932 > URL: https://issues.apache.org/jira/browse/MNG-7932 > Project: Maven > Issue Type: Improvement >Affects Versions: 4.0.0-alpha-8 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 4.0.0-alpha-9, 4.0.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MACR-57) Upgrade maven-plugin parent to 41
[ https://issues.apache.org/jira/browse/MACR-57?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17785656#comment-17785656 ] Karl Heinz Marbaise commented on MACR-57: - Done in [5ee96593f58ac1a97aab4c69d4c398186cb76a4a|https://gitbox.apache.org/repos/asf?p=maven-acr-plugin.git;a=commitdiff;h=5ee96593f58ac1a97aab4c69d4c398186cb76a4a] > Upgrade maven-plugin parent to 41 > - > > Key: MACR-57 > URL: https://issues.apache.org/jira/browse/MACR-57 > Project: Maven ACR Plugin > Issue Type: Improvement >Affects Versions: 3.1.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.2.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MACR-57) Upgrade maven-plugin parent to 41
[ https://issues.apache.org/jira/browse/MACR-57?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MACR-57. --- Resolution: Done > Upgrade maven-plugin parent to 41 > - > > Key: MACR-57 > URL: https://issues.apache.org/jira/browse/MACR-57 > Project: Maven ACR Plugin > Issue Type: Improvement >Affects Versions: 3.1.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.2.0 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MCOMPILER-557) Upgrade maven-plugin parent to 41
Karl Heinz Marbaise created MCOMPILER-557: - Summary: Upgrade maven-plugin parent to 41 Key: MCOMPILER-557 URL: https://issues.apache.org/jira/browse/MCOMPILER-557 Project: Maven Compiler Plugin Issue Type: Improvement Affects Versions: 3.11.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.12.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MACR-57) Upgrade maven-plugin parent to 41
Karl Heinz Marbaise created MACR-57: --- Summary: Upgrade maven-plugin parent to 41 Key: MACR-57 URL: https://issues.apache.org/jira/browse/MACR-57 Project: Maven ACR Plugin Issue Type: Improvement Affects Versions: 3.1.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.2.0 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MASSEMBLY-1007) Upgrade maven-plugin parent to 41
[ https://issues.apache.org/jira/browse/MASSEMBLY-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MASSEMBLY-1007. -- Resolution: Done > Upgrade maven-plugin parent to 41 > - > > Key: MASSEMBLY-1007 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-1007 > Project: Maven Assembly Plugin > Issue Type: Improvement >Affects Versions: 3.6.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MASSEMBLY-1007) Upgrade maven-plugin parent to 41
[ https://issues.apache.org/jira/browse/MASSEMBLY-1007?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17785648#comment-17785648 ] Karl Heinz Marbaise commented on MASSEMBLY-1007: Done in [a700d0e16aefbe866793c8eca5b0693ffcf643a0|https://gitbox.apache.org/repos/asf?p=maven-assembly-plugin.git;a=commitdiff;h=a700d0e16aefbe866793c8eca5b0693ffcf643a0] > Upgrade maven-plugin parent to 41 > - > > Key: MASSEMBLY-1007 > URL: https://issues.apache.org/jira/browse/MASSEMBLY-1007 > Project: Maven Assembly Plugin > Issue Type: Improvement >Affects Versions: 3.6.0 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MNG-7932) Upgrade maven-parent to v41
Karl Heinz Marbaise created MNG-7932: Summary: Upgrade maven-parent to v41 Key: MNG-7932 URL: https://issues.apache.org/jira/browse/MNG-7932 Project: Maven Issue Type: Improvement Affects Versions: 4.0.0-alpha-8 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 4.0.0, 4.0.0-alpha-9 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MASSEMBLY-1007) Upgrade maven-plugin parent to 41
Karl Heinz Marbaise created MASSEMBLY-1007: -- Summary: Upgrade maven-plugin parent to 41 Key: MASSEMBLY-1007 URL: https://issues.apache.org/jira/browse/MASSEMBLY-1007 Project: Maven Assembly Plugin Issue Type: Improvement Affects Versions: 3.6.0 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: next-release -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MDEP-898) Upgrade to JDK11+ build requirement
[
https://issues.apache.org/jira/browse/MDEP-898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MDEP-898:
-
Description:
* Upgrade build requirement to JDK11+ so we can use
{{8}} and get rid of WARNINGs
like {{Warning: bootstrap class path not set in conjunction with -source 8}}
* The reason for the WARNING is that we don't correctly set the bootstrap
classpath which can be easily handled by using {{--release}} option by JDK9+
and the real point is that we don't use animalsniffer anymore. That was our
safety net which is not there anymore.
was:* Upgrade build requirement to JDK11+ so we can use
{{8}} and get rid of WARNINGs
like {{Warning: bootstrap class path not set in conjunction with -source 8}}
> Upgrade to JDK11+ build requirement
> ---
>
> Key: MDEP-898
> URL: https://issues.apache.org/jira/browse/MDEP-898
> Project: Maven Dependency Plugin
> Issue Type: Improvement
>Affects Versions: 3.6.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.6.2
>
>
> * Upgrade build requirement to JDK11+ so we can use
> {{8}} and get rid of
> WARNINGs like {{Warning: bootstrap class path not set in conjunction with
> -source 8}}
> * The reason for the WARNING is that we don't correctly set the bootstrap
> classpath which can be easily handled by using {{--release}} option by JDK9+
> and the real point is that we don't use animalsniffer anymore. That was our
> safety net which is not there anymore.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Commented] (MDEP-899) Upgrade maven-plugin parent to 41
[ https://issues.apache.org/jira/browse/MDEP-899?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17785632#comment-17785632 ] Karl Heinz Marbaise commented on MDEP-899: -- Done in [b773e4cf1c6f39e0afc316c77f5871b8f3eed245|https://gitbox.apache.org/repos/asf?p=maven-dependency-plugin.git;a=commitdiff;h=b773e4cf1c6f39e0afc316c77f5871b8f3eed245] > Upgrade maven-plugin parent to 41 > - > > Key: MDEP-899 > URL: https://issues.apache.org/jira/browse/MDEP-899 > Project: Maven Dependency Plugin > Issue Type: Improvement >Affects Versions: 3.6.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.6.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MDEP-899) Upgrade maven-plugin parent to 41
[ https://issues.apache.org/jira/browse/MDEP-899?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MDEP-899. Resolution: Done > Upgrade maven-plugin parent to 41 > - > > Key: MDEP-899 > URL: https://issues.apache.org/jira/browse/MDEP-899 > Project: Maven Dependency Plugin > Issue Type: Improvement >Affects Versions: 3.6.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: 3.6.2 > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MCLEAN-115) Upgrade maven-plugin parent to 41
[ https://issues.apache.org/jira/browse/MCLEAN-115?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17785623#comment-17785623 ] Karl Heinz Marbaise commented on MCLEAN-115: Done in [de1c07b21f54f25f09a7dcbc142d78e031c9c995|https://gitbox.apache.org/repos/asf?p=maven-clean-plugin.git;a=commitdiff;h=de1c07b21f54f25f09a7dcbc142d78e031c9c995] > Upgrade maven-plugin parent to 41 > - > > Key: MCLEAN-115 > URL: https://issues.apache.org/jira/browse/MCLEAN-115 > Project: Maven Clean Plugin > Issue Type: Improvement >Affects Versions: 3.3.2 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Closed] (MCLEAN-115) Upgrade maven-plugin parent to 41
[ https://issues.apache.org/jira/browse/MCLEAN-115?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MCLEAN-115. -- Resolution: Done > Upgrade maven-plugin parent to 41 > - > > Key: MCLEAN-115 > URL: https://issues.apache.org/jira/browse/MCLEAN-115 > Project: Maven Clean Plugin > Issue Type: Improvement >Affects Versions: 3.3.2 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Minor > Fix For: next-release > > -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Created] (MCLEAN-115) Upgrade maven-plugin parent to 41
Karl Heinz Marbaise created MCLEAN-115: -- Summary: Upgrade maven-plugin parent to 41 Key: MCLEAN-115 URL: https://issues.apache.org/jira/browse/MCLEAN-115 Project: Maven Clean Plugin Issue Type: Improvement Affects Versions: 3.3.2 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: next-release -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MDEP-898) Upgrade to JDK11+ build requirement
[
https://issues.apache.org/jira/browse/MDEP-898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MDEP-898:
-
Description: * Upgrade build requirement to JDK11+ so we can use
{{8}} and get rid of WARNINGs
like {{Warning: bootstrap class path not set in conjunction with -source 8}}
(was: * Upgrade build requirement to JDK11+ so we can use
{{8}} and get rid of WARNINGs
like {{Warning: bootstrap class path not set in conjunction with -source 8}}
** This makes it also possible to build with JDK21)
> Upgrade to JDK11+ build requirement
> ---
>
> Key: MDEP-898
> URL: https://issues.apache.org/jira/browse/MDEP-898
> Project: Maven Dependency Plugin
> Issue Type: Improvement
>Affects Versions: 3.6.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.6.2
>
>
> * Upgrade build requirement to JDK11+ so we can use
> {{8}} and get rid of
> WARNINGs like {{Warning: bootstrap class path not set in conjunction with
> -source 8}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Updated] (MDEP-898) Upgrade to JDK11+ build requirement
[
https://issues.apache.org/jira/browse/MDEP-898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MDEP-898:
-
Description:
* Upgrade build requirement to JDK11+ so we can use
{{8}} and get rid of WARNINGs
like {{Warning: bootstrap class path not set in conjunction with -source 8}}
** This makes it also possible to build with JDK21
was:
* Upgrade build requirement to JDK11+ so we can use
{{8}} and get rid of WARNINGs
like {{Warning: bootstrap class path not set in conjunction with -source 8}}
* It's required to upgrade to maven-plugin parent version 41
** This makes it also possible to build with JDK21
> Upgrade to JDK11+ build requirement
> ---
>
> Key: MDEP-898
> URL: https://issues.apache.org/jira/browse/MDEP-898
> Project: Maven Dependency Plugin
> Issue Type: Improvement
>Affects Versions: 3.6.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.6.2
>
>
> * Upgrade build requirement to JDK11+ so we can use
> {{8}} and get rid of
> WARNINGs like {{Warning: bootstrap class path not set in conjunction with
> -source 8}}
> ** This makes it also possible to build with JDK21
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MDEP-899) Upgrade maven-plugin parent to 41
Karl Heinz Marbaise created MDEP-899: Summary: Upgrade maven-plugin parent to 41 Key: MDEP-899 URL: https://issues.apache.org/jira/browse/MDEP-899 Project: Maven Dependency Plugin Issue Type: Improvement Affects Versions: 3.6.1 Reporter: Karl Heinz Marbaise Assignee: Karl Heinz Marbaise Fix For: 3.6.2 -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Updated] (MDEP-898) Upgrade to JDK11+ build requirement
[
https://issues.apache.org/jira/browse/MDEP-898?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Karl Heinz Marbaise updated MDEP-898:
-
Description:
* Upgrade build requirement to JDK11+ so we can use
{{8}} and get rid of WARNINGs
like {{Warning: bootstrap class path not set in conjunction with -source 8}}
* It's required to upgrade to maven-plugin parent version 41
** This makes it also possible to build with JDK21
was:* Upgrade build requirement to JDK11+ so we can use
{{8}} and get rid of WARNINGs
like {{Warning: bootstrap class path not set in conjunction with -source 8}}
> Upgrade to JDK11+ build requirement
> ---
>
> Key: MDEP-898
> URL: https://issues.apache.org/jira/browse/MDEP-898
> Project: Maven Dependency Plugin
> Issue Type: Improvement
>Affects Versions: 3.6.1
>Reporter: Karl Heinz Marbaise
>Assignee: Karl Heinz Marbaise
>Priority: Minor
> Fix For: 3.6.2
>
>
> * Upgrade build requirement to JDK11+ so we can use
> {{8}} and get rid of
> WARNINGs like {{Warning: bootstrap class path not set in conjunction with
> -source 8}}
> * It's required to upgrade to maven-plugin parent version 41
> ** This makes it also possible to build with JDK21
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Created] (MDEP-898) Upgrade to JDK11+ build requirement
Karl Heinz Marbaise created MDEP-898:
Summary: Upgrade to JDK11+ build requirement
Key: MDEP-898
URL: https://issues.apache.org/jira/browse/MDEP-898
Project: Maven Dependency Plugin
Issue Type: Improvement
Affects Versions: 3.6.1
Reporter: Karl Heinz Marbaise
Assignee: Karl Heinz Marbaise
Fix For: 3.6.2
* Upgrade build requirement to JDK11+ so we can use
{{8}} and get rid of WARNINGs
like {{Warning: bootstrap class path not set in conjunction with -source 8}}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
[jira] [Closed] (MDEP-897) Remove old style JavaDoc Plexus docs
[ https://issues.apache.org/jira/browse/MDEP-897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise closed MDEP-897. Resolution: Done > Remove old style JavaDoc Plexus docs > > > Key: MDEP-897 > URL: https://issues.apache.org/jira/browse/MDEP-897 > Project: Maven Dependency Plugin > Issue Type: Improvement >Affects Versions: 3.6.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Major > Fix For: 3.6.2 > > > There are some of the plexus javadoc things in the code. We should remove > that. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Commented] (MDEP-897) Remove old style JavaDoc Plexus docs
[ https://issues.apache.org/jira/browse/MDEP-897?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=17785599#comment-17785599 ] Karl Heinz Marbaise commented on MDEP-897: -- Done in [3ee528d1f812b1179b2c52faa7651afa149e6ee0|https://gitbox.apache.org/repos/asf?p=maven-dependency-plugin.git;a=commitdiff;h=3ee528d1f812b1179b2c52faa7651afa149e6ee0] > Remove old style JavaDoc Plexus docs > > > Key: MDEP-897 > URL: https://issues.apache.org/jira/browse/MDEP-897 > Project: Maven Dependency Plugin > Issue Type: Improvement >Affects Versions: 3.6.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Major > Fix For: 3.6.2 > > > There are some of the plexus javadoc things in the code. We should remove > that. -- This message was sent by Atlassian Jira (v8.20.10#820010)
[jira] [Assigned] (MDEP-897) Remove old style JavaDoc Plexus docs
[ https://issues.apache.org/jira/browse/MDEP-897?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Karl Heinz Marbaise reassigned MDEP-897: Assignee: Karl Heinz Marbaise > Remove old style JavaDoc Plexus docs > > > Key: MDEP-897 > URL: https://issues.apache.org/jira/browse/MDEP-897 > Project: Maven Dependency Plugin > Issue Type: Improvement >Affects Versions: 3.6.1 >Reporter: Karl Heinz Marbaise >Assignee: Karl Heinz Marbaise >Priority: Major > Fix For: 3.6.2 > > > There are some of the plexus javadoc things in the code. We should remove > that. -- This message was sent by Atlassian Jira (v8.20.10#820010)
