[
https://issues.apache.org/jira/browse/OFBIZ-4213?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=13006203#comment-13006203
]
Marco Risaliti commented on OFBIZ-4213:
---------------------------------------
Hi Jacques,
I have seen that it's due to the element Class-path inside the manifest.mf fo
the jars.
For example inside barcode4j-fop-ext-complete-2.0.jar there is the manifest.jar
with the element Class-path set to ${manifest-classpath}.
So we could avoid it without insert those jar specified in the manifest.mf but
I having no more times to dig it.
Thanks
Marco
> Add <compilerarg value="-Xlint"/> to all build targets
> ------------------------------------------------------
>
> Key: OFBIZ-4213
> URL: https://issues.apache.org/jira/browse/OFBIZ-4213
> Project: OFBiz
> Issue Type: Improvement
> Components: ALL COMPONENTS
> Affects Versions: SVN trunk
> Reporter: Jacques Le Roux
> Assignee: Jacques Le Roux
> Priority: Trivial
> Attachments: OFBIZ-4213_Add compilerarg value=-Xlint.patch
>
>
> THe idea is to use <compilerarg value="-Xlint"/> and to not care about
> Eclipse, if some want to fix warning messages there, perfect, else we will
> simply forget about them
> I will wait to commit that we remove most, if not all, of the warning
> messages in order to not clutter the compile log with them
--
This message is automatically generated by JIRA.
For more information on JIRA, see: http://www.atlassian.com/software/jira
