September 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-20768) Display error dialog when no iOS SDKs are found

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20768?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20768: ----------------------------------- Fix Version/s: (was: 4.3.0.Final) > Display error dialog when no iOS SDKs are found > ----------------------------------------------- > > Key: JBIDE-20768 > URL: https://issues.jboss.org/browse/JBIDE-20768 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, upstream > Affects Versions: 4.3.0.CR1 > Reporter: Pavol Srna > Assignee: Gorkem Ercan > Fix For: 4.3.1.Final > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=478146 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20665) Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle': declaring sources

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20665?page=com.atlassian.jira.plugi... ] Alexey Kazakov resolved JBIDE-20665. ------------------------------------ Fix Version/s: 4.3.0.CR1 (was: 4.3.0.Final) Resolution: Duplicate Issue Duplicates JBDS-3519 > Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle': declaring sources > ---------------------------------------------------------------------------------------------------- > > Key: JBIDE-20665 > URL: https://issues.jboss.org/browse/JBIDE-20665 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.3.0.CR1 > Environment: JBDS 9.0.0.CR1 B100, L64 > Reporter: Jiri Peterka > Assignee: Mickael Istria > Fix For: 4.3.0.CR1 > > > {code} > Duplicate category id 'com.jboss.jbds.central.discovery.integration-stack.bundle': declaring sources: com.jboss.jbds.central.discovery.earlyaccess_9.0.0.CR1_v20150913_1206_B111.jar_519737075012215798.jar, com.jboss.jbds.central.discovery_9.0.0.CR1_v20150913_1206_B111.jar_3714689073912402022.jar > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20760) docker feature not included in Marketplace entry for JBoss Tools

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20760?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20760: ----------------------------------- Priority: Critical (was: Major) > docker feature not included in Marketplace entry for JBoss Tools > ---------------------------------------------------------------- > > Key: JBIDE-20760 > URL: https://issues.jboss.org/browse/JBIDE-20760 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: marketplace > Affects Versions: 4.3.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Priority: Critical > Labels: xtriage > Fix For: 4.3.0.Final > > Attachments: 20760.png > > > Because we removed the docker feature and replaced it with the docker plugins in order to avoid the odious problem of a disabled update site appearing in Eclipse's list of Available Update Sites, we no longer have a way to provide the docker tooling via our Marketplace entry. > Solution: > 1. Stop caring if there's an extra *disabled* update site in Eclipse when we install JBT (there's a disabled Mylyn one there too, plus 4 enabled ones for Mars, Mylyn, Eclipse, and WTP, so what's one more?). > 2. Use the Docker Tooling feature in JBT's CoreTools category & on the Marketplace entry (as we did for Beta2). > Then, for JBDS, we continue to just use the plugins and include them in the com.jboss.devstudio.core.feature so they're installed OOTB via the BYOE / Core feature (and also via Marketplace). > Sound good? > Alternative solutions: > a. Create a new feature wrapper, just to contain the docker plugins > b. Update some JBT plugins to depend on the docker plugins so they get installed along with the existing JBT plugin > c. do nothing -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20770) Cannot run on iOS simulator - out of bounds exception

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20770?page=com.atlassian.jira.plugi... ] Alexey Kazakov commented on JBIDE-20770: ---------------------------------------- commit in master with updated thym - https://github.com/jbosstools/jbosstools-aerogear/commit/973c15ac44bcee9f... > Cannot run on iOS simulator - out of bounds exception > ----------------------------------------------------- > > Key: JBIDE-20770 > URL: https://issues.jboss.org/browse/JBIDE-20770 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, upstream > Affects Versions: 4.3.0.CR1 > Reporter: Pavol Srna > Assignee: Gorkem Ercan > Priority: Blocker > Fix For: 4.3.0.CR2 > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=478154 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20770) Cannot run on iOS simulator - out of bounds exception

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20770?page=com.atlassian.jira.plugi... ] Gorkem Ercan resolved JBIDE-20770. ---------------------------------- Resolution: Done > Cannot run on iOS simulator - out of bounds exception > ----------------------------------------------------- > > Key: JBIDE-20770 > URL: https://issues.jboss.org/browse/JBIDE-20770 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, upstream > Affects Versions: 4.3.0.CR1 > Reporter: Pavol Srna > Assignee: Gorkem Ercan > Priority: Blocker > Fix For: 4.3.0.CR2 > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=478154 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20770) Cannot run on iOS simulator - out of bounds exception

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20770?page=com.atlassian.jira.plugi... ] Gorkem Ercan commented on JBIDE-20770: -------------------------------------- I have now pulled in the new Thym to master which includes a fix. > Cannot run on iOS simulator - out of bounds exception > ----------------------------------------------------- > > Key: JBIDE-20770 > URL: https://issues.jboss.org/browse/JBIDE-20770 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: aerogear-hybrid, upstream > Affects Versions: 4.3.0.CR1 > Reporter: Pavol Srna > Assignee: Gorkem Ercan > Priority: Blocker > Fix For: 4.3.0.CR2 > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=478154 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20795) canonical form is required(project=arquillian-test)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20795?page=com.atlassian.jira.plugi... ] Alexey Kazakov reassigned JBIDE-20795: -------------------------------------- Assignee: Snjezana Peco > canonical form is required(project=arquillian-test) > --------------------------------------------------- > > Key: JBIDE-20795 > URL: https://issues.jboss.org/browse/JBIDE-20795 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: arquillian > Reporter: Aslak Knutsen > Assignee: Snjezana Peco > Fix For: 4.3.x > > > This code: > {code} > @RunWith(Arquillian.class) > public class SimpleTestCase { > @Deployment > public static WebArchive test() { > return ShrinkWrap.create(WebArchive.class) > .addAsLibraries(Maven.resolver().resolve("").withoutTransitivity().asFile()); > } > > @Test > public void shouldX() {} > } > {code} > produce the following warning: > {code} > null > org.jboss.tools.arquillian.core > Warning > Wed Sep 23 23:16:17 CEST 2015 > canonical form is required(project=arquillian-test) > {code} > On top of my head I have no idea what that means. The warning contains no stack trace so hard to tell where it comes from. > With a little digging it's due to the resolve("") failing since the String input is not in the correct format. > The warning is marked on the Method line, not on the line where the Resolver is called. > Would it be possible to re position this somehow? At least get a stack trace or something in the warning? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20795) canonical form is required(project=arquillian-test)

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20795?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-20795: ----------------------------------- Fix Version/s: 4.3.x > canonical form is required(project=arquillian-test) > --------------------------------------------------- > > Key: JBIDE-20795 > URL: https://issues.jboss.org/browse/JBIDE-20795 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: arquillian > Reporter: Aslak Knutsen > Assignee: Snjezana Peco > Fix For: 4.3.x > > > This code: > {code} > @RunWith(Arquillian.class) > public class SimpleTestCase { > @Deployment > public static WebArchive test() { > return ShrinkWrap.create(WebArchive.class) > .addAsLibraries(Maven.resolver().resolve("").withoutTransitivity().asFile()); > } > > @Test > public void shouldX() {} > } > {code} > produce the following warning: > {code} > null > org.jboss.tools.arquillian.core > Warning > Wed Sep 23 23:16:17 CEST 2015 > canonical form is required(project=arquillian-test) > {code} > On top of my head I have no idea what that means. The warning contains no stack trace so hard to tell where it comes from. > With a little digging it's due to the resolve("") failing since the String input is not in the correct format. > The warning is marked on the Method line, not on the line where the Resolver is called. > Would it be possible to re position this somehow? At least get a stack trace or something in the warning? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20795) canonical form is required(project=arquillian-test)

