You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@beehive.apache.org by Carlin Rogers <ca...@gmail.com> on 2007/01/24 01:58:05 UTC
Update the netui-jsf sample build files to support newer MyFaces 1.1.X
I'd like to update the netui-jsf sample build.xml and build.properties
files to support building with newer 1.1.x versions of MyFaces. There
are a couple of issues that I've noticed with the netui-jsf sample.
First, it assumes a file naming convention for MyFaces jars that is no
longer used (since 1.1.2). The build properties file only uses a
directory location and assumes the jar names will not change from
release to release of the JSF implementations. Also, later 1.1.x
releases of MyFaces are dependent on commons-lang.jar.
Does anyone mind if I modify the build.xml and build.properties in the
netui-jsf sample to support newer 1.1.x versions of MyFaces?
NOTE - this is not an effort to test and support the 1.2 version of
MyFaces and the JSF 1.2 spec. I can kick off a separate thread about
JSF 1.2 support (and JEE 5) a little later.
Also, to make sure the distribution builds correctly with the sample,
I will update the netui/external/jsf dir to include MyFaces 1.1.4. The
current version we use for builds and tests is an old MyFaces 1.0.9.
Sound OK?
Thanks,
Carlin
Re: Update the netui-jsf sample build files to support newer MyFaces 1.1.X
Posted by Carlin Rogers <ca...@gmail.com>.
Hey Eddie,
Sounds good. No, at this time I do not see any code changes. Hopefully
there wouldn't be any as I think the code is good at integrating with
the JSF spec API and not the implementation. I'll make sure the jsfWeb
test app runs fine first though. Thanks for the input.
Carlin
On 1/24/07, Eddie O'Neil <ek...@gmail.com> wrote:
> Carlin--
>
> Could we just update to MyFaces 1.1.4 and remove the 1.0.x bits from
> the tree entirely? Unless we're going to use them for something, it
> seems like this is the easiest way forward.
>
> Are there code changes associated with updating to 1.1.4?
>
> Eddie
>
>
> On 1/23/07, Carlin Rogers <ca...@gmail.com> wrote:
> > Eddie,
> >
> > Yes, to update to a newer release. I will leave the older version in
> > the tree. We could still build/test against that if desired. The
> > reason I was going to update and test the build against the newer
> > version is that MyFaces now has a dependency on commons-lang.jar. The
> > changes to the build.xml would check for availability of a
> > commons-lang.jar property in a MyFaces build (target 'build-myfaces')
> > and copy the jar appropriately. We don't ship the MyFaces jars so I
> > don't have to do this but thought it might help.
> >
> > Thanks,
> > Carlin
> >
> > On 1/23/07, Eddie O'Neil <ek...@gmail.com> wrote:
> > > Carlin--
> > >
> > > These changes sound fine to me. To be clear, is the reason to
> > > update MyFaces just to use a newer release?
> > >
> > > With respect to JSF 1.2, MyFaces hasn't delivered official release
> > > that supports this version of the specification; according to their
> > > most recent status report, this should be done sometime in the first
> > > quarter, though testing could be done against builds -- assuming they
> > > exist. :)
> > >
> > > A discussion on JEE 5 support would be great!
> > >
> > > Eddie
> > >
> > >
> > > On 1/23/07, Carlin Rogers <ca...@gmail.com> wrote:
> > > > I'd like to update the netui-jsf sample build.xml and build.properties
> > > > files to support building with newer 1.1.x versions of MyFaces. There
> > > > are a couple of issues that I've noticed with the netui-jsf sample.
> > > > First, it assumes a file naming convention for MyFaces jars that is no
> > > > longer used (since 1.1.2). The build properties file only uses a
> > > > directory location and assumes the jar names will not change from
> > > > release to release of the JSF implementations. Also, later 1.1.x
> > > > releases of MyFaces are dependent on commons-lang.jar.
> > > >
> > > > Does anyone mind if I modify the build.xml and build.properties in the
> > > > netui-jsf sample to support newer 1.1.x versions of MyFaces?
> > > >
> > > > NOTE - this is not an effort to test and support the 1.2 version of
> > > > MyFaces and the JSF 1.2 spec. I can kick off a separate thread about
> > > > JSF 1.2 support (and JEE 5) a little later.
> > > >
> > > > Also, to make sure the distribution builds correctly with the sample,
> > > > I will update the netui/external/jsf dir to include MyFaces 1.1.4. The
> > > > current version we use for builds and tests is an old MyFaces 1.0.9.
> > > >
> > > > Sound OK?
> > > >
> > > > Thanks,
> > > > Carlin
> > > >
> > >
> >
>
Re: Update the netui-jsf sample build files to support newer MyFaces 1.1.X
Posted by Eddie O'Neil <ek...@gmail.com>.
Carlin--
Could we just update to MyFaces 1.1.4 and remove the 1.0.x bits from
the tree entirely? Unless we're going to use them for something, it
seems like this is the easiest way forward.
Are there code changes associated with updating to 1.1.4?
Eddie
On 1/23/07, Carlin Rogers <ca...@gmail.com> wrote:
> Eddie,
>
> Yes, to update to a newer release. I will leave the older version in
> the tree. We could still build/test against that if desired. The
> reason I was going to update and test the build against the newer
> version is that MyFaces now has a dependency on commons-lang.jar. The
> changes to the build.xml would check for availability of a
> commons-lang.jar property in a MyFaces build (target 'build-myfaces')
> and copy the jar appropriately. We don't ship the MyFaces jars so I
> don't have to do this but thought it might help.
>
> Thanks,
> Carlin
>
> On 1/23/07, Eddie O'Neil <ek...@gmail.com> wrote:
> > Carlin--
> >
> > These changes sound fine to me. To be clear, is the reason to
> > update MyFaces just to use a newer release?
> >
> > With respect to JSF 1.2, MyFaces hasn't delivered official release
> > that supports this version of the specification; according to their
> > most recent status report, this should be done sometime in the first
> > quarter, though testing could be done against builds -- assuming they
> > exist. :)
> >
> > A discussion on JEE 5 support would be great!
> >
> > Eddie
> >
> >
> > On 1/23/07, Carlin Rogers <ca...@gmail.com> wrote:
> > > I'd like to update the netui-jsf sample build.xml and build.properties
> > > files to support building with newer 1.1.x versions of MyFaces. There
> > > are a couple of issues that I've noticed with the netui-jsf sample.
> > > First, it assumes a file naming convention for MyFaces jars that is no
> > > longer used (since 1.1.2). The build properties file only uses a
> > > directory location and assumes the jar names will not change from
> > > release to release of the JSF implementations. Also, later 1.1.x
> > > releases of MyFaces are dependent on commons-lang.jar.
> > >
> > > Does anyone mind if I modify the build.xml and build.properties in the
> > > netui-jsf sample to support newer 1.1.x versions of MyFaces?
> > >
> > > NOTE - this is not an effort to test and support the 1.2 version of
> > > MyFaces and the JSF 1.2 spec. I can kick off a separate thread about
> > > JSF 1.2 support (and JEE 5) a little later.
> > >
> > > Also, to make sure the distribution builds correctly with the sample,
> > > I will update the netui/external/jsf dir to include MyFaces 1.1.4. The
> > > current version we use for builds and tests is an old MyFaces 1.0.9.
> > >
> > > Sound OK?
> > >
> > > Thanks,
> > > Carlin
> > >
> >
>
Re: Update the netui-jsf sample build files to support newer MyFaces 1.1.X
Posted by Carlin Rogers <ca...@gmail.com>.
Eddie,
Yes, to update to a newer release. I will leave the older version in
the tree. We could still build/test against that if desired. The
reason I was going to update and test the build against the newer
version is that MyFaces now has a dependency on commons-lang.jar. The
changes to the build.xml would check for availability of a
commons-lang.jar property in a MyFaces build (target 'build-myfaces')
and copy the jar appropriately. We don't ship the MyFaces jars so I
don't have to do this but thought it might help.
Thanks,
Carlin
On 1/23/07, Eddie O'Neil <ek...@gmail.com> wrote:
> Carlin--
>
> These changes sound fine to me. To be clear, is the reason to
> update MyFaces just to use a newer release?
>
> With respect to JSF 1.2, MyFaces hasn't delivered official release
> that supports this version of the specification; according to their
> most recent status report, this should be done sometime in the first
> quarter, though testing could be done against builds -- assuming they
> exist. :)
>
> A discussion on JEE 5 support would be great!
>
> Eddie
>
>
> On 1/23/07, Carlin Rogers <ca...@gmail.com> wrote:
> > I'd like to update the netui-jsf sample build.xml and build.properties
> > files to support building with newer 1.1.x versions of MyFaces. There
> > are a couple of issues that I've noticed with the netui-jsf sample.
> > First, it assumes a file naming convention for MyFaces jars that is no
> > longer used (since 1.1.2). The build properties file only uses a
> > directory location and assumes the jar names will not change from
> > release to release of the JSF implementations. Also, later 1.1.x
> > releases of MyFaces are dependent on commons-lang.jar.
> >
> > Does anyone mind if I modify the build.xml and build.properties in the
> > netui-jsf sample to support newer 1.1.x versions of MyFaces?
> >
> > NOTE - this is not an effort to test and support the 1.2 version of
> > MyFaces and the JSF 1.2 spec. I can kick off a separate thread about
> > JSF 1.2 support (and JEE 5) a little later.
> >
> > Also, to make sure the distribution builds correctly with the sample,
> > I will update the netui/external/jsf dir to include MyFaces 1.1.4. The
> > current version we use for builds and tests is an old MyFaces 1.0.9.
> >
> > Sound OK?
> >
> > Thanks,
> > Carlin
> >
>
Re: Update the netui-jsf sample build files to support newer MyFaces 1.1.X
Posted by Eddie O'Neil <ek...@gmail.com>.
Carlin--
These changes sound fine to me. To be clear, is the reason to
update MyFaces just to use a newer release?
With respect to JSF 1.2, MyFaces hasn't delivered official release
that supports this version of the specification; according to their
most recent status report, this should be done sometime in the first
quarter, though testing could be done against builds -- assuming they
exist. :)
A discussion on JEE 5 support would be great!
Eddie
On 1/23/07, Carlin Rogers <ca...@gmail.com> wrote:
> I'd like to update the netui-jsf sample build.xml and build.properties
> files to support building with newer 1.1.x versions of MyFaces. There
> are a couple of issues that I've noticed with the netui-jsf sample.
> First, it assumes a file naming convention for MyFaces jars that is no
> longer used (since 1.1.2). The build properties file only uses a
> directory location and assumes the jar names will not change from
> release to release of the JSF implementations. Also, later 1.1.x
> releases of MyFaces are dependent on commons-lang.jar.
>
> Does anyone mind if I modify the build.xml and build.properties in the
> netui-jsf sample to support newer 1.1.x versions of MyFaces?
>
> NOTE - this is not an effort to test and support the 1.2 version of
> MyFaces and the JSF 1.2 spec. I can kick off a separate thread about
> JSF 1.2 support (and JEE 5) a little later.
>
> Also, to make sure the distribution builds correctly with the sample,
> I will update the netui/external/jsf dir to include MyFaces 1.1.4. The
> current version we use for builds and tests is an old MyFaces 1.0.9.
>
> Sound OK?
>
> Thanks,
> Carlin
>