11:21 a.m.
Add support for SAR projects
----------------------------
Key: JBIDE-9497
URL: https://issues.jboss.org/browse/JBIDE-9497
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Affects Versions: 3.3.0.M2
Reporter: Fred Bricon
Fix For: 3.3.0.M3
While working on JBIDE-9127, it appeared to me you can not deploy standalone SAR projects
(a jar with a .sar extension, capable of embedding other jars) in JBT.
This is because the JBoss AS server adapters need a new Module type to be able to perform
the actual deployment.
But in order to add such module, we need some sort of marker to identify SAR projects,
most probably a new Facet.
Sooooo, ideally we'd need to :
- create a new SAR Facet. Installing the SAR Facet would create, if needed, an empty
jboss-service.xml file in <some configurable source folder>/META-INF/
- add the ability to include/exclude files from being deployed (using filesets)
- Add a new Server Module / Factory, capable of dealing with SAR projects. SAR could be
deployed either as compressed archive or in an exploded form
- Add a new Wizard, to be able to create SAR archives
From my understanding, this is pretty similar to what's been done
for ESB projects.
Question : where would such plugins/features be kept? ESB has its own module. Adding a new
SAR module or putting it under AS wouldn't feel right IMHO.
I would suggest to rename the ESB module as JBossPackaging (similar to
http://mojo.codehaus.org/jboss-packaging-maven-plugin) and put the SAR stuff next to the
ESB stuff.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:18 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9497) Add support for SAR projects
[
https://issues.jboss.org/browse/JBIDE-9497?page=com.atlassian.jira.plugin...
]
Rob Stryker commented on JBIDE-9497:
------------------------------------
as.wtp already has the base classes required for most of this stuff. Then each component
simply needs to extend those classes for their own use.
Remember, ESB has a lot of other shit in it, like their own custom runtimes nad classpath
containers, that need to be added during creation of the project, so trying to smush this
all together 100% doesn't really work.
Since the base clsases live in as.wtp.core/ui, the extensions nad overrides should live
where they belong. We already have an as.mbeans plugin which is for making mbeans, and, it
would make sense that mbeans live in a sar project, so I think this should live in the
as.mbeans plugin.
Add support for SAR projects
----------------------------
Key: JBIDE-9497
URL: https://issues.jboss.org/browse/JBIDE-9497
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Affects Versions: 3.3.0.M2
Reporter: Fred Bricon
Assignee: Rob Stryker
Labels: configuration, deployment, sar, wizard
Fix For: 3.3.0.M3
While working on JBIDE-9127, it appeared to me you can not deploy standalone SAR projects
(a jar with a .sar extension, capable of embedding other jars) in JBT.
This is because the JBoss AS server adapters need a new Module type to be able to perform
the actual deployment.
But in order to add such module, we need some sort of marker to identify SAR projects,
most probably a new Facet.
Sooooo, ideally we'd need to :
- create a new SAR Facet. Installing the SAR Facet would create, if needed, an empty
jboss-service.xml file in <some configurable source folder>/META-INF/
- add the ability to include/exclude files from being deployed (using filesets)
- Add a new Server Module / Factory, capable of dealing with SAR projects. SAR could be
deployed either as compressed archive or in an exploded form
- Add a new Wizard, to be able to create SAR archives
From my understanding, this is pretty similar to what's been done for ESB projects.
Question : where would such plugins/features be kept? ESB has its own module. Adding a
new SAR module or putting it under AS wouldn't feel right IMHO.
I would suggest to rename the ESB module as JBossPackaging (similar to
http://mojo.codehaus.org/jboss-packaging-maven-plugin) and put the SAR stuff next to the
ESB stuff.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:39 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9497) Add support for SAR projects
[
https://issues.jboss.org/browse/JBIDE-9497?page=com.atlassian.jira.plugin...
]
Fred Bricon commented on JBIDE-9497:
------------------------------------
Rob,
my initial feedback : You need to export the org.jboss.ide.eclipse.as.ui.mbeans.project,
so I can call the facet provider.
Also, If I click on "Run As" on a SAR project, I can't deploy on a server.
And yeah, the Mozilla Icon looks like $h!7 :-)
Add support for SAR projects
----------------------------
Key: JBIDE-9497
URL: https://issues.jboss.org/browse/JBIDE-9497
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Affects Versions: 3.3.0.M2
Reporter: Fred Bricon
Assignee: Fred Bricon
Labels: configuration, deployment, sar, wizard
Fix For: 3.3.0.M3
While working on JBIDE-9127, it appeared to me you can not deploy standalone SAR projects
(a jar with a .sar extension, capable of embedding other jars) in JBT.
This is because the JBoss AS server adapters need a new Module type to be able to perform
the actual deployment.
But in order to add such module, we need some sort of marker to identify SAR projects,
most probably a new Facet.
Sooooo, ideally we'd need to :
- create a new SAR Facet. Installing the SAR Facet would create, if needed, an empty
jboss-service.xml file in <some configurable source folder>/META-INF/
- add the ability to include/exclude files from being deployed (using filesets)
- Add a new Server Module / Factory, capable of dealing with SAR projects. SAR could be
deployed either as compressed archive or in an exploded form
- Add a new Wizard, to be able to create SAR archives
From my understanding, this is pretty similar to what's been done for ESB projects.
Question : where would such plugins/features be kept? ESB has its own module. Adding a
new SAR module or putting it under AS wouldn't feel right IMHO.
I would suggest to rename the ESB module as JBossPackaging (similar to
http://mojo.codehaus.org/jboss-packaging-maven-plugin) and put the SAR stuff next to the
ESB stuff.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:33 p.m.
New subject: [JBoss JIRA] Issue Comment Edited: (JBIDE-9497) Add support for SAR projects
[
https://issues.jboss.org/browse/JBIDE-9497?page=com.atlassian.jira.plugin...
]
Fred Bricon edited comment on JBIDE-9497 at 8/11/11 6:32 PM:
-------------------------------------------------------------
Rob, there seems to be just one big issue : the server adapter deploys .java files instead
of classes.
My .component looks like :
{noformat}
<?xml version="1.0" encoding="UTF-8"?>
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="sarproject">
<wb-resource deploy-path="/"
source-path="/src/main/resources"/>
<wb-resource deploy-path="/"
source-path="/src/main/java"/>
<dependent-module archiveName="commons-lang-2.5.jar"
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>
<property name="java-output-path"
value="target/classes"/>
</wb-module>
</project-modules>
{noformat}
This is really weird, cause it looks like standard utility projects' .component
was (Author: fbricon):
Rob, there seem to be just one big issue : the server adapter deploys .java files
instead of classes.
My .component looks like :
{noformat}
<?xml version="1.0" encoding="UTF-8"?>
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="sarproject">
<wb-resource deploy-path="/"
source-path="/src/main/resources"/>
<wb-resource deploy-path="/"
source-path="/src/main/java"/>
<dependent-module archiveName="commons-lang-2.5.jar"
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>
<property name="java-output-path"
value="target/classes"/>
</wb-module>
</project-modules>
{noformat}
This is really weird, cause it looks like standard utility projects' .component
Add support for SAR projects
----------------------------
Key: JBIDE-9497
URL: https://issues.jboss.org/browse/JBIDE-9497
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Affects Versions: 3.3.0.M2
Reporter: Fred Bricon
Assignee: Fred Bricon
Labels: configuration, deployment, sar, wizard
Fix For: 3.3.0.M3
While working on JBIDE-9127, it appeared to me you can not deploy standalone SAR projects
(a jar with a .sar extension, capable of embedding other jars) in JBT.
This is because the JBoss AS server adapters need a new Module type to be able to perform
the actual deployment.
But in order to add such module, we need some sort of marker to identify SAR projects,
most probably a new Facet.
Sooooo, ideally we'd need to :
- create a new SAR Facet. Installing the SAR Facet would create, if needed, an empty
jboss-service.xml file in <some configurable source folder>/META-INF/
- add the ability to include/exclude files from being deployed (using filesets)
- Add a new Server Module / Factory, capable of dealing with SAR projects. SAR could be
deployed either as compressed archive or in an exploded form
- Add a new Wizard, to be able to create SAR archives
From my understanding, this is pretty similar to what's been done for ESB projects.
Question : where would such plugins/features be kept? ESB has its own module. Adding a
new SAR module or putting it under AS wouldn't feel right IMHO.
I would suggest to rename the ESB module as JBossPackaging (similar to
http://mojo.codehaus.org/jboss-packaging-maven-plugin) and put the SAR stuff next to the
ESB stuff.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:33 p.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9497) Add support for SAR projects
[
https://issues.jboss.org/browse/JBIDE-9497?page=com.atlassian.jira.plugin...
]
Fred Bricon commented on JBIDE-9497:
------------------------------------
Rob, there seem to be just one big issue : the server adapter deploys .java files instead
of classes.
My .component looks like :
{noformat}
<?xml version="1.0" encoding="UTF-8"?>
<project-modules id="moduleCoreId" project-version="1.5.0">
<wb-module deploy-name="sarproject">
<wb-resource deploy-path="/"
source-path="/src/main/resources"/>
<wb-resource deploy-path="/"
source-path="/src/main/java"/>
<dependent-module archiveName="commons-lang-2.5.jar"
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>
<property name="java-output-path"
value="target/classes"/>
</wb-module>
</project-modules>
{noformat}
This is really weird, cause it looks like standard utility projects' .component
Add support for SAR projects
----------------------------
Key: JBIDE-9497
URL: https://issues.jboss.org/browse/JBIDE-9497
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Affects Versions: 3.3.0.M2
Reporter: Fred Bricon
Assignee: Fred Bricon
Labels: configuration, deployment, sar, wizard
Fix For: 3.3.0.M3
While working on JBIDE-9127, it appeared to me you can not deploy standalone SAR projects
(a jar with a .sar extension, capable of embedding other jars) in JBT.
This is because the JBoss AS server adapters need a new Module type to be able to perform
the actual deployment.
But in order to add such module, we need some sort of marker to identify SAR projects,
most probably a new Facet.
Sooooo, ideally we'd need to :
- create a new SAR Facet. Installing the SAR Facet would create, if needed, an empty
jboss-service.xml file in <some configurable source folder>/META-INF/
- add the ability to include/exclude files from being deployed (using filesets)
- Add a new Server Module / Factory, capable of dealing with SAR projects. SAR could be
deployed either as compressed archive or in an exploded form
- Add a new Wizard, to be able to create SAR archives
From my understanding, this is pretty similar to what's been done for ESB projects.
Question : where would such plugins/features be kept? ESB has its own module. Adding a
new SAR module or putting it under AS wouldn't feel right IMHO.
I would suggest to rename the ESB module as JBossPackaging (similar to
http://mojo.codehaus.org/jboss-packaging-maven-plugin) and put the SAR stuff next to the
ESB stuff.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
6:05 a.m.
New subject: [JBoss JIRA] Resolved: (JBIDE-9497) Add support for SAR projects
[
https://issues.jboss.org/browse/JBIDE-9497?page=com.atlassian.jira.plugin...
]
Rob Stryker resolved JBIDE-9497.
--------------------------------
Labels: configuration deployment new_and_noteworthy sar wizard (was:
configuration deployment sar wizard)
Resolution: Done
fixed it!
Add support for SAR projects
----------------------------
Key: JBIDE-9497
URL: https://issues.jboss.org/browse/JBIDE-9497
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Affects Versions: 3.3.0.M2
Reporter: Fred Bricon
Assignee: Rob Stryker
Labels: configuration, deployment, sar, wizard, new_and_noteworthy
Fix For: 3.3.0.M3
While working on JBIDE-9127, it appeared to me you can not deploy standalone SAR projects
(a jar with a .sar extension, capable of embedding other jars) in JBT.
This is because the JBoss AS server adapters need a new Module type to be able to perform
the actual deployment.
But in order to add such module, we need some sort of marker to identify SAR projects,
most probably a new Facet.
Sooooo, ideally we'd need to :
- create a new SAR Facet. Installing the SAR Facet would create, if needed, an empty
jboss-service.xml file in <some configurable source folder>/META-INF/
- add the ability to include/exclude files from being deployed (using filesets)
- Add a new Server Module / Factory, capable of dealing with SAR projects. SAR could be
deployed either as compressed archive or in an exploded form
- Add a new Wizard, to be able to create SAR archives
From my understanding, this is pretty similar to what's been done for ESB projects.
Question : where would such plugins/features be kept? ESB has its own module. Adding a
new SAR module or putting it under AS wouldn't feel right IMHO.
I would suggest to rename the ESB module as JBossPackaging (similar to
http://mojo.codehaus.org/jboss-packaging-maven-plugin) and put the SAR stuff next to the
ESB stuff.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:21 a.m.
New subject: [JBoss JIRA] Closed: (JBIDE-9497) Add support for SAR projects
[
https://issues.jboss.org/browse/JBIDE-9497?page=com.atlassian.jira.plugin...
]
Libor Zoubek closed JBIDE-9497.
-------------------------------
Add support for SAR projects
----------------------------
Key: JBIDE-9497
URL: https://issues.jboss.org/browse/JBIDE-9497
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Affects Versions: 3.3.0.M2
Reporter: Fred Bricon
Assignee: Rob Stryker
Labels: configuration, deployment, new_and_noteworthy, sar, wizard
Fix For: 3.3.0.M3
While working on JBIDE-9127, it appeared to me you can not deploy standalone SAR projects
(a jar with a .sar extension, capable of embedding other jars) in JBT.
This is because the JBoss AS server adapters need a new Module type to be able to perform
the actual deployment.
But in order to add such module, we need some sort of marker to identify SAR projects,
most probably a new Facet.
Sooooo, ideally we'd need to :
- create a new SAR Facet. Installing the SAR Facet would create, if needed, an empty
jboss-service.xml file in <some configurable source folder>/META-INF/
- add the ability to include/exclude files from being deployed (using filesets)
- Add a new Server Module / Factory, capable of dealing with SAR projects. SAR could be
deployed either as compressed archive or in an exploded form
- Add a new Wizard, to be able to create SAR archives
From my understanding, this is pretty similar to what's been done for ESB projects.
Question : where would such plugins/features be kept? ESB has its own module. Adding a
new SAR module or putting it under AS wouldn't feel right IMHO.
I would suggest to rename the ESB module as JBossPackaging (similar to
http://mojo.codehaus.org/jboss-packaging-maven-plugin) and put the SAR stuff next to the
ESB stuff.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
9:21 a.m.
New subject: [JBoss JIRA] Commented: (JBIDE-9497) Add support for SAR projects
[
https://issues.jboss.org/browse/JBIDE-9497?page=com.atlassian.jira.plugin...
]
Libor Zoubek commented on JBIDE-9497:
-------------------------------------
verified on JBT 2011-09-07_05-39-13-H18
Add support for SAR projects
----------------------------
Key: JBIDE-9497
URL: https://issues.jboss.org/browse/JBIDE-9497
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Affects Versions: 3.3.0.M2
Reporter: Fred Bricon
Assignee: Rob Stryker
Labels: configuration, deployment, new_and_noteworthy, sar, wizard
Fix For: 3.3.0.M3
While working on JBIDE-9127, it appeared to me you can not deploy standalone SAR projects
(a jar with a .sar extension, capable of embedding other jars) in JBT.
This is because the JBoss AS server adapters need a new Module type to be able to perform
the actual deployment.
But in order to add such module, we need some sort of marker to identify SAR projects,
most probably a new Facet.
Sooooo, ideally we'd need to :
- create a new SAR Facet. Installing the SAR Facet would create, if needed, an empty
jboss-service.xml file in <some configurable source folder>/META-INF/
- add the ability to include/exclude files from being deployed (using filesets)
- Add a new Server Module / Factory, capable of dealing with SAR projects. SAR could be
deployed either as compressed archive or in an exploded form
- Add a new Wizard, to be able to create SAR archives
From my understanding, this is pretty similar to what's been done for ESB projects.
Question : where would such plugins/features be kept? ESB has its own module. Adding a
new SAR module or putting it under AS wouldn't feel right IMHO.
I would suggest to rename the ESB module as JBossPackaging (similar to
http://mojo.codehaus.org/jboss-packaging-maven-plugin) and put the SAR stuff next to the
ESB stuff.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:45 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-9497) Add support for SAR projects
[
https://issues.jboss.org/browse/JBIDE-9497?page=com.atlassian.jira.plugin...
]
Isaac Rooskov updated JBIDE-9497:
---------------------------------
Release Notes Docs Status: Documented as Resolved Issue
Release Notes Text: JBoss Developer Studio now supports the deployment of
standalone SAR projects. To undertake this a new wizard has been created to take a user
through the process. For further information see the relevant documentation accompanying
this release.
Add support for SAR projects
----------------------------
Key: JBIDE-9497
URL: https://issues.jboss.org/browse/JBIDE-9497
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Affects Versions: 3.3.0.M2
Reporter: Fred Bricon
Assignee: Rob Stryker
Labels: configuration, deployment, new_and_noteworthy, sar, wizard
Fix For: 3.3.0.M3
While working on JBIDE-9127, it appeared to me you can not deploy standalone SAR projects
(a jar with a .sar extension, capable of embedding other jars) in JBT.
This is because the JBoss AS server adapters need a new Module type to be able to perform
the actual deployment.
But in order to add such module, we need some sort of marker to identify SAR projects,
most probably a new Facet.
Sooooo, ideally we'd need to :
- create a new SAR Facet. Installing the SAR Facet would create, if needed, an empty
jboss-service.xml file in <some configurable source folder>/META-INF/
- add the ability to include/exclude files from being deployed (using filesets)
- Add a new Server Module / Factory, capable of dealing with SAR projects. SAR could be
deployed either as compressed archive or in an exploded form
- Add a new Wizard, to be able to create SAR archives
From my understanding, this is pretty similar to what's been done for ESB projects.
Question : where would such plugins/features be kept? ESB has its own module. Adding a
new SAR module or putting it under AS wouldn't feel right IMHO.
I would suggest to rename the ESB module as JBossPackaging (similar to
http://mojo.codehaus.org/jboss-packaging-maven-plugin) and put the SAR stuff next to the
ESB stuff.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:47 p.m.
New subject: [JBoss JIRA] Closed: (JBIDE-9497) Add support for SAR projects
[
https://issues.jboss.org/browse/JBIDE-9497?page=com.atlassian.jira.plugin...
]
Isaac Rooskov closed JBIDE-9497.
--------------------------------
Resolution: Done
re-closing the issue now
Add support for SAR projects
----------------------------
Key: JBIDE-9497
URL: https://issues.jboss.org/browse/JBIDE-9497
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Affects Versions: 3.3.0.M2
Reporter: Fred Bricon
Assignee: Rob Stryker
Labels: configuration, deployment, new_and_noteworthy, sar, wizard
Fix For: 3.3.0.M3
While working on JBIDE-9127, it appeared to me you can not deploy standalone SAR projects
(a jar with a .sar extension, capable of embedding other jars) in JBT.
This is because the JBoss AS server adapters need a new Module type to be able to perform
the actual deployment.
But in order to add such module, we need some sort of marker to identify SAR projects,
most probably a new Facet.
Sooooo, ideally we'd need to :
- create a new SAR Facet. Installing the SAR Facet would create, if needed, an empty
jboss-service.xml file in <some configurable source folder>/META-INF/
- add the ability to include/exclude files from being deployed (using filesets)
- Add a new Server Module / Factory, capable of dealing with SAR projects. SAR could be
deployed either as compressed archive or in an exploded form
- Add a new Wizard, to be able to create SAR archives
From my understanding, this is pretty similar to what's been done for ESB projects.
Question : where would such plugins/features be kept? ESB has its own module. Adding a
new SAR module or putting it under AS wouldn't feel right IMHO.
I would suggest to rename the ESB module as JBossPackaging (similar to
http://mojo.codehaus.org/jboss-packaging-maven-plugin) and put the SAR stuff next to the
ESB stuff.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:04 p.m.
New subject: [JBoss JIRA] Updated: (JBIDE-9497) Add support for SAR projects
[
https://issues.jboss.org/browse/JBIDE-9497?page=com.atlassian.jira.plugin...
]
Isaac Rooskov updated JBIDE-9497:
---------------------------------
Writer: irooskov
Updating 'Writer' and then closing again
Add support for SAR projects
----------------------------
Key: JBIDE-9497
URL: https://issues.jboss.org/browse/JBIDE-9497
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Affects Versions: 3.3.0.M2
Reporter: Fred Bricon
Assignee: Rob Stryker
Labels: configuration, deployment, new_and_noteworthy, sar, wizard
Fix For: 3.3.0.M3
While working on JBIDE-9127, it appeared to me you can not deploy standalone SAR projects
(a jar with a .sar extension, capable of embedding other jars) in JBT.
This is because the JBoss AS server adapters need a new Module type to be able to perform
the actual deployment.
But in order to add such module, we need some sort of marker to identify SAR projects,
most probably a new Facet.
Sooooo, ideally we'd need to :
- create a new SAR Facet. Installing the SAR Facet would create, if needed, an empty
jboss-service.xml file in <some configurable source folder>/META-INF/
- add the ability to include/exclude files from being deployed (using filesets)
- Add a new Server Module / Factory, capable of dealing with SAR projects. SAR could be
deployed either as compressed archive or in an exploded form
- Add a new Wizard, to be able to create SAR archives
From my understanding, this is pretty similar to what's been done for ESB projects.
Question : where would such plugins/features be kept? ESB has its own module. Adding a
new SAR module or putting it under AS wouldn't feel right IMHO.
I would suggest to rename the ESB module as JBossPackaging (similar to
http://mojo.codehaus.org/jboss-packaging-maven-plugin) and put the SAR stuff next to the
ESB stuff.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
11:06 p.m.
New subject: [JBoss JIRA] Closed: (JBIDE-9497) Add support for SAR projects
[
https://issues.jboss.org/browse/JBIDE-9497?page=com.atlassian.jira.plugin...
]
Isaac Rooskov closed JBIDE-9497.
--------------------------------
Resolution: Done
Add support for SAR projects
----------------------------
Key: JBIDE-9497
URL: https://issues.jboss.org/browse/JBIDE-9497
Project: Tools (JBoss Tools)
Issue Type: Feature Request
Affects Versions: 3.3.0.M2
Reporter: Fred Bricon
Assignee: Rob Stryker
Labels: configuration, deployment, new_and_noteworthy, sar, wizard
Fix For: 3.3.0.M3
While working on JBIDE-9127, it appeared to me you can not deploy standalone SAR projects
(a jar with a .sar extension, capable of embedding other jars) in JBT.
This is because the JBoss AS server adapters need a new Module type to be able to perform
the actual deployment.
But in order to add such module, we need some sort of marker to identify SAR projects,
most probably a new Facet.
Sooooo, ideally we'd need to :
- create a new SAR Facet. Installing the SAR Facet would create, if needed, an empty
jboss-service.xml file in <some configurable source folder>/META-INF/
- add the ability to include/exclude files from being deployed (using filesets)
- Add a new Server Module / Factory, capable of dealing with SAR projects. SAR could be
deployed either as compressed archive or in an exploded form
- Add a new Wizard, to be able to create SAR archives
From my understanding, this is pretty similar to what's been done for ESB projects.
Question : where would such plugins/features be kept? ESB has its own module. Adding a
new SAR module or putting it under AS wouldn't feel right IMHO.
I would suggest to rename the ESB module as JBossPackaging (similar to
http://mojo.codehaus.org/jboss-packaging-maven-plugin) and put the SAR stuff next to the
ESB stuff.
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
5305
days inactive
5355
days old
jbosstools-issues@lists.jboss.org
11 comments
4 participants
participants (4)
-
Fred Bricon (JIRA) -
Isaac Rooskov (JIRA)
-
Libor Zoubek (JIRA)
-
Rob Stryker (JIRA)