[
https://issues.jboss.org/browse/JBIDE-20100?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-20100:
------------------------------------
To see the IS content, you need to add the IS content to JBT/JBDS via a -D flag, since the
content is *not yet released*.
Thus, you can launch Eclipse w/ JBT installed into it against the latest CI snapshot...
{code}./eclipse -vmargs \
-Djboss.discovery.directory.url=http://download.jboss.org/jbosstools/mars/snapshots/builds/integration-stack/discovery/4.3.0.Alpha2/jbosstools-integration-stack-directory.xml
\
-Djboss.discovery.site.integration-stack.url=http://download.jboss.org/jbosstools/mars/snapshots/builds/integration-stack/discovery/4.3.0.Alpha2/
{code}
or launch JBDS
{code}./jbodevstudio -vmargs \
-Djboss.discovery.directory.url=https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/9.0.0.Alpha2/devstudio-integration-stack-directory.xml
\
-Djboss.discovery.site.integration-stack.url=https://devstudio.redhat.com/9.0/staging/updates/integration-stack/discovery/9.0.0.Alpha2/
{code}
However, not all JBT/JBDS content will be available because those sites don't contain
all the latest JBT/JBDS CR1a content, only the latest Beta2 + some of the CR1a content /
TP. I'll open another JIRA to get that fixed. Not sure why Paul's including such a
weird hodgepodge.
But using those -D flags you can see the IS content, and probably install it too! Not sure
about missing dependencies - didn't test that yet.
So, when we releaase JBDS 9 CR1 and JBT 4.3 CR1, users will see NONE OF THE IS STUFF until
Paul updates the released discovery sites to include his plugins. But using the above -D
flags you can preview what users WILL SEE once the Alpha2 content is through QE and is
released.
Make sense?
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
Priority: Critical
Labels: new_and_noteworthy, respin-a
Fix For: 4.3.0.CR1
Attachments: 20100_JBDS_CR1_fuse_ea_popup.png, 20100_JBDS_CR1_fuse_unavail.png,
20100_JBDS_CR1_fuse_unavail_popup.png,
20100_JBT_Core_vs_EA_versions_of_Fuse_Connector.png, 20100_JBT_latest_no_checkbox.png,
fuse-icon-fixed.png, JBDS_9_CR1a_No_Fuse.png, JBIDE-20100-2.png, JBIDE-20100-disc1.png,
JBoss_-_JBoss_Central_-_Eclipse_-__Users_max_workspaces_forjoshua.png, not-yet.png,
_JBIDE-20100__how_to_make_users_aware_of_fuse_and_other_tooling_only_being_available_from_earlyaccess__-_JBoss_Issue_Tracker_and_JBoss_-_JBoss_Central_-_Eclipse_-__Users_max_workspaces_forjoshua.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.4.11#64026)