OK, so I can close OPENNLP-40. About OPENNLP-9, do we send the email now or we should wait for the next release? If we send the email now, we will have to explain how to checkout the code and do a build.
Thanks William On Wed, Dec 15, 2010 at 5:06 PM, Jörn Kottmann <[email protected]> wrote: > Just close the issue when you know its done. > > Many use the resolved state to indicate that the issue > is done but still needs verification by the original > reporter. In the case of this issue, that is you. > > For OPENNLP-9 it is the one who reported the issue > in the first place on the user mailing list. > We should reply to this mail again and say that the issue > is resolved now and would like to get a confirmation that it > really solved his problem, afterward we can close it. > > Jörn > > > > On 12/15/10 7:43 PM, William Colen (JIRA) wrote: > >> [ >> https://issues.apache.org/jira/browse/OPENNLP-40?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel] >> >> William Colen resolved OPENNLP-40. >> ---------------------------------- >> >> Resolution: Fixed >> Fix Version/s: tools-1.5.1-incubating >> >> Fixed the code issues. As discussed we will not have automatic validation >> for now. >> >> Java compatibility level should be 1.5 >>> -------------------------------------- >>> >>> Key: OPENNLP-40 >>> URL: https://issues.apache.org/jira/browse/OPENNLP-40 >>> Project: OpenNLP >>> Issue Type: Bug >>> Components: Build, Packaging and Test >>> Affects Versions: tools-1.5.1-incubating, maxent-3.0.1-incubating >>> Reporter: William Colen >>> Assignee: William Colen >>> Fix For: tools-1.5.1-incubating >>> >>> Original Estimate: 2h >>> Time Spent: 0.5h >>> Remaining Estimate: 1.5h >>> >>> Some code is not compatible with Java 1.5 and we should keep the Java >>> compatibility level to 1.5. Need to fix the code and enforce the >>> compatibility level validation at build time. >>> >> >
