SourceForge.net | 1 Jul 2012 02:46
Picon

[ jedit-Feature Requests-2931321 ] Pluginmanager - remove obselete plugins

Feature Requests item #2931321, was opened at 2010-01-13 04:27
Message generated for change (Settings changed) made by ezust
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350588&aid=2931321&group_id=588

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Plugin manager
Group: v4.3
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Lars Grundei (lgrundei)
>Assigned to: Alan Ezust (ezust)
Summary: Pluginmanager - remove obselete plugins

Initial Comment:
Hi,

I had the problem that jedit could no longer work properly, because an outdated plugin was installed.

It would be nice if jedit would recognize outdated plugins, much like in the "Find orphan" button. So that
they can then be removed easily.

Best Regards
Lars

----------------------------------------------------------------------
(Continue reading)

SourceForge.net | 1 Jul 2012 13:55
Picon

[ jedit-Plugin Bugs-3539123 ] Console: NPE when command starts in background

Plugin Bugs item #3539123, was opened at 2012-06-30 02:49
Message generated for change (Comment added) made by synh
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=565475&aid=3539123&group_id=588

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
>Resolution: None
Priority: 5
Private: No
Submitted By: Artem Bryantsev (synh)
Assigned to: Artem Bryantsev (synh)
Summary: Console: NPE when command starts in background

Initial Comment:
Execution "some_command &" or "some_command&" leads to NPE:

[Thread-7] [error] Thread-7: Exception in thread "Thread-7" 
[Thread-7] [error] Thread-7: java.lang.NullPointerException
[Thread-7] [error] Thread-7:  at console.ConsoleProcess.showExit(ConsoleProcess.java:156)
[Thread-7] [error] Thread-7:  at console.ConsoleProcess$1.run(ConsoleProcess.java:111)
[Thread-8] [error] StreamThread: Can't Flush:
[Thread-8] [error] StreamThread: java.lang.NullPointerException
[Thread-8] [error] StreamThread:  at console.StreamThread.flushLine(StreamThread.java:217)
[Thread-8] [error] StreamThread:  at console.StreamThread.run(StreamThread.java:130)

(Continue reading)

Jarek Czekalski | 1 Jul 2012 17:03
Picon
Favicon
Gravatar

twiki, community and drupal upgrade

Hi Vampire

Good news :)
(about the community <at> jedit.org not being a black hole)

About the Foswiki I have no opinion. No-one writes in wiki regardless of the software which is running it. And you struggle with spam all the time, which is not the case in sf wiki. I would rather stop registration at all in TWiki. But of course upgrading the software is nothing wrong.

You may also want to know that yesterday I cleaned 1GB warning.txt file from TWiki. I fixed wrong plugin installations and after grepping -v 2 repeating messages, the file shrank to 1MB.

I'm trying to assess the possibility and the advantages of upgrading drupal to 8 or something. Could you give me maximum rights? Is user #1 password your personal or is it a password you could share, for example in "jedit admin" document?

Thanks
Jarek

W dniu 07/01/2012 01:21 PM, jEdit Community pisze:
Of course, the guy that keeps everything running in the background. ;-)
I'm also working on finally updating our TWiki to the latest Foswiki release.

Regards
Vampire

2012/7/1 Jarek Czekalski <jarekczek <at> poczta.onet.pl>
Hi

Is anyone reading this? And replying? I took the address from the footer of TWiki page.

Jarek




------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
--

-- 
-----------------------------------------------
jEdit Developers' List
jEdit-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jedit-devel
SourceForge.net | 1 Jul 2012 17:53
Picon

[ jedit-Merge Requests-3534174 ] MiscUtilities.openInDesktop() in jEdit 5.0

Merge Requests item #3534174, was opened at 2012-06-10 11:41
Message generated for change (Comment added) made by jarekczek
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1235750&aid=3534174&group_id=588

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: for 5.0.x
>Status: Closed
>Resolution: Accepted
Priority: 5
Private: No
Submitted By: Alan Ezust (ezust)
>Assigned to: Jarek Czekalski (jarekczek)
Summary: MiscUtilities.openInDesktop() in jEdit 5.0

Initial Comment:
Originally, I was just going to move the code out of the browser.actions.xml file and into MiscUtilities
but during testing, I found and fixed a couple of bugs in related to files with spaces in the names.

