]
Nick Boldt edited comment on JBDS-2098 at 5/15/12 11:17 AM:
------------------------------------------------------------
Installing into JBDS (jbdevstudio-product-universal-5.0.0.v201205141759M-H140-Beta3) from
Central:
./jbdevstudio -vmargs
-Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/5.0/staging/devstudio-directory.xml
!JBDS2098-jbds-central.png!
!JBDS2098-jbt-central-installed-mylyn-connectors-and-JIRA-connector-now-RHBZ-and-JBJIRA-both-avail.png!
was (Author: nickboldt):
Installing into JBDS from Central:
./jbdevstudio -vmargs
-Djboss.discovery.directory.url=https://devstudio.jboss.com/updates/5.0/staging/devstudio-directory.xml
!JBDS2098-jbds-central.png!
!JBDS2098-jbt-central-installed-mylyn-connectors-and-JIRA-connector-now-RHBZ-and-JBJIRA-both-avail.png!
provide mylyn connections for
issues.jboss.org and
bugzila.redhat.com
via JBDS & JBT Central (and on Extras site) (was: Can we provide the jira/bugzilla
defaults in JBDS?)
---------------------------------------------------------------------------------------------------------------------------------------------------------------------------
Key: JBDS-2098
URL:
https://issues.jboss.org/browse/JBDS-2098
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Feature Request
Security Level: Public(Everyone can see)
Components: Build, central, updatesite, Upstream
Affects Versions: 5.0.0.Beta3
Reporter: Max Rydahl Andersen
Assignee: Nick Boldt
Fix For: 5.0.0.Beta3
Attachments: JBDS2098-common-central.patch1-revisited.txt,
JBDS2098-common-central.patch1.txt, JBDS2098-extras-product.patch2-revisited.txt,
JBDS2098-extras-product.patch2.txt, JBDS2098-jbds-central.png,
JBDS2098-jbt-central-installed-mylyn-connectors-and-JIRA-connector-now-RHBZ-and-JBJIRA-both-avail.png,
JBDS2098-jbt-central-installed-mylyn-connectors-RHBZ-avail-but-notJBJIRA-need-to-install-JIRA-connector.png,
JBDS2098-jbt-central.png
Related to JBIDE-9351.
1. Add to JBT central discovery plugin
2. Add to JBDS Extras site
3. Add to JBDS central discovery plugin
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators: