February 2015 - jbosstools-issues

[JBoss JIRA] (JBIDE-17497) Servertools plugin heirarchy causes issues for clients

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17497?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-17497: ---------------------------------------- Fix Version/s: 4.3.0.Alpha2 (was: 4.3.0.Alpha1) > Servertools plugin heirarchy causes issues for clients > ------------------------------------------------------ > > Key: JBIDE-17497 > URL: https://issues.jboss.org/browse/JBIDE-17497 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.2.0.Beta2 > Reporter: Rob Stryker > Priority: Critical > Fix For: 4.3.0.Alpha2 > > Attachments: 2014-06-02 19.07.bmml, 2014-06-02 19.07.png > > > The plugin heirarchy of ASTools is better than it used to be, but not good enough for what current consumers of ASTools need it for. > The problem is simple. There are 3 types of clients using ASTools API: > 1) Those who need all of ASTools installed (including server adapter) > 2) Those who only want access to interfaces, to use *if* server adapters is installed (do NOT want as.core force installed) > 3) Those who create their own server adapters, want to use interfaces and some impl classes, but do not want as.core (server adapters) installed. > Those of group 1 are no problem. > Those of group 2 want as.wtp.core and as.wtp.ui to be minimal implementations with very few (near-zero) dependencies > Those of group 3 want as.wtp.core and as.wtp.ui to provide as much functionality as possible, including things like zipping archives, or integration with download runtimes. > An example of group 1 is jbosstools-central. > An example of group 2 is ESB / BPEL > An example of group 3 is FuseIDE > Currently, there are classes in plugins positioned above as.core (ie, depend on as.core) that would be useful to FuseIDE (integration with stacks / runtimes / archives), but pushing these classes down into as.wtp.core / as.wtp.ui would mean the as.wtp.* plugins now require archives / stacks / yaml, and then so does bpel / esb. > There needs to be another set of core/ui plugins for extenders or implementers that do NOT bring in the server adapters. > Alternatively, we could move the server adapters out of as.core / as.ui and into two new higher-level plugins, as.serveradapter.core / as.serveradapter.ui, leaving as.core/as.ui as the new plugins to be extended by fuse-ide. > There are of course other possible solutions, but all possible solutions basically require new plugins with substantial class movement. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3162) Change "jboss-eap" to "JBoss Enterprise Application Platform"

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBDS-3162?page=com.atlassian.jira.plugin.... ] Max Rydahl Andersen updated JBDS-3162: -------------------------------------- Fix Version/s: 9.0.0.Alpha2 (was: 9.0.0.Alpha1) > Change "jboss-eap" to "JBoss Enterprise Application Platform" > ------------------------------------------------------------- > > Key: JBDS-3162 > URL: https://issues.jboss.org/browse/JBDS-3162 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: runtime-detection, server, ui/branding > Reporter: Burr Sutter > Assignee: Rob Stryker > Labels: f2f2014 > Fix For: 9.0.0.Alpha2 > > > When installing JBDS+EAP (same installer), the default name under the Servers tab is "jboss-eap". This is a request to have that default server name changed to "JBoss Enterprise Application Platform". > And the default runtime name to "JBoss EAP Runtime". > http://www.screencast.com/t/POpKcyHjhtlP > http://www.screencast.com/t/LZdFW0rJu0 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18524) Avoid using multiple IDocuments when opening an FTL file

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18524?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-18524: --------------------------------------------- this fell through cracks ... [~dgolovin] / [~ppalaga] is this something that makes sense to put in ? > Avoid using multiple IDocuments when opening an FTL file > -------------------------------------------------------- > > Key: JBIDE-18524 > URL: https://issues.jboss.org/browse/JBIDE-18524 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: freemarker > Affects Versions: 4.2.0.CR2 > Reporter: Peter Palaga > Assignee: Denis Golovin > Priority: Minor > Fix For: 4.2.3.Beta1, 4.3.0.Alpha2 > > > This is a matter of effectiveness and getting in line with what is usual in other plugins: > (1) In the FreeMarker {{Editor}} constructor, we currently create a per-{{Editor}} instance of {{DocumentProvider}}. {{Editor}}s should rather use a single {{DocumentProvider}} hosted in {{Plugin}}. This is how it is done in many other editors, see e.g. {{AntEditor.initializeEditor()}}, {{PropertiesFileEditor.initializeEditor()}}, {{ClassFileEditor()}}, etc. > (2) {{Editor.init(IEditorSite, IEditorInput)}} is called twice from {{FreemarkerMultiPageEditor}} when opening an FTL file. This causes e.g. partitioning twice. Steps to verify: put a breakpoint on {{AbstractTextEditor.init(IEditorSite, IEditorInput)}} and open an FTL file. NOT OK: the breakpoint gets hit twice, ECPECTED: the breakpoint should be visited once only. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18524) Avoid using multiple IDocuments when opening an FTL file

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18524?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen reassigned JBIDE-18524: ------------------------------------------- Assignee: Denis Golovin (was: Peter Palaga) > Avoid using multiple IDocuments when opening an FTL file > -------------------------------------------------------- > > Key: JBIDE-18524 > URL: https://issues.jboss.org/browse/JBIDE-18524 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: freemarker > Affects Versions: 4.2.0.CR2 > Reporter: Peter Palaga > Assignee: Denis Golovin > Priority: Minor > Fix For: 4.2.3.Beta1, 4.3.0.Alpha2 > > > This is a matter of effectiveness and getting in line with what is usual in other plugins: > (1) In the FreeMarker {{Editor}} constructor, we currently create a per-{{Editor}} instance of {{DocumentProvider}}. {{Editor}}s should rather use a single {{DocumentProvider}} hosted in {{Plugin}}. This is how it is done in many other editors, see e.g. {{AntEditor.initializeEditor()}}, {{PropertiesFileEditor.initializeEditor()}}, {{ClassFileEditor()}}, etc. > (2) {{Editor.init(IEditorSite, IEditorInput)}} is called twice from {{FreemarkerMultiPageEditor}} when opening an FTL file. This causes e.g. partitioning twice. Steps to verify: put a breakpoint on {{AbstractTextEditor.init(IEditorSite, IEditorInput)}} and open an FTL file. NOT OK: the breakpoint gets hit twice, ECPECTED: the breakpoint should be visited once only. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18524) Avoid using multiple IDocuments when opening an FTL file

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18524?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18524: ---------------------------------------- Fix Version/s: 4.2.3.Beta1 4.3.0.Alpha2 (was: 4.2.x) (was: 4.3.0.Alpha1) > Avoid using multiple IDocuments when opening an FTL file > -------------------------------------------------------- > > Key: JBIDE-18524 > URL: https://issues.jboss.org/browse/JBIDE-18524 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: freemarker > Affects Versions: 4.2.0.CR2 > Reporter: Peter Palaga > Assignee: Denis Golovin > Priority: Minor > Fix For: 4.2.3.Beta1, 4.3.0.Alpha2 > > > This is a matter of effectiveness and getting in line with what is usual in other plugins: > (1) In the FreeMarker {{Editor}} constructor, we currently create a per-{{Editor}} instance of {{DocumentProvider}}. {{Editor}}s should rather use a single {{DocumentProvider}} hosted in {{Plugin}}. This is how it is done in many other editors, see e.g. {{AntEditor.initializeEditor()}}, {{PropertiesFileEditor.initializeEditor()}}, {{ClassFileEditor()}}, etc. > (2) {{Editor.init(IEditorSite, IEditorInput)}} is called twice from {{FreemarkerMultiPageEditor}} when opening an FTL file. This causes e.g. partitioning twice. Steps to verify: put a breakpoint on {{AbstractTextEditor.init(IEditorSite, IEditorInput)}} and open an FTL file. NOT OK: the breakpoint gets hit twice, ECPECTED: the breakpoint should be visited once only. -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3263) Remove JSF Visual/Source and Preview Tabs

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBDS-3263?page=com.atlassian.jira.plugin.... ] Konstantin Marmalyukov updated JBDS-3263: ----------------------------------------- Fix Version/s: 9.0.0.Beta2 (was: 9.0.0.Alpha1) > Remove JSF Visual/Source and Preview Tabs > ----------------------------------------- > > Key: JBDS-3263 > URL: https://issues.jboss.org/browse/JBDS-3263 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Components: requirements, visual-page-editor-core > Reporter: Burr Sutter > Assignee: Konstantin Marmalyukov > Fix For: 9.0.0.Beta2 > > > Removal of the Visual/Source and Preview tabs, which normally provide an error message as it does not run on 64-bit JVMs. > http://www.screencast.com/t/wettTf6s6cU > http://www.screencast.com/t/zur1sCXmZ -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18755) Autocomplete shows white on white using default RHEL7 theme

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18755?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18755: ---------------------------------------- Fix Version/s: 4.3.0.Alpha2 (was: 4.3.0.Alpha1) > Autocomplete shows white on white using default RHEL7 theme > ----------------------------------------------------------- > > Key: JBIDE-18755 > URL: https://issues.jboss.org/browse/JBIDE-18755 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: upstream > Affects Versions: 4.2.0.Final > Environment: JBDS 8.0.0, RHEL 7 > Reporter: Karel Piwko > Fix For: 4.3.0.Alpha2 > > > I can't see code completion in Eclipse while using default Adawaita theme in RHEL7. See attached screenshot > Tracked in upstream by https://bugs.eclipse.org/bugs/show_bug.cgi?id=439884 -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19252) merge v3 branch into master

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19252?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-19252: ------------------------------------- Git Pull Request: https://github.com/jbosstools/jbosstools-openshift/pull/540 (was: https://github.com/jbosstools/jbosstools-openshift/pull/539) > merge v3 branch into master > --------------------------- > > Key: JBIDE-19252 > URL: https://issues.jboss.org/browse/JBIDE-19252 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Fix For: 4.3.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19252) merge v3 branch into master

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19252?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-19252: ------------------------------------------ merged and pushed to upstream/master. > merge v3 branch into master > --------------------------- > > Key: JBIDE-19252 > URL: https://issues.jboss.org/browse/JBIDE-19252 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.Alpha1 > Reporter: Andre Dietisheim > Assignee: Jeff Cantrill > Fix For: 4.3.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18053) Add Powermock to the target platform

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18053?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen updated JBIDE-18053: ---------------------------------------- Fix Version/s: 4.3.0.Alpha2 (was: 4.3.0.Alpha1) > Add Powermock to the target platform > ------------------------------------ > > Key: JBIDE-18053 > URL: https://issues.jboss.org/browse/JBIDE-18053 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: build > Affects Versions: 4.2.x > Reporter: Jeff Cantrill > Assignee: Nick Boldt > Fix For: 4.3.0.Alpha2 > > > *Reason:* To improving testing by allowing the stubbing of scenerios like "new File(path).exists()" which require bytecode modifications in order to accomplish. Example of intended use: https://gist.github.com/jcantrill/fd83c27d3fc542742ec7 > *License and owner:* Apache 2.0 / https://github.com/jayway > *Original p2 repo:* http://powermock-osgi.googlecode.com/svn/updateSite/1.5.4.1/ > *JBoss mirror:* http://download.jboss.org/jbosstools/updates/requirements/powermock/1.5.4.1/ > *Sources:* https://code.google.com/p/powermock-osgi/ , http://powermock-osgi.googlecode.com/svn/trunk/ > *Affected projects:* OpenShift tests > *Include in JBDS:* No > *Type of dependency:* testing > *List of bundles added/removed:* > {code} > + <unit id="org.powermock.mockito-junit.feature.feature.group" version="1.5.4.1"/> > + <unit id="org.objenesis" version="2.1.0"/> > + <unit id="javassist" version="3.18.1.GA"/> > {code} > *p2diff report:* > {code} > mistria@mistria--rh:~/git/jbosstools-target-platforms/jbosstools/multiple$ ~/git/p2diff/org.eclipse.equinox.p2.example.p2diff.packaging/target/products/org.eclipse.equinox.p2.example.p2diff.product/linux/gtk/x86_64/p2diff http://download.jboss.org/jbosstools/targetplatforms/jbosstoolstarget/4.4... file:$(pwd)/target/jbosstools-multiple.target.repo/ > > org.mockito.mockito-core [1.9.5] > > javassist [3.18.1.GA] > > org.powermock.powermock-api-support [1.5.4] > > org.powermock.powermock-reflect [1.5.4] > > org.powermock.powermock-api-mockito [1.5.4] > > org.powermock.powermock-module-junit4-common [1.5.4] > > org.powermock.powermock-module-junit4 [1.5.4] > > org.powermock.powermock-core [1.5.4] > > org.objenesis [2.1.0] > === Summary === > file:/home/mistria/git/jbosstools-target-platforms/jbosstools/multiple/target/jbosstools-multiple.target.repo/ contains 9 unique IUs > {code} -- This message was sent by Atlassian JIRA (v6.3.11#6341)

11 years, 4 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 February 2015