July 2014 - jbosstools-issues - Jboss List Archives

[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: ------------------------------------------- I'm +1 on having one updatesite url for users. Mostly interested in reviewing how they are structured and how the result will look like for users. Can we make a test of this before making it live on the live system please ? > 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 > > > 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.2.6#6264)

11 years, 8 months

1
0
0 / 0

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

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17986?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-17986: --------------------------------------------- [~nickboldt] yes i know we got the version that is broken from Luna. Thats why I wanted to clarify it is not jbosstools that bundles it (we mirror it yes, but it comes from eclipse luna) [~rcd] can you provide example project where you are seeing the failures ? > 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)

11 years, 8 months

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)

[ https://issues.jboss.org/browse/JBIDE-18003?page=com.atlassian.jira.plugi... ] Vineet Reynolds updated JBIDE-18003: ------------------------------------ Affects Version/s: 4.2.0.Beta3 > 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 > Affects Versions: 4.2.0.Beta3 > 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)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-17825) Cannot initialize JBoss DND

by Snjezana Peco (JIRA)

[ https://issues.jboss.org/browse/JBIDE-17825?page=com.atlassian.jira.plugi... ] Snjezana Peco updated JBIDE-17825: ---------------------------------- Fix Version/s: 4.2.0.CR1 > Cannot initialize JBoss DND > --------------------------- > > Key: JBIDE-17825 > URL: https://issues.jboss.org/browse/JBIDE-17825 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: central > Affects Versions: 4.2.0.Beta3 > Environment: Fedora 20, > Reporter: Radim Hopp > Assignee: Snjezana Peco > Fix For: 4.2.0.CR1 > > > Almost allways (if not allways), when Central is started on fresh forkspace, "Cannot initialize JBoss DND" error appears in error log. > I don't know what's causing this message, but Drag'n'Drop installation from Central works. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-18004) Support launch/execution of specific Forge UICommands or UIWizards from Eclipse cheat sheets

by Vineet Reynolds (JIRA)

Vineet Reynolds created JBIDE-18004: --------------------------------------- Summary: Support launch/execution of specific Forge UICommands or UIWizards from Eclipse cheat sheets Key: JBIDE-18004 URL: https://issues.jboss.org/browse/JBIDE-18004 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: forge Affects Versions: 4.2.0.Beta3 Reporter: Vineet Reynolds Priority: Minor The name of the command to be executed should be accepted as a parameter so that it can be directly launched from an Eclipse cheatsheet, instead of merely guiding the user to the quick access menu. -- This message was sent by Atlassian JIRA (v6.2.6#6264)

11 years, 8 months

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: ---------------------------------- Fix Version/s: 4.2.0.CR1 > 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 > Fix For: 4.2.0.CR1 > > > 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)

11 years, 8 months

1
0
0 / 0

[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)

11 years, 8 months

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)

11 years, 8 months

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)

11 years, 8 months

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)

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 July 2014