June 2015 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-19771) Improve Available detectors dialog

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19771?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-19771: ---------------------------------------- The linked patch was for another issue, and was merged. However, it seems like I didn't push the patch I made to fix this issue. I can't find it on Gerrit, I believe I simply lost it and will have to rewrite it... Anyway, not blocking for Beta1, let's move it to Beta2. > Improve Available detectors dialog > ---------------------------------- > > Key: JBIDE-19771 > URL: https://issues.jboss.org/browse/JBIDE-19771 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: easymport > Affects Versions: 4.3.0.Alpha2 > Reporter: Lucia Jelinkova > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Beta2 > > Attachments: available-detectors.png > > > At the moment, the dialog looks a bit untidy - there is no description what the detectors mean, they are not alphabetically ordered (or does the order mean something?) and they even seem not to be aligned. > Also, the link that opens the dialog is too long - Show available detectors would be enough and the description about what detectors are could go to the dialog. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19771) Improve Available detectors dialog

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19771?page=com.atlassian.jira.plugi... ] Mickael Istria updated JBIDE-19771: ----------------------------------- Fix Version/s: 4.3.0.Beta2 (was: 4.3.0.Beta1) > Improve Available detectors dialog > ---------------------------------- > > Key: JBIDE-19771 > URL: https://issues.jboss.org/browse/JBIDE-19771 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: easymport > Affects Versions: 4.3.0.Alpha2 > Reporter: Lucia Jelinkova > Assignee: Mickael Istria > Priority: Minor > Fix For: 4.3.0.Beta2 > > Attachments: available-detectors.png > > > At the moment, the dialog looks a bit untidy - there is no description what the detectors mean, they are not alphabetically ordered (or does the order mean something?) and they even seem not to be aligned. > Also, the link that opens the dialog is too long - Show available detectors would be enough and the description about what detectors are could go to the dialog. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19733) Easy Import - import is attempted before user presses "finish" - user cannot cancel import if an error occurs

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19733?page=com.atlassian.jira.plugi... ] Lucia Jelinkova closed JBIDE-19733. ----------------------------------- Wizard's design and workflow has been improved since alpha2 release. Verified JBDS 9.0.0.beta1a > Easy Import - import is attempted before user presses "finish" - user cannot cancel import if an error occurs > ------------------------------------------------------------------------------------------------------------- > > Key: JBIDE-19733 > URL: https://issues.jboss.org/browse/JBIDE-19733 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Reporter: Len DiMaggio > Assignee: Mickael Istria > Fix For: 4.3.0.Beta1 > > Attachments: Problems_before_import_completes.png > > > The sequence of user actions and import processing is such that, if an error occurs (for example - as described in JBIDE-19719), the error is reported after the import has been performed. Pressing cancel does not cancel/rollback the import. See attached screenshot. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19728) Easy Import - The first and second screens in the dialog should be merged into one

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19728?page=com.atlassian.jira.plugi... ] Lucia Jelinkova closed JBIDE-19728. ----------------------------------- The wizard's design has been much improved since alpha2 release. Verified in JBDS 9.0.0.beta1a > Easy Import - The first and second screens in the dialog should be merged into one > ---------------------------------------------------------------------------------- > > Key: JBIDE-19728 > URL: https://issues.jboss.org/browse/JBIDE-19728 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: easymport > Affects Versions: 4.3.0.Alpha2 > Reporter: Len DiMaggio > Assignee: Mickael Istria > Fix For: 4.3.0.Beta1 > > Attachments: import_1.png, import_2.png, May11_nightly.png, May11_nightly2.png > > > See the attached screenshots - in the first dialog screen (1/6), the user is presented with a largely blank display. After he/she selects "next" the dialog (2/6) shows the projects that are eligible to be imported. > Why not simply skip the first screen and start with the second? -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19769) Check if the project is already present in the workspace

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19769?page=com.atlassian.jira.plugi... ] Lucia Jelinkova closed JBIDE-19769. ----------------------------------- Closing since it cannot be reproduced > Check if the project is already present in the workspace > -------------------------------------------------------- > > Key: JBIDE-19769 > URL: https://issues.jboss.org/browse/JBIDE-19769 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: easymport > Reporter: Lucia Jelinkova > Assignee: Mickael Istria > Fix For: 4.3.0.Beta1 > > Attachments: existing-projects.png > > > At the moment the project is attempted to import even if it is already in the workspace. It is OK that it is detected but it should be marked as already imported in the wizard table and it should not be imported again. > At the moment, this is logged into Error log: > {code} > org.eclipse.ui.internal.wizards.datatransfer.CouldNotImportProjectException: Could not import project located at /home/ljelinko/workspaces/workspace/RemoteSystemsTempFiles > at org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand.toExistingOrNewProject(OpenFolderCommand.java:294) > at org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand.importProjectAndChildrenRecursively(OpenFolderCommand.java:222) > at org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand.searchAndImportChildrenProjectsRecursively(OpenFolderCommand.java:173) > at org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand.importProjectAndChildrenRecursively(OpenFolderCommand.java:230) > at org.eclipse.ui.internal.wizards.datatransfer.NestedProjectsWizardPage$10.run(NestedProjectsWizardPage.java:258) > at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:119) > Caused by: org.eclipse.core.internal.resources.ResourceException: Resource '/RemoteSystemsTempFiles' already exists. > at org.eclipse.core.internal.resources.Resource.checkDoesNotExist(Resource.java:313) > at org.eclipse.core.internal.resources.Resource.checkDoesNotExist(Resource.java:300) > at org.eclipse.core.internal.resources.Project.assertCreateRequirements(Project.java:51) > at org.eclipse.core.internal.resources.Project.create(Project.java:268) > at org.eclipse.core.internal.resources.Project.create(Project.java:252) > at org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand.createOrImportProject(OpenFolderCommand.java:331) > at org.eclipse.ui.internal.wizards.datatransfer.OpenFolderCommand.toExistingOrNewProject(OpenFolderCommand.java:285) > ... 5 more > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19807) Red Deer site project does not have listed Maven nature

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19807?page=com.atlassian.jira.plugi... ] Lucia Jelinkova closed JBIDE-19807. ----------------------------------- Verified JBDS 9.0.0.beta1a > Red Deer site project does not have listed Maven nature > ------------------------------------------------------- > > Key: JBIDE-19807 > URL: https://issues.jboss.org/browse/JBIDE-19807 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > Assignee: Mickael Istria > Fix For: 4.3.0.Beta1 > > Attachments: site-project.png > > > When I try to import from Red Deer project site, it is listed with no nature at all although it has a pom file. After import the maven nature is present. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19805) Select defaults for folder selection dialog

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19805?page=com.atlassian.jira.plugi... ] Lucia Jelinkova closed JBIDE-19805. ----------------------------------- Verified JBDS 9.0.0.beta1a At first, the workspace directory is selected as default. After first import is the default changed to last imported folder. > Select defaults for folder selection dialog > ------------------------------------------- > > Key: JBIDE-19805 > URL: https://issues.jboss.org/browse/JBIDE-19805 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: easymport > Affects Versions: 4.3.0.Alpha2 > Reporter: Lucia Jelinkova > Assignee: Mickael Istria > Fix For: 4.3.0.Beta1 > > > On the first wizard page, when I hit Browse button I get a dialog to choose the root folder. At the moment, the default path is the installation directory of the running Eclipse instance. I would prefer to initialize the dialog with the current workspace (as it is in the Import Existing Projects into Workspace wizard). > Second issue is that when I choose the folder, import and open the dialog again, the Select root directory text field contains the previous address (this is OK) but when I hit the Browse button it is again initialized with default Eclipse installation directory. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19708) Runtime-detection is not supporting Servlet only distribution of Wildfly 9

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19708?page=com.atlassian.jira.plugi... ] Radim Hopp closed JBIDE-19708. ------------------------------ Verified in JBDS 9.0.0.Beta1a. Closing. > Runtime-detection is not supporting Servlet only distribution of Wildfly 9 > -------------------------------------------------------------------------- > > Key: JBIDE-19708 > URL: https://issues.jboss.org/browse/JBIDE-19708 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: runtime-detection, server > Affects Versions: 4.3.0.Alpha2 > Reporter: Radim Hopp > Assignee: Rob Stryker > Fix For: 4.3.0.Beta1 > > > Runtime detection correctly detects servlet-only distribution of wildfly 9, but fails to add it. Error log is silent. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19774) Visual Editor: XulRunner Engine on Linux is always used if browser was opened before Visual Editor

