[JBoss JIRA] (JBDS-3846) Create container oriented perspective
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3846?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-3846:
--------------------------------------
I'm not sure how we can implement it but we could use it if installed via our Platform installer. So all platform installer users will see it by default.
> Create container oriented perspective
> -------------------------------------
>
> Key: JBDS-3846
> URL: https://issues.jboss.org/browse/JBDS-3846
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Components: cdk, docker, openshift
> Affects Versions: 10.0.0.Alpha1
> Reporter: Marián Labuda
> Priority: Critical
> Fix For: 10.0.0.Alpha2
>
>
> At the moment we have only JBoss perspective. We should create a new, more container oriented perspective, where Docker Explorer view would be opened by default and other views should be added and aligned to satisfy user needs. Layout of perspective should be more focused on container development.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3848) Server adapter types not displayed on Windows10 for JBDS 9.1.0
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3848?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov commented on JBDS-3848:
--------------------------------------
Why not a bug? Eclipse/JBDS should work fine on 4K monitors.
> Server adapter types not displayed on Windows10 for JBDS 9.1.0
> --------------------------------------------------------------
>
> Key: JBDS-3848
> URL: https://issues.jboss.org/browse/JBDS-3848
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: server, upstream
> Affects Versions: 9.1.0.GA
> Environment: Version: 9.1.0.GA
> Build id: GA-v20160414-0124-B497
> Build date: 20160414-0124
> Reporter: Len DiMaggio
> Assignee: Rob Stryker
> Priority: Blocker
> Attachments: CDK_RHEL.png, CDK_Win10.png
>
>
> See attached screenshots - after installing 9.1.0, server adapters are seen on RHEL, not on Windows10.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[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:
-------------------------------------
Hi Tiago:
I've linked the upstream issue and submitted a PR for it. Not sure if it'll be accepted since it's not my area of expertise, but it was fun working on it ;)
> 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
>
> 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, 11 months
[JBoss JIRA] (JBIDE-17882) Validate remote server dir before start/stop/deploy operations
by Rob Stryker (JIRA)
[ https://issues.jboss.org/browse/JBIDE-17882?page=com.atlassian.jira.plugi... ]
Rob Stryker updated JBIDE-17882:
--------------------------------
Story Points: 4 (was: 3.5)
> Validate remote server dir before start/stop/deploy operations
> --------------------------------------------------------------
>
> Key: JBIDE-17882
> URL: https://issues.jboss.org/browse/JBIDE-17882
> Project: Tools (JBoss Tools)
> Issue Type: Feature Request
> Components: server
> Affects Versions: 4.2.0.Beta3
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.4.0.Alpha1
>
>
> Max said this on irc today:
> {quote}
> strykerawb: i got some really weird behavior 12:56:27
> maxandersen strykerawb: see this video: http://screencast.com/t/uSDT1EoS 12:56:31
> jbossbot Title: 014-07-15_1255 - max.rydahl.andersen's library 12:56:31
> maxandersen what is it doing? 12:56:34
> maxandersen this is me dragging a project to wildfly server 12:56:42
> maxandersen ah the server is configured as remote with blank remote server home... 12:57:05
> maxandersen seems that result in complete funky endless loop..
> {quote}
> The problem is that he had an empty dir set up on a remote server. So when he tried to publish, this resulted in some unexpected behavior (endless copy progress in this case).
> Currently, when you create a remote server, the dialog will not let you leave the server home dir empty. But that is not enough. You can still change it in the server editor to be empty. Rob says he wants to remove this field from the server editor and only use the wizard, but that is still not enough - the user can remote the folder on the remote system at a later time.
> We probably don't need to check the folder every time we use it, but at least at the start of each operation such as start/stop server, publish to server.
> Also, the New server dialog checks for empty string, but I'm not 100 % sure if it actually checks that the folder exists.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months