[JBoss JIRA] (JBIDE-18769) ResourceException when generating hbm.xml
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18769?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-18769:
-----------------------------------
Fix Version/s: 4.2.2.Final
4.3.0.Alpha1
(was: 4.2.x)
(was: 4.3.x)
> ResourceException when generating hbm.xml
> -----------------------------------------
>
> Key: JBIDE-18769
> URL: https://issues.jboss.org/browse/JBIDE-18769
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.2.0.Final
> Reporter: Rastislav Wagner
> Assignee: Koen Aers
> Priority: Critical
> Fix For: 4.2.2.Final, 4.3.0.Alpha1
>
>
> {code}
> org.eclipse.core.internal.resources.ResourceException: Resource '/jboss-javaee6-webapp/org/jboss/tools/examples/model' does not exist.
> at org.eclipse.core.internal.resources.Resource.checkExists(Resource.java:341)
> at org.eclipse.core.internal.resources.Resource.checkAccessible(Resource.java:215)
> at org.eclipse.core.internal.resources.File.create(File.java:115)
> at org.eclipse.core.internal.resources.File.create(File.java:188)
> at org.eclipse.jdt.internal.corext.refactoring.nls.changes.CreateFileChange.perform(CreateFileChange.java:165)
> at org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278)
> at org.hibernate.eclipse.jdt.ui.wizards.NewHibernateMappingPreviewPage.performFinish(NewHibernateMappingPreviewPage.java:299)
> at org.hibernate.eclipse.jdt.ui.wizards.NewHibernateMappingFileWizard.performFinish(NewHibernateMappingFileWizard.java:408)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:853)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:438)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3799)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3409)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:832)
> at org.eclipse.jface.window.Window.open(Window.java:808)
> at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:269)
> at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:294)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> 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.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:247)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:229)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:149)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343)
> at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:159)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3799)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3409)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-18769) ResourceException when generating hbm.xml
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18769?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-18769:
-----------------------------------
Priority: Blocker (was: Critical)
> ResourceException when generating hbm.xml
> -----------------------------------------
>
> Key: JBIDE-18769
> URL: https://issues.jboss.org/browse/JBIDE-18769
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: hibernate
> Affects Versions: 4.2.0.Final
> Reporter: Rastislav Wagner
> Assignee: Koen Aers
> Priority: Blocker
> Fix For: 4.2.2.Final, 4.3.0.Alpha1
>
>
> {code}
> org.eclipse.core.internal.resources.ResourceException: Resource '/jboss-javaee6-webapp/org/jboss/tools/examples/model' does not exist.
> at org.eclipse.core.internal.resources.Resource.checkExists(Resource.java:341)
> at org.eclipse.core.internal.resources.Resource.checkAccessible(Resource.java:215)
> at org.eclipse.core.internal.resources.File.create(File.java:115)
> at org.eclipse.core.internal.resources.File.create(File.java:188)
> at org.eclipse.jdt.internal.corext.refactoring.nls.changes.CreateFileChange.perform(CreateFileChange.java:165)
> at org.eclipse.ltk.core.refactoring.CompositeChange.perform(CompositeChange.java:278)
> at org.hibernate.eclipse.jdt.ui.wizards.NewHibernateMappingPreviewPage.performFinish(NewHibernateMappingPreviewPage.java:299)
> at org.hibernate.eclipse.jdt.ui.wizards.NewHibernateMappingFileWizard.performFinish(NewHibernateMappingFileWizard.java:408)
> at org.eclipse.jface.wizard.WizardDialog.finishPressed(WizardDialog.java:853)
> at org.eclipse.jface.wizard.WizardDialog.buttonPressed(WizardDialog.java:438)
> at org.eclipse.jface.dialogs.Dialog$2.widgetSelected(Dialog.java:619)
> at org.eclipse.swt.widgets.TypedListener.handleEvent(TypedListener.java:248)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3799)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3409)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:832)
> at org.eclipse.jface.window.Window.open(Window.java:808)
> at org.eclipse.ui.internal.handlers.WizardHandler$New.executeHandler(WizardHandler.java:269)
> at org.eclipse.ui.internal.handlers.WizardHandler.execute(WizardHandler.java:290)
> at org.eclipse.ui.internal.handlers.HandlerProxy.execute(HandlerProxy.java:294)
> at org.eclipse.ui.internal.handlers.E4HandlerProxy.execute(E4HandlerProxy.java:90)
> 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.e4.core.internal.di.MethodRequestor.execute(MethodRequestor.java:55)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:247)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:229)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:149)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:499)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:508)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.ui.internal.handlers.LegacyHandlerService.executeCommand(LegacyHandlerService.java:343)
> at org.eclipse.ui.internal.actions.CommandAction.runWithEvent(CommandAction.java:159)
> at org.eclipse.jface.action.ActionContributionItem.handleWidgetSelection(ActionContributionItem.java:595)
> at org.eclipse.jface.action.ActionContributionItem.access$2(ActionContributionItem.java:511)
> at org.eclipse.jface.action.ActionContributionItem$5.handleEvent(ActionContributionItem.java:420)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4454)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3799)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3409)
> 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)
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBDS-3281) Screencasts: Git
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3281?page=com.atlassian.jira.plugin.... ]
Len DiMaggio updated JBDS-3281:
-------------------------------
Component/s: documentation
> Screencasts: Git
> ----------------
>
> Key: JBDS-3281
> URL: https://issues.jboss.org/browse/JBDS-3281
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: documentation
> Reporter: Burr Sutter
>
> As a Java EE developer, new to Eclipse + Git, I need educational, 5 minute screencasts on the most common uses of Git inside of Eclipse.
> Use cases include:
> 1) as a new member of the team, just having only installed JBDS, I need to add an element to the project
> assume a clone, add (or modify), commit, push workflow
> a- Getting started as a new member of an existing git project (I need to clone a repo, import the project, insure my facets/Maven are set correctly)
> b- navigate/browse an existing repository
> c- git add - for a newly added class or file
> d- git commit -a
> e- git push
> as a new member of the team, just having only installed JBDS, I need to resolve a pull request.
> 2) other scenarios
> - git init a current project that I have in my workspace (and should I move it outside of my workspace first)
> - git checkout for a specific branch - getting Maven and Eclipse Facets to properly recognize my newly checked out branch
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBDS-3280) Screencasts: Java EE
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3280?page=com.atlassian.jira.plugin.... ]
Len DiMaggio updated JBDS-3280:
-------------------------------
Component/s: documentation
> Screencasts: Java EE
> --------------------
>
> Key: JBDS-3280
> URL: https://issues.jboss.org/browse/JBDS-3280
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: documentation
> Reporter: Burr Sutter
>
> As a new Eclipse+Java EE developer, I need educational screencasts, around 5 minutes each that educate me on a specific Java EE development capabilities of JBDS.
> Use cases include:
> - JPA - how to add one, content-assist, relationships
> - database reverse engineering via DTP vs Forge
> - JAX-RS: creation of new endpoints, content-assist, tester - including the GET/POST/PUT/DELETE with JSON payloads
> - JAX-WS: creation of new endpoints, content-assist, tester
> - CDI special features
> - Servlets
> - JSF
> - deployment to localhost EAP
> - deployment to remove EAP
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBDS-2851) Team Usability
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-2851?page=com.atlassian.jira.plugin.... ]
Len DiMaggio closed JBDS-2851.
------------------------------
Resolution: Done
> Team Usability
> --------------
>
> Key: JBDS-2851
> URL: https://issues.jboss.org/browse/JBDS-2851
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Components: requirements
> Reporter: Burr Sutter
> Assignee: Len DiMaggio
> Priority: Critical
> Labels: QE_JBDS80_needinfo
> Fix For: 8.0.0.GA
>
>
> It has come to our attention in the past that users, relatively new to Eclipse overall struggle with basic team dev concepts such as
> - how to integrate with CVS, SVN, Git
> - how to "import" a Maven-based project from SCM
> "Check out Maven Projects from SCM" has misfired for some users
> - how to "checkin" changes back to the SCM
> To some degree the problem is simply that Eclipse offers way too many menu-items that see to do approximately the same things.
> For example, if "Check out Maven Projects from SCM" is supposed to work then we likely need to document how it works with CVS, SVN and Git specifically.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBDS-2851) Team Usability
by CDW Engine (JIRA)
[ https://issues.jboss.org/browse/JBDS-2851?page=com.atlassian.jira.plugin.... ]
CDW Engine reassigned JBDS-2851:
--------------------------------
> Team Usability
> --------------
>
> Key: JBDS-2851
> URL: https://issues.jboss.org/browse/JBDS-2851
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Components: requirements
> Reporter: Burr Sutter
> Assignee: Len DiMaggio
> Priority: Critical
> Labels: QE_JBDS80_needinfo
> Fix For: 8.0.0.GA
>
>
> It has come to our attention in the past that users, relatively new to Eclipse overall struggle with basic team dev concepts such as
> - how to integrate with CVS, SVN, Git
> - how to "import" a Maven-based project from SCM
> "Check out Maven Projects from SCM" has misfired for some users
> - how to "checkin" changes back to the SCM
> To some degree the problem is simply that Eclipse offers way too many menu-items that see to do approximately the same things.
> For example, if "Check out Maven Projects from SCM" is supposed to work then we likely need to document how it works with CVS, SVN and Git specifically.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBDS-2851) Team Usability
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-2851?page=com.atlassian.jira.plugin.... ]
Len DiMaggio updated JBDS-2851:
-------------------------------
Fix Version/s: 8.0.0.GA
> Team Usability
> --------------
>
> Key: JBDS-2851
> URL: https://issues.jboss.org/browse/JBDS-2851
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Epic
> Components: requirements
> Reporter: Burr Sutter
> Assignee: Len DiMaggio
> Priority: Critical
> Labels: QE_JBDS80_needinfo
> Fix For: 8.0.0.GA
>
>
> It has come to our attention in the past that users, relatively new to Eclipse overall struggle with basic team dev concepts such as
> - how to integrate with CVS, SVN, Git
> - how to "import" a Maven-based project from SCM
> "Check out Maven Projects from SCM" has misfired for some users
> - how to "checkin" changes back to the SCM
> To some degree the problem is simply that Eclipse offers way too many menu-items that see to do approximately the same things.
> For example, if "Check out Maven Projects from SCM" is supposed to work then we likely need to document how it works with CVS, SVN and Git specifically.
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months
[JBoss JIRA] (JBIDE-18900) CordovaSim: Can't run default FeedHenry app locally
by Ilya Buziuk (JIRA)
[ https://issues.jboss.org/browse/JBIDE-18900?page=com.atlassian.jira.plugi... ]
Ilya Buziuk commented on JBIDE-18900:
-------------------------------------
< if that file is going to be there
[~maxandersen], this is actually a great remark. There are several thing I want to figure out(please, correct me if I'm wrong):
1) This is the basic basic FH Hybrid app - hyhttps://github.com/feedhenry-templates/helloworld-app. This app contains gruntfile.js with relevant info. However, it's not possible to import it to JBDS. As I understand it's just a template, which will be used for creating full value app via FH magic.
2) *ToolsProject-Cordova-App*, which Burr has provided me with, is a full value hybrid app that was created via FH magic and can be imported as a Hybrid app to the studio. The app works with local and remote server just fine. However, there is *no* gruntfile.js in it. I have debugged this app and find out how that switching between local and remote server happens in the runtime in feedhenry.js in *CloudHost.prototype.getHost* function. Basically, it checks the parameter availability and decides what server (remote / local) to use. Assuming, that this check happens in the runtime it's not possible to find out the port before start up. I guess if we want to automate this process we will need to ask user via some preferences / dialog whether he wants to use local server and where this server is running
> CordovaSim: Can't run default FeedHenry app locally
> ---------------------------------------------------
>
> Key: JBIDE-18900
> URL: https://issues.jboss.org/browse/JBIDE-18900
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: cordovasim
> Affects Versions: 4.2.1.Final
> Reporter: Ilya Buziuk
> Assignee: Burr Sutter
> Fix For: 4.3.0.Alpha1
>
> Attachments: configuration.png, cordovasimFH.png, hello_tom.png, preferences.png, ToolsProject-Cloud-App.zip, ToolsProject-Cordova-App.zip
>
>
> Basically, the situation is the following:
> 1. *ToolsProject-Cordova-App.zip* - is a basic FH hybrid app (all the app does is saying Hello + 'username' from the input field )
> 2. To run this app one simply needs to unpack the archive and import it as a cordova project to the studio
> 3. The application will work with a *remote* server like a charm !hello_tom.png|thumbnail!
> 4. However, there is an option to use *local* server instead of *remote* one
> 5. *ToolsProject-Cloud-App.zip* - is a app for running local server via grunt task runner
> 6. In order to run local server one needs:
> - unpack the app
> - run *npm install .*
> - run *grunt serve*
> Need to find the way to made CordovaSim use this *local* server
--
This message was sent by Atlassian JIRA
(v6.3.11#6341)
11 years, 4 months