[
https://issues.apache.org/jira/browse/OAK-10032?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17648228#comment-17648228
]
Konrad Windszus edited comment on OAK-10032 at 12/15/22 8:31 PM:
-----------------------------------------------------------------
The problem is the order of execution: Without profile {{apache-release}} it is
first {{maven-assembly-plugin}} and then {{maven-antrun-plugin}} (for goals
bound to the same phase), with the profile it is the other way around.
Unfortunately both bind with their executions in
#
https://github.com/apache/jackrabbit-oak/blob/56a0fa0828e42b59089d014a20dff3b378d8edc9/oak-run/pom.xml#L102
and
#
https://github.com/apache/jackrabbit-oak/blob/56a0fa0828e42b59089d014a20dff3b378d8edc9/oak-run/pom.xml#L120
to the same phase {{package}}, therefore the order is determined by the order
in which the plugins are declared in the plugins section (theoretically). This
is complicated though as profile activation and pom inheritance is taken into
account, for details refer to https://issues.apache.org/jira/browse/MNG-5987
and TBH I don't know which change exactly from
https://github.com/apache/jackrabbit-oak/commit/fcf75771d16f1c89e7c62441ef67f0ad3f37006c#diff-ef85e9003cb1d311055f2c063ab67a54115b8e0e2c1f31638d80e34c075a73bb
can have such an effect (yet)
was (Author: kwin):
The problem is the order of execution: Without profile {{apache-release}} it is
first {{maven-assembly-plugin}} and then {{maven-antrun-plugin}} (for goals
bound to the same phase_, with the profile it is the other way around.
Unfortunately both bind with their executions in
#
https://github.com/apache/jackrabbit-oak/blob/56a0fa0828e42b59089d014a20dff3b378d8edc9/oak-run/pom.xml#L102
and
#
https://github.com/apache/jackrabbit-oak/blob/56a0fa0828e42b59089d014a20dff3b378d8edc9/oak-run/pom.xml#L120
to the same phase {{package}}, therefore the order is determined by the order
in which the plugins are declared in the plugins section (theoretically). This
is complicated though as profile and pom inheritance is taken into account, for
details refer to https://issues.apache.org/jira/browse/MNG-5987 and TBH I don't
know which change exactly from can have such an effect (yet)
> release:perform fails in oak-run
> --------------------------------
>
> Key: OAK-10032
> URL: https://issues.apache.org/jira/browse/OAK-10032
> Project: Jackrabbit Oak
> Issue Type: Bug
> Components: run
> Reporter: Julian Reschke
> Assignee: Nitin Gupta
> Priority: Critical
> Fix For: 1.46.0
>
>
> With diagnostics:
> {noformat}
> [INFO] [ERROR] Failed to execute goal
> org.apache.maven.plugins:maven-antrun-plugin:3.1.0:run (default) on project
> oak-run: An Ant BuildException has occured: Warning: Could not find file
> /Users/N/jackrabbit_oak_git/jackrabbit-oak/target/checkout/oak-run/target/oak-run-1.46.0-oak.jar
> to copy.
> [INFO] [ERROR] around Ant part ...<copy
> file="/Users/N/jackrabbit_oak_git/jackrabbit-oak/target/checkout/oak-run/target/oak-run-1.46.0-oak.jar"
>
> tofile="/Users/N/jackrabbit_oak_git/jackrabbit-oak/target/checkout/oak-run/target/oak-run-1.46.0.jar"
> />... @ 4:231 in
> /Users/N/jackrabbit_oak_git/jackrabbit-oak/target/checkout/oak-run/target/antrun/build-main.xml
> {noformat}
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
