Return-Path: Delivered-To: apmail-repository-archive@www.apache.org Received: (qmail 95534 invoked from network); 19 Jun 2006 14:02:19 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (209.237.227.199) by minotaur.apache.org with SMTP; 19 Jun 2006 14:02:19 -0000 Received: (qmail 27439 invoked by uid 500); 19 Jun 2006 14:02:18 -0000 Delivered-To: apmail-repository-archive@apache.org Received: (qmail 27398 invoked by uid 500); 19 Jun 2006 14:02:17 -0000 Mailing-List: contact repository-help@apache.org; run by ezmlm Precedence: bulk list-help: list-unsubscribe: List-Post: Reply-To: repository@apache.org List-Id: Delivered-To: mailing list repository@apache.org Delivered-To: moderator for repository@apache.org Received: (qmail 23135 invoked by uid 99); 19 Jun 2006 13:58:52 -0000 X-ASF-Spam-Status: No, hits=2.0 required=10.0 tests=RCVD_IN_SORBS_DUL X-Spam-Check-By: apache.org Received-SPF: neutral (asf.osuosl.org: local policy) Message-ID: <4496AD86.50606@apache.org> Date: Mon, 19 Jun 2006 06:58:30 -0700 From: Jeremy Boynes User-Agent: Mozilla Thunderbird 1.0.7-1.1.fc3 (X11/20050929) X-Accept-Language: en-us, en MIME-Version: 1.0 To: Brett Porter Cc: repository@apache.org Subject: Re: org.osoa in the snapshot repository References: <9e3862d80606162042m6a483170l1d1b293e2be03e1@mail.gmail.com> In-Reply-To: <9e3862d80606162042m6a483170l1d1b293e2be03e1@mail.gmail.com> Content-Type: text/plain; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit X-Virus-Checked: Checked by ClamAV on apache.org X-Spam-Rating: minotaur.apache.org 1.6.2 0/1000/N Brett Porter wrote: > Hi Jeremy, > > I see you deployed this: > > http://people.apache.org/maven-snapshot-repository/org/osoa/ > > Is this something Tuscany is producing? Why the org.osoa group ID? > Yes it is. It is the API jars for the specification (like the javax JARs) which are under a license that allows us to distribute them. > I can only assume it stands for something like open SOA, but > www.osoa.org doesn't resolve to anything. > That will be the website for the specification collaboration but they have had issues getting it up. Hopefully that will be resolved soon. -- Jeremy