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
It is impossible to actually use your own version numbers because they will break resolution of dependencies within the parent, many of which are missing version numbers of any kind. This makes version management of the actual project completely broken, its not possible to have "different" published versions of the same work-item because they wont build.
The text was updated successfully, but these errors were encountered:
mP1
changed the title
parent pom version handling is broken.
org.jbpm.contrib:workitems as a parent pom results in broken version handling
Jul 8, 2020
When creating a work item handler using the parent results in broken versioning.
It is impossible to actually use your own version numbers because they will break resolution of dependencies within the parent, many of which are missing version numbers of any kind. This makes version management of the actual project completely broken, its not possible to have "different" published versions of the same work-item because they wont build.
The text was updated successfully, but these errors were encountered: