[Esapi-dev] ClassPath in 1.4 Manifest?
schallee at darkmist.net
Wed Sep 8 23:01:50 EDT 2010
I just noticed that we have the pom for 1.4 adding the ClassPath to MANIFEST.MF. We're not doing it for 2.0. Does anyone know anything about this? Other than spurious non-existent class path entry warnings from ant I'm not aware of this causing harm. Similarly, it's not too useful either.
I'm tempted to just remove this but perhaps there are reasons not to that I am not aware of.
-------------- next part --------------
A non-text attachment was scrubbed...
Name: not available
Size: 198 bytes
Desc: Digital signature
Url : https://lists.owasp.org/pipermail/esapi-dev/attachments/20100908/7d60b570/attachment.bin
More information about the Esapi-dev