[
https://issues.jboss.org/browse/JBIDE-18995?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-18995:
------------------------------------
As I started removing them I realized that this impacts the release process (because
ide-config.properties points to the staging discovery site, which includes the
earlyaccess.properties file), so maybe we should add these files into the EA site itself?
That way when we publish a new EA site + zip to staging or release, we'll just have
the new file colocated in the update site, and publishing is simpler (ide-config.props can
just point at the staging EA site, instead of the staging discovery site).
[~mickael_istria] If you agree, I can add this change/requirement to JBIDE-18984.
Early Access features can be installed from JBoss Tools p2 repository
even if 'Enable Early Access' is disabled in Central
--------------------------------------------------------------------------------------------------------------------------
Key: JBIDE-18995
URL:
https://issues.jboss.org/browse/JBIDE-18995
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: updatesite
Affects Versions: 4.2.1.Final
Reporter: Denis Golovin
Assignee: Nick Boldt
Priority: Minor
Fix For: 4.2.1.Final
Attachments: ea-disabled.png, ea-installed.png
I noticed central has "(Early Access Installed)" sign in after I installed
everything from JBos Tools stable p2 repository.
!ea-installed.png!
"Enable Early Access" checkbox is not set by default in Central Editor
!ea-disabled.png!
This means I bypassed warning dialog in this scenario.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)