[JBoss JIRA] (JBIDE-22145) nio WatchService possibly causing errors / locking files on windows
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22145?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22145:
-------------------------------
Fix Version/s: 4.5.x
(was: 4.5.0.AM1)
> 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.5.x
>
> Attachments: FSWatcherHang.txt, FailureWatchModify1.PML, FileWatchError.zip, 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
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-22175) Warnings in JBDS after importing kitchensink-jsp quickstart
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22175?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22175:
-------------------------------
Fix Version/s: 4.5.0.Final
(was: 4.5.0.AM1)
> Warnings in JBDS after importing kitchensink-jsp quickstart
> -----------------------------------------------------------
>
> Key: JBIDE-22175
> URL: https://issues.jboss.org/browse/JBIDE-22175
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: jsp/jsf/xml/html-source-editing, upstream
> Reporter: Sande Gilda
> Assignee: Victor Rubezhny
> Fix For: 4.5.0.Final
>
>
> After importing the quickstart into JBDS, the following warnings are produced
> * The tag handler class for "c:forEach" (org.apache.taglibs.standard.tag.rt.core.ForEachTag) was not found on the Java Build Path
> * The tag handler class for "c:out" (org.apache.taglibs.standard.tag.rt.core.OutTag) was not found on the Java Build Path
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-22290) Open via livereload quick access errors when no livereload server is present
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22290?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22290:
-------------------------------
Fix Version/s: 4.5.0.Final
(was: 4.5.0.AM1)
> Open via livereload quick access errors when no livereload server is present
> ----------------------------------------------------------------------------
>
> Key: JBIDE-22290
> URL: https://issues.jboss.org/browse/JBIDE-22290
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: livereload
> Affects Versions: 4.4.0.Alpha1
> Reporter: Jan Richter
> Assignee: Xavier Coulon
> Fix For: 4.5.0.Final
>
>
> The following error is produced while the livereload server is starting:
> {noformat}
> Problems occurred when invoking code from plug-in: "org.jboss.tools.livereload.ui".
> org.eclipse.swt.SWTException: Invalid thread access
> at org.eclipse.swt.SWT.error(SWT.java:4522)
> at org.eclipse.swt.SWT.error(SWT.java:4437)
> at org.eclipse.swt.SWT.error(SWT.java:4408)
> at org.eclipse.swt.widgets.Display.error(Display.java:1186)
> at org.eclipse.swt.widgets.Display.checkDevice(Display.java:765)
> at org.eclipse.swt.widgets.Display.getActiveShell(Display.java:1400)
> at org.jboss.tools.livereload.ui.internal.command.OpenInWebBrowserViaLiveReloadUtils.openInWebBrowser(OpenInWebBrowserViaLiveReloadUtils.java:189)
> at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler.openInWebBrowser(LaunchLiveReloadServerCommandHandler.java:114)
> at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler.access$0(LaunchLiveReloadServerCommandHandler.java:112)
> at org.jboss.tools.livereload.ui.internal.command.LaunchLiveReloadServerCommandHandler$2.done(LaunchLiveReloadServerCommandHandler.java:67)
> at org.eclipse.core.internal.jobs.JobListeners$3.notify(JobListeners.java:42)
> at org.eclipse.core.internal.jobs.JobListeners.doNotify(JobListeners.java:106)
> at org.eclipse.core.internal.jobs.JobListeners.done(JobListeners.java:144)
> at org.eclipse.core.internal.jobs.JobManager.endJob(JobManager.java:694)
> at org.eclipse.core.internal.jobs.WorkerPool.endJob(WorkerPool.java:105)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:72)
> {noformat}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-22416) Plugins dependency conflict when importing JavaEE7 Sample
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22416?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22416:
-------------------------------
Fix Version/s: 4.5.0.Final
(was: 4.5.0.AM1)
> Plugins dependency conflict when importing JavaEE7 Sample
> ---------------------------------------------------------
>
> Key: JBIDE-22416
> URL: https://issues.jboss.org/browse/JBIDE-22416
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: maven, project-examples, upstream
> Affects Versions: 4.4.0.Alpha1
> Environment: Version: 10.0.0.Alpha1
> Build id: Alpha1-v20160520-0424-B5396
> Build date: 20160520-0424
> Reporter: Josef Kopriva
> Assignee: Fred Bricon
> Fix For: 4.5.0.Final
>
> Attachments: import_issue.png
>
>
> When I import JavaEE7 sample sample extra/spock-tests, I cannot install plugin due to plugin conflict issue.
> {code:java}
> Cannot complete the install because of a conflicting dependency.
> Software being installed: Groovy-Eclipse M2E integration 2.9.2.xx-201604081629-e45 (org.codehaus.groovy.m2eclipse.feature.feature.group 2.9.2.xx-201604081629-e45)
> Software currently installed: Red Hat Developer Studio (Branded Product) 10.0.0.Alpha1-v20160520-0424-B5396 (com.jboss.devstudio.core.package 10.0.0.Alpha1-v20160520-0424-B5396)
> Software currently installed: TestNG 6.9.11.201604020423 (org.testng.eclipse.feature.group 6.9.11.201604020423)
> Only one of the following can be installed at once:
> Java Development Tools Core 3.12.0.v20160426-1326 (org.eclipse.jdt.core 3.12.0.v20160426-1326)
> Java Development Tools Core 3.11.0.xx-201604081629-e45 (org.eclipse.jdt.core 3.11.0.xx-201604081629-e45)
> Cannot satisfy dependency:
> From: Red Hat Developer Studio (Core Features) 10.0.0.Alpha1-v20160520-0424-B5396 (com.jboss.devstudio.core.feature.feature.group 10.0.0.Alpha1-v20160520-0424-B5396)
> To: org.eclipse.jdt.feature.group 0.0.0
> Cannot satisfy dependency:
> From: Red Hat Developer Studio (Branded Product) 10.0.0.Alpha1-v20160520-0424-B5396 (com.jboss.devstudio.core.package 10.0.0.Alpha1-v20160520-0424-B5396)
> To: com.jboss.devstudio.core.feature.feature.group [10.0.0.Alpha1-v20160520-0424-B5396]
> Cannot satisfy dependency:
> From: Groovy-Eclipse Compilerless Feature 2.9.2.xx-201604081629-e45 (org.codehaus.groovy.compilerless.feature.feature.group 2.9.2.xx-201604081629-e45)
> To: org.codehaus.groovy.headless.feature.feature.group [2.9.2.xx-201604081629-e45]
> Cannot satisfy dependency:
> From: Groovy-Eclipse Feature 2.9.2.xx-201604081629-e45 (org.codehaus.groovy.eclipse.feature.feature.group 2.9.2.xx-201604081629-e45)
> To: org.codehaus.groovy.compilerless.feature.feature.group [2.9.2.xx-201604081629-e45]
> Cannot satisfy dependency:
> From: Groovy-Eclipse Headless Feature 2.9.2.xx-201604081629-e45 (org.codehaus.groovy.headless.feature.feature.group 2.9.2.xx-201604081629-e45)
> To: org.codehaus.groovy.jdt.patch.feature.group [2.9.2.xx-201604081629-e45]
> Cannot satisfy dependency:
> From: Groovy-Eclipse M2E integration 2.9.2.xx-201604081629-e45 (org.codehaus.groovy.m2eclipse.feature.feature.group 2.9.2.xx-201604081629-e45)
> To: org.codehaus.groovy.eclipse.feature.feature.group 0.0.0
> Cannot satisfy dependency:
> From: Java Development Tools JUnit support 3.9.0.v20160421-1701 (org.eclipse.jdt.junit 3.9.0.v20160421-1701)
> To: bundle org.eclipse.jdt.core [3.12.0,4.0.0)
> Cannot satisfy dependency:
> From: TestNG Eclipse Support 6.9.11.201604020423 (org.testng.eclipse 6.9.11.201604020423)
> To: bundle org.eclipse.jdt.junit 0.0.0
> Cannot satisfy dependency:
> From: TestNG 6.9.11.201604020423 (org.testng.eclipse.feature.group 6.9.11.201604020423)
> To: org.testng.eclipse [6.9.11.201604020423]
> Cannot satisfy dependency:
> From Patch: org.codehaus.groovy.jdt.patch.feature.group 2.9.2.xx-201604081629-e45 Eclipse Java Development Tools 3.12.0.v20160428-0800 (org.eclipse.jdt.feature.group 3.12.0.v20160428-0800)
> To: org.eclipse.jdt.core [3.11.0.xx-201604081629-e45]
> {code}
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-22375) Improve HCR OpenShift
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22375?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22375:
-------------------------------
Fix Version/s: 4.5.0.AM2
(was: 4.5.0.AM1)
> Improve HCR OpenShift
> ---------------------
>
> Key: JBIDE-22375
> URL: https://issues.jboss.org/browse/JBIDE-22375
> Project: Tools (JBoss Tools)
> Issue Type: Epic
> Components: jmx, openshift
> Affects Versions: 4.3.1.Beta2
> Reporter: Fred Bricon
> Assignee: Rob Stryker
> Priority: Blocker
> Labels: openshift_v3, server_adapter
> Fix For: 4.5.0.AM2
>
>
> When enabling debug mode on an EAP server deployed on OpenShift, locally changing a class file will :
> - work sometimes when only the content of the method changed, but could fail in some other occasions with the Debugger saying the JDK is out of sync
> - will always fail if a method signature changed, the debugger saying JDK is out of sync
> Restarting the deployed module (with the .dodeploy flag) doesn't fixes the issue (as opposed to the same tweak ahen running on a local EAP server)
> This may be caused by running OpenJDK? Does it support the same level of debugging as Oracle JDK?
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months
[JBoss JIRA] (JBIDE-22605) Remote server with fs operations sometimes cannot be stopped
by Jeff MAURY (JIRA)
[ https://issues.jboss.org/browse/JBIDE-22605?page=com.atlassian.jira.plugi... ]
Jeff MAURY updated JBIDE-22605:
-------------------------------
Fix Version/s: 4.5.0.AM2
(was: 4.5.0.AM1)
> Remote server with fs operations sometimes cannot be stopped
> ------------------------------------------------------------
>
> Key: JBIDE-22605
> URL: https://issues.jboss.org/browse/JBIDE-22605
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Affects Versions: 4.4.0.Final
> Reporter: Martin Malina
> Assignee: Rob Stryker
> Fix For: 4.5.0.AM2
>
>
> Yesterday when we were found out that remote servers don't work with management operations (JBIDE-22601) I wanted to check if at least FS operations work.
> In one instance of Eclipse, stopping such server didn't work.
> But then I tried in devstudio and it worked, so I assumed it was some glitch.
> But today this happened to me again with the latest devstudio 10.0.0.GA B30 build - the one that contains a fix to the above mentioned JIRA.
> From several attempts, it seems that this is only reproducible if you deploy a project. If you just start the server and then stop, it will stop just fine.
> One more thing, regardless of whether a given server can be stopped or not, I always get this in the Error Log view during server startup:
> {code}Unable to retrieve a list of remote deployment scanners for server Red Hat JBoss EAP 7.0 marvin{code}
> (Let me know if you want an additional JIRA for that.)
--
This message was sent by Atlassian JIRA
(v7.2.3#72005)
8 years, 9 months