[JBoss JIRA] (JBDS-1609) Installer should check system prerequisites and warn user if they are not fullfilled
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-1609?page=com.atlassian.jira.plugin.... ]
Denis Golovin updated JBDS-1609:
--------------------------------
Fix Version/s: 8.0.0.Alpha1
(was: 7.1.x)
> Installer should check system prerequisites and warn user if they are not fullfilled
> ------------------------------------------------------------------------------------
>
> Key: JBDS-1609
> URL: https://issues.jboss.org/browse/JBDS-1609
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: installer
> Affects Versions: 4.0.0.GA
> Reporter: Jiri Peterka
> Assignee: Denis Golovin
> Priority: Critical
> Fix For: 8.0.0.Alpha1
>
>
> To prevent insufficient machine parameters or setting installer should do basic check for some parameters like:
> - memory amount
> - maximum open file limit
> - maximum thread count limit
> - internet connection
> - others reasonable criteria should be added here
> If these criteria aren't met, installer should display add warning page before further installation saying that requirements aren't satisfied and tools may not work properly. Reason for this is that sometimes JBDS is used in very strict environment (typically training rooms, universities, etc where many system resources are limited or blocked) but user isn't warned and after install user can see after that lots of runtime errors and got bad feeling about the tool. This should be avoided and user should be at least warn that he is running JBDS in inappropriate environment.
--
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, 5 months
[JBoss JIRA] (JBDS-2663) Installer cannot find unpack200.exe due to spaces in JDK path on Windows 8
by Denis Golovin (JIRA)
[ https://issues.jboss.org/browse/JBDS-2663?page=com.atlassian.jira.plugin.... ]
Denis Golovin commented on JBDS-2663:
-------------------------------------
I would migrate to IzPack 5 in master only to have time to find and fix all possible issues, for 7.1.1 I fix patch it at build time by replacing LibraryRemover with patched version form http://jira.codehaus.org/browse/IZPACK-960
> Installer cannot find unpack200.exe due to spaces in JDK path on Windows 8
> --------------------------------------------------------------------------
>
> Key: JBDS-2663
> URL: https://issues.jboss.org/browse/JBDS-2663
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Bug
> Security Level: Public(Everyone can see)
> Components: installer, upstream
> Affects Versions: 7.0.0.Beta2
> Environment: Windows 8, Oracle JRE 1.6 x86_64/x86
> Reporter: Denis Golovin
> Assignee: Denis Golovin
> Fix For: 7.1.0.CR1
>
>
> {code}C:\Users\alena\Downloads>java -jar jbdevstudio-product-universal-7.0.0.Beta2-B26
> 1.jar
> java.io.IOException: Cannot run program "C:\Program": CreateProcess error=2, The
> system cannot find the file specified
> at java.lang.ProcessBuilder.start(Unknown Source)
> at java.lang.Runtime.exec(Unknown Source)
> at java.lang.Runtime.exec(Unknown Source)
> at java.lang.Runtime.exec(Unknown Source)
> at com.izforge.izpack.util.LibraryRemover.initJavaExec(Unknown Source)
> at com.izforge.izpack.util.LibraryRemover.<init>(Unknown Source)
> at com.izforge.izpack.util.LibraryRemover.invoke(Unknown Source)
> at com.izforge.izpack.util.Librarian.cleanUp(Unknown Source)
> at com.izforge.izpack.util.Housekeeper.shutDown(Unknown Source)
> at com.izforge.izpack.installer.InstallerFrame.exit(InstallerFrame.java:
> 1161)
> at com.izforge.izpack.installer.InstallerFrame$NavigationHandler.actionP
> erformed(InstallerFrame.java:1562)
> at javax.swing.AbstractButton.fireActionPerformed(Unknown Source)
> at javax.swing.AbstractButton$Handler.actionPerformed(Unknown Source)
> at javax.swing.DefaultButtonModel.fireActionPerformed(Unknown Source)
> at javax.swing.DefaultButtonModel.setPressed(Unknown Source)
> at javax.swing.plaf.basic.BasicButtonListener.mouseReleased(Unknown Sour
> ce)
> at java.awt.Component.processMouseEvent(Unknown Source)
> at javax.swing.JComponent.processMouseEvent(Unknown Source)
> at java.awt.Component.processEvent(Unknown Source)
> at java.awt.Container.processEvent(Unknown Source)
> at java.awt.Component.dispatchEventImpl(Unknown Source)
> at java.awt.Container.dispatchEventImpl(Unknown Source)
> at java.awt.Component.dispatchEvent(Unknown Source)
> at java.awt.LightweightDispatcher.retargetMouseEvent(Unknown Source)
> at java.awt.LightweightDispatcher.processMouseEvent(Unknown Source)
> at java.awt.LightweightDispatcher.dispatchEvent(Unknown Source)
> at java.awt.Container.dispatchEventImpl(Unknown Source)
> at java.awt.Window.dispatchEventImpl(Unknown Source)
> at java.awt.Component.dispatchEvent(Unknown Source)
> at java.awt.EventQueue.dispatchEventImpl(Unknown Source)
> at java.awt.EventQueue.access$400(Unknown Source)
> at java.awt.EventQueue$2.run(Unknown Source)
> at java.awt.EventQueue$2.run(Unknown Source)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown
> Source)
> at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown
> Source)
> at java.awt.EventQueue$3.run(Unknown Source)
> at java.awt.EventQueue$3.run(Unknown Source)
> at java.security.AccessController.doPrivileged(Native Method)
> at java.security.AccessControlContext$1.doIntersectionPrivilege(Unknown
> Source)
> at java.awt.EventQueue.dispatchEvent(Unknown Source)
> at java.awt.EventDispatchThread.pumpOneEventForFilters(Unknown Source)
> at java.awt.EventDispatchThread.pumpEventsForFilter(Unknown Source)
> at java.awt.EventDispatchThread.pumpEventsForHierarchy(Unknown Source)
> at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
> at java.awt.EventDispatchThread.pumpEvents(Unknown Source)
> at java.awt.EventDispatchThread.run(Unknown Source)
> Caused by: java.io.IOException: CreateProcess error=2, The system cannot find th
> e file specified
> at java.lang.ProcessImpl.create(Native Method)
> at java.lang.ProcessImpl.<init>(Unknown Source)
> at java.lang.ProcessImpl.start(Unknown Source)
> ... 47 more{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
12 years, 5 months
[JBoss JIRA] (JBIDE-13870) Can't re-add BrowserSim toolbar to perspective
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-13870?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-13870:
-------------------------------------------
Fix Version/s: 4.2.x
(was: 4.1.x)
> Can't re-add BrowserSim toolbar to perspective
> ----------------------------------------------
>
> Key: JBIDE-13870
> URL: https://issues.jboss.org/browse/JBIDE-13870
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim, upstream
> Affects Versions: 4.0.0.Final
> Environment: Fedora 17, JBDS 6 standalone
> Reporter: Michelle Murray
> Assignee: Konstantin Marmalyukov
> Fix For: 4.2.x
>
>
> I removed the BrowserSim tool bar from the JBoss perspective and then tried to re-add it. But the check box was already selected, indicating it was already enabled, yet the toolbar still wasn't visible. I went back to JBDS 5 to see if it was a problem there to but it doesn't appear to be. This problem is not restricted to the JBoss perspective.
--
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, 5 months
[JBoss JIRA] (JBIDE-11259) BrowserSim: broken layout on Linux
by Konstantin Marmalyukov (JIRA)
[ https://issues.jboss.org/browse/JBIDE-11259?page=com.atlassian.jira.plugi... ]
Konstantin Marmalyukov updated JBIDE-11259:
-------------------------------------------
Fix Version/s: 4.2.x
(was: 4.1.x)
> BrowserSim: broken layout on Linux
> ----------------------------------
>
> Key: JBIDE-11259
> URL: https://issues.jboss.org/browse/JBIDE-11259
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: browsersim
> Affects Versions: 3.3.0.Beta1
> Reporter: Yahor Radtsevich
> Assignee: Konstantin Marmalyukov
> Fix For: 4.2.x
>
> Attachments: BrowserSim_BrokenRender.png, screenshot-1.png
>
>
> *Steps to reproduce:*
> # Run BrowserSim on Linux (I used Ubuntu Linux 11.10 x86_64)
> # Check 'Use Skins' if it is not checked.
> # Select 'Samsung Galaxy Tab 10.1' skin
> # Click 'Turn Left' several times.
> *Actual result:*
> From time to time the layout of the window is broken:
> !screenshot-1.png|thumbnail!
> *Update:*
> Video created by [~rhopp]: http://youtu.be/HKN7hnLQOz8
--
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, 5 months
[JBoss JIRA] (JBIDE-15851) Eclipse fails to compile classes and requires transitive dependencies in the compiler classpath
by Fred Bricon (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15851?page=com.atlassian.jira.plugi... ]
Fred Bricon closed JBIDE-15851.
-------------------------------
Labels: jdt upstream (was: maven upstream)
Resolution: Won't Fix
Closing as it's caused by jdt being more strict than javac.
BTW, the servlet API was not defined as a transitive dependency in maven's reactor. The version is just managed in the dependencyManagement section of the BOM. It's the project responsibility to add it to its classpath.
> Eclipse fails to compile classes and requires transitive dependencies in the compiler classpath
> -----------------------------------------------------------------------------------------------
>
> Key: JBIDE-15851
> URL: https://issues.jboss.org/browse/JBIDE-15851
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Affects Versions: 4.1.0.Final
> Reporter: Vineet Reynolds
> Assignee: Fred Bricon
> Priority: Critical
> Labels: upstream, jdt
> Attachments: kitchensink-spring-matrixvariables.png
>
>
> On importing the kitchensink-spring-matrixvariables quickstart (of WFK quickstarts) into JBDS 7.0.0/7.0.1 GA, the following compiler error is reported:
> {noformat}
> Description Resource Path Location Type
> The type javax.servlet.ServletContext cannot be resolved. It is indirectly referenced from required .class files WebConfig.java /jboss-kitchensink-spring-matrixvariables/src/main/java/org/jboss/as/quickstarts/kitchensink/spring/matrixvariables/config line 1 Java Problem
> {noformat}
> This compilation issue is not encountered when running the build from the command line, either via {{mvn clean compile}} or even {{mvn clean package jboss-as:deploy}}.
> Additionally, the deployment is successful when performed via Maven CLI. The deployment is unusable when Eclipse is used to perform deployment against JBoss EAP 6.1.1 (provided that the Maven compile or package goal was not executed). The following error is reported in the log:
> {noformat}
> 20:34:42,439 ERROR [org.springframework.web.servlet.DispatcherServlet] (http-/0.0.0.0:8080-1) Context initialization failed: org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'org.jboss.as.quickstarts.kitchensink.spring.matrixvariables.config.WebConfig#0' defined in ServletContext resource [/WEB-INF/jboss-as-spring-mvc-context.xml]: Instantiation of bean failed; nested exception is org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.jboss.as.quickstarts.kitchensink.spring.matrixvariables.config.WebConfig$$EnhancerByCGLIB$$fb8c765d]: Constructor threw exception; nested exception is java.lang.Error: Unresolved compilation problem:
> The type javax.servlet.ServletContext cannot be resolved. It is indirectly referenced from required .class files
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:1007) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:953) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:487) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:295) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:292) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:626) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:932) [spring-context-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:479) [spring-context-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at org.springframework.web.servlet.FrameworkServlet.configureAndRefreshWebApplicationContext(FrameworkServlet.java:651) [spring-webmvc-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:599) [spring-webmvc-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:665) [spring-webmvc-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at org.springframework.web.servlet.FrameworkServlet.initWebApplicationContext(FrameworkServlet.java:518) [spring-webmvc-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at org.springframework.web.servlet.FrameworkServlet.initServletBean(FrameworkServlet.java:459) [spring-webmvc-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at org.springframework.web.servlet.HttpServletBean.init(HttpServletBean.java:136) [spring-webmvc-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at javax.servlet.GenericServlet.init(GenericServlet.java:242) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
> at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1194) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:950) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:151) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
> Caused by: org.springframework.beans.BeanInstantiationException: Could not instantiate bean class [org.jboss.as.quickstarts.kitchensink.spring.matrixvariables.config.WebConfig$$EnhancerByCGLIB$$fb8c765d]: Constructor threw exception; nested exception is java.lang.Error: Unresolved compilation problem:
> The type javax.servlet.ServletContext cannot be resolved. It is indirectly referenced from required .class files
> at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:163) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:87) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:1000) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> ... 32 more
> Caused by: java.lang.Error: Unresolved compilation problem:
> The type javax.servlet.ServletContext cannot be resolved. It is indirectly referenced from required .class files
> at org.jboss.as.quickstarts.kitchensink.spring.matrixvariables.config.WebConfig.<init>(WebConfig.java:1) [classes:]
> at org.jboss.as.quickstarts.kitchensink.spring.matrixvariables.config.WebConfig$$EnhancerByCGLIB$$fb8c765d.<init>(<generated>) [spring-core-3.2.3.RELEASE.jar:]
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.7.0_45]
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) [rt.jar:1.7.0_45]
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_45]
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526) [rt.jar:1.7.0_45]
> at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:148) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> ... 34 more
> 20:34:42,444 ERROR [org.apache.catalina.core.ContainerBase.[jboss.web].[default-host].[/jboss-kitchensink-spring-matrixvariables].[jboss-as-kitchensink]] (http-/0.0.0.0:8080-1) JBWEB000235: Allocate exception for servlet jboss-as-kitchensink: java.lang.Error: Unresolved compilation problem:
> The type javax.servlet.ServletContext cannot be resolved. It is indirectly referenced from required .class files
> at org.jboss.as.quickstarts.kitchensink.spring.matrixvariables.config.WebConfig.<init>(WebConfig.java:1) [classes:]
> at org.jboss.as.quickstarts.kitchensink.spring.matrixvariables.config.WebConfig$$EnhancerByCGLIB$$fb8c765d.<init>(<generated>) [spring-core-3.2.3.RELEASE.jar:]
> at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method) [rt.jar:1.7.0_45]
> at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57) [rt.jar:1.7.0_45]
> at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45) [rt.jar:1.7.0_45]
> at java.lang.reflect.Constructor.newInstance(Constructor.java:526) [rt.jar:1.7.0_45]
> at org.springframework.beans.BeanUtils.instantiateClass(BeanUtils.java:148) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at org.springframework.beans.factory.support.SimpleInstantiationStrategy.instantiate(SimpleInstantiationStrategy.java:87) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.instantiateBean(AbstractAutowireCapableBeanFactory.java:1000) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBeanInstance(AbstractAutowireCapableBeanFactory.java:953) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.doCreateBean(AbstractAutowireCapableBeanFactory.java:487) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at org.springframework.beans.factory.support.AbstractAutowireCapableBeanFactory.createBean(AbstractAutowireCapableBeanFactory.java:458) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at org.springframework.beans.factory.support.AbstractBeanFactory$1.getObject(AbstractBeanFactory.java:295) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at org.springframework.beans.factory.support.DefaultSingletonBeanRegistry.getSingleton(DefaultSingletonBeanRegistry.java:223) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at org.springframework.beans.factory.support.AbstractBeanFactory.doGetBean(AbstractBeanFactory.java:292) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at org.springframework.beans.factory.support.AbstractBeanFactory.getBean(AbstractBeanFactory.java:194) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at org.springframework.beans.factory.support.DefaultListableBeanFactory.preInstantiateSingletons(DefaultListableBeanFactory.java:626) [spring-beans-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at org.springframework.context.support.AbstractApplicationContext.finishBeanFactoryInitialization(AbstractApplicationContext.java:932) [spring-context-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at org.springframework.context.support.AbstractApplicationContext.refresh(AbstractApplicationContext.java:479) [spring-context-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at org.springframework.web.servlet.FrameworkServlet.configureAndRefreshWebApplicationContext(FrameworkServlet.java:651) [spring-webmvc-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:599) [spring-webmvc-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at org.springframework.web.servlet.FrameworkServlet.createWebApplicationContext(FrameworkServlet.java:665) [spring-webmvc-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at org.springframework.web.servlet.FrameworkServlet.initWebApplicationContext(FrameworkServlet.java:518) [spring-webmvc-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at org.springframework.web.servlet.FrameworkServlet.initServletBean(FrameworkServlet.java:459) [spring-webmvc-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at org.springframework.web.servlet.HttpServletBean.init(HttpServletBean.java:136) [spring-webmvc-3.2.3.RELEASE.jar:3.2.3.RELEASE]
> at javax.servlet.GenericServlet.init(GenericServlet.java:242) [jboss-servlet-api_3.0_spec-1.0.2.Final-redhat-1.jar:1.0.2.Final-redhat-1]
> at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1194) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> at org.apache.catalina.core.StandardWrapper.allocate(StandardWrapper.java:950) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:151) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:149) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.jpa.interceptor.WebNonTxEmCloserValve.invoke(WebNonTxEmCloserValve.java:50) [jboss-as-jpa-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.jboss.as.web.security.SecurityContextAssociationValve.invoke(SecurityContextAssociationValve.java:169) [jboss-as-web-7.2.1.Final-redhat-10.jar:7.2.1.Final-redhat-10]
> at org.apache.catalina.core.StandardHostValve.invoke(StandardHostValve.java:145) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> at org.apache.catalina.valves.ErrorReportValve.invoke(ErrorReportValve.java:97) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> at org.apache.catalina.core.StandardEngineValve.invoke(StandardEngineValve.java:102) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> at org.apache.catalina.connector.CoyoteAdapter.service(CoyoteAdapter.java:336) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> at org.apache.coyote.http11.Http11Processor.process(Http11Processor.java:856) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> at org.apache.coyote.http11.Http11Protocol$Http11ConnectionHandler.process(Http11Protocol.java:653) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> at org.apache.tomcat.util.net.JIoEndpoint$Worker.run(JIoEndpoint.java:920) [jbossweb-7.2.2.Final-redhat-1.jar:7.2.2.Final-redhat-1]
> at java.lang.Thread.run(Thread.java:744) [rt.jar:1.7.0_45]
> {noformat}
--
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, 5 months
[JBoss JIRA] (JBIDE-15793) Cordova Feature multiselection is not working
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15793?page=com.atlassian.jira.plugi... ]
Vlado Pakan edited comment on JBIDE-15793 at 11/4/13 11:58 AM:
---------------------------------------------------------------
Could be for me it's not working because if you select Cancel button it's not added properly and Cordova Configuration Editor gets broken JBIDE-15843
For me it's almost the same situation as before this fix. User selects more Plug-ins and they are not added if he says Cancel to Overwrite Files. It's improvement because if he says Yes to all Plug-Ins are added but I don't like how it's fixed because after some adding/removing plugins Cordova Configuration Editor seems to be confused.
I can close this Jira because I already reported JBIDE-15843 so malfunction of Cordova Feature Multiselection is recorded properly in Jira.
So [~maxandersen] should I close this one?
was (Author: vpakan):
Could be for me it's not working because if you select Cancel button it's not added properly and Cordova Configuration Editor gets broken https://issues.jboss.org/browse/JBIDE-15843
For me it's almost the same situation as before this fix. User selects more Plug-ins and they are not added if he says Cancel to Overwrite Files. It's improvement because if he says Yes to all Plug-Ins are added but I don't like how it's fixed because after some adding/removing plugins Cordova Configuration Editor seems to be confused.
I can close this Jira because I already reported https://issues.jboss.org/browse/JBIDE-15843 so malfunction of Cordova Feature Multiselection is recorded properly in Jira.
So [~maxandersen] should I close this one?
> Cordova Feature multiselection is not working
> ---------------------------------------------
>
> Key: JBIDE-15793
> URL: https://issues.jboss.org/browse/JBIDE-15793
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Beta1
> Environment: JBT 4.1.1 Beta1-v20131020-0207-B454
> Reporter: Vlado Pakan
> Assignee: Gorkem Ercan
> Labels: respin-b
> Fix For: 4.1.1.Beta1
>
> Attachments: overwritefilesdialog.png
>
>
> 1. Create new Hybrid Mobile project
> 2. Open config.xml file via Cordova Configuration Editor
> 3. Choose Add.. to add features, select more than one feature and click Finish
> ERROR: Only first selected feature is added to project and to config.xml file
--
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, 5 months