Great news! How about the current blocking issues for core 1.1.5?
Shouldn't they be fixed first?
E.g. https://issues.apache.org/jira/browse/MYFACES-1488 -- ASF source
header + copyright notice
And https://issues.apache.org/jira/browse/MYFACES-1479 -- SerialFactory
breaks portlet bridge
Also
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
