On 30.12.2011 15:25, Jonas Maebe wrote:
On 29 Dec 2011, at 14:18, Sven Barth wrote:
On 29.12.2011 13:49, Jonas Maebe wrote:
On 28 Dec 2011, at 23:28, Sven Barth wrote:
1) as it seems to be a rather usual practice in Java, would it be possible to disable the
"Constructor should be public"
On 29 Dec 2011, at 14:18, Sven Barth wrote:
> On 29.12.2011 13:49, Jonas Maebe wrote:
>>
>> On 28 Dec 2011, at 23:28, Sven Barth wrote:
>>
>>> 1) as it seems to be a rather usual practice in Java, would it be possible
>>> to disable the "Constructor should be public" warnings if the target cpu
On Thu, Dec 29, 2011 at 10:49 AM, Jonas Maebe wrote:
> On 28 Dec 2011, at 23:28, Sven Barth wrote:
>
>> 1) as it seems to be a rather usual practice in Java, would it be possible
>> to disable the "Constructor should be public" warnings if the target cpu is
>> the JVM?
>
> Yes.
BTW, is there an
On 29.12.2011 13:49, Jonas Maebe wrote:
On 28 Dec 2011, at 23:28, Sven Barth wrote:
1) as it seems to be a rather usual practice in Java, would it be possible to disable the
"Constructor should be public" warnings if the target cpu is the JVM?
Yes.
This would be nice :)
2) in the code
On 28 Dec 2011, at 23:28, Sven Barth wrote:
> 1) as it seems to be a rather usual practice in Java, would it be possible to
> disable the "Constructor should be public" warnings if the target cpu is the
> JVM?
Yes.
> 2) in the code I converted the classes often seem to "reintroduce" methods
Hello Jonas!
Today I've converted a third party jar file using javapp, which went
without problems so far (I only need to convert another jar file,
because there is a dependency).
When compiling I noticed a few warnings though:
=== output ===
...
bukkit.inc(1668,5) Warning: Constructor shoul
