Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
What are the plug-in conventions you use in your big Eclipse RCP-applications?
Should ui and code-behind be separated, or is it enough to separate the different parts of the program into plug-in-projects?
What about the database-connection? Should this be one plug-in as well?
The biggest convention is making product releasing and patching even more simplier. For example, if there is a bug in plugin.A, the fixing and patching are only plugin.A related changes, instead of the whole product rebuilding and distributing.
The best practices could be learned from well-known eclipse projects plugin organization, like CDT, or other projects. However, the requirements from your application are the most important.