June 2016 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-20577) Allow setting exploded or zipped on per-module basis

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20577?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-20577: --------------------------------------- Verified in devstudio-10.0.0.Alpha3-v20160531-1024-B5476-installer-standalone.jar . I had various projects deployed with mixed settings. And one of the project had a utility jar - in this case you can set each independently. Also, Fred's suggested are now included - the settings is disabled when it's disabled. And the note at the top is in bold. > Allow setting exploded or zipped on per-module basis > ---------------------------------------------------- > > Key: JBIDE-20577 > URL: https://issues.jboss.org/browse/JBIDE-20577 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: server > Affects Versions: 4.3.0.CR1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Labels: new_and_noteworthy > Fix For: 4.4.0.Alpha2 > > > While in the past, we automatically zipped up dependent utility projects, we recently switched to allowing exploded utility projects for appserver versions that suppoort it. Some users have determined this is slower for their usecase, and we should investigate giving users more control over this feature. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22325) Clean up enablement on module deploy page of server editor

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22325?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22325. --------------------------------- Verified in devstudio-10.0.0.Alpha3-v20160531-1024-B5476-installer-standalone.jar . I had various projects deployed with mixed settings. And one of the project had a utility jar - in this case you can set each independently. Also, Fred's suggested are now included - the settings is disabled when it's disabled. And the note at the top is in bold. > Clean up enablement on module deploy page of server editor > ---------------------------------------------------------- > > Key: JBIDE-22325 > URL: https://issues.jboss.org/browse/JBIDE-22325 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.4.0.Alpha1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha2 > > > As mentioned in JBIDE-20577, enablement must be more clear. Unfortunately this requires moving a useful utility class from openshift into foundation. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22157) On deployment, utility JAR projects are being exploded on WEB-INF/LIB

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22157?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-22157. --------------------------------- OK, the utility project actually has its own entry in the Deployment tab of the server editor, so one can go ahead and compress only the utility jar and not the encompassing war. So I consider this done then. Verified in JBDS 10.0.0.Alpha3 B5476 > On deployment, 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.Alpha2 > > Attachments: JBIDE22157.zip > > > 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)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22157) On deployment, utility JAR projects are being exploded on WEB-INF/LIB

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22157?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-22157: --------------------------------------- [~rob.stryker], I'm a bit confused. You said this could be fixed in Jasper/WildFly, so that they support exploded jars. And then suddenly you said "pushed to master". But the attached PR actually belongs more to JBIDE-20577 in my opinion - you added per-module zip options, but not an option to keep a utility jar zipped even if the module is exploded, right? > On deployment, 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.Alpha2 > > Attachments: JBIDE22157.zip > > > 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)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22472) Improve UI of per-module zip settings

by Martin Malina (JIRA)

Martin Malina created JBIDE-22472: ------------------------------------- Summary: Improve UI of per-module zip settings Key: JBIDE-22472 URL: https://issues.jboss.org/browse/JBIDE-22472 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: server Affects Versions: 4.4.0.Alpha3 Reporter: Martin Malina Assignee: Rob Stryker This is a follow up of JBIDE-22157 and JBIDE-20577. When you were implementing JBIDE-22157, you asked me for feedback which I gave you but there was no further reply from you: https://github.com/jbosstools/jbosstools-server/pull/412 {quote} what happens if I select to zip all? the new column does not apply then? it would be good to make this obvious somehow. also, could it be a checkbox instead of false/true? {quote} 1) Could we have checkboxes instead of true/false? 2) On a new server adapter, a "false" actually means "see default above" - once you change the default to compress all, each "false" will change to "true". But once you change a module to true and then back to false, changing the default will no longer affect the module settings anymore. This is counter intuitive. So what would make more sense in my opinion is to have checkboxes for each module and then perhaps a link called "all" at the column header? And get rid of the default settings? What do you think? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-21100) start process of WildFly-8.2.0-Final never finish (Starting, Synchronized)

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-21100?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-21100. --------------------------------- > start process of WildFly-8.2.0-Final never finish (Starting, Synchronized) > --------------------------------------------------------------------------- > > Key: JBIDE-21100 > URL: https://issues.jboss.org/browse/JBIDE-21100 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Environment: start process of WildFly-8.2.0-Final never finish (Starting, Synchronized) > Reporter: carl zhang > Assignee: Rob Stryker > Fix For: 4.4.0.Alpha1 > > > please refer to > https://developer.jboss.org/thread/265726?start=0&tstart=0 > refer to the picture of 28-Oct-2015 9:46 AM (layer 3) > In the left panel: WildFly 8.x is configured to connect to localhost > WildFly 8.x(1) is configured to connect to remote host (Linux) > The localhost cannot finish start process. WildFly 8.x(1) (remote) can. > What ports, or temp files, or anything else are checked when changing from starting to started state? -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-719) Fix 'DataTransformationDeploymentEAPTest'

