[jbosstools-issues] [JBoss JIRA] Commented: (JBIDE-9497) Add support for SAR projects

[Fred Bricon (JIRA)]

    [ https://issues.jboss.org/browse/JBIDE-9497?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12620554#comment-12620554 ] 

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