August 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18129) Ionic content assist is available for HTML4 files w/o ionic JS links

by Alexey Kazakov (JIRA)

Alexey Kazakov created JBIDE-18129: -------------------------------------- Summary: Ionic content assist is available for HTML4 files w/o ionic JS links Key: JBIDE-18129 URL: https://issues.jboss.org/browse/JBIDE-18129 Project: Tools (JBoss Tools) Issue Type: Bug Components: jsp/jsf/xml/html source editing Affects Versions: 4.2.0.CR1 Reporter: Alexey Kazakov Assignee: Alexey Kazakov Fix For: 4.2.0.CR1 1. Create the following HTML file: {code} <html> <body> </body> </html> {code} 2. FAILURE: Content assist suggests <ion-*> tags for this file but this file doesn't have any ionic JS links. This file is not an AngularJS template file either. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17990) Organize imports does not work for Maven dependencies

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17990?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-17990: --------------------------------------- It would be also good if you could start the org.eclipse.m2e.jdt plugin as follows: - open the Console view - click the view's "Open Console" menu and select "Host OSGi Console" - enter start org.eclipse.m2e.jdt - if there is an output, copy it > Organize imports does not work for Maven dependencies > ----------------------------------------------------- > > Key: JBIDE-17990 > URL: https://issues.jboss.org/browse/JBIDE-17990 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, upstream > Affects Versions: 4.2.0.Beta3 > Environment: Oracle JDK 1.8.0_05, Eclipse Luna > Reporter: Harald Wellmann > Assignee: Snjezana Peco > Fix For: 4.2.0.CR1 > > > After upgrading from 4.2.0.Beta2 to Beta3 to test the fix for JBIDE-17724, Organize Imports is broken in my workspace. More precisely, I'm referring to the capability of finding the package a class lives in and generating the {{import}} directive with the FQCN. > The corresponding Quick Fix is also broken. > It only works for class names from sources in the workspace, it no longer works for class names from a Maven dependency in the local repository. > This is even worse than JBIDE-17724, I'll have to revert to Beta2. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18128) Jboss Eclipse Luna plugin doesn't deploy all .class

by Alexey Kazakov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18128?page=com.atlassian.jira.plugi... ] Alexey Kazakov updated JBIDE-18128: ----------------------------------- Component/s: server > Jboss Eclipse Luna plugin doesn't deploy all .class > --------------------------------------------------- > > Key: JBIDE-18128 > URL: https://issues.jboss.org/browse/JBIDE-18128 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta3 > Reporter: fede pia > Priority: Blocker > > The problem I'm facing is that when I run/debug my aplication from Server view in Eclipse the jboss plugin doesn't deploy all the .class files, thus I get ClassNotFoundException. > I've tried cleaning the project, cleaning jboss, remove temporaries but nothing works. The not found classes are random. > For Eclipse 4.3 everything works fine, although this issue usually happens but I can solve it with a Project -> Clean > As a context, I've installed Eclipse Luna (also tried STS 3.6) and added Jboss Tools plugin 4.2.0 Beta 3 (I've installed only Jboss AS component). The jboss servers I tested were JBoss 7.1 and Wildfly 8.1. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18128) Jboss Eclipse Luna plugin doesn't deploy all .class

by fede pia (JIRA)

