July 2014 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-17957) Change error logged when no maven profile is selected

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17957?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-17957: ---------------------------------- Fix Version/s: 4.2.0.CR1 > Change error logged when no maven profile is selected > ----------------------------------------------------- > > Key: JBIDE-17957 > URL: https://issues.jboss.org/browse/JBIDE-17957 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: testing-tools > Affects Versions: 4.2.0.Beta3 > Reporter: Lucia Jelinkova > Assignee: Snjezana Peco > Fix For: 4.2.0.CR1 > > > When I try to run a test on arquillian project that has no maven profile selected and I choose to open the launch configuration, the following error is logged in error log: > {code} > Arquillian tests are missing an implementation of DeploymentContainer on the project build path. Do you want to configure it? > {code} > - I do not think the question is appropriate for error log message > - I do not think this error should be logged when opening launcher since the user is about to configure what he needs. > So please either remove this from error log or log it when user press OK button in launcher. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17956) Add progress bar to Add Arquillian profiles dialog

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17956?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-17956: ---------------------------------- Affects Version/s: 4.2.0.Beta3 > Add progress bar to Add Arquillian profiles dialog > -------------------------------------------------- > > Key: JBIDE-17956 > URL: https://issues.jboss.org/browse/JBIDE-17956 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: testing-tools > Affects Versions: 4.2.0.Beta3 > Reporter: Lucia Jelinkova > Assignee: Snjezana Peco > Priority: Minor > > In Add Arquillian profiles dialog, when I select all profiles and press OK, it takes quite a long time to finish the task. There should be a progress bar in this case. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17808?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17808: --------------------------------------------- no, the discovery would only have the *current* list of EA thus it would not catch them all. We talked about starting by just having a simple properties file with IU=<comma separated osgi version ranges> to mark what is/was early access. updating that could be automated over time. > 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 > Fix For: 4.2.0.CR1 > > > [~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)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-18003) Forge quick access menu loses focus and closes when executed in the context of a cheatsheet command/action

by Vineet Reynolds (JIRA)

Vineet Reynolds created JBIDE-18003: --------------------------------------- Summary: Forge quick access menu loses focus and closes when executed in the context of a cheatsheet command/action Key: JBIDE-18003 URL: https://issues.jboss.org/browse/JBIDE-18003 Project: Tools (JBoss Tools) Issue Type: Bug Components: forge Reporter: Vineet Reynolds Priority: Minor When I add the org.jboss.tools.forge.ui.command.runForgeCommand command to an Eclipse cheatsheet and execute it, the quick access menu is launched, but immediately closes when the cheatsheet regain focus. We should find a way to retain focus in the quick access menu so that it wont be closed and will continue to receive user input. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17986) Bundled version of m2e-mavenarchiver is broken

