April 2016 - jbosstools-issues - Jboss List Archives

[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 commented on JBIDE-22157: ------------------------------------- This would be a regression from JBIDE-20071 > 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-20937) Create resource(s) from json

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20937?page=com.atlassian.jira.plugi... ] Jeff Cantrill commented on JBIDE-20937: --------------------------------------- Per my discussion with [~fbricon], the first pass of this feature will only allow you to select a file to create resources; editing will be a follow on enhancement. > Create resource(s) from json > ---------------------------- > > Key: JBIDE-20937 > URL: https://issues.jboss.org/browse/JBIDE-20937 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR2 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: New Resource Wizard Mockup.bmml, New Resource Wizard Mockup.png > > > It would be nice to have feature to create a new resource, e.g. image stream or pod, from provided json. Similar to "oc create -f some_resource.json" > Currently it would be very usable for MW application templates, because jboss-eap basic s2i template requires image stream which is defined in another json. Also there are applications which are consisting of separately defined resources (e.g. in openshift origin repo is hello world application and its having defined pod in separated json). > This could be available via context menu New - Resource (like we have for application, projects and connections). And it could be accessible via context menu of a project and specific resource type (e.g. for tree item Image Streams). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-20937) Create resource(s) from json

by Jeff Cantrill (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20937?page=com.atlassian.jira.plugi... ] Jeff Cantrill reassigned JBIDE-20937: ------------------------------------- Assignee: Jeff Cantrill > Create resource(s) from json > ---------------------------- > > Key: JBIDE-20937 > URL: https://issues.jboss.org/browse/JBIDE-20937 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: openshift > Affects Versions: 4.3.0.CR2 > Reporter: Marián Labuda > Assignee: Jeff Cantrill > Priority: Critical > Fix For: 4.4.0.Alpha1 > > Attachments: New Resource Wizard Mockup.bmml, New Resource Wizard Mockup.png > > > It would be nice to have feature to create a new resource, e.g. image stream or pod, from provided json. Similar to "oc create -f some_resource.json" > Currently it would be very usable for MW application templates, because jboss-eap basic s2i template requires image stream which is defined in another json. Also there are applications which are consisting of separately defined resources (e.g. in openshift origin repo is hello world application and its having defined pod in separated json). > This could be available via context menu New - Resource (like we have for application, projects and connections). And it could be accessible via context menu of a project and specific resource type (e.g. for tree item Image Streams). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-22132) Resource name is badly generated in Deploy to Openshift wizard

by Viacheslav Kabanovich (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22132?page=com.atlassian.jira.plugi... ] Viacheslav Kabanovich commented on JBIDE-22132: ----------------------------------------------- After having automatically cut the name to the size limit, we also have to remove trailing '-' symbols as name cannot end with it. > Resource name is badly generated in Deploy to Openshift wizard > -------------------------------------------------------------- > > Key: JBIDE-22132 > URL: https://issues.jboss.org/browse/JBIDE-22132 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: openshift > Reporter: Jeff MAURY > Assignee: Jeff MAURY > Fix For: 4.4.x > > > When the wizard for deploying a Docker image to Openshift is displayed, the resource name is derived from the image name. But as the '_' seems to be forbidden, an error is generated each time the image name contains this character. Maybe worth replacing with '-' when the resource name is generated -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-110) CA shows property names in dependency proposals for bower/npm [EBZ#488100]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-110?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-110: ----------------------------- Story Points: 5 > CA shows property names in dependency proposals for bower/npm [EBZ#488100] > -------------------------------------------------------------------------- > > Key: ERT-110 > URL: https://issues.jboss.org/browse/ERT-110 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Labels: bzira, wst.json > > There shouldn't be any of property proposals shown when a user invokes content assistant for dependencies. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-110) CA shows property names in dependency proposals for bower/npm [EBZ#488100]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-110?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-110: ----------------------------- Sprint: devex #6 April 2016 > CA shows property names in dependency proposals for bower/npm [EBZ#488100] > -------------------------------------------------------------------------- > > Key: ERT-110 > URL: https://issues.jboss.org/browse/ERT-110 > Project: Eclipse Release Train > Issue Type: Task > Components: WTP Source Editing > Reporter: Friendly Jira Robot > Labels: bzira, wst.json > > There shouldn't be any of property proposals shown when a user invokes content assistant for dependencies. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-112) [debug] Better JavaScript hot replace support for Chromium/V8 debugger [EBZ#488344]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-112?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-112: ----------------------------- Story Points: 25 > [debug] Better JavaScript hot replace support for Chromium/V8 debugger [EBZ#488344] > ----------------------------------------------------------------------------------- > > Key: ERT-112 > URL: https://issues.jboss.org/browse/ERT-112 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Labels: Debug, bzira > > Current Chrome/V8 debugger contribution supports hot deployment for changed .js file to JavaScript MV running in debug mode. It can be done by selecting action from context menu on changed .js file opened in JS Editor from Debug session virtual file system. > This feature should be supported for editing .js files in eclipse workspace as well. When debugging session is on and .js file is changed IDE should check if it is used in current debugging session and ask if it should be hot deployed to JavaScript VM. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-98) V8 Debugging Menu is shown on too many places [EBZ#488865]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-98?page=com.atlassian.jira.plugin.sys... ] Gorkem Ercan updated ERT-98: ---------------------------- Story Points: 5 > V8 Debugging Menu is shown on too many places [EBZ#488865] > ---------------------------------------------------------- > > Key: ERT-98 > URL: https://issues.jboss.org/browse/ERT-98 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Nick Boldt > Labels: Debug, bzira > > V8 debugging menu is very eager. We should tune down the places that it is shown. Also we need to consider if the menu is still needed after our integration. -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-121) [content assist] Content Assist templates still contain traces of Java [EBZ#489320]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-121?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-121: ----------------------------- Story Points: 2 > [content assist] Content Assist templates still contain traces of Java [EBZ#489320] > ----------------------------------------------------------------------------------- > > Key: ERT-121 > URL: https://issues.jboss.org/browse/ERT-121 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Labels: General, bzira > > Each content assist template should be reviewed such that it is applicable to JavaScript developers. > For instance, here's an excerpt from the live JSDT catchblock template: > ${exception_var}.printStackTrace() -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

1
0
0 / 0

[JBoss JIRA] (ERT-121) [content assist] Content Assist templates still contain traces of Java [EBZ#489320]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-121?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-121: ----------------------------- Sprint: devex #6 April 2016 > [content assist] Content Assist templates still contain traces of Java [EBZ#489320] > ----------------------------------------------------------------------------------- > > Key: ERT-121 > URL: https://issues.jboss.org/browse/ERT-121 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Labels: General, bzira > > Each content assist template should be reviewed such that it is applicable to JavaScript developers. > For instance, here's an excerpt from the live JSDT catchblock template: > ${exception_var}.printStackTrace() -- This message was sent by Atlassian JIRA (v6.4.11#64026)

10 years

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 April 2016