fede pia created JBIDE-18128: -------------------------------- Summary: Jboss Eclipse Luna plugin doesn't deploy all .class Key: JBIDE-18128 URL: https://issues.jboss.org/browse/JBIDE-18128 Project: Tools (JBoss Tools) Issue Type: Bug Affects Versions: 4.2.0.Beta3 Reporter: fede pia Priority: Blocker The problem I'm facing is that when I run/debug my aplication from Server view in Eclipse the jboss plugin doesn't deploy all the .class files, thus I get ClassNotFoundException. I've tried cleaning the project, cleaning jboss, remove temporaries but nothing works. The not found classes are random. For Eclipse 4.3 everything works fine, although this issue usually happens but I can solve it with a Project -> Clean As a context, I've installed Eclipse Luna (also tried STS 3.6) and added Jboss Tools plugin 4.2.0 Beta 3 (I've installed only Jboss AS component). The jboss servers I tested were JBoss 7.1 and Wildfly 8.1. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3086) Change Central Discovery URLs?

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3086?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen commented on JBDS-3086: ------------------------------------------- just to be sure i'm not misunderstanding. You write: "Uncategorized view in JBDS won't change, since the TP contents are not categorized" I assume you meant to write *Categorized* view in JBDS won't change, right ? And when you say TP here - which TP do you mean ? All of them ? > Change Central Discovery URLs? > ------------------------------ > > Key: JBDS-3086 > URL: https://issues.jboss.org/browse/JBDS-3086 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Task > Security Level: Public(Everyone can see) > Components: build, discovery, updatesite > Affects Versions: 8.0.0.Beta3 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 8.0.0.CR1 > > Attachments: jbds3086_no-change-to-categorized-view.png, jbds3086_uncategorized-view-sample1.png, jbds3086_uncategorized-view-sample2.png > > > Today, the Central discovery plugin for JBDS is points to this URL: > <site>/central/core/ > and for Early Access discovery: > <site>/central/earlyaccess/ > However, Max has suggested that we simplify the first, and change the second. > I believe he wants something like this: > https://devstudio.jboss.com/updates/8.0-staging/ > https://devstudio.jboss.com/updates/8.0-development > https://devstudio.jboss.com/updates/8.0/ > and > https://devstudio.jboss.com/earlyaccess/8.0-staging/ > https://devstudio.jboss.com/earlyaccess/8.0-development/ > https://devstudio.jboss.com/earlyaccess/8.0/ > What do people think about this proposed change? > [~mickael_istria] [~maxandersen] [~dgolovin] -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18105) generate jbtearlyaccess.properties from jbtearlyaccess-multiple.target

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18105?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-18105 at 8/26/14 5:59 PM: ------------------------------------------------------------- I wonder if instead of creating something new (parse .target into .properties), we can extend org.jboss.tools.tycho.sitegenerator.GenerateRepositoryFacadeMojo#generateSiteProperties() to work for uncategorized features, or more simply, just call http://download.jboss.org/jbosstools/updates/scripted-installation/direct... #list.feature.groups to pull the whole list of IUs and dump that to a file, like this: {code:title=https://raw.githubusercontent.com/jbosstools/jbosstools-build-ci/master/util/installFromTarget.sh} ${ECLIPSEEXEC} -consolelog -nosplash -data ${WORKSPACE}/data -application org.eclipse.ant.core.antRunner -f ${WORKSPACE}/director.xml -DtargetDir=${ECLIPSE} \ list.feature.groups -Doutput=${WORKSPACE}/feature.group.list.properties -DsourceSites=${INSTALL_PLAN} -Dexec=${ECLIPSEEXEC} {code} [~mickael_istria], WDYT? Maven or Ant ftw? was (Author: nickboldt): I wonder if instead of creating something new (parse .target into .properties), we can extend org.jboss.tools.tycho.sitegenerator.GenerateRepositoryFacadeMojo#generateSiteProperties() to work for uncategorized features, or repurpose http://download.jboss.org/jbosstools/updates/scripted-installation/direct... #list.feature.groups to pull the whole list of IUs and dump that to a file? [~mickael_istria], WDYT? Maven or Ant ftw? > generate jbtearlyaccess.properties from jbtearlyaccess-multiple.target > ---------------------------------------------------------------------- > > Key: JBIDE-18105 > URL: https://issues.jboss.org/browse/JBIDE-18105 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, central, discovery > Affects Versions: 4.2.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.0.CR1 > > > Since the JBT EA .target file already contains all the IUs which are considered early access (and their dependencies, which are sometimes also EA, like Tern) we can generate the list of EA features from that .target file, and maintain an ongoing [min,max] version range of what's considered early access. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18105) generate jbtearlyaccess.properties from jbtearlyaccess-multiple.target

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18105?page=com.atlassian.jira.plugi... ] Nick Boldt edited comment on JBIDE-18105 at 8/26/14 5:57 PM: ------------------------------------------------------------- I wonder if instead of creating something new (parse .target into .properties), we can extend org.jboss.tools.tycho.sitegenerator.GenerateRepositoryFacadeMojo#generateSiteProperties() to work for uncategorized features, or repurpose http://download.jboss.org/jbosstools/updates/scripted-installation/direct... #list.feature.groups to pull the whole list of IUs and dump that to a file? [~mickael_istria], WDYT? Maven or Ant ftw? was (Author: nickboldt): I wonder if instead of creating something new (parse .target into .properties), we can extend org.jboss.tools.tycho.sitegenerator.GenerateRepositoryFacadeMojo#generateSiteProperties() to work for uncategorized features, or repurpose http://download.jboss.org/jbosstools/updates/scripted-installation/direct... #list.feature.groups to pull the whole list of IUs and dump that to a file? > generate jbtearlyaccess.properties from jbtearlyaccess-multiple.target > ---------------------------------------------------------------------- > > Key: JBIDE-18105 > URL: https://issues.jboss.org/browse/JBIDE-18105 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, central, discovery > Affects Versions: 4.2.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.0.CR1 > > > Since the JBT EA .target file already contains all the IUs which are considered early access (and their dependencies, which are sometimes also EA, like Tern) we can generate the list of EA features from that .target file, and maintain an ongoing [min,max] version range of what's considered early access. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18105) generate jbtearlyaccess.properties from jbtearlyaccess-multiple.target

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18105?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18105: ------------------------------------ I wonder if instead of creating something new (parse .target into .properties), we can extend org.jboss.tools.tycho.sitegenerator.GenerateRepositoryFacadeMojo#generateSiteProperties() to work for uncategorized features, or repurpose http://download.jboss.org/jbosstools/updates/scripted-installation/direct... #list.feature.groups to pull the whole list of IUs and dump that to a file? > generate jbtearlyaccess.properties from jbtearlyaccess-multiple.target > ---------------------------------------------------------------------- > > Key: JBIDE-18105 > URL: https://issues.jboss.org/browse/JBIDE-18105 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, central, discovery > Affects Versions: 4.2.0.CR1 > Reporter: Nick Boldt > Fix For: 4.2.0.CR1 > > > Since the JBT EA .target file already contains all the IUs which are considered early access (and their dependencies, which are sometimes also EA, like Tern) we can generate the list of EA features from that .target file, and maintain an ongoing [min,max] version range of what's considered early access. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18105) generate jbtearlyaccess.properties from jbtearlyaccess-multiple.target

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18105?page=com.atlassian.jira.plugi... ] Nick Boldt reassigned JBIDE-18105: ---------------------------------- Assignee: Nick Boldt > generate jbtearlyaccess.properties from jbtearlyaccess-multiple.target > ---------------------------------------------------------------------- > > Key: JBIDE-18105 > URL: https://issues.jboss.org/browse/JBIDE-18105 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: build, central, discovery > Affects Versions: 4.2.0.CR1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.2.0.CR1 > > > Since the JBT EA .target file already contains all the IUs which are considered early access (and their dependencies, which are sometimes also EA, like Tern) we can generate the list of EA features from that .target file, and maintain an ongoing [min,max] version range of what's considered early access. -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16877) Application wizard: Domain- and gear-combo are too small, selected item is not fully visible

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16877?page=com.atlassian.jira.plugi... ] Snjezana Peco commented on JBIDE-16877: --------------------------------------- I have already fixed this issue. The following is the mesage I sent to the jbosstools-dev mailing list: "The issue can be reproduced on F19, but can't on Ubuntu 13.10. I have tried to create a pure SWT test, but that isn't easy because the issue disappears when resizing (packing) the dialog/shell. It seems that the issue isn't related to Eclipse, but to GTK. Michelle, If you resize the New OpenShift Application wizard dialog, the issue will disappear. https://github.com/jbosstools/jbosstools-openshift/pull/378 fixes the issue." I have rebased the patch. > Application wizard: Domain- and gear-combo are too small, selected item is not fully visible > -------------------------------------------------------------------------------------------- > > Key: JBIDE-16877 > URL: https://issues.jboss.org/browse/JBIDE-16877 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta1 > Environment: Fedora 19, 64-bit, java version "1.7.0_51", OpenJDK Runtime Environment (fedora-2.4.5.0.fc19-x86_64 u51-b31) GTK3 > Reporter: Michelle Murray > Assignee: Snjezana Peco > Labels: application_wizard, gtk3, upstream > Fix For: 4.2.0.CR1 > > Attachments: OpenShift_newpg2.png > > Original Estimate: 2 hours > Remaining Estimate: 2 hours > > The default wizard window size obscures fields, Domain and Gear profile. > Work around: If I click Advanced then Embedded Cartridges pane shrinks vertically and the whole of the Domain and Gear profile fields can be seen. > Is there a way to ensure the whole of the Domain and Gear profile fields can be seen in the default view? Perhaps by reducing the size of the Embedded Cartridges pane? > !OpenShift_newpg2.png! -- This message was sent by Atlassian JIRA (v6.3.1#6329)

11 years, 8 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 August 2014