[JBoss JIRA] (JBIDE-18187) ResourceException: "Resource '/test' is not open" exception after closing cordova project
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18187?page=com.atlassian.jira.plugi... ]
Gorkem Ercan reassigned JBIDE-18187:
------------------------------------
Assignee: Gorkem Ercan
> ResourceException: "Resource '/test' is not open" exception after closing cordova project
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-18187
> URL: https://issues.jboss.org/browse/JBIDE-18187
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.0.CR1
> Reporter: Denis Golovin
> Assignee: Gorkem Ercan
> Fix For: 4.2.0.CR1
>
>
> {code}org.eclipse.core.internal.resources.ResourceException: Resource '/test' is not open.
> at org.eclipse.core.internal.resources.Project.checkAccessible(Project.java:150)
> at org.eclipse.core.internal.resources.Project.hasNature(Project.java:584)
> at org.jboss.tools.aerogear.thym.internal.convert.NatureConvertListener.resourceChanged(NatureConvertListener.java:41)
> at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:291)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285)
> at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149)
> at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:378)
> at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1498)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:45)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54){code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18187) ResourceException: "Resource '/test' is not open" exception after closing cordova project
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18187?page=com.atlassian.jira.plugi... ]
Gorkem Ercan updated JBIDE-18187:
---------------------------------
Fix Version/s: 4.2.0.CR1
> ResourceException: "Resource '/test' is not open" exception after closing cordova project
> -----------------------------------------------------------------------------------------
>
> Key: JBIDE-18187
> URL: https://issues.jboss.org/browse/JBIDE-18187
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.2.0.CR1
> Reporter: Denis Golovin
> Assignee: Gorkem Ercan
> Fix For: 4.2.0.CR1
>
>
> {code}org.eclipse.core.internal.resources.ResourceException: Resource '/test' is not open.
> at org.eclipse.core.internal.resources.Project.checkAccessible(Project.java:150)
> at org.eclipse.core.internal.resources.Project.hasNature(Project.java:584)
> at org.jboss.tools.aerogear.thym.internal.convert.NatureConvertListener.resourceChanged(NatureConvertListener.java:41)
> at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:291)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285)
> at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149)
> at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:378)
> at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1498)
> at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:45)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54){code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18187) ResourceException: "Resource '/test' is not open" exception after closing cordova project
by Denis Golovin (JIRA)
Denis Golovin created JBIDE-18187:
-------------------------------------
Summary: ResourceException: "Resource '/test' is not open" exception after closing cordova project
Key: JBIDE-18187
URL: https://issues.jboss.org/browse/JBIDE-18187
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: aerogear-hybrid
Affects Versions: 4.2.0.CR1
Reporter: Denis Golovin
{code}org.eclipse.core.internal.resources.ResourceException: Resource '/test' is not open.
at org.eclipse.core.internal.resources.Project.checkAccessible(Project.java:150)
at org.eclipse.core.internal.resources.Project.hasNature(Project.java:584)
at org.jboss.tools.aerogear.thym.internal.convert.NatureConvertListener.resourceChanged(NatureConvertListener.java:41)
at org.eclipse.core.internal.events.NotificationManager$1.run(NotificationManager.java:291)
at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
at org.eclipse.core.internal.events.NotificationManager.notify(NotificationManager.java:285)
at org.eclipse.core.internal.events.NotificationManager.broadcastChanges(NotificationManager.java:149)
at org.eclipse.core.internal.resources.Workspace.broadcastPostChange(Workspace.java:378)
at org.eclipse.core.internal.resources.Workspace.endOperation(Workspace.java:1498)
at org.eclipse.core.internal.resources.InternalWorkspaceJob.run(InternalWorkspaceJob.java:45)
at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54){code}
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17992) Show Tern Modules configuration under different preferences category
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17992?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-17992:
----------------------------------
Description:
Tern modules configuration should be visible to let disable/enable specific modules. At the same time we should still not show JavaScript Engine configuration preferences.
Modules should be available under JavaScript category
!modules.png!
was:
Tern modules configuration should be visible to let disable/enable specific modules. At the same time we should still not show JavaScript Engine configuration preferences.
Should be possible by creating new category and assigning tern modules preference page class to it.
Should test if it works with both original and new category visible.
> Show Tern Modules configuration under different preferences category
> --------------------------------------------------------------------
>
> Key: JBIDE-17992
> URL: https://issues.jboss.org/browse/JBIDE-17992
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.CR1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 4.2.0.CR1
>
> Attachments: modules.png
>
>
> Tern modules configuration should be visible to let disable/enable specific modules. At the same time we should still not show JavaScript Engine configuration preferences.
> Modules should be available under JavaScript category
> !modules.png!
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-17992) Show Tern Modules configuration under different preferences category
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17992?page=com.atlassian.jira.plugi... ]
Denis Golovin updated JBIDE-17992:
----------------------------------
Attachment: modules.png
> Show Tern Modules configuration under different preferences category
> --------------------------------------------------------------------
>
> Key: JBIDE-17992
> URL: https://issues.jboss.org/browse/JBIDE-17992
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: jsp/jsf/xml/html source editing
> Affects Versions: 4.2.0.CR1
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Priority: Blocker
> Fix For: 4.2.0.CR1
>
> Attachments: modules.png
>
>
> Tern modules configuration should be visible to let disable/enable specific modules. At the same time we should still not show JavaScript Engine configuration preferences.
> Should be possible by creating new category and assigning tern modules preference page class to it.
> Should test if it works with both original and new category visible.
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18154) For JBIDE 4.2.0.CR1: Code Freeze + Branch [Central Discovery]
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18154?page=com.atlassian.jira.plugi... ]
Mickael Istria resolved JBIDE-18154.
------------------------------------
Resolution: Done
> For JBIDE 4.2.0.CR1: Code Freeze + Branch [Central Discovery]
> -------------------------------------------------------------
>
> Key: JBIDE-18154
> URL: https://issues.jboss.org/browse/JBIDE-18154
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: discovery
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.CR1
>
>
> For JBIDE 4.2.0.CR1 [Central Discovery]: Please perform the following tasks:
> 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR1
> [Unresolved JIRAs with fixVersion = 4.2.0.CR1, 8.0.0.CR1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
> *NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
> {code}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.21.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.2.0.CR1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.CR1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.CR1-SNAPSHOT;
> {code}
> mvn clean verify -Dtpc.version=4.40.0.CR1 # (if the TP is already released)
> or
> mvn clean verify -Dtpc.version=4.40.0.CR1-SNAPSHOT # (if still being staged)
> {code}
> 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.x{color}* branch;
> {code}
> git fetch origin master
> git checkout FETCH_HEAD
> git checkout -b jbosstools-4.2.x
> git push origin jbosstools-4.2.x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
> {code}
> git checkout master
> git pull origin master
> {code}
> 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.CR2-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.CR2-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.2.0.CR1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and
> * *{color:orange}4.2.0.CR2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Central Discovery task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18154) For JBIDE 4.2.0.CR1: Code Freeze + Branch [Central Discovery]
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18154?page=com.atlassian.jira.plugi... ]
Mickael Istria reassigned JBIDE-18154:
--------------------------------------
Assignee: Mickael Istria
> For JBIDE 4.2.0.CR1: Code Freeze + Branch [Central Discovery]
> -------------------------------------------------------------
>
> Key: JBIDE-18154
> URL: https://issues.jboss.org/browse/JBIDE-18154
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: discovery
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.CR1
>
>
> For JBIDE 4.2.0.CR1 [Central Discovery]: Please perform the following tasks:
> 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR1
> [Unresolved JIRAs with fixVersion = 4.2.0.CR1, 8.0.0.CR1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
> *NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
> {code}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.21.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.2.0.CR1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.CR1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.CR1-SNAPSHOT;
> {code}
> mvn clean verify -Dtpc.version=4.40.0.CR1 # (if the TP is already released)
> or
> mvn clean verify -Dtpc.version=4.40.0.CR1-SNAPSHOT # (if still being staged)
> {code}
> 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.x{color}* branch;
> {code}
> git fetch origin master
> git checkout FETCH_HEAD
> git checkout -b jbosstools-4.2.x
> git push origin jbosstools-4.2.x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
> {code}
> git checkout master
> git pull origin master
> {code}
> 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.CR2-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.CR2-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.2.0.CR1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and
> * *{color:orange}4.2.0.CR2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Central Discovery task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months
[JBoss JIRA] (JBIDE-18156) For JBIDE 4.2.0.CR1: Code Freeze + Branch [Hibernate]
by Mickael Istria (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18156?page=com.atlassian.jira.plugi... ]
Mickael Istria resolved JBIDE-18156.
------------------------------------
Resolution: Done
Branch exists and build has run.
> For JBIDE 4.2.0.CR1: Code Freeze + Branch [Hibernate]
> -----------------------------------------------------
>
> Key: JBIDE-18156
> URL: https://issues.jboss.org/browse/JBIDE-18156
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: hibernate
> Reporter: Mickael Istria
> Assignee: Koen Aers
> Priority: Blocker
> Labels: task
> Fix For: 4.2.0.CR1
>
>
> For JBIDE 4.2.0.CR1 [Hibernate]: Please perform the following tasks:
> 0. If nothing has changed in your component since 4.1.1.Final / 7.1.0.GA (eg., XulRunner, GWT, Freemarker, BIRT), *{color:red}Reject this JIRA{color}*.
> Otherwise:
> 0. Make sure your component has no remaining unresolved JIRAs set for fixVersion = 4.2.0.CR1
> [Unresolved JIRAs with fixVersion = 4.2.0.CR1, 8.0.0.CR1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%22J...]
> 1. Ensure your component features/plugins have been [properly upversioned|http://wiki.eclipse.org/Version_Numbering#Overall_example], eg., from 1.0.0 to 1.0.1.
> *NOTE:* If you already did this for the previous milestone you do *not* need to do so again.
> {code}
> mvn -Dtycho.mode=maven org.sonatype.tycho:tycho-versions-plugin:0.21.0:set-version -DnewVersion=1.0.1-SNAPSHOT
> {code}
> 2. Update your root pom to use parent pom version 4.2.0.CR1-SNAPSHOT;
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.CR1-SNAPSHOT</version>
> </parent>
> {code}
> 3. Ensure you've built & run your plugin tests using the latest target platform version 4.40.0.CR1-SNAPSHOT;
> {code}
> mvn clean verify -Dtpc.version=4.40.0.CR1 # (if the TP is already released)
> or
> mvn clean verify -Dtpc.version=4.40.0.CR1-SNAPSHOT # (if still being staged)
> {code}
> 4. Branch from your existing master branch into a new *{color:blue}jbosstools-4.2.x{color}* branch;
> {code}
> git fetch origin master
> git checkout FETCH_HEAD
> git checkout -b jbosstools-4.2.x
> git push origin jbosstools-4.2.x
> {code}
> 5. *NOW THAT YOU HAVE BRANCHED*, check out your *{color:orange}master branch{color}*.
> {code}
> git checkout master
> git pull origin master
> {code}
> 6. Update your *{color:orange}master branch{color}* parent pom to use the latest version, *{color:orange}4.2.0.CR2-SNAPSHOT{color}*:
> {code}
> <parent>
> <groupId>org.jboss.tools</groupId>
> <artifactId>parent</artifactId>
> <version>4.2.0.CR2-SNAPSHOT</version>
> </parent>
> {code}
> Now, your root pom will use parent pom version:
> * *{color:blue}4.2.0.CR1-SNAPSHOT{color}* in your *{color:blue}jbosstools-4.2.x{color}* branch, and
> * *{color:orange}4.2.0.CR2-SNAPSHOT{color}* in your *{color:orange}master{color}* branch.
> 7. Close (do not resolve) this JIRA when done.
> 8. If you have any outstanding [New + Noteworthy JIRAs|https://issues.jboss.org/issues/?jql=%28%28project%20in%20%28JBDS%2...] to do, please complete them next.
> [Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for Hibernate task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.1#6329)
11 years, 7 months