March 2013 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-13763) openshift-java-client: exception does not say to what server it was trying to connect

by Andre Dietisheim (JIRA)

Andre Dietisheim created JBIDE-13763: ---------------------------------------- Summary: openshift-java-client: exception does not say to what server it was trying to connect Key: JBIDE-13763 URL: https://issues.jboss.org/browse/JBIDE-13763 Project: Tools (JBoss Tools) Issue Type: Enhancement Components: openshift Affects Versions: 4.1.0.Alpha2 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 4.1.0.Alpha2 Most exceptions that occur while talking to OpenShift are not telling you to what server the client was talking to. They mostly simply repeat the path: {code} com.openshift.client.OpenShiftEndpointException: Could not request /api: java.net.ConnectException: Connection timed out at com.openshift.internal.client.RestService.request(RestService.java:103) at com.openshift.internal.client.RestService.request(RestService.java:91) at com.openshift.internal.client.RestService.request(RestService.java:72) at com.openshift.internal.client.AbstractOpenShiftConnectionFactory.getConnection(AbstractOpenShiftConnectionFactory.java:34) at com.openshift.client.OpenShiftConnectionFactory.getConnection(OpenShiftConnectionFactory.java:161) at com.openshift.client.utils.TestConnectionFactory.getConnection(TestConnectionFactory.java:31) at com.openshift.internal.client.ApplicationResourceIntegrationTest.setUp(ApplicationResourceIntegrationTest.java:50) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:57) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43) at java.lang.reflect.Method.invoke(Method.java:616) at org.junit.runners.model.FrameworkMethod$1.runReflectiv {code} -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13683) JPP not instantiated by runtime detection

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13683?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-13683: --------------------------------------- Verified in JBDS 6.0.1.CR1a B338. Will close when verified in JBDS 7.0.0.Alpha2. > JPP not instantiated by runtime detection > ----------------------------------------- > > Key: JBIDE-13683 > URL: https://issues.jboss.org/browse/JBIDE-13683 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 4.0.1.Final > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 4.0.1.Final, 4.1.0.Alpha2 > > > Use runtime detection against a folder containing JPP 6, and try to have it create the server. It does not create any server. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-11319) Use Eclipse-SourceReferences

by Max Rydahl Andersen (JIRA)

