[
https://issues.jboss.org/browse/JBIDE-20100?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-20100:
----------------------------------------
{quote}a) I assume the dialog does not show up if there is just one connector available
and it is GA'ed (non-early access), right ?{quote}
yes
{quote}b) it should automatically select an option - I suggest the supported version and
after that what user chose last.
c) earlyaccess should not be the first item in the list.{quote}
right for both, I'll integrate that in the PR.
{quote}d) how do I disable earlyaccess so it will remove the EA updatesite from the list
of updatesites it will look at ?{quote}
The link "Manage Early-Access" shows the installation page for which I submitted
2 screenshots here. On this page, user can see the Early-Access content they install and
have the opportunity to disable it (remove features and repositories).
{quote}Once you have installed something from early access the earlyaccess updatesite is
added to your jbds install and thus the choice you have here really does not guarantee you
that the GA bits will be installed over what is in the earlyaccess. IMO, once a user the
first time have said yes to earlyaccess and thus enabled earlyaccess he don't really
have a choice anymore until he disables it.{quote}
And vice-versa, the fact that you have some Early-Access repositories enabled doesn't
guarantee that when installing a connector, you get the Early-Access version of its
features/plugins.
With our current implementation of Central and the connectors we have, the same feature
isn't available in 2 different versions, what makes the difference is which features
are installed by the GA version vs the EA one. In such case we have the guarantee that
installing a GA connector doesn't install the EA additions.
Note that you comment is as true/false with the current implementation, so it's not a
consequence of this UI change.
{quote}About the making JBDS users aware of using older JBDS - that was the main issue in
this jira{quote}
I've read the first few lines of this Jira over and over again, and the main issue if
that Fuse doesn't appear unless user think by themselves of enabling EA. The
description doesn't even mention anything about older JBDS. It's more your mind
which is focused on that part than the initial user request.
{quote}But I'm able to perform smoke tests (installation and key functionalities) on
Mars TP, if it is needed.{quote}
To me, this means that we can put current Fuse IDE as an "Early Access"
connector in JBDS 9. When developing Early-Access, it was exactly the purpose.
how to make users aware of fuse and other tooling only being
available from earlyaccess?
-----------------------------------------------------------------------------------------
Key: JBIDE-20100
URL:
https://issues.jboss.org/browse/JBIDE-20100
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central
Reporter: Max Rydahl Andersen
Assignee: Mickael Istria
Fix For: 4.3.0.CR1
Attachments: JBIDE-20100-2.png
[~jtyrrell] find it confusing when he cannot see Fuse and other earlyaccess features
immediately on the install page.
Some comments:
"I install JBDS 8.1 and click on the JBoss Integration and SOA Development, but
where is the Fuse tooling in that list."
"<without earlyaccess> why doesn’t my screen shot tell me to use an older
version of JBDS or something."
Suggestion:
"when I picked the Integration Stack a greyed out Fuse IDE thingy in the list of
choices, and something like (Select early Access) to enable this feature."
I'm fine exploring options to show early access features more prominently but would
prefer we would not need to treat Fuse "special" so maybe we should have a
"Early Access" section at the bottom instead of filtered in between everything
else ?
and for any connectors that has additional/different features just add a "Extra
features available in Early access " comment ?
But what to do when Fuse or others dont even have an earlyaccess out yet ? (like is
currently the state for devstudio 9)
[~crobson], [~aileenc] and [~lhein] got any suggestions ?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)