Add prefix/suffix to 'jvm-driver' artefact name #6
Replies: 1 comment
-
What you say is right. This problem was caused by the fact that initially the jvm driver was a @burningwave project that after some releases it was moved to @toolfactory. The project therefore underwent strong structural changes up to assuming a completely extensible architecture and at this point a project was also created on @burningwave which extended this architecture with a more performing native engine by taking up the original artifactId. The project name (org.burningwave.jvm-driver) is correct, the problem is that unfortunately maven does not allow setting a name for the generated artifact other than the artifactId tag and if such a change were made it would cause a domain misalignment. However, I'm leaving this issue open in the hope that one day Maven will allow setting the generated artifact name independently of the artifactId tag |
Beta Was this translation helpful? Give feedback.
-
This 'jvm-driver' adapter requires actual 'jvm-driver':
They both have same name but different purpose. Would be useful if adapter was marked somehow, e.g. 'jvm-driver-wrapper' or 'bw-jvm-driver' or something like.
Beta Was this translation helpful? Give feedback.
All reactions