No problem, let's wait new version.
2006/10/24, Nathan Beyer <[EMAIL PROTECTED]>:
Most of the concurrent code warnings go away with newer versions (from
the concurrency scm), but those newer versions also have Java 6 API
dependencies, so at the moment we'll have to stick with what we have.
-Nat
Most of the concurrent code warnings go away with newer versions (from
the concurrency scm), but those newer versions also have Java 6 API
dependencies, so at the moment we'll have to stick with what we have.
-Nathan
On 10/24/06, Denis Kishenko <[EMAIL PROTECTED]> wrote:
Sorry, I skiped this ma
Sorry, I skiped this mail, too long topic name =)
It's ok to rollback.
Actually concurrent module has a lot of warnings and I have started
fix them. I have some suggestion about generic warnings. Is Doug Lea
subscribed on dev list?
2006/10/20, Mark Hindess <[EMAIL PROTECTED]>:
On 20 October 2
that's not a bad idea...
Nathan Beyer wrote:
This can be controlled a bit more. An svn:externals link can point to
a specific revision, not just a SVN URL. This way the working copy
download has to be changed at the point of link.
-Nathan
On 10/21/06, Geir Magnusson Jr. <[EMAIL PROTECTED]> wro
This can be controlled a bit more. An svn:externals link can point to
a specific revision, not just a SVN URL. This way the working copy
download has to be changed at the point of link.
-Nathan
On 10/21/06, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote:
Great - I wanted to make sure. I was aski
Great - I wanted to make sure. I was asking based on a cursory glance.
geir
Nathan Beyer wrote:
They are in 'standard' and do use 'links' (svn:externals). Check out
the full path of the original commit message. Using svn:externals just
makes it seem like it's in 'extended', but that's just in
On 21/10/06, Nathan Beyer <[EMAIL PROTECTED]> wrote:
They are in 'standard' and do use 'links' (svn:externals). Check out
the full path of the original commit message. Using svn:externals just
makes it seem like it's in 'extended', but that's just in your working
copy.
Agreed -- there is no pro
They are in 'standard' and do use 'links' (svn:externals). Check out
the full path of the original commit message. Using svn:externals just
makes it seem like it's in 'extended', but that's just in your working
copy.
-Nathan
On 10/20/06, Geir Magnusson Jr. <[EMAIL PROTECTED]> wrote:
Thanks for
Thanks for bringing this up. I did a classlib update this morning, and
saw these files change, and I was confused.
Why do we have the files here anyway? I thought we were going to keep
in /standard and use links?
geir
Tim Ellison wrote:
Mark,
I suggest that this is rolled back since it is
On 20 October 2006 at 17:21, Tim Ellison <[EMAIL PROTECTED]> wrote:
>
> Mark,
>
> I suggest that this is rolled back since it is modifying the
> concurrency code in our 'standard' SVN area that we aim to keep in
> close sync with Doug's repository.
Agreed. I thought about this after doing it th
Mark,
I suggest that this is rolled back since it is modifying the concurrency
code in our 'standard' SVN area that we aim to keep in close sync with
Doug's repository.
Perhaps we can offer the patch to that community, and/or set up local
compiler options to hide the warnings in this module.
Reg
11 matches
Mail list logo
