April 2012 - jbosstools-issues - Jboss List Archives

[JBoss JIRA] (JBIDE-11628) Improve perfs of aggregation script

by Mickael Istria (JIRA)

Mickael Istria created JBIDE-11628: -------------------------------------- Summary: Improve perfs of aggregation script Key: JBIDE-11628 URL: https://issues.jboss.org/browse/JBIDE-11628 Project: Tools (JBoss Tools) Issue Type: Enhancement Reporter: Mickael Istria Assignee: Mickael Istria Fix For: 3.3.0.CR1 the aggregation script (build.xml) performs a lot of magic, such as collecting zips and source zips. Some steps may be obsolete and no more necessary, we should clean it to save execution time. -- 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

11 years, 8 months

3
10
0 / 0

[JBoss JIRA] (JBIDE-10299) aggregate SOA source features into a single site

by Nick Boldt (Created) (JIRA)

aggregate SOA source features into a single site ------------------------------------------------ Key: JBIDE-10299 URL: https://issues.jboss.org/browse/JBIDE-10299 Project: Tools (JBoss Tools) Issue Type: Sub-task Components: Build/Releng Reporter: Nick Boldt Fix For: 3.3.0.Beta1 -- 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

11 years, 8 months

4
13
0 / 0

[JBoss JIRA] (JBIDE-10983) openshift properties should show username and host as separate values

by Max Rydahl Andersen (JIRA)

Max Rydahl Andersen created JBIDE-10983: ------------------------------------------- Summary: openshift properties should show username and host as separate values Key: JBIDE-10983 URL: https://issues.jboss.org/browse/JBIDE-10983 Project: Tools (JBoss Tools) Issue Type: Bug Components: openshift Reporter: Max Rydahl Andersen Assignee: Andre Dietisheim Fix For: 3.3.0.CR1 its nice to easily copy the git url - should also provide the username and host for easy copy/paste for ssh command line -- 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

11 years, 8 months

2
4
0 / 0

[JBoss JIRA] (JBIDE-11215) JbossTools 3.3.0M5 fail deployment after some time

by Jesper Skov (JIRA)