So revision # 21791 moves the code into MiscUtilities (which is a new API) and also fixes some of the code
that was there before. I would like to put this into jEdit 5.0 so that plugins can use it sooner (esp.
projectviewer which has duplicate bad code right now).

----------------------------------------------------------------------

>Comment By: Jarek Czekalski (jarekczek)
Date: 2012-07-01 08:53

Message:
Applied to 5.0 as r21894. It would be easier if there were no other changes
to the method applied inbetween and no whitespace changes in different
places.

----------------------------------------------------------------------

Comment By: Alan Ezust (ezust)
Date: 2012-06-26 14:41

Message:
Rev# 21880 should address all your issues.

----------------------------------------------------------------------

Comment By: Jarek Czekalski (jarekczek)
Date: 2012-06-26 07:22

Message:
Alan, with such hasty comment and this level of your verbosity I see no way
to work on this ticket. And my opinion about this new api in 5.1 remains
negative.

----------------------------------------------------------------------

Comment By: Alan Ezust (ezust)
Date: 2012-06-25 10:17

Message:
That is incorrect. 
An IOException can also be thrown from Runtime.exec(). if for example,
command is not found or filename is bad. 

----------------------------------------------------------------------

Comment By: Jarek Czekalski (jarekczek)
Date: 2012-06-25 10:12

Message:
There is a problem with method's signature, maybe with javadoc.

 <at> throws IOException if the path is not valid or something else is not
working

Usually the exception will not be thrown because the string is simply
passed to a native command. Only in

// I don't know what platform it is...

there may really be IOException raised. But that's the border case, as all
known operating systems don't reach this line.

I think it would be better to remove this misleading exception from
signature. Capture it and report immediately, maybe returning true on
success, false on failure.

Copying the code from action to api seems to be not enough in this case.
Api needs additional care.

----------------------------------------------------------------------

Comment By: Jarek Czekalski (jarekczek)
Date: 2012-06-17 08:07

Message:
Kazutoshi was not sure whether to agree on this merge. I am going to commit
it, but will wait a few days for possible objections.

----------------------------------------------------------------------

Comment By: Alan Ezust (ezust)
Date: 2012-06-14 10:47

Message:
Rev#21801 improves the API docs for the function. 

----------------------------------------------------------------------

Comment By: Alan Ezust (ezust)
Date: 2012-06-11 11:11

Message:
I hope an exception can be made in this case.
I was just a day late :-)

----------------------------------------------------------------------

Comment By: Jarek Czekalski (jarekczek)
Date: 2012-06-11 10:27

Message:
Alan, so you suggest that 5.0pre1 (already released) have different api
than 5.0 or 5.0pre2? I remember someone said recently that it shouldn't be
done, but I don't see any written rule about that.

----------------------------------------------------------------------

Comment By: Alan Ezust (ezust)
Date: 2012-06-11 10:12

Message:
I removed some unnecessary code in rev# 21792 so you can apply that as part
of this merge request too.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=1235750&aid=3534174&group_id=588

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
--

-- 
-----------------------------------------------
jEdit Developers' List
jEdit-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jedit-devel

Kazutoshi Satoda | 1 Jul 2012 17:56
Picon
Gravatar

Re: [ jEdit-commits ] SF.net SVN: jedit:[21890] plugins/Console/trunk/console

sullengron <at> gmail.com wrote:
> In my opinion initial code was not safe, because this is not completed and
> invokes NullPointer Exceptions.
>
> I could not remove this functionality: probably somebody uses it (I did
> not know how).
> I did not want to fix this code: it seems old and probably nobody uses it.
> And I only disabled this functionality and created tickets at the tracker.

I think you should not commit such an uncertain change. If it should be
committed for some reason, you should write all the above as additional
comments besides the code.

I'm pointing the general programming practice, not the validity of the
change itself.

Here is a relevant question on stackoverflow.
http://stackoverflow.com/questions/1022552/old-code-in-comments

-- 
k_satoda

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
--

-- 
-----------------------------------------------
jEdit Developers' List
jEdit-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jedit-devel

SourceForge.net | 1 Jul 2012 18:25
Picon

[ jedit-Patches-3539298 ] Disable obsolete plugins #2931321

