Mailing-List: contact dev-help@maven.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "Maven Developers List" <dev@maven.apache.org>
Received-SPF: pass (herse.apache.org: domain of mkleint@gmail.com designates
 64.233.184.228 as permitted sender)
DomainKey-Signature: a=rsa-sha1; c=nofws;
        d=gmail.com; s=beta;
        h=received:message-id:date:from:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references;
        b=Ueo1utNPoFAxQQVOIS16pLYSzZxB5YPVNpnJrBP6RZZIB+5XO2Xq7avSwPk8T2Asjzi4fbGyaQyNvi0PqGpZtE1+O1TdfCmtX6bd3uVAxTlHuPU4xI1C4loGS0kMHUIyjI9wSAn65d+I9Gaqas0NFhE1/YSPj+ftFKpSCsltCr4=
Message-ID: <f84708e90704010349mb266b57mdba391131cc9cdc5@mail.gmail.com>
Date: Sun, 1 Apr 2007 12:49:04 +0200
From: "Milos Kleint" <mkleint@gmail.com>
To: "Maven Developers List" <dev@maven.apache.org>
Subject: Re: [Archetypes] plugin proposition
In-Reply-To: <394ab6ec0703311321y3d4739cdr80b080ba0102c7c8@mail.gmail.com>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: quoted-printable
Content-Disposition: inline
References: <7fdaf8540703081054r185d9631jb8e641158c760fc5@mail.gmail.com>
	 <7D0F77F1-C388-47EC-8496-4970A28D406D@apache.org>
	 <7fdaf8540703231024j6580fc10m9e62235d1dfb6ea0@mail.gmail.com>
	 <06841E73-E24B-4A8C-9997-52EB7C8E5275@apache.org>
	 <7fdaf8540703291156s71ff8700jf460b0cb6f5b3962@mail.gmail.com>
	 <7fdaf8540703310707q4ec7daf3if7e5178d242512d@mail.gmail.com>
	 <164F374D-2491-43B7-B6AE-6BFC2B6BF73B@maven.org>
	 <394ab6ec0703310908x48415a98o564280910ea8bd5e@mail.gmail.com>
	 <24BE1707-360B-4C8A-AFD3-F192E5D70A3B@maven.org>
	 <394ab6ec0703311321y3d4739cdr80b080ba0102c7c8@mail.gmail.com>

On 3/31/07, Heinrich Nirschl <heinrich.nirschl@gmail.com> wrote:
> On 3/31/07, Jason van Zyl <jason@maven.org> wrote:
> >
> > On 31 Mar 07, at 12:08 PM 31 Mar 07, Heinrich Nirschl wrote:
> >
> > > On 3/31/07, Jason van Zyl <jason@maven.org> wrote:
> > >>
> > >> On 31 Mar 07, at 10:07 AM 31 Mar 07, Rapha=EBl Pi=E9roni wrote:
> > >>
> > >> > Hi here comes a new proposition for the future descriptor.
> > >> >
> > >> > I made it the most simpler i can think.
> > >> >
> > >> > Please comment it.
> > >> >
> > >>
> > >> I think it duplicates too much that's in the POM. The POM should be
> > >> the model that used for Archetype wherever possible and an ancillary
> > >> model should only be used where absolutely necessary. But as far as
> > >> any sources, resources and any filtering what is done in the POM for
> > >> the Archetype project is how the prototype generated from that
> > >> Archetype should end up.
> > >
> > > I don't think it is feasible in all cases to take out the information
> > > from the pom.
> >
> > I didn't say in all cases.
> >
> > > For example, the archetype author may want to put some
> > > resources into the specified package, while others have already the
> > > correct place. The pom does not allow to express this.
> >
> > Sorry, I don't grok this sentence. Give me an example.
>
> Some resources should have an absolute position in the classpath, an
> example being log4j.properties which is normally in the root of the
> classpath (default package).
> Other resources, like for example hibernate mappings, should be in the
> same package as the class they belong to.
> This means, in an archetype it must be possible to control which
> resource files get prefixed by the package and which don't. It is
> hard, if not impossible, to make the decision automatically.
>

exactly this is a showstopper for me in the current archetype when I
attempted to create an archetype for netbeans module development. I
need to place Bundle.properties and layer.xml file in resources into
the proper package.

Milos

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