September 2013 - jbosstools-issues

[JBoss JIRA] (JBIDE-15494) Software/Update page - Cannot create temporary directory

by Mickael Istria (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15494?page=com.atlassian.jira.plugi... ] Mickael Istria commented on JBIDE-15494: ---------------------------------------- What OS are you using? Did you install JBT/JBDS in a location where you can write? Do you have write access to java.io.tmpdir? Can you reproduce it on other machines? > 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15354) CordovaSim: CordovaSim window is not available after switching off second monitor

by Konstantin Marmalyukov (JIRA)

[ https://issues.jboss.org/browse/JBIDE-15354?page=com.atlassian.jira.plugi... ] Konstantin Marmalyukov commented on JBIDE-15354: ------------------------------------------------ Vlado, do you switch monitor off "programmaticaly" via control panel? > CordovaSim: CordovaSim window is not available after switching off second monitor > --------------------------------------------------------------------------------- > > Key: JBIDE-15354 > URL: https://issues.jboss.org/browse/JBIDE-15354 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: browsersim > Affects Versions: 4.2.0.Alpha1 > Reporter: Konstantin Marmalyukov > Assignee: Konstantin Marmalyukov > Fix For: 4.1.1.Alpha1, 4.2.0.Alpha1 > > > 1. Open cordovaSim with two monitors. > 2. Close cordovaSim. > 3. Switch off monitor where cordovaSim window was. > 4. Open CordovaSim. ERROR: cordovaSim window is not available. -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBIDE-15494) Software/Update page - Cannot create temporary directory

by Radim Hopp (JIRA)

Radim Hopp created JBIDE-15494: ---------------------------------- Summary: 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-178) In JBTIS 4.1.3.beta2 - The SOA5 category includes Drools6 which may be incompatible with BRMS5 and SOA5

by Lukáš Petrovický (JIRA)

[ https://issues.jboss.org/browse/JBTIS-178?page=com.atlassian.jira.plugin.... ] Lukáš Petrovický commented on JBTIS-178: ---------------------------------------- Kris, correct me if I'm wrong, but isn't 6.0 always used for rule validation inside the editor etc.? > In JBTIS 4.1.3.beta2 - The SOA5 category includes Drools6 which may be incompatible with BRMS5 and SOA5 > ------------------------------------------------------------------------------------------------------- > > Key: JBTIS-178 > URL: https://issues.jboss.org/browse/JBTIS-178 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: drools/ jBPM5 > Reporter: Len DiMaggio > Assignee: Paul Leacu > Attachments: drools1.png > > > See the attached screenshot - how can JBTIS support both SOA5/BRMS5 and 6? -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-165) Regression - Cannot add a file to the attachments

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-165?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky commented on JBTIS-165: ----------------------------------------- Now, I'm not able to add files from the root directory, only from esbcontent and src. Is this intended? I use JBTIS 4.1.3.Beta2 (JBoss ESB Tools 1.5.301.Final-v20130913-1412-B1193) > Regression - Cannot add a file to the attachments > ------------------------------------------------- > > Key: JBTIS-165 > URL: https://issues.jboss.org/browse/JBTIS-165 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: ESB > Affects Versions: 4.1.2 > Environment: JBoss ESB Tools 1.5.300.Final-v20130815-1755-B1189 > Reporter: Andrej Podhradsky > Assignee: Viacheslav Kabanovich > Priority: Blocker > Attachments: esb_attachment_bug.png, test.zip > > > Cannot add a file to the attachments from esbcontent folder. It's also impossible to add .txt file from the root but .zip file is possible to add. See the screenshot -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-179) ModeShape Client is in wrong categories

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTIS-179?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration updated JBTIS-179: ------------------------------------------ Bugzilla Update: Perform Bugzilla References: https://bugzilla.redhat.com/show_bug.cgi?id=1008848 > ModeShape Client is in wrong categories > --------------------------------------- > > Key: JBTIS-179 > URL: https://issues.jboss.org/browse/JBTIS-179 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: modeshape > Affects Versions: 7.0.0-JBDS > Environment: http://www.qa.jboss.com/binaries/RHDS/updates/integration/kepler/integrat... > Reporter: Andrej Podhradsky > > Now, the ModeShape Cient in the following categories > * JBoss Business Process and Rules Development (there's nothing in common with ModeShape) > * JBoss Data Virtualization Development (OK) > * JBoss SOA 5.x Development (maybe OK, but EDS is needed) > * JBoss SOA Development (wrong, we need DV for ModeShape) -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-179) ModeShape Client is in wrong categories

