On Thu, Apr 21, 2011 at 6:33 AM, Jörg Schaible <[email protected]> wrote: > Jochen Wiedmann wrote: > >> On Wed, Apr 20, 2011 at 11:28 AM, xanadu72 <[email protected]> wrote: >> >>> The client api is a separate artifact. You can reuse it as you want. In >>> your repository you will get in the same release folder two artifacts : >> >> That's completely understood. But as a separate jar file, you should >> ensure that it is compilable without any of the other classes. For >> example, it might accidentally import something from the rest of the >> packages. You don't get that safety by just repackaging a bunch of >> class files in another jar file. > > Even more, the implementation may require dependencies, that are absolutely > uninteresting (and unwanted) for the client. This itches me already for the > ejb-client artifact. Separate projects can have different dependencies, > attached artifacts share them always with the main artifact.
+1 for all the reasons to separate client/api jars. --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