Patches item #3539298, was opened at 2012-07-01 09:25
Message generated for change (Tracker Item Submitted) made by ezust
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300588&aid=3539298&group_id=588

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Alan Ezust (ezust)
Assigned to: Matthieu Casanova (kpouer)
Summary: Disable obsolete plugins #2931321

Initial Comment:
Attached is a patch that disables obsolete plugins.
You can test it by placing Optional.jar into your jars folder and running it against jEdit 5.1.
It will automatically disable/blacklist Optional whenever the pluginlist is updated.
I am not sure what the correct action is though.
Should it log an error or pop up a dialog?
Should it mark it as red or remove it completely? 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300588&aid=3539298&group_id=588

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
--

-- 
-----------------------------------------------
jEdit Developers' List
jEdit-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jedit-devel

SourceForge.net | 1 Jul 2012 18:27
Picon

[ jedit-Feature Requests-2931321 ] Pluginmanager - disable obselete plugins

Feature Requests item #2931321, was opened at 2010-01-13 04:27
Message generated for change (Comment added) made by ezust
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350588&aid=2931321&group_id=588

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Plugin manager
>Group: None
>Status: Closed
>Resolution: Fixed
Priority: 5
Private: No
Submitted By: Lars Grundei (lgrundei)
Assigned to: Alan Ezust (ezust)
>Summary: Pluginmanager - disable obselete plugins

Initial Comment:
Hi,

I had the problem that jedit could no longer work properly, because an outdated plugin was installed.

It would be nice if jedit would recognize outdated plugins, much like in the "Find orphan" button. So that
they can then be removed easily.

Best Regards
Lars

----------------------------------------------------------------------

>Comment By: Alan Ezust (ezust)
Date: 2012-07-01 09:27

Message:
Patch#3539298 submitted.

----------------------------------------------------------------------

Comment By: Lars Grundei (lgrundei)
Date: 2010-01-13 10:07

Message:
In my opinion, this do not need to happen automatically (although it would
be perfect). A button in the plugin manager would be enough.

----------------------------------------------------------------------

Comment By: Alan Ezust (ezust)
Date: 2010-01-13 10:05

Message:
Since the pluginlist is cached, it can be done on startup provided the
pluginlist was cached once before.

----------------------------------------------------------------------

Comment By: Alan Ezust (ezust)
Date: 2010-01-13 09:58

Message:
basically, if the "max version" of a plugin is set in the plugin manager
pluginlist.xml, then 
jedit should check if it is greater than that max version for each of the
plugins that are installed, and 
disable the plugins that do not satisfy that requirement.

But when should it be done? Ideally, before the plugin is activated. But
jEdit doesn't load that information (the max version) until the plugin list
is downloaded for the first time, in the update/install pane of
pluginmanager.
So where/when should the checking and disabling be done? 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350588&aid=2931321&group_id=588

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
--

-- 
-----------------------------------------------
jEdit Developers' List
jEdit-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jedit-devel

SourceForge.net | 1 Jul 2012 18:32
Picon

[ jedit-Feature Requests-2931321 ] Pluginmanager - disable obselete plugins

Feature Requests item #2931321, was opened at 2010-01-13 04:27
Message generated for change (Comment added) made by ezust
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350588&aid=2931321&group_id=588

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: Plugin manager
Group: None
>Status: Open
Resolution: Fixed
Priority: 5
Private: No
Submitted By: Lars Grundei (lgrundei)
Assigned to: Alan Ezust (ezust)
Summary: Pluginmanager - disable obselete plugins

Initial Comment:
Hi,

I had the problem that jedit could no longer work properly, because an outdated plugin was installed.

It would be nice if jedit would recognize outdated plugins, much like in the "Find orphan" button. So that
they can then be removed easily.

Best Regards
Lars

----------------------------------------------------------------------

>Comment By: Alan Ezust (ezust)
Date: 2012-07-01 09:32

Message:
Leaving as "open" until the patch is committed.

----------------------------------------------------------------------

Comment By: Alan Ezust (ezust)
Date: 2012-07-01 09:27

Message:
Patch#3539298 submitted.

----------------------------------------------------------------------

Comment By: Lars Grundei (lgrundei)
Date: 2010-01-13 10:07

Message:
In my opinion, this do not need to happen automatically (although it would
be perfect). A button in the plugin manager would be enough.

