On Thu, Sep 13, 2012 at 10:15 PM, Chris Graham <[email protected]> wrote: > :-) [Trying...too...resist...the...urge...to...say...use...eclipse...]
I used to. Anyway, luckily for us, the newer versions of the toolchain jar do not upset them, so I updated m-j-p's dependency. > > But seriously, a Zip file has "directory" entries in it. They can be a File > entry, that points to a file's contents, or a Directory entry. > > If the (empty) directory entries are not there, then most archive tools > simply go ahead and create the path and then the file anyway. > > Having the Directory entries there is not unique to maven's archiver. > > In short, IntelliJ need to fix their code. They should be able to handle > that situation. > > -Chris > > On Fri, Sep 14, 2012 at 2:18 AM, Benson Margulies > <[email protected]>wrote: > >> I had trouble working on the javadoc plugin in IntelliJ, and this >> response came back from their support person. >> >> What's special about this artifact? Should I see if making a new >> release will fix it? >> >> >> Quote starts here: >> >> This issue occurs because >> >> ...\.m2\repository\org\apache\maven\maven-toolchain\1.0\maven-toolchain-1.0.jar >> file has some weird archive format that IDEA cannot read: >> http://dl.dropbox.com/u/2752840/screens/snap2142-1347566987.png . >> >> If you look inside this jar with any external unpacker, you'll find >> that it contains empty file entries that match directories. >> So it's some Maven packaging issue that affects IDEA ability to >> properly read this jar. >> >> I don't think that we'll want to invest resources into fixing this >> issue, it should be rather fixed in the Maven repository. >> >> --------------------------------------------------------------------- >> To unsubscribe, e-mail: [email protected] >> For additional commands, e-mail: [email protected] >> >> --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
