August 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18060) Copy/Past hot keys are not working for resource bundle editor

by Denis Golovin (JIRA)

Denis Golovin created JBIDE-18060: ------------------------------------- Summary: Copy/Past hot keys are not working for resource bundle editor Key: JBIDE-18060 URL: https://issues.jboss.org/browse/JBIDE-18060 Project: Tools (JBoss Tools) Issue Type: Bug Components: common/jst/core Affects Versions: 4.2.0.Beta3 Reporter: Denis Golovin Inside Properties tab when editing name/value in cell editor hot keys for copy/paste don't work. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18059) Forge branding problems in Eclipse Installation Details dialog

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18059?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-18059: ---------------------------------- Fix Version/s: 4.2.0.CR1 > Forge branding problems in Eclipse Installation Details dialog > -------------------------------------------------------------- > > Key: JBIDE-18059 > URL: https://issues.jboss.org/browse/JBIDE-18059 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.Beta3 > Reporter: Denis Golovin > Fix For: 4.2.0.CR1 > > Attachments: aesh-provider.png, forge-provider.png > > > ProviderName and FeatureName are not set for forge.m2e.feature in Installation Details->'Features' tab > !forge-provider.png! > aesh plug-in > !aesh-provider.png! -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18059) Forge branding problems in Eclipse Installation Details dialog

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18059?page=com.atlassian.jira.plugi... ] Denis Golovin reassigned JBIDE-18059: ------------------------------------- Assignee: Denis Golovin > Forge branding problems in Eclipse Installation Details dialog > -------------------------------------------------------------- > > Key: JBIDE-18059 > URL: https://issues.jboss.org/browse/JBIDE-18059 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.Beta3 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.2.0.CR1 > > Attachments: aesh-provider.png, forge-provider.png > > > ProviderName and FeatureName are not set for forge.m2e.feature in Installation Details->'Features' tab > !forge-provider.png! > aesh plug-in > !aesh-provider.png! -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-16358) "jboss-client_6_0.xsd" is missing in XML catalog

by Wolfgang Knauf (JIRA)

