Alex Blewitt wrote:
> I've created Harmony 599
> (http://issues.apache.org/jira/browse/HARMONY-599) with a zip of what
> I've done so far. I don't believe that it has compile errors, and the
> tests run OK -- it's just if I depend on a method/class that's not yet
> available in the classpath build
> That wasn't what I meant. I meant excluding the single file(s) that
> cause the problem.
Well you /could/ but I would claim that is not very desirable, since we
would have to back out some changes in the existing built code for
pack200, convince each IDE that not all files in the src/main were
Geir Magnusson Jr skrev den 12-06-2006 20:10:
Would be a nifty feature - to tell your IDE to ignore a file...
Eclipse can do that. Right click on given Java file, and locate the
"Remove from Build Path" menu item.
Very handy in a pinch.
--
Thorbjørn
smime.p7s
Description: S/MIME Cr
Tim Ellison wrote:
> Geir Magnusson Jr wrote:
>> Tim Ellison wrote:
>>> Geir Magnusson Jr wrote:
Tim Ellison wrote:
> Since we want to keep ARCHIVE working throughout we can create a branch
> if you think the pack200 dev will be dangerous (I think we can handle it
> in-place, but
Geir Magnusson Jr wrote:
>
> Tim Ellison wrote:
>> Geir Magnusson Jr wrote:
>>> Tim Ellison wrote:
Since we want to keep ARCHIVE working throughout we can create a branch
if you think the pack200 dev will be dangerous (I think we can handle it
in-place, but whatever).
>>> Why a bran
Tim Ellison wrote:
> Geir Magnusson Jr wrote:
>> Tim Ellison wrote:
>>> Since we want to keep ARCHIVE working throughout we can create a branch
>>> if you think the pack200 dev will be dangerous (I think we can handle it
>>> in-place, but whatever).
>> Why a branch? can it just be out of the mai
Geir Magnusson Jr wrote:
>
> Tim Ellison wrote:
>> Since we want to keep ARCHIVE working throughout we can create a branch
>> if you think the pack200 dev will be dangerous (I think we can handle it
>> in-place, but whatever).
>
> Why a branch? can it just be out of the mainline build? IOW, exc
Tim Ellison wrote:
>
> Since we want to keep ARCHIVE working throughout we can create a branch
> if you think the pack200 dev will be dangerous (I think we can handle it
> in-place, but whatever).
Why a branch? can it just be out of the mainline build? IOW, excluded
for everyone else in the b
Alex Blewitt wrote:
> Well, I'm about half way through being able to read my HelloWorld.jar
> file; I've got the basic codec working, as well as decoding the
> constant pools that come at the front of an archive. There's still
> some missing bits -- for example, I don't handle the s=2 set of
> enco
1) Please put [classlib] or whatever sort token is appropriate.
2) To answer your question, yes, it would be very cool to post as JIRA
so people can see it and comment, and maybe get someone to help you.
I'd be happy to drop into svn somewhere so you and others can start
submitting patches agains
Well, I'm about half way through being able to read my HelloWorld.jar
file; I've got the basic codec working, as well as decoding the
constant pools that come at the front of an archive. There's still
some missing bits -- for example, I don't handle the s=2 set of
encodings (largely because I'm no
11 matches
Mail list logo
