5:10 p.m.
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
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
6:42 p.m.
[
https://issues.jboss.org/browse/JBIDE-10592?page=com.atlassian.jira.plugi...
]
Fred Bricon commented on JBIDE-10592:
-------------------------------------
Rob, it seems that tab ignores the archiveName of the ear component references. It should
use it by default.
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
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
7:24 p.m.
[
https://issues.jboss.org/browse/JBIDE-10592?page=com.atlassian.jira.plugi...
]
erik van altena commented on JBIDE-10592:
-----------------------------------------
I realized it might help if I say how the project was constructed. I did not create it
from scratch, I checked out an existing project from SVN and then imported the individual
modules (import -> maven -> import existing maven modules). .project and .classpath
were checked out, however the configuration (.settings) is not committed to SVN, that was
created fresh in my workspace for all modules.
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
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
2:51 p.m.
[
https://issues.jboss.org/browse/JBIDE-10592?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen updated JBIDE-10592:
----------------------------------------
Fix Version/s: 3.3.0.Beta1
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
2:51 p.m.
[
https://issues.jboss.org/browse/JBIDE-10592?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-10592:
---------------------------------------------
Is this really minor ? sounds like a bad broken thing ?
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
10:24 a.m.
[
https://issues.jboss.org/browse/JBIDE-10592?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-10592:
-------------------------------------
Hi Erik:
I'd love it if you could send me an extremely stripped down basic mavenized project I
can test this with. I'd like to fully explore the situation before taking Fred's
advice and simply using the component name, since we try to avoid component names as much
as possible (and instead use module names.)
Anyway, an example project would be very much appreciated here.
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
11:54 a.m.
[
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
3:44 p.m.
[
https://issues.jboss.org/browse/JBIDE-10592?page=com.atlassian.jira.plugi...
]
Fred Bricon commented on JBIDE-10592:
-------------------------------------
Rob, you can reproduce the issue by creating a new JavaEE Project from JBoss Central.
Once the projects are created, look at the archiveNames in
<project>-ear/.settings/org.eclipse.wst.common.component.
deploy the EAR project on AS7, the projects are deployed following the expected
archiveName property :
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="multi">
<wb-resource deploy-path="/"
source-path="/target/m2e-wtp/ear-resources"/>
<wb-resource deploy-path="/"
source-path="/src/main/application" tag="defaultRootSource"/>
<dependent-module archiveName="multi-web-0.0.1-SNAPSHOT.war"
deploy-path="/" handle="module:/resource/multi-web/multi-web">
<dependency-type>uses</dependency-type>
</dependent-module>
<dependent-module archiveName="multi-ejb-0.0.1-SNAPSHOT.jar"
deploy-path="/" handle="module:/resource/multi-ejb/multi-ejb">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{code}
Now go to you AS instance deployment tab and check the deployment locations are different
from the aforementioned archiveNames.
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
3:46 p.m.
[
https://issues.jboss.org/browse/JBIDE-10592?page=com.atlassian.jira.plugi...
]
Fred Bricon edited comment on JBIDE-10592 at 2/14/12 9:44 AM:
--------------------------------------------------------------
Rob, you can reproduce the issue by creating a new JavaEE Project from JBoss Central.
Once the projects are created, look at the archiveNames in
<project>-ear/.settings/org.eclipse.wst.common.component.
deploy the EAR project on AS7, the projects are deployed following the expected
archiveName property :
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="multi">
<wb-resource deploy-path="/"
source-path="/target/m2e-wtp/ear-resources"/>
<wb-resource deploy-path="/"
source-path="/src/main/application" tag="defaultRootSource"/>
<dependent-module archiveName="multi-web-0.0.1-SNAPSHOT.war"
deploy-path="/" handle="module:/resource/multi-web/multi-web">
<dependency-type>uses</dependency-type>
</dependent-module>
<dependent-module archiveName="multi-ejb-0.0.1-SNAPSHOT.jar"
deploy-path="/" handle="module:/resource/multi-ejb/multi-ejb">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{code}
Now go to your AS instance deployment tab and check the deployment locations are different
from the aforementioned archiveNames.
was (Author: fbricon):
Rob, you can reproduce the issue by creating a new JavaEE Project from JBoss Central.
Once the projects are created, look at the archiveNames in
<project>-ear/.settings/org.eclipse.wst.common.component.
deploy the EAR project on AS7, the projects are deployed following the expected
archiveName property :
{code:xml}
<?xml version="1.0" encoding="UTF-8"?>
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="multi">
<wb-resource deploy-path="/"
source-path="/target/m2e-wtp/ear-resources"/>
<wb-resource deploy-path="/"
source-path="/src/main/application" tag="defaultRootSource"/>
<dependent-module archiveName="multi-web-0.0.1-SNAPSHOT.war"
deploy-path="/" handle="module:/resource/multi-web/multi-web">
<dependency-type>uses</dependency-type>
</dependent-module>
<dependent-module archiveName="multi-ejb-0.0.1-SNAPSHOT.jar"
deploy-path="/" handle="module:/resource/multi-ejb/multi-ejb">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{code}
Now go to you AS instance deployment tab and check the deployment locations are different
from the aforementioned archiveNames.
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
3:50 p.m.
[
https://issues.jboss.org/browse/JBIDE-10592?page=com.atlassian.jira.plugi...
]
Fred Bricon commented on JBIDE-10592:
-------------------------------------
I might add that if you remove the <finalName> from the ear's pom.xml and run
Maven > Update project configuration, the deploy-name of your ear will be
<project>-<version> in
<project>-ear/.settings/org.eclipse.wst.common.component. And then you face
https://bugs.eclipse.org/bugs/show_bug.cgi?id=340918
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
3:54 p.m.
[
https://issues.jboss.org/browse/JBIDE-10592?page=com.atlassian.jira.plugi...
]
Fred Bricon edited comment on JBIDE-10592 at 2/14/12 9:52 AM:
--------------------------------------------------------------
I might add that, with m2e-wtp >= 0.15, if you remove the <finalName> from the
ear's pom.xml and run Maven > Update project configuration, the deploy-name of your
ear will be <project>-<version> in
<project>-ear/.settings/org.eclipse.wst.common.component. And then you face
https://bugs.eclipse.org/bugs/show_bug.cgi?id=340918
was (Author: fbricon):
I might add that if you remove the <finalName> from the ear's pom.xml and
run Maven > Update project configuration, the deploy-name of your ear will be
<project>-<version> in
<project>-ear/.settings/org.eclipse.wst.common.component. And then you face
https://bugs.eclipse.org/bugs/show_bug.cgi?id=340918
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
5:14 p.m.
[
https://issues.jboss.org/browse/JBIDE-10592?page=com.atlassian.jira.plugi...
]
erik van altena commented on JBIDE-10592:
-----------------------------------------
I would also want to raise a question of documentation based on this. If you want reliable
results using JBoss Tools in a Mavenized project, it is really necessary that you provide
a proper finalName for all Maven modules in the pom to circumvent this and other
deployment issues. In fact it is highly necessary that you have your pom configuration
clean and proper, or else m2eclipse might wrongly setup the Eclipse project facets to a
point where JBoss Tools is also influenced:
https://issues.jboss.org/browse/JBIDE-10591
Perhaps the JBoss Tools documentation should have a document on Maven usage with best
practices. For example, Jboss Tools has a Maven integration module, yet I don't see an
entry in the reference guide for it yet:
http://download.jboss.org/jbosstools/nightly-docs/
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
noon
[
https://issues.jboss.org/browse/JBIDE-10592?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-10592:
-------------------------------------
This behavior cannot change. I realize it seems broken, but, this is a problem with having
too many pieces, and there's no way for this to change without huge changes to the api
and ui.
The reason is that the deployment tab of the server editor assigns a deployment name to a
module. This name, if set, will override any other name. A Web project can have 3 or 4
different ear projects containing it. You can try this. Make 4 ear projects, make 1 web
project, add that web project to each of the ear projects.
In this way, if Ear1 says the web child should be called Web1, but Ear2 says the web
child should be called Web2, etc etc, then in the server editor, which value should
show? We cannot default to showing any one favored parent project's internal details
in this way. It seems, then we should leave it blank, or put some other default text like
{unset}, but that does not provide sufficient guidance for a user to know what they can
change and what are accepted values.
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
1:43 p.m.
[
https://issues.jboss.org/browse/JBIDE-10592?page=com.atlassian.jira.plugi...
]
erik van altena commented on JBIDE-10592:
-----------------------------------------
Before I comment, I have to retract an earlier statement I made from my original issue
description:
"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."
This is in fact not true upon retesting; likely I mistakenly thought this because I
happened to have added the bundleFileName to the ear pom in between attempts to get things
to work properly.
the server editor assigns a deployment name to a module. This name,
if set, will override any other name.
Exactly how I would expect it to work. But now
examine the actual situation I'm seeing:
Deployment tab reports: app-web.war (which is the name I want to have!)
Full publish produces: app-web-1.0.0-SNAPSHOT.war (not what the deployment tab reports but
what is in the archiveName inside the eclipse settings file)
This discrepancy contradicts what you state yourself; the deployment tab should have
overridden the name. I agree that it should work like that, but in this particular case it
does not.
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
3:58 p.m.
[
https://issues.jboss.org/browse/JBIDE-10592?page=com.atlassian.jira.plugi...
]
Rob Stryker updated JBIDE-10592:
--------------------------------
Fix Version/s: 3.3.x
(was: 3.3.0.Beta1)
Odds are this will not make any release soon, since it requires some heavy investigation
and big changes.
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.x
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
11 a.m.
[
https://issues.jboss.org/browse/JBIDE-10592?page=com.atlassian.jira.plugi...
]
Rob Stryker commented on JBIDE-10592:
-------------------------------------
While re-reading these comments, I'm quite confused. In all examples, it seems as if
you're deploying the web project inside an ear. If you're deploying inside an ear,
then the settings on the deployment tab of the server editor are irrelevent, as those
settings are ONLY applied for standalone deployments.
If you're bundling the web project inside an ear, then the settings in teh deployment
tab are completely ignopred, and only teh values in the component xml file are respected.
i would really need to hear a more clear explanation of this issue before I can begin to
work on it.
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.x
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
11 a.m.
[
https://issues.jboss.org/browse/JBIDE-10592?page=com.atlassian.jira.plugi...
]
Rob Stryker reassigned JBIDE-10592:
-----------------------------------
Assignee: Fred Bricon (was: Rob Stryker)
Hey fred, can you clear this up for me? thanks
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: Fred Bricon
Priority: Minor
Fix For: 3.3.x
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
12:04 p.m.
[
https://issues.jboss.org/browse/JBIDE-10592?page=com.atlassian.jira.plugi...
]
erik van altena commented on JBIDE-10592:
-----------------------------------------
The issue is 6 months old and quite stale. At this point I'd have to retest everything
with JBoss Tools 3.3 final (I have the idea that the deployment tab is now showing me a
different picture than what I saw all those months ago). I'll see if I can find some
time to reproduce the issue with a completely fresh project. But I must admit that since
then I've had the pleasure of doing some deployments to Tomcat 7 and the process is
far from an automatic one in a Mavenized project; it requires many manual project setting
corrections before it works properly.
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: Fred Bricon
Priority: Minor
Fix For: 3.3.x
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
2:29 p.m.
[
https://issues.jboss.org/browse/JBIDE-10592?page=com.atlassian.jira.plugi...
]
Max Rydahl Andersen commented on JBIDE-10592:
---------------------------------------------
erik - not sure how to read your last paragraph.
Are you saying:
Tomcat 7 is a pleasure to use and our JBoss server adapter is far from automatic to use on
an mavenized project
OR
Tomcat 7 was *not* a pleasure to use since opposite to JBoss server adapter it was far
from automatic to setup ?
In both cases i'm curious to know more about the issues found - if unrelated to this
specific one please open a forum thread instead, ok ?
Thanks
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: Fred Bricon
Priority: Minor
Fix For: 3.3.x
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
3:39 p.m.
[
https://issues.jboss.org/browse/JBIDE-10592?page=com.atlassian.jira.plugi...
]
erik van altena commented on JBIDE-10592:
-----------------------------------------
Whoops, I meant displeasure! This report is not my finest moment.
No the other way around - deploying to JBoss 7, when I adjust the poms to take into
account the naming issue I've tried to report here, works remarkably well. Deployment
to Tomcat 7 fails without manual intervention because the deployment assembly is incorrect
on multiple points and even though it is easily manually corrected, it becomes incorrect
again when you but change a project setting which is not that unlikely in a Mavenized
project.
What I really want to do is upgrade to Eclipse 4 with JBoss Tools 3.3 final and see what
happens then in all cases, but yeah... need to find the time.
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: Fred Bricon
Priority: Minor
Fix For: 3.3.x
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
11:40 a.m.
[
https://issues.jboss.org/browse/JBIDE-10592?page=com.atlassian.jira.plugi...
]
Fred Bricon reassigned JBIDE-10592:
-----------------------------------
Assignee: Rob Stryker (was: Fred Bricon)
A webapp inside an ear should not be displayed in the deployment tab, as its deployment
can not be controlled by the user at that point, only by the ear config.
Worse, if the same webapp is deployed twice in different ears, under different locations,
it would only appear as one module in the deployment tab and there would be no way to
display its proper location.
Rob, remove the goddamn embedded modules :-)
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.x
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
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:03 a.m.
[
https://issues.jboss.org/browse/JBIDE-10592?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-10592.
---------------------------------
Fix Version/s: 4.0.0.CR1
(was: 3.3.x)
Resolution: Done
committed to trunk. I added a new selection in the pulldown called DEPLOYABLE. This
filters out child modules, and this choice is now the default. ALL remains in place, in
case users who understand what they're doing wish to make changes there.
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: 4.0.0.CR1
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
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:07 p.m.
[
https://issues.jboss.org/browse/JBIDE-10592?page=com.atlassian.jira.plugi...
]
Rob Stryker resolved JBIDE-10592.
---------------------------------
Resolution: Done
Hey Martin:
I believe you will see it now. I didn't change the commit at all, but I definitely see
4 elements: All, Deployable, Deployed, By Module Name.
Re-open if you still don't see it.
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: 4.0.0.CR1
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
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:46 p.m.
[
https://issues.jboss.org/browse/JBIDE-10592?page=com.atlassian.jira.plugi...
]
Martin Malina updated JBIDE-10592:
----------------------------------
Fix Version/s: 4.0.0.Beta2
(was: 4.0.0.CR1)
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: 4.0.0.Beta2
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
For more information on JIRA, see: http://www.atlassian.com/software/jira
12:46 p.m.
[
https://issues.jboss.org/browse/JBIDE-10592?page=com.atlassian.jira.plugi...
]
Martin Malina commented on JBIDE-10592:
---------------------------------------
ok, I can see it now. Will verify again in Beta2 (it should be there, right?).
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: 4.0.0.Beta2
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
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:50 p.m.
[
https://issues.jboss.org/browse/JBIDE-10592?page=com.atlassian.jira.plugi...
]
Martin Malina closed JBIDE-10592.
---------------------------------
Verified as fixed in JBT 4.0.0.Beta2a B74. Now Deployable is default and it does not show
child modules.
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: 4.0.0.Beta2
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
For more information on JIRA, see: http://www.atlassian.com/software/jira
4242
days inactive
4557
days old
jbosstools-issues@lists.jboss.org
25 comments
8 participants
participants (8)
-
erik van altena (Commented) (JIRA) -
erik van altena (Created) (JIRA)
-
erik van altena (JIRA)
-
Fred Bricon (Commented) (JIRA)
-
Fred Bricon (JIRA)
-
Martin Malina (JIRA)
-
Max Rydahl Andersen (JIRA)
-
Rob Stryker (JIRA)