[JBoss JIRA] (JBTIS-697) doTry blocks disappearing in Camel Blueprint.xml
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBTIS-697?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBTIS-697:
-----------------------------
Project: JBoss Tools Integration Stack (was: Red Hat Developer Studio (DevStudio))
Key: JBTIS-697 (was: JBDS-3858)
Workflow: GIT Pull Request workflow (was: CDW v1)
Status: Open (was: New)
Docs QE Status: (was: NEW)
Component/s: Fuse IDE
(was: integration)
Affects Version/s: 9.0.0.GA
(was: 9.0.0.GA)
(was: 8.1.0.GA)
> doTry blocks disappearing in Camel Blueprint.xml
> ------------------------------------------------
>
> Key: JBTIS-697
> URL: https://issues.jboss.org/browse/JBTIS-697
> Project: JBoss Tools Integration Stack
> Issue Type: Bug
> Components: Fuse IDE
> Affects Versions: 9.0.0.GA
> Environment: Using JBDS with the integration pack.
> Developing camel routes with Blueprint XML.
> Reporter: Michael Thirion
>
> During the edition of the Camel's blueprint.xml file, when switching from "design" view to "source" view, the doTry blocks with their content totally disappear.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3860) [Fedora23] java.security.KeyException after upgrade to java-1.8.0.91 (was JBDS 9.1 not connecting to internet)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3860?page=com.atlassian.jira.plugin.... ]
Nick Boldt closed JBDS-3860.
----------------------------
Fix Version/s: 9.1.0.GA
Resolution: Done
Thanks for documenting the workaround. I'll let our docs people know this could be another known issue / getting started guide gotcha to add.
[~mhusnain] FYI.
> [Fedora23] java.security.KeyException after upgrade to java-1.8.0.91 (was JBDS 9.1 not connecting to internet)
> --------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3860
> URL: https://issues.jboss.org/browse/JBDS-3860
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Bug
> Components: updatesite, upstream
> Affects Versions: 9.1.0.GA
> Reporter: Nichola Moore
> Assignee: Nick Boldt
> Labels: docs_getting_started_guide, docs_gettingstarted_guide, known_issue, new_and_noteworthy, release_notes
> Fix For: 9.1.0.GA
>
> Attachments: JBDS9.1_bug.png, JBDS9.1_error_log.png, JBDS9.1_whole_screen.png, jbds_error_log.txt
>
>
> I have downloaded and installed JBDS 9.1.0 GA on to Fedora 23.
> When I try to get to JBDS-IS on Red Hat Central > Software/Update I get the error shown in the attached screenshot [1] in a pop-up window.
> The rest of the screen looks like the screenshot at [2] when I click OK on the pop-up window.
> [1] JBDS9.1_bug.png
> [2] JBDS9.1_whole_screen.png
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3860) [Fedora23] java.security.KeyException after upgrade to java-1.8.0.91 (was JBDS 9.1 not connecting to internet)
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3860?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3860:
-----------------------------
Summary: [Fedora23] java.security.KeyException after upgrade to java-1.8.0.91 (was JBDS 9.1 not connecting to internet) (was: JBDS 9.1 not connecting to internet)
> [Fedora23] java.security.KeyException after upgrade to java-1.8.0.91 (was JBDS 9.1 not connecting to internet)
> --------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3860
> URL: https://issues.jboss.org/browse/JBDS-3860
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Bug
> Components: updatesite, upstream
> Affects Versions: 9.1.0.GA
> Reporter: Nichola Moore
> Assignee: Nick Boldt
> Attachments: JBDS9.1_bug.png, JBDS9.1_error_log.png, JBDS9.1_whole_screen.png, jbds_error_log.txt
>
>
> I have downloaded and installed JBDS 9.1.0 GA on to Fedora 23.
> When I try to get to JBDS-IS on Red Hat Central > Software/Update I get the error shown in the attached screenshot [1] in a pop-up window.
> The rest of the screen looks like the screenshot at [2] when I click OK on the pop-up window.
> [1] JBDS9.1_bug.png
> [2] JBDS9.1_whole_screen.png
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3860) JBDS 9.1 not connecting to internet
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBDS-3860?page=com.atlassian.jira.plugin.... ]
Nick Boldt updated JBDS-3860:
-----------------------------
Component/s: upstream
> JBDS 9.1 not connecting to internet
> -----------------------------------
>
> Key: JBDS-3860
> URL: https://issues.jboss.org/browse/JBDS-3860
> Project: Red Hat Developer Studio (DevStudio)
> Issue Type: Bug
> Components: updatesite, upstream
> Affects Versions: 9.1.0.GA
> Reporter: Nichola Moore
> Assignee: Nick Boldt
> Attachments: JBDS9.1_bug.png, JBDS9.1_error_log.png, JBDS9.1_whole_screen.png, jbds_error_log.txt
>
>
> I have downloaded and installed JBDS 9.1.0 GA on to Fedora 23.
> When I try to get to JBDS-IS on Red Hat Central > Software/Update I get the error shown in the attached screenshot [1] in a pop-up window.
> The rest of the screen looks like the screenshot at [2] when I click OK on the pop-up window.
> [1] JBDS9.1_bug.png
> [2] JBDS9.1_whole_screen.png
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-19738) Failed runtime download offers no error message
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19738?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-19738:
-------------------------------
Fix Version/s: 4.4.0.Alpha2
(was: 4.4.0.Alpha1)
> Failed runtime download offers no error message
> -----------------------------------------------
>
> Key: JBIDE-19738
> URL: https://issues.jboss.org/browse/JBIDE-19738
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: runtime-detection
> Affects Versions: 4.2.3.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Priority: Minor
> Fix For: 4.4.0.Alpha2
>
>
> While verifying JBIDE-19571 the runtime download failed and there was no error whatsoever. The download of FSW 6.0 almost started, but after a few seconds on the progress bar an error window showed up for a moment and then disappeared again and the download window was gone, too. After this, there was no error in the error view or the workspace log.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-19505) Angular Code Assist doesn't work for jboss-kitchensink-angularjs app
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19505?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-19505:
-------------------------------
Fix Version/s: 4.4.0.Alpha2
(was: 4.4.0.Alpha1)
> Angular Code Assist doesn't work for jboss-kitchensink-angularjs app
> --------------------------------------------------------------------
>
> Key: JBIDE-19505
> URL: https://issues.jboss.org/browse/JBIDE-19505
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: javascript, jsp/jsf/xml/html-source-editing, upstream
> Affects Versions: 4.3.0.Alpha1
> Environment: JBDS 9.0.0.Alpha1-v20150216-1042-B11, Linux
> Reporter: Vlado Pakan
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 4.4.0.Alpha2
>
> Attachments: angular-code-assist.png
>
>
> 1. Import jboss-kitchensink-angularjs from JBoss Central
> 2. Open partials/home.html page
> 3. Open Angular Explorer and link modules > MemberService > MembersCtrl to controler
> 4. Find this line {code}<li ng-repeat="message in errorMessages">{{message}}</li>{code} and invoke Code Assist for {{m
> ERROR: Code Assist doesn't contain proposal for message variable
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBIDE-18876) Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds
by Nick Boldt (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18876?page=com.atlassian.jira.plugi... ]
Nick Boldt updated JBIDE-18876:
-------------------------------
Fix Version/s: 4.4.0.Alpha2
(was: 4.4.0.Alpha1)
> Improve TP publishing so changes released to git or deployed to nexus would not break developer local builds
> ------------------------------------------------------------------------------------------------------------
>
> Key: JBIDE-18876
> URL: https://issues.jboss.org/browse/JBIDE-18876
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: build
> Affects Versions: 4.3.0.Alpha1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Minor
> Fix For: 4.4.0.Alpha2
>
>
> Latest Thym update is 'good' example for this problem. I was in the middle of testing some changes in parent/pom.xml and suddenly build start to fail with Thym resolution problem. IMO what happened is TP .target files were published to nexus before actual p2-repos appeared online. Building from latest revision didn't help ether because of the same problem. I had to revert to previous revision to continue my task.
> So it would be good if TP builds publish binaries first and then release TP sources to git and deploy to nexus.
> Please note, that when sftp/rsync for unified TP binaries is finished it doesn't mean p2-repos are available from download.jboss.org right away.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months