by Radim Hopp (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19774?page=com.atlassian.jira.plugi... ] Radim Hopp commented on JBIDE-19774: ------------------------------------ That's almost exactly how it behaves ;-) With exception in point 2. xulrunner is used, but no error message is shown. Should I close this one as verified and open new minor jira? > Visual Editor: XulRunner Engine on Linux is always used if browser was opened before Visual Editor > -------------------------------------------------------------------------------------------------- > > Key: JBIDE-19774 > URL: https://issues.jboss.org/browse/JBIDE-19774 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: visual-page-editor-core > Affects Versions: 4.3.0.Alpha2 > Environment: Linux > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Priority: Critical > Fix For: 4.3.0.Beta1 > > > While testing new Central I notice that if Central was opened before visual editor, XulRunner engine is always used. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3460) Line numbers should be shown in text editors by default

by Marián Labuda (JIRA)

[ https://issues.jboss.org/browse/JBDS-3460?page=com.atlassian.jira.plugin.... ] Marián Labuda updated JBDS-3460: -------------------------------- Summary: Line numbers should be shown in text editors by default (was: Line numbers should be shown by default in text editors) > Line numbers should be shown in text editors by default > ------------------------------------------------------- > > Key: JBDS-3460 > URL: https://issues.jboss.org/browse/JBDS-3460 > Project: Developer Studio (JBoss Developer Studio) > Issue Type: Feature Request > Affects Versions: 9.0.0.Beta1 > Reporter: Marián Labuda > > Eclipse use by default shown line numbers for text editors (e.g. Java classes). But our developer studio has line numbers hidden by default. I remember there was some questionnarie some time ago but unfortunately I do not remember results from it. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 11 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 June 2015