[JBoss JIRA] (JBIDE-22157) On deployoment, utility JAR projects are being exploded on WEB-INF/LIB
by Tiago Matias (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22157?page=com.atlassian.jira.plugi... ]
Tiago Matias commented on JBIDE-22157:
--------------------------------------
Thank you. I voted for JBIDE-20577
However, until then is there a work around for this issue ? Downgrade the tools? Eclipse? Wildfly version?
Thanks
> 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] (JBTIS-659) JBTIS Target Platform - Neon
by Paul Leacu (JIRA)
Paul Leacu created JBTIS-659:
--------------------------------
Summary: JBTIS Target Platform - Neon
Key: JBTIS-659
URL: https://issues.jboss.org/browse/JBTIS-659
Project: JBoss Tools Integration Stack
Issue Type: Feature Request
Components: target-platform
Affects Versions: 10.0.0.Beta1-SNAPSHOT
Reporter: Paul Leacu
Assignee: Paul Leacu
Add support for a Neon based JBTIS target platform.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3789) Installer - "Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments"
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3789?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3789:
---------------------------------
Fix Version/s: 9.1.0.GA
> Installer - "Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments"
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3789
> URL: https://issues.jboss.org/browse/JBDS-3789
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer, upstream
> Affects Versions: 9.1.0.CR1
> Reporter: Len DiMaggio
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: havoc
> Fix For: 9.1.0.GA
>
> Attachments: install.log, install_fail.png, log, vagrant.log, vbox.log
>
>
> This issue is being seen with the Setup-bundled-0.0.2-20160411-98 installer
> After an apparently clean/successful install, starting the CDK runtime as a server fails with this error:
> Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments
> Log files and screenshot are attached.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3789) Installer - "Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments"
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3789?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3789:
---------------------------------
Component/s: upstream
> Installer - "Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments"
> -------------------------------------------------------------------------------------------------------------------------
>
> Key: JBDS-3789
> URL: https://issues.jboss.org/browse/JBDS-3789
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer, upstream
> Affects Versions: 9.1.0.CR1
> Reporter: Len DiMaggio
> Assignee: Denis Golovin
> Priority: Blocker
> Labels: havoc
> Attachments: install.log, install_fail.png, log, vagrant.log, vbox.log
>
>
> This issue is being seen with the Setup-bundled-0.0.2-20160411-98 installer
> After an apparently clean/successful install, starting the CDK runtime as a server fails with this error:
> Unable to configure docker and openshift. Calls to vagrant service-manager are returning empty environments
> Log files and screenshot are attached.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years