[JBoss JIRA] (JBTIS-432) Cannot install JBoss Integration and SOA Development from non-earlyaccess site
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-432?page=com.atlassian.jira.plugin.... ]
Paul Leacu reassigned JBTIS-432:
--------------------------------
Assignee: Paul Leacu
> Cannot install JBoss Integration and SOA Development from non-earlyaccess site
> ------------------------------------------------------------------------------
>
> Key: JBTIS-432
> URL: https://issues.jboss.org/browse/JBTIS-432
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 8.0.2.CR1
> Environment: JBDS 8.1.0.GA + JBDS-IS 8.0.2.ER1 (without earlyaccess)
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
>
> Cannot install JBoss Integration and SOA Development from non-earlyaccess site, namely if you try to install com.jboss.devstudio.integration-stack.soa.feature.
> Note that this is not a common use case since you have to uncheck 'Group items by category' during installation.
> The problem is that this feature includes switchyard features which are available only on early access.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 2 months
[JBoss JIRA] (JBTIS-423) Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle'
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-423?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-423:
----------------------------------
[~maxandersen] - Hey Max - I wanted to run the resolution for this Jira past you. In order to correct the duplicate category ID it was necessary to establish a new category ID for the EA connectors. This gave me two categories. In order to support production bundles which have both EA and release connectors, it was necessary to establish new connector IDs on the EA side only. The result I think is clearer for the user - see attachment. The released connector IDs remain unchanged so updates in the future will be unaffected. To see for yourself:
./jbdevstudio -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.2.ER1/devstudio-integration-stack-directory.xml -Djboss.discovery.site.integration-stack.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/8.0.2.ER1
ref: https://github.com/jbosstools/jbosstools-integration-stack/blob/jbosstool...
> Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle'
> ---------------------------------------------------------------------------------
>
> Key: JBTIS-423
> URL: https://issues.jboss.org/browse/JBTIS-423
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 8.0.1.GA
> Environment: JBDS 8.1.0.GA
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Priority: Minor
> Fix For: 8.0.2.GA
>
> Attachments: ea1.png
>
>
> When we try to install JBDS-IS 8.0.1.GA from JBoss Central we can see the following error in Error Log
> {code}
> Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle': declaring sources:
> com.jboss.jbds.central.discovery.integration_stack_8.0.1.GA_v20150408_1203_B104.jar_3208083343377093610.jar,
> com.jboss.jbds.central.discovery.integration_stack.earlyaccess_8.0.1.GA_v20150408_1203_B104.jar_2051386990248092532.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 2 months
[JBoss JIRA] (JBIDE-19687) Web Service wizard buttons act strangely if an error occurs creating CXF service
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19687?page=com.atlassian.jira.plugi... ]
Brian Fitzpatrick commented on JBIDE-19687:
-------------------------------------------
Unfortunately not, but I'll take a look this week.
> Web Service wizard buttons act strangely if an error occurs creating CXF service
> --------------------------------------------------------------------------------
>
> Key: JBIDE-19687
> URL: https://issues.jboss.org/browse/JBIDE-19687
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: webservices
> Affects Versions: 4.3.0.Alpha2
> Environment: Fedora 20 x64, openjdk 1.7.0_75
> Reporter: Jan Richter
> Assignee: Brian Fitzpatrick
> Attachments: errorMessage
>
>
> Trying to create a bottom up Apache CXF web service. If after the "Apache CXF Wbe Service Java2WS Configuration" step an error occurs, the "back" and "next" buttons stop behaving in the expected fashion.
> So far I've found these cases:
> - The back button will loop through the last 3 pages of the wizard, while pressing "next" on any of these pages will return you to the first page.
> - You can return with the back button, but pressing next will open an error dialog with the same message as the original error.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 2 months
[JBoss JIRA] (JBTIS-423) Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle'
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-423?page=com.atlassian.jira.plugin.... ]
Paul Leacu updated JBTIS-423:
-----------------------------
Attachment: ea1.png
> Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle'
> ---------------------------------------------------------------------------------
>
> Key: JBTIS-423
> URL: https://issues.jboss.org/browse/JBTIS-423
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 8.0.1.GA
> Environment: JBDS 8.1.0.GA
> Reporter: Andrej Podhradsky
> Assignee: Paul Leacu
> Priority: Minor
> Fix For: 8.0.2.GA
>
> Attachments: ea1.png
>
>
> When we try to install JBDS-IS 8.0.1.GA from JBoss Central we can see the following error in Error Log
> {code}
> Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle': declaring sources:
> com.jboss.jbds.central.discovery.integration_stack_8.0.1.GA_v20150408_1203_B104.jar_3208083343377093610.jar,
> com.jboss.jbds.central.discovery.integration_stack.earlyaccess_8.0.1.GA_v20150408_1203_B104.jar_2051386990248092532.jar
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 2 months
[JBoss JIRA] (JBTIS-434) Some features are duplicated on Update Site in site.xml
by Tomáš Sedmík (JIRA)
Tomáš Sedmík created JBTIS-434:
----------------------------------
Summary: Some features are duplicated on Update Site in site.xml
Key: JBTIS-434
URL: https://issues.jboss.org/browse/JBTIS-434
Project: JBoss Tools Integration Stack
Issue Type: Bug
Components: distribution
Affects Versions: 4.2.2.Final
Environment: JBDSIS 8.0.2.ER1
Reporter: Tomáš Sedmík
Assignee: Paul Leacu
Priority: Minor
Runtime detectors in _site.xml_ on Update Site are duplicated see:
http://www.qa.jboss.com/binaries/RHDS/updates/development/luna/integratio...
{code}
...
<feature id="org.jboss.tools.runtime.drools.detector.feature" url="features/org.jboss.tools.runtime.drools.detector.feature_6.2.0.Final.jar" version="6.2.0.Final">
<category name="BusinessLogic"/>
<category name="SOADev"/>
<category name="SOADev5"/>
</feature>
<feature id="org.jboss.tools.runtime.esb.detector.feature" url="features/org.jboss.tools.runtime.esb.detector.feature_1.5.530.Final-v20150310-1957-B70.jar" version="1.5.530.Final-v20150310-1957-B70">
<category name="SOADev5"/>
</feature>
<feature id="org.jboss.tools.runtime.jbpm.detector.feature" url="features/org.jboss.tools.runtime.jbpm.detector.feature_4.5.200.Final-v20130815-1941-B2008.jar" version="4.5.200.Final-v20130815-1941-B2008">
<category name="SOADev"/>
<category name="SOADev5"/>
</feature>
...
<!-- runtime detectors -->
<feature id="org.jboss.tools.runtime.drools.detector.feature"/>
<feature id="org.jboss.tools.runtime.esb.detector.feature"/>
<feature id="org.jboss.tools.runtime.jbpm.detector.feature"/>
...
{code}
IMHO there should be only one entry for one feature
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 2 months
[JBoss JIRA] (JBIDE-19757) Consider using main JBT site for server discovery
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19757?page=com.atlassian.jira.plugi... ]
Mickael Istria commented on JBIDE-19757:
----------------------------------------
There is no right URL with no site.xml in them.
What I did was importing the org.eclipse.wst.server.discovery bundle in my workspace, running application to check how long it took to load the JBoss Tools server adapter in the discovery page, then hacked the serverAdaptersSite.xml to replace URL, try again; then removed the site.xml on the remote site adn tried again.
AFAIK, there is not property available to override that. Hacking the serverAdaptersSite.xml is the best thing I found (I didn't search a lot).
Please try similar experiments on your side and see whether they infirm/confirm what I measured.
> Consider using main JBT site for server discovery
> -------------------------------------------------
>
> Key: JBIDE-19757
> URL: https://issues.jboss.org/browse/JBIDE-19757
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build, server
> Reporter: Mickael Istria
> Fix For: 4.3.0.Beta1
>
>
> With https://bugs.eclipse.org/bugs/show_bug.cgi?id=434185 , WTP Server Discovery mechanism was granted a new strategy which allows to rely on regular p2 metadata instead of a site.xml.
> Support for this was already merged in server ( https://github.com/jbosstools/jbosstools-server/commit/2d3cc63a9b67753ad9... )
> In order to save an artifact to manage (the webtools p2 repository), we could use this mechanism and consider contributing directly the main JBT URL to webtools discovery.
> However, server discovery also keeps older strategies and since we produce invalid site.xml files, this is currently failing
> {code}
> !ENTRY org.eclipse.equinox.p2.updatesite 2 0 2015-05-04 09:40:58.088
> !MESSAGE Error parsing feature stream. The unique identifier or the version is null or empty for the State: "Category": unique identifier="minimal-json" version="null".
> {code}
> because we are lines specifying bundle but no version in the site.xml.
> [~nickboldt] What are those site.xml useful for? Could we get rid of them?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 2 months
[JBoss JIRA] (JBIDE-19697) org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation
by Martin Malina (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19697?page=com.atlassian.jira.plugi... ]
Martin Malina commented on JBIDE-19697:
---------------------------------------
Yes, I probably was asked the first time if I wanted to record this runtime setting in the future and I agreed (I didn't pay much attention).
And probably the same thing happens for usage tracking - this is stored via Ooomph as well and I believe a new instance of Eclipse automatically gets my preference to ignore usage tracking. But looking at the Preference Recorder, the usage properties are not checked. So I guess I will have to verify this all over again, annoying :)
> org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19697
> URL: https://issues.jboss.org/browse/JBIDE-19697
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.3.0.Alpha2
> Reporter: Martin Malina
> Assignee: Snjezana Peco
> Fix For: 4.3.0.Beta1
>
> Attachments: preference-recorder.png
>
>
> When I install JBDs 9.0.0.Alpha2 B24 BYOE into new Eclipse Mars M6 and new workspace, during the installation, suddenly the runtime detection config appears inside my Eclipse isntall dir:
> {code}
> $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'
> Eclipse-runtime-test.app//Contents/Eclipse/configuration/.settings/org.jboss.tools.runtime.ui.prefs
> {code}
> This is inside the file:
> {code}
> $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'|xargs cat
> eclipse.preferences.version=1
> runtimePaths=<?xml version\="1.0" encoding\="UTF-8" standalone\="no"?>\n<runtimePaths version\="2">\n <runtimePath path\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" scanOnEveryStartup\="false" timestamp\="-1">\n <serverDefinitions>\n <serverDefinition description\="" enabled\="true" location\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" name\="JBoss EAP 6.3" type\="EAP" version\="6.3">\n <included/>\n </serverDefinition>\n </serverDefinitions>\n </runtimePath>\n</runtimePaths>\n
> {code}
> It contains /Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0 which I use regularly when testing server tooling. But how did this happen?
> I looked for the pref file before I started BYOE installation. Then a bit later, a few minutes into the installation, I checked again and the file is there now.
> Can somebody explain what's going on?
> Note: This happened to me yesterday and it surprised me, but I wasn't sure if it wasn't my mistake somehow. But Max preferred I try again, so I did. And it is happening again now.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 2 months
[JBoss JIRA] (JBDS-3377) Random "not responding" message when installing from central
by Alexander Kurtakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3377?page=com.atlassian.jira.plugin.... ]
Alexander Kurtakov commented on JBDS-3377:
------------------------------------------
I have seen this on F20 but not on newer Fedora versions. Happens when something in the UI thread blocks it for longer periods. Considering that Fedora 20 would be EOLed the coming June just update to newer Fedora.
> Random "not responding" message when installing from central
> ------------------------------------------------------------
>
> Key: JBDS-3377
> URL: https://issues.jboss.org/browse/JBDS-3377
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: central, ui/branding
> Affects Versions: 8.1.0.CR1
> Environment: Fedora 20 64-bit, OpenJDK 1.7.0_75
> Reporter: Jan Richter
> Assignee: Mickael Istria
> Priority: Minor
> Fix For: 9.0.0.Beta1
>
>
> Trying to install all from central sometimes causes the "not responding" dialog to pop up while the "Calculating Dependencies" dialog is active. The app is still responding when the dialog opens though.
> I cannot find a particular pattern to this, it looks completely random.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 2 months
[JBoss JIRA] (JBIDE-19757) Consider using main JBT site for server discovery
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19757?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19757:
---------------------------------------------
can't you just override the setting in PDE for the url and point to the right url with no site.xml on them ?
5 seconds sounds very very low to me since just getting a list of content for the main updatesite takes significantly more for me.
> Consider using main JBT site for server discovery
> -------------------------------------------------
>
> Key: JBIDE-19757
> URL: https://issues.jboss.org/browse/JBIDE-19757
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: build, server
> Reporter: Mickael Istria
> Fix For: 4.3.0.Beta1
>
>
> With https://bugs.eclipse.org/bugs/show_bug.cgi?id=434185 , WTP Server Discovery mechanism was granted a new strategy which allows to rely on regular p2 metadata instead of a site.xml.
> Support for this was already merged in server ( https://github.com/jbosstools/jbosstools-server/commit/2d3cc63a9b67753ad9... )
> In order to save an artifact to manage (the webtools p2 repository), we could use this mechanism and consider contributing directly the main JBT URL to webtools discovery.
> However, server discovery also keeps older strategies and since we produce invalid site.xml files, this is currently failing
> {code}
> !ENTRY org.eclipse.equinox.p2.updatesite 2 0 2015-05-04 09:40:58.088
> !MESSAGE Error parsing feature stream. The unique identifier or the version is null or empty for the State: "Category": unique identifier="minimal-json" version="null".
> {code}
> because we are lines specifying bundle but no version in the site.xml.
> [~nickboldt] What are those site.xml useful for? Could we get rid of them?
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 2 months
[JBoss JIRA] (JBIDE-19697) org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19697?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-19697:
---------------------------------------------
IMO if the user says yet to oomph to enable the property copying this seems to be the right thing to happen.
We should though not do this for all setings - i.e. usage tracking would not be a good thing to share this way.
> org.jboss.tools.runtime.ui.prefs mysteriously appears in Eclipse dir during JBDS BYOE installation
> --------------------------------------------------------------------------------------------------
>
> Key: JBIDE-19697
> URL: https://issues.jboss.org/browse/JBIDE-19697
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.3.0.Alpha2
> Reporter: Martin Malina
> Assignee: Snjezana Peco
> Fix For: 4.3.0.Beta1
>
> Attachments: preference-recorder.png
>
>
> When I install JBDs 9.0.0.Alpha2 B24 BYOE into new Eclipse Mars M6 and new workspace, during the installation, suddenly the runtime detection config appears inside my Eclipse isntall dir:
> {code}
> $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'
> Eclipse-runtime-test.app//Contents/Eclipse/configuration/.settings/org.jboss.tools.runtime.ui.prefs
> {code}
> This is inside the file:
> {code}
> $ find Eclipse-runtime-test.app/ -name 'org.jboss.tools.runtime.*.prefs'|xargs cat
> eclipse.preferences.version=1
> runtimePaths=<?xml version\="1.0" encoding\="UTF-8" standalone\="no"?>\n<runtimePaths version\="2">\n <runtimePath path\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" scanOnEveryStartup\="false" timestamp\="-1">\n <serverDefinitions>\n <serverDefinition description\="" enabled\="true" location\="/Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0" name\="JBoss EAP 6.3" type\="EAP" version\="6.3">\n <included/>\n </serverDefinition>\n </serverDefinitions>\n </runtimePath>\n</runtimePaths>\n
> {code}
> It contains /Users/rasp/jbossqa/runtimes/jboss-eap-6.3.0 which I use regularly when testing server tooling. But how did this happen?
> I looked for the pref file before I started BYOE installation. Then a bit later, a few minutes into the installation, I checked again and the file is there now.
> Can somebody explain what's going on?
> Note: This happened to me yesterday and it surprised me, but I wasn't sure if it wasn't my mistake somehow. But Max preferred I try again, so I did. And it is happening again now.
--
This message was sent by Atlassian JIRA
(v6.3.15#6346)
11 years, 2 months