Jesper Skov created JBIDE-11215: ----------------------------------- Summary: JbossTools 3.3.0M5 fail deployment after some time Key: JBIDE-11215 URL: https://issues.jboss.org/browse/JBIDE-11215 Project: Tools (JBoss Tools) Issue Type: Bug Components: JBossAS/Servers Affects Versions: 3.3.0.M5 Environment: Windows XP, Eclipse 3.7.sr2 Reporter: Jesper Skov Assignee: Rob Stryker JBossTools 3.3.0M5 fails deploying to EAP5.1.1 after some time (after 2-6 hours of many successful deployments). Similar behavior from the nightly build 2012.02.27. M4 is working without problems, and this is the version we revert to when restarts of Eclipse with M5 gets too tedious. The Eclipse log shows JMX console login problems as the (propable) cause, see below. We use admin/admin credentials for the JMX console, and don't change these during the day. Hard to reproduce, but (obviously) we are willing and happy to test any build you might feel should fix this. We don't want to get stranded at M4 :) (I will attach a snapshot of the server configuration page when I get a chance.) Let me know if there is any logging we can tweak to help you find and fix the cause of this. Log output from the 2012.02.27 nightly build: {code} java.lang.SecurityException: Failed to authenticate principal=null, securityDomain=jmx-console at org.jboss.jmx.connector.invoker.AuthenticationInterceptor.invoke(AuthenticationInterceptor.java:89) at org.jboss.mx.server.Invocation.invoke(Invocation.java:90) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) at org.jboss.invocation.jrmp.server.JRMPProxyFactory.invoke(JRMPProxyFactory.java:180) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at org.jboss.mx.interceptor.ReflectedDispatcher.invoke(ReflectedDispatcher.java:157) at org.jboss.mx.server.Invocation.dispatch(Invocation.java:96) at org.jboss.mx.server.Invocation.invoke(Invocation.java:88) at org.jboss.mx.server.AbstractMBeanInvoker.invoke(AbstractMBeanInvoker.java:264) at org.jboss.mx.server.MBeanServerImpl.invoke(MBeanServerImpl.java:668) at org.jboss.invocation.jrmp.server.JRMPInvoker$MBeanServerAction.invoke(JRMPInvoker.java:855) at org.jboss.invocation.jrmp.server.JRMPInvoker.invoke(JRMPInvoker.java:422) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source) at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source) at java.lang.reflect.Method.invoke(Unknown Source) at sun.rmi.server.UnicastServerRef.dispatch(Unknown Source) at sun.rmi.transport.Transport$1.run(Unknown Source) at java.security.AccessController.doPrivileged(Native Method) at sun.rmi.transport.Transport.serviceCall(Unknown Source) at sun.rmi.transport.tcp.TCPTransport.handleMessages(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run0(Unknown Source) at sun.rmi.transport.tcp.TCPTransport$ConnectionHandler.run(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source) at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source) at java.lang.Thread.run(Unknown Source) at sun.rmi.transport.StreamRemoteCall.exceptionReceivedFromServer(Unknown Source) at sun.rmi.transport.StreamRemoteCall.executeCall(Unknown Source) at sun.rmi.server.UnicastRef.invoke(Unknown Source) at org.jboss.invocation.jrmp.server.JRMPInvoker_Stub.invoke(Unknown Source) at org.jboss.invocation.jrmp.interfaces.JRMPInvokerProxy.invoke(JRMPInvokerProxy.java:133) at org.jboss.invocation.InvokerInterceptor.invokeInvoker(InvokerInterceptor.java:365) at org.jboss.invocation.InvokerInterceptor.invoke(InvokerInterceptor.java:197) at org.jboss.jmx.connector.invoker.client.InvokerAdaptorClientInterceptor.invoke(InvokerAdaptorClientInterceptor.java:66) at org.jboss.proxy.SecurityInterceptor.invoke(SecurityInterceptor.java:68) at org.jboss.proxy.ClientMethodInterceptor.invoke(ClientMethodInterceptor.java:74) at org.jboss.proxy.ClientContainer.invoke(ClientContainer.java:101) at $Proxy30.invoke(Unknown Source) at org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.ensureDeployLocationAdded(JMXServerLifecycleListener.java:124) at org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener$1.run(JMXServerLifecycleListener.java:65) at org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:71) at org.jboss.ide.eclipse.as.jmx.integration.JMXSafeRunner.run(JMXSafeRunner.java:52) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnection.run(JBossServerConnection.java:97) at org.jboss.ide.eclipse.as.jmx.integration.JBossServerConnectionProvider.run(JBossServerConnectionProvider.java:58) at org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.doDeploymentAddition(JMXServerLifecycleListener.java:69) at org.jboss.ide.eclipse.as.jmx.integration.JMXServerLifecycleListener.serverChanged(JMXServerLifecycleListener.java:55) at org.jboss.ide.eclipse.as.core.server.UnitedServerListenerManager.serverChanged(UnitedServerListenerManager.java:128) at org.eclipse.wst.server.core.internal.ServerNotificationManager.broadcastChange(ServerNotificationManager.java:125) at org.eclipse.wst.server.core.internal.Server.fireServerStateChangeEvent(Server.java:735) at org.eclipse.wst.server.core.internal.Server.setServerState(Server.java:643) at org.eclipse.wst.server.core.model.ServerBehaviourDelegate.setServerState(ServerBehaviourDelegate.java:143) at org.jboss.ide.eclipse.as.core.server.internal.DeployableServerBehavior.setServerStarted(DeployableServerBehavior.java:194) at org.jboss.ide.eclipse.as.core.server.internal.DelegatingServerBehavior.setServerStarted(DelegatingServerBehavior.java:91) at org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate.setServerStarted(AbstractJBossBehaviourDelegate.java:128) at org.jboss.ide.eclipse.as.core.server.internal.AbstractJBossBehaviourDelegate$1.stateAsserted(AbstractJBossBehaviourDelegate.java:102) at org.jboss.ide.eclipse.as.core.server.internal.PollThread.alertListener(PollThread.java:232) at org.jboss.ide.eclipse.as.core.server.internal.PollThread.handlePollerHasAnswer(PollThread.java:161) at org.jboss.ide.eclipse.as.core.server.internal.PollThread.run(PollThread.java:149) {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

11 years, 8 months

5
56
0 / 0

[JBoss JIRA] Created: (JBIDE-8132) Changes in Source tab are not synchronized with Design (graphical) tab for extension activities

by Robert (Bob) Brodt (JIRA)

Changes in Source tab are not synchronized with Design (graphical) tab for extension activities ----------------------------------------------------------------------------------------------- Key: JBIDE-8132 URL: https://issues.jboss.org/browse/JBIDE-8132 Project: Tools (JBoss Tools) Issue Type: Bug Components: bpel Affects Versions: 3.2.0.CR1 Reporter: Robert (Bob) Brodt Assignee: Robert (Bob) Brodt Fix For: 3.2.x This was reported here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=332926 I have applied a patch to the BPEL editor code line at eclipse.org, but it needs to be merged into jboss code. Also, we need to build a SWTBot test that exercises extension activities. It should include a real-life sample (maybe the model and UI extensions from SMILA?) -- This message is automatically generated by JIRA. - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

3
7
0 / 0

