You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've brought this up on the Maven dev list and the suggestion there is
Most of the module-path listed there is not intended to be used as module
(maven plugin stack is a good example of that) so looks like moditech
should support classpath option too as the JVM and not assume everything is
a module from my window.
Is this supported by the Moditect plugin?
TY!
The text was updated successfully, but these errors were encountered:
This looks like a split package problem to me, in which case the only way to solve this is to move the org.apache.maven.model.merge package to a single module.
First, identify which packages are split across different modules/JARs. There are a few ways to find that out, I can recommend https://github.com/kordamp/jarviz
Next, if possible, move all affected classes to a single module/JAR. This would require consumers adjusting their dependencies configuration. Failing that, moving classes to other packages which breaks backwards compatibility and thus be considered as last resort unless BC changes were already considered in the next major release.
Hi All,
Over at Apache Commons, we use custom Maven plugins and specifically our Apache Commons Build Plugin.
We define our use of the Moditect Maven plugin in our parent POM: The Apache Commons Parent POM.
This works for the normal Java JAR component I've tried so far but it does not for the Commons Build Maven plugin where we get this error:
Details:
I've brought this up on the Maven dev list and the suggestion there is
Is this supported by the Moditect plugin?
TY!
The text was updated successfully, but these errors were encountered: