Mailing-List: contact dev-help@myfaces.apache.org; run by ezmlm
Precedence: bulk
Reply-To: "MyFaces Development" <dev@myfaces.apache.org>
Received-SPF: neutral (asf.osuosl.org: local policy)
Content-class: urn:content-classes:message
MIME-Version: 1.0
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: quoted-printable
Subject: RE: MyFaces portlet dependency
Date: Mon, 21 Nov 2005 11:36:14 -0600
Message-ID: 
 <C2CDEFBECFC9A14892BCCFB4C95F486802980367@EX-201.mail.navisite.com>
Thread-Topic: MyFaces portlet dependency
Thread-Index: AcXusl1KFTJuvGytTdCXX3uvq7ySiAAD4zKA
From: "Stan Silvert" <stan.silvert@jboss.com>
To: "MyFaces Development" <dev@myfaces.apache.org>

The portlet jar is only required for compiling.  If you are running a
MyFaces portlet application then the portlet API will be provided by the
portlet container.

Stan Silvert
JBoss, Inc.
ssilvert@jboss.com
callto://stansilvert

> -----Original Message-----
> From: Wendy Smoak [mailto:wsmoak@gmail.com]
> Sent: Monday, November 21, 2005 10:43 AM
> To: MyFaces Development
> Subject: MyFaces portlet dependency
>=20
> The pom in the (Maven 2) repository for MyFaces 1.1.0 lists the
> portlet api as required.
>
http://www.ibiblio.org/maven2/myfaces/myfaces-parent/1.1.0/myfaces-paren
t-
> 1.1.0.pom
>=20
> M2 has transitive dependencies, so this is going to cause the portlet
> api jar to get added to WEB-INF/lib for webapps that depend on
> MyFaces.
>=20
> Can someone please clarify when the portlet api is required?  I think
> it's required to build the implementation, but optional at runtime
> unless you're using certain classes.
>=20
> Adding a comment to build.xml would be nice, too-- that's what the
> Maven team is using to validate user suggestions about what is and is
> not required.
>=20
> http://jira.codehaus.org/browse/MEV-136
>=20
> Thanks,
> Wendy