6 Replies Latest reply on Jul 25, 2013 3:29 PM by twogee

TTALE-13 (support for RAR)

twogee Jul 22, 2013 5:51 AM

IMHO, RAR could be treated as a kind of WAR, couldn't it?

1. Re: TTALE-13 (support for RAR)

jesper.pedersen Jul 22, 2013 1:54 PM (in response to twogee)

Sort of, yes.

You can see packaging requirements here - http://www.ironjacamar.org/doc/userguide/1.1/en-US/html/ch05.html#packagingrequirements

Note, that a lot of .rar archives package .class files directly in the .rar/ - wrong, but what can you do ? Well, other than flag it. TTALE should consider these archives though.
Actions
2. Re: TTALE-13 (support for RAR)

twogee Jul 23, 2013 5:46 AM (in response to jesper.pedersen)

WarArchive does not care where it finds .class files, so it is suitable for the task.
Actions
3. Re: TTALE-13 (support for RAR)

jesper.pedersen Jul 23, 2013 3:21 PM (in response to twogee)

I meant that the archive checks should follow the classloader semantics defined in the various specs, and if possible take vendor extensions into account.
Actions
4. Re: TTALE-13 (support for RAR)

twogee Jul 25, 2013 7:06 AM (in response to jesper.pedersen)

Oops, I meant WarScanner in my previous post... which results in RAR being treated as a WarArchive.
What you discuss sounds like a suitable ClassLoaderStructure, which is of course relevant, but outside the scope from my point of view.
Actions
5. Re: TTALE-13 (support for RAR)

jesper.pedersen Jul 25, 2013 11:35 AM (in response to twogee)

Eh, what ? .rar files shouldn't be picked up by the WarScanner. The classloading semantics is different.
Actions
6. Re: TTALE-13 (support for RAR)

twogee Jul 25, 2013 3:29 PM (in response to jesper.pedersen)

Why not? AFAICS Scanners care only about archive structure, classloading semantics is of interest for Reports extending CLSReport, and by extension, for relevant ClassLoaderStructures.
Did I miss something?
Actions

Go to original post