[
https://issues.jboss.org/browse/JBIDE-18995?page=com.atlassian.jira.plugi...
]
Nick Boldt commented on JBIDE-18995:
------------------------------------
{quote} shouldn't depend on this files from the discovery plugins, and should instead
depend on the ones on download.jboss.org.{quote}
Yes, we agree here.
But I was asking if we ought to include this file inside the early access site (rather
than the discovery plugin), since otherwise it needs to be manually created for each
staged build. If it's simply part of the EA site, then when we stage the site, the
file's already on the server. And when we're ready to move from staging to
development, there's no manual step in copying content in the file; rather, we just
move the whole EA site and voila, published.
If we treat this as an artifact independent of the EA site, then maybe it should live in
http://download.jboss.org/jbosstools/configuration/ ?
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)