October 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20884) OpenShift New and Noteworthy for 4.3.0.Final

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20884?page=com.atlassian.jira.plugi... ] Misha Ali commented on JBIDE-20884: ----------------------------------- Done, two minor typos, otherwise looks good. :) > OpenShift New and Noteworthy for 4.3.0.Final > -------------------------------------------- > > Key: JBIDE-20884 > URL: https://issues.jboss.org/browse/JBIDE-20884 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Alexey Kazakov > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate <component>-news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new <component>-news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20884) OpenShift New and Noteworthy for 4.3.0.Final

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20884?page=com.atlassian.jira.plugi... ] Fred Bricon edited comment on JBIDE-20884 at 10/5/15 9:58 PM: -------------------------------------------------------------- [~mhusnain], [~supriya.bharadwaj] wanna review do a quick review of https://github.com/jbosstools/jbosstools-website/pull/512 pretty please? Rendered page: https://github.com/fbricon/jbosstools-website/blob/os3-nn-430Final/docume... was (Author: fbricon): [~mhusnain], [~supriya.bharadwaj] wanna review do a quick review of https://github.com/jbosstools/jbosstools-website/pull/512 pretty please? > OpenShift New and Noteworthy for 4.3.0.Final > -------------------------------------------- > > Key: JBIDE-20884 > URL: https://issues.jboss.org/browse/JBIDE-20884 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Alexey Kazakov > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate <component>-news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new <component>-news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20884) OpenShift New and Noteworthy for 4.3.0.Final

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20884?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-20884: ------------------------------------- [~mhusnain], [~supriya.bharadwaj] wanna review do a quick review of https://github.com/jbosstools/jbosstools-website/pull/512 pretty please? > OpenShift New and Noteworthy for 4.3.0.Final > -------------------------------------------- > > Key: JBIDE-20884 > URL: https://issues.jboss.org/browse/JBIDE-20884 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: openshift > Reporter: Alexey Kazakov > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.3.0.Final > > > If no news for 4.3.0.Final since the last CR release for this component please reject and close this issue. The final N&N page will be aggregated from all previous N&N documents. > If you want to add a comment to the final document then create a separate <component>-news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pull request. The final N&N page will be aggregated from all previous N&N documents plus this *.Final.adoc. > If you want to replace all previous N&Ns by a new document then create a new <component>-news-4.3.0.Final.adoc file in [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...], add "Include-previous: false" directive to the document and submit a pull request. > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.... ] Paul Leacu commented on JBTIS-504: ---------------------------------- Hey [~nickboldt] - your suggestion almost works. I reused the fuse tooling connector ID for the generic ID on the released side (the NA one). The NA connector disappeared as soon as I checked the 'Enable Early Access' which is great. After I installed all of the EA components and rebooted it returned. Definitely better... > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, is-in-dev.png, is-in-dev_JBDS.png, jbtis-disc-ea.png, jbtis-disc.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- 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 Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20795?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-20795: --------------------------------------- I have fixed the marker position. Eclipse already logs an exception when starting in the debug mode (using the -debug option). Please reopen the jira if you think we always have to log it. > 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.4.0.Alpha1 > > > 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 Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20795?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-20795: ---------------------------------- Fix Version/s: 4.4.0.Alpha1 (was: 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.4.0.Alpha1 > > > 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-20912) LiveReload is not disabled

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20912?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-20912: --------------------------------------------- okey, so this work as expected. LiveReload.js is now forced into the web page so any setting in either browser or livereload will have zero effect. The livereload injected is not the livereload browsersim is reacting to. They just in this case have the same file name - it could just as well be something else than livereload that got injected. > LiveReload is not disabled > -------------------------- > > Key: JBIDE-20912 > URL: https://issues.jboss.org/browse/JBIDE-20912 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim, cordovasim > Affects Versions: 4.3.0.CR2 > Environment: JBDS 9.0.0.GA-v20151002-2235-B124, Fedora 22 KDE 64 bit, Oracle Java 1.8 > Reporter: Vlado Pakan > Assignee: Ilya Buziuk > Fix For: 4.3.1.Final > > > 1. Import HTML 5 project from JBoss Central > 2. Run it on server > 3. Open Server view, expand running server, select HTML 5 project, click on context menu 'Show In' > 'Web Browser via LiveReolad Server' > ASSERT: index.html page is opened in system web browser > 4. Copy link with index.html from system web broweer to Browsersim > ASSERT: LiveReload is enabled in BrowserSim context menu > 5. Open index.html page in VPE, change content and save it > ASSERT: Changes are rendered in BrowserSim and system web browser > 6. Disable LiveReload in BrowserSim context menu > 7. change content of index.html and save it > ASSERT: Changes are rendered in system web browser > ERROR: Changes are rendered in BrowserSim (CordovaSim) -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.... ] Paul Leacu edited comment on JBTIS-504 at 10/5/15 3:32 PM: ----------------------------------------------------------- This proposal attempts to address two issues: 1. The 'not available' Integration Stack connectors are obscuring the real stuff you can install. 2. The original Jira (20100) that said there was no way to know that Fuse Tooling was available from EA when you get to the initial discovery window. Keeping all of the existing connectors as 'not available' from the release side and pointing them to the 'Enable Early Access' seems redundant and "sucks". Removing the "not available" connectors from the release side window doesn't solve #2 above. Max suggested having just one entry for all of the missing EA IS components. This seemed logical to me. Take a look at these attachments and let me know what you think. JBDSIS Discovery: !disc-jbdsis.png|thumbnail! !disc-jbdsis-ea.png|thumbnail! JBTIS Discovery: !jbtis-disc.png|thumbnail! !jbtis-disc-ea.png|thumbnail! The obvious issue is that the generic connector stays around after you install the EA components. was (Author: pleacu): This proposal attempt to address to issues: 1. The 'not available' Integration Stack connectors are obscuring the real stuff you can install. 2. The original Jira (20100) that said there was no way to know that Fuse Tooling was available from EA when you get to the initial discovery window. Keeping all of the existing connectors as not available from the release side and pointing them to the 'Enable Early Access' seems redundant and "sucks". Removing the "not available" connectors from the release side window doesn't solve #2 above. Max suggested having just one entry for all of the missing EA IS components. This seemed logical to me. Take a look at these attachments and let me know what you think. JBDSIS Discovery: !disc-jbdsis.png|thumbnail! !disc-jbdsis-ea.png|thumbnail! JBTIS Discovery: !jbtis-disc.png|thumbnail! !jbtis-disc-ea.png|thumbnail! The obvious issue is that the generic connector stays around after you install the EA components. > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, is-in-dev.png, is-in-dev_JBDS.png, jbtis-disc-ea.png, jbtis-disc.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.... ] Paul Leacu edited comment on JBTIS-504 at 10/5/15 3:26 PM: ----------------------------------------------------------- This proposal attempt to address to issues: 1. The 'not available' Integration Stack connectors are obscuring the real stuff you can install. 2. The original Jira (20100) that said there was no way to know that Fuse Tooling was available from EA when you get to the initial discovery window. Keeping all of the existing connectors as not available from the release side and pointing them to the 'Enable Early Access' seems redundant and "sucks". Removing the "not available" connectors from the release side window doesn't solve #2 above. Max suggested having just one entry for all of the missing EA IS components. This seemed logical to me. Take a look at these attachments and let me know what you think. JBDSIS Discovery: !disc-jbdsis.png|thumbnail! !disc-jbdsis-ea.png|thumbnail! JBTIS Discovery: !jbtis-disc.png|thumbnail! !jbtis-disc-ea.png|thumbnail! The obvious issue is that the generic connector stays around after you install the EA components. was (Author: pleacu): This proposal attempt to address to issues: 1. The 'not available' Integration Stack connectors are obscuring the real stuff you can install. 2. The original Jira (20100) that said there was no way to know that Fuse Tooling was available from EA when you get to the initial discovery window. Keeping all of the existing connectors as not available from the release side and pointing them to the 'Enable Early Access' seems redundant and "sucks". Removing the "not available" connectors from the release side window doesn't solve #2 above. Max suggested having just one entry for all of the missing EA IS components. This seemed logical to me. Take a look at these attachments and let me know what you think. !disc-jbdsis.png|thumbnail! !disc-jbdsis-ea.png|thumbnail! !jbtis-disc.png|thumbnail! !jbtis-disc-ea.png|thumbnail! The obvious issue is that the generic connector stays around after you install the EA components. > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, is-in-dev.png, is-in-dev_JBDS.png, jbtis-disc-ea.png, jbtis-disc.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years, 6 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-504) publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-504?page=com.atlassian.jira.plugin.... ] Paul Leacu edited comment on JBTIS-504 at 10/5/15 3:25 PM: ----------------------------------------------------------- This proposal attempt to address to issues: 1. The 'not available' Integration Stack connectors are obscuring the real stuff you can install. 2. The original Jira (20100) that said there was no way to know that Fuse Tooling was available from EA when you get to the initial discovery window. Keeping all of the existing connectors as not available from the release side and pointing them to the 'Enable Early Access' seems redundant and "sucks". Removing the "not available" connectors from the release side window doesn't solve #2 above. Max suggested having just one entry for all of the missing EA IS components. This seemed logical to me. Take a look at these attachments and let me know what you think. !disc-jbdsis.png|thumbnail! !disc-jbdsis-ea.png|thumbnail! !jbtis-disc.png|thumbnail! !jbtis-disc-ea.png|thumbnail! The obvious issue is that the generic connector stays around after you install the EA components. was (Author: pleacu): This proposal attempt to address to issues: 1. The 'not available' Integration Stack connectors are obscuring the real stuff you can install. 2. The original Jira (20100) that said there was no way to know that Fuse Tooling was available from EA when you get to the initial discovery window. Keeping all of the existing connectors as not available from the release side and pointing them to the 'Enable Early Access' seems redundant and "sucks". Removing the "not available" connectors from the release side window doesn't solve #2 above. Max suggested having just one entry for all of the missing EA IS components. This seemed logical to me. Take a look at these attachments and let me know what you think. !disc-jbdsis.png|thumbnail! !disc-jbdsis-ea.png|thumbnail! !disc-jbtis.png|thumbnail! !disc-jbtis-ea.png|thumbnail! The obvious issue is that the generic connector stays around after you install the EA components. > publish Alpha2 IS discovery jars into JBT/JBDS CR1(a) discovery site when available > ----------------------------------------------------------------------------------- > > Key: JBTIS-504 > URL: https://issues.jboss.org/browse/JBTIS-504 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: distribution > Affects Versions: 4.3.0.Alpha2 > Reporter: Nick Boldt > Assignee: Paul Leacu > Fix For: 4.3.0.Alpha2 > > Attachments: disc-jbdsis-ea.png, disc-jbdsis.png, disc-jbtis-ea.png, disc-jbtis.png, is-in-dev.png, is-in-dev_JBDS.png, jbtis-disc-ea.png, jbtis-disc.png > > > Per the details in JBIDE-20100, when IS is ready to go, it needs to provide the discovery jars into the JBT/JBDS CR1 site so that the "not available" connectors will be seen in JBT/JBDS. -- 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 October 2015