May 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBTIS-440) Back off version of Saxon in JBTIS TP to 4.2.4.Final - Teiid isn't upgrading until JBDSIS 8.0.3

by Paul Leacu (JIRA)

[ https://issues.jboss.org/browse/JBTIS-440?page=com.atlassian.jira.plugin.... ] Paul Leacu updated JBTIS-440: ----------------------------- Summary: Back off version of Saxon in JBTIS TP to 4.2.4.Final - Teiid isn't upgrading until JBDSIS 8.0.3 (was: Back off version of JBTIS TP to 4.2.2.Final - Teiid isn't upgrading until JBDSIS 8.0.3) > Back off version of Saxon in JBTIS TP to 4.2.4.Final - Teiid isn't upgrading until JBDSIS 8.0.3 > ----------------------------------------------------------------------------------------------- > > Key: JBTIS-440 > URL: https://issues.jboss.org/browse/JBTIS-440 > Project: JBoss Tools Integration Stack > Issue Type: Task > Components: target-platform > Affects Versions: 8.0.2.GA > Reporter: Paul Leacu > Assignee: Paul Leacu > Fix For: 8.0.2.GA > > > Teiid Designer needs a new Saxon/ Locus for their Luna August release. For JBDSIS 8.0.2 they need to stay with the old Saxon from JBTIS TP 4.2.2.Final. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ] Radim Hopp edited comment on JBIDE-19410 at 5/18/15 9:55 AM: ------------------------------------------------------------- While trying to verify this issue, I'm unable to start eclipse with p2 disabled. I thought that unchecking "Support software installation in the launched application" in launch config is enough. Here is screencast showing what i'm trying to do: https://youtu.be/Lh02z4V1tzE I shouldn't be able to install anything from central, when "Support software..." checkbox is unchecked, right? And moreover this issue should show itself (on earlier builds by modal window, in latter build by warning in error log or something like that)? was (Author: rhopp): While trying to verify this issue, I'm unable to start eclipse with p2 disabled. I thought that unchecking "Support software installation in the launched application" in launch config is enough. Here is screencast showing what i'm trying to do: https://youtu.be/Lh02z4V1tzE I shouldn't be able to install anything from central, when "Support software..." checkbox is unchecked, right? > earlyaccess still not failing gracefully > ---------------------------------------- > > Key: JBIDE-19410 > URL: https://issues.jboss.org/browse/JBIDE-19410 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE) > start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently. > but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19410) earlyaccess still not failing gracefully

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19410?page=com.atlassian.jira.plugi... ] Radim Hopp commented on JBIDE-19410: ------------------------------------ While trying to verify this issue, I'm unable to start eclipse with p2 disabled. I thought that unchecking "Support software installation in the launched application" in launch config is enough. Here is screencast showing what i'm trying to do: https://youtu.be/Lh02z4V1tzE I shouldn't be able to install anything from central, when "Support software..." checkbox is unchecked, right? > earlyaccess still not failing gracefully > ---------------------------------------- > > Key: JBIDE-19410 > URL: https://issues.jboss.org/browse/JBIDE-19410 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Reporter: Max Rydahl Andersen > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Alpha2 > > > start jboss tools in PDE and earlyaccess will pop up with error dialog that it had an error because it could not install things (which is expected when running in PDE) > start jboss tools without network access and I sometime see it pop up - can't reprouce that consistently. > but in short - seems like earlyaccess continues to want to tell users that something is wrong with early access even when it is not enabled but nor should it even if enabled. Show such error on the earlyaccess page rather than a blocking dialog. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19816) Add Bintray JCenter to Maven Repository wizard

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19816?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-19816: ---------------------------------------- Sprint: Sprint #3 May 2015 (was: 2015/S9 (27-Apr > 10-May)) > Add Bintray JCenter to Maven Repository wizard > ---------------------------------------------- > > Key: JBIDE-19816 > URL: https://issues.jboss.org/browse/JBIDE-19816 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: maven > Affects Versions: 4.2.3.Final > Reporter: Fred Bricon > Assignee: Fred Bricon > Priority: Minor > Fix For: 4.3.0.Beta1 > > > [Bintray JCenter|https://bintray.com/bintray/jcenter] is one alternative (and superset) to Maven Central. I believe we should add it to the list of available Maven repository templates in Preferences > JBoss Tools > JBoss Maven Integration > Configure Maven Repositories... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19806) Red Deer archetype project is not imported correctly (not detected as Maven)

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19806?page=com.atlassian.jira.plugi... ] Mickael Istria resolved JBIDE-19806. ------------------------------------ Resolution: Done The part about archetype being wrongly imported should be fixed with https://github.com/jbosstools/jbosstools-playground/commit/81087ea8d2738a... > Red Deer archetype project is not imported correctly (not detected as Maven) > ---------------------------------------------------------------------------- > > Key: JBIDE-19806 > URL: https://issues.jboss.org/browse/JBIDE-19806 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Reporter: Lucia Jelinkova > Attachments: archetype-project.png > > > When I try to import from Red Deer project archetype, I end up with 2 projects instead of one. > The first one, archetype, is the correct one, however, in the report diaog there is not written that it is a maven project, even though it actually has maven nature after the import. > The second one, archetype-resources is actually located in the source folder of the previous one, so I think it should be skipped. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (TOOLSDOC-640) Need to ensure users fully install Android SDK before attempting to build/import hybrid mobile project in JBoss Tools/JBDS

