[
https://issues.jboss.org/browse/JBIDE-19948?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-19948:
-------------------------------------
However I do not want any version=2 or higher to be used, because it
requires changes in your system and the reason of the JDF rest service was to make sure
you do not need to implement anything if the sales wants to add/remove some fields.
Yeah, we're aware of your proposal, but it just doesn't seem viable after some
discussion. I think a well defined and versioned protocol is better, especially since
we're considering changing things like return codes or adding fields or removing
fields. If it was just adding or removing fields, it's possible to do something
dynamic (but not in the JBDS 9 timeframe).
But when we take into account the full scope of things that are likely to change in the
future, status codes, urls, request / response text, fields, etc, a versioned protocol
is much more reasonable.
We can't predict what new or other business requirements will be added a year from
now...
Reimplement Eclipse Download plugin to allow dynamic work flow
--------------------------------------------------------------
Key: JBIDE-19948
URL:
https://issues.jboss.org/browse/JBIDE-19948
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Components: runtime-detection, server
Affects Versions: 4.3.0.Alpha2
Reporter: David Hladky
Assignee: Rob Stryker
Fix For: 4.3.0.CR1
We need to reimplement the plugin to accept new terms and conditions models as well as
follow the workflow changes in case of changes to the current ones.
Under this issue I will create the tasks we need to achieve this goal.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)