----------------------------------------------------------------------

Comment By: Alan Ezust (ezust)
Date: 2010-01-13 10:05

Message:
Since the pluginlist is cached, it can be done on startup provided the
pluginlist was cached once before.

----------------------------------------------------------------------

Comment By: Alan Ezust (ezust)
Date: 2010-01-13 09:58

Message:
basically, if the "max version" of a plugin is set in the plugin manager
pluginlist.xml, then 
jedit should check if it is greater than that max version for each of the
plugins that are installed, and 
disable the plugins that do not satisfy that requirement.

But when should it be done? Ideally, before the plugin is activated. But
jEdit doesn't load that information (the max version) until the plugin list
is downloaded for the first time, in the update/install pane of
pluginmanager.
So where/when should the checking and disabling be done? 

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=350588&aid=2931321&group_id=588

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
--

-- 
-----------------------------------------------
jEdit Developers' List
jEdit-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jedit-devel

SourceForge.net | 1 Jul 2012 18:42
Picon

[ jedit-Patches-3539298 ] Disable obsolete plugins #2931321

Patches item #3539298, was opened at 2012-07-01 09:25
Message generated for change (Comment added) made by ezust
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300588&aid=3539298&group_id=588

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Alan Ezust (ezust)
Assigned to: Matthieu Casanova (kpouer)
Summary: Disable obsolete plugins #2931321

Initial Comment:
Attached is a patch that disables obsolete plugins.
You can test it by placing Optional.jar into your jars folder and running it against jEdit 5.1.
It will automatically disable/blacklist Optional whenever the pluginlist is updated.
I am not sure what the correct action is though.
Should it log an error or pop up a dialog?
Should it mark it as red or remove it completely? 

----------------------------------------------------------------------

>Comment By: Alan Ezust (ezust)
Date: 2012-07-01 09:42

Message:
I had the code in the wrong place. Removing my first attempt. I am going to
make a better patch and attach that.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300588&aid=3539298&group_id=588

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
--

-- 
-----------------------------------------------
jEdit Developers' List
jEdit-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jedit-devel

SourceForge.net | 1 Jul 2012 18:59
Picon

[ jedit-Patches-3539298 ] Disable obsolete plugins #2931321

Patches item #3539298, was opened at 2012-07-01 09:25
Message generated for change (Comment added) made by ezust
You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300588&aid=3539298&group_id=588

Please note that this message will contain a full copy of the comment thread,
including the initial issue submission, for this request,
not just the latest update.
Category: None
Group: None
Status: Open
Resolution: None
Priority: 5
Private: No
Submitted By: Alan Ezust (ezust)
Assigned to: Matthieu Casanova (kpouer)
Summary: Disable obsolete plugins #2931321

Initial Comment:
Attached is a patch that disables obsolete plugins.
You can test it by placing Optional.jar into your jars folder and running it against jEdit 5.1.
It will automatically disable/blacklist Optional whenever the pluginlist is updated.
I am not sure what the correct action is though.
Should it log an error or pop up a dialog?
Should it mark it as red or remove it completely? 

----------------------------------------------------------------------

>Comment By: Alan Ezust (ezust)
Date: 2012-07-01 09:59

Message:
I am submitting a newer patch that tries to "breakPlugin()" the pluginJAR.
I was hoping that would have the side-effect of also marking it red in the
ManagePanel but it doesn't work. 
Matthieu, perhaps you can make things look nicer in the ManagePanel when an
obsolete plugin is found?

----------------------------------------------------------------------

Comment By: Alan Ezust (ezust)
Date: 2012-07-01 09:42

Message:
I had the code in the wrong place. Removing my first attempt. I am going to
make a better patch and attach that.

----------------------------------------------------------------------

You can respond by visiting: 
https://sourceforge.net/tracker/?func=detail&atid=300588&aid=3539298&group_id=588

------------------------------------------------------------------------------
Live Security Virtual Conference
Exclusive live event will cover all the ways today's security and 
threat landscape has changed and how IT managers can respond. Discussions 
will include endpoint security, mobile security and the latest in malware 
threats. http://www.accelacomm.com/jaw/sfrnl04242012/114/50122263/
--

-- 
-----------------------------------------------
jEdit Developers' List
jEdit-devel <at> lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/jedit-devel


Gmane