Error: Failed to execute goal org.apache.maven.plugins:maven-dependency-plugin:2.8:copy (copy-documentation) on project ide-cli: Unable to find artifact. Could not find artifact com.devonfw.tools.IDEasy:ide-doc:pdf:2024.06.002-alpha-SNAPSHOT in ossrh (https://s01.oss.sonatype.org/content/repositories/snapshots/)
we now only build the cli for native-image without other modules (since gui failed there and nothing else is/should be required for native-image)
therefore IDEasy documentation is not build before
however, maven build for CLI seems to require documentation artifact to be build before.
Suggestion:
We may move the maven logic to include the documentation into the CLI package into a profile that only gets triggered by deployment or that is active by default but can be disabled in nightly build maven call for native image.
Note:
When working on the workflow we should also align it with the Release workflow:
Release workflow is simply doing
cd cli
mvn «args»
while currently NightlyBuild is doing
mvn «args» -pl cli
More or less both approaches work, but we should better align our workflows and IMHO the cd cli approach is simpler to understand.
NightlyBuild workflow got broken: https://github.com/devonfw/IDEasy/actions/runs/9607252940/job/26498103697
Related maven config is here: https://github.com/devonfw/IDEasy/blob/ee596dadce0cf902cdce23abe346c1c2ac5d3015/cli/pom.xml#L227-L250
Problems:
Suggestion: We may move the maven logic to include the documentation into the CLI package into a profile that only gets triggered by deployment or that is active by default but can be disabled in nightly build maven call for native image.
Note: When working on the workflow we should also align it with the Release workflow: Release workflow is simply doing
while currently NightlyBuild is doing
More or less both approaches work, but we should better align our workflows and IMHO the
cd cli
approach is simpler to understand.