January 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] Created: (JBIDE-9227) AS7: when stopping the server, we provide a valid fallback (should kill process ?) if mgm api is not available

by Andre Dietisheim (JIRA)

AS7: when stopping the server, we provide a valid fallback (should kill process ?) if mgm api is not available -------------------------------------------------------------------------------------------------------------- Key: JBIDE-9227 URL: https://issues.jboss.org/browse/JBIDE-9227 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS Affects Versions: 3.3.0.M1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.M2 -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

8
17
0 / 0

[JBoss JIRA] (JBIDE-10491) OpenShift error messages should contain more specific description

by Stefan Bunciak (Created) (JIRA)

OpenShift error messages should contain more specific description ----------------------------------------------------------------- Key: JBIDE-10491 URL: https://issues.jboss.org/browse/JBIDE-10491 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 3.3.0.M5 Reporter: Stefan Bunciak Assignee: Andre Dietisheim The wizard should explain why the name of domain,aplication, e.g. can't be created (in my case it was due to special characters in name) -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
3
0 / 0

[JBoss JIRA] (JBIDE-10483) OpenShift application has no Java Version specified, facets requires Java 1.6

by Stefan Bunciak (Created) (JIRA)

OpenShift application has no Java Version specified, facets requires Java 1.6 ----------------------------------------------------------------------------- Key: JBIDE-10483 URL: https://issues.jboss.org/browse/JBIDE-10483 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Affects Versions: 3.3.0.M5 Environment: fedora 15 Reporter: Stefan Bunciak Assignee: Andre Dietisheim Priority: Critical Newly created application contains this error: "Dynamic Web Module 3.0 requires Java 1.6 or newer." and no facets are selected (except JBoss Maven Integration) After adding <plugin> <groupId>org.apache.maven.plugins</groupId> <artifactId>maven-compiler-plugin</artifactId> <version>2.0.2</version> <configuration> <source>1.6</source> <target>1.6</target> </configuration> </plugin> to pom.xml and updating maven project configuration, dynamic web module and other facets were ok. Maybe you can add this to OpensShift Maven profile. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
2
0 / 0

[JBoss JIRA] Created: (JBIDE-8967) fetch drools upstream from nexus via maven & unpack into local update site

by Nick Boldt (JIRA)

fetch drools upstream from nexus via maven & unpack into local update site -------------------------------------------------------------------------- Key: JBIDE-8967 URL: https://issues.jboss.org/browse/JBIDE-8967 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng Affects Versions: 3.3.0.M2 Reporter: Nick Boldt Assignee: Nick Boldt Fix For: 3.3.0.M2 Per sample in https://svn.devel.redhat.com/repos/jboss-soa/trunk/soa-p/pom.xml, we can now pull drools artifacts from https://repository.jboss.org/nexus/content/groups/public/org/drools/org.d... via maven dep resolution, unpack them to a local folder, composite them via a generated composite*.xml pair, and generate downstream update site using a purely maven solution (without shell hacks). This would also mean that nightly update sites would become maven artifacts for consumption, rather than pure p2 sites, bridging both worlds. In theory, anyway. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

2
6
0 / 0

[JBoss JIRA] (JBIDE-9853) are org.jboss.tools.patches.swt.gtk.linux.x86.feature and org.jboss.tools.patches.swt.gtk.linux.x86_64.feature obsolete?

by Nick Boldt (Created) (JIRA)

are org.jboss.tools.patches.swt.gtk.linux.x86.feature and org.jboss.tools.patches.swt.gtk.linux.x86_64.feature obsolete? ------------------------------------------------------------------------------------------------------------------------ Key: JBIDE-9853 URL: https://issues.jboss.org/browse/JBIDE-9853 Project: Tools (JBoss Tools) Issue Type: Bug Components: Build/Releng, updatesite, UpStream, Visual Page Editor core Affects Versions: 3.3.0.M4 Reporter: Nick Boldt Assignee: Snjezana Peco Fix For: 3.3.0.M4 New SWT release as part of Eclipse 3.7.1 (Indigo SR1) includes these plugins. {code} ./M20110909-1335/plugins/org.eclipse.swt.gtk.linux.x86_3.7.1.v3738a.jar ./M20110909-1335/plugins/org.eclipse.swt.gtk.linux.x86_64_3.7.1.v3738a.jar ./M20110909-1335/plugins/org.eclipse.swt.gtk.linux.x86_64.source_3.7.1.v3738a.jar ./M20110909-1335/plugins/org.eclipse.swt.gtk.linux.x86.source_3.7.1.v3738a.jar Do we still need to apply these patches? http://download.jboss.org/jbosstools/updates/requirements/swt/3.7.0.v3735... -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

