ch to nullability is wrong, broken, and will never work
reliably from my POV.)
Cheers,
Simon
FO]
>
>
+1.
If jxpath doesn't use logging directly, but does via another optional
dependency then using dependencyManagement looks to be the right option
to set.
This isn't release critical IMO, because us
g on, where 1.0 or 1.1 or 2.3 or whatever can be chosen
depending on transient dependencies. Instead for a parent pom the
version to use has to be explicitly specified.
Regards,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Sun, 2007-08-19 at 00:45 +0200, Oliver Zeigermann wrote:
> Folks!
>
> I have finally managed to make some progress on my "navigation still
> points to jakarta" problem and it seems to be it is broken in all
> components.
Hmm, yes this appears to be true. I published the logging module
recently
h
caution. We don't want to bloat existing libs, ie add code that isn't
actively being used. So some of the ideas listed above might need some
justification before being accepted.
Math might be an exception, as implementing known algorithms seems a
useful thing - though I should le
tage" which handles
links differently (more like site:deploy does I think). Not sure if this
is what you are looking for..
http://maven.apache.org/plugins/maven-site-plugin/
Regards,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Tue, 2007-09-04 at 14:21 -0500, Paul Benedict wrote:
> The menu has erroneous links for its user guides (1.8 and 1.7). Both
> versions are pointing to the API docs instead.
The guide *is* the package documentation. Try scrolling down the page a
bit
-
he fact that it works for you under Windows
supports that.
So let's just ignore this problem and go ahead with the release..
Cheers, Simon
On Tue, 2007-10-09 at 22:22 +0200, Dennis Lundberg wrote:
> Simon,
>
> Is this in JIRA somewhere?
>
> I can run 'ant -f build-tes
saw - but we agreed that could just be ignored.
As you're more familiar with maven than me, I'd be very happy if you
volunteered to be the release manager..
Cheers,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTE
On Fri, 2007-10-19 at 11:42 -0400, James Carman wrote:
> When unit testing classes that are going to be remotified (it's a
> word), it's important to test that the parameters and return types can
> be serialized/deserialized properly. What if commons-proxy included a
> neat little helper class tha
ing?
There is a RELEASE-NOTES.txt file in the root dir (which is also in the
tgz file) which is much more useful.
Regards,
Simon
On Thu, 2007-10-25 at 22:16 +0200, Oliver Heger wrote:
> Hi,
>
> the artifacts look good to me. Building from source also worked fine.
>
> The only iss
ss this is something to do with either the maven commons-parent
pom, or the commons-build module, or a maven plugin update. Anyone have
any idea what the cause might be?
Thanks,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
27;t see the value of maintaining our own version of this page, so
> I'll go head and remove it from svn.
Yes, it would be nice to have a common version for all projects but
right now all I see is a very bare page with nothing close to the useful
info on the old page. It's not rele
ou put in to
get this release done.
Regards, Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
cubator the right place.
But out of curiosity, can you briefly describe what your component would
do?
Regards,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
To expand a bit:
install subversion (svn)
install maven 2.x (mvn)
svn co (the url above) cli
cd cli
mvn clean install
There will be a jarfile created in the "target" subdirectory.
Just about every java proj
ures, so be
careful with the meta-data for it. Digester is an ordinary library
though.
Regards,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
better.
I agree with Niall. I would have voted -1 on the logging release if I
had realised that the Notice/License files were auto-generated. I have
to kick myself for not having found time to check the logging release.
I have seen little positive comment on the remote-resources approach,
certainl
release; once it's ready upstream I'll try to make time to work on that.
If you could spare some time to help with maven2 stuff for Digester that
would be great.
Cheers, Simon
-
To unsubscribe, e-mail: [EMAIL PROTEC
rent
copyright holders, licensed under BSD licenses. Can the maven pom define
this information? I believe there is only one field. Or is the
fallback here to use a manual NOTICE file?
(2) If commons-bar then depends on commons-foo, what should be in the
NOTICE file?
Regards,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Thu, 2008-01-10 at 21:20 +0100, Dennis Lundberg wrote:
> Simon Kitching wrote:
> > Jochen Wiedmann <[EMAIL PROTECTED]> schrieb:
> >> On Jan 10, 2008 9:04 AM, Simon Kitching <[EMAIL PROTECTED]> wrote:
> >>
> >>> No. What I
sues either, and it may well
be that you are right and I am wrong. But if processes are to be
*changed*, then surely we need to validate the change before applying
it. Just making changes to the legal processes without any expert
opinion seems to be askin
ted.
And why would we ever care that some modules use version X of a plugin,
and some use version Y? If a module declares it needs version X, and
builds correctly with version X, then it seems *bad* to me to force an
unnecessary change via inheriting new settings from a parent pom.
So in short, I
On Sat, 2008-01-12 at 14:38 +0100, Dennis Lundberg wrote:
> simon wrote:
> > On Sat, 2008-01-12 at 00:20 +, Niall Pemberton wrote:
> >> On Jan 11, 2008 11:29 PM, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
> >>> Jochen Wiedmann wrote:
> >>>>
On Sat, 2008-01-12 at 20:35 +, Niall Pemberton wrote:
> Hi,
>
> Seems like discussion has concluded so trying again...
>
> The changes since the the last release of version 6 in summary:
>
> Changes to the pom.xml:
> - Configure NOTICE.txt and LICENSE.txt resources
> - add *hack* to put N
email would be something like:
[beanutils] add bean merging to BeanUtils.copyProperties (patch)
Regards,
Simon
On Fri, 2008-02-01 at 13:22 -0200, Rodrigo di Lorenzo Lopes wrote:
> Hi all!
>
> I'm Rodrigo di Lorenzo Lopes and I'd like to do some contributions to
> commons ap
ems right to me that
the same license should be attached to the source jar.
So unless there is an official statement from the board, or a qualified
lawyer says this is wrong, I'm +1 on releasing these sources jars, but
suggest that people be given a few days to check that they have the
right contents first.
Regards,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
e *already* released,
and then applying a different compression method (jar, not zip).
Regards,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
ng that? Or are you using something like
MEVENIDE?
I use eclipse and have no problem with any commons project I've worked
on so far, but only use eclipse:eclipse and not any other plugins.
Regards,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Yeah, and maven1 is pretty much dead. Providing Ant + maven2 should make
the vast majority of users happy.
On Sat, 2008-02-16 at 22:02 +0100, Emmanuel Bourg wrote:
> I agree, it's a burden to maintain otherwise.
>
> Emmanuel Bourg
>
>
> Oliver Heger a écrit :
> > With regards to the build files
g is possible, but what if there is
another change at some time in the future that is again so significant
that it is necessary to permit installation of old and new code in
parallel? [Well, by then Java might have a mechanism for handling this
built-in (like .Net), so it might be a moot point..]
Regards
rform
>
> This has worked OK for me for releasing the poms - but I haven't tried
> it on a component. The main thing I don't like about the release
> plugin is that every time you do release:prepare, it does 3 commits -
> which is alot of noise if you have several release candidates. Also
> I'm not quite sure how we go from stage rc --> actual release. I guess
> you have to tag and version as if it were the proper release - and
> delete the tag if a RC fails.
Yeah, the release plugin is "sub-optimal". It just occurred to me
recently that it probably does this in order to be able to support CVS
etc which cannot so easily branch, fix branch, tag. Instead it does "fix
trunk", tag, "refix trunk".
Regards,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
c version of trunk.
(e)
Update the scm link, from pointing at trunk to pointing at the tag dir.
Actually, I don't think this is very useful. Pointing at the trunk is
probably better, particularly when a release includes source jars
already.
(f)
Run all tests against the modified pom.
Well, if a "release branch" approach is used, then that happens
automatically when the release candidate code is built.
Regards,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
On Wed, 2008-04-23 at 09:30 +0100, sebb wrote:
> 2008/4/23 Torsten Curdt <[EMAIL PROTECTED]>:
> >
> > > Risks are mitigated to an arguably acceptable level by wrappering the
> > > entire release process at Apache around the point to point secure
> > > transport guarantee that signing is meant to p
the projects that use it, or are interested in using it.
There is a pretty low bar for committers on existing apache projects to
get commit access to commons; a major goal of commons is to centralise
code shared between apache projects exactly as you are proposing here.
But yes starting in "sandbox" is the usual path.
Regards,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
es.
Sounds good to me. I cannot think of any problems that might cause, it
does seem likely to result in a performance improvement, and it looks
safer.
Regards,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
. I know I don't usually put the password in there, but always
> forget about the username bit.
Yep. It defaults to your local username, which ain't good if your remote
server account is different.
Just for the record, you can also do
apach
e(
org.apache.lang.math.DoubleRange range,
double val);
Now doesn't loading that bundle in an OSGi app limit the entire app to
having just one common version of lang, just like a non-OSGi app would
be?
I'd love to be wrong - it would be cool to solve that probl
instead.
Sorry I don't have time to be more thorough; off on a trip tomorrow
morning for 2 days. And unfortunately I'm waiting for an svn password
reset so cannot commit just at the moment.
Cheers,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
va stuff.
Wasn't there some kind of agreement that if other non-java communities
wanted to form a commons then they could share the commons.apache.org
site? With the current website that is going to be pretty hard to do.
Regards,
Simon
---
I noticed that the user list hasn't been informed of the changes, so
have just sent a warning about the current changes. Hope that's ok with
you all.
When everything's settled we should sent a final update message to that
list...
Cheers,
Simon
Forwarded Message -
y exists.
My preference would have been to use commons-jakarta.apache.org (or
commons-java.apache.org if legal) from the start but that wasn't the
consensus.
Regards,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For
On Tue, 2007-07-31 at 08:26 -0700, Henri Yandell wrote:
> There are 11 bugs in EL, many of them pretty big and yet no activity
> since 2003-08-01.
>
> Anyone up for working on this?
Is this the EL interpreter used by Tomcat? If so, I would have expected
it to be maintained as part of normal tomca
mprove our
documentation about how to get Maven to work for us..
There is a nice maven manual available for download called "Better
Builds with Maven". See the documentation link on the maven.apache.org
site.
BTW, I see that Mergere.com (home of many maven developers) is now
De
han writing a complete maven1 buildfile. Most
components currently have maven1 builds because they were first
converted over before maven2 existed..
BTW, I see that Mergere.com (home of many maven developers) is now
DevZuz.com. That had me confused for a while..
Cheers,
Simon
code. The docs
have been updated in svn ready for our upcoming release that hasn't yet
happened.
We do *hope* to have a 1.1.1 release out in the next few weeks, though
progress isn't very rapid at the moment...
Regards,
Simon
---
a.apache.org/commons
to commons.apache.org. A few things have broken in the process,
including nightly builds. Sorry about that.
I suggest you check out the code and build it yourself. You'll need
maven 2.x then just run "mvn install"
P move a separate commits list for commons has
now been created.
However if you're proposing a separate commit list for every project I'd
be against that for a number of reasons. Why can't you just add a filter
if you only want certain topics?
Regards,
Simon
--
On Tue, 2007-08-07 at 11:23 +0200, simon wrote:
>
> Oops .. sorry Oleksandr. The latest release is 1.1.0.
>
> All the commons websites were recently regenerated (as part of the move
> to our new web address) and this was done from the TRUNK code. The docs
> have been updated in
if I can do anything that helps pushing beanutils2 across the
finish line!
Thanks a lot,
Simon
if OSGI related changes are wanted.
Simon
On Feb 7, 2018 5:10 AM, "Stefan Bodewig" wrote:
> On 2018-02-07, Jochen Wiedmann wrote:
>
> > On Wed, Feb 7, 2018 at 9:54 AM, Stefan Bodewig
> wrote:
>
> >> I know I asked before (I really am not an OSGi gu
?
I think it might be as easy as adding to the build.xml file.
Thanks again!
Simon
Hi Gary,
I added the Automatic Module Name and sent a PR request
(https://github.com/apache/commons-beanutils/pull/4) a while ago ... is there
anything I can do to help moving this forward?
Thanks,
Simon
sion should be bumped to match the most significant change in any
package in the bundle/artifact, so that maven version-range dependencies
don't break, but that ship has sunk.
Simon
p.s.
The reason I'd been making changes to commons-compress was to support
creating and using random access t
hat the annotated item
is really really deprecated.) It's not needed in this case, but is worth
thinking about when jdk9 is eventually released (latest schedule change :
from 7/27/2017 to 9/21/2017).
Simon
[1] https://github.com/apache/commons-lang/commit/7c19a1ff4c217
f0
n inlined), but could not be re-compiled.
I don't know why anyone would be doing this...
(CLIRR pre-dates string switches)
Simon
On Thu, Jun 8, 2017 at 5:10 PM, sebb wrote:
> On 8 June 2017 at 18:09, Gary Gregory wrote:
> > On Thu, Jun 8, 2017 at 9:57 AM, sebb wrote:
> >
&g
larly urgent, but if/when jdk9 is released, it might
be worth considering
Simon
ses@snarkive$ javac -version
*javac 1.8.0_131*
ses@snarkive$ javac -cp build/classes/main depup/src/EyeOfTheWeasel.java
*Note: depup/src/EyeOfTheWeasel.java uses or overrides a deprecated API.*
*Note: Recompile with
would require that the animal sniffer plugin be setup for components
> that do want to go that way. Doable if there is a sig file for the right
> Java version for that component.
>
> Gary
>
> On Jun 9, 2017 8:13 AM, "Simon Spero" wrote:
>
> > On Thu, Jun 8, 20
;M coming... and Jar
Hell's coming with me, you hear? **Jar Hell's coming with me!*
Simon
On Wed, Jun 7, 2017 at 5:02 PM, Gary Gregory wrote:
> On Wed, Jun 7, 2017 at 10:28 AM, Simon Spero wrote:
>
> > As Bertrand mentioned earlier, the bundle:baseline goal is built in t
have been the wrong response.
If you like, I can post a list of what the package version should have
been, assuming that every compatibility change was intentional, and
versioning was properly applied, for every bundle series under
org.apache.commons and commons-* that was on maven-central as of mid-may?
Simon
he commons parent verify stage seems like a
sensible move regardless. This should not replace japicmp, as they have
non-overlapping features. These goals should replace CLIRR, which is
obsolete (so obsolete that won't run under jdk-9 because jdk 1.5 bytecode
is no longer supported) .
Simon
p.
On Mon, Jun 12, 2017 at 10:53 AM, Matt Sicker wrote:
> I'd love to have a semantic versioning plugin like that which can suggest
> what the version number is for the entire project. Elm (programming
> language) has a tool like that, and it works rather well in practice (even
> though there are so
tional work after a subsequent api change is
https://github.com/apache/commons-compress/pull/27/commits/82405c13bd2688817108d3f2854387b3417a764d
Some of these changes can be lifted to the parent; the initial setup of
package-info.java @Version annotations requires some code.
Simon
¹ OK, I made the change
On Jun 14, 2017 4:28 AM, "Benedikt Ritter" wrote:
I’d like to have feedback for CLI-277 [1], especially whether it will
affect BC. Clirr is happy with this changes, to I suppose it is fine to
merge this?
[1] https://github.com/apache/commons-cli/pull/13 <
https://github.com/apache/commons-cli/pu
Oops -I missed that the method was already generic. Need bigger tablet/more
coffee / bigger caffeine tablet
On Jun 14, 2017 8:46 AM, "Simon Spero" wrote:
On Jun 14, 2017 4:28 AM, "Benedikt Ritter" wrote:
I’d like to have feedback for CLI-277 [1], especially whether it will
But BC, per initial response. I said I needed more coffee :)
On Wed, Jun 14, 2017 at 8:55 AM, Simon Spero wrote:
> Oops -I missed that the method was already generic. Need bigger
> tablet/more coffee / bigger caffeine tablet
>
>
> On Jun 14, 2017 8:46 AM, "Simon Spero&qu
ations that do this.
Like, um, javac :-)
Materializing these strings as possibly transient CharSequence's is
really convenient... until some method just has to have a String
Also, wouldn't some sort of low-space-overhead string storage be a good
fit for text?
Simon
[1] Spero,S. (2015)
not replying to an email from him (on dev) that I'd missed because of
coveralls) .
So +1.
Also, I need to reply to that email :)
Simon
On Jun 19, 2017 6:33 AM, "Stefan Bodewig" wrote:
Hi all
apart from dev@ and user@ we've got three lists that have been created
for specific n
es to whitespace, and which
intellij and I haven't figured the pattern to.
Checkstyle as plugin is still annoying, but only when we disagree :)
Simon
On Jun 18, 2017 2:33 AM, "PascalSchumacher" wrote:
Github user PascalSchumacher commented on the issue:
https://github.com/apac
On Jun 19, 2017 9:56 AM, "Stefan Bodewig" wrote:
On 2017-06-19, Simon Spero wrote:
with all parenteses properly nested, wow ;-)
No need to apologize, really.
(apply #'append '((not) (a problem)))
Hudkins is alive!
On Tue, Jun 20, 2017 at 12:49 AM, Dave Fisher wrote:
> Check with Infra weird errors are happening.
>
> Regards,
> Dave
>
> Sent from my iPhone
>
> > On Jun 19, 2017, at 8:53 PM, Stefan Bodewig wrote:
> >
> >> On 2017-06-19, Gary Gregory wrote:
> >>
> >> Is it just me or have
On Tue, Jun 20, 2017 at 10:18 AM, Stefan Bodewig wrote:
>
> Interesting. This means OSGi only provides a way for consumers to say
> which version of an API they want, but not which implementation. This means
> as a consumer you can't say "I want version 1.19 of Compress because I know
> it contai
but
having all the format fixes in a single commit is a lot better than having
them mixed in with real changes.
Simon
P. S.
I prefer the builtin /google_checks.xml styleguide to the older sun_checks,
partly because it's more up to date, and partly because Google provides
native ide configur
COMPRESS-413 has some examples which include:
- Switching to the trusty container, which doesn't require installing as
many updates.
- Use only two JDKs: openjdk7 and openjdk8.
- JDK 7 is obsolete -
- Oracle EOL'ed JDK7 over two years ago; openjdk7 occasionally gets
pa
Java 9 you can get rid of the NoPS with the spin-wait hinting.
Simon
under plain old JDK 8; much of
the rest is subsumed by various functional and/or reactive libraries (of
which there are quite a few). AOL's Cyclops [1] bridges a bunch of these
(e.g. [2],[3].[4]). Is there anything that isn't provided for in cyclops or
one of the things it bridges?
Simon
maven-compiler-plugin [4] via a
element in the plugin configuration, or by settting the property
*maven.compiler.release* .
Simon
[1] https://bugs.openjdk.java.net/browse/JDK-8011044
[2]
http://openjdk.java.net/projects/jigsaw/spec/minutes/2017-05-18#AutomaticModuleNames--ModuleNameInManifest
[3]
It doesn't work. :-)
More specifically, it doesn't work because coveralls is trying to use JAXB,
which is not available by default in JDK9. (It ships. It's just not
available without command line arguments.)
The coveralls plugin is using JAXB for a single static method, to convert a
byte[] dige
It was failing when I got here officer
On Jul 4, 2017 1:46 PM, "Pascal Schumacher"
wrote:
> Am 04.07.2017 um 16:17 schrieb Simon Spero:
>
>> It doesn't work. :-)
>>
>> More specifically, it doesn't work because coveralls is trying to use
>>
hide the conspiracy than in the heartblood of the conspiracy
theorists.
All hail Eris!
Simon // Ok, it could spam, but that just doesn't seem as plausible.
Is this jdk 8 vs. java SDK 8? The oracle code picked up some fairly big
changes along the way that aren't present in the IBM library. (jdk 9 is
really different from both. I haven't seen what the IBM Java 9 is like
yet).
I will see if anything looks blatantly obvious.
Simon
On Jul
Since it's an interface, I could change it to IHasACharset?
Or If you prefer I could rename it to YouGiveLove? (Lucky Millenials- you
aren't headsonged)
The name follows a pattern for interfaces of this sort, which are basically
retrofit markers for the presence of property, (with associated ge
On Jul 16, 2017 11:49 AM, "Matt Sicker" wrote:
C quality somewhat depends on which version of C you're trying to remain
compatible with (I'm guessing C89 due to Windows, though I could be wrong).
Valgrind and other tracing tools are typically used.
Valgrind is a default choice (though then you
s could be provided to support populating a Map from an input source
containing contents formatted as specified in j.u.Properties.
So, io with a touch of codec?
Simon
remaining synchronized. Everything gets delegated to the chm.
Still full of unchecked goodness.
And a great example of how sometimes inheritance is so useless you just
compose and delegate anyway.
Simon
Class file format is not treated as a breaking change under most versioning
approaches, including the JLS.
The checkers I looked at that reported on class file format changes
consider it a micro level version change (+0.0.1)
The past few major version bumps for projects I've worked happened to
pplier
function (e.g. CardinalDirection::values).
You could use a cache in the RNG, keyed by the class, but that's still
going to be a bit expensive in the middle of a tight loop.
Simon
Simon
tes of the armistice talks.
jigsaw modules are pretty useless for most of Commons (consumers pretty
much have to shade dependencies). [ subliminal whisper about benefits of
having correct OSGI headers]
Simon
On Aug 8, 2017 11:08 AM, "Jörg Schaible"
wrote:
> Hi,
>
> Gilles wrote
urrent code as almost an implementation
module, define a separate API module, and add extra interfaces and
alternate implementations to support the target use case (mutable
records, streams, reactivex, transform functions or what have you).
Simon
Camel * Camel = Camel
Let Dunhill + Dunhill = Dunhill,
Dunhill + Camel = Camel,
Camel + Dunhill = Camel,
Camel + Camel = Dunhill
Then is a Field, but of brands of cigarette.
So I vote Camel or Dunhill depending.
Simon
uction use, etc).
Simon
On Oct 9, 2017 5:21 PM, "Rob Tompkins" wrote:
Hey all,
At my day job we saw a 60% performance improvement (cpu utilization)
between 1.8.0_40 and 1.8.0_121, and I was wondering if anyone else out
there has seen anything like that before or if anyone might know what co
es (and possibly not
even all of those), it's essy to use a static map (which can be pretty much
generated from jmod/jdep).
Simon
[1] A module can only appear in the modpath once. A package can only come
from one module. If an application uses multiple third party dependencies,
which us
(e.g. return hasDataDescriptor).
2. Better handling when ZipArchiveInputStream is used to read such streams.
Currently it silently fails when this happens when if hits an invalid
LFH_SIG by returning null.
Cheers
Simon
of error occurs
but indicate the error somehow. There might be issues here (I am no zip
expert) but I would be worried about false errors being reported.
Simon
On 11/03/2010 13:11, "Stefan Bodewig" wrote:
> On 2010-03-10, Simon Tyler wrote:
>
>> Do we have a date ye
The file called Word.xps at:
http://www.wssdemo.com/XPS/Forms/AllItems.aspx
exhibits the problem.
You are entirely correct the entry is STORED so COMPRESS-100 does the trick
for me.
Simon
On 12/03/2010 15:17, "Stefan Bodewig" wrote:
> On 2010-03-12, Simon Tyler wrot
r it
changed or not.
Regards,
Simon
-
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
Luc Maisonobe schrieb:
Maven also failed with a fatal error trying to compare with version
1.8.0-BETA which it did not found (I'm not even sure it tried to
download it). I fixed this again by downloading and installing both the
pom and jar file manually.
This is a known bug with the clirr p
p and
IdentityHashSet classes as well, given that LANG still targets Java
1.3.
WDYT?
And do these classes need a new package, or would the top-level package be OK?
No opinion.
Cheers,
Simon
-
To unsubscribe, e-mail: [EMAIL PROT
sebb schrieb:
On 16/09/2008, Simon Kitching <[EMAIL PROTECTED]> wrote:
One other concern is regarding garbage collection. From a brief look at the
code, this thread-local registry object contains a set of Integer hashcodes.
With this change, the set will now contain real hard referen
sebb schrieb:
On 16/09/2008, Jörg Schaible <[EMAIL PROTECTED]> wrote:
sebb wrote:
> On 16/09/2008, Simon Kitching <[EMAIL PROTECTED]> wrote:
[snip]
It's not quite clear to me why a threadlocal is being used here. I'm
>> guessing it is for
1 - 100 of 132 matches
Mail list logo
