Mailing-List: contact dev-help@tomcat.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Tomcat Developers List" <dev@tomcat.apache.org>
Received-SPF: pass (athena.apache.org: domain of henri.gomez@gmail.com
 designates 209.85.200.170 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=gamma;
        h=message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=TVKZIwy+FgV8BybmXW4wukvGyfY9LkgnM+TSFwhM7pJIpu9DS1gWc884URVw20R6g8TkGEwkJlt1D7tyW+gUzKs4xrGQ+8WeE1HbLn0QnPFiXTNBVsDjRZlL+BeArVu68SPOwxrz/V7F7bJcOulsYG669z3qd5q45atr95faxmc=
Message-ID: <6291fc850804231338m1bef1425n808d7dd34223f45c@mail.gmail.com>
Date: Wed, 23 Apr 2008 22:38:15 +0200
From: "Henri Gomez" <henri.gomez@gmail.com>
To: "Tomcat Developers List" <dev@tomcat.apache.org>
Subject: Re: Osgifing Tomcat
In-Reply-To: <96e4b5230804231325j79498ed8wc3121b6ec64a2e91@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <6291fc850804220345w746f8b5cwc98eba9fbc5bcb14@mail.gmail.com>
	 <6291fc850804230836l35a7fd44yfae52464ab282dc7@mail.gmail.com>
	 <96e4b5230804231001he40cd16q67e7fb21a2b95393@mail.gmail.com>
	 <6291fc850804231012x4712f3a2n65242abc206431fd@mail.gmail.com>
	 <480F783C.9020107@hanik.com>
	 <6291fc850804231223g7a95d3ccx9911009430f1d953@mail.gmail.com>
	 <480F9375.2050805@hanik.com>
	 <96e4b5230804231305s451889c1u1f76fbd8c90cebbf@mail.gmail.com>
	 <6291fc850804231317p15ef2747tdf5fc020a6427a5a@mail.gmail.com>
	 <96e4b5230804231325j79498ed8wc3121b6ec64a2e91@mail.gmail.com>

>  >  it was the idea.
>
>  Sorry, -1 from me ( again ).

Sic...

>  And that would be the reason for -1.
>  If a build system requires intrusive changes and forces a particular code
>  organization - it shouldn't be used.

that's maven phylosophy, not so bad.

>  It is a choice each project can make, some people  like intrusive tools :-)

Intrusive ? Nope, just maven convention.

>  I think it is great to have alternative build files - as long as the
>  build system plays
>  nicely with others and doesn't set conditions on how we should organize code.
>  In particular - we have eclipse build support, it would be great to
>  add idea/netbeans
>  if anyone can support them - and if you can add maven in the same way ( i.e.
>  just maven files in a separate dir, without changes to source layout
>  just because
>  maven needs them) - no problem with me.

I use eclipse with m2eclipse and the support for multi modules is right.

Netbeans has a great maven support with mevenide (may be the best) and
some co-workers use IDEA and are very happy with its maven support.

>From my experience a mavenized project is buildable from command line
and with majors IDEs.

I've got a decent experiences after converting more than 100 projects
from ant to maven and make them as confortable under Eclipse than
previously.

Using maven and keeping the actual layout will be possible, but will
complexify the mvn and poms.

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org