[jbosstools-issues] [JBoss JIRA] (JBIDE-6313) ESB binary export from JBDS doesn't include source

[Rob Stryker (JIRA)]

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

Rob Stryker commented on JBIDE-6313:
------------------------------------

I have ideas, but it would require a rewiring of esb.  ESB is currently basing its deployment code off some ASTools code, which was put in BEFORE wtp accepted some very large patches. And the AS Tools code is depending on deprecated code in wtp. 

This jira will need to wait for several issues to be fixed, and will require a rewiring of the guts of esb's module factory. 

I can work on it if you think it's valuable and I find time, since it is important to eventually move off the deprecated classes in wtp, and it will provide substantial benefits to us in other ways. 


                
> ESB binary export from JBDS doesn't include source
> --------------------------------------------------
>
>                 Key: JBIDE-6313
>                 URL: https://issues.jboss.org/browse/JBIDE-6313
>             Project: Tools (JBoss Tools)
>          Issue Type: Feature Request
>          Components: z - Legacy - libmanagement
>    Affects Versions: 3.0.0.GA
>            Reporter: Stelios Koussouris
>            Assignee: Rob Stryker
>              Labels: libmanagement
>             Fix For: 4.0.x
>
>   Original Estimate: 0 minutes
>  Remaining Estimate: 0 minutes
>
> Trying to export ESB binary along with the source code of
> a) the esb actions
> b) the referenced jars
> The result of setting the references to other projects/jars via 
> ESB Project --> Properties --> Module Assembly and then
> ESB Project --> Export --> ESB --> clicking the  "export source files"
> the jars of the referenced projects are included but no source code for nether the ESB classes or the referenced projects.

--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators
For more information on JIRA, see: http://www.atlassian.com/software/jira