[
https://issues.apache.org/jira/browse/GUACAMOLE-1752?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=17704992#comment-17704992
]
Mike Jumper commented on GUACAMOLE-1752:
----------------------------------------
So, bumping the versions of guacamole-server and guacamole-client is clear
enough, as the source of both has been modified and therefore both get a bump,
but I'm not sure about the submodules of guacamole-client.
Things like guacamole-common and guacamole-ext have not been modified, but
their {{pom.xml}} has to point to the parent, which currently is 1.5.0. I can
think of three options, none of which is clearly best:
# *Bump only the main parent {{pom.xml}}:* Simple and representative, but child
projects no longer inherit from the project that contains them.
# *Bump the main parent {{pom.xml}} and references to it, but not child
{{pom.xml}} versions:* Child projects correctly inherit from the parent, but
there is no longer consistency in what "1.5.0" represents for those child
projects.
# *Bump all project {{pom.xml}} versions:* Everything is consistent, but
several projects get a version bump where their only modification since last
release is that version bump.
I suppose I'd lean toward bumping everything as being the most consistent and
least confusing for users consuming the release...
Thoughts?
> Bump versions to 1.5.1
> ----------------------
>
> Key: GUACAMOLE-1752
> URL: https://issues.apache.org/jira/browse/GUACAMOLE-1752
> Project: Guacamole
> Issue Type: Task
> Reporter: Nick Couchman
> Assignee: Mike Jumper
> Priority: Blocker
> Fix For: 1.5.1
>
>
--
This message was sent by Atlassian Jira
(v8.20.10#820010)