[ https://issues.jboss.org/browse/JBIDE-11319?page=com.atlassian.jira.plugi... ] Max Rydahl Andersen commented on JBIDE-11319: --------------------------------------------- I believe [~dgolovin] already did this earlier - Denis, did you try? > Use Eclipse-SourceReferences > ---------------------------- > > Key: JBIDE-11319 > URL: https://issues.jboss.org/browse/JBIDE-11319 > Project: Tools (JBoss Tools) > Issue Type: Enhancement > Components: Build/Releng > Reporter: Mickael Istria > Assignee: Mickael Istria > Priority: Optional > Fix For: 4.1.x > > > In order to provide nice entry points to turn users into contributors, it could be efficient to set Eclipse-SourceReferences in Manifest: http://wiki.eclipse.org/PDE/UI/SourceReferences -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-12361) PRoblem with WorkspaceFIlesetVirtualComponent, publish using fileset virtual component

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12361?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-12361. --------------------------------- Closing again. Please put JIRAs back to the previous state after reopening for release notes. > PRoblem with WorkspaceFIlesetVirtualComponent, publish using fileset virtual component > -------------------------------------------------------------------------------------- > > Key: JBIDE-12361 > URL: https://issues.jboss.org/browse/JBIDE-12361 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers > Affects Versions: 3.3.1 > Reporter: Rob Stryker > Assignee: Rob Stryker > Fix For: 3.3.2, 4.0.0.Alpha1 > > Attachments: JBIDE-12361.33x.patch, JBIDE-12361.33x.v2.patch > > > Steps to reproduce: > 1) Create a dynamic web project > 2) Create a POJP > 3) Inside POJP, make some file structure (foldera, foldera/file1.txt, foldera/file2.txt, folderb, folderb/b1.txt, etc) > 4) Right-click web project, go to deployment assembly page > 5) click add > 6) click 'fileset' > 7) set root to /pojp > 8) set includes pattern to **/file1* > 9) finish > 10) publish this to some server > You will note that matching files inside a subdirectory that is not explicitly included in the includes pattern does not get included. In this case, foldera/file1.txt will not be included, and folder 'foldera' will also not be created in the deployment. This is a bug. > Part of this commit has been made over at JBIDE-12360 by accident -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13346) DirectoryScanner fails on non-existing folders

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13346?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-13346. --------------------------------- Closing again. Please put JIRAs back to the previous state after reopening for release notes. > DirectoryScanner fails on non-existing folders > ---------------------------------------------- > > Key: JBIDE-13346 > URL: https://issues.jboss.org/browse/JBIDE-13346 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: Archives, JBossAS/Servers > Affects Versions: 4.0.0.Final > Environment: Windows XP/Windows 7 > Eclipse 4.3M4 > Reporter: Jesper Skov > Assignee: Rob Stryker > Priority: Minor > Fix For: 4.0.1.Final, 4.1.0.Alpha1 > > Attachments: org.eclipse.wst.common.component > > > DirectoryScanner can be made to fail on non-existing folders. > In our setup, these folders are possibly picked up from the Deployment Assembly settings. > The folders are created by our custom Builder with highest priority, so appears to work properly with everything else in Eclipse. > But it seems the Archive DirectoryScanner runs before our builder. > The stack trace looks like this: > > {code} > java.lang.IllegalStateException: basedir C:\udvikler\ws\plugins\jb.it.reuters\build\gen-lib-deployable is not a directory > at org.jboss.ide.eclipse.archives.core.asf.DirectoryScanner.scanPrepare(DirectoryScanner.java:552) > at org.jboss.ide.eclipse.archives.core.asf.DirectoryScanner.scan(DirectoryScanner.java:588) > at org.jboss.ide.eclipse.archives.core.model.DirectoryScannerFactory.createDirectoryScanner(DirectoryScannerFactory.java:66) > at org.jboss.ide.eclipse.archives.webtools.filesets.vcf.WorkspaceFilesetVirtualComponent$WorkspaceFilter.<init>(WorkspaceFilesetVirtualComponent.java:100) > at org.jboss.ide.eclipse.archives.webtools.filesets.vcf.WorkspaceFilesetVirtualComponent.getRootFolder(WorkspaceFilesetVirtualComponent.java:53) > at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.consumeComponent(FlatVirtualComponent.java:203) > at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.addConsumedReferences(FlatVirtualComponent.java:196) > at org.eclipse.jst.j2ee.internal.common.ClasspathLibraryExpander.optimize(ClasspathLibraryExpander.java:47) > at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.cacheResources(FlatVirtualComponent.java:119) > at org.eclipse.wst.common.componentcore.internal.flat.FlatVirtualComponent.fetchResources(FlatVirtualComponent.java:101) > at org.eclipse.jst.j2ee.internal.common.ClasspathLibraryExpander.fetchResource(ClasspathLibraryExpander.java:74) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.getBaseEARLibRefs(J2EEComponentClasspathContainer.java:463) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.requiresUpdate(J2EEComponentClasspathContainer.java:208) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathContainer.refresh(J2EEComponentClasspathContainer.java:540) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.processModules(J2EEComponentClasspathUpdater.java:311) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.access$4(J2EEComponentClasspathUpdater.java:295) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob$1.run(J2EEComponentClasspathUpdater.java:336) > at org.eclipse.core.runtime.SafeRunner.run(SafeRunner.java:42) > at org.eclipse.jst.j2ee.internal.common.classpath.J2EEComponentClasspathUpdater$ModuleUpdateJob.run(J2EEComponentClasspathUpdater.java:321) > at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53) > {code} -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-12725) Name of JBoss server cannot be changed

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-12725?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-12725. --------------------------------- Verified. > Name of JBoss server cannot be changed > -------------------------------------- > > Key: JBIDE-12725 > URL: https://issues.jboss.org/browse/JBIDE-12725 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers, UpStream > Affects Versions: 4.0.0.Alpha2 > Reporter: Jaroslav Jankovič > Assignee: Rob Stryker > Fix For: 4.0.1.Final > > Attachments: JBIDE-12725-bug.ogv, JBIDE-12725.ogg, JBIDE-12725.ogg > > > https://bugs.eclipse.org/bugs/show_bug.cgi?id=390993 > Created a bug and patch upstream > SR2 is scheduled for GA: 2/22 (http://wiki.eclipse.org/Juno/Simultaneous_Release_Plan#SR2) -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13762) add ui to handle error in case of typo in system properties or discovery plugin

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-13762: ------------------------------------------- Summary: add ui to handle error in case of typo in system properties or discovery plugin Key: JBIDE-13762 URL: https://issues.jboss.org/browse/JBIDE-13762 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: central Reporter: Max Rydahl Andersen Assignee: Snjezana Peco if system properties are broken or discovery has bugs (i.e. bad url or url/host not found) there currently are no error handling that inform the user nor us what went wrong. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13690) Detect future EAP 6 based server like SOA-P

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13690?page=com.atlassian.jira.plugi... ] Martin Malina commented on JBIDE-13690: --------------------------------------- [~rob.stryker] so such an altered EAP should be detected as what exactly? EAP 6.1, right? I'm getting AS 7.2 from runtime detection. But I think I need to wait for the next respin (of JBT 4.0.1) for the fix to get in. > Detect future EAP 6 based server like SOA-P > ------------------------------------------- > > Key: JBIDE-13690 > URL: https://issues.jboss.org/browse/JBIDE-13690 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: JBossAS/Servers, runtime-detection > Reporter: Max Rydahl Andersen > Assignee: Len DiMaggio > Priority: Blocker > Labels: new_and_noteworthy, respin-a > Fix For: 4.0.1.Final, 4.1.0.Alpha2 > > > To be sure future AS7/EAP 6 based servers such as SOA-P 6 can be detected and started as an EAP 6 we need to provide a fallback for this instead of the currrent hardcoding of eap slots. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13537) Unable to create EAP6.1 server [4.0.1 maintenance]

