Remember to use the "provided" scope so you do not include these jars in
your final WAR deployment.

Some containers dislike that so to avoid any confusion later.


-----Original Message-----
From: [email protected] [mailto:[email protected]]
On Behalf Of Jacques Koorts
Sent: 10. maj 2012 12:05
To: Maven Integration for Eclipse users mailing list
Subject: Re: [m2e-users] M2E not working as advertised.

Fixed the 2 problems. Should have used

<dependency>
        <groupId>javax.servlet</groupId>
        <artifactId>javax.servlet-api</artifactId>
        <version>3.0.1</version>
        </dependency>



On Thu, May 10, 2012 at 12:02 PM, Jacques Koorts <[email protected]> wrote:
> update:
>
> Changed wurfl from 1.4 to 1.3
> Ran Maven > Update Project..
> Fixed a wurfl coding change issue (red line) Ran Project > Clean
>
> problems:
> "The import javax.servlet.annotation cannot be resolved"
> "WebListener cannot be resolved to a type"
>
>
> On Thu, May 10, 2012 at 11:57 AM, Jacques Koorts <[email protected]>
wrote:
>> I dont think this is necessary cause it was a maven project to begin
with.
>>
>> On Thu, May 10, 2012 at 11:36 AM, Thorsten Heit <[email protected]>
wrote:
>>> Hi,
>>>
>>>> I think eclipse does not know where to find my class files. It was 
>>>> advertised that you dont need to do mvn eclipse:eclipse anymore, so 
>>>> I didnt.
>>>
>>> Did you enable Maven dependency management for your project at all?
>>> I.e. right-click on your project => Configure => Convert to Maven 
>>> Project
>>>
>>> ?
>>>
>>>
>>> HTH
>>>
>>> Thorsten
>>> _______________________________________________
>>> m2e-users mailing list
>>> [email protected]
>>> https://dev.eclipse.org/mailman/listinfo/m2e-users
>>>
_______________________________________________
m2e-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/m2e-users

_______________________________________________
m2e-users mailing list
[email protected]
https://dev.eclipse.org/mailman/listinfo/m2e-users

Reply via email to