Our code is in Java and Javascript (AJAX libraries). We have wrappers / reusable code around existing libraries to perform common tasks like db connections, session management, logging, sleep settings, basic structure, some reusable multi-level code, etc. From the end of javascript, we have page initializers, interface layout components, js user objects, and some of our own logic.
We have several projects where this code can be reused, but at the same time this code develops with the application. Therefore, if we find a common way to do this, we can transfer it to the framework code and let other projects also benefit from it. If / when we find an error in the base code, we can fix it in one place and fix it, and all other projects will pick up the change (and not all, making the changes locally).
If it is only java files, we can save it as a separate project and include it as a dependent module in eclipse / maven and include it as a jar when and when it is needed. This part is easy to handle, but now we also have reusable javascript in the code, which may not be exactly jar (ed). We need some suggestions on how the code should be output, so we can reuse it through maven (deployment time) and through eclipse (development time) without going through too many hoops.
Before writing this, I came across some articles on stackoverflow that talk about reusing code and methodologies that are great, but not exactly how to manage them using svn, maven, eclipse, etc.
Contact them for reference.
ant, , . , , , . 5 .
, , - , eclipse, , ?