by RH Bugzilla Integration (JIRA)

[ https://issues.jboss.org/browse/JBTIS-179?page=com.atlassian.jira.plugin.... ] RH Bugzilla Integration commented on JBTIS-179: ----------------------------------------------- Andrej Podhradsky <apodhrad(a)redhat.com> made a comment on [bug 1008848|https://bugzilla.redhat.com/show_bug.cgi?id=1008848] Description of problem: see the external issue tracker Version-Release number of selected component (if applicable): How reproducible: Steps to Reproduce: 1. 2. 3. Actual results: Expected results: Additional info: > ModeShape Client is in wrong categories > --------------------------------------- > > Key: JBTIS-179 > URL: https://issues.jboss.org/browse/JBTIS-179 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: modeshape > Affects Versions: 7.0.0-JBDS > Environment: http://www.qa.jboss.com/binaries/RHDS/updates/integration/kepler/integrat... > Reporter: Andrej Podhradsky > > Now, the ModeShape Cient in the following categories > * JBoss Business Process and Rules Development (there's nothing in common with ModeShape) > * JBoss Data Virtualization Development (OK) > * JBoss SOA 5.x Development (maybe OK, but EDS is needed) > * JBoss SOA Development (wrong, we need DV for ModeShape) -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-179) ModeShape Client is in wrong categories

by Andrej Podhradsky (JIRA)

Andrej Podhradsky created JBTIS-179: --------------------------------------- Summary: ModeShape Client is in wrong categories Key: JBTIS-179 URL: https://issues.jboss.org/browse/JBTIS-179 Project: JBoss Tools Integration Stack Issue Type: Bug Security Level: Public (Everyone can see) Affects Versions: 7.0.0-JBDS Environment: http://www.qa.jboss.com/binaries/RHDS/updates/integration/kepler/integrat... Reporter: Andrej Podhradsky Now, the ModeShape Cient in the following categories * JBoss Business Process and Rules Development (there's nothing in common with ModeShape) * JBoss Data Virtualization Development (OK) * JBoss SOA 5.x Development (maybe OK, but EDS is needed) * JBoss SOA Development (wrong, we need DV for ModeShape) -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-179) ModeShape Client is in wrong categories

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-179?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-179: ------------------------------------ Component/s: modeshape > ModeShape Client is in wrong categories > --------------------------------------- > > Key: JBTIS-179 > URL: https://issues.jboss.org/browse/JBTIS-179 > Project: JBoss Tools Integration Stack > Issue Type: Bug > Security Level: Public(Everyone can see) > Components: modeshape > Affects Versions: 7.0.0-JBDS > Environment: http://www.qa.jboss.com/binaries/RHDS/updates/integration/kepler/integrat... > Reporter: Andrej Podhradsky > > Now, the ModeShape Cient in the following categories > * JBoss Business Process and Rules Development (there's nothing in common with ModeShape) > * JBoss Data Virtualization Development (OK) > * JBoss SOA 5.x Development (maybe OK, but EDS is needed) > * JBoss SOA Development (wrong, we need DV for ModeShape) -- 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

12 years, 7 months

1
0
0 / 0

[JBoss JIRA] (JBTIS-175) Test Teiid Designer Server Management and Integration to JBDS/JBT

by Andrej Podhradsky (JIRA)

[ https://issues.jboss.org/browse/JBTIS-175?page=com.atlassian.jira.plugin.... ] Andrej Podhradsky updated JBTIS-175: ------------------------------------ Component/s: QE > Test Teiid Designer Server Management and Integration to JBDS/JBT > ----------------------------------------------------------------- > > Key: JBTIS-175 > URL: https://issues.jboss.org/browse/JBTIS-175 > Project: JBoss Tools Integration Stack > Issue Type: Task > Security Level: Public(Everyone can see) > Components: QE > Reporter: Lucie Fabrikova > Assignee: Lucie Fabrikova > > - focus on feature-related improvements > - area of server management, integrating to JBDS/JBT > - create AS5.1 + teiid 7.7.x, EAP 6.1 + Teiid 8.4.x servers, switching between them to preview data (tables) and execute VDB's. Open/close projects > - performing preview/execute/deploy actions when 1) NO server defined 2) Server defined but not started -- 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

12 years, 7 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 September 2013