[JBoss JIRA] (JBIDE-15793) Cordova Feature multiselection is not working
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15793?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen commented on JBIDE-15793:
---------------------------------------------
[~vpakan] this sounds like a separate bug and not related to multi selection ?
> 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
[JBoss JIRA] (JBIDE-15802) Unable to import Cordova Plugin from Git
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15802?page=com.atlassian.jira.plugi... ]
Vlado Pakan resolved JBIDE-15802.
---------------------------------
Resolution: Done
Working with git repo URL provided by Gorkem.
> Unable to import Cordova Plugin from Git
> ----------------------------------------
>
> Key: JBIDE-15802
> URL: https://issues.jboss.org/browse/JBIDE-15802
> 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
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> 1. Create Hybrid Mobile project
> 2. Open config.xml in Corodova Configuration editor
> 3. Click on button Add.. to add Feature
> 4. Click on Git tab of Cordova Plugins Discovery dialog
> 5. Write some Plugins git repo to URL text
> ERROR: Finish button is always disabled so it's not possible to add Plugin from Git repo
--
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-15802) Unable to import Cordova Plugin from Git
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15802?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-15802:
-------------------------------------
Should I create new Feature request for dialog displaying "Add feature" problems?
> Unable to import Cordova Plugin from Git
> ----------------------------------------
>
> Key: JBIDE-15802
> URL: https://issues.jboss.org/browse/JBIDE-15802
> 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
>
> Original Estimate: 0 minutes
> Remaining Estimate: 0 minutes
>
> 1. Create Hybrid Mobile project
> 2. Open config.xml in Corodova Configuration editor
> 3. Click on button Add.. to add Feature
> 4. Click on Git tab of Cordova Plugins Discovery dialog
> 5. Write some Plugins git repo to URL text
> ERROR: Finish button is always disabled so it's not possible to add Plugin from Git repo
--
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-2738) Support OpenShift 2.0 features
by Andre Dietisheim (JIRA)
[ https://issues.jboss.org/browse/JBDS-2738?page=com.atlassian.jira.plugin.... ]
Andre Dietisheim commented on JBDS-2738:
----------------------------------------
we should close this as partially completed (2 top priorities as discussed)
> Support OpenShift 2.0 features
> ------------------------------
>
> Key: JBDS-2738
> URL: https://issues.jboss.org/browse/JBDS-2738
> Project: Developer Studio (JBoss Developer Studio)
> Issue Type: Feature Request
> Security Level: Public(Everyone can see)
> Components: openshift
> Reporter: Max Rydahl Andersen
> Assignee: Andre Dietisheim
> Priority: Blocker
> Fix For: 7.1.0.Beta1
>
>
> OpenShift 2.0 is coming, needs to investigate when that happens and what it implies for eclipse (and eventually Forge) tooling.
> This functionallity would need to be added without breaking how we work with current openshift online and openshift enterprise which has 1.x api's.
> Opening this issue to track issues related to this (please create subtasks)
--
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-15826) Incorrect Constraint Problem for JSF composite component
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15826?page=com.atlassian.jira.plugi... ]
Vlado Pakan commented on JBIDE-15826:
-------------------------------------
Tested with JBDS7.1.0.Beta1b Beta1-v20131102-1529-B493
There is no warning anymore but looks like now user can specify any value for required attribute neither true/false nor EL variable. Any string will be accepted as correct value. Is it ok?
> Incorrect Constraint Problem for JSF composite component
> --------------------------------------------------------
>
> Key: JBIDE-15826
> URL: https://issues.jboss.org/browse/JBIDE-15826
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: common/jst/core, jsf
> Affects Versions: 4.1.0.Final
> Reporter: Alexey Kazakov
> Assignee: Viacheslav Kabanovich
> Priority: Critical
> Labels: respin-b
> Fix For: 4.1.1.Beta1
>
>
> First at all we must have a preference page where we can disable this validation.
> There should not be any validation which is imposible to disable.
> Every validation problem should have a default quick fix which opens the corresponding preference page and disable this validation rule.
> We have such preferences/quick fixes for our validation that extends common validation framework.
> But this one is a part of XModel validation (https://github.com/jbosstools/jbosstools-base/blob/master/common/plugins/...).
--
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 edited comment on JBIDE-15851 at 11/4/13 11:36 AM:
---------------------------------------------------------------
As explained on IRC, this is a behavior discrepancy between javac and jdt.
jdt requires the servlet api to be on the classpath, so it needs to be added (the version is managed by the jboss boms)
You can see the same issue if you tell maven CLI builds to use jdt instead of javac :
{noformat}
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.1</version>
<configuration>
<!-- http://maven.apache.org/plugins/maven-compiler-plugin/ -->
<source>1.6</source>
<target>1.6</target>
<compilerId>jdt</compilerId>
</configuration>
<dependencies>
<dependency>
<groupId>org.eclipse.tycho</groupId>
<artifactId>tycho-compiler-jdt</artifactId>
<version>0.19.0</version>
</dependency>
</dependencies>
</plugin>
{noformat}
Best solution is to add the servlet dependency to the project pom
was (Author: fbricon):
As explained on IRC, this is a behavior discrepancy between javac and jdt.
jdt requires the servlet api to be on the classpath, so it needs to be added (the version is managed by the jboss boms)
You can see the same issue if you tell maven CLI builds to use jdt instead of javac :
{noformat}
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.1</version>
<configuration>
<!-- http://maven.apache.org/plugins/maven-compiler-plugin/ -->
<source>1.6</source>
<target>1.6</target>
<compilerId>jdt</compilerId>
</configuration>
<dependencies>
<dependency>
<groupId>org.eclipse.tycho</groupId>
<artifactId>tycho-compiler-jdt</artifactId>
<version>0.19.0</version>
</dependency>
</dependencies>
</plugin>
{noformat}
> 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: maven, upstream
> 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-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 commented on JBIDE-15851:
-------------------------------------
As explained on IRC, this is a behavior discrepancy between javac and jdt.
jdt requires the servlet api to be on the classpath, so it needs to be added (the version is managed by the jboss boms)
You can see the same issue if you tell maven CLI builds to use jdt instead of javac :
{noformat}
<plugin>
<groupId>org.apache.maven.plugins</groupId>
<artifactId>maven-compiler-plugin</artifactId>
<version>3.1</version>
<configuration>
<!-- http://maven.apache.org/plugins/maven-compiler-plugin/ -->
<source>1.6</source>
<target>1.6</target>
<compilerId>jdt</compilerId>
</configuration>
<dependencies>
<dependency>
<groupId>org.eclipse.tycho</groupId>
<artifactId>tycho-compiler-jdt</artifactId>
<version>0.19.0</version>
</dependency>
</dependencies>
</plugin>
{noformat}
> 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: maven, upstream
> 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-15648) Add tests for EAP 6.2 to integration tests
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15648?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-15648:
----------------------------------------
Fix Version/s: 4.1.1.CR1
(was: 4.1.1.Beta1)
> Add tests for EAP 6.2 to integration tests
> ------------------------------------------
>
> Key: JBIDE-15648
> URL: https://issues.jboss.org/browse/JBIDE-15648
> Project: Tools (JBoss Tools)
> Issue Type: Task
> Components: qa
> Affects Versions: 4.1.1.Alpha1
> Reporter: Martin Malina
> Assignee: Radim Hopp
> Fix For: 4.1.1.CR1
>
>
> Please add a new test suite for EAP 6.2. In the tools it uses the type EAP 6.1+ (previously EAP 6.1), but since there is a new message in the welcome web page, it is probably better to have new test classes for EAP 6.2:
> Radim Hatlapatka said:
> {quote}
> Ahoj, z duvodu brandingu se zmenil text na uvodni strance EAPu z "Welcome to EAP 6" na "Welcome to JBoss EAP 6"
> {quote}
--
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-15635) Null Pointer when code assumes runtime type cannot be null
by Max Rydahl Andersen (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15635?page=com.atlassian.jira.plugi... ]
Max Rydahl Andersen updated JBIDE-15635:
----------------------------------------
Summary: Null Pointer when code assumes runtime type cannot be null (was: Central shows error if workspace contains server adapters which plugins are not loaded)
> Null Pointer when code assumes runtime type cannot be null
> ----------------------------------------------------------
>
> Key: JBIDE-15635
> URL: https://issues.jboss.org/browse/JBIDE-15635
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: server
> Environment: Mac OSX 10.8.5
> Oracle JDK 1.7.0_40
> JBoss Developer Studio
> Version: 7.0.1.GA
> Build id: GA-v20130930-2238-B7
> Build date: 20130930-2238
> Reporter: Cojan van Ballegooijen
> Assignee: Rob Stryker
> Fix For: 4.1.1.CR1
>
> Attachments: jbosstools-diagnostics-20131008232745.zip, Screen Shot 2013-10-08 at 2.22.05 PM.png
>
>
> - Installed JBoss Developer 7.0.0GA using
> - Upgraded to 7.0.1GA
> - Starting JBoss Developer Studio shows the following error window
> An internal error occurred during: "Refreshing JBoss Tutorials...".
> java.lang.NullPointerException
> - The error mentioned before also occurs when doing a refresh inside JBoss Central in the Start from a sample "portlet"
> - Starting a new Java EE Web project results in the following error
> An error has occurred. See error log for more details.
> java.lang.NullPointerException
> No error log is created in ~/workspace, tried to find *.log file in JBoss Developer Studio installation directory, no log files.
> Found .log in ~/workspace/.metadata
> !SESSION 2013-10-08 16:14:47.792 -----------------------------------------------
> eclipse.buildId=unknown
> java.version=1.7.0_40
> java.vendor=Oracle Corporation
> BootLoader constants: OS=macosx, ARCH=x86_64, WS=cocoa, NL=en_US
> Framework arguments: -product com.jboss.jbds.product.product -keyring /Users/cballego/.eclipse_keyring -showlocation
> Command-line arguments: -os macosx -ws cocoa -arch x86_64 -product com.jboss.jbds.product.product -keyring /Users/cballego/.eclipse_keyring -consoleLog -showlocation
> !ENTRY org.eclipse.core.net 1 0 2013-10-08 16:14:52.252
> !MESSAGE System property http.nonProxyHosts has been set to local|*.local|169.254/16|*.169.254/16 by an external source. This value will be overwritten using the values from the preferences
> !ENTRY org.eclipse.jface 2 0 2013-10-08 16:14:52.626
> !MESSAGE Keybinding conflicts occurred. They may interfere with normal accelerator operation.
> !SUBENTRY 1 org.eclipse.jface 2 0 2013-10-08 16:14:52.626
> !MESSAGE A conflict occurred for ALT+COMMAND+Z:
> Binding(ALT+COMMAND+Z,
> ParameterizedCommand(Command(org.jboss.tools.cdi.ui.open.namedBean,Open CDI Named Bean,
> Open CDI Named Bean,
> Category(org.eclipse.ui.category.navigate,Navigate,null,true),
> org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@54158353,
> ,,true),null),
> org.eclipse.ui.defaultAcceleratorConfiguration,
> org.eclipse.ui.contexts.window,,,system)
> Binding(ALT+COMMAND+Z,
> ParameterizedCommand(Command(org.eclipse.jdt.ui.edit.text.java.surround.with.quickMenu,Surround With Quick Menu,
> Shows the Surround With quick menu,
> Category(org.eclipse.jdt.ui.category.source,Source,Java Source Actions,true),
> org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@5060e945,
> ,,true),null),
> org.eclipse.ui.defaultAcceleratorConfiguration,
> org.eclipse.ui.contexts.window,,cocoa,system)
> !SUBENTRY 1 org.eclipse.jface 2 0 2013-10-08 16:14:52.626
> !MESSAGE A conflict occurred for COMMAND+SHIFT+F10:
> Binding(COMMAND+SHIFT+F10,
> ParameterizedCommand(Command(org.jboss.tools.common.ui.RegisterAsService,Register As Service,
> Adds class name to META-INF/services/%serviceType% file after service type is selected in the dialog from types extended and implemented by the class.,
> Category(org.eclipse.ui.category.file,File,null,true),
> org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@a72da3d,
> ,,true),null),
> org.eclipse.ui.defaultAcceleratorConfiguration,
> org.eclipse.ui.contexts.window,,,system)
> Binding(COMMAND+SHIFT+F10,
> ParameterizedCommand(Command(org.eclipse.ui.window.showSystemMenu,Show System Menu,
> Show the system menu,
> Category(org.eclipse.ui.category.window,Window,null,true),
> org.eclipse.ui.internal.WorkbenchHandlerServiceHandler@7a55e026,
> ,,true),null),
> org.eclipse.ui.defaultAcceleratorConfiguration,
> org.eclipse.ui.contexts.window,,cocoa,system)
> !ENTRY org.eclipse.core.jobs 4 2 2013-10-08 16:15:04.413
> !MESSAGE An internal error occurred during: "Refreshing JBoss Tutorials...".
> !STACK 0
> java.lang.NullPointerException
> at org.jboss.tools.as.runtimes.integration.util.RuntimeMatcher.findExistingRuntimes(RuntimeMatcher.java:158)
> at org.jboss.tools.as.runtimes.integration.util.RuntimeMatcher.findExistingRuntimes(RuntimeMatcher.java:151)
> at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.getRuntimesFromPattern(WTPRuntimeFix.java:102)
> at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.getBestRuntime(WTPRuntimeFix.java:248)
> at org.jboss.tools.project.examples.fixes.WTPRuntimeFix.canFix(WTPRuntimeFix.java:130)
> at org.jboss.tools.project.examples.ProjectExamplesActivator.canFix(ProjectExamplesActivator.java:796)
> at org.jboss.tools.central.jobs.RefreshTutorialsJob.run(RefreshTutorialsJob.java:68)
> at org.eclipse.core.internal.jobs.Worker.run(Worker.java:53)
--
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-15486) Export Mobile Application dialog is not working
by Vlado Pakan (JIRA)
[ https://issues.jboss.org/browse/JBIDE-15486?page=com.atlassian.jira.plugi... ]
Vlado Pakan closed JBIDE-15486.
-------------------------------
Dialog is working fine in JBDS7.1.0.Beta1b Beta1-v20131102-1529-B493
But there is still this issue https://issues.jboss.org/browse/JBIDE-14544 so Export didn't finish correctly.
> Export Mobile Application dialog is not working
> -----------------------------------------------
>
> Key: JBIDE-15486
> URL: https://issues.jboss.org/browse/JBIDE-15486
> Project: Tools (JBoss Tools)
> Issue Type: Bug
> Components: aerogear-hybrid
> Affects Versions: 4.1.1.Alpha1
> Environment: Fedora 18 64 bit, KDE, JBT Alpha1-v20130909-0110-B392
> Reporter: Vlado Pakan
> Assignee: Gorkem Ercan
> Priority: Critical
> Labels: respin-b
> Fix For: 4.1.1.Beta1
>
>
> 1. Create new Mobile Hybrid Project.
> 2. Select it and choose Export > Mobile > Export Mobile Application
> 3. Click Next
> ERROR: Nothing happens
> 4. Click Next Again
> ERROR: Dialog with no widget is displayed with error "No platform is selected. Please select a platform"
--
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