[JBoss JIRA] (JBIDE-15348) when hyperlinked file does not exist offer to create one
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15348?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-15348:
---------------------------------------------
No, I just see eclipse "blink" when ctrl+clicking.
> when hyperlinked file does not exist offer to create one
> --------------------------------------------------------
>
> Key: JBIDE-15348
> URL: https://issues.jboss.org/browse/JBIDE-15348
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Max Rydahl Andersen
> Assignee: Daniel Azarov
> Labels: new_and_noteworthy
> Fix For: 4.2.x
>
> Attachments: CreateFileHyperlink.png, Question.png
>
>
> When Ctrl+clicking on app.js in this snippet:
> <script type="text/javascript" src="js/app.js"></script>
> And the file js/app.js does not exist eclipse just "blinks".
> Better if we could offer creating the file, even just a blank/empty one.
> The same goes for image and css references, all those would be nice not having to go through the full ctrl+N wizard to just create such files.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (JBTIS-158) create composite site zip containing JBDS IS + dependencies for easier offline install
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBTIS-158?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBTIS-158:
-------------------------------------------
This approach (separate composite zip for offline install) will make all the sites content exposed in the P2 UI (i.e. graphiti, etc.) would show up; unless they are not listed in any categories.
But I guess there aren't really much that can be done about that issue within current p2 UI setup.
If the associate site references to JBT core are the actual matching stable urls and not version specific urls then I don't see much problem (from enduser perspective), but I do see it being tricky to control/verify by QA since they won't be able to test in real isolation.
> create composite site zip containing JBDS IS + dependencies for easier offline install
> --------------------------------------------------------------------------------------
>
> Key: JBTIS-158
> URL: https://issues.jboss.org/browse/JBTIS-158
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution
> Affects Versions: 4.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Rob Cernich
>
> Suggested by [~rcernich]:
> {quote}For the JBDS-IS site, I was recommending creating a project that would zip the JBDS-IS and JBDS-IS TP sites into a composite site. The zip contents would look something like:
> {code}./compositeContent.xml
> ./compositeArtifacts.xml
> ./7.1.0/7.1.0.Beta1-jbds-is/
> ./7.1.0/7.1.0.Beta1-jbds-is-target-platform/{code}
> {quote}
> This will work if we assume users have already installed JBDS. If we cannot make that assumption, then the composite zip must also include the JBDS update site + JBDS TP site.
> If we did a similar thing for JBT IS, it would need to contain these sites:
> {code}
> JBT webtools aggregate site (not the full JBT aggregate site)
> JBT TP
> JBT IS
> JBT IS TP
> {code}
> Or, if we assume that users will already have JBT (or some part of it) installed, then we need only:
> {code}
> JBT IS
> JBT IS TP
> {code}
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (JBIDE-15349) content assist for filenames in html
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15349?page=com.atlassian.jira.plugi... ]
Alexey Kazakov edited comment on JBIDE-15349 at 8/26/13 5:23 PM:
-----------------------------------------------------------------
Content assist works for full path and for file names: http://www.screenr.com/rQOH
It works for:
- <script src="*.js">
- <link rel="stylesheet" href="*.css">
- <img src="image files">
- <video src="video files">
- <audio src="audio filse">
- <source src="video or audio depending on the parent element">
- <a href="html files">
was (Author: akazakov):
http://www.screenr.com/rQOH
> content assist for filenames in html
> ------------------------------------
>
> Key: JBIDE-15349
> URL: https://issues.jboss.org/browse/JBIDE-15349
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Max Rydahl Andersen
> Assignee: Alexey Kazakov
> Labels: new_and_noteworthy
> Fix For: 4.2.x
>
>
> given
> <script type="text/javascript" src="|"></script>
> and app.js, lib/angular.js exists relative to the file being edited.
> then content assist at | should offer app.js and lib/angular.js as options.
> given src="a|" then content assist should at least offer app.js as completion but also nice if lib/angular.js is offered so it user does not need to remember the full path. This "secondary" location should be lower than app.js in priority.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (JBIDE-15349) content assist for filenames in html
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15349?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-15349:
-----------------------------------
Fix Version/s: 4.2.0.Alpha1
(was: 4.2.x)
> content assist for filenames in html
> ------------------------------------
>
> Key: JBIDE-15349
> URL: https://issues.jboss.org/browse/JBIDE-15349
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Max Rydahl Andersen
> Assignee: Alexey Kazakov
> Labels: new_and_noteworthy
> Fix For: 4.2.0.Alpha1
>
>
> given
> <script type="text/javascript" src="|"></script>
> and app.js, lib/angular.js exists relative to the file being edited.
> then content assist at | should offer app.js and lib/angular.js as options.
> given src="a|" then content assist should at least offer app.js as completion but also nice if lib/angular.js is offered so it user does not need to remember the full path. This "secondary" location should be lower than app.js in priority.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (JBIDE-15349) content assist for filenames in html
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15349?page=com.atlassian.jira.plugi... ]
Alexey Kazakov commented on JBIDE-15349:
----------------------------------------
http://www.screenr.com/rQOH
> content assist for filenames in html
> ------------------------------------
>
> Key: JBIDE-15349
> URL: https://issues.jboss.org/browse/JBIDE-15349
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: jsp/jsf/xml/html source editing
> Reporter: Max Rydahl Andersen
> Assignee: Alexey Kazakov
> Labels: new_and_noteworthy
> Fix For: 4.2.x
>
>
> given
> <script type="text/javascript" src="|"></script>
> and app.js, lib/angular.js exists relative to the file being edited.
> then content assist at | should offer app.js and lib/angular.js as options.
> given src="a|" then content assist should at least offer app.js as completion but also nice if lib/angular.js is offered so it user does not need to remember the full path. This "secondary" location should be lower than app.js in priority.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (JBTIS-160) Use jboss.discovery.site.url in JBT IS and JBDS IS sites so we can more easily override used URL and test Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-160?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBTIS-160 at 8/26/13 5:03 PM:
-----------------------------------------------------------
PR 104: fixes the readme (simpler): https://github.com/jbosstools/jbosstools-integration-stack/pull/104
PR 105: fixes readme and verifies that Fuse can be installed using this override (after fixing feature names in the connector): https://github.com/jbosstools/jbosstools-integration-stack/pull/105
Same instructions as before except that I built it like this in step 1:
{code}
cd ~/tru/jbosstools-integration-stack/devstudio
mvn clean install -DTARGET_PLATFORM=kepler -DBUILD_TYPE=integration -DIS_TP_VERSION=7.1.0.Final -DVERSION=7.1.0 \
-DBUILD_NUMBER=111 -DBUILD_ALIAS=CI-2013-08-21_20-10-23-B111 \
-DCOMPOSITE_SITE=http://download.jboss.org/jbosstools/updates/integration/kepler/integration-stack/aggregate/4.1.2/ \
-DUPSTREAM_DIRECTORY_XML=https://devstudio.jboss.com/updates/7.0-development/devstudio-directory.xml \
-DCOMPOSITE_URLS=https://devstudio.jboss.com/updates/7.0.0/7.0.0.GA.core/,https://devstudio.jboss.com/updates/7.0.0/7.0.0.GA.target-platform/,https://devstudio.jboss.com/updates/7.0.0/7.1.0.Beta1.jbds-is-target-platform/,http://download.jboss.org/jbosstools/builds/staging/JBDSIS-aggregate-disc/all/repo/
{code}
And of course all the file paths are in devstudio/ instead of jbosstools/, including the httpd server.
Then in steps 4-6, I installed JBDS 7 (jbdevstudio-product-universal-7.0.0.GA-v20130720-0044-B364.jar) instead of Eclipse, and ran like this:
{code}
/home/nboldt/jbdevstudio-product-universal-7.0.0.GA-v20130720-0044-B364/jbdevstudio \
-data /tmp/workspace-jbdevstudio-product-universal-7.0.0.GA-v20130720-0044-B364 \
-vmargs -Djboss.discovery.directory.url=http://localhost:8080/plugins/devstudio-integration-stack-directory.xml \
-Djboss.discovery.site.url=http://localhost:8080/discovery-site/
{code}
was (Author: nickboldt):
PR 104: fixes the readme (simpler): https://github.com/jbosstools/jbosstools-integration-stack/pull/104
PR 105: fixes readme and verifies that Fuse can be installed using this override (after fixing feature names in the connector): https://github.com/jbosstools/jbosstools-integration-stack/pull/105
Same instructions as before except that I built it like this in step 1:
{code}
cd ~/tru/jbosstools-integration-stack/devstudio
mvn clean install -DTARGET_PLATFORM=kepler -DBUILD_TYPE=integration -DIS_TP_VERSION=7.1.0.Final -DVERSION=7.1.0 -DBUILD_NUMBER=111 -DBUILD_ALIAS=CI-2013-08-21_20-10-23-B111 -DCOMPOSITE_SITE=http://download.jboss.org/jbosstools/updates/integration/kepler/integration-stack/aggregate/4.1.2/ -DUPSTREAM_DIRECTORY_XML=https://devstudio.jboss.com/updates/7.0-development/devstudio-directory.xml -DCOMPOSITE_URLS=https://devstudio.jboss.com/updates/7.0.0/7.0.0.GA.core/,https://devstudio.jboss.com/updates/7.0.0/7.0.0.GA.target-platform/,https://devstudio.jboss.com/updates/7.0.0/7.1.0.Beta1.jbds-is-target-platform/,http://download.jboss.org/jbosstools/builds/staging/JBDSIS-aggregate-disc/all/repo/
{code}
And of course all the file paths are in devstudio/ instead of jbosstools/, including the httpd server.
Then in steps 4-6, I installed JBDS 7 (jbdevstudio-product-universal-7.0.0.GA-v20130720-0044-B364.jar) instead of Eclipse, and ran like this:
{code}
/home/nboldt/jbdevstudio-product-universal-7.0.0.GA-v20130720-0044-B364/jbdevstudio -data /tmp/workspace-jbdevstudio-product-universal-7.0.0.GA-v20130720-0044-B364 -vmargs -Djboss.discovery.directory.url=http://localhost:8080/plugins/devstudio-integration-stack-directory.xml -Djboss.discovery.site.url=http://localhost:8080/discovery-site/
{code}
> Use jboss.discovery.site.url in JBT IS and JBDS IS sites so we can more easily override used URL and test Central
> -----------------------------------------------------------------------------------------------------------------
>
> Key: JBTIS-160
> URL: https://issues.jboss.org/browse/JBTIS-160
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution
> Affects Versions: 4.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Paul Leacu
>
> Rather than hardcoding URLs in plugin.properties for
> {code}
> jboss.is.update.url = http://download.jboss.org/jbosstools/updates/development/kepler/central/i...
> {code}
> or
> {code}
> jboss.is.update.url = https://devstudio.jboss.com/updates/7.0-development/central/integration-s...
> {code}
> We should use the jboss.discovery.site.url variable so that commandline value of the URL can be set, in order to make testing easier.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (JBTIS-160) Use jboss.discovery.site.url in JBT IS and JBDS IS sites so we can more easily override used URL and test Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-160?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBTIS-160 at 8/26/13 5:04 PM:
-----------------------------------------------------------
PR: https://github.com/jbosstools/jbosstools-integration-stack/pull/103
How to use:
1. Build:
{code}
cd ~/tru/jbosstools-integration-stack/jbosstools
mvn clean install -DTARGET_PLATFORM=kepler -DBUILD_TYPE=integration -DIS_TP_VERSION=4.1.2.Final -DVERSION=4.1.2 \
-DBUILD_NUMBER=111 -DBUILD_ALIAS=CI-2013-08-21_20-10-23-B111 -DCOMPOSITE_SITE=file://`pwd`/site/target/repository \
-DUPSTREAM_DIRECTORY_XML=http://download.jboss.org/jbosstools/updates/development/kepler/jbosstools-directory.xml \
-DCOMPOSITE_URLS=http://download.jboss.org/jbosstools/updates/development/kepler/,http://download.jboss.org/jbosstools/updates/integration/kepler/integration-stack/aggregate/4.1.2/,http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.1.2.Final/REPO/
{code}
2. Fix generated directory.xml to point to locally-built jar, eg., use this
{code}
<entry url="org.jboss.tools.central.discovery.integration-stack_4.1.2.CI-2013-08-21_20-10-23-B111-v20130101-0001-B111.jar" permitCategories="true"/>
{code}
instead of
{code}
<entry url="http://download.jboss.org/jbosstools/discovery/integration/integration-st..." permitCategories="true"/>
{code}
2. Launch a local nanohttpd server [1] to host the directory.xml / discovery plugin, and the Discovery composite site.
{code}
cd ~/tru/jbosstools-integration-stack/jbosstools/discovery/generation/target/
/opt/sun-java2-7.0/bin/java NanoHTTPD -d `pwd` -p 8080
{code}
[1] https://github.com/NanoHttpd/nanohttpd/blob/master/core/src/main/java/fi/...
4. install Eclipse Kepler JEE bundle; launch at fresh workspace
5. install JBoss Central into Eclipse from http://localhost:8081/discovery-site/
6. re-launch Eclipse with
{code}
./eclipse -vmargs \
-Djboss.discovery.directory.url=http://localhost:8080/plugins/jbosstools-integration-stack-directory.xml \
-Djboss.discovery.site.url=http://localhost:8081/discovery-site/
{code}
was (Author: nickboldt):
PR: https://github.com/jbosstools/jbosstools-integration-stack/pull/103
How to use:
1. Build:
cd ~/tru/jbosstools-integration-stack/jbosstools
mvn clean install -DTARGET_PLATFORM=kepler -DBUILD_TYPE=integration -DIS_TP_VERSION=4.1.2.Final -DVERSION=4.1.2 -DBUILD_NUMBER=111 -DBUILD_ALIAS=CI-2013-08-21_20-10-23-B111 -DCOMPOSITE_SITE=file://`pwd`/site/target/repository -DUPSTREAM_DIRECTORY_XML=http://download.jboss.org/jbosstools/updates/development/kepler/jbosstools-directory.xml -DCOMPOSITE_URLS=http://download.jboss.org/jbosstools/updates/development/kepler/,http://download.jboss.org/jbosstools/updates/integration/kepler/integration-stack/aggregate/4.1.2/,http://download.jboss.org/jbosstools/targetplatforms/jbtistarget/4.1.2.Final/REPO/
2. Fix generated directory.xml to point to locally-built jar, eg., use this
{code}
<entry url="org.jboss.tools.central.discovery.integration-stack_4.1.2.CI-2013-08-21_20-10-23-B111-v20130101-0001-B111.jar" permitCategories="true"/>
{code}
instead of
{code}
<entry url="http://download.jboss.org/jbosstools/discovery/integration/integration-st..." permitCategories="true"/>
{code}
2. Launch a local nanohttpd server [1] to host the directory.xml / discovery plugin, and the Discovery composite site.
{code}
cd ~/tru/jbosstools-integration-stack/jbosstools/discovery/generation/target/
/opt/sun-java2-7.0/bin/java NanoHTTPD -d `pwd` -p 8080
{code}
[1] https://github.com/NanoHttpd/nanohttpd/blob/master/core/src/main/java/fi/...
4. install Eclipse Kepler JEE bundle; launch at fresh workspace
5. install JBoss Central into Eclipse from http://localhost:8081/discovery-site/
6. re-launch Eclipse with
{code}
./eclipse -vmargs \
-Djboss.discovery.directory.url=http://localhost:8080/plugins/jbosstools-integration-stack-directory.xml \
-Djboss.discovery.site.url=http://localhost:8081/discovery-site/
{code}
> Use jboss.discovery.site.url in JBT IS and JBDS IS sites so we can more easily override used URL and test Central
> -----------------------------------------------------------------------------------------------------------------
>
> Key: JBTIS-160
> URL: https://issues.jboss.org/browse/JBTIS-160
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution
> Affects Versions: 4.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Paul Leacu
>
> Rather than hardcoding URLs in plugin.properties for
> {code}
> jboss.is.update.url = http://download.jboss.org/jbosstools/updates/development/kepler/central/i...
> {code}
> or
> {code}
> jboss.is.update.url = https://devstudio.jboss.com/updates/7.0-development/central/integration-s...
> {code}
> We should use the jboss.discovery.site.url variable so that commandline value of the URL can be set, in order to make testing easier.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months
[JBoss JIRA] (JBTIS-160) Use jboss.discovery.site.url in JBT IS and JBDS IS sites so we can more easily override used URL and test Central
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-160?page=com.atlassian.jira.plugin.... ]
Nick Boldt edited comment on JBTIS-160 at 8/26/13 5:03 PM:
-----------------------------------------------------------
PR 104: fixes the readme (simpler): https://github.com/jbosstools/jbosstools-integration-stack/pull/104
PR 105: fixes readme and verifies that Fuse can be installed using this override (after fixing feature names in the connector): https://github.com/jbosstools/jbosstools-integration-stack/pull/105
Same instructions as before except that I built it like this in step 1:
{code}
cd ~/tru/jbosstools-integration-stack/devstudio
mvn clean install -DTARGET_PLATFORM=kepler -DBUILD_TYPE=integration -DIS_TP_VERSION=7.1.0.Final -DVERSION=7.1.0 -DBUILD_NUMBER=111 -DBUILD_ALIAS=CI-2013-08-21_20-10-23-B111 -DCOMPOSITE_SITE=http://download.jboss.org/jbosstools/updates/integration/kepler/integration-stack/aggregate/4.1.2/ -DUPSTREAM_DIRECTORY_XML=https://devstudio.jboss.com/updates/7.0-development/devstudio-directory.xml -DCOMPOSITE_URLS=https://devstudio.jboss.com/updates/7.0.0/7.0.0.GA.core/,https://devstudio.jboss.com/updates/7.0.0/7.0.0.GA.target-platform/,https://devstudio.jboss.com/updates/7.0.0/7.1.0.Beta1.jbds-is-target-platform/,http://download.jboss.org/jbosstools/builds/staging/JBDSIS-aggregate-disc/all/repo/
{code}
And of course all the file paths are in devstudio/ instead of jbosstools/, including the httpd server.
Then in steps 4-6, I installed JBDS 7 (jbdevstudio-product-universal-7.0.0.GA-v20130720-0044-B364.jar) instead of Eclipse, and ran like this:
{code}
/home/nboldt/jbdevstudio-product-universal-7.0.0.GA-v20130720-0044-B364/jbdevstudio -data /tmp/workspace-jbdevstudio-product-universal-7.0.0.GA-v20130720-0044-B364 -vmargs -Djboss.discovery.directory.url=http://localhost:8080/plugins/devstudio-integration-stack-directory.xml -Djboss.discovery.site.url=http://localhost:8080/discovery-site/
{code}
was (Author: nickboldt):
PR 104: fixes the readme (simpler)
PR 105: fixes readme and verifies that Fuse can be installed using this override.
Same instructions as before except that I built it like this in step 1:
{code}
cd ~/tru/jbosstools-integration-stack/devstudio
mvn clean install -DTARGET_PLATFORM=kepler -DBUILD_TYPE=integration -DIS_TP_VERSION=7.1.0.Final -DVERSION=7.1.0 -DBUILD_NUMBER=111 -DBUILD_ALIAS=CI-2013-08-21_20-10-23-B111 -DCOMPOSITE_SITE=http://download.jboss.org/jbosstools/updates/integration/kepler/integration-stack/aggregate/4.1.2/ -DUPSTREAM_DIRECTORY_XML=https://devstudio.jboss.com/updates/7.0-development/devstudio-directory.xml -DCOMPOSITE_URLS=https://devstudio.jboss.com/updates/7.0.0/7.0.0.GA.core/,https://devstudio.jboss.com/updates/7.0.0/7.0.0.GA.target-platform/,https://devstudio.jboss.com/updates/7.0.0/7.1.0.Beta1.jbds-is-target-platform/,http://download.jboss.org/jbosstools/builds/staging/JBDSIS-aggregate-disc/all/repo/
{code}
And of course all the file paths are in devstudio/ instead of jbosstools/, including the httpd server.
Then in steps 4-6, I installed JBDS 7 (jbdevstudio-product-universal-7.0.0.GA-v20130720-0044-B364.jar) instead of Eclipse, and ran like this:
{code}
/home/nboldt/jbdevstudio-product-universal-7.0.0.GA-v20130720-0044-B364/jbdevstudio -data /tmp/workspace-jbdevstudio-product-universal-7.0.0.GA-v20130720-0044-B364 -vmargs -Djboss.discovery.directory.url=http://localhost:8080/plugins/devstudio-integration-stack-directory.xml -Djboss.discovery.site.url=http://localhost:8080/discovery-site/
{code}
{code}
> Use jboss.discovery.site.url in JBT IS and JBDS IS sites so we can more easily override used URL and test Central
> -----------------------------------------------------------------------------------------------------------------
>
> Key: JBTIS-160
> URL: https://issues.jboss.org/browse/JBTIS-160
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution
> Affects Versions: 4.1.0.Beta1
> Reporter: Nick Boldt
> Assignee: Paul Leacu
>
> Rather than hardcoding URLs in plugin.properties for
> {code}
> jboss.is.update.url = http://download.jboss.org/jbosstools/updates/development/kepler/central/i...
> {code}
> or
> {code}
> jboss.is.update.url = https://devstudio.jboss.com/updates/7.0-development/central/integration-s...
> {code}
> We should use the jboss.discovery.site.url variable so that commandline value of the URL can be set, in order to make testing easier.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira
10 years, 10 months