[JBoss JIRA] (JBIDE-13766) org.jboss.tools.maven.profiles.ui doesn't export all packages
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13766?page=com.atlassian.jira.plugi... ]
Snjezana Peco commented on JBIDE-13766:
---------------------------------------
Maven/m2e is required by the following functionalities:
- add/remove the Arquillian support
- add Arquillian Profiles (based on the Arquillian Forge plugin - https://github.com/forge/plugin-arquillian)
Most of the other Arquillian functionalities don't require maven/m2e.
The org.jboss.tools.maven.project.examples doesn't export any package (internal or not).
I think we would need to export all the packages and mark the internal packages with x-internal. Eclipse works that way.
For the time being, I have made a workaround for the arquillian-eclipse feature.
> org.jboss.tools.maven.profiles.ui doesn't export all packages
> -------------------------------------------------------------
>
> Key: JBIDE-13766
> URL: https://issues.jboss.org/browse/JBIDE-13766
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven
> Affects Versions: 4.1.0.Alpha1
> Reporter: Snjezana Peco
> Assignee: Snjezana Peco
>
> Some classes from those packages are required by the arquillian feature.
--
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
13 years
[JBoss JIRA] (JBIDE-13491) org.jboss.tools.jst.css.test.jbide.InputFractionalValueTest_JBIDE4790 test failure for Eclipse 4.3.0.M5
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13491?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-13491:
-----------------------------------
Fix Version/s: 4.1.0.Alpha2
(was: 4.1.x)
> org.jboss.tools.jst.css.test.jbide.InputFractionalValueTest_JBIDE4790 test failure for Eclipse 4.3.0.M5
> -------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-13491
> URL: https://issues.jboss.org/browse/JBIDE-13491
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: common/jst/core
> Affects Versions: 4.1.0.Alpha1
> Reporter: Alexey Kazakov
> Assignee: Konstantin Marmalyukov
> Fix For: 4.1.0.Alpha2
>
>
> {code}
> -------------------------------------------------------------------------------
> Test set: org.jboss.tools.jst.css.test.CSSAllTests
> -------------------------------------------------------------------------------
> Tests run: 16, Failures: 1, Errors: 0, Skipped: 0, Time elapsed: 31.228 sec <<< FAILURE!
> testPreviewView(org.jboss.tools.jst.css.test.CSSViewTest) Time elapsed: 2.592 sectestPerspective(org.jboss.tools.jst.css.test.CSSViewTest) Time elapsed: 0.431 sectestEditorViewSelection(org.jboss.tools.jst.css.test.CSSViewTest) Time elapsed: 2.448 sectestEditorViewTabs(org.jboss.tools.jst.css.test.CSSViewTest) Time elapsed: 12.118 sectestInputFractionalValue(org.jboss.tools.jst.css.test.jbide.InputFractionalValueTest_JBIDE4790) Time elapsed: 1.519 sec <<< FAILURE!
> junit.framework.ComparisonFailure: expected:<1[em1.em1].em> but was:<1[].em>
> at junit.framework.Assert.assertEquals(Assert.java:85)
> at junit.framework.Assert.assertEquals(Assert.java:91)
> at org.jboss.tools.jst.css.test.jbide.InputFractionalValueTest_JBIDE4790.testInputFractionalValue(InputFractionalValueTest_JBIDE4790.java:105)
> {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
13 years
[JBoss JIRA] (JBIDE-4790) Impossible to edit Font Size Property in CSS Properties View
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-4790?page=com.atlassian.jira.plugin... ]
Konstantin Marmalyukov resolved JBIDE-4790.
-------------------------------------------
Fix Version/s: 4.1.0.Alpha2
(was: LATER)
Resolution: Done
issue is fixed by wtp team, test is passing, so issue can be resolved.
> Impossible to edit Font Size Property in CSS Properties View
> ------------------------------------------------------------
>
> Key: JBIDE-4790
> URL: https://issues.jboss.org/browse/JBIDE-4790
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Visual Page Editor core
> Affects Versions: 3.1.0.M3, 3.1.0.M4
> Environment: Ubuntu 8.10, JBossTools revision 17062
> Reporter: Olga Chukhutsina
> Assignee: Konstantin Marmalyukov
> Fix For: 4.1.0.Alpha2
>
> Attachments: CSSPropertiesBug.png
>
>
> When you try to edit Font Size property in your css file using CSS Properties View, the source file is not edited properly and the Error message appears( An error occurred while setting the value).
> Detailed testcase:
> 1. Create css file.
> 2. input the next css class - .classA{font-size:1.6em;}
> 3. open CSS Properties View
> 4. in series delete all digits in "Font Size" field
> 5. ASSERT: error message appears
> 6. try to input fractional number again
> 7.ASSERT: font-size attribute contains only dot instead number
--
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
13 years
[JBoss JIRA] (JBIDE-13599) externalize Central site URL into a commandline property so that testing or mirroring is easier
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13599?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-13599:
-------------------------------
Attachment: JBTalpha2-using-new-variables-in-central-discovery-plugin-no-entries-found.png
> externalize Central site URL into a commandline property so that testing or mirroring is easier
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-13599
> URL: https://issues.jboss.org/browse/JBIDE-13599
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Fix For: 4.1.0.Alpha2
>
> Attachments: JBDS7alpha2-using-new-variables-in-central-discovery-plugin-no-entries-found.png, JBIDE13599-patch-to-make-central-plugins-use-variable-jboss.discovery.site.url.txt, JBTalpha2-using-new-variables-in-central-discovery-plugin-no-entries-found.png
>
>
> As discussed in https://issues.jboss.org/browse/JBDS-2469?focusedCommentId=12755106&page=... testing Central is tricky if it's not properly bootstrapped, and bootstrapping is hard when we're on an early Alpha and don't want bits to be public before they've passed QE.
> A better approach than having the update site URL used in Central's discovery plugin.xml hardcoded into that file would be to have it read from a Preference in Eclipse or JBDS. This would allow it to be overwritten/overridden should a user want to test installation from a different URL than the default value.
> This might even make it possible to have the same discovery plugin used for JBT and JBDS (assuming the list of connectors were the same, and certification was to appear for both instances) simply by having the preference changed to a different default URL when installing JBT or JBDS BYOE.
--
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
13 years
[JBoss JIRA] (JBIDE-13599) externalize Central site URL into a commandline property so that testing or mirroring is easier
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13599?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13599 at 3/13/13 2:50 PM:
-------------------------------------------------------------
1. With nanohttpd server (above) still running, build Central from master
{code}
cd /home/nboldt/tru/jbosstools-central/
mvn clean install -DskipTests
{code}
2. Add these URLs to Eclipse, and install the Central Community feature
{code}
http://download.jboss.org/jbosstools/updates/nightly/core/trunk/
/home/nboldt/tru/jbosstools-central/site/target/repository
{code}
3. Shut down eclipse completely
4. Edit eclipse.ini file adding these under the -vmargs line
{code}
-Djboss.discovery.directory.url=http://localhost:8080/discovery/core/org.jboss.tools.central.discovery/target/discovery-site/jbosstools-directory.xml
-Djboss.discovery.site.url=http://localhost:8080/discovery/core/org.jboss.tools.central.discovery/target/discovery-site/
{code}
5. Start eclipse using -consolelog -debug
Same problem:
{code}
!ENTRY org.eclipse.mylyn.discovery.core 4 0 2013-03-13 14:47:30.362
!MESSAGE org.jboss.tools.central.discovery_1.2.0.Alpha2-20130313-0625.jar_4413449892339815491.jar: Invalid connectorDescriptor/@siteUrl
!STACK 1
org.eclipse.mylyn.internal.discovery.core.model.ValidationException: Invalid connectorDescriptor/@siteUrl
at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDescriptor.validate(ConnectorDescriptor.java:228)
at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscoveryExtensionReader.readConnectorDescriptor(ConnectorDiscoveryExtensionReader.java:112)
at org.eclipse.mylyn.internal.discovery.core.model.BundleDiscoveryStrategy.processExtensions(BundleDiscoveryStrategy.java:72)
at org.eclipse.mylyn.internal.discovery.core.model.RemoteBundleDiscoveryStrategy.performDiscovery(RemoteBundleDiscoveryStrategy.java:198)
at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:115)
at org.jboss.tools.central.editors.xpl.DiscoveryViewer$18.run(DiscoveryViewer.java:1510)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
!SUBENTRY 1 org.eclipse.mylyn.discovery.core 4 0 2013-03-13 14:47:30.362
!MESSAGE Invalid connectorDescriptor/@siteUrl
{code}
!JBTalpha2-using-new-variables-in-central-discovery-plugin-no-entries-found.png!
was (Author: nickboldt):
1. With nanohttpd server (above) still running, build Central from master
{code}
cd /home/nboldt/tru/jbosstools-central/
mvn clean install -DskipTests
{code}
2. Add these URLs to Eclipse, and install the Central Community feature
{code}
http://download.jboss.org/jbosstools/updates/nightly/core/trunk/
/home/nboldt/tru/jbosstools-central/site/target/repository
{code}
{code}
3. Shut down eclipse completely
4. Edit eclipse.ini file adding these under the -vmargs line
{code}
-Djboss.discovery.directory.url=http://localhost:8080/discovery/core/org.jboss.tools.central.discovery/target/discovery-site/jbosstools-directory.xml
-Djboss.discovery.site.url=http://localhost:8080/discovery/core/org.jboss.tools.central.discovery/target/discovery-site/
{code}
5. Start eclipse using -consolelog -debug
Same problem:
{code}
!ENTRY org.eclipse.mylyn.discovery.core 4 0 2013-03-13 14:47:30.362
!MESSAGE org.jboss.tools.central.discovery_1.2.0.Alpha2-20130313-0625.jar_4413449892339815491.jar: Invalid connectorDescriptor/@siteUrl
!STACK 1
org.eclipse.mylyn.internal.discovery.core.model.ValidationException: Invalid connectorDescriptor/@siteUrl
at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDescriptor.validate(ConnectorDescriptor.java:228)
at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscoveryExtensionReader.readConnectorDescriptor(ConnectorDiscoveryExtensionReader.java:112)
at org.eclipse.mylyn.internal.discovery.core.model.BundleDiscoveryStrategy.processExtensions(BundleDiscoveryStrategy.java:72)
at org.eclipse.mylyn.internal.discovery.core.model.RemoteBundleDiscoveryStrategy.performDiscovery(RemoteBundleDiscoveryStrategy.java:198)
at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:115)
at org.jboss.tools.central.editors.xpl.DiscoveryViewer$18.run(DiscoveryViewer.java:1510)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
!SUBENTRY 1 org.eclipse.mylyn.discovery.core 4 0 2013-03-13 14:47:30.362
!MESSAGE Invalid connectorDescriptor/@siteUrl
{code}
6.
> externalize Central site URL into a commandline property so that testing or mirroring is easier
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-13599
> URL: https://issues.jboss.org/browse/JBIDE-13599
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Fix For: 4.1.0.Alpha2
>
> Attachments: JBDS7alpha2-using-new-variables-in-central-discovery-plugin-no-entries-found.png, JBIDE13599-patch-to-make-central-plugins-use-variable-jboss.discovery.site.url.txt, JBTalpha2-using-new-variables-in-central-discovery-plugin-no-entries-found.png
>
>
> As discussed in https://issues.jboss.org/browse/JBDS-2469?focusedCommentId=12755106&page=... testing Central is tricky if it's not properly bootstrapped, and bootstrapping is hard when we're on an early Alpha and don't want bits to be public before they've passed QE.
> A better approach than having the update site URL used in Central's discovery plugin.xml hardcoded into that file would be to have it read from a Preference in Eclipse or JBDS. This would allow it to be overwritten/overridden should a user want to test installation from a different URL than the default value.
> This might even make it possible to have the same discovery plugin used for JBT and JBDS (assuming the list of connectors were the same, and certification was to appear for both instances) simply by having the preference changed to a different default URL when installing JBT or JBDS BYOE.
--
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
13 years
[JBoss JIRA] (JBIDE-13599) externalize Central site URL into a commandline property so that testing or mirroring is easier
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13599?page=com.atlassian.jira.plugi... ]
Nick Boldt commented on JBIDE-13599:
------------------------------------
1. With nanohttpd server (above) still running, build Central from master
{code}
cd /home/nboldt/tru/jbosstools-central/
mvn clean install -DskipTests
{code}
2. Add these URLs to Eclipse, and install the Central Community feature
{code}
http://download.jboss.org/jbosstools/updates/nightly/core/trunk/
/home/nboldt/tru/jbosstools-central/site/target/repository
{code}
{code}
3. Shut down eclipse completely
4. Edit eclipse.ini file adding these under the -vmargs line
{code}
-Djboss.discovery.directory.url=http://localhost:8080/discovery/core/org.jboss.tools.central.discovery/target/discovery-site/jbosstools-directory.xml
-Djboss.discovery.site.url=http://localhost:8080/discovery/core/org.jboss.tools.central.discovery/target/discovery-site/
{code}
5. Start eclipse using -consolelog -debug
Same problem:
{code}
!ENTRY org.eclipse.mylyn.discovery.core 4 0 2013-03-13 14:47:30.362
!MESSAGE org.jboss.tools.central.discovery_1.2.0.Alpha2-20130313-0625.jar_4413449892339815491.jar: Invalid connectorDescriptor/@siteUrl
!STACK 1
org.eclipse.mylyn.internal.discovery.core.model.ValidationException: Invalid connectorDescriptor/@siteUrl
at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDescriptor.validate(ConnectorDescriptor.java:228)
at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscoveryExtensionReader.readConnectorDescriptor(ConnectorDiscoveryExtensionReader.java:112)
at org.eclipse.mylyn.internal.discovery.core.model.BundleDiscoveryStrategy.processExtensions(BundleDiscoveryStrategy.java:72)
at org.eclipse.mylyn.internal.discovery.core.model.RemoteBundleDiscoveryStrategy.performDiscovery(RemoteBundleDiscoveryStrategy.java:198)
at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:115)
at org.jboss.tools.central.editors.xpl.DiscoveryViewer$18.run(DiscoveryViewer.java:1510)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
!SUBENTRY 1 org.eclipse.mylyn.discovery.core 4 0 2013-03-13 14:47:30.362
!MESSAGE Invalid connectorDescriptor/@siteUrl
{code}
6.
> externalize Central site URL into a commandline property so that testing or mirroring is easier
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-13599
> URL: https://issues.jboss.org/browse/JBIDE-13599
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Fix For: 4.1.0.Alpha2
>
> Attachments: JBDS7alpha2-using-new-variables-in-central-discovery-plugin-no-entries-found.png, JBIDE13599-patch-to-make-central-plugins-use-variable-jboss.discovery.site.url.txt
>
>
> As discussed in https://issues.jboss.org/browse/JBDS-2469?focusedCommentId=12755106&page=... testing Central is tricky if it's not properly bootstrapped, and bootstrapping is hard when we're on an early Alpha and don't want bits to be public before they've passed QE.
> A better approach than having the update site URL used in Central's discovery plugin.xml hardcoded into that file would be to have it read from a Preference in Eclipse or JBDS. This would allow it to be overwritten/overridden should a user want to test installation from a different URL than the default value.
> This might even make it possible to have the same discovery plugin used for JBT and JBDS (assuming the list of connectors were the same, and certification was to appear for both instances) simply by having the preference changed to a different default URL when installing JBT or JBDS BYOE.
--
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
13 years
[JBoss JIRA] (JBIDE-4790) Impossible to edit Font Size Property in CSS Properties View
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-4790?page=com.atlassian.jira.plugin... ]
Konstantin Marmalyukov reassigned JBIDE-4790:
---------------------------------------------
Assignee: Konstantin Marmalyukov (was: Yahor Radtsevich)
> Impossible to edit Font Size Property in CSS Properties View
> ------------------------------------------------------------
>
> Key: JBIDE-4790
> URL: https://issues.jboss.org/browse/JBIDE-4790
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: Visual Page Editor core
> Affects Versions: 3.1.0.M3, 3.1.0.M4
> Environment: Ubuntu 8.10, JBossTools revision 17062
> Reporter: Olga Chukhutsina
> Assignee: Konstantin Marmalyukov
> Fix For: LATER
>
> Attachments: CSSPropertiesBug.png
>
>
> When you try to edit Font Size property in your css file using CSS Properties View, the source file is not edited properly and the Error message appears( An error occurred while setting the value).
> Detailed testcase:
> 1. Create css file.
> 2. input the next css class - .classA{font-size:1.6em;}
> 3. open CSS Properties View
> 4. in series delete all digits in "Font Size" field
> 5. ASSERT: error message appears
> 6. try to input fractional number again
> 7.ASSERT: font-size attribute contains only dot instead number
--
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
13 years
[JBoss JIRA] (JBIDE-13599) externalize Central site URL into a commandline property so that testing or mirroring is easier
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13599?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-13599:
-------------------------------
Attachment: JBDS7alpha2-using-new-variables-in-central-discovery-plugin-no-entries-found.png
> externalize Central site URL into a commandline property so that testing or mirroring is easier
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-13599
> URL: https://issues.jboss.org/browse/JBIDE-13599
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Fix For: 4.1.0.Alpha2
>
> Attachments: JBDS7alpha2-using-new-variables-in-central-discovery-plugin-no-entries-found.png, JBIDE13599-patch-to-make-central-plugins-use-variable-jboss.discovery.site.url.txt
>
>
> As discussed in https://issues.jboss.org/browse/JBDS-2469?focusedCommentId=12755106&page=... testing Central is tricky if it's not properly bootstrapped, and bootstrapping is hard when we're on an early Alpha and don't want bits to be public before they've passed QE.
> A better approach than having the update site URL used in Central's discovery plugin.xml hardcoded into that file would be to have it read from a Preference in Eclipse or JBDS. This would allow it to be overwritten/overridden should a user want to test installation from a different URL than the default value.
> This might even make it possible to have the same discovery plugin used for JBT and JBDS (assuming the list of connectors were the same, and certification was to appear for both instances) simply by having the preference changed to a different default URL when installing JBT or JBDS BYOE.
--
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
13 years
[JBoss JIRA] (JBIDE-13599) externalize Central site URL into a commandline property so that testing or mirroring is easier
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13599?page=com.atlassian.jira.plugi... ]
Nick Boldt edited comment on JBIDE-13599 at 3/13/13 1:37 PM:
-------------------------------------------------------------
Does not appear to be working.
Steps to repro:
1. Build JBDS 7 locally from trunk.
{code}
cd ~/devstudio/trunk/product
mvn clean install -P maximum,jboss-requirements-composite-extras-mirror,jbosstools-staging-aggregate
{code}
2. Apply this patch: [^JBIDE13599-patch-to-make-central-plugins-use-variable-jboss.discovery.site.url.txt]
3. Build discovery plugins locally from trunk (with patch).
{code}
cd ~/devstudio/trunk/product/discovery
mvn clean install -DUPDATE_SITE=http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ -DEXTRAS_SITE=http://download.jboss.org/jbosstools/updates/kepler/extras/
{code}
4. launch local webserver (in a separate console window - do not close until done testing):
{code}
cd /tmp
wget -nc https://raw.github.com/elonen/nanohttpd/master/NanoHTTPD.java
/opt/sun-java2-7.0/bin/javac NanoHTTPD.java
java NanoHTTPD -d ~/devstudio/trunk/product/ -p 8080
{code}
5. Install JBDS you just built.
6. Edit its jbdevstudio.ini file, setting these -D flags:
{code}
-Djboss.discovery.directory.url=http://localhost:8080/discovery/core/com.jboss.jbds.central.discovery/target/discovery-site/devstudio-directory.xml
-Djboss.discovery.site.url=http://localhost:8080/discovery/core/com.jboss.jbds.central.discovery/target/discovery-site/
{code}
7. Launch JBDS:
{code}
./jbdevstudio -consolelog -debug
{code}
8. Open the Software/Updates tab in Central. For all the entries with
{code}
siteUrl="${jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/core/}
{code}
you will see no connectors listed. Only Android and JRebel will be shown.
!JBDS7alpha2-using-new-variables-in-central-discovery-plugin-no-entries-found.png!
Error log shows:
{code}
!ENTRY org.eclipse.mylyn.discovery.core 4 0 2013-03-13 13:34:57.449
!MESSAGE com.jboss.jbds.central.discovery_7.0.0.Alpha2-20130313-0501.jar_3856479853350480263.jar: Invalid connectorDescriptor/@siteUrl
!STACK 1
org.eclipse.mylyn.internal.discovery.core.model.ValidationException: Invalid connectorDescriptor/@siteUrl
at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDescriptor.validate(ConnectorDescriptor.java:228)
at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscoveryExtensionReader.readConnectorDescriptor(ConnectorDiscoveryExtensionReader.java:112)
at org.eclipse.mylyn.internal.discovery.core.model.BundleDiscoveryStrategy.processExtensions(BundleDiscoveryStrategy.java:72)
at org.eclipse.mylyn.internal.discovery.core.model.RemoteBundleDiscoveryStrategy.performDiscovery(RemoteBundleDiscoveryStrategy.java:198)
at org.eclipse.mylyn.internal.discovery.core.model.ConnectorDiscovery.performDiscovery(ConnectorDiscovery.java:115)
at org.jboss.tools.central.editors.xpl.DiscoveryViewer$18.run(DiscoveryViewer.java:1510)
at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:121)
!SUBENTRY 1 org.eclipse.mylyn.discovery.core 4 0 2013-03-13 13:34:57.451
!MESSAGE Invalid connectorDescriptor/@siteUrl
{code}
was (Author: nickboldt):
Does not appear to be working.
Steps to repro:
1. Build JBDS 7 locally from trunk.
{code}
cd ~/devstudio/trunk/product
mvn clean install -P maximum,jboss-requirements-composite-extras-mirror,jbosstools-staging-aggregate
{code}
2. Apply this patch: [^JBIDE13599-patch-to-make-central-plugins-use-variable-jboss.discovery.site.url.txt]
3. Build discovery plugins locally from trunk (with patch).
{code}
cd ~/devstudio/trunk/product/discovery
mvn clean install -DUPDATE_SITE=http://download.jboss.org/jbosstools/updates/nightly/core/trunk/ -DEXTRAS_SITE=http://download.jboss.org/jbosstools/updates/kepler/extras/
{code}
4. launch local webserver (in a separate console window - do not close until done testing):
{code}
cd /tmp
wget -nc https://raw.github.com/elonen/nanohttpd/master/NanoHTTPD.java
/opt/sun-java2-7.0/bin/javac NanoHTTPD.java
java NanoHTTPD -d ~/devstudio/trunk/product/ -p 8080
{code}
5. Install JBDS you just built.
6. Edit its jbdevstudio.ini file, setting these -D flags:
{code}
-Djboss.discovery.directory.url=http://localhost:8080/discovery/core/com.jboss.jbds.central.discovery/target/discovery-site/devstudio-directory.xml
-Djboss.discovery.site.url=http://localhost:8080/discovery/core/com.jboss.jbds.central.discovery/target/discovery-site/
{code}
7. Launch JBDS:
{code}
./jbdevstudio -consolelog -debug
{code}
8. Open the Software/Updates tab in Central. For all the entries with
siteUrl="${jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/core/}
you will see no connectors listed. Only Android and JRebel will be shown.
> externalize Central site URL into a commandline property so that testing or mirroring is easier
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-13599
> URL: https://issues.jboss.org/browse/JBIDE-13599
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central
> Affects Versions: 4.1.0.Alpha1
> Reporter: Nick Boldt
> Assignee: Snjezana Peco
> Fix For: 4.1.0.Alpha2
>
> Attachments: JBDS7alpha2-using-new-variables-in-central-discovery-plugin-no-entries-found.png, JBIDE13599-patch-to-make-central-plugins-use-variable-jboss.discovery.site.url.txt
>
>
> As discussed in https://issues.jboss.org/browse/JBDS-2469?focusedCommentId=12755106&page=... testing Central is tricky if it's not properly bootstrapped, and bootstrapping is hard when we're on an early Alpha and don't want bits to be public before they've passed QE.
> A better approach than having the update site URL used in Central's discovery plugin.xml hardcoded into that file would be to have it read from a Preference in Eclipse or JBDS. This would allow it to be overwritten/overridden should a user want to test installation from a different URL than the default value.
> This might even make it possible to have the same discovery plugin used for JBT and JBDS (assuming the list of connectors were the same, and certification was to appear for both instances) simply by having the preference changed to a different default URL when installing JBT or JBDS BYOE.
--
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
13 years