[
https://issues.jboss.org/browse/JBIDE-15494?page=com.atlassian.jira.plugi...
]
Stefan Bunciak commented on JBIDE-15494:
----------------------------------------
[~mickael_istria]: Hi Mickael! I can reproduce this issue as well. Using fc19.x86_64 ,
jbds isntalled to ~/tools/jbdevstudio (where I have write permissions).
System.getProperty("java.io.tmpdir") returned /tmp
{code}
[sbunciak@sbunciak-ntb ~]$ ls -al /tmp
total 28
drwxrwxrwt. 22 root root 580 Sep 17 10:48 .
dr-xr-xr-x. 18 root root 4096 Sep 17 08:33 ..
{code}
Software/Update page - Cannot create temporary directory
--------------------------------------------------------
Key: JBIDE-15494
URL:
https://issues.jboss.org/browse/JBIDE-15494
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: central
Affects Versions: 4.1.0.Final, 4.1.1.Alpha1
Reporter: Radim Hopp
Priority: Blocker
Recently, Software/Update page of JBoss Central stopped working (No Connectors Found).
Error log:
{noformat}
Cannot download bundle at
http://download.jboss.org/jbosstools/updates/development/kepler/plugins/o...:
Unable to create temporary file
{noformat}
{noformat}
a.io.IOException: Unable to create temporary file
at java.io.File$TempDirectory.generateFile(File.java:1891)
at java.io.File.createTempFile(File.java:1979)
at
org.jboss.tools.project.examples.internal.discovery.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:217)
at
org.jboss.tools.project.examples.internal.discovery.xpl.RemoteExternalBundleDiscoveryStrategy$DownloadBundleJob.call(RemoteExternalBundleDiscoveryStrategy.java:1)
at java.util.concurrent.FutureTask.run(FutureTask.java:262)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
at java.lang.Thread.run(Thread.java:724)
{noformat}
This issue affects both JBDS and JBT, both not only in 7.1.0 (4.1.1) but also in
7.0.0.Final (4.1.0.Final), thus it's marked as blocker.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see:
http://www.atlassian.com/software/jira