[JBoss JIRA] (JBIDE-17944) BrowserSim: Use http: protocol instead of file: for accessing local files
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17944?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-17944:
---------------------------------------------
I think browsersim should support file:// natively.
But there is a point in having the option to "simulate" standalone apps, but for that we already have livereload that can serve out content via http (but it doesn't know about web content root ;/)
One could argue maybe preview should get more of the features browsersim has (mobile support etc.)
I think there is a middle ground to be found though - but not sure how to do it without making it utterly complex to manage ;)
> BrowserSim: Use http: protocol instead of file: for accessing local files
> -------------------------------------------------------------------------
>
> Key: JBIDE-17944
> URL: https://issues.jboss.org/browse/JBIDE-17944
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: browsersim
> Reporter: Alexey Kazakov
> Assignee: Konstantin Marmalyukov
> Fix For: 4.3.0.Alpha1
>
>
> Currently, BrowserSim works through file: protocol but this protocol doesn't work well with paths relative to the webroot (which start with "/").
> So if a local file contains any links to local resources (css, js, ...) via relative paths then these resources are not available in BrowserSim.
> For example all official ionic example projects use such paths. It makes "open with BrowserSim" feature useless for those projects.
> It would be great if BrowserSim uses http: as our HTML5 preview does.
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17010) Hibernate schema update error while deploying Seam Portlet on JPP 6.1.1
by Snjezana Peco (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17010?page=com.atlassian.jira.plugi... ]
Snjezana Peco resolved JBIDE-17010.
-----------------------------------
Resolution: Cannot Reproduce Bug
Please reopen the jira if you can reproduce the issue with the New Web Seam Project wizard.
> Hibernate schema update error while deploying Seam Portlet on JPP 6.1.1
> -----------------------------------------------------------------------
>
> Key: JBIDE-17010
> URL: https://issues.jboss.org/browse/JBIDE-17010
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: portal-gatein
> Affects Versions: 4.2.0.Beta1
> Environment: JPP 6.1.1, Seam 2.3.2, Portlet Bridge 3.2.1, Database: HSQL (DefaultDS)
> Reporter: Radoslav Rábara
> Assignee: Snjezana Peco
> Fix For: 4.2.0.CR1
>
> Attachments: jpp611.log
>
>
> There is an error in console output when seam portlet is deployed to JPP 6.1.1.
> {code}
> ERROR [org.hibernate.tool.hbm2ddl.SchemaUpdate] (ServerService Thread Pool -- 84) HHH000299: Could not complete schema update: java.lang.NullPointerException
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-9641) Allow plugins to contribute Forge components
by George Gastaldi (JIRA)
[ https://issues.jboss.org/browse/JBIDE-9641?page=com.atlassian.jira.plugin... ]
George Gastaldi closed JBIDE-9641.
----------------------------------
Fix Version/s: (was: 4.2.x)
Resolution: Duplicate Issue
Already implemented in JBIDE-17930
> Allow plugins to contribute Forge components
> --------------------------------------------
>
> Key: JBIDE-9641
> URL: https://issues.jboss.org/browse/JBIDE-9641
> Project: Tools (JBoss Tools)
> Issue Type: Enhancement
> Components: forge
> Reporter: Rob Cernich
> Assignee: Koen Aers
>
> It would be nice if Forge components could be contributed through an extension point. This would allow components supplied by other projects (e.g. SwitchYard) to bundle their plugins in an Eclipse plugin and have them available automatically.
> This would also help ensure the Forge plugins are compatible with the Forge installation used within Eclipse.
> (I think the current integration, adding <user>/.forge/plugins, could leak incompatible Forge plugins into the Eclipse integration. Just my two cents.)
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-16597) OpenShift Server Adapter: Open launch configuration cause error
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16597?page=com.atlassian.jira.plugi... ]
Andre Dietisheim updated JBIDE-16597:
-------------------------------------
Fix Version/s: 4.3.x
(was: 4.2.0.CR1)
> OpenShift Server Adapter: Open launch configuration cause error
> ---------------------------------------------------------------
>
> Key: JBIDE-16597
> URL: https://issues.jboss.org/browse/JBIDE-16597
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Alpha2
> Reporter: Marián Labuda
> Priority: Minor
> Labels: server_adapter_editor
> Fix For: 4.3.x
>
> Attachments: open_launch_config1.png, open_launch_config2.png, open_launch_config3.png
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> In OpenShift server adapter settings is Open launch configuration link. Throws error after click on it. See attached images and error log:
> {code:title=.log}
> !ENTRY org.eclipse.ui 4 0 2014-02-17 13:45:08.437
> !MESSAGE Unhandled event loop exception
> !STACK 0
> java.lang.NullPointerException
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.handleApplyPressed(LaunchConfigurationTabGroupViewer.java:1401)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer$3.widgetSelected(LaunchConfigurationTabGroupViewer.java:308)
> 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:4423)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3771)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3391)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.open(LaunchConfigurationsDialog.java:1154)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationPropertiesDialog.open(LaunchConfigurationPropertiesDialog.java:213)
> at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationPropertiesDialog(DebugUITools.java:661)
> at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationPropertiesDialog(DebugUITools.java:638)
> at org.eclipse.wst.server.ui.internal.editor.OverviewEditorPart$9.linkActivated(OverviewEditorPart.java:594)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:327)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:311)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:125)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4423)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3771)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3391)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1122)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1006)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:146)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:615)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:566)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:125)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:109)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:80)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:372)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:226)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17986) Bundled version of m2e-mavenarchiver is broken
by Rich DiCroce (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17986?page=com.atlassian.jira.plugi... ]
Rich DiCroce commented on JBIDE-17986:
--------------------------------------
[~maxandersen] The problem occurred on all of the Maven projects I looked at, except the ones with WAR packaging because m2e-wtp has special handling for those. You should be able to reproduce the problem by setting up a stock Luna install and then installing the Abridged JBoss Tools package. The result is not a failure exactly, in that there's no error message. The pom.properties file just isn't generated.
> Bundled version of m2e-mavenarchiver is broken
> ----------------------------------------------
>
> Key: JBIDE-17986
> URL: https://issues.jboss.org/browse/JBIDE-17986
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: central, discovery, maven, target-platform
> Affects Versions: 4.2.0.Beta3
> Reporter: Rich DiCroce
> Assignee: Nick Boldt
> Fix For: 4.2.0.CR1
>
>
> The version of m2e-mavenarchiver that is bundled in JBoss Tools seems to be broken. I was not getting any descriptors generated. Upgrading to the latest version fixes the problem. See http://repository.takari.io:8081/nexus/content/sites/m2e.extras/m2eclipse...
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-16597) OpenShift Server Adapter: Open launch configuration cause error
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBIDE-16597?page=com.atlassian.jira.plugi... ]
Andre Dietisheim commented on JBIDE-16597:
------------------------------------------
postponed to 4.3.x since went out of time for 4.2.0.CR1
> OpenShift Server Adapter: Open launch configuration cause error
> ---------------------------------------------------------------
>
> Key: JBIDE-16597
> URL: https://issues.jboss.org/browse/JBIDE-16597
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.2.0.Alpha2
> Reporter: Marián Labuda
> Priority: Minor
> Labels: server_adapter_editor
> Fix For: 4.3.x
>
> Attachments: open_launch_config1.png, open_launch_config2.png, open_launch_config3.png
>
> Original Estimate: 1 day
> Remaining Estimate: 1 day
>
> In OpenShift server adapter settings is Open launch configuration link. Throws error after click on it. See attached images and error log:
> {code:title=.log}
> !ENTRY org.eclipse.ui 4 0 2014-02-17 13:45:08.437
> !MESSAGE Unhandled event loop exception
> !STACK 0
> java.lang.NullPointerException
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer.handleApplyPressed(LaunchConfigurationTabGroupViewer.java:1401)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationTabGroupViewer$3.widgetSelected(LaunchConfigurationTabGroupViewer.java:308)
> 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:4423)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3771)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3391)
> at org.eclipse.jface.window.Window.runEventLoop(Window.java:827)
> at org.eclipse.jface.window.Window.open(Window.java:803)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationsDialog.open(LaunchConfigurationsDialog.java:1154)
> at org.eclipse.debug.internal.ui.launchConfigurations.LaunchConfigurationPropertiesDialog.open(LaunchConfigurationPropertiesDialog.java:213)
> at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationPropertiesDialog(DebugUITools.java:661)
> at org.eclipse.debug.ui.DebugUITools.openLaunchConfigurationPropertiesDialog(DebugUITools.java:638)
> at org.eclipse.wst.server.ui.internal.editor.OverviewEditorPart$9.linkActivated(OverviewEditorPart.java:594)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleActivate(AbstractHyperlink.java:233)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.handleMouseUp(AbstractHyperlink.java:327)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink.access$2(AbstractHyperlink.java:311)
> at org.eclipse.ui.forms.widgets.AbstractHyperlink$4.handleEvent(AbstractHyperlink.java:125)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.sendEvent(Display.java:4423)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1388)
> at org.eclipse.swt.widgets.Display.runDeferredEvents(Display.java:3771)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3391)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$9.run(PartRenderingEngine.java:1122)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1006)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:146)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:615)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:332)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:566)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:125)
> at org.eclipse.equinox.internal.app.EclipseAppHandle.run(EclipseAppHandle.java:196)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.runApplication(EclipseAppLauncher.java:109)
> at org.eclipse.core.runtime.internal.adaptor.EclipseAppLauncher.start(EclipseAppLauncher.java:80)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:372)
> at org.eclipse.core.runtime.adaptor.EclipseStarter.run(EclipseStarter.java:226)
> at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57)
> at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
> at java.lang.reflect.Method.invoke(Method.java:606)
> at org.eclipse.equinox.launcher.Main.invokeFramework(Main.java:636)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:591)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1450)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1426)
> {code}
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months
[JBoss JIRA] (JBIDE-17998) Use better <name> in pom file
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17998?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-17998:
---------------------------------------------
yeah its just the descriptive name I believe. does not change the GAV parts of the identification.
It will change the output in the mvn builds so the names should still be unique.
> Use better <name> in pom file
> -----------------------------
>
> Key: JBIDE-17998
> URL: https://issues.jboss.org/browse/JBIDE-17998
> Project: Tools (JBoss Tools)
> Issue Type: Sub-task
> Components: build
> Reporter: Mickael Istria
> Assignee: Mickael Istria
> Fix For: 4.2.0.CR1
>
>
> In order to improve identification of jbosstools related reports on SonarQube, the <name> in pom files should be:
> * For the root pom, same name as the GitHub repo. Eg jbosstools-webservices, jbosstools-server...
> * For the children, <name-of-repo>.<name-of-artifact>. Eg jbosstools-webservices.features, jbosstools-server.jmx.plugins...
--
This message was sent by Atlassian JIRA
(v6.2.6#6264)
11 years, 8 months