configuration and offer maximum
flexibility to work on one or several branches and the trunk.
On Fri, Apr 22, 2011 at 1:13 AM, Barrie Treloar [via Maven] <
ml-node+4332054-280406953-197...@n5.nabble.com> wrote:
> On Thu, Apr 21, 2011 at 5:35 PM, xanadu72 <[hidden
> email]<http://
ail]<http://user/SendEmail.jtp?type=node&node=4329867&i=1&by-user=t>>
> wrote:
> >> Jochen Wiedmann wrote:
> >>
> >>> On Wed, Apr 20, 2011 at 11:28 AM, xanadu72 <[hidden
> >>> email]<http://user/SendEmail.jtp?type=node&node=432
. In this
context the API is not intended to provided a way to implement multiple
implementations. The term api can be replaced with client.
On Wed, Apr 20, 2011 at 11:34 AM, jochen-2 [via Maven] <
ml-node+4315334-12416097-197...@n5.nabble.com> wrote:
> On Wed, Apr 20, 2011 at 11:28 AM
lone.
>
> Jochen
>
>
> On Wed, Apr 20, 2011 at 11:06 AM, xanadu72 <[hidden
> email]<http://user/SendEmail.jtp?type=node&node=4315310&i=0&by-user=t>>
> wrote:
>
> > Just to propose an article for the maven article page if you find it
>
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
