Mailing-List: contact pluto-dev-help@portals.apache.org; run by ezmlm
Precedence: bulk
Reply-To: pluto-dev@portals.apache.org
Reply-To: pluto-dev@portals.apache.org
Received-SPF: neutral (herse.apache.org: local policy)
Message-ID: <461F64C4.1080405@apache.org>
Date: Fri, 13 Apr 2007 07:08:52 -0400
From: "David H. DeWolf" <ddewolf@apache.org>
User-Agent: Thunderbird 1.5.0.10 (Macintosh/20070221)
MIME-Version: 1.0
To: pluto-dev@portals.apache.org
Subject: Re: Adding JSR-286 API jar to a Maven repository
References: 
 <OF31C16A01.76418FC0-ON852572BC.00328E7E-852572BC.0034F074@hannaford.com>
In-Reply-To: 
 <OF31C16A01.76418FC0-ON852572BC.00328E7E-852572BC.0034F074@hannaford.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit

The biggest question is probably concerning licensing and if we're 
allowed to publish it.  This may not be an issue, but it's something we 
need to look into before we move forward.

CDoremus@hannaford.com wrote:
> 
> Hi all,
> 
> As part of the development of the JSR-286 Reference Implementation, a 
> copy of the portlet API jar (found here: 
> http://ipc658.inf-swt.uni-jena.de/spec/JSR%202.0%20API/lib/) needs to be 
> deployed to a Maven 2 repository. I was wondering which repository 
> should I use for this purpose? Should it be the pluto-staging or 
> apache.snapshot repository noted in the root pom.xml file or somewhere 
> else?
> 
> I also need to know what is the appropriate naming convention to use for 
> this file (i.e. the version element in the pom.xml). The current 
> portlet-2.0.jar is based on the Early Draft 2, Revision 13 of the 
> JSR-286 spec, so it seems like the version element value should be 
> something like '2.0-ED2-Rev13'. I'm not sure if we need to append 
> 'SNAPSHOT' to this version value. Please advise?
> 
> I am assuming that the groupId would be javax.portlet and the artifactId 
> would be portlet-api for this file as is now the case for the 
> portlet-1.0.jar file that contains the JSR-168 API.
> /Craig