May 2015 - jbosstools-issues - Jboss List Archives

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

by Lucia Jelinkova (JIRA)

Lucia Jelinkova created JBIDE-19805: --------------------------------------- Summary: 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 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19804) Select folder dialog problem

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19804?page=com.atlassian.jira.plugi... ] Lucia Jelinkova updated JBIDE-19804: ------------------------------------ Attachment: video.avi dialog.png > Select folder dialog problem > ---------------------------- > > Key: JBIDE-19804 > URL: https://issues.jboss.org/browse/JBIDE-19804 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > Attachments: dialog.png, video.avi > > > Sometimes (but not allways, maybe 1 out of 5 times) I got the problem that when I want to choose the folder to open, the dialog is open and after some time it is interrupted with some other dialog for really small time (you can only see it blink). After that you need to click OK several times to make the dialog response (maybe only wait would be OK). > I captured this on the video (attached) but due to the poor quality you cannot actually see the dialog (the blink is around second 10). However, I managed to make a screenshot from higher-quality video I have on my computer. > It seems it is an OOmph dialog so I am not sure it really relates to the easy import component at all. But maybe you do work with Preferences and could avoid the OOmph invokation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19804) Select folder dialog problem

by Lucia Jelinkova (JIRA)

Lucia Jelinkova created JBIDE-19804: --------------------------------------- Summary: Select folder dialog problem Key: JBIDE-19804 URL: https://issues.jboss.org/browse/JBIDE-19804 Project: Tools (JBoss Tools) Issue Type: Bug Components: easymport Affects Versions: 4.3.0.Beta1 Reporter: Lucia Jelinkova Sometimes (but not allways, maybe 1 out of 5 times) I got the problem that when I want to choose the folder to open, the dialog is open and after some time it is interrupted with some other dialog for really small time (you can only see it blink). After that you need to click OK several times to make the dialog response (maybe only wait would be OK). I captured this on the video (attached) but due to the poor quality you cannot actually see the dialog (the blink is around second 10). However, I managed to make a screenshot from higher-quality video I have on my computer. It seems it is an OOmph dialog so I am not sure it really relates to the easy import component at all. But maybe you do work with Preferences and could avoid the OOmph invokation. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19803) Workspace root is detected as JavaEE project

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19803?page=com.atlassian.jira.plugi... ] Lucia Jelinkova updated JBIDE-19803: ------------------------------------ Summary: Workspace root is detected as JavaEE project (was: Workspace root is detected as ) > Workspace root is detected as JavaEE project > -------------------------------------------- > > Key: JBIDE-19803 > URL: https://issues.jboss.org/browse/JBIDE-19803 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: easymport > Affects Versions: 4.3.0.Beta1 > Reporter: Lucia Jelinkova > > When I select to import workspace root that contains Dynamic Web Project it is imported as "Eclipse Project, Java, JavaScript, Java EE Servlet" and the following error is logged into error log. > {code} > org.jboss.tools.playground.easymport.jee > Error > Thu May 14 10:58:02 CEST 2015 > Content is not allowed in prolog. > org.xml.sax.SAXParseException; lineNumber: 2; columnNumber: 1; Content is not allowed in prolog. > at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:257) > at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:347) > at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:121) > at org.jboss.tools.playground.easymport.jee.servlet.ServletProjectConfigurator.configure(ServletProjectConfigurator.java:62) > at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.importProjectAndChildrenRecursively(EasymportJob.java:219) > at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.run(EasymportJob.java:87) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) > {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19803) Workspace root is detected as

by Lucia Jelinkova (JIRA)

Lucia Jelinkova created JBIDE-19803: --------------------------------------- Summary: Workspace root is detected as Key: JBIDE-19803 URL: https://issues.jboss.org/browse/JBIDE-19803 Project: Tools (JBoss Tools) Issue Type: Bug Components: easymport Affects Versions: 4.3.0.Beta1 Reporter: Lucia Jelinkova When I select to import workspace root that contains Dynamic Web Project it is imported as "Eclipse Project, Java, JavaScript, Java EE Servlet" and the following error is logged into error log. {code} org.jboss.tools.playground.easymport.jee Error Thu May 14 10:58:02 CEST 2015 Content is not allowed in prolog. org.xml.sax.SAXParseException; lineNumber: 2; columnNumber: 1; Content is not allowed in prolog. at com.sun.org.apache.xerces.internal.parsers.DOMParser.parse(DOMParser.java:257) at com.sun.org.apache.xerces.internal.jaxp.DocumentBuilderImpl.parse(DocumentBuilderImpl.java:347) at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:121) at org.jboss.tools.playground.easymport.jee.servlet.ServletProjectConfigurator.configure(ServletProjectConfigurator.java:62) at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.importProjectAndChildrenRecursively(EasymportJob.java:219) at org.eclipse.ui.internal.wizards.datatransfer.EasymportJob.run(EasymportJob.java:87) at org.eclipse.core.internal.jobs.Worker.run(Worker.java:55) {code} -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19768) Add possibility to select which nested projects to import

