[JBoss JIRA] (JBIDE-19228) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [JST]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19228:
----------------------------------
Summary: For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [JST]
Key: JBIDE-19228
URL: https://issues.jboss.org/browse/JBIDE-19228
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: common/jst/core
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.0.Alpha1 [JST]: Please perform the following tasks:
0. If nothing has changed in your component since the creation of the 4.2.x branch (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.3.0.Alpha1
[Unresolved JIRAs with fixVersion = 4.3.0.Alpha1, 9.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
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.1.0, or from 1.2.2 to 1.2.100.
*NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.0.Alpha1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.0.Alpha1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha1;
{code}
mvn clean verify -Dtpc.version=4.50.0.Alpha1 # (if the TP is already released)
{code}
4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha1x branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.3.0.Alpha1x
git push origin jbosstools-4.3.0.Alpha1x
{code}
5. Close (do not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for JST task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19229) For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [VPE]
by Nick Boldt (JIRA)
Nick Boldt created JBIDE-19229:
----------------------------------
Summary: For JBIDE 4.3.0.Alpha1: Code Freeze + Branch [VPE]
Key: JBIDE-19229
URL: https://issues.jboss.org/browse/JBIDE-19229
Project: Tools (JBoss Tools)
Issue Type: Sub-task
Components: visual-page-editor-core
Reporter: Nick Boldt
Priority: Blocker
For JBIDE 4.3.0.Alpha1 [VPE]: Please perform the following tasks:
0. If nothing has changed in your component since the creation of the 4.2.x branch (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.3.0.Alpha1
[Unresolved JIRAs with fixVersion = 4.3.0.Alpha1, 9.0.0.Alpha1|https://issues.jboss.org/issues/?jql=%28%28project%20%3D%20%...]
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.1.0, or from 1.2.2 to 1.2.100.
*NOTE:* If you already did this for your master branch, you do *not* need to do so again. Please also ensure that the version of your code in the master branch is *greater* than your code in the 4.2.x branch.
{code}
mvn -Dtycho.mode=maven org.eclipse.tycho:tycho-versions-plugin:0.22.0:set-version -DnewVersion=4.3.0-SNAPSHOT
{code}
2. Update your root pom to use parent pom version 4.3.0.Alpha1-SNAPSHOT;
{code}
<parent>
<groupId>org.jboss.tools</groupId>
<artifactId>parent</artifactId>
<version>4.3.0.Alpha1-SNAPSHOT</version>
</parent>
{code}
3. Ensure you've built & run your plugin tests using the latest target platform version 4.50.0.Alpha1;
{code}
mvn clean verify -Dtpc.version=4.50.0.Alpha1 # (if the TP is already released)
{code}
4. Branch from your existing master branch into a new jbosstools-4.3.0.Alpha1x branch;
{code}
git checkout master
git pull origin master
git checkout -b jbosstools-4.3.0.Alpha1x
git push origin jbosstools-4.3.0.Alpha1x
{code}
5. Close (do not resolve) this JIRA when done.
[Search for all task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...], or [Search for VPE task JIRA|https://issues.jboss.org/issues/?jql=%28%28project+in+%28JBDS%29+and...]
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19187) CordovaSim + localhost:8080 fail
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19187?page=com.atlassian.jira.plugi... ]
Ilya Buziuk edited comment on JBIDE-19187 at 2/11/15 11:08 AM:
---------------------------------------------------------------
[~burrsutter], well we have discussed cross domain ajax issues in JBIDE-18312 and JBIDE-18404
in JBIDE-18404 our user and contributor Kaloyan Raev (zend studio lead) proposed very important stuff:
{quote}
I experience serious troubles with CordovaSim after this switch to using the Remote cross domain proxy. Setting the Cross Domain Proxy to Remote means that all calls go through a cloud-based proxy server hosted at https://rippleapi.herokuapp.com/xhr_proxy. More info is available here: https://issues.apache.org/jira/browse/RIPPLE-63
In addition to the security issues, this also breaks mobile apps which tries to talk to a backend on localhost or to a remote server in the user's intranet - the cloud-based proxy just cannot connect to such backends. I also experience troubles with backends hosted on AWS. These are a quite common use cases during development of mobile apps.
Of course, users can switch the Cross Domain Proxy to Local or Disabled, but (1) this takes some painful hours to realize, and (2) it has to be done every time the simulator is started. All this ruins the user experience.
Was setting the default value to Remote really necessary to resolve this issue? I see it was just one of many changes done. Is it possible to revert it back to Local as the default?
{quote}
So, this is exactly what we are facing in this issue. Now it fixed in master - JBIDE-18732. However, it's not pushed to 4.2.x cause it was decided that the fix is not safe enough.
What is proposed and will be done for 8.1.0 release:
1. local proxy will be default one
2. fixing livereload issue - JBIDE-19109
3. security warning for remote proxy JBIDE-19163 (PR was also contributed back to ripple - https://github.com/apache/incubator-ripple/pull/37)
Basically, as I said before, there is no silver bullet for handling all cross domain ajax. It depend dramatically on the server side setup - http://stackoverflow.com/questions/18402422/phonegap-application-not-work...
Also, I have decided to write a blog about CordovaSim and CrossDomain ajax in order to avoid misleading stuff our users might experience.
was (Author: ibuziuk):
[~burrsutter], well we have discussed cross domain ajax issues in JBIDE-18312 and JBIDE-18404
in JBIDE-18404 our user and contributor Kaloyan Raev (zend studio lead) proposed very important stuff:
{quote}
I experience serious troubles with CordovaSim after this switch to using the Remote cross domain proxy. Setting the Cross Domain Proxy to Remote means that all calls go through a cloud-based proxy server hosted at https://rippleapi.herokuapp.com/xhr_proxy. More info is available here: https://issues.apache.org/jira/browse/RIPPLE-63
In addition to the security issues, this also breaks mobile apps which tries to talk to a backend on localhost or to a remote server in the user's intranet - the cloud-based proxy just cannot connect to such backends. I also experience troubles with backends hosted on AWS. These are a quite common use cases during development of mobile apps.
Of course, users can switch the Cross Domain Proxy to Local or Disabled, but (1) this takes some painful hours to realize, and (2) it has to be done every time the simulator is started. All this ruins the user experience.
Was setting the default value to Remote really necessary to resolve this issue? I see it was just one of many changes done. Is it possible to revert it back to Local as the default?
{quote}
So, this is exactly what we are facing in this issue. Now it fixed in master - JBIDE-18732. However, it's not pushed to 4.2.x cause it was decided that the fix is not save enough.
What is proposed and will be done for 8.1.0 release:
1. local proxy will be default one
2. fixing livereload issue - JBIDE-19109
3. security warning for remote proxy JBIDE-19163 (PR was also contributed back to ripple - https://github.com/apache/incubator-ripple/pull/37)
Basically, as I said before, there is no silver bullet for handling all cross domain ajax. It depend dramatically on the server side setup - http://stackoverflow.com/questions/18402422/phonegap-application-not-work...
Also, I have decided to write a blog about CordovaSim and CrossDomain ajax in order to avoid misleading stuff our users might experience.
> CordovaSim + localhost:8080 fail
> --------------------------------
>
> Key: JBIDE-19187
> URL: https://issues.jboss.org/browse/JBIDE-19187
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cordovasim
> Affects Versions: 4.2.0.Final
> Environment: JBDS 8
> Reporter: Burr Sutter
> Assignee: Ilya Buziuk
> Priority: Critical
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha1
>
> Attachments: hybrid4001.zip, localhost_error.png
>
>
> The following logic used to work and now fails:
> $.getJSON("http://localhost:8080/jboss-as-kitchensink-html5-mobile/rest/members", function(data) {
> $("#contacts").empty();
> var items = [];
> $.each(data, function(key, val) {
> console.log("item: " + key + " " + val.name);
> items.push("<li><a href='#"+ key + "'>" + val.name +"</a></li>");
> });
> $("#contacts").append(items);
> $("#contacts").listview("refresh");
> });
> -------
> as seen in this youtube video and comments
> https://www.youtube.com/watch?v=FstGLMr3W8s&feature=gp-n-y&google_comment...
> ---- Using the Chrome Debugger (via CordovaSim, right-click, Dev Tools)
> has the following error message:
> https://rippleapi.herokuapp.com/xhr_proxy?tinyhippos_apikey=ABC&tinyhippo... 500 () rippleapi.herokuapp.com/xhr_proxy?tinyhippos_apikey=ABC&tinyhippos_rurl=h...
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBDS-3344) java.lang.NoClassDefFoundError: javax/servlet/http/HttpServletRequest
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBDS-3344?page=com.atlassian.jira.plugin.... ]
Jiri Peterka commented on JBDS-3344:
------------------------------------
Not present in WFK 2.7. There is different set of Spring examples with quite a completely different set of Internal Errors.
> java.lang.NoClassDefFoundError: javax/servlet/http/HttpServletRequest
> ---------------------------------------------------------------------
>
> Key: JBDS-3344
> URL: https://issues.jboss.org/browse/JBDS-3344
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: 3rd-party-certification, project-examples
> Affects Versions: 8.0.2.GA
> Environment: JBDS 8.0.2.GA
> Reporter: Jiri Peterka
> Fix For: 9.0.0.Alpha1
>
>
> {code}
> java.lang.NoClassDefFoundError: javax/servlet/http/HttpServletRequest
> at java.lang.Class.getDeclaredMethods0(Native Method)
> at java.lang.Class.privateGetDeclaredMethods(Class.java:2693)
> at java.lang.Class.getDeclaredMethods(Class.java:1967)
> at org.springframework.core.type.StandardAnnotationMetadata.hasAnnotatedMethods(StandardAnnotationMetadata.java:129)
> at org.springframework.context.annotation.ConfigurationClassUtils.isLiteConfigurationCandidate(ConfigurationClassUtils.java:131)
> at org.springframework.context.annotation.ConfigurationClassUtils.checkConfigurationClassCandidate(ConfigurationClassUtils.java:90)
> at org.springframework.context.annotation.ConfigurationClassPostProcessor.processConfigBeanDefinitions(ConfigurationClassPostProcessor.java:274)
> at org.springframework.ide.eclipse.metadata.process.JdtConfigurationClassPostProcessor.postProcess(JdtConfigurationClassPostProcessor.java:87)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$4.run(BeansConfig.java:752)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.executePostProcessor(BeansConfig.java:745)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.postProcess(BeansConfig.java:629)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig.access$8(BeansConfig.java:588)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$3.call(BeansConfig.java:455)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansConfig$3.call(BeansConfig.java:1)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511)
> at java.util.concurrent.FutureTask.run(FutureTask.java:266)
> at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142)
> at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617)
> at java.lang.Thread.run(Thread.java:745)
> Caused by: java.lang.ClassNotFoundException: javax.servlet.http.HttpServletRequest
> at java.net.URLClassLoader$1.run(URLClassLoader.java:372)
> at java.net.URLClassLoader$1.run(URLClassLoader.java:361)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.net.URLClassLoader.findClass(URLClassLoader.java:360)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
> at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
> ... 21 more
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19079) SWTException when creating JPA 2.0 project
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19079?page=com.atlassian.jira.plugi... ]
Koen Aers updated JBIDE-19079:
------------------------------
Fix Version/s: 4.3.0.Alpha2
(was: 4.3.0.Alpha1)
> SWTException when creating JPA 2.0 project
> ------------------------------------------
>
> Key: JBIDE-19079
> URL: https://issues.jboss.org/browse/JBIDE-19079
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Reporter: Koen Aers
> Assignee: Koen Aers
> Fix For: 4.2.3.Beta1, 4.3.0.Alpha2
>
>
> This is the produced stacktrace:
> org.eclipse.swt.SWTException: Widget is disposed
> at org.eclipse.swt.SWT.error(SWT.java:4441)
> at org.eclipse.swt.SWT.error(SWT.java:4356)
> at org.eclipse.swt.SWT.error(SWT.java:4327)
> at org.eclipse.swt.widgets.Widget.error(Widget.java:783)
> at org.eclipse.swt.widgets.Widget.getDisplay(Widget.java:903)
> at org.hibernate.eclipse.console.views.KnownConfigurationsProvider.refreshTree(KnownConfigurationsProvider.java:91)
> at org.hibernate.eclipse.console.views.KnownConfigurationsProvider.access$0(KnownConfigurationsProvider.java:85)
> at org.hibernate.eclipse.console.views.KnownConfigurationsProvider$KnownConfigurationsVisitor.visit(KnownConfigurationsProvider.java:163)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:69)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:49)
> at org.hibernate.eclipse.console.views.KnownConfigurationsProvider.resourceChanged(KnownConfigurationsProvider.java:141)
> 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.Workspace.run(Workspace.java:2322)
> at org.eclipse.wst.common.project.facet.ui.ModifyFacetedProjectWizard$4.run(ModifyFacetedProjectWizard.java:345)
> at org.eclipse.jface.operation.ModalContext$ModalContextThread.run(ModalContext.java:122)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-19225) java.lang.IllegalArgumentException: null source after importing WFK Spring projects
by Jiri Peterka (JIRA)
[ https://issues.jboss.org/browse/JBIDE-19225?page=com.atlassian.jira.plugi... ]
Jiri Peterka commented on JBIDE-19225:
--------------------------------------
In WFK 2.7 is different set of Spring examples with quite a completely different set of Internal Errors.
> java.lang.IllegalArgumentException: null source after importing WFK Spring projects
> -----------------------------------------------------------------------------------
>
> Key: JBIDE-19225
> URL: https://issues.jboss.org/browse/JBIDE-19225
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: project-examples, upstream
> Affects Versions: 4.2.2.Final
> Reporter: Jiri Peterka
>
> {code}
> java.lang.IllegalArgumentException: null source
> at java.util.EventObject.<init>(EventObject.java:56)
> at org.springframework.ide.eclipse.core.model.ModelChangeEvent.<init>(ModelChangeEvent.java:43)
> at org.springframework.ide.eclipse.core.model.AbstractModel.notifyListeners(AbstractModel.java:43)
> at org.springframework.ide.eclipse.beans.core.internal.model.BeansModel$ResourceChangeEventHandler.configAdded(BeansModel.java:598)
> at org.springframework.ide.eclipse.beans.core.internal.model.resources.BeansResourceChangeListener$BeansResourceVisitor.resourceAdded(BeansResourceChangeListener.java:97)
> at org.springframework.ide.eclipse.core.internal.model.resources.SpringResourceChangeListener$SpringResourceVisitor.visit(SpringResourceChangeListener.java:145)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:69)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
> at org.eclipse.core.internal.events.ResourceDelta.accept(ResourceDelta.java:80)
> at org.springframework.ide.eclipse.core.internal.model.resources.SpringResourceChangeListener.resourceChanged(SpringResourceChangeListener.java:83)
> 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.broadcastBuildEvent(Workspace.java:364)
> at org.eclipse.core.internal.events.AutoBuildJob.doBuild(AutoBuildJob.java:146)
> at org.eclipse.core.internal.events.AutoBuildJob.run(AutoBuildJob.java:241)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:54)
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months
[JBoss JIRA] (JBIDE-18527) "rm -rf project" in Forge Console doesn't delete project
by Koen Aers (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18527?page=com.atlassian.jira.plugi... ]
Koen Aers updated JBIDE-18527:
------------------------------
Fix Version/s: (was: 4.3.0.Alpha1)
> "rm -rf project" in Forge Console doesn't delete project
> --------------------------------------------------------
>
> Key: JBIDE-18527
> URL: https://issues.jboss.org/browse/JBIDE-18527
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: forge
> Affects Versions: 4.2.0.CR2
> Reporter: Pavol Srna
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.2.x
>
>
> {code}
> org.eclipse.core.internal.resources.ResourceException: Errors occurred while refreshing resources with the local file system.
> at org.eclipse.core.internal.localstore.FileSystemResourceManager.refreshResource(FileSystemResourceManager.java:923)
> at org.eclipse.core.internal.localstore.FileSystemResourceManager.refresh(FileSystemResourceManager.java:904)
> at org.eclipse.core.internal.localstore.FileSystemResourceManager.refreshRoot(FileSystemResourceManager.java:951)
> at org.eclipse.core.internal.localstore.FileSystemResourceManager.refresh(FileSystemResourceManager.java:897)
> at org.eclipse.core.internal.resources.Resource.refreshLocal(Resource.java:1705)
> at org.jboss.tools.forge.ui.internal.cli.CommandLineListener.refreshResource(CommandLineListener.java:315)
> at org.jboss.tools.forge.ui.internal.cli.CommandLineListener.refresh(CommandLineListener.java:129)
> at org.jboss.tools.forge.ui.internal.cli.CommandLineListener.access$2(CommandLineListener.java:126)
> at org.jboss.tools.forge.ui.internal.cli.CommandLineListener$1.run(CommandLineListener.java:86)
> at org.eclipse.swt.widgets.RunnableLock.run(RunnableLock.java:35)
> at org.eclipse.swt.widgets.Synchronizer.runAsyncMessages(Synchronizer.java:136)
> at org.eclipse.swt.widgets.Display.runAsyncMessages(Display.java:3774)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3412)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1151)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1032)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:148)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:636)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:579)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:135)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:134)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:104)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:380)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:235)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:62)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:483)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:648)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:603)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1465)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1438)
> Contains: The project description file (.project) for 'jboss-as-kitchensink-html5-mobile' is missing. This file contains important information about the project. The project will not function properly until this file is restored.
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 2 months