[jbosstools-issues] [JBoss JIRA] (JBIDE-18494) Importing EAP "jboss-logging" quickstart raises errors

Fred Bricon (JIRA) issues at jboss.org
Thu Oct 2 17:16:02 EDT 2014


     [ https://issues.jboss.org/browse/JBIDE-18494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Fred Bricon updated JBIDE-18494:
--------------------------------
    Workaround Description: 
In the <dependencies> section, you need to add 			
<dependency>
	<groupId>org.jboss.spec.javax.servlet</groupId>
	<artifactId>jboss-servlet-api_3.0_spec</artifactId>
	<scope>provided</scope>
</dependency>
                Workaround: Workaround Exists
               Component/s: upstream


The JSP validator/builder needs the Servlet API in the classpath whenever  JSPs are found in a project.

The example needs to be fixed to add jboss-servlet-api_3,0_spec to the project dependencies. In the <dependencies> (not <dependencyManagement>!), one should add : 
{noformat}
			<dependency>
				<groupId>org.jboss.spec.javax.servlet</groupId>
				<artifactId>jboss-servlet-api_3.0_spec</artifactId>
				<scope>provided</scope>
			</dependency>
{noformat}


> Importing EAP "jboss-logging" quickstart raises errors
> ------------------------------------------------------
>
>                 Key: JBIDE-18494
>                 URL: https://issues.jboss.org/browse/JBIDE-18494
>             Project: Tools (JBoss Tools)
>          Issue Type: Bug
>          Components: maven, upstream
>    Affects Versions: 4.2.0.CR1
>         Environment: JBDS 8.0.CR1
> Java 1.7 - OpenJDK
> RHEL6
>            Reporter: Len DiMaggio
>            Assignee: Fred Bricon
>             Fix For: 4.2.0.Final
>
>
> Steps to recreate issue:
> * Dowload, unzip EAP quickstarts from - http://www.jboss.org/quickstarts/eap
> * Install JBDS8.0.CR1
> * Import-> Existing Maven Projects - select the quickstart
> The error raised is:
> The superclass "javax.servlet.http.HttpServlet" was not found on the Java Build Path	home.jsp	/jboss-logging/src/main/webapp	line 1	JSP Problem
> (This can be fixed by adding Maven Managed Dependencies to the Java Build path)



--
This message was sent by Atlassian JIRA
(v6.3.1#6329)


More information about the jbosstools-issues mailing list