[JBoss JIRA] Created: (JBIDE-9496) [regression] - Exported files don't honor the module assembly settings
10:06 a.m.
[regression] - Exported files don't honor the module assembly settings
----------------------------------------------------------------------
Key: JBIDE-9496
URL: https://issues.jboss.org/browse/JBIDE-9496
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Environment: Vista, eclipse 3.5.1, JBT 3.1.CR1
Reporter: Fred Bricon
Assignee: Rob Stryker
I'm investigating ways to implement SAR support in m2eclipse (for selfish motivations
I agree). See https://issues.sonatype.org/browse/MNGECLIPSE-1984.
A SAR project would need to export dependencies in a lib folder, inside the archive.
During my investigation, I tried to use the JBT 3.1.CR1 module assembly page, which would,
from my understanding, allow me to reach the desired effect.
So I've created sample maven-less projects :
-sarproject : has a dependency to JUNIT_HOME\junit.jar in the module assembly page. The
resulting org.eclipse.wst.common.component contains :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="sarproject">
<wb-resource deploy-path="/" source-path="/src"/>
<dependent-module archiveName="junit.jar" deploy-path="/"
handle="module:/classpath/var/JUNIT_HOME/junit.jar">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
-earproject : needed so sarproject can be a Module project (which totally sucks). I've
manually tweaked org.eclipse.wst.common.component so sarproject will have the .sar
extension when deployed. Here is the end result :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="earproject">
<wb-resource deploy-path="/"
source-path="/EarContent"/>
<dependent-module archiveName="sarproject.sar"
deploy-path="/" handle="module:/resource/sarproject/sarproject">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
Now, when exporting earproject.ear, there's no junit.jar to be found in sarproject.sar
(not expected) nor in the ear (expected).
When using export module on sarproject, the resulting file doesn't contain junit.jar
either.
This looks like a bug I've opened at eclipse's bugzilla for Connector projects :
https://bugs.eclipse.org/bugs/show_bug.cgi?id=298735
The module assembly page looks very promising in theory, as it would allow support for any
kind of archives (sar, har ...)
but from what I understand it's only usable for ear and war projects.
This bug should probably be opened at eclipse.org or is totally a duplicate of #298735
(you tell me),
but I think the module assembly page should not be visible on unsupported projects.
regards,
Fred Bricon
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:42 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-9496) [regression] - Exported files don't honor the module assembly settings
[
https://issues.jboss.org/browse/JBIDE-9496?page=com.atlassian.jira.plugin...
]
Fred Bricon updated JBIDE-9496:
-------------------------------
Description:
I'm investigating ways to implement SAR support for maven projects (JBIDE-9127).
So far I've been adding the Utility Facet to such projects, so they can be deployed in
EARs.
A SAR project can embed dependencies in a lib folder, inside the archive.
A previous upstream bug prevented this behavior, but it has been fixed since : JBIDE-5691
Unfortunately, it seems a regression has crept in, because using the same projects
attached in JBIDE-5691, the embedded jar (junit.jar) is no longer deployed on any JBoss
AS.
In this use case, I have 2 sample maven-less projects :
-sarproject : has a dependency to JUNIT_HOME\junit.jar in the module assembly page. The
resulting org.eclipse.wst.common.component contains :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="sarproject">
<wb-resource deploy-path="/" source-path="/src"/>
<dependent-module archiveName="junit.jar" deploy-path="/"
handle="module:/classpath/var/JUNIT_HOME/junit.jar">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
-earproject : needed so sarproject can be a Module project. I've manually tweaked
org.eclipse.wst.common.component so sarproject will have the .sar extension when deployed.
Here is the end result :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="earproject">
<wb-resource deploy-path="/"
source-path="/EarContent"/>
<dependent-module archiveName="sarproject.sar"
deploy-path="/" handle="module:/resource/sarproject/sarproject">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
was:
I'm investigating ways to implement SAR support in m2eclipse (for selfish motivations
I agree). See https://issues.sonatype.org/browse/MNGECLIPSE-1984.
A SAR project would need to export dependencies in a lib folder, inside the archive.
During my investigation, I tried to use the JBT 3.1.CR1 module assembly page, which would,
from my understanding, allow me to reach the desired effect.
So I've created sample maven-less projects :
-sarproject : has a dependency to JUNIT_HOME\junit.jar in the module assembly page. The
resulting org.eclipse.wst.common.component contains :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="sarproject">
<wb-resource deploy-path="/" source-path="/src"/>
<dependent-module archiveName="junit.jar" deploy-path="/"
handle="module:/classpath/var/JUNIT_HOME/junit.jar">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
-earproject : needed so sarproject can be a Module project (which totally sucks). I've
manually tweaked org.eclipse.wst.common.component so sarproject will have the .sar
extension when deployed. Here is the end result :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="earproject">
<wb-resource deploy-path="/"
source-path="/EarContent"/>
<dependent-module archiveName="sarproject.sar"
deploy-path="/" handle="module:/resource/sarproject/sarproject">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
Now, when exporting earproject.ear, there's no junit.jar to be found in sarproject.sar
(not expected) nor in the ear (expected).
When using export module on sarproject, the resulting file doesn't contain junit.jar
either.
This looks like a bug I've opened at eclipse's bugzilla for Connector projects :
https://bugs.eclipse.org/bugs/show_bug.cgi?id=298735
The module assembly page looks very promising in theory, as it would allow support for any
kind of archives (sar, har ...)
but from what I understand it's only usable for ear and war projects.
This bug should probably be opened at eclipse.org or is totally a duplicate of #298735
(you tell me),
but I think the module assembly page should not be visible on unsupported projects.
regards,
Fred Bricon
Environment: Ubuntu 11.04, eclipse 3.7, JBT 3.3.0 M3 (was: Vista, eclipse 3.5.1, JBT
3.1.CR1)
[regression] - Exported files don't honor the module assembly
settings
----------------------------------------------------------------------
Key: JBIDE-9496
URL: https://issues.jboss.org/browse/JBIDE-9496
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Environment: Ubuntu 11.04, eclipse 3.7, JBT 3.3.0 M3
Reporter: Fred Bricon
Assignee: Rob Stryker
I'm investigating ways to implement SAR support for maven projects (JBIDE-9127).
So far I've been adding the Utility Facet to such projects, so they can be deployed
in EARs.
A SAR project can embed dependencies in a lib folder, inside the archive.
A previous upstream bug prevented this behavior, but it has been fixed since : JBIDE-5691
Unfortunately, it seems a regression has crept in, because using the same projects
attached in JBIDE-5691, the embedded jar (junit.jar) is no longer deployed on any JBoss
AS.
In this use case, I have 2 sample maven-less projects :
-sarproject : has a dependency to JUNIT_HOME\junit.jar in the module assembly page. The
resulting org.eclipse.wst.common.component contains :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="sarproject">
<wb-resource deploy-path="/" source-path="/src"/>
<dependent-module archiveName="junit.jar" deploy-path="/"
handle="module:/classpath/var/JUNIT_HOME/junit.jar">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
-earproject : needed so sarproject can be a Module project. I've manually tweaked
org.eclipse.wst.common.component so sarproject will have the .sar extension when deployed.
Here is the end result :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="earproject">
<wb-resource deploy-path="/"
source-path="/EarContent"/>
<dependent-module archiveName="sarproject.sar"
deploy-path="/" handle="module:/resource/sarproject/sarproject">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:45 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-9496) [regression] - Exported files don't honor the module assembly settings
[
https://issues.jboss.org/browse/JBIDE-9496?page=com.atlassian.jira.plugin...
]
Fred Bricon updated JBIDE-9496:
-------------------------------
Attachment: JBIDE_9496_projects.zip
[regression] - Exported files don't honor the module assembly
settings
----------------------------------------------------------------------
Key: JBIDE-9496
URL: https://issues.jboss.org/browse/JBIDE-9496
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Environment: Ubuntu 11.04, eclipse 3.7, JBT 3.3.0 M3
Reporter: Fred Bricon
Assignee: Rob Stryker
Attachments: JBIDE_9496_projects.zip
I'm investigating ways to implement SAR support for maven projects (JBIDE-9127).
So far I've been adding the Utility Facet to such projects, so they can be deployed
in EARs.
A SAR project can embed dependencies in a lib folder, inside the archive.
A previous upstream bug prevented this behavior, but it has been fixed since : JBIDE-5691
Unfortunately, it seems a regression has crept in, because using the same projects
attached in JBIDE-5691, the embedded jar (junit.jar) is no longer deployed on any JBoss
AS.
In this use case, I have 2 sample maven-less projects :
-sarproject : has a dependency to JUNIT_HOME\junit.jar in the module assembly page. The
resulting org.eclipse.wst.common.component contains :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="sarproject">
<wb-resource deploy-path="/" source-path="/src"/>
<dependent-module archiveName="junit.jar" deploy-path="/"
handle="module:/classpath/var/JUNIT_HOME/junit.jar">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
-earproject : needed so sarproject can be a Module project. I've manually tweaked
org.eclipse.wst.common.component so sarproject will have the .sar extension when deployed.
Here is the end result :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="earproject">
<wb-resource deploy-path="/"
source-path="/EarContent"/>
<dependent-module archiveName="sarproject.sar"
deploy-path="/" handle="module:/resource/sarproject/sarproject">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:49 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-9496) [regression] - Exported files don't honor the module assembly settings
[
https://issues.jboss.org/browse/JBIDE-9496?page=com.atlassian.jira.plugin...
]
Fred Bricon updated JBIDE-9496:
-------------------------------
Fix Version/s: 3.3.0.M3
Description:
I'm investigating ways to implement SAR support for maven projects (JBIDE-9127).
So far I've been adding the Utility Facet to such projects, so they can be deployed in
EARs.
A SAR project can embed dependencies in a lib folder, inside the archive.
A previous upstream bug prevented this behavior, but it has been fixed since : JBIDE-5691
Unfortunately, it seems a regression has crept in, because using the same projects
attached in JBIDE-5691, the embedded jar (junit.jar) is no longer present at the root of
sarproject.sar, when earproject is deployed on (any) JBoss AS.
In this use case, I have 2 sample maven-less projects :
-sarproject : has a dependency to JUNIT_HOME\junit.jar in the module assembly page. The
resulting org.eclipse.wst.common.component contains :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="sarproject">
<wb-resource deploy-path="/" source-path="/src"/>
<dependent-module archiveName="junit.jar" deploy-path="/"
handle="module:/classpath/var/JUNIT_HOME/junit.jar">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
-earproject : needed so sarproject can be a Module project. I've manually tweaked
org.eclipse.wst.common.component so sarproject will have the .sar extension when deployed.
Here is the end result :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="earproject">
<wb-resource deploy-path="/"
source-path="/EarContent"/>
<dependent-module archiveName="sarproject.sar"
deploy-path="/" handle="module:/resource/sarproject/sarproject">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
was:
I'm investigating ways to implement SAR support for maven projects (JBIDE-9127).
So far I've been adding the Utility Facet to such projects, so they can be deployed in
EARs.
A SAR project can embed dependencies in a lib folder, inside the archive.
A previous upstream bug prevented this behavior, but it has been fixed since : JBIDE-5691
Unfortunately, it seems a regression has crept in, because using the same projects
attached in JBIDE-5691, the embedded jar (junit.jar) is no longer deployed on any JBoss
AS.
In this use case, I have 2 sample maven-less projects :
-sarproject : has a dependency to JUNIT_HOME\junit.jar in the module assembly page. The
resulting org.eclipse.wst.common.component contains :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="sarproject">
<wb-resource deploy-path="/" source-path="/src"/>
<dependent-module archiveName="junit.jar" deploy-path="/"
handle="module:/classpath/var/JUNIT_HOME/junit.jar">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
-earproject : needed so sarproject can be a Module project. I've manually tweaked
org.eclipse.wst.common.component so sarproject will have the .sar extension when deployed.
Here is the end result :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="earproject">
<wb-resource deploy-path="/"
source-path="/EarContent"/>
<dependent-module archiveName="sarproject.sar"
deploy-path="/" handle="module:/resource/sarproject/sarproject">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
Labels: archive deployment sar (was: )
Affects Version/s: 3.3.0.M3
[regression] - Exported files don't honor the module assembly
settings
----------------------------------------------------------------------
Key: JBIDE-9496
URL: https://issues.jboss.org/browse/JBIDE-9496
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.3.0.M3
Environment: Ubuntu 11.04, eclipse 3.7, JBT 3.3.0 M3
Reporter: Fred Bricon
Assignee: Rob Stryker
Labels: archive, deployment, sar
Fix For: 3.3.0.M3
Attachments: JBIDE_9496_projects.zip
I'm investigating ways to implement SAR support for maven projects (JBIDE-9127).
So far I've been adding the Utility Facet to such projects, so they can be deployed
in EARs.
A SAR project can embed dependencies in a lib folder, inside the archive.
A previous upstream bug prevented this behavior, but it has been fixed since : JBIDE-5691
Unfortunately, it seems a regression has crept in, because using the same projects
attached in JBIDE-5691, the embedded jar (junit.jar) is no longer present at the root of
sarproject.sar, when earproject is deployed on (any) JBoss AS.
In this use case, I have 2 sample maven-less projects :
-sarproject : has a dependency to JUNIT_HOME\junit.jar in the module assembly page. The
resulting org.eclipse.wst.common.component contains :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="sarproject">
<wb-resource deploy-path="/" source-path="/src"/>
<dependent-module archiveName="junit.jar" deploy-path="/"
handle="module:/classpath/var/JUNIT_HOME/junit.jar">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
-earproject : needed so sarproject can be a Module project. I've manually tweaked
org.eclipse.wst.common.component so sarproject will have the .sar extension when deployed.
Here is the end result :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="earproject">
<wb-resource deploy-path="/"
source-path="/EarContent"/>
<dependent-module archiveName="sarproject.sar"
deploy-path="/" handle="module:/resource/sarproject/sarproject">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:31 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9496) [regression] - Exported files don't honor the module assembly settings
[
https://issues.jboss.org/browse/JBIDE-9496?page=com.atlassian.jira.plugin...
]
Rob Stryker commented on JBIDE-9496:
------------------------------------
Typically when we clone a bug, we indicate WHY we cloned it, by adding a comment, such as
"seems to have reversed" or what's different from the last issue.
[regression] - Exported files don't honor the module assembly
settings
----------------------------------------------------------------------
Key: JBIDE-9496
URL: https://issues.jboss.org/browse/JBIDE-9496
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.3.0.M3
Environment: Ubuntu 11.04, eclipse 3.7, JBT 3.3.0 M3
Reporter: Fred Bricon
Assignee: Rob Stryker
Labels: archive, deployment, sar
Fix For: 3.3.0.M3
Attachments: JBIDE_9496_projects.zip
I'm investigating ways to implement SAR support for maven projects (JBIDE-9127).
So far I've been adding the Utility Facet to such projects, so they can be deployed
in EARs.
A SAR project can embed dependencies in a lib folder, inside the archive.
A previous upstream bug prevented this behavior, but it has been fixed since : JBIDE-5691
Unfortunately, it seems a regression has crept in, because using the same projects
attached in JBIDE-5691, the embedded jar (junit.jar) is no longer present at the root of
sarproject.sar, when earproject is deployed on (any) JBoss AS.
In this use case, I have 2 sample maven-less projects :
-sarproject : has a dependency to JUNIT_HOME\junit.jar in the module assembly page. The
resulting org.eclipse.wst.common.component contains :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="sarproject">
<wb-resource deploy-path="/" source-path="/src"/>
<dependent-module archiveName="junit.jar" deploy-path="/"
handle="module:/classpath/var/JUNIT_HOME/junit.jar">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
-earproject : needed so sarproject can be a Module project. I've manually tweaked
org.eclipse.wst.common.component so sarproject will have the .sar extension when deployed.
Here is the end result :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="earproject">
<wb-resource deploy-path="/"
source-path="/EarContent"/>
<dependent-module archiveName="sarproject.sar"
deploy-path="/" handle="module:/resource/sarproject/sarproject">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:57 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9496) [regression] - Exported files don't honor the module assembly settings
[
https://issues.jboss.org/browse/JBIDE-9496?page=com.atlassian.jira.plugin...
]
Rob Stryker commented on JBIDE-9496:
------------------------------------
The utility project is being identified as a "single root" project. There seems
to be a bug in the single root handler (an efficient handler for specific cases) where it
ignores references that are not child modules.
Workaround is to make your project NOT single root. Steps to do that include:
1) Adding a new folder to your project called "garbage" or some other
irrelevant name
2) Adding a folder mapping from "garbage" to "/" via the module
assembly page.
At this point your project is no longer single root and this bug is worked around.
[regression] - Exported files don't honor the module assembly
settings
----------------------------------------------------------------------
Key: JBIDE-9496
URL: https://issues.jboss.org/browse/JBIDE-9496
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.3.0.M3
Environment: Ubuntu 11.04, eclipse 3.7, JBT 3.3.0 M3
Reporter: Fred Bricon
Assignee: Rob Stryker
Labels: archive, deployment, sar
Fix For: 3.3.0.M3
Attachments: JBIDE_9496_projects.zip
I'm investigating ways to implement SAR support for maven projects (JBIDE-9127).
So far I've been adding the Utility Facet to such projects, so they can be deployed
in EARs.
A SAR project can embed dependencies in a lib folder, inside the archive.
A previous upstream bug prevented this behavior, but it has been fixed since : JBIDE-5691
Unfortunately, it seems a regression has crept in, because using the same projects
attached in JBIDE-5691, the embedded jar (junit.jar) is no longer present at the root of
sarproject.sar, when earproject is deployed on (any) JBoss AS.
In this use case, I have 2 sample maven-less projects :
-sarproject : has a dependency to JUNIT_HOME\junit.jar in the module assembly page. The
resulting org.eclipse.wst.common.component contains :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="sarproject">
<wb-resource deploy-path="/" source-path="/src"/>
<dependent-module archiveName="junit.jar" deploy-path="/"
handle="module:/classpath/var/JUNIT_HOME/junit.jar">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
-earproject : needed so sarproject can be a Module project. I've manually tweaked
org.eclipse.wst.common.component so sarproject will have the .sar extension when deployed.
Here is the end result :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="earproject">
<wb-resource deploy-path="/"
source-path="/EarContent"/>
<dependent-module archiveName="sarproject.sar"
deploy-path="/" handle="module:/resource/sarproject/sarproject">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:59 a.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBIDE-9496) [regression] - Exported files don't honor the module assembly settings
[
https://issues.jboss.org/browse/JBIDE-9496?page=com.atlassian.jira.plugin...
]
Rob Stryker edited comment on JBIDE-9496 at 8/10/11 2:57 AM:
-------------------------------------------------------------
[edit] this comment was on the wrong bug ;) ... or something.
was (Author: rob.stryker):
Typically when we clone a bug, we indicate WHY we cloned it, by adding a comment, such
as "seems to have reversed" or what's different from the last issue.
[regression] - Exported files don't honor the module assembly
settings
----------------------------------------------------------------------
Key: JBIDE-9496
URL: https://issues.jboss.org/browse/JBIDE-9496
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.3.0.M3
Environment: Ubuntu 11.04, eclipse 3.7, JBT 3.3.0 M3
Reporter: Fred Bricon
Assignee: Rob Stryker
Labels: archive, deployment, sar
Fix For: 3.3.0.M3
Attachments: JBIDE_9496_projects.zip
I'm investigating ways to implement SAR support for maven projects (JBIDE-9127).
So far I've been adding the Utility Facet to such projects, so they can be deployed
in EARs.
A SAR project can embed dependencies in a lib folder, inside the archive.
A previous upstream bug prevented this behavior, but it has been fixed since : JBIDE-5691
Unfortunately, it seems a regression has crept in, because using the same projects
attached in JBIDE-5691, the embedded jar (junit.jar) is no longer present at the root of
sarproject.sar, when earproject is deployed on (any) JBoss AS.
In this use case, I have 2 sample maven-less projects :
-sarproject : has a dependency to JUNIT_HOME\junit.jar in the module assembly page. The
resulting org.eclipse.wst.common.component contains :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="sarproject">
<wb-resource deploy-path="/" source-path="/src"/>
<dependent-module archiveName="junit.jar" deploy-path="/"
handle="module:/classpath/var/JUNIT_HOME/junit.jar">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
-earproject : needed so sarproject can be a Module project. I've manually tweaked
org.eclipse.wst.common.component so sarproject will have the .sar extension when deployed.
Here is the end result :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="earproject">
<wb-resource deploy-path="/"
source-path="/EarContent"/>
<dependent-module archiveName="sarproject.sar"
deploy-path="/" handle="module:/resource/sarproject/sarproject">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:30 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9496) [regression] - Exported files don't honor the module assembly settings
[
https://issues.jboss.org/browse/JBIDE-9496?page=com.atlassian.jira.plugin...
]
Fred Bricon commented on JBIDE-9496:
------------------------------------
Actually, I stumbled upon this bug using a maven project initially, which already maps 2
source folders to / :
{noformat}
<?xml version="1.0" encoding="UTF-8"?>
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="sar-0.0.1-SNAPSHOT">
<wb-resource deploy-path="/"
source-path="/src/main/java"/>
<wb-resource deploy-path="/"
source-path="/src/main/resources"/>
<dependent-module deploy-path="/lib"
handle="module:/classpath/var/M2_REPO/commons-lang/commons-lang/2.5/commons-lang-2.5.jar">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
[regression] - Exported files don't honor the module assembly
settings
----------------------------------------------------------------------
Key: JBIDE-9496
URL: https://issues.jboss.org/browse/JBIDE-9496
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.3.0.M3
Environment: Ubuntu 11.04, eclipse 3.7, JBT 3.3.0 M3
Reporter: Fred Bricon
Assignee: Rob Stryker
Labels: archive, deployment, sar
Fix For: 3.3.0.M3
Attachments: JBIDE_9496_projects.zip
I'm investigating ways to implement SAR support for maven projects (JBIDE-9127).
So far I've been adding the Utility Facet to such projects, so they can be deployed
in EARs.
A SAR project can embed dependencies in a lib folder, inside the archive.
A previous upstream bug prevented this behavior, but it has been fixed since : JBIDE-5691
Unfortunately, it seems a regression has crept in, because using the same projects
attached in JBIDE-5691, the embedded jar (junit.jar) is no longer present at the root of
sarproject.sar, when earproject is deployed on (any) JBoss AS.
In this use case, I have 2 sample maven-less projects :
-sarproject : has a dependency to JUNIT_HOME\junit.jar in the module assembly page. The
resulting org.eclipse.wst.common.component contains :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="sarproject">
<wb-resource deploy-path="/" source-path="/src"/>
<dependent-module archiveName="junit.jar" deploy-path="/"
handle="module:/classpath/var/JUNIT_HOME/junit.jar">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
-earproject : needed so sarproject can be a Module project. I've manually tweaked
org.eclipse.wst.common.component so sarproject will have the .sar extension when deployed.
Here is the end result :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="earproject">
<wb-resource deploy-path="/"
source-path="/EarContent"/>
<dependent-module archiveName="sarproject.sar"
deploy-path="/" handle="module:/resource/sarproject/sarproject">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
2:55 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9496) [regression] - Exported files don't honor the module assembly settings
[
https://issues.jboss.org/browse/JBIDE-9496?page=com.atlassian.jira.plugin...
]
Fred Bricon commented on JBIDE-9496:
------------------------------------
OK, so the 2 folders above use the same root, so your workaround wouldn't work.
Adding another folder to the root of the project makes the references deploy to /lib
So, is it a JBT or an upstream issue?
[regression] - Exported files don't honor the module assembly
settings
----------------------------------------------------------------------
Key: JBIDE-9496
URL: https://issues.jboss.org/browse/JBIDE-9496
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.3.0.M3
Environment: Ubuntu 11.04, eclipse 3.7, JBT 3.3.0 M3
Reporter: Fred Bricon
Assignee: Rob Stryker
Labels: archive, deployment, sar
Fix For: 3.3.0.M3
Attachments: JBIDE_9496_projects.zip
I'm investigating ways to implement SAR support for maven projects (JBIDE-9127).
So far I've been adding the Utility Facet to such projects, so they can be deployed
in EARs.
A SAR project can embed dependencies in a lib folder, inside the archive.
A previous upstream bug prevented this behavior, but it has been fixed since : JBIDE-5691
Unfortunately, it seems a regression has crept in, because using the same projects
attached in JBIDE-5691, the embedded jar (junit.jar) is no longer present at the root of
sarproject.sar, when earproject is deployed on (any) JBoss AS.
In this use case, I have 2 sample maven-less projects :
-sarproject : has a dependency to JUNIT_HOME\junit.jar in the module assembly page. The
resulting org.eclipse.wst.common.component contains :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="sarproject">
<wb-resource deploy-path="/" source-path="/src"/>
<dependent-module archiveName="junit.jar" deploy-path="/"
handle="module:/classpath/var/JUNIT_HOME/junit.jar">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
-earproject : needed so sarproject can be a Module project. I've manually tweaked
org.eclipse.wst.common.component so sarproject will have the .sar extension when deployed.
Here is the end result :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="earproject">
<wb-resource deploy-path="/"
source-path="/EarContent"/>
<dependent-module archiveName="sarproject.sar"
deploy-path="/" handle="module:/resource/sarproject/sarproject">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:34 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9496) [regression] - Exported files don't honor the module assembly settings
[
https://issues.jboss.org/browse/JBIDE-9496?page=com.atlassian.jira.plugin...
]
Rob Stryker commented on JBIDE-9496:
------------------------------------
seems to be a number of them. SingleRoot is ignoring the jar, and somehow magically, a
"lib" appeared. .....
[regression] - Exported files don't honor the module assembly
settings
----------------------------------------------------------------------
Key: JBIDE-9496
URL: https://issues.jboss.org/browse/JBIDE-9496
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.3.0.M3
Environment: Ubuntu 11.04, eclipse 3.7, JBT 3.3.0 M3
Reporter: Fred Bricon
Assignee: Rob Stryker
Labels: archive, deployment, sar
Fix For: 3.3.0.M3
Attachments: JBIDE_9496_projects.zip
I'm investigating ways to implement SAR support for maven projects (JBIDE-9127).
So far I've been adding the Utility Facet to such projects, so they can be deployed
in EARs.
A SAR project can embed dependencies in a lib folder, inside the archive.
A previous upstream bug prevented this behavior, but it has been fixed since : JBIDE-5691
Unfortunately, it seems a regression has crept in, because using the same projects
attached in JBIDE-5691, the embedded jar (junit.jar) is no longer present at the root of
sarproject.sar, when earproject is deployed on (any) JBoss AS.
In this use case, I have 2 sample maven-less projects :
-sarproject : has a dependency to JUNIT_HOME\junit.jar in the module assembly page. The
resulting org.eclipse.wst.common.component contains :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="sarproject">
<wb-resource deploy-path="/" source-path="/src"/>
<dependent-module archiveName="junit.jar" deploy-path="/"
handle="module:/classpath/var/JUNIT_HOME/junit.jar">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
-earproject : needed so sarproject can be a Module project. I've manually tweaked
org.eclipse.wst.common.component so sarproject will have the .sar extension when deployed.
Here is the end result :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="earproject">
<wb-resource deploy-path="/"
source-path="/EarContent"/>
<dependent-module archiveName="sarproject.sar"
deploy-path="/" handle="module:/resource/sarproject/sarproject">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
4:34 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9496) [regression] - Exported files don't honor the module assembly settings
[
https://issues.jboss.org/browse/JBIDE-9496?page=com.atlassian.jira.plugin...
]
Rob Stryker commented on JBIDE-9496:
------------------------------------
Link to https://bugs.eclipse.org/bugs/show_bug.cgi?id=354469
[regression] - Exported files don't honor the module assembly
settings
----------------------------------------------------------------------
Key: JBIDE-9496
URL: https://issues.jboss.org/browse/JBIDE-9496
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS
Affects Versions: 3.3.0.M3
Environment: Ubuntu 11.04, eclipse 3.7, JBT 3.3.0 M3
Reporter: Fred Bricon
Assignee: Rob Stryker
Labels: archive, deployment, sar
Fix For: 3.3.0.M3
Attachments: JBIDE_9496_projects.zip
I'm investigating ways to implement SAR support for maven projects (JBIDE-9127).
So far I've been adding the Utility Facet to such projects, so they can be deployed
in EARs.
A SAR project can embed dependencies in a lib folder, inside the archive.
A previous upstream bug prevented this behavior, but it has been fixed since : JBIDE-5691
Unfortunately, it seems a regression has crept in, because using the same projects
attached in JBIDE-5691, the embedded jar (junit.jar) is no longer present at the root of
sarproject.sar, when earproject is deployed on (any) JBoss AS.
In this use case, I have 2 sample maven-less projects :
-sarproject : has a dependency to JUNIT_HOME\junit.jar in the module assembly page. The
resulting org.eclipse.wst.common.component contains :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="sarproject">
<wb-resource deploy-path="/" source-path="/src"/>
<dependent-module archiveName="junit.jar" deploy-path="/"
handle="module:/classpath/var/JUNIT_HOME/junit.jar">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
-earproject : needed so sarproject can be a Module project. I've manually tweaked
org.eclipse.wst.common.component so sarproject will have the .sar extension when deployed.
Here is the end result :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="earproject">
<wb-resource deploy-path="/"
source-path="/EarContent"/>
<dependent-module archiveName="sarproject.sar"
deploy-path="/" handle="module:/resource/sarproject/sarproject">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:02 a.m.
New subject: [JBoss JIRA] Updated: (JBIDE-9496) [regression] - Exported files don't honor the module assembly settings
[
https://issues.jboss.org/browse/JBIDE-9496?page=com.atlassian.jira.plugin...
]
Rob Stryker updated JBIDE-9496:
-------------------------------
Fix Version/s: 3.3.0.M4
(was: 3.3.0.M3)
[regression] - Exported files don't honor the module assembly
settings
----------------------------------------------------------------------
Key: JBIDE-9496
URL: https://issues.jboss.org/browse/JBIDE-9496
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M3
Environment: Ubuntu 11.04, eclipse 3.7, JBT 3.3.0 M3
Reporter: Fred Bricon
Assignee: Rob Stryker
Labels: archive, deployment, sar
Fix For: 3.3.0.M4
Attachments: JBIDE_9496_projects.zip
I'm investigating ways to implement SAR support for maven projects (JBIDE-9127).
So far I've been adding the Utility Facet to such projects, so they can be deployed
in EARs.
A SAR project can embed dependencies in a lib folder, inside the archive.
A previous upstream bug prevented this behavior, but it has been fixed since : JBIDE-5691
Unfortunately, it seems a regression has crept in, because using the same projects
attached in JBIDE-5691, the embedded jar (junit.jar) is no longer present at the root of
sarproject.sar, when earproject is deployed on (any) JBoss AS.
In this use case, I have 2 sample maven-less projects :
-sarproject : has a dependency to JUNIT_HOME\junit.jar in the module assembly page. The
resulting org.eclipse.wst.common.component contains :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="sarproject">
<wb-resource deploy-path="/" source-path="/src"/>
<dependent-module archiveName="junit.jar" deploy-path="/"
handle="module:/classpath/var/JUNIT_HOME/junit.jar">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
-earproject : needed so sarproject can be a Module project. I've manually tweaked
org.eclipse.wst.common.component so sarproject will have the .sar extension when deployed.
Here is the end result :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="earproject">
<wb-resource deploy-path="/"
source-path="/EarContent"/>
<dependent-module archiveName="sarproject.sar"
deploy-path="/" handle="module:/resource/sarproject/sarproject">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
3:11 a.m.
New subject: [JBoss JIRA] (JBIDE-9496) [regression] - Exported files don't honor the module assembly settings
[
https://issues.jboss.org/browse/JBIDE-9496?page=com.atlassian.jira.plugin...
]
Rob Stryker updated JBIDE-9496:
-------------------------------
Fix Version/s: 3.3.0.Final
(was: 3.3.0.M4)
Since this is an upstream bug, targeting to final
[regression] - Exported files don't honor the module assembly
settings
----------------------------------------------------------------------
Key: JBIDE-9496
URL: https://issues.jboss.org/browse/JBIDE-9496
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M3
Environment: Ubuntu 11.04, eclipse 3.7, JBT 3.3.0 M3
Reporter: Fred Bricon
Assignee: Rob Stryker
Labels: archive, deployment, sar
Fix For: 3.3.0.Final
Attachments: JBIDE_9496_projects.zip
I'm investigating ways to implement SAR support for maven projects (JBIDE-9127).
So far I've been adding the Utility Facet to such projects, so they can be deployed
in EARs.
A SAR project can embed dependencies in a lib folder, inside the archive.
A previous upstream bug prevented this behavior, but it has been fixed since : JBIDE-5691
Unfortunately, it seems a regression has crept in, because using the same projects
attached in JBIDE-5691, the embedded jar (junit.jar) is no longer present at the root of
sarproject.sar, when earproject is deployed on (any) JBoss AS.
In this use case, I have 2 sample maven-less projects :
-sarproject : has a dependency to JUNIT_HOME\junit.jar in the module assembly page. The
resulting org.eclipse.wst.common.component contains :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="sarproject">
<wb-resource deploy-path="/" source-path="/src"/>
<dependent-module archiveName="junit.jar" deploy-path="/"
handle="module:/classpath/var/JUNIT_HOME/junit.jar">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
-earproject : needed so sarproject can be a Module project. I've manually tweaked
org.eclipse.wst.common.component so sarproject will have the .sar extension when deployed.
Here is the end result :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="earproject">
<wb-resource deploy-path="/"
source-path="/EarContent"/>
<dependent-module archiveName="sarproject.sar"
deploy-path="/" handle="module:/resource/sarproject/sarproject">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
--
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
9:11 a.m.
New subject: [JBoss JIRA] (JBIDE-9496) [regression] - Exported files don't honor the module assembly settings
[
https://issues.jboss.org/browse/JBIDE-9496?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen updated JBIDE-9496:
---------------------------------------
Fix Version/s: 3.3.0.Beta1
(was: 3.3.0.Final)
[regression] - Exported files don't honor the module assembly
settings
----------------------------------------------------------------------
Key: JBIDE-9496
URL: https://issues.jboss.org/browse/JBIDE-9496
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers
Affects Versions: 3.3.0.M3
Environment: Ubuntu 11.04, eclipse 3.7, JBT 3.3.0 M3
Reporter: Fred Bricon
Assignee: Rob Stryker
Labels: archive, deployment, sar
Fix For: 3.3.0.Beta1
Attachments: JBIDE_9496_projects.zip
I'm investigating ways to implement SAR support for maven projects (JBIDE-9127).
So far I've been adding the Utility Facet to such projects, so they can be deployed
in EARs.
A SAR project can embed dependencies in a lib folder, inside the archive.
A previous upstream bug prevented this behavior, but it has been fixed since : JBIDE-5691
Unfortunately, it seems a regression has crept in, because using the same projects
attached in JBIDE-5691, the embedded jar (junit.jar) is no longer present at the root of
sarproject.sar, when earproject is deployed on (any) JBoss AS.
In this use case, I have 2 sample maven-less projects :
-sarproject : has a dependency to JUNIT_HOME\junit.jar in the module assembly page. The
resulting org.eclipse.wst.common.component contains :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="sarproject">
<wb-resource deploy-path="/" source-path="/src"/>
<dependent-module archiveName="junit.jar" deploy-path="/"
handle="module:/classpath/var/JUNIT_HOME/junit.jar">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
-earproject : needed so sarproject can be a Module project. I've manually tweaked
org.eclipse.wst.common.component so sarproject will have the .sar extension when deployed.
Here is the end result :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="earproject">
<wb-resource deploy-path="/"
source-path="/EarContent"/>
<dependent-module archiveName="sarproject.sar"
deploy-path="/" handle="module:/resource/sarproject/sarproject">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
--
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
4:59 a.m.
New subject: [JBoss JIRA] (JBIDE-9496) [regression] - Exported files don't honor the module assembly settings
[
https://issues.jboss.org/browse/JBIDE-9496?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen updated JBIDE-9496:
---------------------------------------
Component/s: UpStream
[regression] - Exported files don't honor the module assembly
settings
----------------------------------------------------------------------
Key: JBIDE-9496
URL: https://issues.jboss.org/browse/JBIDE-9496
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers, UpStream
Affects Versions: 3.3.0.M3
Environment: Ubuntu 11.04, eclipse 3.7, JBT 3.3.0 M3
Reporter: Fred Bricon
Assignee: Rob Stryker
Labels: archive, deployment, sar
Fix For: 3.3.0.Beta1
Attachments: JBIDE_9496_projects.zip
I'm investigating ways to implement SAR support for maven projects (JBIDE-9127).
So far I've been adding the Utility Facet to such projects, so they can be deployed
in EARs.
A SAR project can embed dependencies in a lib folder, inside the archive.
A previous upstream bug prevented this behavior, but it has been fixed since : JBIDE-5691
Unfortunately, it seems a regression has crept in, because using the same projects
attached in JBIDE-5691, the embedded jar (junit.jar) is no longer present at the root of
sarproject.sar, when earproject is deployed on (any) JBoss AS.
In this use case, I have 2 sample maven-less projects :
-sarproject : has a dependency to JUNIT_HOME\junit.jar in the module assembly page. The
resulting org.eclipse.wst.common.component contains :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="sarproject">
<wb-resource deploy-path="/" source-path="/src"/>
<dependent-module archiveName="junit.jar" deploy-path="/"
handle="module:/classpath/var/JUNIT_HOME/junit.jar">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
-earproject : needed so sarproject can be a Module project. I've manually tweaked
org.eclipse.wst.common.component so sarproject will have the .sar extension when deployed.
Here is the end result :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="earproject">
<wb-resource deploy-path="/"
source-path="/EarContent"/>
<dependent-module archiveName="sarproject.sar"
deploy-path="/" handle="module:/resource/sarproject/sarproject">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
--
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
4:33 a.m.
New subject: [JBoss JIRA] (JBIDE-9496) [regression] - Exported files don't honor the module assembly settings
[
https://issues.jboss.org/browse/JBIDE-9496?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen updated JBIDE-9496:
---------------------------------------
Fix Version/s: 3.3.0.Beta1
(was: 3.3.0.M5)
Priority: Blocker (was: Major)
[regression] - Exported files don't honor the module assembly
settings
----------------------------------------------------------------------
Key: JBIDE-9496
URL: https://issues.jboss.org/browse/JBIDE-9496
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers, UpStream
Affects Versions: 3.3.0.M3
Environment: Ubuntu 11.04, eclipse 3.7, JBT 3.3.0 M3
Reporter: Fred Bricon
Assignee: Rob Stryker
Priority: Blocker
Labels: archive, deployment, sar
Fix For: 3.3.0.Beta1
Attachments: JBIDE_9496_projects.zip
I'm investigating ways to implement SAR support for maven projects (JBIDE-9127).
So far I've been adding the Utility Facet to such projects, so they can be deployed
in EARs.
A SAR project can embed dependencies in a lib folder, inside the archive.
A previous upstream bug prevented this behavior, but it has been fixed since : JBIDE-5691
Unfortunately, it seems a regression has crept in, because using the same projects
attached in JBIDE-5691, the embedded jar (junit.jar) is no longer present at the root of
sarproject.sar, when earproject is deployed on (any) JBoss AS.
In this use case, I have 2 sample maven-less projects :
-sarproject : has a dependency to JUNIT_HOME\junit.jar in the module assembly page. The
resulting org.eclipse.wst.common.component contains :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="sarproject">
<wb-resource deploy-path="/" source-path="/src"/>
<dependent-module archiveName="junit.jar" deploy-path="/"
handle="module:/classpath/var/JUNIT_HOME/junit.jar">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
-earproject : needed so sarproject can be a Module project. I've manually tweaked
org.eclipse.wst.common.component so sarproject will have the .sar extension when deployed.
Here is the end result :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="earproject">
<wb-resource deploy-path="/"
source-path="/EarContent"/>
<dependent-module archiveName="sarproject.sar"
deploy-path="/" handle="module:/resource/sarproject/sarproject">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
--
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
4:35 a.m.
New subject: [JBoss JIRA] (JBIDE-9496) [regression] - Exported files don't honor the module assembly settings
[
https://issues.jboss.org/browse/JBIDE-9496?page=com.atlassian.jira.plugin...
]
Max Rydahl Andersen commented on JBIDE-9496:
--------------------------------------------
follow up on bugzilla to make sure it is in SR2 of WTP
[regression] - Exported files don't honor the module assembly
settings
----------------------------------------------------------------------
Key: JBIDE-9496
URL: https://issues.jboss.org/browse/JBIDE-9496
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers, UpStream
Affects Versions: 3.3.0.M3
Environment: Ubuntu 11.04, eclipse 3.7, JBT 3.3.0 M3
Reporter: Fred Bricon
Assignee: Rob Stryker
Priority: Blocker
Labels: archive, deployment, sar
Fix For: 3.3.0.Beta1
Attachments: JBIDE_9496_projects.zip
I'm investigating ways to implement SAR support for maven projects (JBIDE-9127).
So far I've been adding the Utility Facet to such projects, so they can be deployed
in EARs.
A SAR project can embed dependencies in a lib folder, inside the archive.
A previous upstream bug prevented this behavior, but it has been fixed since : JBIDE-5691
Unfortunately, it seems a regression has crept in, because using the same projects
attached in JBIDE-5691, the embedded jar (junit.jar) is no longer present at the root of
sarproject.sar, when earproject is deployed on (any) JBoss AS.
In this use case, I have 2 sample maven-less projects :
-sarproject : has a dependency to JUNIT_HOME\junit.jar in the module assembly page. The
resulting org.eclipse.wst.common.component contains :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="sarproject">
<wb-resource deploy-path="/" source-path="/src"/>
<dependent-module archiveName="junit.jar" deploy-path="/"
handle="module:/classpath/var/JUNIT_HOME/junit.jar">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
-earproject : needed so sarproject can be a Module project. I've manually tweaked
org.eclipse.wst.common.component so sarproject will have the .sar extension when deployed.
Here is the end result :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="earproject">
<wb-resource deploy-path="/"
source-path="/EarContent"/>
<dependent-module archiveName="sarproject.sar"
deploy-path="/" handle="module:/resource/sarproject/sarproject">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
--
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:19 a.m.
New subject: [JBoss JIRA] (JBIDE-9496) [regression] - Exported files don't honor the module assembly settings
[
https://issues.jboss.org/browse/JBIDE-9496?page=com.atlassian.jira.plugin...
]
Rob Stryker commented on JBIDE-9496:
------------------------------------
As per https://bugs.eclipse.org/bugs/show_bug.cgi?id=354346
This is in SR2 with a unit test
[regression] - Exported files don't honor the module assembly
settings
----------------------------------------------------------------------
Key: JBIDE-9496
URL: https://issues.jboss.org/browse/JBIDE-9496
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers, UpStream
Affects Versions: 3.3.0.M3
Environment: Ubuntu 11.04, eclipse 3.7, JBT 3.3.0 M3
Reporter: Fred Bricon
Assignee: Rob Stryker
Priority: Blocker
Labels: archive, deployment, sar
Fix For: 3.3.0.Beta1
Attachments: JBIDE_9496_projects.zip
I'm investigating ways to implement SAR support for maven projects (JBIDE-9127).
So far I've been adding the Utility Facet to such projects, so they can be deployed
in EARs.
A SAR project can embed dependencies in a lib folder, inside the archive.
A previous upstream bug prevented this behavior, but it has been fixed since : JBIDE-5691
Unfortunately, it seems a regression has crept in, because using the same projects
attached in JBIDE-5691, the embedded jar (junit.jar) is no longer present at the root of
sarproject.sar, when earproject is deployed on (any) JBoss AS.
In this use case, I have 2 sample maven-less projects :
-sarproject : has a dependency to JUNIT_HOME\junit.jar in the module assembly page. The
resulting org.eclipse.wst.common.component contains :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="sarproject">
<wb-resource deploy-path="/" source-path="/src"/>
<dependent-module archiveName="junit.jar" deploy-path="/"
handle="module:/classpath/var/JUNIT_HOME/junit.jar">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
-earproject : needed so sarproject can be a Module project. I've manually tweaked
org.eclipse.wst.common.component so sarproject will have the .sar extension when deployed.
Here is the end result :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="earproject">
<wb-resource deploy-path="/"
source-path="/EarContent"/>
<dependent-module archiveName="sarproject.sar"
deploy-path="/" handle="module:/resource/sarproject/sarproject">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
--
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:23 a.m.
New subject: [JBoss JIRA] (JBIDE-9496) [regression] - Exported files don't honor the module assembly settings
[
https://issues.jboss.org/browse/JBIDE-9496?page=com.atlassian.jira.plugin...
]
Rob Stryker resolved JBIDE-9496.
--------------------------------
Fix Version/s: 3.3.0.CR1
(was: 3.3.0.Beta1)
Resolution: Done
Due to uncertainty as to when we upgrade our TP, I am marking this as already complete for
CR1, assuming of course that we upgrade our TP before then. Since it's already in the
sr2 builds, I'm fairly certain this is accurate.
[regression] - Exported files don't honor the module assembly
settings
----------------------------------------------------------------------
Key: JBIDE-9496
URL: https://issues.jboss.org/browse/JBIDE-9496
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers, UpStream
Affects Versions: 3.3.0.M3
Environment: Ubuntu 11.04, eclipse 3.7, JBT 3.3.0 M3
Reporter: Fred Bricon
Assignee: Rob Stryker
Priority: Blocker
Labels: archive, deployment, sar
Fix For: 3.3.0.CR1
Attachments: JBIDE_9496_projects.zip
I'm investigating ways to implement SAR support for maven projects (JBIDE-9127).
So far I've been adding the Utility Facet to such projects, so they can be deployed
in EARs.
A SAR project can embed dependencies in a lib folder, inside the archive.
A previous upstream bug prevented this behavior, but it has been fixed since : JBIDE-5691
Unfortunately, it seems a regression has crept in, because using the same projects
attached in JBIDE-5691, the embedded jar (junit.jar) is no longer present at the root of
sarproject.sar, when earproject is deployed on (any) JBoss AS.
In this use case, I have 2 sample maven-less projects :
-sarproject : has a dependency to JUNIT_HOME\junit.jar in the module assembly page. The
resulting org.eclipse.wst.common.component contains :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="sarproject">
<wb-resource deploy-path="/" source-path="/src"/>
<dependent-module archiveName="junit.jar" deploy-path="/"
handle="module:/classpath/var/JUNIT_HOME/junit.jar">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
-earproject : needed so sarproject can be a Module project. I've manually tweaked
org.eclipse.wst.common.component so sarproject will have the .sar extension when deployed.
Here is the end result :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="earproject">
<wb-resource deploy-path="/"
source-path="/EarContent"/>
<dependent-module archiveName="sarproject.sar"
deploy-path="/" handle="module:/resource/sarproject/sarproject">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
--
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:36 a.m.
New subject: [JBoss JIRA] (JBIDE-9496) [regression] - Exported files don't honor the module assembly settings
[
https://issues.jboss.org/browse/JBIDE-9496?page=com.atlassian.jira.plugin...
]
Martin Malina closed JBIDE-9496.
--------------------------------
Verified in JBT nightly 3.3.0.v20120423-2057-H4719-Beta3 and EAP 5.1.2
[regression] - Exported files don't honor the module assembly
settings
----------------------------------------------------------------------
Key: JBIDE-9496
URL: https://issues.jboss.org/browse/JBIDE-9496
Project: Tools (JBoss Tools)
Issue Type: Bug
Components: JBossAS/Servers, UpStream
Affects Versions: 3.3.0.M3
Environment: Ubuntu 11.04, eclipse 3.7, JBT 3.3.0 M3
Reporter: Fred Bricon
Assignee: Rob Stryker
Priority: Blocker
Labels: archive, deployment, sar
Fix For: 3.3.0.Beta3
Attachments: JBIDE_9496_projects.zip
I'm investigating ways to implement SAR support for maven projects (JBIDE-9127).
So far I've been adding the Utility Facet to such projects, so they can be deployed
in EARs.
A SAR project can embed dependencies in a lib folder, inside the archive.
A previous upstream bug prevented this behavior, but it has been fixed since : JBIDE-5691
Unfortunately, it seems a regression has crept in, because using the same projects
attached in JBIDE-5691, the embedded jar (junit.jar) is no longer present at the root of
sarproject.sar, when earproject is deployed on (any) JBoss AS.
In this use case, I have 2 sample maven-less projects :
-sarproject : has a dependency to JUNIT_HOME\junit.jar in the module assembly page. The
resulting org.eclipse.wst.common.component contains :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="sarproject">
<wb-resource deploy-path="/" source-path="/src"/>
<dependent-module archiveName="junit.jar" deploy-path="/"
handle="module:/classpath/var/JUNIT_HOME/junit.jar">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
-earproject : needed so sarproject can be a Module project. I've manually tweaked
org.eclipse.wst.common.component so sarproject will have the .sar extension when deployed.
Here is the end result :
{noformat}
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="earproject">
<wb-resource deploy-path="/"
source-path="/EarContent"/>
<dependent-module archiveName="sarproject.sar"
deploy-path="/" handle="module:/resource/sarproject/sarproject">
<dependency-type>uses</dependency-type>
</dependent-module>
</wb-module>
</project-modules>
{noformat}
--
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
5097
days inactive
5357
days old
jbosstools-issues@lists.jboss.org
19 comments
6 participants
participants (6)
-
Fred Bricon (JIRA) -
Martin Malina (JIRA)
-
Max Rydahl Andersen (Commented) (JIRA)
-
Max Rydahl Andersen (Updated) (JIRA)
-
Rob Stryker (JIRA)
-
Rob Stryker (Updated) (JIRA)