5
4
0 / 0

[JBoss JIRA] Created: (JBIDE-9325) Refactor PollThread to not set the server but to return the caller the state the server shall be set to

by Andre Dietisheim (JIRA)

Refactor PollThread to not set the server but to return the caller the state the server shall be set to ------------------------------------------------------------------------------------------------------- Key: JBIDE-9325 URL: https://issues.jboss.org/browse/JBIDE-9325 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: JBossAS Affects Versions: 3.3.0.M2 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.x The current implementation of the PollThread, which monitors the server startup/shutdown currently sets the server state. IMHO in sake of separation of concerns the PollThread should not set the server state but shut return the caller the state that it detected/failure. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

3
3
0 / 0

[JBoss JIRA] (JBIDE-10282) Application Server download from within the JBoss Runtime Detection preferences errors on installation without any information on why -> when the folder being installed to isn't writable by the current OS user

by Isaac Rooskov (Created) (JIRA)

Application Server download from within the JBoss Runtime Detection preferences errors on installation without any information on why -> when the folder being installed to isn't writable by the current OS user ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-10282 URL: https://issues.jboss.org/browse/JBIDE-10282 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.M4 Environment: Fedora 14, JBT 3.3.0.M4 Reporter: Isaac Rooskov Assignee: Rob Stryker Fix For: 3.3.0.M5 When using the Download button within the JBoss Tools Runtime Detection preferences screen, I highlight JBoss AS 7.0.2 and click OK. I choose an installation folder within /home that isn't for the user I am logged in as and click OK (leaving the download location as the default). The application server is then downloaded, but once installation begins, because the folder is not writable by the user who is running the Eclipse instance, an error occurs, however no information is provided on why (see attached screenshot). I recommend one of two things, either: - Check that the directory is writeable before beginning the download OR - When the error occurs, provide text explaining to the user what has happened and then provide a way for a different install location to be selected. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

7
7
0 / 0

[JBoss JIRA] (JBIDE-10164) Seam UI test failure

by Alexey Kazakov (Created) (JIRA)

Seam UI test failure -------------------- Key: JBIDE-10164 URL: https://issues.jboss.org/browse/JBIDE-10164 Project: Tools (JBoss Tools) Issue Type: Bug Components: Seam 2 Affects Versions: 3.3.0.Beta1 Reporter: Alexey Kazakov Assignee: Viacheslav Kabanovich Fix For: 3.3.0.Beta1 {code} Failed tests: testAddComponentInXmlFile(org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest) testRenameComponentInXmlFile(org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest) testDeleteComponentInXmlFile(org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest) testAddComponentInClass(org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest) testRenameComponentInClass(org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest) testDeleteComponentInClass(org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest) Tests in error: testFlatSeamPackages(org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest) testHierarchicalSeamPackages(org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest) Tests run: 72, Failures: 6, Errors: 2, Skipped: 0, Time elapsed: 564.94 sec <<< FAILURE! testAddComponentInXmlFile(org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest) Time elapsed: 2.336 sec <<< FAILURE! junit.framework.AssertionFailedError: Seam model is not updated, expected package 'myPackage' is not found in tree at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest.testAddComponentInXmlFile(SeamComponentsViewTest.java:128) testRenameComponentInXmlFile(org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest) Time elapsed: 0.542 sec <<< FAILURE! junit.framework.AssertionFailedError: Expected package 'myPackage' was not found it tree at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest.testRenameComponentInXmlFile(SeamComponentsViewTest.java:148) testDeleteComponentInXmlFile(org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest) Time elapsed: 0.555 sec <<< FAILURE! junit.framework.AssertionFailedError: Package "myNewPackage" not found! at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest.testDeleteComponentInXmlFile(SeamComponentsViewTest.java:216) testAddComponentInClass(org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest) Time elapsed: 2.066 sec <<< FAILURE! junit.framework.AssertionFailedError: Package "demo" not found! at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest.testAddComponentInClass(SeamComponentsViewTest.java:286) testRenameComponentInClass(org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest) Time elapsed: 1.055 sec <<< FAILURE! junit.framework.AssertionFailedError: Package "demo" not found! at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest.testRenameComponentInClass(SeamComponentsViewTest.java:304) testDeleteComponentInClass(org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest) Time elapsed: 0.673 sec <<< FAILURE! junit.framework.AssertionFailedError: null at junit.framework.Assert.fail(Assert.java:47) at junit.framework.Assert.assertTrue(Assert.java:20) at junit.framework.Assert.assertNotNull(Assert.java:214) at junit.framework.Assert.assertNotNull(Assert.java:207) at org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest.testDeleteComponentInClass(SeamComponentsViewTest.java:359) testFlatSeamPackages(org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest) Time elapsed: 1.679 sec <<< ERROR! java.lang.NullPointerException at org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest.testFlatSeamPackages(SeamComponentsViewTest.java:418) testHierarchicalSeamPackages(org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest) Time elapsed: 1.565 sec <<< ERROR! java.lang.NullPointerException at org.jboss.tools.seam.ui.test.view.SeamComponentsViewTest.testHierarchicalSeamPackages(SeamComponentsViewTest.java:454) {code} -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