by Tomáš Sedmík (JIRA)

[ https://issues.jboss.org/browse/JBTIS-719?page=com.atlassian.jira.plugin.... ] Tomáš Sedmík edited comment on JBTIS-719 at 6/1/16 7:23 AM: ------------------------------------------------------------ (/) On Mac only: {code} Timeout after: 300 s.: server's state is: Started {code} --> set runtime JRE (JavaSE-1.6 is set as default) was (Author: tsedmik): (x) On Mac only: {code} Timeout after: 300 s.: server's state is: Started {code} --> set runtime JRE (JavaSE-1.6 is set as default) > Fix 'DataTransformationDeploymentEAPTest' > ----------------------------------------- > > Key: JBTIS-719 > URL: https://issues.jboss.org/browse/JBTIS-719 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: Fuse IDE, QE > Affects Versions: 4.3.0.Final > Environment: Fuse on EAP 6.3.0.ER1 > JBDS 9.1.0.GA > JBDSIS 9.0.0.GA > Reporter: Tomáš Sedmík > Assignee: Tomáš Sedmík > Fix For: 4.3.0.Final > > > Fuse on EAP log was slightly changed. > {code} > ...file://src/data) Creating JAXBContext... > {code} > to > {code} > ...file://src/data) Created XMLInputFactory... > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20767) Create tests for the Hbm2DDLExporter facade implementations

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20767?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-20767. ------------------------------------ verified in git > Create tests for the Hbm2DDLExporter facade implementations > ----------------------------------------------------------- > > Key: JBIDE-20767 > URL: https://issues.jboss.org/browse/JBIDE-20767 > Project: Tools (JBoss Tools) > Issue Type: Task > Components: hibernate > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20921) Create tests for HibernateMappingExporterExtension classes

by Rastislav Wagner (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20921?page=com.atlassian.jira.plugi... ] Rastislav Wagner closed JBIDE-20921. ------------------------------------ verified in git > Create tests for HibernateMappingExporterExtension classes > ---------------------------------------------------------- > > Key: JBIDE-20921 > URL: https://issues.jboss.org/browse/JBIDE-20921 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: hibernate > Reporter: Koen Aers > Assignee: Koen Aers > Fix For: 4.4.0.Alpha1 > > -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-725) Fix Model Wizard Test

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-725?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-725: ----------------------------------------- [~mmakovy] please add a repository for the new TD update site to teiid.ui.bot.test/pom.xml. Otherwise, the verification job will fail. > Fix Model Wizard Test > --------------------- > > Key: JBTIS-725 > URL: https://issues.jboss.org/browse/JBTIS-725 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Components: QE, teiid > Affects Versions: 4.3.0.Final > Reporter: Matus Makovy > Assignee: Matus Makovy > Fix For: 4.3.1.Final > > > Fix model names in new Model Wizard -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 10 months

1
0
0 / 0

2026

2025

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues June 2016