April 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-21780) Cordova projects exported as native projects fails to run in iOS simulator under XCode

by Pavol Srna (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21780?page=com.atlassian.jira.plugi... ] Pavol Srna closed JBIDE-21780. ------------------------------ Verified in JBT 4.3.1.CR1 respin-a build. > Cordova projects exported as native projects fails to run in iOS simulator under XCode > -------------------------------------------------------------------------------------- > > Key: JBIDE-21780 > URL: https://issues.jboss.org/browse/JBIDE-21780 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid > Affects Versions: 4.3.1.Beta2 > Environment: Mac OS X 10.11.3 (El Capitan); > XCode 7.2.1; > JBDS 9.1.0 Beta2 > iPhone 6 Simulator (iOS 9.2) among others > Reporter: Vineet Reynolds > Assignee: Gorkem Ercan > Fix For: 4.3.1.CR1 > > > Cordova projects with Cordova plugins when exported as native projects appear to have incorrect locations set for config.xml. > A new config.xml appears to be created with default content and none of the Cordova plugins in the configuration, which is incorrect. In addition, the original config.xml file is created/copied into the www/ directory, which is ignored by the build and/or runtime. > When the native project is run in the iOS simulator, it shows errors/warnings that indicate failure in initialising Cordova. Plugins like the Device plugin are not loaded since they cannot be found in the config.xml (assuming the newly created config is overridding the original config), resulting in a failed application start. > The output window shows the following message: > {{ERROR: Plugin 'Device' not found, or is not a CDVPlugin. Check your plugin mapping in config.xml.}} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-631) Add test for BZ#1321332

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-631?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-631: ------------------------------------ Fix Version/s: 4.3.0.Final > Add test for BZ#1321332 > ----------------------- > > Key: JBTIS-631 > URL: https://issues.jboss.org/browse/JBTIS-631 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: BPMN2, QE > Affects Versions: 4.3.0.Beta1 > Reporter: Jozef Marko > Assignee: Jozef Marko > Fix For: 4.3.0.Final > > > See bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=1321332 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-620) Fix Guides Test

by Matej Kralik (JIRA)

[ https://issues.jboss.org/browse/JBTIS-620?page=com.atlassian.jira.plugin.... ] Matej Kralik updated JBTIS-620: ------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-integration-stack-tests/pull/679 > Fix Guides Test > --------------- > > Key: JBTIS-620 > URL: https://issues.jboss.org/browse/JBTIS-620 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: QE, teiid > Affects Versions: 4.2.5.Final, 4.3.0.Beta1 > Reporter: Matej Kralik > Assignee: Matej Kralik > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-631) Add test for BZ#1321332

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-631?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-631: ------------------------------------ Affects Version/s: 4.3.0.Beta1 > Add test for BZ#1321332 > ----------------------- > > Key: JBTIS-631 > URL: https://issues.jboss.org/browse/JBTIS-631 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: BPMN2, QE > Affects Versions: 4.3.0.Beta1 > Reporter: Jozef Marko > Assignee: Jozef Marko > Fix For: 4.3.0.Final > > > See bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=1321332 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-631) Add test for BZ#1321332

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-631?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-631: ------------------------------------ Component/s: QE > Add test for BZ#1321332 > ----------------------- > > Key: JBTIS-631 > URL: https://issues.jboss.org/browse/JBTIS-631 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: BPMN2, QE > Reporter: Jozef Marko > Assignee: Jozef Marko > > See bugzilla https://bugzilla.redhat.com/show_bug.cgi?id=1321332 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-633) Add tests for global elements in Camel Editor

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-633?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík updated JBTIS-633: ------------------------------- Original Estimate: 2 days Remaining Estimate: 2 days > Add tests for global elements in Camel Editor > --------------------------------------------- > > Key: JBTIS-633 > URL: https://issues.jboss.org/browse/JBTIS-633 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.3.0.CR1 > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Fix For: 4.3.0.Final > > Original Estimate: 2 days > Remaining Estimate: 2 days > > Tab _Configurations_ in the Camel Editor -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22108) xcodeproj is shown as a directory in Project Explorer

by Pavol Srna (JIRA)

Pavol Srna created JBIDE-22108: ---------------------------------- Summary: xcodeproj is shown as a directory in Project Explorer Key: JBIDE-22108 URL: https://issues.jboss.org/browse/JBIDE-22108 Project: Tools (JBoss Tools) Issue Type: Bug Components: aerogear-hybrid, upstream Affects Versions: 4.3.1.CR1 Reporter: Pavol Srna Fix For: 4.4.0.Alpha1 https://bugs.eclipse.org/bugs/show_bug.cgi?id=491074 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-633) Add tests for global elements in Camel Editor

by Tomáš Sedmík (JIRA)

Tomáš Sedmík created JBTIS-633: ---------------------------------- Summary: Add tests for global elements in Camel Editor Key: JBTIS-633 URL: https://issues.jboss.org/browse/JBTIS-633 Project: JBoss Tools Integration Stack Issue Type: Task Components: Fuse IDE, QE Affects Versions: 4.3.0.CR1 Reporter: Tomáš Sedmík Assignee: Tomáš Sedmík Fix For: 4.3.0.Final Tab _Configurations_ in the Camel Editor -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22105) Update AERI Server to 2.0

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22105?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-22105: --------------------------------------------- your proposal for doing this seems as good as any. Any timeframe for this ? right now I don't think we need to spend too much time on it besides verifying it works since its still "new days" having aeri running. > Update AERI Server to 2.0 > ------------------------- > > Key: JBIDE-22105 > URL: https://issues.jboss.org/browse/JBIDE-22105 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: aeri > Reporter: Marcel Bruch > Priority: Minor > > I'd like to roll out an update of the aeri server. > Notable changes on for Eclipse clients: > This update changes the sever responses send back to clients on submission of a problem report. The response format is compatible with the Eclipse AERI integration 1.100+ > No breaking changes. > Most notable changes on the server's web-site: > * The UI changed from AngularJS to Vaadin > * Improved JIRA integration. > * Improved customization of email digests and bug creation templates > * Fine-grained control over server-responses > * Auto-Actions for automated problem state transitions on problem state changes (e.g., _number-of-reporters > 100 && status=open --> Set Severity to major._ or _If new error reports arrived in with bundle.version > 1.2.3 --> set status=reopen. > Details will be announced separately. > In this bug I'm looking for a process *how* to perform an server-update for JBoss Tools. > I'd like to know who needs to be involved in case of major/minor updates? Is some testing / approval from QE required before an update can go live? > My proposed way of doing a major update: > * Copy the current database. > * Set up a sandbox instance running on the copied database > * Create a JIRA issue for the planned update. > * After approval by QE switch testing instance to production > FWIW, I don't plan to announce minor bugfixes and minor improvements (e.g., to duplicate detection) as long as they do have user-observable impact or lead to significant changes in the UI and workflows. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBTIS-632) Add regression test for FUSETOOLS-1701

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-632?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík updated JBTIS-632: ------------------------------- Original Estimate: 2 hours Remaining Estimate: 2 hours > Add regression test for FUSETOOLS-1701 > -------------------------------------- > > Key: JBTIS-632 > URL: https://issues.jboss.org/browse/JBTIS-632 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: Fuse IDE, QE > Affects Versions: 4.3.0.CR1 > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Fix For: 4.3.0.Final > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > SSIA -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2016