by Martin Malina (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13537?page=com.atlassian.jira.plugi... ] Martin Malina closed JBIDE-13537. --------------------------------- Closing again. > Unable to create EAP6.1 server [4.0.1 maintenance] > --------------------------------------------------- > > Key: JBIDE-13537 > URL: https://issues.jboss.org/browse/JBIDE-13537 > Project: Tools (JBoss Tools) > Issue Type: Bug > Components: JBossAS/Servers, runtime-detection > Affects Versions: 4.1.0.Alpha1 > Reporter: Rastislav Wagner > Assignee: Rob Stryker > Priority: Blocker > Labels: new_and_noteworthy > Fix For: 4.0.1.Final > > Attachments: New Server Runtime Environment _002.png, New Server Runtime Environment _003.png > > > EAP6.1 is detected via runtime detection but nothing happens when I click OK to create runtime. Also manually adding it through Runtime Enviroment -> add -> EAP6.x does not work. -- 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

13 years

1
0
0 / 0

[JBoss JIRA] (JBIDE-13750) 2 failures in org.jboss.tools.as.test.core

by Rob Stryker (JIRA)

[ https://issues.jboss.org/browse/JBIDE-13750?page=com.atlassian.jira.plugi... ] Rob Stryker resolved JBIDE-13750. --------------------------------- Resolution: Done pushed to master > 2 failures in org.jboss.tools.as.test.core > ------------------------------------------ > > Key: JBIDE-13750 > URL: https://issues.jboss.org/browse/JBIDE-13750 > Project: Tools (JBoss Tools) > Issue Type: Feature Request > Components: JBossAS/Servers > Affects Versions: 4.1.0.Alpha1 > Reporter: Martin Malina > Assignee: Rob Stryker > Fix For: 4.1.0.Alpha2 > > > While verifying JBIDE-13459 I checked the current results and saw two remaining failures in https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/JBossTools/view/JBo... > {code} > >>> org.jboss.tools.as.test.core.launch.MockArgsTests.testRemoveCriticalVMArgs[11] 50 sec 11 > >>> org.jboss.tools.as.test.core.classpath.EJB3SupportVerifierTest.testEJB30Support[12] 12 ms 11 > {code} -- 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

13 years

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 March 2013