[JBoss JIRA] (JBDS-3760) Installer - Reference to "JBDS" should be changed to "JBoss Developer Studio"
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3760?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov updated JBDS-3760:
---------------------------------
Component/s: platform-installer
(was: installer)
> Installer - Reference to "JBDS" should be changed to "JBoss Developer Studio"
> -----------------------------------------------------------------------------
>
> Key: JBDS-3760
> URL: https://issues.jboss.org/browse/JBDS-3760
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Environment: Setup-bundled-0.0.2-20160401-33.exe
> Reporter: Len DiMaggio
> Assignee: Denis Golovin
> Fix For: 9.1.0.GA
>
> Attachments: JBDS_1.png, JBDS_2.png, JBDS_3.png, JBDS_4.png
>
>
> The screen displayed after the user logs in refers to "JBDS" - this is the only time that the installer refers to "JBDS" - the other references are to "JBoss Developer Studio."
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)
9 years, 11 months
[JBoss JIRA] (JBDS-3760) Installer - Reference to "JBDS" should be changed to "JBoss Developer Studio"
by Alexey Kazakov (JIRA)
[ https://issues.jboss.org/browse/JBDS-3760?page=com.atlassian.jira.plugin.... ]
Alexey Kazakov resolved JBDS-3760.
----------------------------------
Fix Version/s: 9.1.0.GA
(was: 10.0.0.Alpha1)
Resolution: Done
This one was fixed for 9.1.0
> Installer - Reference to "JBDS" should be changed to "JBoss Developer Studio"
> -----------------------------------------------------------------------------
>
> Key: JBDS-3760
> URL: https://issues.jboss.org/browse/JBDS-3760
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Components: platform-installer
> Affects Versions: 9.1.0.CR1
> Environment: Setup-bundled-0.0.2-20160401-33.exe
> Reporter: Len DiMaggio
> Assignee: Denis Golovin
> Fix For: 9.1.0.GA
>
> Attachments: JBDS_1.png, JBDS_2.png, JBDS_3.png, JBDS_4.png
>
>
> The screen displayed after the user logs in refers to "JBDS" - this is the only time that the installer refers to "JBDS" - the other references are to "JBoss Developer Studio."
--
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 updated JBIDE-22157:
--------------------------------
Story Points: 8
> 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: 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