[JBoss JIRA] (JBDS-3793) On Windows 10 (4K Display), installer dialogs are too small and cannot be resized
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3793?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov reassigned JBDS-3793:
------------------------------------
Assignee: Denis Golovin
> On Windows 10 (4K Display), installer dialogs are too small and cannot be resized
> ---------------------------------------------------------------------------------
>
> Key: JBDS-3793
> URL: https://issues.jboss.org/browse/JBDS-3793
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Environment: Version: 9.1.0.GA
> Build id: GA-v20160410-1849-B495
> Build date: 20160410-1849
> Windows 10
> 4K Display
> Reporter: Len DiMaggio
> Assignee: Denis Golovin
> Attachments: installer.png
>
>
> See the attached screenshot - This issue has been raised before regarding the default size used for the JBDS IDE display - the issues that are specific to the JBDS installer is that the small sized dialogs obscure user-editable fields and and that the dialogs cannot be resized.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBIDE-20937) Create resource(s) from json
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20937?page=com.atlassian.jira.plugi... ]
Fred Bricon commented on JBIDE-20937:
-------------------------------------
Assigning to [~jeffmaury] as this is pure UI candy on the Eclipse side, no rest client changes necessary.
> 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 MAURY
> 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
[JBoss JIRA] (JBIDE-20937) Create resource(s) from json
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-20937?page=com.atlassian.jira.plugi... ]
Fred Bricon reassigned JBIDE-20937:
-----------------------------------
Assignee: Jeff MAURY (was: 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 MAURY
> 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
[JBoss JIRA] (JBDS-3793) On Windoiws 10, installer dialogs are too small and cannot be resized
by Len DiMaggio (JIRA)
[ https://issues.jboss.org/browse/JBDS-3793?page=com.atlassian.jira.plugin.... ]
Len DiMaggio updated JBDS-3793:
-------------------------------
Attachment: installer.png
> On Windoiws 10, installer dialogs are too small and cannot be resized
> ---------------------------------------------------------------------
>
> Key: JBDS-3793
> URL: https://issues.jboss.org/browse/JBDS-3793
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Environment: Version: 9.1.0.GA
> Build id: GA-v20160410-1849-B495
> Build date: 20160410-1849
> Windows 10
> 4K Display
> Reporter: Len DiMaggio
> Attachments: installer.png
>
>
> See the attached screenshot - This issue has been raised before regarding the default size used for the JBDS IDE display - the issues that are specific to the JBDS installer is that the small sized dialogs obscure user-editable fields and and that the dialogs cannot be resized.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3793) On Windows 10, installer dialogs are too small and cannot be resized
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBDS-3793?page=com.atlassian.jira.plugin.... ]
Fred Bricon updated JBDS-3793:
------------------------------
Summary: On Windows 10, installer dialogs are too small and cannot be resized (was: On Windoiws 10, installer dialogs are too small and cannot be resized)
> On Windows 10, installer dialogs are too small and cannot be resized
> --------------------------------------------------------------------
>
> Key: JBDS-3793
> URL: https://issues.jboss.org/browse/JBDS-3793
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Environment: Version: 9.1.0.GA
> Build id: GA-v20160410-1849-B495
> Build date: 20160410-1849
> Windows 10
> 4K Display
> Reporter: Len DiMaggio
> Attachments: installer.png
>
>
> See the attached screenshot - This issue has been raised before regarding the default size used for the JBDS IDE display - the issues that are specific to the JBDS installer is that the small sized dialogs obscure user-editable fields and and that the dialogs cannot be resized.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years
[JBoss JIRA] (JBDS-3793) On Windoiws 10, installer dialogs are too small and cannot be resized
by Len DiMaggio (JIRA)
Len DiMaggio created JBDS-3793:
----------------------------------
Summary: On Windoiws 10, installer dialogs are too small and cannot be resized
Key: JBDS-3793
URL: https://issues.jboss.org/browse/JBDS-3793
Project: Developer Studio (JBoss Developer Studio)
Issue Type: Bug
Components: installer
Affects Versions: 9.1.0.CR1
Environment: Version: 9.1.0.GA
Build id: GA-v20160410-1849-B495
Build date: 20160410-1849
Windows 10
4K Display
Reporter: Len DiMaggio
See the attached screenshot - This issue has been raised before regarding the default size used for the JBDS IDE display - the issues that are specific to the JBDS installer is that the small sized dialogs obscure user-editable fields and and that the dialogs cannot be resized.
--
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 commented on JBIDE-22157:
-------------------------------------
[~tiago.matias] Would it be possible for you to whip up a zip with a very basic set of example projects? If you do, we might be able to open this issue up at jasper and get them to try to support exploded deployments. Of course when that makes it into a wildfly or EAP would be a long way off, but at least then we could tackle the issue at both ends.
> 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 commented on JBIDE-22157:
-------------------------------------
The only workaround at this time is to open the server editor (double-click server in server view) and go to deployment tab and always use zipped deployment. This means you won't be doing exploded deployment anymore, and so you won't benefit from incremental publishing, sadly :(
> 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] (JBDS-3791) JBDS installer - Non-existent dir off of home dir automatically added to runtime detection
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3791?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-3791:
--------------------------------------
Yes, this works as designed in JBDS-2515. But I agree it might look like a bug. I'm not rejecting it right now. Let see if we can handle it better.
> JBDS installer - Non-existent dir off of home dir automatically added to runtime detection
> ------------------------------------------------------------------------------------------
>
> Key: JBDS-3791
> URL: https://issues.jboss.org/browse/JBDS-3791
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: installer
> Affects Versions: 9.1.0.CR1
> Environment: Version: 9.1.0.GA
> Build id: GA-v20160410-1849-B495
> Build date: 20160410-1849
> Reporter: Len DiMaggio
> Assignee: Alexey Kazakov
> Priority: Minor
> Fix For: LATER
>
> Attachments: homeDir.png
>
>
> See attached screenshot - why are we adding a (potentially) non-existent directory off of the installer's homedir to runtime detection?
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
10 years