[
https://issues.apache.org/jira/browse/JAMESAPP-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Eric Charles closed JAMESAPP-3.
-------------------------------
Resolution: Fixed
James App can now be debugged in eclipse and appassemble still works via
command line.
http://james.apache.org/server/3/dev-build.html must be adapted, but this is
part of the global website update for beta4 (conf,...).
Closing this.
> Make App project friend with your favorite maven IDE
> ----------------------------------------------------
>
> Key: JAMESAPP-3
> URL: https://issues.apache.org/jira/browse/JAMESAPP-3
> Project: JAMES App
> Issue Type: Improvement
> Reporter: Eric Charles
> Assignee: Eric Charles
>
> Atm, we can not debug anymore james in a IDE (Eclipse...) because:
> - The main class is in server-container-spring => Move main class from
> container-spring to app
> - Some of the config files are still loaded reading via 'file', and not via
> 'classpath', which makes necessary to copy them => Load all via classpath
> - The config files loaded via classpath are not located in src/main/resources
> => Move config files to src/main/resources
> So:
> - Move main class from container-spring to app
> - Load all via classpath (will be also more osgi-friendly for the future)
> - Move config files to src/main/resources
> With those changes, it will be straighforward for any developer to setup its
> IDE and code/debug james.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://issues.apache.org/jira/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
