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 would like each plugin artifact to include its 'plugin' folder when published to the maven repository.
I would then like to use maven to unpack the plugin folder as part of web/pom.xml process-resources step.
Ideally this should allow developers to build metadata101 schema plugins independently, and add profiles to web/pom.xml for use.
Describe alternatives you've considered
I considered asking each plugin to publish a second "zip" artifact (so both a jar and zip) would be published. While possible it is not really a maven best practice (which thrives at having one artifact for each pom.xml).
I considered having the java bean extract its own plugin folder when it is first run If the folder is not already unpacked). This has been shown to work for thesauri, but would make testing a bit harder. I also note that this is this approach may be added as a capability in the future if there is interest.
Transition from use of
maven-resources-plugin:copy-resources
(directory based) tomaven-dependency-plugin:unpack
(artifact based).See proposal Host Geonetwork artifacts on repo.osgeo.org for background information.
Describe the solution you'd like
I would like each plugin artifact to include its 'plugin' folder when published to the maven repository.
I would then like to use maven to unpack the plugin folder as part of web/pom.xml process-resources step.
Ideally this should allow developers to build metadata101 schema plugins independently, and add profiles to web/pom.xml for use.
Describe alternatives you've considered
I considered asking each plugin to publish a second "zip" artifact (so both a jar and zip) would be published. While possible it is not really a maven best practice (which thrives at having one artifact for each pom.xml).
I considered having the java bean extract its own plugin folder when it is first run If the folder is not already unpacked). This has been shown to work for thesauri, but would make testing a bit harder. I also note that this is this approach may be added as a capability in the future if there is interest.
Additional context
This is an orthogonal but complementary change to changing maven repositories to manage artifacts.
The text was updated successfully, but these errors were encountered: