[jbosstools-dev] [jdf-dev] JDF Quickstarts in JBoss Central?

Max Rydahl Andersen max.andersen at redhat.com
Thu Oct 11 12:30:39 EDT 2012


>>>>>>> Can we check what the actual problem is here?
>>>>>> When the project you import is directly located in your workspace folder, the project name in eclipse must match the folder name. This is a limitation in Eclipse. So when we import quickstarts in the workspace (the default behaviour), eclipse uses the folder name, not the artifact id


>>>>>> The context root is set by m2e-wtp according to the maven rules. WTP uses it to open a browser when it receives the signal the app deployment is complete. However, the AS server adapter in JBT does not respect the context root as declared in the project, deploys it using the project name in the workspace instead. This mismatch between war file and context root leads to a 404.
>>>>>> 
>>>>>> Easiest/cheapest solution here (by far) is to add a <finalName> in the pom.xmls that matches the folder name. Leads to shorter context name, leads to less typing, leads to developer happiness.
>>>>> Except that this will break the maven import.
>>>> Why?
>>> 
>>> From experience, here the artifact id must be the same as the context root.
>> You should try again then :-)
>> Only what you code in your app might lead to such constraint. And that would be a baaad thing
> 
> This definitely failed in the past in JBDS, hence why we aligned all of this. I really don't want to change this rule *again*.

hmm - the only restriction I recall is the same we are bumping into now, projectname == deployment name by default and if that doesn't matches 
yeah you get funkyness.

Could it be that in the past dirname == artifactid  thus it was perceived as being tied to artifactid ?

/max




More information about the jbosstools-dev mailing list