by Aslak Knutsen (JIRA)

Aslak Knutsen created JBIDE-20795: ------------------------------------- Summary: canonical form is required(project=arquillian-test) Key: JBIDE-20795 URL: https://issues.jboss.org/browse/JBIDE-20795 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: arquillian Reporter: Aslak Knutsen This code: {code} @RunWith(Arquillian.class) public class SimpleTestCase { @Deployment public static WebArchive test() { return ShrinkWrap.create(WebArchive.class) .addAsLibraries(Maven.resolver().resolve("").withoutTransitivity().asFile()); } @Test public void shouldX() {} } {code} produce the following warning: {code} null org.jboss.tools.arquillian.core Warning Wed Sep 23 23:16:17 CEST 2015 canonical form is required(project=arquillian-test) {code} On top of my head I have no idea what that means. The warning contains no stack trace so hard to tell where it comes from. With a little digging it's due to the resolve("") failing since the String input is not in the correct format. The warning is marked on the Method line, not on the line where the Resolver is called. Would it be possible to re position this somehow? At least get a stack trace or something in the warning? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20783) For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [OpenShift]

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20783?page=com.atlassian.jira.plugi... ] Fred Bricon resolved JBIDE-20783. --------------------------------- Assignee: Fred Bricon Resolution: Done Done in master > For JBIDE 4.4.0.Alpha1: Prepare for future Alpha1 [OpenShift] > ------------------------------------------------------------- > > Key: JBIDE-20783 > URL: https://issues.jboss.org/browse/JBIDE-20783 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Nick Boldt > Assignee: Fred Bricon > Priority: Blocker > Labels: task > Fix For: 4.4.0.Alpha1 > > > For JBIDE 4.4.0.Alpha1 [OpenShift]: Please perform the following tasks: > 0. If your component is at end of life and won't have new development on Eclipse 4.6 (Neon) you can probably *{color:red}Reject this JIRA{color}*. Please confirm with Alexey or Max. (For example, Portlet & GWT did no development for Mars.) > Otherwise: > 1. In your *{color:orange}master branch{color}* ONLY, ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 4.3.0 to 4.4.0 (if planning minor changes) or from 4.3.0 to 4.3.100 (if planning only maintenance). > {code} > mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.4.0-SNAPSHOT > {code} > 2. In your *{color:orange}master branch{color}* ONLY, update your root pom to use parent pom version *{color:orange}4.4.0.Alpha1-SNAPSHOT{color}*; > {code} > <parent> > <groupId>org.jboss.tools</groupId> > <artifactId>parent</artifactId> > <version>4.4.0.Alpha1-SNAPSHOT</version> > </parent> > {code} > 3. In your *{color:orange}master branch{color}* ONLY, ensure you've built & run your tests using the latest target platform version *{color:orange}4.60.0.Alpha1-SNAPSHOT{color}*; > {code} > mvn clean verify -Dtpc.version=4.60.0.Alpha1-SNAPSHOT > {code} > 4. Close (do not resolve) this JIRA when done. > [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for OpenShift task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...] -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

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 September 2015