What the article describes, is definitely not recommended practice. A better approach would be to have separate projects, say "client-api" and "client-impl", with the latter depending on the former. With your approach, you don't enforce that the api jar file is usable standalone.
Jochen On Wed, Apr 20, 2011 at 11:06 AM, xanadu72 <surs...@gmail.com> wrote: > Just to propose an article for the maven article page if you find it usefull. > > I wrote an article on how to manage > http://java-tutorial.ch/architecture/three-tier-architecture-with-maven > Three tier architecture using Maven > Feel free to give me your feedback about it or to indicate me something > wrong > > > Would it be possible to add this to the article page (maybe just a french > translation link or what so ever). > > Thans in advance for your time > > Cheers, > Sébastien Ursini > > -- > View this message in context: > http://maven.40175.n5.nabble.com/Article-proposed-for-Maven-Article-Page-tp4315294p4315294.html > Sent from the Maven Developers mailing list archive at Nabble.com. -- I Am What I Am And That's All What I Yam (Popeye) --------------------------------------------------------------------- To unsubscribe, e-mail: dev-unsubscr...@maven.apache.org For additional commands, e-mail: dev-h...@maven.apache.org
