FYI
I have just started preparing the core release 1.1.5.
See http://wiki.apache.org/myfaces/CoreRelease115#diary for details on
the proceedings.
--Manfred
On 2/2/07, Manfred Geiler [EMAIL PROTECTED] wrote:
FYI
I have just started preparing the core release 1.1.5.
See http://wiki.apache.org/myfaces/CoreRelease115#diary for details on
the proceedings.
--Manfred
I think you've just discovered that some things in the maven project
need
:)
Thank You
Paul Spencer
Manfred Geiler wrote:
FYI
I have just started preparing the core release 1.1.5.
See http://wiki.apache.org/myfaces/CoreRelease115#diary for details on
the proceedings.
--Manfred
We should release Core 1.1.5 soon, as it's needed for the next tomahawk release.
Therefore I tested the current trunk against Sun's TCK and fixed all
issues. MyFaces core is new 100 % compatible.
I have some time to prepare the release, but will need help from some
of you (eg. Wendy).
First of
there are some 1.1.5 issues with patch available status. Any chance
that these might be included?
Regards,
Erik-Berndt Scheper
-Oorspronkelijk bericht-
Van: Thomas Spiegl [mailto:[EMAIL PROTECTED]
Verzonden: woensdag 8 november 2006 15:40
Aan: MyFaces Development
Onderwerp: Core Release
On 11/8/06, Thomas Spiegl [EMAIL PROTECTED] wrote:
I have some time to prepare the release, but will need help from some
of you (eg. Wendy).
First of all I will create a branch for core 1.1.5 and shared 2.0.5
and start the release process.
We need to fix the license headers before branching,
Wendy,
I have submitted a patch to correct the license headers for one of the
core maven projects [1]. As soon as it is committed, I will create
patches for the remaining maven projects.
FYI: I have an internal project that is waiting on the release, so I am
motivated to provided a patch
On 11/8/06, Wendy Smoak [EMAIL PROTECTED] wrote:
Unless someone changed it, the trunk of Core (1.1.5-SNAPSHOT) still
depends on the 2.0.4 branch of shared, so if all goes well we can use
it for both Core and Tomahawk.
Martin changed the Shared dependency yesterday in r472050.
Hi Wendy!
If not, Core 1.1.5 can stay at Shared 2.0.4 and can use the same
Shared branch as Tomahawk 1.1.4.
Hmmm ... but shared will be copied into the core (or tomahawk)
distribution - there is no shared.jar, so I see no advantage of *not*
upgrading to the latest shared. This should not
On 11/8/06, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hmmm ... but shared will be copied into the core (or tomahawk)
distribution - there is no shared.jar, so I see no advantage of *not*
upgrading to the latest shared. This should not introduce a
incompatibility with any other release. At least
Yes, I will run the tests again.
On 11/9/06, Wendy Smoak [EMAIL PROTECTED] wrote:
On 11/8/06, Mario Ivankovits [EMAIL PROTECTED] wrote:
Hmmm ... but shared will be copied into the core (or tomahawk)
distribution - there is no shared.jar, so I see no advantage of *not*
upgrading to the
11 matches
Mail list logo