by Lucia Jelinkova (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19768?page=com.atlassian.jira.plugi... ] Lucia Jelinkova commented on JBIDE-19768: ----------------------------------------- I think my issue will be fixed by this PR: https://git.eclipse.org/r/#/c/47733/ > Add possibility to select which nested projects to import > --------------------------------------------------------- > > Key: JBIDE-19768 > URL: https://issues.jboss.org/browse/JBIDE-19768 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: easymport > Affects Versions: 4.3.0.Alpha2 > Reporter: Lucia Jelinkova > Assignee: Mickael Istria > Priority: Critical > > At the moment, all nested projects are imported - it would be useful to have the possibility to select which projects one wants to import. > Also, sometimes projects contain test data that are detected as projects - this feature would help also in this case. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 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 commented on JBIDE-19769: ----------------------------------------- I tried to reproduce it today but it seems to work on nightly build now. > 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, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19346) jbosstools-earlyaccess.properties contains old versions of tern, angular, jetty, and vjet

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19346?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-19346: --------------------------------------- IMO this file contains a lot more information than it should. Feature life cycle is simple: EA -> NONE EA It is never downgraded this way NONE EA - > EA This means there is no reason to have lower version in this file at all. Upper part should be filled after feature is promoted out of EA. So basically for features that haven get promoted yet there should be no version range at all. For features that have been promoted there should be only upper part of the range only, which means version that got promoted. That would mean less maintenance required, no need to update upper range with every new release. > jbosstools-earlyaccess.properties contains old versions of tern, angular, jetty, and vjet > ----------------------------------------------------------------------------------------- > > Key: JBIDE-19346 > URL: https://issues.jboss.org/browse/JBIDE-19346 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: build > Affects Versions: 4.3.0.Alpha1 > Reporter: Nick Boldt > Assignee: Nick Boldt > Fix For: 4.3.0.Beta1 > > > While promoting JBT 4.3.0.Alpha1 to /development/ I realized that jbosstools-earlyaccess.properties contains old versions. We should have tern/angular 0.8 in there, right [~dgolovin] ? > {code} > $➔ cat jbosstools-earlyaccess.properties > #Mon Sep 01 18:54:14 CEST 2014 > org.eclipse.vjet.rt.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > org.jboss.tools.arquillian.feature.feature.group=[1.1.2.CR1-v20140830-0003-B63,1.1.2.CR1-v20140830-0003-B63] > org.eclipse.vjet.extmod.jsdt.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > org.eclipse.vjet.web.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > org.eclipse.vjet.extmod.dltk.core.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > org.eclipse.vjet.codegen.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > tern-server-nodejs-feature.feature.group=[0.5.0.201408272110,0.5.0.201408272110] > org.eclipse.vjet.eclipse.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > tern.eclipse.ide.tools.feature.feature.group=[0.5.0.201408272110,0.5.0.201408272110] > tern.eclipse.ide.server.nodejs.embed.feature.group=[0.5.0.201408272110,0.5.0.201408272110] > org.eclipse.vjet.vsf.domkit.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > org.eclipse.equinox.server.jetty.feature.group=[1.1.100.v20140416-1649,1.1.100.v20140416-1649] > org.eclipse.vjet.extmod.rhino.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > tern-feature.feature.group=[0.5.0.201408272110,0.5.0.201408272110] > org.eclipse.vjet.core.feature.group=[0.10.0.201403201656,0.10.0.201403201656] > tern-jsdt-feature.feature.group=[0.5.0.201408272110,0.5.0.201408272110] > angularjs-eclipse-feature.feature.group=[0.5.0.201408281218,0.5.0.201408281218] > {code} > -- http://download.jboss.org/jbosstools/discovery/staging/4.3.0.Alpha1/jboss... -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19590) Update module's README.md files with information about dependencies to other modules

by Denis Golovin (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19590?page=com.atlassian.jira.plugi... ] Denis Golovin commented on JBIDE-19590: --------------------------------------- Haven't looked at oomph yet, will do. > Update module's README.md files with information about dependencies to other modules > ------------------------------------------------------------------------------------ > > Key: JBIDE-19590 > URL: https://issues.jboss.org/browse/JBIDE-19590 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: build > Affects Versions: 4.3.0.Alpha2 > Reporter: Denis Golovin > Assignee: Denis Golovin > Fix For: 4.3.0.Beta1 > > Attachments: hibernate-psf-import.mp4 > > > For almost every JBoss Tools module there are three major steps to configure eclipse workspace for development: > 1. Set up target platform in preferences > 2. Import JBT module sources into workspace > 3. Import required JBT module sources into worksapce > (1) and (2) are well documented in README.md files, but (3) is not (see forum reference for jbosstools-hibernate as an example). -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-19663) jst/jsf New and Noteworthy for 4.3.0.Alpha2

by Vlado Pakan (JIRA)

[ https://issues.jboss.org/browse/JBIDE-19663?page=com.atlassian.jira.plugi... ] Vlado Pakan closed JBIDE-19663. ------------------------------- Verified on http://tools.jboss.org/documentation/whatsnew/jbosstools/4.3.0.Alpha2.html > jst/jsf New and Noteworthy for 4.3.0.Alpha2 > ------------------------------------------- > > Key: JBIDE-19663 > URL: https://issues.jboss.org/browse/JBIDE-19663 > Project: Tools (JBoss Tools) > Issue Type: Sub-task > Components: jsf, jsp/jsf/xml/html source editing > Reporter: Alexey Kazakov > Assignee: Alexey Kazakov > Priority: Critical > Fix For: 4.3.0.Alpha2 > > > This [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...] contains the search for the specific component(s), to see all, use this [query|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+an...]. > If jst/jsf is not listed here check if there are issues that should be added and add them. > Document the ones relevant for jst/jsf by adding to [whatsnew|https://github.com/jbosstools/jbosstools-website/tree/master/doc...] and submit a pullrequest. > If no news for this component please reject and close this issue. -- This message was sent by Atlassian JIRA (v6.3.15#6346)

10 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 May 2015