[
Date Prev][
Date Next][
Thread Prev][
Thread Next][
Date Index][
Thread Index]
[
List Home]
|
Re: [m2e-users] using a repository built by m2eclipse 0.12.1 with m2e 1.0 - invalid MANIFEST.MF
|
No, this is not expected. Both 0.12.1 and 1.0 are supposed to manage
maven local repository the same way and compatible with command line
maven. In fact, both 0.12.1 and 1.0 use exactly the same embeded maven
runtime (3.0.2).
--
Regards,
Igor
On 11-06-30 12:22 AM, Eugen Paraschiv wrote:
I have just upgraded to Eclipse 3.7 and m2e 1.0. I pointed m2e to my old
repository, downloaded with the previous m2eclipse 0.12.1. Now, some
dependencies are seen as invalid - the MANIFEST.MF file of the maven
downloaded jar is considered invalid: when opened, it displays:
/invalid LOC header (bad signature)/
What is more, m2e now completely ignores the entire jar - meaning it
doesn't show up in either the Eclipse index or in the dependency management.
As far as I could observe, these were all dependencies defined with a
runtime scope, but I'm not certain that is relevant (may be a coincidence).
If I delete the entire dependency from the repo by hand, and redownload
it again, it works fine.
Is it good practice to redownload the entire repository again with m2e 1.0?
Is this a known issue?
Thanks.
_______________________________________________
m2e-users mailing list
m2e-users@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/m2e-users
