You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@excalibur.apache.org by "J Aaron Farr (JIRA)" <de...@excalibur.apache.org> on 2005/12/13 20:42:47 UTC

[jira] Resolved: (FORTRESS-17) Running Fortress in Eclipse

     [ http://issues.apache.org/jira/browse/FORTRESS-17?page=all ]
     
J Aaron Farr resolved FORTRESS-17:
----------------------------------

    Resolution: Fixed

There's a work around for now (using the roles file).

> Running Fortress in Eclipse
> ---------------------------
>
>          Key: FORTRESS-17
>          URL: http://issues.apache.org/jira/browse/FORTRESS-17
>      Project: Excalibur Fortress
>         Type: Bug
>   Components: Implementation
>     Versions: 1.0, 1.1
>  Environment: Tested in Eclipse 3.0.1 on Java 1.4.2 (Windows)
>     Reporter: J Aaron Farr
>     Assignee: J Aaron Farr
>      Fix For: 1.2

>
> Fortress does not launch correctly embedded within an Eclipse plugin when using the meta info.  SVN revision 160410 fixes a bug when using EMC-style "roles" files so that this method works in Eclipse, but switching to using the meta-format results in ClassNotFound exceptions.  It is probably something with a Classloader that is not using the user supplied classloader from FortressConfig.  
> When embedding in Eclipse, you must provide the classloader, for example:
>         final FortressConfig config = new FortressConfig();
>         config.setContextClassLoader(MyPlugin.class.getClassLoader());

-- 
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
   http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
   http://www.atlassian.com/software/jira


---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@excalibur.apache.org
For additional commands, e-mail: dev-help@excalibur.apache.org