[
https://issues.jboss.org/browse/JBIDE-10592?page=com.atlassian.jira.plugi...
]
erik van altena commented on JBIDE-10592:
-----------------------------------------
I must add that in the last weeks I have come to understand the 'cascade' of
settings; from Maven poms to Eclipse project through the m2eclipse plugin, and then from
Eclipse project to Jboss Tools. I realize that JBoss Tools has very little to do with the
Maven configuration itself; and it should stay that way IMO.
I did some leg work myself and probably came up with the root of the issue. After some
poor attempts at quickly reproducing (recreate server instance, check out in a fresh
workspace) I didn't come up with anything. Then I realized that in the meanwhile I
might have added either the finalName to the war pom or the bundleFileName to the ear pom
(these override the name of the produced war file through Maven). So I removed both those
configuration elements and let m2eclipse update the Eclipse project configuration; these
changes I checked into SVN. You have to understand that at this point when you let maven
build the application, you get the war name with SNAPSHOT and project version in it.
I then created a fresh workspace, imported the project from SVN fresh (this time without
the name overrides in the poms) and tried to publish again to a fresh server instance.
Result: I get the wrong deployment name (but the deployments tab still shows the correct
name)!
My line of thinking is that m2eclipse synchronizes settings to the EAR module; perhaps it
has something to do with the file
'.settings/org.eclipse.wst.common.component.prefs' in the Eclipse project of the
ear module? This file now contains this line:
<dependent-module archiveName="app-web-1.0.0-SNAPSHOT.war"
deploy-path="/" handle="module:/resource/app-web/app-web">
Now, when I add back the module filename override in the EAR pom and let m2eclipse
synchronize the changes to the ear module, after a full publish I get the correct
deployment name. The line in the settings has changed to this:
<dependent-module archiveName="app-web.war" deploy-path="/"
handle="module:/resource/app-web/app-web">
That 'archiveName' element definitely seems to be involved. The issue would be
reduced to this:
- for some reason the deployments tab shows the name of the project, not what is mentioned
in the archiveName. Yet upon publishing, the archiveName is used
- when you save the changes in the deployments tab, from that moment on the (incorrect?)
value in the deployments tab is persisted somewhere and used from that moment on
Does that make any sense?
deployments tab war module deployment location is ignored
---------------------------------------------------------
Key: JBIDE-10592
URL:
https://issues.jboss.org/browse/JBIDE-10592
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M5
Environment: Eclipse Indigo SR1
Reporter: erik van altena
Assignee: Rob Stryker
Priority: Minor
Fix For: 3.3.0.Beta1
This bug report is created as per requested in this closed issue:
https://issues.jboss.org/browse/JBIDE-10590
I have a Mavenized project (m2eclipse, JBoss Tools Maven Integration) which I publish to
a JBoss 7 runtime (standalone) by dragging it to the runtime instance. To work around the
publish directory names not matching the maven pom configuration, I use the runtime
deployment tab to override the directory names that the project modules are deployed under
in the deployments folder of the server.
(next part copy/pasted from original issue comments)
But then I run into the next oddity: the settings for the war module seem to be ignored
out of the box. The deployment tab mentions the war module as being deployed as
'app-web.war' while in fact it ends up in the deployments directory as
'app-web-1.0.0-SNAPSHOT.war', just like Maven would name it if you don't
provide a finalName. However, as soon as I tab over the deployment locations and save the
changes to the runtime configuration, upon full publish the web module gets the directory
name as it is listed in the deployments tab.
To be a little more specific: I get this behavior when I haven't made changes yet to
the war entry in the deployment tab; the tab indicates the correct name but the result
after publishing is wrong. When I then press tab to navigate to the deployment-location of
the war, I don't change anything but I hit CTRL+S to save changes, upon full publish
the name is then correct.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.jboss.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see:
http://www.atlassian.com/software/jira