[jira] [Commented] (PIVOT-850) Fail to take input characters other than English in Mac Lion

[ https://issues.apache.org/jira/browse/PIVOT-850?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16015075#comment-16015075 ] Roger Whitcomb commented on PIVOT-850: -- First phase of Input Method Editor support in

Jenkins build is back to normal : Pivot-trunk on Java 7 #1232

See

[jira] [Commented] (PIVOT-997) Deprecate (and eventually remove) the WTKListenerList class, which is currently empty

[ https://issues.apache.org/jira/browse/PIVOT-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16014607#comment-16014607 ] Roger Whitcomb commented on PIVOT-997: -- Also remove inadvertent changes for TextInputM

Build failed in Jenkins: Pivot-trunk on Java 7 #1231

See Changes: [rwhitcomb] PIVOT-997: Another round of changing WTKListenerList to just ListenerList as part of the effort to deprecate and then remove this now empty class. [rwhitcomb] PIVOT-997: An

[jira] [Commented] (PIVOT-997) Deprecate (and eventually remove) the WTKListenerList class, which is currently empty

[ https://issues.apache.org/jira/browse/PIVOT-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16014555#comment-16014555 ] Roger Whitcomb commented on PIVOT-997: -- Final set of changes in "trunk". Now all of t

[jira] [Commented] (PIVOT-997) Deprecate (and eventually remove) the WTKListenerList class, which is currently empty

[ https://issues.apache.org/jira/browse/PIVOT-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16014544#comment-16014544 ] Roger Whitcomb commented on PIVOT-997: -- Second round of changes in "trunk": Sending

Re: [jira] [Commented] (PIVOT-997) Deprecate (and eventually remove) the WTKListenerList class, which is currently empty

Ugh! Mistakenly added "TextInputMethodListener.java" in here -- this is meant for the other set of changes related to Input Method Editor support. Will remove that (for now). On 5/17/17 10:30 AM, Roger Whitcomb (JIRA) wrote: [ https://issues.apache.org/jira/browse/PIVOT-997?page=co

[jira] [Commented] (PIVOT-997) Deprecate (and eventually remove) the WTKListenerList class, which is currently empty

[ https://issues.apache.org/jira/browse/PIVOT-997?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=16014455#comment-16014455 ] Roger Whitcomb commented on PIVOT-997: -- First set of changes in "trunk": Sending

[jira] [Created] (PIVOT-997) Deprecate (and eventually remove) the WTKListenerList class, which is currently empty

Roger Whitcomb created PIVOT-997: Summary: Deprecate (and eventually remove) the WTKListenerList class, which is currently empty Key: PIVOT-997 URL: https://issues.apache.org/jira/browse/PIVOT-997 Pro

RE: Jenkins build is back to normal : Pivot-maintenance on Java 8 #1120

The other thing is that building the 2.0.x branch with Java 8 gives 100s of Javadoc warnings, which are also not really helpful. I have fixed all these in "trunk". But, if we're going to do a Jenkins build for 2.0.x (and I think we should, since is the current release branch), then it should b

RE: Any idea why we have WTKListenerList

If I mark the class as deprecated, then we get 100s of warnings in the build. I'd rather not do that on the branch we're about to release (2.0.5) So, I will mark it "@Deprecated" in "trunk", while at the same time changing the rest of the code not to use it -Original Message-

RE: Jenkins build is back to normal : Pivot-maintenance on Java 8 #1120

So, what I found out (separately) is that even if you set the build class to 1.7 (say), and use the 1.8 compiler, but DON'T set the 1.7 bootstrap classpath, then the compiler will not flag stuff that is not compliant with the earlier version, so we need to either build with 1.6, or set the boots

Re: Jenkins build is back to normal : Pivot-maintenance on Java 8 #1120

Hi Roger, I dropped the build on Java 7 only because on 2.0.x the minimum required Java version is 6, and the current one is Java 8, and Java 7 is after End-of-Life so I think is no more relevant (even because if some code compiles with Java 6 and with Java 8 usually if works even with Java 7) ...

Re: Jenkins build is back to normal : Pivot-maintenance on Java 8 #1120

So, the "maintenance" branch (2.0.x) still only requires Java 1.6, so why are we only building with Java 8? I would think we should be building with Java 1.6, so we know that it works at the lowest common denominator still. Is that possible? Does the Jenkins machine have access to Java 1