by Rich DiCroce (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17986?page=com.atlassian.jira.plugi... ] Rich DiCroce commented on JBIDE-17986: -------------------------------------- [~maxandersen] I downloaded it from the site linked in the description of this issue. > Bundled version of m2e-mavenarchiver is broken > ---------------------------------------------- > > Key: JBIDE-17986 > URL: https://issues.jboss.org/browse/JBIDE-17986 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, discovery, maven, target-platform > Affects Versions: 4.2.0.Beta3 > Reporter: Rich DiCroce > Assignee: Nick Boldt > Fix For: 4.2.0.CR1 > > > The version of m2e-mavenarchiver that is bundled in JBoss Tools seems to be broken. I was not getting any descriptors generated. Upgrading to the latest version fixes the problem. See http://repository.takari.io:8081/nexus/content/sites/m2e.extras/m2eclipse... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17964) add keywords to JBoss Tools and Developer Studio marketplace entries for Fuse/Camel/Fabric

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17964?page=com.atlassian.jira.plugi... ] Nick Boldt commented on JBIDE-17964: ------------------------------------ >From jiralint: "Problem: Unresolved issue with already released fix version - This issue is set to be fixed in an already released version. Please triage." So I've set this to 4.1.x for now. Because 4.1.2.Final IS a valid fixversion (for this rare case only), but jiralint correctly disagrees. > add keywords to JBoss Tools and Developer Studio marketplace entries for Fuse/Camel/Fabric > ------------------------------------------------------------------------------------------ > > Key: JBIDE-17964 > URL: https://issues.jboss.org/browse/JBIDE-17964 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: marketplace > Affects Versions: 4.1.2.Final > Reporter: Lars Heinemann > Assignee: Nick Boldt > Fix For: 4.1.x > > > Currently when people search the marketplace for Fuse, Fabric, Fabric8 or Camel they don't find JBoss products. We should add those keywords to JBT and JBDS. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17964) add keywords to JBoss Tools and Developer Studio marketplace entries for Fuse/Camel/Fabric

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17964?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-17964: ------------------------------- Fix Version/s: 4.1.x (was: 4.1.2.Final) > add keywords to JBoss Tools and Developer Studio marketplace entries for Fuse/Camel/Fabric > ------------------------------------------------------------------------------------------ > > Key: JBIDE-17964 > URL: https://issues.jboss.org/browse/JBIDE-17964 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: marketplace > Affects Versions: 4.1.2.Final > Reporter: Lars Heinemann > Assignee: Nick Boldt > Fix For: 4.1.x > > > Currently when people search the marketplace for Fuse, Fabric, Fabric8 or Camel they don't find JBoss products. We should add those keywords to JBT and JBDS. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17986) Bundled version of m2e-mavenarchiver is broken

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17986?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-17986: ------------------------------- Component/s: central > Bundled version of m2e-mavenarchiver is broken > ---------------------------------------------- > > Key: JBIDE-17986 > URL: https://issues.jboss.org/browse/JBIDE-17986 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central, discovery, maven, target-platform > Affects Versions: 4.2.0.Beta3 > Reporter: Rich DiCroce > Assignee: Nick Boldt > Fix For: 4.2.0.CR1 > > > The version of m2e-mavenarchiver that is bundled in JBoss Tools seems to be broken. I was not getting any descriptors generated. Upgrading to the latest version fixes the problem. See http://repository.takari.io:8081/nexus/content/sites/m2e.extras/m2eclipse... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17986) Bundled version of m2e-mavenarchiver is broken

by Nick Boldt (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17986?page=com.atlassian.jira.plugi... ] Nick Boldt updated JBIDE-17986: ------------------------------- Component/s: discovery maven target-platform > Bundled version of m2e-mavenarchiver is broken > ---------------------------------------------- > > Key: JBIDE-17986 > URL: https://issues.jboss.org/browse/JBIDE-17986 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: discovery, maven, target-platform > Affects Versions: 4.2.0.Beta3 > Reporter: Rich DiCroce > Assignee: Nick Boldt > Fix For: 4.2.0.CR1 > > > The version of m2e-mavenarchiver that is bundled in JBoss Tools seems to be broken. I was not getting any descriptors generated. Upgrading to the latest version fixes the problem. See http://repository.takari.io:8081/nexus/content/sites/m2e.extras/m2eclipse... -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

[JBoss JIRA] (JBIDE-17977) Server adapter: "configure markers" missing in server adapter context menu

by Andre Dietisheim (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17977?page=com.atlassian.jira.plugi... ] Andre Dietisheim edited comment on JBIDE-17977 at 7/30/14 10:54 AM: -------------------------------------------------------------------- I added the "Configure Markers" item to the context menu of the server adapter, right below "Delete Application" in it's own separator: !server-adapter-configure-markers.png! was (Author: adietish): I added the "Configure Markers" item to the context menu of the server adapter, right below "Delete Application" in it's own separator. > Server adapter: "configure markers" missing in server adapter context menu > -------------------------------------------------------------------------- > > Key: JBIDE-17977 > URL: https://issues.jboss.org/browse/JBIDE-17977 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: openshift > Affects Versions: 4.2.0.Beta3 > Reporter: Max Rydahl Andersen > Labels: server_adapter > Fix For: 4.2.0.CR1 > > Attachments: server-adapter-configure-markers.png > > > configure markers available from the project context menu should also be accessible from server context menu. > seem to have been missed when we aligned the context markers. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

10 years, 1 month

1
0
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues July 2014