[
https://issues.apache.org/jira/browse/MNG-8486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17910833#comment-17910833
]
Nils Breunese commented on MNG-8486:
------------------------------------
I've also updated the ticket title and description to the best of my
understanding. Feel free to change it further if it's still not quite correct
of course.
> Maven System Properties does not contain Maven User Properties anymore
> ----------------------------------------------------------------------
>
> Key: MNG-8486
> URL: https://issues.apache.org/jira/browse/MNG-8486
> Project: Maven
> Issue Type: Bug
> Affects Versions: 4.0.0-rc-2
> Reporter: Nils Breunese
> Priority: Major
> Fix For: 4.0.0-rc-3
>
>
> I’m using {{jib-maven-plugin}} with some properties provided on the command
> line to build a container image. According to
> [https://github.com/GoogleContainerTools/jib/tree/master/jib-maven-plugin#system-properties]
> this can be done as follows:
> {code:java}
> mvn compile jib:build -Djib.to.image=myregistry/myimage:latest
> {code}
> I’ve been successfully using the syntax above with Maven 3.9.9, but when I
> try this with Maven 4.0.0-rc-2 it seems that the {{jib.to.image}} property is
> not picked up by {{{}jib-maven-plugin{}}}.
> When I do this, it does work:
> {code:java}
> MAVEN_OPTS="-Djib.to.image=myregistry/myimage:latest” compile jib:build
> {code}
> I noticed that the Jib Maven Plugin documentation says that {{jib.to.image}}
> is a _system_ property, while technically {{-D}} on the Maven command line is
> for _user_ properties.
> I've initially [reported this on the Maven users
> mailinglist|https://lists.apache.org/thread/56fsshgwpb358dtw314khlpdylyffl4y]
> and then created this ticket.
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
