[
http://jira.codehaus.org/browse/MWAS-34?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Chris Graham updated MWAS-34:
-----------------------------
Attachment: Was7-Structure.jpg
> ejbDeploy for WAS6 is broken
> ----------------------------
>
> Key: MWAS-34
> URL: http://jira.codehaus.org/browse/MWAS-34
> Project: Maven 2.x WebSphere 6 Plugin
> Issue Type: Bug
> Affects Versions: 1.1
> Environment: Was 6.0.x
> Reporter: Chris Graham
> Assignee: David J. M. Karlsen
> Priority: Blocker
> Attachments: MWAS-34.patch, Was6-Structure.jpg, Was61-Structure.jpg,
> Was7-Structure.jpg
>
>
> The current was6-maven-plugin sucessfully calls the ws_ant script to execute
> the ejbDeploy task. This is all working perfectly.
> However, the next thing that the plugin does is look at the workspace to
> extract the generated sources and generated/compiled classes.
> This is where the plugin fails (unnecessarilly). There are two issues that
> are causing issues here.
> 1. WAS 6.1 (and 7.0) creates an EJB project of the name of the project (the
> current plugin uses the finalname).
> WAS 6.0 creates an EJB project of a meaningless name (eg, actual example:
> e74f842a).
> The plugin was looking for the finalname/ejbModule to look for the generated
> sources, which could not be found when built with WAS 6.0.
> I've patched the code to work from a dir listing rather than the final name.
> 2. WAS 6.1 (and 7.0) creates nicely separated source (ejbModule) and compiled
> output directories (build/classes).
> WAS 6.0 does no such thing - they are not separated and all in the ejbModule
> dir.
> So, I've patched the plugin so that it does not fail the build if the dirs
> can not be found, but issue a warning instead. This is consistent with the
> plugin's handeling of missing source dirs to start with (issue a warning
> stating that "No sources were generated".
> I've also included screen shots of the various dir structures.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe from this list, please visit:
http://xircles.codehaus.org/manage_email
