August 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-18056) Server adapter: Use same terminology "OpenShift Server Adapter" everywhere

by Marián Labuda (JIRA)

Marián Labuda created JBIDE-18056: ------------------------------------- Summary: Server adapter: Use same terminology "OpenShift Server Adapter" everywhere Key: JBIDE-18056 URL: https://issues.jboss.org/browse/JBIDE-18056 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.2.0.Beta3 Reporter: Marián Labuda We have changed label in New Application wizard to use "server adapter" instead of "server" (see JBIDE-18046). This is desired and already used in documentation. We should use same terminology everywhere: - type in OpenShift Server Adapter properties - type is "OpenShift Server" - tree item in New Server wizard and label before text field on the same wizard page - tree item is "OpenShift Server" and label is "Server name:" - title and description in New Server wizard on the next wizard page - title is "Create an OpenShift Server" and description is "Create an OpenShift Server by choosing your connection, application and deploy project" -- 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 Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18053?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18053: ------------------------------------ Costs include: a) increased disk usage & maintenance (more to mirror and maintain in the TP) b) by including more than 1 of these features (in support of easymock and testng), we open to the door to a lack of uniformity, as you point out So perhaps we only need the single feature. > 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

[JBoss JIRA] (JBIDE-18009) JAX-RS Explorer is broken when the edited file is saved after a delay

by Xavier Coulon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18009?page=com.atlassian.jira.plugi... ] Xavier Coulon resolved JBIDE-18009. ----------------------------------- Resolution: Done [~rrabara], This issue was fixed while working on JBIDE-17796. Can you verify that it's good for you with the next nightly build ? Thanks > JAX-RS Explorer is broken when the edited file is saved after a delay > --------------------------------------------------------------------- > > Key: JBIDE-18009 > URL: https://issues.jboss.org/browse/JBIDE-18009 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: webservices > Affects Versions: 4.2.0.Beta3 > Reporter: Radoslav Rábara > Assignee: Xavier Coulon > Fix For: 4.2.0.CR1 > > Attachments: JBIDE-18009.ogv > > -- 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: --------------------------------------- [~nickboldt] I think it depends on what is currently be used in the code base. Do we have any unit tests that utilize 'testng'? Do we have any unit tests that utilize easymock? It is my opinion for uniformity across the code base we should promote one or the other and limit the feature group. The alternative is to add them since it doesn't 'cost' us anything right? > 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

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17808?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17808: ------------------------------------ +100, I love it. See also JBIDE-18001 for a PR that affects this screenshot, where I've also changed "with Early Access enabled" to "(Early Access Enabled)", and swapped in a more pale yellow colour. PR still waiting for approval there. > 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-18053) Add Powermock to the target platform

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18053?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-18053: ------------------------------------ The PR only includes one feature - for mockito-junit. What about the other three mocks? {code} org.powermock.easymock-junit.feature.feature.group 1.5.4.1 org.powermock.easymock-testng.feature.feature.group 1.5.4.1 org.powermock.mockito-testng.feature.feature.group 1.5.4.1 {code} Would anyone in JBTIS or JBT benefit from those? WDYT, [~adietish], [~xcoulon], [~phantomjinx] (ref: JBIDE-12971, JBIDE-14315 ) > 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

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18053?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18053: ------------------------------- Description: 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: was: 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: If applicable: non-p2 repository: non-p2 ids: > 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

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

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-18053?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-18053: ------------------------------- Description: 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: If applicable: non-p2 repository: non-p2 ids: was: 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: Yes|No Type of dependency: testing List of bundles added/removed: If applicable: non-p2 repository: non-p2 ids: > 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: > 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

[JBoss JIRA] (JBIDE-17682) RSE: allow users to browse application in "Remote Systems" view

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17682?page=com.atlassian.jira.plugi... ] Andre Dietisheim updated JBIDE-17682: ------------------------------------- Fix Version/s: 4.3.x (was: 4.2.x) > RSE: allow users to browse application in "Remote Systems" view > --------------------------------------------------------------- > > Key: JBIDE-17682 > URL: https://issues.jboss.org/browse/JBIDE-17682 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.2.0.Beta2 > Reporter: Andre Dietisheim > Fix For: 4.3.x > > Attachments: cf_eclipse_remote_systems_view.png > > > We should automatically create a mapping in "Remove Systems" view that allows users to browse the file-system of the application within Eclipse. > Cloud Foundry tooling for Eclipse does this and it looks like a pretty nice enhancement: > http://blog.cloudfoundry.org/2012/04/02/introduction-to-cloud-foundry-int... > !cf_eclipse_remote_systems_view.png! -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-14890) Application wizard: Use EGit recursive merge instead of copying git repository

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-14890?page=com.atlassian.jira.plugi... ] Andre Dietisheim commented on JBIDE-14890: ------------------------------------------ bumped to 4.3.x, https://bugs.eclipse.org/bugs/show_bug.cgi?id=372606 is still not fixed. We currently have to push force our "merged" existing project since we copy files around (EGit recursive merge wasnt available when we implemented this feature). This is suboptimal and we should offer our help to fix the EGit issue. > Application wizard: Use EGit recursive merge instead of copying git repository > ------------------------------------------------------------------------------ > > Key: JBIDE-14890 > URL: https://issues.jboss.org/browse/JBIDE-14890 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Affects Versions: 4.1.0.Beta2, 4.1.1.Final > Reporter: Andre Dietisheim > Labels: application_wizard > Fix For: 4.3.x > > Attachments: user-existing-project.png > > > OpenShift tooling is working around missing recursive merge when importing into an existing Project ("use existing") > !user-existing-project.png! > When using the git command line one is told to merge by using the recursive merge startegy: > {code} > git merge -s recursive -X ours foo > {code} > When we created the JBoss Tools for OpenShift there was no recursive merge in EGit/JGit. We therefore worked around it by cloning the OpenShift repository and copying stuff over. > EGit 3.0 introduced the recursive merge strategy and put it to the default that's being used: > https://bugs.eclipse.org/bugs/show_bug.cgi?id=380314#c22 -- 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