|
If you were logged in you would be able to see more operations.
|
|
|
|
Original Estimate:
|
Unknown
|
Remaining Estimate:
|
Unknown
|
Time Spent:
|
Unknown
|
|
Environment:
|
Windows XP
|
|
| Build: |
6,141
|
| Severity: |
Low
|
|
Even with a META-INF/MANIFEST.MF in the source root the "Build Jars.." feature creates a default manifest file, unless "*.MF" is the resource patterns and the META-INF directory is in the source root. Not exactly intuitive. Better to explicitly indicate the manifest file somehow.
|
|
Description
|
Even with a META-INF/MANIFEST.MF in the source root the "Build Jars.." feature creates a default manifest file, unless "*.MF" is the resource patterns and the META-INF directory is in the source root. Not exactly intuitive. Better to explicitly indicate the manifest file somehow. |
Show » |
| There are no comments yet on this issue.
|
|
Bug
Open
Normal
Build Jar won't use a supplied manifest file in a module without unintuitive configuration