April 2016 - jbosstools-issues - Jboss List Archives

[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 updated JBDS-3848: --------------------------------- Component/s: upstream > 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: Max Rydahl Andersen > 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

1
0
0 / 0

[JBoss JIRA] (JBDS-3848) Server adapter types not displayed on Windows10 for JBDS 9.1.0

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBDS-3848?page=com.atlassian.jira.plugin.... ] Rob Stryker commented on JBDS-3848: ----------------------------------- [~ldimaggio] can you try resizing the window and see if stuff shows up? I've seen behavior like that before in linux in the past. If resizing doesn't work, there's a bigger bug. If it does, then it's a small issue with some swt cause behind it. > 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 > 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: Max Rydahl Andersen > 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

1
0
0 / 0

[JBoss JIRA] (JBDS-3848) Server adapter types not displayed on Windows10 for JBDS 9.1.0

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3848?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3848: ------------------------------- Priority: Blocker (was: Major) > 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 > 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: Max Rydahl Andersen > 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

1
0
0 / 0

[JBoss JIRA] (JBDS-3848) Server adapter types not displayed on Windows10 for JBDS 9.1.0

by Len DiMaggio (JIRA)

[ https://issues.jboss.org/browse/JBDS-3848?page=com.atlassian.jira.plugin.... ] Len DiMaggio updated JBDS-3848: ------------------------------- Attachment: CDK_RHEL.png CDK_Win10.png > 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 > 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: Max Rydahl Andersen > 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

1
0
0 / 0

[JBoss JIRA] (JBIDE-22145) nio WatchService possibly causing errors / locking files on windows

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22145?page=com.atlassian.jira.plugi... ] Rob Stryker commented on JBIDE-22145: ------------------------------------- The error in the description was fixed by JBIDE-22078, however, the larger upstream issue with windows locking files is still relevant and should be tracked. Unfortunately it will probably be a bit longer before it makes it into any consumable JRE / JDK, and our tools still need to function since many users will not be using the most up-to-date JDK available. > nio WatchService possibly causing errors / locking files on windows > ------------------------------------------------------------------- > > Key: JBIDE-22145 > URL: https://issues.jboss.org/browse/JBIDE-22145 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Final > Environment: - Windows 7 x64 > - jdk1.8.0_77 (32-bit) > - Eclipse Mars.2 (32-bit) > - JBoss Tools 4.3.0.FINAL > - Wildfly 10.0.0.FINAL > Reporter: Tobias van den Berg > Assignee: Thomas Mäder > Priority: Critical > Fix For: 4.4.x > > Attachments: FailureWatchModify1.PML, FileWatchError.zip, FSWatcherHang.txt, Logfile.PML, OkWatchModify1.PML > > > The following error is thrown after publishing a maven webapplication (.war) to Wildfly 10.0: > "Error renaming C:\wildfly-10.0.0.Final\standalone\tmp\tmp8945090880188299781.properties to C:\wildfly-10.0.0.Final\standalone\deployments\WebViewer-0.0.3-SNAPSHOT.war\META-INF\maven\nl.incad.webviewer\WebViewer\pom.properties. > This may be caused by incorrect file permissions, or your server's temporary deploy directory may be on a different filesystem than the final destination. > You may adjust these settings in the server editor." > The webapplication is no longer available/online after the error. The only solution is to restart the server and to re-add the webapplication to the server. This makes it very hard to develop/test a webapplication on wildfly 10. The same error is thrown on wildfly 8.0/8.1, but the difference is that the webapplication is still available/online after the error. > I've tried/tested the following: > - Checked/updated Windows file permisions for the wildfly directory > - Take ownership of the wildfly directory (recursively) > - Disabled Windows User Account Control (UAC) > - Run Eclipse as Admin > Relates to: > - JBIDE-18697 > - JBIDE-17545 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-22145) nio WatchService possibly causing errors / locking files on windows

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-22145?page=com.atlassian.jira.plugi... ] Rob Stryker updated JBIDE-22145: -------------------------------- Fix Version/s: 4.4.x (was: 4.4.0.Alpha1) > nio WatchService possibly causing errors / locking files on windows > ------------------------------------------------------------------- > > Key: JBIDE-22145 > URL: https://issues.jboss.org/browse/JBIDE-22145 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: server > Affects Versions: 4.3.0.Final > Environment: - Windows 7 x64 > - jdk1.8.0_77 (32-bit) > - Eclipse Mars.2 (32-bit) > - JBoss Tools 4.3.0.FINAL > - Wildfly 10.0.0.FINAL > Reporter: Tobias van den Berg > Assignee: Thomas Mäder > Priority: Critical > Fix For: 4.4.x > > Attachments: FailureWatchModify1.PML, FileWatchError.zip, FSWatcherHang.txt, Logfile.PML, OkWatchModify1.PML > > > The following error is thrown after publishing a maven webapplication (.war) to Wildfly 10.0: > "Error renaming C:\wildfly-10.0.0.Final\standalone\tmp\tmp8945090880188299781.properties to C:\wildfly-10.0.0.Final\standalone\deployments\WebViewer-0.0.3-SNAPSHOT.war\META-INF\maven\nl.incad.webviewer\WebViewer\pom.properties. > This may be caused by incorrect file permissions, or your server's temporary deploy directory may be on a different filesystem than the final destination. > You may adjust these settings in the server editor." > The webapplication is no longer available/online after the error. The only solution is to restart the server and to re-add the webapplication to the server. This makes it very hard to develop/test a webapplication on wildfly 10. The same error is thrown on wildfly 8.0/8.1, but the difference is that the webapplication is still available/online after the error. > I've tried/tested the following: > - Checked/updated Windows file permisions for the wildfly directory > - Take ownership of the wildfly directory (recursively) > - Disabled Windows User Account Control (UAC) > - Run Eclipse as Admin > Relates to: > - JBIDE-18697 > - JBIDE-17545 -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBDS-3848) Server adapter types not displayed on Windows10 for JBDS 9.1.0

