[JBoss JIRA] (JBTIS-608) Camel route viewer support for Java DSL
by Paul Leacu (JIRA)
[ https://issues.jboss.org/browse/JBTIS-608?page=com.atlassian.jira.plugin.... ]
Paul Leacu reassigned JBTIS-608:
--------------------------------
Assignee: Lars Heinemann
> Camel route viewer support for Java DSL
> ----------------------------------------
>
> Key: JBTIS-608
> URL: https://issues.jboss.org/browse/JBTIS-608
> Project: JBoss Tools Integration Stack
> Issue Type: Feature Request
> Components: Fuse IDE
> Affects Versions: 9.0.0.Beta1
> Reporter: Roger Hui
> Assignee: Lars Heinemann
>
> Currently, the fuse viewer can viewer and configure Camel route that are written in blueprint or spring XML. However, current there is no support for Java DSL.
> It would be nice to have the same viewer support for Java DSL. If not, a read only chart to demonstrate what the route looks like would be great.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBTIS-397) Missing source bundle for org.teiid.designer.webservice.lib
by Andrej Podhradsky (JIRA)
[ https://issues.jboss.org/browse/JBTIS-397?page=com.atlassian.jira.plugin.... ]
Andrej Podhradsky closed JBTIS-397.
-----------------------------------
Verified with JBDS-IS 9.0.0.Beta1 earlyaccess
> Missing source bundle for org.teiid.designer.webservice.lib
> -----------------------------------------------------------
>
> Key: JBTIS-397
> URL: https://issues.jboss.org/browse/JBTIS-397
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: distribution
> Affects Versions: 8.0.0.GA
> Reporter: Andrej Podhradsky
> Assignee: Barry LaFond
> Priority: Minor
> Fix For: 4.3.0.Beta1, 9.0.0.Beta1
>
>
> Source bundle for org.teiid.designer.webservice.lib is missing in JBDS-IS 8.0.0.CR3. Notice that this bundle contains only two classes
> * org/teiid/designer/webservice/lib/WebServiceLibPlugin.class
> * org/teiid/designer/webservice/lib/WebServiceLibConstants.class
> so I set the priority as minor.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3605) Rebranding to developers.redhat.com
by SJ Cox (JIRA)
[ https://issues.jboss.org/browse/JBDS-3605?page=com.atlassian.jira.plugin.... ]
SJ Cox commented on JBDS-3605:
------------------------------
Nick, these are looking good! My responses to your questions:
1. I'll supply a revised splash screen so that RHDS will align better with the dynamic text. The RGB value for the text is 255, 255, 255.
2. The RGB value for the dark gray is 36, 36, 36. Just use white text for "Installation" and step numbers.
3. Yay!
> Rebranding to developers.redhat.com
> -----------------------------------
>
> Key: JBDS-3605
> URL: https://issues.jboss.org/browse/JBDS-3605
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Components: installer, p2-product
> Reporter: Max Rydahl Andersen
> Assignee: Catherine Robson
> Priority: Blocker
> Fix For: 10.0.0.Alpha1
>
> Attachments: about-jbds10.png, header-jbds10-installer.png, RedHatDevelopersStudio_SplashScreen.zip, RedHatDeveloperStudio-Branding_Final_2016-03-16.pdf, RedHatDeveloperStudio_BrandingDeliverables.zip, splash-jbds10.png
>
>
> Developer Studio, Central and any related installers, website content etc. is requested to be rebranded under http://developers.redhat.com.
> The visual name will change but for JBDS 9.1 we will not change things that risk breaking functionallity (i.e. changing the binary from jbds to rhds will potentially break update path, ini and p2 update mechanisms)
> Thus changing about screen, splash screens etc. are the target - more deeper rebranding will be done in future and on a case-by-base basis if at all necessary.
>
> This jira will be the epic where we add related issues.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3605) Rebranding to developers.redhat.com
by SJ Cox (JIRA)
[ https://issues.jboss.org/browse/JBDS-3605?page=com.atlassian.jira.plugin.... ]
SJ Cox edited comment on JBDS-3605 at 3/24/16 10:08 AM:
--------------------------------------------------------
[~nickboldt] these are looking good! My responses to your questions:
1. I'll supply a revised splash screen so that RHDS will align better with the dynamic text. The RGB value for the text is 255, 255, 255.
2. The RGB value for the dark gray is 36, 36, 36. Just use white text for "Installation" and step numbers.
3. Yay!
was (Author: sjcox):
Nick, these are looking good! My responses to your questions:
1. I'll supply a revised splash screen so that RHDS will align better with the dynamic text. The RGB value for the text is 255, 255, 255.
2. The RGB value for the dark gray is 36, 36, 36. Just use white text for "Installation" and step numbers.
3. Yay!
> Rebranding to developers.redhat.com
> -----------------------------------
>
> Key: JBDS-3605
> URL: https://issues.jboss.org/browse/JBDS-3605
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Components: installer, p2-product
> Reporter: Max Rydahl Andersen
> Assignee: Catherine Robson
> Priority: Blocker
> Fix For: 10.0.0.Alpha1
>
> Attachments: about-jbds10.png, header-jbds10-installer.png, RedHatDevelopersStudio_SplashScreen.zip, RedHatDeveloperStudio-Branding_Final_2016-03-16.pdf, RedHatDeveloperStudio_BrandingDeliverables.zip, splash-jbds10.png
>
>
> Developer Studio, Central and any related installers, website content etc. is requested to be rebranded under http://developers.redhat.com.
> The visual name will change but for JBDS 9.1 we will not change things that risk breaking functionallity (i.e. changing the binary from jbds to rhds will potentially break update path, ini and p2 update mechanisms)
> Thus changing about screen, splash screens etc. are the target - more deeper rebranding will be done in future and on a case-by-base basis if at all necessary.
>
> This jira will be the epic where we add related issues.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3719) Initial search for an existing JBDS is present but disabled
by Jan Richter (JIRA)
Jan Richter created JBDS-3719:
---------------------------------
Summary: Initial search for an existing JBDS is present but disabled
Key: JBDS-3719
URL: https://issues.jboss.org/browse/JBDS-3719
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: installer
Affects Versions: 9.1.0.CR1
Reporter: Jan Richter
The installer calls the functionality to search for an existing JBDS when the confirm page loads, but the method has a built-in check that just interrupts it. Meaning - checking an existing installation will only proceed if a folder was selected by the user, the initial search will not.
Is this by design? If it is there is no point in initiating the search automatically.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3719) Initial search for an existing JBDS is present but disabled
by Jan Richter (JIRA)
[ https://issues.jboss.org/browse/JBDS-3719?page=com.atlassian.jira.plugin.... ]
Jan Richter reassigned JBDS-3719:
---------------------------------
Assignee: Denis Golovin
> Initial search for an existing JBDS is present but disabled
> -----------------------------------------------------------
>
> Key: JBDS-3719
> URL: https://issues.jboss.org/browse/JBDS-3719
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Reporter: Jan Richter
> Assignee: Denis Golovin
> Labels: havoc
>
> The installer calls the functionality to search for an existing JBDS when the confirm page loads, but the method has a built-in check that just interrupts it. Meaning - checking an existing installation will only proceed if a folder was selected by the user, the initial search will not.
> Is this by design? If it is there is no point in initiating the search automatically.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years