"alesj" wrote : "scott.stark(a)jboss.org" wrote :
| | Every project should be further broken up into an spi/api artifacts for the spi
packages, and a plugin artifact for the plugin/implementation packages.
| |
|
| Divided into different projects - [project]-spi and [project]-impl?
| Probably not?
|
Yes, that *is* what we want.
We need a project that creates a kind of "j2ee.jar" for our shared integration
such that people compile against the api/spi not the implementation details
which are subject to change and will only lead to incompatibilies if people did it.
There's also a case for creating seperate projects for
[project]-tests
since many of the tests do depend upon implemenation details (specific implementations)
that the main projects should not depend upon.
But, Maven does support classpaths for the main source and tests
(unlike Eclipse), so this is less important.
View the original post :
http://www.jboss.com/index.html?module=bb&op=viewtopic&p=3990979#...
Reply to the post :
http://www.jboss.com/index.html?module=bb&op=posting&mode=reply&a...