, build it on F17
(or rawhide) and fire off a Hibernate 4 build?
I think we should just stick the issues we find into bz 809950, unless
they are Hibernate 4 specific.
On 07/05/2012 09:55 AM, Dan Allen wrote:
On Thu, Jul 5, 2012 at 3:46 AM, Aleksandar Kurtakov
<akurtako(a)redhat.com <mailto:email@example.com>> wrote:
One more project lost for us thanks to gradle :(
There's no doubt, the adoption of Gradle has slowed down updates until
the packaging is complete. But, software is going to change, that's
just the nature of it. Nothing has been lost, we just have to rise
together to the new challenge. We could have said the same thing about
Maven builds before you all did the innovative work of integrating
that into rpmbuild.
It's becoming very clear to me, though, that we need to get more
information out there (this list is as good as any) on the status of
the Gradle packaging. That will help everyone set schedules and
expectations better. Let's frame it as a challenge, not a problem.
Principal Software Engineer, Red Hat | Author of Seam in Action
Registered Linux User #231597
java-devel mailing list