[JBoss JIRA] (JBIDE-15496) Openshift Re-org: Phase 1, easy separation
by Rob Stryker (JIRA)
Rob Stryker created JBIDE-15496:
-----------------------------------
Summary: Openshift Re-org: Phase 1, easy separation
Key: JBIDE-15496
URL: https://issues.jboss.org/browse/JBIDE-15496
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: openshift
Affects Versions: 4.2.0.Alpha1
Reporter: Rob Stryker
Assignee: Rob Stryker
Fix For: 4.2.0.Alpha1
Phase 1 for re-org is to:
1) Create the core bundle
2) Move the low-hanging fruit (easy classes)
3) Adjust tests / imports
Phase 2 will be in a separate jira but will involve migrating classes with harder core/ui mingling.
--
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
12 years, 7 months
[JBoss JIRA] (JBTIS-171) Don't override other connectors in discovery.xml
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-171?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBTIS-171:
----------------------------------
(Aside: Yes, I know that the plugin version of JBDS 7.1 discovery is 7.0.0, not 7.1. That's been fixed in Alpha2.)
> Don't override other connectors in discovery.xml
> ------------------------------------------------
>
> Key: JBTIS-171
> URL: https://issues.jboss.org/browse/JBTIS-171
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution
> Reporter: Max Rydahl Andersen
> Assignee: Paul Leacu
>
> Currently this is in discovery plugin:
> siteUrl="$\{jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
>
> And instructions to test it says:
> -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1/devstudio-integration-stack-directory.xml -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1
> This is all great but it disables all other connectors in JBDS/eclipse thus it makes it hard to get together.
> I suggest you use your own specific site url instead, something like:
> siteUrl="$\{jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
> Then the base connectors will still work.
> We might even consider using recursive properties to allow for a global override, this would need changing in both IS And core discovery.xml to the tune of:
> in core: siteUrl="$\{jboss.global.discovery.site.url,jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/core}"
> in stack:
> siteUrl="$\{jboss.global.discovery.site.url,jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
--
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
12 years, 7 months
[JBoss JIRA] (JBTIS-171) Don't override other connectors in discovery.xml
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-171?page=com.atlassian.jira.plugin.... ]
Nick Boldt commented on JBTIS-171:
----------------------------------
I think the problem is that I don't define "generating a new pair of composite*.xml files" as "a rebuild of JBDSIS", but rather a simple exercise that anyone could do.
Here's a sample of those 2 files:
http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-s...
http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-s...
Also, if you wanted to test JBDSIS 7.0.0.Beta2 against JBDS 7.1.0.Alpha1, with your solution, would require 4 runtime parameters:
-Djboss.is-discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta2/devstudio-integration-stack-directory.xml
-Djboss.is-discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta2/
-Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/development/7.1.0.Alpha1/devstudio-integration-stack-directory.xml
-Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/development/7.1.0.Alpha1/
*BUT WAIT!*
How does Central know to look in TWO different directory.xml files?
Answer: It doesn't. It can't. It can only see one jboss.discovery.directory.url - either the default one set in the Examples plugin in JBT, or the value set in jbdevstudio.ini (or eclipse.ini), or the value you pass in via commandline override.
So, to support the notion of feeding in content from more than one place (ie., the Core and IS plugins), we have a generated/merged JBDSIS directory.xml file, which references both JBDS IS and JBDS Core content in a single xml file:
{code:title=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta2/devstudio-integration-stack-directory.xml}
<entry url="https://devstudio.jboss.com/updates/7.0/discovery/com.jboss.jbds.central...." permitCategories="true"/>
<entry url="com.jboss.jbds.central.discovery.integration-stack_7.0.0.Beta2.CI-2013-09-14_08-04-55-B34-v20130914-0804-B34.jar" permitCategories="true"/>
{code}
So how do you tell JBDS 7.0 to read the combination of [JBDS 7.1 discovery plugin + JBDS IS 7.0 discovery plugin]? You generate a new .xml file which lists these:
{code}
<entry url="http://www.qa.jboss.com/binaries/RHDS/discovery/development/7.1.0.Alpha1/..." permitCategories="true"/>
<entry url="com.jboss.jbds.central.discovery.integration-stack_7.0.0.Beta2.CI-2013-09-14_08-04-55-B34-v20130914-0804-B34.jar" permitCategories="true"/>
{code}
And how do you generate that? Well, you run this build:
https://jenkins.mw.lab.eng.bos.redhat.com/hudson/job/JBDSIS-aggregate-disc/
If you have a better way that "just regenerate the XML files", I'm happy to hear it, but I don't think your solution is a complete one.
> Don't override other connectors in discovery.xml
> ------------------------------------------------
>
> Key: JBTIS-171
> URL: https://issues.jboss.org/browse/JBTIS-171
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution
> Reporter: Max Rydahl Andersen
> Assignee: Paul Leacu
>
> Currently this is in discovery plugin:
> siteUrl="$\{jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
>
> And instructions to test it says:
> -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1/devstudio-integration-stack-directory.xml -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1
> This is all great but it disables all other connectors in JBDS/eclipse thus it makes it hard to get together.
> I suggest you use your own specific site url instead, something like:
> siteUrl="$\{jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
> Then the base connectors will still work.
> We might even consider using recursive properties to allow for a global override, this would need changing in both IS And core discovery.xml to the tune of:
> in core: siteUrl="$\{jboss.global.discovery.site.url,jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/core}"
> in stack:
> siteUrl="$\{jboss.global.discovery.site.url,jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
--
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
12 years, 7 months
[JBoss JIRA] (JBTIS-161) Should the JBTIS 4.1 target platform include SpringIDE 3.3 instead of 3.2?
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-161?page=com.atlassian.jira.plugin.... ]
Paul Leacu commented on JBTIS-161:
----------------------------------
Co-installation confirmed but I did see this problem (JBDSIS 7.0.0.Beta2):
!ENTRY org.springsource.ide.eclipse.commons.frameworks.core 0 0 2013-09-17 13:29:43.908
!MESSAGE Result of converting legacy STS 2.x workspace preferences to 3.x
!SUBENTRY 1 org.springsource.ide.eclipse.commons.frameworks.core 0 0 2013-09-17 13:29:43.908
!MESSAGE Converted legacy STS plugin preferences
!SUBENTRY 1 unknown 0 0 2013-09-17 13:29:43.908
!MESSAGE OK
!SUBENTRY 1 org.springsource.ide.eclipse.commons.frameworks.core 0 0 2013-09-17 13:29:43.908
!MESSAGE Converted legacy Roo plugin state locations
!SUBENTRY 1 org.springsource.ide.eclipse.commons.frameworks.core 0 0 2013-09-17 13:29:43.908
!MESSAGE Converted legacy STS plugin state locations
!ENTRY org.eclipse.ui.navigator 4 0 2013-09-17 13:31:04.737
!MESSAGE A navigatorContent extension does not exist with id: org.springframework.ide.eclipse.aop.ui.navigator.projectExplorerContent in plugin org.springframework.ide.eclipse.aop.ui
!ENTRY org.eclipse.ui.navigator 4 0 2013-09-17 13:31:04.737
!MESSAGE A navigatorContent extension does not exist with id: org.springframework.ide.eclipse.beans.ui.navigator.springExplorerContent in plugin org.springframework.ide.eclipse.beans.ui
!ENTRY org.eclipse.ui.navigator 4 0 2013-09-17 13:31:04.737
!MESSAGE A navigatorContent extension does not exist with id: org.springframework.ide.eclipse.beans.ui.navigator.projectExplorerContent in plugin org.springframework.ide.eclipse.beans.ui
!ENTRY org.eclipse.ui.navigator 4 0 2013-09-17 13:31:04.737
!MESSAGE A navigatorContent extension does not exist with id: org.springframework.ide.eclipse.data.beans.ui.model.projectExplorerContent in plugin org.springframework.ide.eclipse.data.core
!ENTRY org.eclipse.ui.navigator 4 0 2013-09-17 13:31:04.737
!MESSAGE A navigatorContent extension does not exist with id: org.springframework.ide.eclipse.ui.navigator.springExplorerContent in plugin org.springframework.ide.eclipse.ui
!ENTRY org.eclipse.ui.navigator 4 0 2013-09-17 13:31:04.737
!MESSAGE A navigatorContent extension does not exist with id: org.springframework.ide.eclipse.ui.navigator.projectExplorerContent in plugin org.springframework.ide.eclipse.ui
!ENTRY org.eclipse.ui.navigator 4 0 2013-09-17 13:31:04.737
!MESSAGE A navigatorContent extension does not exist with id: org.springframework.ide.eclipse.ui.navigator.workingsets in plugin org.springframework.ide.eclipse.ui
!ENTRY org.eclipse.ui.navigator 4 0 2013-09-17 13:31:04.738
!MESSAGE A navigatorContent extension does not exist with id: org.springframework.ide.eclipse.webflow.ui.navigator.springExplorerContent in plugin org.springframework.ide.eclipse.webflow.ui
!ENTRY org.eclipse.ui.navigator 4 0 2013-09-17 13:31:04.738
!MESSAGE A navigatorContent extension does not exist with id: org.springframework.ide.eclipse.webflow.ui.navigator.projectExplorerContent in plugin org.springframework.ide.eclipse.webflow.ui
!ENTRY org.eclipse.ui.navigator 4 0 2013-09-17 13:31:04.738
!MESSAGE A navigatorContent extension does not exist with id: com.springsource.sts.wizard.navigatorContent in plugin org.springframework.ide.eclipse.wizard
An existing camel active-mq fuse project went from passing to fail once the SpringIDE 3.3 installation was complete.
> Should the JBTIS 4.1 target platform include SpringIDE 3.3 instead of 3.2?
> --------------------------------------------------------------------------
>
> Key: JBTIS-161
> URL: https://issues.jboss.org/browse/JBTIS-161
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: target-platform
> Affects Versions: 4.1.2
> Reporter: Nick Boldt
> Assignee: Paul Leacu
>
> The version of SpringIDE vetted by QE to be included in JBDS 7 Central is Spring IDE 3.3 [1].
> [1] http://download.jboss.org/jbosstools/updates/requirements/springide/3.3.0...
> However, as reported in http://fusesource.com/issues/browse/ECLIPSE-955 Fuse currently depends on Spring IDE 3.2 [2]
> [2] https://github.com/jbosstools/jbosstools-integration-stack/blob/master/ta...
> This disconnect may cause problems when co-installing SpringIDE 3.3 from JBDS Central and Fuse (which will bring in SpringIDE 3.2 jars).
> Therefore, should Central, JBTIS TP 4.1, and Fuse all use the same version of Spring IDE, namely 3.3 instead of 3.2 and 3.3?
--
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
12 years, 7 months
[JBoss JIRA] (JBTIS-165) Regression - Cannot add a file to the attachments
by Brian Fitzpatrick (JIRA)
[ https://issues.jboss.org/browse/JBTIS-165?page=com.atlassian.jira.plugin.... ]
Brian Fitzpatrick commented on JBTIS-165:
-----------------------------------------
Thanks Tom!
> Regression - Cannot add a file to the attachments
> -------------------------------------------------
>
> Key: JBTIS-165
> URL: https://issues.jboss.org/browse/JBTIS-165
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: ESB
> Affects Versions: 4.1.2
> Environment: JBoss ESB Tools 1.5.300.Final-v20130815-1755-B1189
> Reporter: Andrej Podhradsky
> Assignee: Viacheslav Kabanovich
> Priority: Blocker
> Attachments: esb_attachment_bug.png, test.zip
>
>
> Cannot add a file to the attachments from esbcontent folder. It's also impossible to add .txt file from the root but .zip file is possible to add. See the screenshot
--
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
12 years, 7 months
[JBoss JIRA] (JBTIS-171) Don't override other connectors in discovery.xml
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBTIS-171?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBTIS-171:
-------------------------------------------
let me clarify what I mean without overlap.
JBDS 5 soa tooling doesn't point to a merged site with both JBDS and Soa tooling. That is at least how it was originally designed.
If it now does that then JBDS 5 soa tooling has the same problem - not possible to test it with a newer version of JBDS afaics since the updatesites gets pointed to the hardcoded version that JBDSIS was built against.
Maybe i'm missing it - but I don't see how with your change above can test against JBDS 7.1 without a rebuild of JBDSIS.
> Don't override other connectors in discovery.xml
> ------------------------------------------------
>
> Key: JBTIS-171
> URL: https://issues.jboss.org/browse/JBTIS-171
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution
> Reporter: Max Rydahl Andersen
> Assignee: Paul Leacu
>
> Currently this is in discovery plugin:
> siteUrl="$\{jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
>
> And instructions to test it says:
> -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1/devstudio-integration-stack-directory.xml -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1
> This is all great but it disables all other connectors in JBDS/eclipse thus it makes it hard to get together.
> I suggest you use your own specific site url instead, something like:
> siteUrl="$\{jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
> Then the base connectors will still work.
> We might even consider using recursive properties to allow for a global override, this would need changing in both IS And core discovery.xml to the tune of:
> in core: siteUrl="$\{jboss.global.discovery.site.url,jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/core}"
> in stack:
> siteUrl="$\{jboss.global.discovery.site.url,jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
--
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
12 years, 7 months
[JBoss JIRA] (JBTIS-171) Don't override other connectors in discovery.xml
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBTIS-171?page=com.atlassian.jira.plugin.... ]
Max Rydahl Andersen commented on JBTIS-171:
-------------------------------------------
Nick - I don't see how your solution is better since mine still only require one url to be passed in.
afaics I can actually go and test JBDS 7 with JBDS Soa Tooling 5 today without overlap.
The above for me seem to still require a rebuild of JBDSIS to be able to test it in isolation with JBDS 7.1
> Don't override other connectors in discovery.xml
> ------------------------------------------------
>
> Key: JBTIS-171
> URL: https://issues.jboss.org/browse/JBTIS-171
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: distribution
> Reporter: Max Rydahl Andersen
> Assignee: Paul Leacu
>
> Currently this is in discovery plugin:
> siteUrl="$\{jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
>
> And instructions to test it says:
> -vmargs -Djboss.discovery.directory.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1/devstudio-integration-stack-directory.xml -Djboss.discovery.site.url=http://www.qa.jboss.com/binaries/RHDS/discovery/integration/integration-stack/7.0.0.Beta1
> This is all great but it disables all other connectors in JBDS/eclipse thus it makes it hard to get together.
> I suggest you use your own specific site url instead, something like:
> siteUrl="$\{jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
> Then the base connectors will still work.
> We might even consider using recursive properties to allow for a global override, this would need changing in both IS And core discovery.xml to the tune of:
> in core: siteUrl="$\{jboss.global.discovery.site.url,jboss.discovery.site.url:https://devstudio.jboss.com/updates/7.0-development/central/core}"
> in stack:
> siteUrl="$\{jboss.global.discovery.site.url,jboss.discovery.integration-stack.site.url:https://devstudio.jboss.com/updates/7.0-development/central/integration-stack/}"
--
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
12 years, 7 months