[JBoss JIRA] (JBDS-2738) Support OpenShift 2.0 features
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-2738?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim updated JBDS-2738:
-----------------------------------
CDW release: ?
Status: New (was: New)
CDW exception: ?
CDW blocker: ?
Target Release: 7.1.0.GA
> Support OpenShift 2.0 features
> ------------------------------
>
> Key: JBDS-2738
> URL: https://issues.jboss.org/browse/JBDS-2738
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: openshift
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
>
> OpenShift 2.0 is coming, needs to investigate when that happens and what it implies for eclipse (and eventually Forge) tooling.
> This functionallity would need to be added without breaking how we work with current openshift online and openshift enterprise which has 1.x api's.
> Opening this issue to track issues related to this (please create subtasks)
--
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, 6 months
[JBoss JIRA] (JBDS-2738) Support OpenShift 2.0 features
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-2738?page=com.atlassian.jira.plugin.... ]
CDW Engine updated JBDS-2738:
-----------------------------
CDW pm_ack: ?
> Support OpenShift 2.0 features
> ------------------------------
>
> Key: JBDS-2738
> URL: https://issues.jboss.org/browse/JBDS-2738
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: openshift
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
>
> OpenShift 2.0 is coming, needs to investigate when that happens and what it implies for eclipse (and eventually Forge) tooling.
> This functionallity would need to be added without breaking how we work with current openshift online and openshift enterprise which has 1.x api's.
> Opening this issue to track issues related to this (please create subtasks)
--
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, 6 months
[JBoss JIRA] (JBTIS-171) Don't override other connectors in discovery.xml
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-171?page=com.atlassian.jira.plugin.... ]
Paul Leacu resolved JBTIS-171.
------------------------------
Resolution: Done
See lengthy discussion.
> 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, 6 months
[JBoss JIRA] (JBIDE-15486) Export Mobile Application dialog is not working
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15486?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-15486:
----------------------------------
Fix Version/s: 4.1.1.Beta1
(was: 4.1.1.Alpha1)
> Export Mobile Application dialog is not working
> -----------------------------------------------
>
> Key: JBIDE-15486
> URL: https://issues.jboss.org/browse/JBIDE-15486
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Alpha1
> Environment: Fedora 18 64 bit, KDE, JBT Alpha1-v20130909-0110-B392
> Reporter: Vlado Pakan
> Assignee: Gorkem Ercan
> Priority: Critical
> Fix For: 4.1.1.Beta1
>
>
> 1. Create new Mobile Hybrid Project.
> 2. Select it and choose Export > Mobile > Export Mobile Application
> 3. Click Next
> ERROR: Nothing happens
> 4. Click Next Again
> ERROR: Dialog with no widget is displayed with error "No platform is selected. Please select a platform"
--
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, 6 months
[JBoss JIRA] (JBIDE-15487) Export Native Platform Project is not working
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15487?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-15487:
----------------------------------
Fix Version/s: 4.1.1.Beta1
(was: 4.1.1.Alpha1)
> Export Native Platform Project is not working
> ---------------------------------------------
>
> Key: JBIDE-15487
> URL: https://issues.jboss.org/browse/JBIDE-15487
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Alpha1
> Environment: Fedora 18 64 bit, KDE, JBT Alpha1-v20130909-0110-B392
> Reporter: Vlado Pakan
> Assignee: Gorkem Ercan
> Priority: Critical
> Fix For: 4.1.1.Beta1
>
>
> 1. Create new Mobile Hybrid Project.
> 2. Select it and choose Export > Mobile > Export Native Platform Project
> 3. Click Next
> ERROR: Nothing happens
> 4. Click Next Again
> ERROR: Dialog with no widget is displayed with error "No platform is selected. Please select a platform"
--
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, 6 months