[ https://issues.jboss.org/browse/JBIDE-16358?page=com.atlassian.jira.plugi... ] Wolfgang Knauf commented on JBIDE-16358: ---------------------------------------- I can confirm that this works with 4.2.0Beta3. Thank you, good work! About the validation error with jboss-app.xml: I forgot that I filed a similar error last year for jboss-web.xml ;-): #JBMETA-363 > "jboss-client_6_0.xsd" is missing in XML catalog > ------------------------------------------------ > > Key: JBIDE-16358 > URL: https://issues.jboss.org/browse/JBIDE-16358 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.1.1.Final > Reporter: Wolfgang Knauf > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.2.0.Beta2 > > Attachments: jboss_client_catalog.png, jboss_client_wizard.png > > > See subject -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17808) Identify which installed IUs are from Early Access vs. supported/tested versions

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17808?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-17808: ---------------------------------------- Those are not necessarily features (they can be any IU), so they may not have necessary branding info, copyright, icon and so on... But for sure, in case there is, we can show more details. The "Features" section is indeed what I'd like the page to look like, and in case IU is a bundle, it would simply show a <no branding available> text. > Identify which installed IUs are from Early Access vs. supported/tested versions > -------------------------------------------------------------------------------- > > Key: JBIDE-17808 > URL: https://issues.jboss.org/browse/JBIDE-17808 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: central > Reporter: Nick Boldt > Assignee: Mickael Istria > Labels: documentation > Fix For: 4.2.0.CR1 > > Attachments: JBIDE17808.jpeg > > > [~maxandersen] brought up a good point on a call today: > we have no way from within JBDS of identifying which installed IUs were installed from Early Access vs. those what were installed from Central or another "supported" location. > Thus we need some sort of UI to list installed IUs that are "Early Access". > This could be... (brainstorming now): > * a text file with the list of things installed from Early Access (features and plugins) > * a set of asterisks added to the Help > About dialogs when browsing for installed features / plugins > * a way to filter the plugin view (Help > About) to show only EA content (or exclude it) > * ... ? -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18059) Forge branding problems in Eclipse Installation Details dialog

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18059?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-18059: ---------------------------------- Summary: Forge branding problems in Eclipse Installation Details dialog (was: ProviderName and FeatureName are not set for forge.m2e.feature in Installation Details->'Features' tab) > Forge branding problems in Eclipse Installation Details dialog > -------------------------------------------------------------- > > Key: JBIDE-18059 > URL: https://issues.jboss.org/browse/JBIDE-18059 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.Beta3 > Reporter: Denis Golovin > Attachments: aesh-provider.png, forge-provider.png > > > !forge-provider.png! -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18059) Forge branding problems in Eclipse Installation Details dialog

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18059?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-18059: ---------------------------------- Description: ProviderName and FeatureName are not set for forge.m2e.feature in Installation Details->'Features' tab !forge-provider.png! aesh plug-in !aesh-provider.png! was:!forge-provider.png! > Forge branding problems in Eclipse Installation Details dialog > -------------------------------------------------------------- > > Key: JBIDE-18059 > URL: https://issues.jboss.org/browse/JBIDE-18059 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.Beta3 > Reporter: Denis Golovin > Attachments: aesh-provider.png, forge-provider.png > > > ProviderName and FeatureName are not set for forge.m2e.feature in Installation Details->'Features' tab > !forge-provider.png! > aesh plug-in > !aesh-provider.png! -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18059) Forge branding problems in Eclipse Installation Details dialog

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18059?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-18059: ---------------------------------- Attachment: aesh-provider.png > Forge branding problems in Eclipse Installation Details dialog > -------------------------------------------------------------- > > Key: JBIDE-18059 > URL: https://issues.jboss.org/browse/JBIDE-18059 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.Beta3 > Reporter: Denis Golovin > Attachments: aesh-provider.png, forge-provider.png > > > ProviderName and FeatureName are not set for forge.m2e.feature in Installation Details->'Features' tab > !forge-provider.png! > aesh plug-in > !aesh-provider.png! -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18059) ProviderName and FeatureName are not set for forge.m2e.feature in Installation Details->'Features' tab

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18059?page=com.atlassian.jira.plugi... ] Denis Golovin updated JBIDE-18059: ---------------------------------- Summary: ProviderName and FeatureName are not set for forge.m2e.feature in Installation Details->'Features' tab (was: ProviderName and FeatureName are not set for forge.m2e.feature) > ProviderName and FeatureName are not set for forge.m2e.feature in Installation Details->'Features' tab > ------------------------------------------------------------------------------------------------------ > > Key: JBIDE-18059 > URL: https://issues.jboss.org/browse/JBIDE-18059 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: forge > Affects Versions: 4.2.0.Beta3 > Reporter: Denis Golovin > Attachments: forge-provider.png > > > !forge-provider.png! -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

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

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18053?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-18053: --------------------------------------- [~phantomjinx] [~adietish] I don't really want to preach too extensively about unit testing best practices, but generally it is most desirable to isolate your test code from interface points which you have limited control (e.g. the file system, network) or leave behind undesirable artifacts or require you to clean-up. Unit tests are supposed to allow you to quickly test code without dependency on such interfaces. Powermock extends the great features of mockito by allowing stubbing of constructor methods without forcing you to introduce an interface or factory method; these kind of classes, in this specific case, would just be extraneous. Powermock also allows you to stub static methods. We, IMO, should prefer the use of mocking and stubbing in unit tests where appropriate over relying on OS functions; thats what integration tests are for. > 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.2.0.CR1 > > > 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 repo: https://github.com/jayway/powermock > JBoss mirror: Unknown > Sources: Unknown > Affected projects: > 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} > If applicable: > non-p2 repository: > non-p2 ids: -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 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 August 2014