There are a couple of JSRs (294 and 277) in the offing concerning modularity which may be a concern if you were to adopt OSGi. The main one of concern is JSR 294 due in Java 7 which contains language and packaging changes. There's also been some disagreement about whether or not to use OSGi as an implementation of the spec.
The other thing to keep in mind about OSGi is that there are different implementations which may present debugging and testing challenges. I've used the Knopflerfish plugin before and spent a lot of time dealing with classloading issues encountered while unit testing. Both Apache and Eclipse have their own implementations. I don't have any experience with either of them, but as far as Eclipse is concerned, adopting Equinox (the Eclipse implementation) may be a challenge for those developers not using Eclipse. Regards, Mark > > > As I've said many times, the OSGi/Eclipse plugin model is the one that > > ArgoUML should migrate to. > > I don't think we have any expertise on this but I think we're all > agreed that using common standards can only help us. > > I'll do what I suggested previously for the wiki and create a proposal > page then I'll create a placeholder for this proposal. > > ------------------------------------------------------ http://argouml.tigris.org/ds/viewMessage.do?dsForumId=450&dsMessageId=987521 To unsubscribe from this discussion, e-mail: [[email protected]].
