[ http://jira.codehaus.org/browse/MEV-176?page=comments#action_50088 ]
Carlos Sanchez commented on MEV-176:
That's exactly the same that happens when you use a deprecated API.
You can follow the instructions at
http://maven.apache.org/guides/mini/guide-m
[ http://jira.codehaus.org/browse/MEV-176?page=comments#action_50087 ]
Brian Fox commented on MEV-176:
---
That leaves users of 1.1 forever looking at a warning. I guess I don't see what
the harm is in updating a pom that we know has a fixable warning.
> Struts
[ http://jira.codehaus.org/browse/MEV-176?page=comments#action_50086 ]
Carlos Sanchez commented on MEV-176:
They should update the pom in next versions
> Struts 1.1 pom has invalid servlet-api dependency
>
[ http://jira.codehaus.org/browse/MEV-176?page=comments#action_50085 ]
Brian Fox commented on MEV-176:
---
Ok, but doesn't that still mean that the pom should be updated? Otherwise
what's the point of the warning?
> Struts 1.1 pom has invalid servlet-api depend
[ http://jira.codehaus.org/browse/MEV-176?page=comments#action_50084 ]
Carlos Sanchez commented on MEV-176:
You get a relocation warning, not an error, everything still works
> Struts 1.1 pom has invalid servlet-api dependency
> -
[ http://jira.codehaus.org/browse/MEV-176?page=comments#action_50083 ]
Brian Fox commented on MEV-176:
---
...in other words, the relocation of servletapi is exactly what caused this
problem
> Struts 1.1 pom has invalid servlet-api dependency
> -
[ http://jira.codehaus.org/browse/MEV-176?page=comments#action_50082 ]
Brian Fox commented on MEV-176:
---
We found this specificaly after cleaning all our repos. The problem is that
struts still refers to the old location and we get the error saying it's been
r