by Misha Ali (JIRA)

[ https://issues.jboss.org/browse/TOOLSDOC-640?page=com.atlassian.jira.plug... ] Misha Ali resolved TOOLSDOC-640. -------------------------------- Resolution: Done Fixed in both upstream and enterprise documentation at the link provided earlier. > Need to ensure users fully install Android SDK before attempting to build/import hybrid mobile project in JBoss Tools/JBDS > -------------------------------------------------------------------------------------------------------------------------- > > Key: TOOLSDOC-640 > URL: https://issues.jboss.org/browse/TOOLSDOC-640 > Project: Documentation for JBoss Tools and Developer Studio > Issue Type: Feature Request > Components: General documentation issues > Affects Versions: 4.3.0.Final > Reporter: Len DiMaggio > Assignee: Misha Ali > Fix For: 4.3.0.Final > > > This is related to: https://issues.jboss.org/browse/JBIDE-19716 > The point to make clear to users is that they may see unexpected errors if they create/install a hybrid mobile project before first fully installing and Android SDK. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19817) Application wizard: v3 application wizard needs to be able to react to changing connections

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19817?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19817: ------------------------------------- Summary: Application wizard: v3 application wizard needs to be able to react to changing connections (was: Application wizard: v3 application wizard needs to be able to react to chaning connections) > Application wizard: v3 application wizard needs to be able to react to changing connections > ------------------------------------------------------------------------------------------- > > Key: JBIDE-19817 > URL: https://issues.jboss.org/browse/JBIDE-19817 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > > The current application wizard for OpenShift v3 takes a project in the constructor. It was designed to be launched from the explorer where a v3 connection/project is selected before the wizard is launched. The wizard is not able to react to changing connections. In order for the wizard to be able to get launched from File->New->OpenShift we need the wizard to be able to react to chaning connections. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19759) Application wizard: cannot launch v3 application wizard via File->New->OpenShift

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19759?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-19759 at 5/18/15 5:45 AM: ------------------------------------------------------------------- When launching the application wizard via File->New->OpenShift the connection page is to be shown in the first place. Hitting "Next" then takes the user to either the v2 or the v3 application wizard. The user then can get back to the connection page whenever he wants. This requires the application wizard(s) to be able to react to changing connections. It turns out that the OpenShift v3 application wizard was implemented not being able to react to changing connections. The v3 app wizard needs to be improved in this matter before we can allow users to get to the v3 app wizard via File->New->OpenShift: JBIDE-19817 I thus prepared v3 with the extension point to contribute the application wizard but commented it https://github.com/jbosstools/jbosstools-openshift/pull/622/files#diff-e2...: {code:title=org.jboss.tools.openshift.ui/plugin.xml}    {code} The connection page will then show an error telling the user that there's no application wizard for 3 connections once the user selects the "OpenShift v3" server type: !no-application-wizard.png! was (Author: adietish): When launching the application wizard via File->New->OpenShift the connection page is to be shown in the first place. Hitting "Next" then takes the user to either the v2 or the v3 application wizard. The user then can get back to the connection page whenever he wants. This requires the application wizard(s) to be able to react to changing connections. It turns out that the OpenShift v3 application wizard was implemented not being able to react to changing connections. The v3 app wizard needs to be improved in this matter before we can allow users to get to the v3 app wizard via File->New->OpenShift: JBIDE-19817 I thus prepared v3 with the extension point to contribute the application wizard but commented it: {code:title=org.jboss.tools.openshift.ui/plugin.xml}    {code} The connection page will then show an error telling the user that there's no application wizard for 3 connections once the user selects the "OpenShift v3" server type: !no-application-wizard.png! > Application wizard: cannot launch v3 application wizard via File->New->OpenShift > -------------------------------------------------------------------------------- > > Key: JBIDE-19759 > URL: https://issues.jboss.org/browse/JBIDE-19759 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Beta1 > > Attachments: empty-v2-wizard-page.png, no-application-wizard.png > > > If you launch the application wizard via File->New->OpenShift you can only create OpenShift v2 applications. I should get v3 pages if I select a v3 connection in the 1st wizard page with the connection credentials. Currently if I select a v2 connection I can create v2 applications. If I select a v3 connection the wizard is non-functional. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19817) Application wizard: v3 application wizard needs to be able to react to chaning connections

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19817?page=com.atlassian.jira.plugi... ] Andre Dietisheim reassigned JBIDE-19817: ---------------------------------------- Assignee: Jeff Cantrill > Application wizard: v3 application wizard needs to be able to react to chaning connections > ------------------------------------------------------------------------------------------ > > Key: JBIDE-19817 > URL: https://issues.jboss.org/browse/JBIDE-19817 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.3.0.Beta1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > > The current application wizard for OpenShift v3 takes a project in the constructor. It was designed to be launched from the explorer where a v3 connection/project is selected before the wizard is launched. The wizard is not able to react to changing connections. In order for the wizard to be able to get launched from File->New->OpenShift we need the wizard to be able to react to chaning connections. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19759) Application wizard: cannot launch v3 application wizard via File->New->OpenShift

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19759?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-19759 at 5/18/15 5:42 AM: ------------------------------------------------------------------- When launching the application wizard via File->New->OpenShift the connection page is to be shown in the first place. Hitting "Next" then takes the user to either the v2 or the v3 application wizard. The user then can get back to the connection page whenever he wants. This requires the application wizard(s) to be able to react to changing connections. It turns out that the OpenShift v3 application wizard was implemented not being able to react to changing connections. The v3 app wizard needs to be improved in this matter before we can allow users to get to the v3 app wizard via File->New->OpenShift: JBIDE-19817 I thus prepared v3 with the extension point to contribute the application wizard but commented it: {code:title=org.jboss.tools.openshift.ui/plugin.xml}    {code} The connection page will then show an error telling the user that there's no application wizard for 3 connections once the user selects the "OpenShift v3" server type: !no-application-wizard.png! was (Author: adietish): When launching the application wizard via File->New->OpenShift the connection page is to be shown in the first place. Hitting "Next" then takes the user to either the v2 or the v3 application wizard. The user then can get back to the connection page whenever he wants. This requires the application wizard(s) to be able to react to changing connections. It turns out that the OpenShift v3 application wizard was implemented not being able to react to changing connections. The v3 app wizard needs to be improved in this matter before we can allow users to get to the v3 app wizard via File->New->OpenShift I thus prepared v3 with the extension point to contribute the application wizard but commented it: {code:title=org.jboss.tools.openshift.ui/plugin.xml}    {code} The connection page will then show an error telling the user that there's no application wizard for 3 connections once the user selects the "OpenShift v3" server type: !no-application-wizard.png! > Application wizard: cannot launch v3 application wizard via File->New->OpenShift > -------------------------------------------------------------------------------- > > Key: JBIDE-19759 > URL: https://issues.jboss.org/browse/JBIDE-19759 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Reporter: Andre Dietisheim > Assignee: Andre Dietisheim > Fix For: 4.3.0.Beta1 > > Attachments: empty-v2-wizard-page.png, no-application-wizard.png > > > If you launch the application wizard via File->New->OpenShift you can only create OpenShift v2 applications. I should get v3 pages if I select a v3 connection in the 1st wizard page with the connection credentials. Currently if I select a v2 connection I can create v2 applications. If I select a v3 connection the wizard is non-functional. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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 May 2015