[
https://issues.jboss.org/browse/JBIDE-20826?page=com.atlassian.jira.plugi...
]
Lucia Jelinkova commented on JBIDE-20826:
-----------------------------------------
No, the Maven import works fine, that's why I've added Easymport to the
components.
The difference is that while Easymport names the Eclipse project by the same name as the
git folder name (batch-processing), the Maven import names it by the artifact id from pom
file (jboss-batch-processing/). This causes that the context-root in settings (mentioned
in the Description section) are different and when deployed to the server it is all mixed
up.
I am not sure, which component to blame. EI should probably make sure, that the settings
are correct but on the other hand, AS should be able to detect the right context root too.
Web module's URL is not detected correctly
------------------------------------------
Key: JBIDE-20826
URL:
https://issues.jboss.org/browse/JBIDE-20826
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: easymport, server
Affects Versions: 4.3.0.CR1
Reporter: Lucia Jelinkova
The module's URL is not detected correctly in case project name is different to
context-root mentioned in .settings/org.eclipse.wst.common.component.
This could happen for example when you import Maven project using Easymport.
--
This message was sent by Atlassian JIRA
(v6.4.11#64026)