That's right. I was already wondering why it stopped failing. I was always
hoping
that it would happen so that I could bug you :) Now you destroyed my hopes.
On Thu, 14 Jan 2010 14:52:14 -0300, Steve Ebersole
wrote:
>> even if this means that we increase the chance getting more
>> unreprod
On Thu, 2010-01-14 at 13:06 -0300, Hardy Ferentschik wrote:
> However, we should align the version string creation with whatever happens
> in Core,
I agree
> even if this means that we increase the chance getting more unreproducible
> build problems
> using Steve's magic plugin.
Btw when was
Good point.
On Thu, 2010-01-14 at 09:57 -0500, Chris Bredesen wrote:
> On 01/14/2010 05:34 AM, Emmanuel Bernard wrote:
> > Or simply remove them now that ANN and HEM are part of Core. The only
> > drawback I see is that HEM runs before Core but I guess we could
> > trigger the call to the static
I agree. As long as they are separate jars it makes sense to have different
version strings. It makes it easier to detect if someone has library
problems, eg
an old annotations jar in a shared server lib.
However, we should align the version string creation with whatever happens
in Core,
even
On 01/14/2010 05:34 AM, Emmanuel Bernard wrote:
> Or simply remove them now that ANN and HEM are part of Core. The only
> drawback I see is that HEM runs before Core but I guess we could
> trigger the call to the static version display from HEM to Core.
They're still separate jars though, right?
On Thu, 2010-01-14 at 10:17 -0300, Hardy Ferentschik wrote:
> I think we could do the same with the version string as we do in Validator
> ( and maybe Search, not sure ). There we
> read the version string from the MANIFEST file. The nice things about this
> is that the version in the MANIFEST
We should probably just remove them I think. Pretty annoying to see the
same version output over and over and over.
On Thu, 2010-01-14 at 11:34 +0100, Emmanuel Bernard wrote:
> Yeah!
> I've just noticed one glitch (except the NPE I managed to add ;) ). The
> Version numbers in the logs are not u
I think we could do the same with the version string as we do in Validator
( and maybe Search, not sure ). There we
read the version string from the MANIFEST file. The nice things about this
is that the version in the MANIFEST is
dynamically created during the build.
Generally there are quite
Yeah!
I've just noticed one glitch (except the NPE I managed to add ;) ). The Version
numbers in the logs are not updated for annotations and entity manager.
We should add them to the release procedure.
Or simply remove them now that ANN and HEM are part of Core. The only drawback
I see is that