Community
Participate
Working Groups
I call ajc -sourceroots <mydir> -outjar <my.jar> and an output file is created with a .jar extension, but it is not a valid jar file because there is no MANIFEST.MF file. I see that the text for ajc says: -outjar <file> put output classes in zip file <file> which might imply that it is supposed to be a zip file, but a parameter called - outjar which creates a zip file doesn't really make sense. If -outjar is used, the resulting file should be a valid jar file, i.e. with a META-INF/MANIFEST.MF file inside.
Matthew - another variation of the jar files and manifests problem, do you think you could take a look please? Thks :)
When using the “-outjar” option and not binary weaving a simple default manifest, similar to that produced by other tools like jar and ant, should be generated: Manifest-Version: 1.0 Created-By: AspectJ 1.2 If this is insuffiecent it can be replaced later by the user with: jar –mf …
Created attachment 8628 [details] Fix When -outjar specified a manfiest is either copied from the FIRST JAR in -injars/-inpath or one is created. If writing to a directory the manifest is copied but one is NOT created.
Fixed by patch contributed by Matthew.
