[
https://issues.jboss.org/browse/JBIDE-21850?page=com.atlassian.jira.plugi...
]
Mickael Istria commented on JBIDE-21850:
----------------------------------------
[~fbricon]: Shouldn't m2e-wtp set context root to project name rather than artifactId
by default?
Independently of easymport, let's imagine a user creates a webapp in project
"myProject", later they maven-ify it and call the artifact "myWebapp"
(keeping project name to "myProject") and run m2e configuration. Then m2e-wtp
would have the same issue as the one described here, no?
Maven project has wrong context root set up after import
--------------------------------------------------------
Key: JBIDE-21850
URL:
https://issues.jboss.org/browse/JBIDE-21850
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: easymport
Affects Versions: 4.3.1.CR1
Reporter: Radim Hopp
Importing maven project (in my case "servlet-security" from EAP quickstarts)
via easymport has wrong context root (right click on project->Properties->Web
Project Settings) configured.
Name of project is servlet-security, but web context root is jboss-servlet-security
This results into 404 when this project gets deployed to server. IDE opens url
http://localhost:8080/jboss-servlet-security, but correct url is
http://localhost:8080/servlet-security.
Note, that this does not happen when importing this project as existing maven project
(not using easymport).
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)