[JBoss JIRA] (JBIDE-22157) On deployoment, utility JAR projects are being exploded on WEB-INF/LIB
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22157?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-22157:
--------------------------------
Summary: On deployoment, utility JAR projects are being exploded on WEB-INF/LIB (was: On deployoment, dependent JAR's are being exploded on WEB-INF/LIB)
> On deployoment, utility JAR projects are being exploded on WEB-INF/LIB
> ----------------------------------------------------------------------
>
> Key: JBIDE-22157
> URL: https://issues.jboss.org/browse/JBIDE-22157
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Environment: Eclipse: Mars, latest version.
> Webserver: Wilfly 10.0.0
> Maven: 3.3.3
> JBoss Tools: Latest version.
> Reporter: Tiago Matias
> Assignee: Rob Stryker
> Fix For: 4.4.0.Alpha1
>
>
> Consider two eclipse maven projects: A Web project (WAR) and a Utility project JAR with a JSP TLD file inside.
> After building the project and deploying to Wildfly the utiltiy JAR will be exploded under WEB-INF/LIB of the WAR project.
> An exploded jar is incompatible with TLD files since the JSP engine search for the TLD file and then try to open/unzip the JAR. Since the JAR is just a folder, it causes an "Access Denied" exception, as shown below:
> org.apache.jasper.JasperException: java.io.FileNotFoundException: C:\Program Files\Java\wildfly-10.0.0.Final\standalone\deployments\portal.web.war\WEB-INF\lib\portal.framework-0.0.1-SNAPSHOT.jar (Acesso negado)
> org.apache.jasper.compiler.TagLibraryInfoImpl.<init>(TagLibraryInfoImpl.java:151)
> org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:412)
> org.apache.jasper.compiler.Parser.parseDirective(Parser.java:475)
> org.apache.jasper.compiler.Parser.parseElements(Parser.java:1456)
> org.apache.jasper.compiler.Parser.parse(Parser.java:143)
> A possible alternative would be to turnoff the option "Resolve dependencies from workspace projects" in Eclipse. In this scenario the JAR won't get exploded on WAR's WEB-INF/lib and everything works. However, any change to the JAR project won't get picked up and deployed to the target unless it's POM version is incremented which is incompatible with a development scenario where the projects are constantly updated and built.
> I request that the eclipse wildfly connector provides an option to control weather the dependency JAR's are exploded or not into the final deployment.
> Please note, this only applies to dependencies that are workspace projects. All the other dependencies (spring, hibernate, etc...) are simply copied as a JAR archive, as expected.
> Thank you.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22157) On deployoment, utility JAR projects are being exploded on WEB-INF/LIB
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22157?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-22157:
--------------------------------
Fix Version/s: 4.4.0.Alpha1
> On deployoment, utility JAR projects are being exploded on WEB-INF/LIB
> ----------------------------------------------------------------------
>
> Key: JBIDE-22157
> URL: https://issues.jboss.org/browse/JBIDE-22157
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Environment: Eclipse: Mars, latest version.
> Webserver: Wilfly 10.0.0
> Maven: 3.3.3
> JBoss Tools: Latest version.
> Reporter: Tiago Matias
> Assignee: Rob Stryker
> Fix For: 4.4.0.Alpha1
>
>
> Consider two eclipse maven projects: A Web project (WAR) and a Utility project JAR with a JSP TLD file inside.
> After building the project and deploying to Wildfly the utiltiy JAR will be exploded under WEB-INF/LIB of the WAR project.
> An exploded jar is incompatible with TLD files since the JSP engine search for the TLD file and then try to open/unzip the JAR. Since the JAR is just a folder, it causes an "Access Denied" exception, as shown below:
> org.apache.jasper.JasperException: java.io.FileNotFoundException: C:\Program Files\Java\wildfly-10.0.0.Final\standalone\deployments\portal.web.war\WEB-INF\lib\portal.framework-0.0.1-SNAPSHOT.jar (Acesso negado)
> org.apache.jasper.compiler.TagLibraryInfoImpl.<init>(TagLibraryInfoImpl.java:151)
> org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:412)
> org.apache.jasper.compiler.Parser.parseDirective(Parser.java:475)
> org.apache.jasper.compiler.Parser.parseElements(Parser.java:1456)
> org.apache.jasper.compiler.Parser.parse(Parser.java:143)
> A possible alternative would be to turnoff the option "Resolve dependencies from workspace projects" in Eclipse. In this scenario the JAR won't get exploded on WAR's WEB-INF/lib and everything works. However, any change to the JAR project won't get picked up and deployed to the target unless it's POM version is incremented which is incompatible with a development scenario where the projects are constantly updated and built.
> I request that the eclipse wildfly connector provides an option to control weather the dependency JAR's are exploded or not into the final deployment.
> Please note, this only applies to dependencies that are workspace projects. All the other dependencies (spring, hibernate, etc...) are simply copied as a JAR archive, as expected.
> Thank you.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22134) Sometimes docker image data are not shown in Deploy to OpenShift wizard
by Jeff Cantrill (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22134?page=com.atlassian.jira.plugi... ]
Jeff Cantrill commented on JBIDE-22134:
---------------------------------------
I am unable to reproduce using master. Looking at the trace log, I see the import command failing against the internal registry and falling back to query dockerhub. This call succeeds and the env vars and ports are available.
> Sometimes docker image data are not shown in Deploy to OpenShift wizard
> -----------------------------------------------------------------------
>
> Key: JBIDE-22134
> URL: https://issues.jboss.org/browse/JBIDE-22134
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: openshift
> Affects Versions: 4.3.1.CR1
> Reporter: Marián Labuda
> Assignee: Jeff Cantrill
> Labels: docker, openshift_v3
> Fix For: 4.4.0.Alpha1
>
>
> Sometimes docker image data are not shown/processed in Deploy to OpenShift wizard. Environment variables, exposed ports etc. Unfortunately I don't have a way to reproduce it 100 %, I am not sure at the moment what is causing it, but when deploying a local docker image (image already pulled) to OpenShift, environment variables and exposed ports are empty, even though when using an image which has not been pulled yet, I have not spotted this at all.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22157) On deployoment, dependent JAR's are being exploded on WEB-INF/LIB
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22157?page=com.atlassian.jira.plugi... ]
Alexey Kazakov updated JBIDE-22157:
-----------------------------------
Component/s: server
> On deployoment, dependent JAR's are being exploded on WEB-INF/LIB
> -----------------------------------------------------------------
>
> Key: JBIDE-22157
> URL: https://issues.jboss.org/browse/JBIDE-22157
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Environment: Eclipse: Mars, latest version.
> Webserver: Wilfly 10.0.0
> Maven: 3.3.3
> JBoss Tools: Latest version.
> Reporter: Tiago Matias
>
> Consider two eclipse maven projects: A Web project (WAR) and a Utility project JAR with a JSP TLD file inside.
> After building the project and deploying to Wildfly the utiltiy JAR will be exploded under WEB-INF/LIB of the WAR project.
> An exploded jar is incompatible with TLD files since the JSP engine search for the TLD file and then try to open/unzip the JAR. Since the JAR is just a folder, it causes an "Access Denied" exception, as shown below:
> org.apache.jasper.JasperException: java.io.FileNotFoundException: C:\Program Files\Java\wildfly-10.0.0.Final\standalone\deployments\portal.web.war\WEB-INF\lib\portal.framework-0.0.1-SNAPSHOT.jar (Acesso negado)
> org.apache.jasper.compiler.TagLibraryInfoImpl.<init>(TagLibraryInfoImpl.java:151)
> org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:412)
> org.apache.jasper.compiler.Parser.parseDirective(Parser.java:475)
> org.apache.jasper.compiler.Parser.parseElements(Parser.java:1456)
> org.apache.jasper.compiler.Parser.parse(Parser.java:143)
> A possible alternative would be to turnoff the option "Resolve dependencies from workspace projects" in Eclipse. In this scenario the JAR won't get exploded on WAR's WEB-INF/lib and everything works. However, any change to the JAR project won't get picked up and deployed to the target unless it's POM version is incremented which is incompatible with a development scenario where the projects are constantly updated and built.
> I request that the eclipse wildfly connector provides an option to control weather the dependency JAR's are exploded or not into the final deployment.
> Please note, this only applies to dependencies that are workspace projects. All the other dependencies (spring, hibernate, etc...) are simply copied as a JAR archive, as expected.
> Thank you.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-22157) On deployoment, dependent JAR's are being exploded on WEB-INF/LIB
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22157?page=com.atlassian.jira.plugi... ]
Alexey Kazakov reassigned JBIDE-22157:
--------------------------------------
Assignee: Rob Stryker
> On deployoment, dependent JAR's are being exploded on WEB-INF/LIB
> -----------------------------------------------------------------
>
> Key: JBIDE-22157
> URL: https://issues.jboss.org/browse/JBIDE-22157
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Environment: Eclipse: Mars, latest version.
> Webserver: Wilfly 10.0.0
> Maven: 3.3.3
> JBoss Tools: Latest version.
> Reporter: Tiago Matias
> Assignee: Rob Stryker
>
> Consider two eclipse maven projects: A Web project (WAR) and a Utility project JAR with a JSP TLD file inside.
> After building the project and deploying to Wildfly the utiltiy JAR will be exploded under WEB-INF/LIB of the WAR project.
> An exploded jar is incompatible with TLD files since the JSP engine search for the TLD file and then try to open/unzip the JAR. Since the JAR is just a folder, it causes an "Access Denied" exception, as shown below:
> org.apache.jasper.JasperException: java.io.FileNotFoundException: C:\Program Files\Java\wildfly-10.0.0.Final\standalone\deployments\portal.web.war\WEB-INF\lib\portal.framework-0.0.1-SNAPSHOT.jar (Acesso negado)
> org.apache.jasper.compiler.TagLibraryInfoImpl.<init>(TagLibraryInfoImpl.java:151)
> org.apache.jasper.compiler.Parser.parseTaglibDirective(Parser.java:412)
> org.apache.jasper.compiler.Parser.parseDirective(Parser.java:475)
> org.apache.jasper.compiler.Parser.parseElements(Parser.java:1456)
> org.apache.jasper.compiler.Parser.parse(Parser.java:143)
> A possible alternative would be to turnoff the option "Resolve dependencies from workspace projects" in Eclipse. In this scenario the JAR won't get exploded on WAR's WEB-INF/lib and everything works. However, any change to the JAR project won't get picked up and deployed to the target unless it's POM version is incremented which is incompatible with a development scenario where the projects are constantly updated and built.
> I request that the eclipse wildfly connector provides an option to control weather the dependency JAR's are exploded or not into the final deployment.
> Please note, this only applies to dependencies that are workspace projects. All the other dependencies (spring, hibernate, etc...) are simply copied as a JAR archive, as expected.
> Thank you.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (ERT-91) bower dependency content assist is broken [EBZ#487888]
by Gorkem Ercan (JIRA)
[ https://issues.jboss.org/browse/ERT-91?page=com.atlassian.jira.plugin.sys... ]
Gorkem Ercan updated ERT-91:
----------------------------
Sprint: devex #6 April 2016 (was: devex #5 April 2016)
> bower dependency content assist is broken [EBZ#487888]
> ------------------------------------------------------
>
> Key: ERT-91
> URL: https://issues.jboss.org/browse/ERT-91
> Project: Eclipse Release Train
> Issue Type: Task
> Components: WTP Source Editing
> Reporter: Friendly Jira Robot
> Labels: 3.8_M7, bzira, wst.json
> Fix For: Neon (4.6) M7
>
>
> The content assist has stopped working for me and started to constantly throw the exceptions (see below). The problem might be occurring because either the URL that is used to get the dependency proposals has stopped working or the site was/is just shut down for some purpose.
> But anyway, probably just the displaying such a stack trace in the console is not a proper way to notify a user on the problem. We should properly log it into the Error Log instead.
> The stack trace appearing in the console:
> !ENTRY org.eclipse.wst.json.ui 4 4 2016-02-16 06:51:31.376
> !MESSAGE org.eclipse.json.provisonnal.com.eclipsesource.json.ParseException: Expected value at 1:0
> !STACK 0
> java.io.IOException: org.eclipse.json.provisonnal.com.eclipsesource.json.ParseException: Expected value at 1:0
> at org.eclipse.json.http.HttpHelper.makeRequest(HttpHelper.java:74)
> at org.eclipse.wst.json.ui.contentassist.HttpCompletionProposalCollector.addProposals(HttpCompletionProposalCollector.java:28)
> at org.eclipse.wst.json.ui.internal.contentassist.CompletionProposalMatcher.addProposalsIfMatch(CompletionProposalMatcher.java:42)
> at org.eclipse.wst.json.ui.internal.contentassist.CompletionProposalCollectorsRegistryReader.addProposals(CompletionProposalCollectorsRegistryReader.java:62)
> at org.eclipse.wst.json.ui.internal.contentassist.JSONCompletionProposalComputer.collectProposalsFromExtensionPoint(JSONCompletionProposalComputer.java:56)
> at org.eclipse.wst.json.ui.internal.contentassist.JSONCompletionProposalComputer.addObjectKeyProposals(JSONCompletionProposalComputer.java:43)
> at org.eclipse.wst.json.ui.contentassist.AbstractJSONCompletionProposalComputer.computeObjectKeyProposals(AbstractJSONCompletionProposalComputer.java:197)
> at org.eclipse.wst.json.ui.contentassist.AbstractJSONCompletionProposalComputer.computeCompletionProposals(AbstractJSONCompletionProposalComputer.java:153)
> at org.eclipse.wst.json.ui.contentassist.AbstractJSONCompletionProposalComputer.computeCompletionProposals(AbstractJSONCompletionProposalComputer.java:82)
> at org.eclipse.wst.sse.ui.internal.contentassist.CompletionProposalComputerDescriptor.computeCompletionProposals(CompletionProposalComputerDescriptor.java:284)
> at org.eclipse.wst.sse.ui.internal.contentassist.CompletionProposalCategory.computeCompletionProposals(CompletionProposalCategory.java:290)
> at org.eclipse.wst.sse.ui.contentassist.StructuredContentAssistProcessor.collectProposals(StructuredContentAssistProcessor.java:484)
> at org.eclipse.wst.sse.ui.contentassist.StructuredContentAssistProcessor.computeCompletionProposals(StructuredContentAssistProcessor.java:255)
> at org.eclipse.wst.sse.ui.internal.contentassist.CompoundContentAssistProcessor.computeCompletionProposals(CompoundContentAssistProcessor.java:127)
> at org.eclipse.jface.text.contentassist.ContentAssistant$5.run(ContentAssistant.java:1904)
> at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42)
> at org.eclipse.jface.text.contentassist.ContentAssistant.computeCompletionProposals(ContentAssistant.java:1902)
> at org.eclipse.jface.text.contentassist.CompletionProposalPopup.computeProposals(CompletionProposalPopup.java:573)
> at org.eclipse.jface.text.contentassist.CompletionProposalPopup.access$16(CompletionProposalPopup.java:570)
> at org.eclipse.jface.text.contentassist.CompletionProposalPopup$2.run(CompletionProposalPopup.java:505)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.jface.text.contentassist.CompletionProposalPopup.showProposals(CompletionProposalPopup.java:499)
> at org.eclipse.jface.text.contentassist.ContentAssistant.showPossibleCompletions(ContentAssistant.java:1720)
> at org.eclipse.wst.sse.ui.internal.StructuredTextViewer.doOperation(StructuredTextViewer.java:488)
> at org.eclipse.ui.texteditor.ContentAssistAction$1.run(ContentAssistAction.java:82)
> at org.eclipse.swt.custom.BusyIndicator.showWhile(BusyIndicator.java:70)
> at org.eclipse.ui.texteditor.ContentAssistAction.run(ContentAssistAction.java:80)
> at org.eclipse.jface.action.Action.runWithEvent(Action.java:473)
> at org.eclipse.jface.commands.ActionHandler.execute(ActionHandler.java:122)
> 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:56)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invokeUsingClass(InjectorImpl.java:252)
> at org.eclipse.e4.core.internal.di.InjectorImpl.invoke(InjectorImpl.java:234)
> at org.eclipse.e4.core.contexts.ContextInjectionFactory.invoke(ContextInjectionFactory.java:132)
> at org.eclipse.e4.core.commands.internal.HandlerServiceHandler.execute(HandlerServiceHandler.java:152)
> at org.eclipse.core.commands.Command.executeWithChecks(Command.java:493)
> at org.eclipse.core.commands.ParameterizedCommand.executeWithChecks(ParameterizedCommand.java:486)
> at org.eclipse.e4.core.commands.internal.HandlerServiceImpl.executeHandler(HandlerServiceImpl.java:210)
> at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.executeCommand(KeyBindingDispatcher.java:286)
> at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.press(KeyBindingDispatcher.java:507)
> at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.processKeyEvent(KeyBindingDispatcher.java:558)
> at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.filterKeySequenceBindings(KeyBindingDispatcher.java:378)
> at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher.access$0(KeyBindingDispatcher.java:324)
> at org.eclipse.e4.ui.bindings.keys.KeyBindingDispatcher$KeyDownFilter.handleEvent(KeyBindingDispatcher.java:86)
> at org.eclipse.swt.widgets.EventTable.sendEvent(EventTable.java:84)
> at org.eclipse.swt.widgets.Display.filterEvent(Display.java:1550)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1328)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1353)
> at org.eclipse.swt.widgets.Widget.sendEvent(Widget.java:1338)
> at org.eclipse.swt.widgets.Widget.sendKeyEvent(Widget.java:1365)
> at org.eclipse.swt.widgets.Widget.gtk_key_press_event(Widget.java:763)
> at org.eclipse.swt.widgets.Control.gtk_key_press_event(Control.java:3317)
> at org.eclipse.swt.widgets.Composite.gtk_key_press_event(Composite.java:785)
> at org.eclipse.swt.widgets.Widget.windowProc(Widget.java:1980)
> at org.eclipse.swt.widgets.Control.windowProc(Control.java:5590)
> at org.eclipse.swt.widgets.Display.windowProc(Display.java:4717)
> at org.eclipse.swt.internal.gtk.OS._gtk_main_do_event(Native Method)
> at org.eclipse.swt.internal.gtk.OS.gtk_main_do_event(OS.java:9279)
> at org.eclipse.swt.widgets.Display.eventProc(Display.java:1225)
> at org.eclipse.swt.internal.gtk.OS._g_main_context_iteration(Native Method)
> at org.eclipse.swt.internal.gtk.OS.g_main_context_iteration(OS.java:2425)
> at org.eclipse.swt.widgets.Display.readAndDispatch(Display.java:3428)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine$4.run(PartRenderingEngine.java:1127)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.e4.ui.internal.workbench.swt.PartRenderingEngine.run(PartRenderingEngine.java:1018)
> at org.eclipse.e4.ui.internal.workbench.E4Workbench.createAndRunUI(E4Workbench.java:156)
> at org.eclipse.ui.internal.Workbench$5.run(Workbench.java:654)
> at org.eclipse.core.databinding.observable.Realm.runWithDefault(Realm.java:337)
> at org.eclipse.ui.internal.Workbench.createAndRunWorkbench(Workbench.java:598)
> at org.eclipse.ui.PlatformUI.createAndRunWorkbench(PlatformUI.java:150)
> at org.eclipse.ui.internal.ide.application.IDEApplication.start(IDEApplication.java:139)
> 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:669)
> at org.eclipse.equinox.launcher.Main.basicRun(Main.java:608)
> at org.eclipse.equinox.launcher.Main.run(Main.java:1515)
> at org.eclipse.equinox.launcher.Main.main(Main.java:1488)
> Caused by: org.eclipse.json.provisonnal.com.eclipsesource.json.ParseException: Expected value at 1:0
> at org.eclipse.json.provisonnal.com.eclipsesource.json.JsonParser.error(JsonParser.java:368)
> at org.eclipse.json.provisonnal.com.eclipsesource.json.JsonParser.expected(JsonParser.java:361)
> at org.eclipse.json.provisonnal.com.eclipsesource.json.JsonParser.readValue(JsonParser.java:97)
> at org.eclipse.json.provisonnal.com.eclipsesource.json.JsonParser.parse(JsonParser.java:62)
> at org.eclipse.json.provisonnal.com.eclipsesource.json.JsonValue.readFrom(JsonValue.java:91)
> at org.eclipse.json.http.HttpHelper.makeRequest(HttpHelper.java:70)
> ... 87 more
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years