by Len DiMaggio (JIRA)

Len DiMaggio created JBDS-3848: ---------------------------------- Summary: 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 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: Max Rydahl Andersen 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

1
0
0 / 0

[JBoss JIRA] (ERT-132) Need to create launch configuration for npm "scripts" [EBZ#491474]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-132?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-132: ----------------------------- Story Points: 10 > Need to create launch configuration for npm "scripts" [EBZ#491474] > ------------------------------------------------------------------ > > Key: ERT-132 > URL: https://issues.jboss.org/browse/ERT-132 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Nick Boldt > Labels: General, bzira > > For now npm is used only as a package manager - only npm Install & npm Update shortcuts available. Need to extend npm functionality by supporting "scripts" property. This will allow to use npm as a Build Tool (like grunt / gulp) i.e. > all scripts defined in package.json should be contributed to CNF with launch shortcuts availbale for launch -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-20687) Deployed war is NOT the specified war name

by Fred Bricon (JIRA)

[ https://issues.jboss.org/browse/JBIDE-20687?page=com.atlassian.jira.plugi... ] Fred Bricon commented on JBIDE-20687: ------------------------------------- I guess we should just check this is fixed in Neon. But also double-check this fix doesn't break other use cases. > Deployed war is NOT the specified war name > ------------------------------------------ > > Key: JBIDE-20687 > URL: https://issues.jboss.org/browse/JBIDE-20687 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: maven, server, upstream > Affects Versions: 4.3.0.CR1 > Reporter: ehsavoie Hugonnet > Assignee: Fred Bricon > Priority: Critical > Fix For: 4.4.0.Alpha1 > > > The deployed war name is the *artifactId* and not the specified *warName* from the war plugin nor the *finalName*. > Sample pom.xml which exibits the issue > {code:xml}<project xmlns="http://maven.apache.org/POM/4.0.0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance" > xsi:schemaLocation="http://maven.apache.org/POM/4.0.0 http://maven.apache.org/maven-v4_0_0.xsd"> > <modelVersion>4.0.0</modelVersion> > <groupId>org.glassfish-samples</groupId> > <artifactId>auction</artifactId> > <version>4.0-SNAPSHOT</version> > <packaging>war</packaging> > <name>WebSocket Auction Sample Application</name> > > <dependencies> > <dependency> > <groupId>javax</groupId> > <artifactId>javaee-api</artifactId> > <version>7.0</version> > <scope>provided</scope> > </dependency> > </dependencies> > > <build> > <finalName>websocket-auction</finalName> > <plugins> > <plugin> > <artifactId>maven-compiler-plugin</artifactId> > <version>3.1</version> > <configuration> > <source>1.8</source> > <target>1.8</target> > </configuration> > </plugin> > <plugin> > <groupId>org.apache.maven.plugins</groupId> > <artifactId>maven-war-plugin</artifactId> > <version>2.3</version> > <configuration> > <failOnMissingWebXml>false</failOnMissingWebXml> > <warName>websocket-auction</warName> > </configuration> > </plugin> > </plugins> > </build> > </project> > {code} -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 months

1
0
0 / 0

[JBoss JIRA] (ERT-142) JavaScript Problems get doubled in Dynamic Web Projects [EBZ#491751]

by Gorkem Ercan (JIRA)

[ https://issues.jboss.org/browse/ERT-142?page=com.atlassian.jira.plugin.sy... ] Gorkem Ercan updated ERT-142: ----------------------------- Story Points: 20 > JavaScript Problems get doubled in Dynamic Web Projects [EBZ#491751] > -------------------------------------------------------------------- > > Key: ERT-142 > URL: https://issues.jboss.org/browse/ERT-142 > Project: Eclipse Release Train > Issue Type: Task > Components: JSDT > Reporter: Friendly Jira Robot > Labels: General, bzira > > Created attachment 260976 > Doubled problems in Problem view > JavaScript Problems are doubling in Dynamic Web Projects (See the attached screenshot). -- This message was sent by Atlassian JIRA (v6.4.11#64026)

9 years, 11 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 April 2016