Mailing-List: contact dev-help@geronimo.apache.org; run by ezmlm
Precedence: bulk
Reply-To: dev@geronimo.apache.org
Received-SPF: pass (asf.osuosl.org: domain of eljotpl@gmail.com designates
 64.233.166.178 as permitted sender)
DomainKey-Signature: a=rsa-sha1; q=dns; c=nofws;
        s=beta; d=gmail.com;
        h=received:message-id:date:from:reply-to:sender:to:subject:in-reply-to:mime-version:content-type:content-transfer-encoding:content-disposition:references:x-google-sender-auth;
        b=pKD3iNwJCv8J4pVCeNvo35Mv3s4L0b3xoYNBqaLWpHKIBraCi4H52SvW0lMqcGLsWpm500vRmj430dfr7jbMWcL3wJqZJgWYW5qISskaJlcklZs9EMfzEdijbAFOIRWkbfGvfrmTLGmdb/JPbjv8GvaMjgptqx1qigPnqeXzttQ=
Message-ID: <1b5bfeb50608311612q26a6c5bdk91c7c9f8990aaba4@mail.gmail.com>
Date: Fri, 1 Sep 2006 01:12:15 +0200
From: "Jacek Laskowski" <jacek@laskowski.net.pl>
Reply-To: jacek@laskowski.net.pl
Sender: eljotpl@gmail.com
To: dev@geronimo.apache.org
Subject: Re: JPA Plugin patch
In-Reply-To: <939D6FCD-BC36-4AF2-B29C-B33323CE643F@objectstyle.org>
MIME-Version: 1.0
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
Content-Disposition: inline
References: <939D6FCD-BC36-4AF2-B29C-B33323CE643F@objectstyle.org>

On 8/31/06, Andrus Adamchik <andrus@objectstyle.org> wrote:
> Hi Aaron,
>
> finally got time to start poking around JPA plugin. I can compile it
> now, but it requires a patch below to build against the latest JPA
> spec. Not a big fan of SF issue tracker, so I simply put it on the web:
>
> http://people.apache.org/~aadamchik/jpa-plugin-patch.txt

Hi Aaron and Andrus,

The patch caught my attention and got me thinking about the plugin and
where it's being developed.

The first time I read it I thought why Andrus was asking that question
here (yet complaining about SF issue tracker) since the plugin itself
has been developed outside the project? (well, it's for the project,
but it's not part of it, right?). I meant to have asked the question
to Andrus, but then thought it's not him I should ask about it, but
Aaron who *seem* to have made it hard(er) to understand where people
should collaborate about stuff being developed outside, but still
relevant to Geronimo. For me, it should've been asked in the used
mailing list at most if not in the space it's being developed (in this
case, it's SF).

I think the question's already been asked, but will ask again since
the plugin has drawn more attention. Aaron, why can't the plugin
development be conducted here, in sandbox? Does it use a code not
allowed to be in the Geronimo repo?

Jacek

-- 
Jacek Laskowski
http://www.laskowski.net.pl