4
4
0 / 0

[JBoss JIRA] (JBIDE-9857) Openshift Express: provide possibility to request with a custom user agent string so that we can identify request done by our tooling

by Andre Dietisheim (Created) (JIRA)

Openshift Express: provide possibility to request with a custom user agent string so that we can identify request done by our tooling ------------------------------------------------------------------------------------------------------------------------------------- Key: JBIDE-9857 URL: https://issues.jboss.org/browse/JBIDE-9857 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: JBossAS/Servers Affects Versions: 3.3.0.M4 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.0.M4 We want to be able to track requests our tooling does compared to requests that are done by the web gui. We therefore need to provide the capability to supply a custom user agent to the openshift express service. -- This message is automatically generated by JIRA. If you think it was sent incorrectly, please contact your JIRA administrators: https://issues.jboss.org/secure/ContactAdministrators!default.jspa For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

8
13
0 / 0

[JBoss JIRA] Created: (JBIDE-9525) PublishCopyUtil#copyFile throws an Exception but it's impl catches it and returns an IStatus instead

by Andre Dietisheim (JIRA)

PublishCopyUtil#copyFile throws an Exception but it's impl catches it and returns an IStatus instead ---------------------------------------------------------------------------------------------------- Key: JBIDE-9525 URL: https://issues.jboss.org/browse/JBIDE-9525 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: JBossAS Affects Versions: 3.3.0.M3 Reporter: Andre Dietisheim Assignee: Rob Stryker Fix For: 3.3.x see https://source.jboss.org/cru/REV-JBIDE-4/#c79 PublishCopyUtil#copyFile should either throw Exceptions or return status objects. The current impl where exceptions are declared in the method signature but catched in the impl makes no sense. We have to decide what strategy to take (either throw or catch and return status). {code} private IStatus copyFile(InputStream in, IPath to, long ts, IModuleFile mf) throws CoreException { File tempFile = null; try { File file = to.toFile(); tempFile = writeToTempFile(in, to); moveTempFile(tempFile, file); if (ts != IResource.NULL_STAMP && ts != 0) file.setLastModified(ts); } catch (CoreException e) { throw e; } catch (Exception e) { IPath path = mf.getModuleRelativePath().append(mf.getName()); return new Status(IStatus.ERROR, ServerPlugin.PLUGIN_ID, IEventCodes.JST_PUB_FAIL, NLS.bind(Messages.errorCopyingFile, path.toOSString(), e.getLocalizedMessage()), null); } finally { if (tempFile != null && tempFile.exists()) tempFile.deleteOnExit(); try { if (in != null) in.close(); } catch (Exception ex) { // ignore } } return null; } {code} -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

14 years

5
4
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 January 2012