[JBoss JIRA] (JBIDE-11534) Wrong error on <jar-file/> option in multi-module EAR

by Marius Bogoevici (JIRA)

Marius Bogoevici created JBIDE-11534: ---------------------------------------- Summary: Wrong error on <jar-file/> option in multi-module EAR Key: JBIDE-11534 URL: https://issues.jboss.org/browse/JBIDE-11534 Project: Tools (JBoss Tools) Issue Type: Bug Components: hibernate Affects Versions: 3.3.0.Beta2 Reporter: Marius Bogoevici Assignee: Dmitry Geraskov In a multi-module ear, one of the modules has a persistence.xml file which uses the following option to reference another module. {code} <jar-file>snowdrop-domain.jar</jar-file> {code} This results in a validation error in JBDS/JBoss Tools, the jar is deemed not to be found. -- 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

11 years, 8 months

5
20
0 / 0

[JBoss JIRA] Created: (JBIDE-9443) Wizard for creating Service implementations (ServiceLoader / Service file)

by Lincoln Baxter III (JIRA)

Wizard for creating Service implementations (ServiceLoader / Service file) -------------------------------------------------------------------------- Key: JBIDE-9443 URL: https://issues.jboss.org/browse/JBIDE-9443 Project: Tools (JBoss Tools) Issue Type: Feature Request Affects Versions: 3.3.0.M2 Reporter: Lincoln Baxter III It would be very nice if we had a wizard or hotkey to create a new service implementation: CTRL-N --> New Service Implementation Class 1. Wizard asks you to specify the service Interface you wish to implement, and then lets you give the typical new-class information (with Interface already populated and greyed out.) 2. When submitted, the wizard creates the implementing class, and also creates a service file in the java-resources 'META-INF/services' directory, containing the name of your service implementation class. If the Service file already exists, your class should be added to it on a new line: META-INF/services/org.example.service.spi.Interface -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

8
30
0 / 0

[JBoss JIRA] Created: (JBIDE-8654) New Instance wizard: add capability to create server adapter from instance

by Andre Dietisheim (JIRA)

New Instance wizard: add capability to create server adapter from instance -------------------------------------------------------------------------- Key: JBIDE-8654 URL: https://issues.jboss.org/browse/JBIDE-8654 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: deltacloud Affects Versions: 3.2.0.Final, 3.3.0.M1 Reporter: Andre Dietisheim Assignee: Andre Dietisheim Fix For: 3.3.x Currently you may create a new server adapter in 2 ways: 1) fully automatically when launching the instance: check "Create Server Adapter" 2) manually: * launch an instance * show in remote system explorer (creates the RSE connection) * create server adapter, switch it to remote mode and use the RSE connection as host Option 1) is pretty error prone. If 1 of the 3 tasks fail no server adapter is created and it's hard to find out why it went wrong. IMHO the process is too automatic, too long, too intrasparent. Option 2) is pretty transparent, but not obvious. We would improve the situation if we would offer an action "Create Server Adapter" in the context menu of the instances. -- This message is automatically generated by JIRA. For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

3
4
0 / 0

[JBoss JIRA] (JBIDE-11689) Target Platforms Should Optionally Include Source Code

by Dan Florian (JIRA)

Dan Florian created JBIDE-11689: ----------------------------------- Summary: Target Platforms Should Optionally Include Source Code Key: JBIDE-11689 URL: https://issues.jboss.org/browse/JBIDE-11689 Project: Tools (JBoss Tools) Issue Type: Feature Request Components: target-platform Affects Versions: 3.3.0.Beta3 Reporter: Dan Florian Assignee: Mickael Istria Fix For: 3.4.x When developers are researching issues they typically end up debugging in classes found in the target platform. It would be nice if the JBT target platforms optionally could contain source or if new target platforms with source could be created. -- 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

11 years, 8 months

3
6
0 / 0

[JBoss JIRA] Created: (JBDS-1377) Eclipse Makretplace in JBDS

by Libor Zoubek (JIRA)

Eclipse Makretplace in JBDS --------------------------- Key: JBDS-1377 URL: https://jira.jboss.org/browse/JBDS-1377 Project: Developer Studio (JBoss Developer Studio) Issue Type: Feature Request Components: Build Affects Versions: 4.0.0.Beta1 Reporter: Libor Zoubek It would be nice to have Eclipse market place available in JBDS. It is present in JBT (when I install it on top of helios-jee bundle), but it is missing in JBDS (probably because we build JBDS against SDK). -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.jboss.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira

11 years, 8 months

4
8
0 / 0

2024

2023

2022

2021

2020

2019

2018

2017

2016

2015

2014

2013

2012

2011

2010

2009

2008

2007

2006

jbosstools-issues April 2012