jedit-devel Mailing List for jEdit

I make occasional use of the Java Insight plugin, but I notice that the 
JODE decompiler is getting a little out of date and doesn't look if it 
is being maintained any more.

I was thinking of replacing the of replacing it with a more up to date 
one, such as CFR http://www.benf.org/other/cfr/ -  though I would need 
to check with the author  for permission, though his website mentions 
that he will be using and MIT licence.

Yes, as I said, it should be sufficient.
You might not have some cool features that are only available in Ultimate
version, like UML Designer, XPath support and so on, but nothing you
necessarily need.
But you can just try it.
Just use the Community Edition and / or use the 30 day trial of the
Ultimate Edition.
Just check out the sourcecode and open the project with IJ, then you are
completely set-up to work with core jEdit.
For plugins, it depends on the individual plugin developer.
The plugins are all maintained by community members, some of which happen
to also be core committers.
But even if there are no checked in IJ project files for the plugins you
want to look at, you should be easily able to either create a separate
project for them, or to add them as modules to the jEdit project.
Both can be done "from existing sources" with IJ.

2015-04-18 1:02 GMT+02:00 Edward Diener <eld...@tr...>:

> On 4/17/2015 6:07 PM, Björn Kautler wrote:
> > The project license is for Ultimate Edition.
> > Most features in Ultimate Edition are more interesting for corporate
> > development.
> > See differences here:
> > https://www.jetbrains.com/idea/features/editions_comparison_matrix.html
>
> If the community edition is sufficient for jedit development it is fine
> with me. Is there any documentation about developing/updating jedit or
> jedit plugins with IntelliJ ? It was mentioned that project files for IJ
> are part of version control.
>
> >
> > 2015-04-17 21:44 GMT+02:00 Edward Diener <eld...@tr...
> > <mailto:eld...@tr...>>:
> >
> >     On 4/16/2015 9:13 PM, Vampire wrote:
> >     > Edward you could also use IntelliJ IDEA instead.
> >     > It is the best Java IDE available.
> >     > And it works with jEdit sourcecode out-of-the-box, because the
> project
> >     > files for IJ are checked into version control
> >     > .
> >     > The free community edition of IJ should be sufficient.
> >     > If you plan to work on jEdit or a plugin in the future, I can even
> give
> >     > you our free project license of IJ.
> >
> >     What is the difference between the free community edition and a free
> >     project license ?
> >
> >     I would like to work on jEdit or a plugin in the future but I do not
> >     know when/if I will have some time to do so. If I do get the free
> >     project license of IJ I can promise I will not be doing any
> commercial
> >     development with it.
> >
> >     >
> >     > Regards
> >     > Björn
> >     >
> >     >
> >     > 2015-02-21 0:30 GMT+01:00 Dale Anson <da...@da... <mailto:
> da...@da...>
> >      > <mailto:da...@da... <mailto:da...@da...>>>:
> >     >
> >     >     I've done exactly what you're asking with Netbeans 7, or maybe
> it
> >     >     was 6, it's been some months anyway. I'm sure it's still
> doable with
> >     >     8. Unfortunately, I'm not in a place where I can send you good
> >     >     instructions to help you out. If I recall correctly, set up a
> >     >     .../jEdit directory containing the jEdit source, then in that
> >     >     directory, create a plugins directory and check out the source
> to
> >     >     your plugins there. Create a Netbeans project from existing
> sources.
> >     >     Start jEdit from the command line in debug mode, you'll have
> to look
> >     >     up that part, I don't recall the command off of the top of my
> head.
> >     >     Use the version where you set a debug port. Then in Netbeans,
> open
> >     >     the debugger pointing at that port. Do your debugging. That
> should
> >     >     be all there is to it.
> >     >
> >     >     Dale
> >     >
> >     >     On Feb 19, 2015 5:59 PM, "Alan Ezust" <ala...@gm...
> <mailto:ala...@gm...>
> >     >     <mailto:ala...@gm... <mailto:ala...@gm...>>>
> wrote:
> >     >
> >     >
> >     >
> >     >         On Wed, Feb 18, 2015 at 4:32 PM, Edward Diener
> >     >         <eld...@tr... <mailto:
> eld...@tr...>
> >      >         <mailto:eld...@tr...
> >     <mailto:eld...@tr...>>> wrote:
> >      >
> >      >             On 2/18/2015 6:42 PM, Alan Ezust wrote:
> >      >             > Basically, if you want to step through code of
> >     jEdit, you need to add
> >      >             > jEdit as a project.
> >      >             > If you want to step through code of a plugin, you
> >     need to create a new
> >      >             > project for that plugin, and set its dependences
> >     correctly.
> >      >             > Then when you run jEdit from your IDE, it should be
> >     able to find your
> >      >             > sources for a given plugin. And if it steps through
> >     a code of a plugin
> >      >             > you haven't created a project for, you'll have to
> >     add that project too.
> >      >
> >      >             I will have to look at Netbeans more carefully but I
> am
> >      >             hoping to setup
> >      >             a Netbeans project so that both jedit and the plugins
> >     I want
> >      >             to debug
> >      >             are part of the same project. Ohterwise I don't see
> how
> >      >             Netbeans can
> >      >             find a plugins source if each is a different project.
> >      >
> >      >
> >      >         I know with Eclipse you can have separate projects for
> each
> >      >         plugin open in the workspace. I assume the same is true
> with
> >      >         NetBeans.
> >      >
> >      >
> >      >             Should I be using the Netbeans "Java Project with
> >     Existing
> >      >             Sources",
> >      >             which has the IDE creating an IDE-generated Ant build
> >     script
> >      >             or the
> >      >             Netbeans "Java Free-Form Project" which uses the
> >     current Ant
> >      >             scripts
> >      >             already in place ? Has anyone had any experience
> actually
> >      >             doing this
> >      >             with Netbeans so far ? I have never been able to
> >     understand
> >      >             Eclipse and
> >      >             have found Netbeans much friendlier in the past, but
> I am
> >      >             not mainly a
> >      >             Java programmer so I thought I should first ask
> >     others about
> >      >             setting up
> >      >             building JEdit and plugins in the Netbeans IDE.
> >      >
> >      >
> >      >         I don't know about netbeans, sorry.
>
>
>
>
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live
> exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
> event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
> --
> -----------------------------------------------
> jEdit Developers' List
> jEd...@li...
> https://lists.sourceforge.net/lists/listinfo/jedit-devel
>

On 4/17/2015 6:07 PM, Björn Kautler wrote:
> The project license is for Ultimate Edition.
> Most features in Ultimate Edition are more interesting for corporate
> development.
> See differences here:
> https://www.jetbrains.com/idea/features/editions_comparison_matrix.html

If the community edition is sufficient for jedit development it is fine 
with me. Is there any documentation about developing/updating jedit or 
jedit plugins with IntelliJ ? It was mentioned that project files for IJ 
are part of version control.

>
> 2015-04-17 21:44 GMT+02:00 Edward Diener <eld...@tr...
> <mailto:eld...@tr...>>:
>
>     On 4/16/2015 9:13 PM, Vampire wrote:
>     > Edward you could also use IntelliJ IDEA instead.
>     > It is the best Java IDE available.
>     > And it works with jEdit sourcecode out-of-the-box, because the project
>     > files for IJ are checked into version control
>     > .
>     > The free community edition of IJ should be sufficient.
>     > If you plan to work on jEdit or a plugin in the future, I can even give
>     > you our free project license of IJ.
>
>     What is the difference between the free community edition and a free
>     project license ?
>
>     I would like to work on jEdit or a plugin in the future but I do not
>     know when/if I will have some time to do so. If I do get the free
>     project license of IJ I can promise I will not be doing any commercial
>     development with it.
>
>     >
>     > Regards
>     > Björn
>     >
>     >
>     > 2015-02-21 0:30 GMT+01:00 Dale Anson <da...@da... <mailto:da...@da...>
>      > <mailto:da...@da... <mailto:da...@da...>>>:
>     >
>     >     I've done exactly what you're asking with Netbeans 7, or maybe it
>     >     was 6, it's been some months anyway. I'm sure it's still doable with
>     >     8. Unfortunately, I'm not in a place where I can send you good
>     >     instructions to help you out. If I recall correctly, set up a
>     >     .../jEdit directory containing the jEdit source, then in that
>     >     directory, create a plugins directory and check out the source to
>     >     your plugins there. Create a Netbeans project from existing sources.
>     >     Start jEdit from the command line in debug mode, you'll have to look
>     >     up that part, I don't recall the command off of the top of my head.
>     >     Use the version where you set a debug port. Then in Netbeans, open
>     >     the debugger pointing at that port. Do your debugging. That should
>     >     be all there is to it.
>     >
>     >     Dale
>     >
>     >     On Feb 19, 2015 5:59 PM, "Alan Ezust" <ala...@gm... <mailto:ala...@gm...>
>     >     <mailto:ala...@gm... <mailto:ala...@gm...>>> wrote:
>     >
>     >
>     >
>     >         On Wed, Feb 18, 2015 at 4:32 PM, Edward Diener
>     >         <eld...@tr... <mailto:eld...@tr...>
>      >         <mailto:eld...@tr...
>     <mailto:eld...@tr...>>> wrote:
>      >
>      >             On 2/18/2015 6:42 PM, Alan Ezust wrote:
>      >             > Basically, if you want to step through code of
>     jEdit, you need to add
>      >             > jEdit as a project.
>      >             > If you want to step through code of a plugin, you
>     need to create a new
>      >             > project for that plugin, and set its dependences
>     correctly.
>      >             > Then when you run jEdit from your IDE, it should be
>     able to find your
>      >             > sources for a given plugin. And if it steps through
>     a code of a plugin
>      >             > you haven't created a project for, you'll have to
>     add that project too.
>      >
>      >             I will have to look at Netbeans more carefully but I am
>      >             hoping to setup
>      >             a Netbeans project so that both jedit and the plugins
>     I want
>      >             to debug
>      >             are part of the same project. Ohterwise I don't see how
>      >             Netbeans can
>      >             find a plugins source if each is a different project.
>      >
>      >
>      >         I know with Eclipse you can have separate projects for each
>      >         plugin open in the workspace. I assume the same is true with
>      >         NetBeans.
>      >
>      >
>      >             Should I be using the Netbeans "Java Project with
>     Existing
>      >             Sources",
>      >             which has the IDE creating an IDE-generated Ant build
>     script
>      >             or the
>      >             Netbeans "Java Free-Form Project" which uses the
>     current Ant
>      >             scripts
>      >             already in place ? Has anyone had any experience actually
>      >             doing this
>      >             with Netbeans so far ? I have never been able to
>     understand
>      >             Eclipse and
>      >             have found Netbeans much friendlier in the past, but I am
>      >             not mainly a
>      >             Java programmer so I thought I should first ask
>     others about
>      >             setting up
>      >             building JEdit and plugins in the Netbeans IDE.
>      >
>      >
>      >         I don't know about netbeans, sorry.

The project license is for Ultimate Edition.
Most features in Ultimate Edition are more interesting for corporate
development.
See differences here:
https://www.jetbrains.com/idea/features/editions_comparison_matrix.html

2015-04-17 21:44 GMT+02:00 Edward Diener <eld...@tr...>:

> On 4/16/2015 9:13 PM, Vampire wrote:
> > Edward you could also use IntelliJ IDEA instead.
> > It is the best Java IDE available.
> > And it works with jEdit sourcecode out-of-the-box, because the project
> > files for IJ are checked into version control
> > .
> > The free community edition of IJ should be sufficient.
> > If you plan to work on jEdit or a plugin in the future, I can even give
> > you our free project license of IJ.
>
> What is the difference between the free community edition and a free
> project license ?
>
> I would like to work on jEdit or a plugin in the future but I do not
> know when/if I will have some time to do so. If I do get the free
> project license of IJ I can promise I will not be doing any commercial
> development with it.
>
> >
> > Regards
> > Björn
> >
> >
> > 2015-02-21 0:30 GMT+01:00 Dale Anson <da...@da...
> > <mailto:da...@da...>>:
> >
> >     I've done exactly what you're asking with Netbeans 7, or maybe it
> >     was 6, it's been some months anyway. I'm sure it's still doable with
> >     8. Unfortunately, I'm not in a place where I can send you good
> >     instructions to help you out. If I recall correctly, set up a
> >     .../jEdit directory containing the jEdit source, then in that
> >     directory, create a plugins directory and check out the source to
> >     your plugins there. Create a Netbeans project from existing sources.
> >     Start jEdit from the command line in debug mode, you'll have to look
> >     up that part, I don't recall the command off of the top of my head.
> >     Use the version where you set a debug port. Then in Netbeans, open
> >     the debugger pointing at that port. Do your debugging. That should
> >     be all there is to it.
> >
> >     Dale
> >
> >     On Feb 19, 2015 5:59 PM, "Alan Ezust" <ala...@gm...
> >     <mailto:ala...@gm...>> wrote:
> >
> >
> >
> >         On Wed, Feb 18, 2015 at 4:32 PM, Edward Diener
> >         <eld...@tr...
> >         <mailto:eld...@tr...>> wrote:
> >
> >             On 2/18/2015 6:42 PM, Alan Ezust wrote:
> >             > Basically, if you want to step through code of jEdit, you
> need to add
> >             > jEdit as a project.
> >             > If you want to step through code of a plugin, you need to
> create a new
> >             > project for that plugin, and set its dependences correctly.
> >             > Then when you run jEdit from your IDE, it should be able
> to find your
> >             > sources for a given plugin. And if it steps through a code
> of a plugin
> >             > you haven't created a project for, you'll have to add that
> project too.
> >
> >             I will have to look at Netbeans more carefully but I am
> >             hoping to setup
> >             a Netbeans project so that both jedit and the plugins I want
> >             to debug
> >             are part of the same project. Ohterwise I don't see how
> >             Netbeans can
> >             find a plugins source if each is a different project.
> >
> >
> >         I know with Eclipse you can have separate projects for each
> >         plugin open in the workspace. I assume the same is true with
> >         NetBeans.
> >
> >
> >             Should I be using the Netbeans "Java Project with Existing
> >             Sources",
> >             which has the IDE creating an IDE-generated Ant build script
> >             or the
> >             Netbeans "Java Free-Form Project" which uses the current Ant
> >             scripts
> >             already in place ? Has anyone had any experience actually
> >             doing this
> >             with Netbeans so far ? I have never been able to understand
> >             Eclipse and
> >             have found Netbeans much friendlier in the past, but I am
> >             not mainly a
> >             Java programmer so I thought I should first ask others about
> >             setting up
> >             building JEdit and plugins in the Netbeans IDE.
> >
> >
> >         I don't know about netbeans, sorry.
> >
> >
> >
> >
>  ------------------------------------------------------------------------------
> >         Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> >         from Actuate! Instantly Supercharge Your Business Reports and
> >         Dashboards
> >         with Interactivity, Sharing, Native Excel Exports, App
> >         Integration & more
> >         Get technology previously reserved for billion-dollar
> >         corporations, FREE
> >
> http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
> >         --
> >         -----------------------------------------------
> >         jEdit Developers' List
> >         jEd...@li...
> >         <mailto:jEd...@li...>
> >         https://lists.sourceforge.net/lists/listinfo/jedit-devel
> >
> >
> >
>  ------------------------------------------------------------------------------
> >     Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> >     from Actuate! Instantly Supercharge Your Business Reports and
> Dashboards
> >     with Interactivity, Sharing, Native Excel Exports, App Integration &
> >     more
> >     Get technology previously reserved for billion-dollar corporations,
> FREE
> >
> http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
> >     --
> >     -----------------------------------------------
> >     jEdit Developers' List
> >     jEd...@li...
> >     <mailto:jEd...@li...>
> >     https://lists.sourceforge.net/lists/listinfo/jedit-devel
> >
> >
> >
> >
> >
> ------------------------------------------------------------------------------
> > BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> > Develop your own process in accordance with the BPMN 2 standard
> > Learn Process modeling best practices with Bonita BPM through live
> exercises
> > http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
> event?utm_
> > source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
> >
> >
> >
>
>
>
>
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live
> exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual-
> event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
> --
> -----------------------------------------------
> jEdit Developers' List
> jEd...@li...
> https://lists.sourceforge.net/lists/listinfo/jedit-devel
>

On 4/16/2015 9:13 PM, Vampire wrote:
> Edward you could also use IntelliJ IDEA instead.
> It is the best Java IDE available.
> And it works with jEdit sourcecode out-of-the-box, because the project
> files for IJ are checked into version control
> .
> The free community edition of IJ should be sufficient.
> If you plan to work on jEdit or a plugin in the future, I can even give
> you our free project license of IJ.

What is the difference between the free community edition and a free 
project license ?

I would like to work on jEdit or a plugin in the future but I do not 
know when/if I will have some time to do so. If I do get the free 
project license of IJ I can promise I will not be doing any commercial 
development with it.

>
> Regards
> Björn
>
>
> 2015-02-21 0:30 GMT+01:00 Dale Anson <da...@da...
> <mailto:da...@da...>>:
>
>     I've done exactly what you're asking with Netbeans 7, or maybe it
>     was 6, it's been some months anyway. I'm sure it's still doable with
>     8. Unfortunately, I'm not in a place where I can send you good
>     instructions to help you out. If I recall correctly, set up a
>     .../jEdit directory containing the jEdit source, then in that
>     directory, create a plugins directory and check out the source to
>     your plugins there. Create a Netbeans project from existing sources.
>     Start jEdit from the command line in debug mode, you'll have to look
>     up that part, I don't recall the command off of the top of my head.
>     Use the version where you set a debug port. Then in Netbeans, open
>     the debugger pointing at that port. Do your debugging. That should
>     be all there is to it.
>
>     Dale
>
>     On Feb 19, 2015 5:59 PM, "Alan Ezust" <ala...@gm...
>     <mailto:ala...@gm...>> wrote:
>
>
>
>         On Wed, Feb 18, 2015 at 4:32 PM, Edward Diener
>         <eld...@tr...
>         <mailto:eld...@tr...>> wrote:
>
>             On 2/18/2015 6:42 PM, Alan Ezust wrote:
>             > Basically, if you want to step through code of jEdit, you need to add
>             > jEdit as a project.
>             > If you want to step through code of a plugin, you need to create a new
>             > project for that plugin, and set its dependences correctly.
>             > Then when you run jEdit from your IDE, it should be able to find your
>             > sources for a given plugin. And if it steps through a code of a plugin
>             > you haven't created a project for, you'll have to add that project too.
>
>             I will have to look at Netbeans more carefully but I am
>             hoping to setup
>             a Netbeans project so that both jedit and the plugins I want
>             to debug
>             are part of the same project. Ohterwise I don't see how
>             Netbeans can
>             find a plugins source if each is a different project.
>
>
>         I know with Eclipse you can have separate projects for each
>         plugin open in the workspace. I assume the same is true with
>         NetBeans.
>
>
>             Should I be using the Netbeans "Java Project with Existing
>             Sources",
>             which has the IDE creating an IDE-generated Ant build script
>             or the
>             Netbeans "Java Free-Form Project" which uses the current Ant
>             scripts
>             already in place ? Has anyone had any experience actually
>             doing this
>             with Netbeans so far ? I have never been able to understand
>             Eclipse and
>             have found Netbeans much friendlier in the past, but I am
>             not mainly a
>             Java programmer so I thought I should first ask others about
>             setting up
>             building JEdit and plugins in the Netbeans IDE.
>
>
>         I don't know about netbeans, sorry.
>
>
>
>         ------------------------------------------------------------------------------
>         Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
>         from Actuate! Instantly Supercharge Your Business Reports and
>         Dashboards
>         with Interactivity, Sharing, Native Excel Exports, App
>         Integration & more
>         Get technology previously reserved for billion-dollar
>         corporations, FREE
>         http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
>         --
>         -----------------------------------------------
>         jEdit Developers' List
>         jEd...@li...
>         <mailto:jEd...@li...>
>         https://lists.sourceforge.net/lists/listinfo/jedit-devel
>
>
>     ------------------------------------------------------------------------------
>     Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
>     from Actuate! Instantly Supercharge Your Business Reports and Dashboards
>     with Interactivity, Sharing, Native Excel Exports, App Integration &
>     more
>     Get technology previously reserved for billion-dollar corporations, FREE
>     http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
>     --
>     -----------------------------------------------
>     jEdit Developers' List
>     jEd...@li...
>     <mailto:jEd...@li...>
>     https://lists.sourceforge.net/lists/listinfo/jedit-devel
>
>
>
>
> ------------------------------------------------------------------------------
> BPM Camp - Free Virtual Workshop May 6th at 10am PDT/1PM EDT
> Develop your own process in accordance with the BPMN 2 standard
> Learn Process modeling best practices with Bonita BPM through live exercises
> http://www.bonitasoft.com/be-part-of-it/events/bpm-camp-virtual- event?utm_
> source=Sourceforge_BPM_Camp_5_6_15&utm_medium=email&utm_campaign=VA_SF
>
>
>

Thanks Vampire, I'll be sure to look out for these things in the future if
I have to do another release.

EB

On Wed, Apr 15, 2015 at 7:38 PM, Vampire <Va...@je...> wrote:

> So, finally I reviewed your release Eric.
> All in all, everything seems to be fine.
> Just some minor glitches.
>
> - Release.gpg was missing, but that is ok, as you produce warnings if you
> change the signing key. I uploaded the correct signing file and now all
> Debian updates should go through smoothly
> - Why did you check-in releasing-jedit.txt? This is not mentioned in
> releasing-jedit.txt because is not meant to be done. You don't even have to
> save the file. The variable substitution is solely for easier copy & paste
> usage. Checking in the replaced file makes it useless for further releases.
> - The fixes in CHANGES.txt according to 2. were not done (one newline is
> missing, an empty section was not removed, the version was not set to the
> final version as it was no pre-release anymore [while the last point was
> fixed by Alan just in time :-)])
> - file sizes and page amounts were not corrected on download.html
> according to 9.
> - web changes were not checked into SVN according to 9. (
> https://sourceforge.net/p/jedit/svn/HEAD/tree/www/trunk/htdocs/)
> - IRC channel topic was not updated according to 12.
> - Community Page Start Page News were not written according to 13.
>
> Other than that, everything seems to be fine, thanks again for doing the
> release.
>
> Cheers
> Björn
>
>
> 2015-02-28 4:20 GMT+01:00 Björn Kautler <Bj...@ka...>:
>
>> Definitely, that's why I wrote the step-by-step releasing-jedit.txt with
>> which most people with access should be able to do the release easily by
>> following step for step. I'll be away the next two weeks, but after that I
>> will gladly review what you did and at least add the debian metadata.
>>
>> Cheers
>> Björn
>>
>> 2015-02-28 4:00 GMT+01:00 Eric Berry <el...@gm...>:
>>
>>> Thanks Vampire,
>>> I'm glad you're feeling better. Please let me know if I did anything
>>> incorrectly. I think it's a good idea for multiple people to be able to do
>>> releases so there's less pressure on any one person, and the community
>>> doesn't get stuck accidentally.
>>>
>>> Thanks,
>>> Eric
>>>
>>> On Fri, Feb 27, 2015 at 6:52 PM, Björn Kautler <Bj...@ka...>
>>> wrote:
>>>
>>>> Hey guys,
>>>>
>>>> thanks for doing the release this time.
>>>> I'm really sorry I wasn't around, but a serious illness caught me quite
>>>> some time and I had no internet access.
>>>> I'm well again now and can do future releases again.
>>>> But I'm glad all went well.
>>>> I'll have a look at the debian repository files soon and update them
>>>> for the new release.
>>>>
>>>> Cheers
>>>> Björn
>>>>
>>>>
>>>> 2015-02-06 3:19 GMT+01:00 Alan Ezust <ala...@gm...>:
>>>>
>>>>> Thank you Eric!!! (& Eric too!)
>>>>>
>>>>> Once again, you save the day!!
>>>>>
>>>>> --Alan
>>>>>
>>>>>
>>>>>
>>>>> ------------------------------------------------------------------------------
>>>>> Dive into the World of Parallel Programming. The Go Parallel Website,
>>>>> sponsored by Intel and developed in partnership with Slashdot Media,
>>>>> is your
>>>>> hub for all things parallel software development, from weekly thought
>>>>> leadership blogs to news, videos, case studies, tutorials and more.
>>>>> Take a
>>>>> look and join the conversation now. http://goparallel.sourceforge.net/
>>>>> --
>>>>> -----------------------------------------------
>>>>> jEdit Developers' List
>>>>> jEd...@li...
>>>>> https://lists.sourceforge.net/lists/listinfo/jedit-devel
>>>>>
>>>>>
>>>>
>>>
>>>
>>> --
>>> Learn from the past. Live in the present. Work towards the future.
>>> Blog: http://eric-berry.blogspot.com
>>> jEdit <http://www.jedit.org> - Programmer's Text Editor
>>>
>>
>>
>


-- 
Learn from the past. Live in the present. Work towards the future.
Blog: http://eric-berry.blogspot.com
jEdit <http://www.jedit.org> - Programmer's Text Editor

Edward you could also use IntelliJ IDEA instead.
It is the best Java IDE available.
And it works with jEdit sourcecode out-of-the-box, because the project
files for IJ are checked into version control
.
The free community edition of IJ should be sufficient.
If you plan to work on jEdit or a plugin in the future, I can even give you
our free project license of IJ.

Regards
Björn


2015-02-21 0:30 GMT+01:00 Dale Anson <da...@da...>:

> I've done exactly what you're asking with Netbeans 7, or maybe it was 6,
> it's been some months anyway. I'm sure it's still doable with 8.
> Unfortunately, I'm not in a place where I can send you good instructions to
> help you out. If I recall correctly, set up a .../jEdit directory
> containing the jEdit source, then in that directory, create a plugins
> directory and check out the source to your plugins there. Create a Netbeans
> project from existing sources. Start jEdit from the command line in debug
> mode, you'll have to look up that part, I don't recall the command off of
> the top of my head. Use the version where you set a debug port. Then in
> Netbeans, open the debugger pointing at that port. Do your debugging. That
> should be all there is to it.
>
> Dale
> On Feb 19, 2015 5:59 PM, "Alan Ezust" <ala...@gm...> wrote:
>
>>
>>
>> On Wed, Feb 18, 2015 at 4:32 PM, Edward Diener <
>> eld...@tr...> wrote:
>>
>>> On 2/18/2015 6:42 PM, Alan Ezust wrote:
>>> > Basically, if you want to step through code of jEdit, you need to add
>>> > jEdit as a project.
>>> > If you want to step through code of a plugin, you need to create a new
>>> > project for that plugin, and set its dependences correctly.
>>> > Then when you run jEdit from your IDE, it should be able to find your
>>> > sources for a given plugin. And if it steps through a code of a plugin
>>> > you haven't created a project for, you'll have to add that project too.
>>>
>>> I will have to look at Netbeans more carefully but I am hoping to setup
>>> a Netbeans project so that both jedit and the plugins I want to debug
>>> are part of the same project. Ohterwise I don't see how Netbeans can
>>> find a plugins source if each is a different project.
>>>
>>
>> I know with Eclipse you can have separate projects for each plugin open
>> in the workspace. I assume the same is true with NetBeans.
>>
>>
>>
>>>
>>> Should I be using the Netbeans "Java Project with Existing Sources",
>>> which has the IDE creating an IDE-generated Ant build script or the
>>> Netbeans "Java Free-Form Project" which uses the current Ant scripts
>>> already in place ? Has anyone had any experience actually doing this
>>> with Netbeans so far ? I have never been able to understand Eclipse and
>>> have found Netbeans much friendlier in the past, but I am not mainly a
>>> Java programmer so I thought I should first ask others about setting up
>>> building JEdit and plugins in the Netbeans IDE.
>>>
>>
>> I don't know about netbeans, sorry.
>>
>>
>>
>>
>> ------------------------------------------------------------------------------
>> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
>> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
>> with Interactivity, Sharing, Native Excel Exports, App Integration & more
>> Get technology previously reserved for billion-dollar corporations, FREE
>>
>> http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
>> --
>> -----------------------------------------------
>> jEdit Developers' List
>> jEd...@li...
>> https://lists.sourceforge.net/lists/listinfo/jedit-devel
>>
>>
>
> ------------------------------------------------------------------------------
> Download BIRT iHub F-Type - The Free Enterprise-Grade BIRT Server
> from Actuate! Instantly Supercharge Your Business Reports and Dashboards
> with Interactivity, Sharing, Native Excel Exports, App Integration & more
> Get technology previously reserved for billion-dollar corporations, FREE
>
> http://pubads.g.doubleclick.net/gampad/clk?id=190641631&iu=/4140/ostg.clktrk
> --
> -----------------------------------------------
> jEdit Developers' List
> jEd...@li...
> https://lists.sourceforge.net/lists/listinfo/jedit-devel
>
>

So, finally I reviewed your release Eric.
All in all, everything seems to be fine.
Just some minor glitches.

- Release.gpg was missing, but that is ok, as you produce warnings if you
change the signing key. I uploaded the correct signing file and now all
Debian updates should go through smoothly
- Why did you check-in releasing-jedit.txt? This is not mentioned in
releasing-jedit.txt because is not meant to be done. You don't even have to
save the file. The variable substitution is solely for easier copy & paste
usage. Checking in the replaced file makes it useless for further releases.
- The fixes in CHANGES.txt according to 2. were not done (one newline is
missing, an empty section was not removed, the version was not set to the
final version as it was no pre-release anymore [while the last point was
fixed by Alan just in time :-)])
- file sizes and page amounts were not corrected on download.html according
to 9.
- web changes were not checked into SVN according to 9. (
https://sourceforge.net/p/jedit/svn/HEAD/tree/www/trunk/htdocs/)
- IRC channel topic was not updated according to 12.
- Community Page Start Page News were not written according to 13.

Other than that, everything seems to be fine, thanks again for doing the
release.

Cheers
Björn


2015-02-28 4:20 GMT+01:00 Björn Kautler <Bj...@ka...>:

> Definitely, that's why I wrote the step-by-step releasing-jedit.txt with
> which most people with access should be able to do the release easily by
> following step for step. I'll be away the next two weeks, but after that I
> will gladly review what you did and at least add the debian metadata.
>
> Cheers
> Björn
>
> 2015-02-28 4:00 GMT+01:00 Eric Berry <el...@gm...>:
>
>> Thanks Vampire,
>> I'm glad you're feeling better. Please let me know if I did anything
>> incorrectly. I think it's a good idea for multiple people to be able to do
>> releases so there's less pressure on any one person, and the community
>> doesn't get stuck accidentally.
>>
>> Thanks,
>> Eric
>>
>> On Fri, Feb 27, 2015 at 6:52 PM, Björn Kautler <Bj...@ka...>
>> wrote:
>>
>>> Hey guys,
>>>
>>> thanks for doing the release this time.
>>> I'm really sorry I wasn't around, but a serious illness caught me quite
>>> some time and I had no internet access.
>>> I'm well again now and can do future releases again.
>>> But I'm glad all went well.
>>> I'll have a look at the debian repository files soon and update them for
>>> the new release.
>>>
>>> Cheers
>>> Björn
>>>
>>>
>>> 2015-02-06 3:19 GMT+01:00 Alan Ezust <ala...@gm...>:
>>>
>>>> Thank you Eric!!! (& Eric too!)
>>>>
>>>> Once again, you save the day!!
>>>>
>>>> --Alan
>>>>
>>>>
>>>>
>>>> ------------------------------------------------------------------------------
>>>> Dive into the World of Parallel Programming. The Go Parallel Website,
>>>> sponsored by Intel and developed in partnership with Slashdot Media, is
>>>> your
>>>> hub for all things parallel software development, from weekly thought
>>>> leadership blogs to news, videos, case studies, tutorials and more.
>>>> Take a
>>>> look and join the conversation now. http://goparallel.sourceforge.net/
>>>> --
>>>> -----------------------------------------------
>>>> jEdit Developers' List
>>>> jEd...@li...
>>>> https://lists.sourceforge.net/lists/listinfo/jedit-devel
>>>>
>>>>
>>>
>>
>>
>> --
>> Learn from the past. Live in the present. Work towards the future.
>> Blog: http://eric-berry.blogspot.com
>> jEdit <http://www.jedit.org> - Programmer's Text Editor
>>
>
>

If you just want the jEdit API in your browser, you don't have to install
the HelpServer plugin, just open the API with your browser.
It is plain HTML files in the jEdit installation directory. :-)

2015-03-01 16:24 GMT+01:00 Edward Diener <eld...@tr...>:

> On 3/1/2015 7:44 AM, Eric Le Lay wrote:
> > HelpServer is released now: http://plugins.jedit.org/plugins/?HelpServer
>
> It would be real nice if the help server could be turned on or off as
> the Help viewer after being installed. I need HelpServer to view the
> JEdit API since the font in normal Help is way too small to see, but
> otherwise I like normal Help a bit more. But once I install the Help
> Server plugin I always get Help Server help in my browser.
>
> >
> > Regarding packaging JavaFX, there are native libraries for webview
> > (webkit), and scene-graph (3D stuff).
> >
> > Cheers,
> > Eric
> >
> >
> > Le Sat, 28 Feb 2015 03:42:12 +0100,
> > Björn Kautler <Bj...@ka...> a écrit :
> >
> >> Eric wrote:
> >>
> >>> That's all well and good, but I want my help now :-)
> >>> jEdit 5.2 depends on java 1.7 so can't depend on JavaFX.
> >>
> >> Well yes and no. 1.7 supports JavaFX, you just have to ship the
> >> runtime environment.
> >> 1.8 just changes that it is shipped with the JRE (besides some
> >> updating)
> >>
> >>> Even current stable (5.1) can be supported by HelpServer, not by
> >>> JavaFX.
> >>
> >> Indeed, I didn't say that HelpServer is maybe not a great work-around
> >> for the existing versions.
> >> I just think that the goal should be a more integrated solution than
> >> having jEdit be a web server and look at the docs with a browser.
> >> Sometimes I don't want a browser open to save memory e. g. if on a
> >> restricted environment, or sometimes I use jEdit via port forwarding
> >> on a headless server where no browser is installed.
> >>
> >>> And there is no openjdk javafx for the 3 platforms I run
> >>> (ArchLinux, Fedora Core 19 and Mac OS 10.6).
> >>
> >> If there is Java 7, there should be JavaFX. As far as I have it in
> >> mind the JavaFX JAR is pure-java and thus should work on all of them,
> >> but I might be wrong.
> >>
> >>> Can you confirm that it also display the images, etc. referenced
> >>> from jeditresource: urls? e.g. can it display the JavaSideKick
> >>> plugin help icons?
> >>
> >> I didn't check this, no.
> >> And due to my work laptop where I did the experiments with the WebView
> >> meeting death,
> >> I lost what I did there and cannot easily test now.
> >>
> >>> Note that eclipse chose to have it both ways: an embedded web server
> >>> AND a native webview...
> >>
> >> Well, to be honest I think Eclipse is not a nice or useable program.
> >> I hear my colleagues rant about it on an hourly basis and each time
> >> I'm glad to have my IntelliJ IDEA.
> >> So Eclipse is not really a good argument for me. ;-)
> >> But yeah, noone stops you from doing this web server as plugin,
> >> that's the great thing at jEdit. :-)
> >>
> >>
> >>
> >> Alan wrote:
> >>
> >>> This is much easier to package with jEdit than JavaFX! Let's clone
> >>> it in
> >> jEdit's git, and make it integrate nice and tight.
> >>
> >> Well, to package JavaFX is just including a JAR file. To integrate it
> >> might need some work, yes.
> >> But due to many reasons some of which I stated above I still think
> >> that jEdit should provide a built-in help viewer like we have.
> >> Especially now with the HelpViewer plugin the situation is not as bad
> >> as it was anymore.
> >>
> >> But as this only hits developers that want to browse the JavaDocs, as
> >> the normal help is not affected,
> >> I'd say we should not ship the HelpServer plugin but provide it via
> >> Plugin Central as almost any other plugins if that was what you
> >> meant. :-)
> >>
> >>
> >> Cheers
> >> Björn
> >>
> >> 2014-12-03 23:38 GMT+01:00 Dale Anson <da...@da...>:
> >>
> >>> I finally got around to trying this, wish I'd done it earlier.
> >>> Really nice!
> >>>
> >>> On Mon, Nov 17, 2014 at 8:11 AM, Dale Anson <da...@da...>
> >>> wrote:
> >>>
> >>>> Actually, it looks like there is a general outage at sourceforge
> >>>> at the moment. I'll give it a try later.
> >>>>
> >>>> On Mon, Nov 17, 2014 at 8:10 AM, Dale Anson <da...@da...>
> >>>> wrote:
> >>>>
> >>>>> Eric, I wanted to give this a try, but I'm getting an error page
> >>>>> from sourceforge for
> >>>>> https://sourceforge.net/u/kerik-sf/helpserver/ci/master/tree/. Any
> >>>>> chance you can post the plugin jar somewhere easily accessible?
> >>>>>
> >>>>> Thanks,
> >>>>>
> >>>>> Dale
> >>>>>
> >>>>>
> >>>>>
> >>>>> On Wed, Nov 5, 2014 at 11:28 PM, Alan Ezust <ala...@gm...>
> >>>>> wrote:
> >>>>>
> >>>>>>
> >>>>>>
> >>>>>> On Wed, Oct 29, 2014 at 11:13 AM, Eric Le Lay <
> >>>>>> ker...@us...> wrote:
> >>>>>>
> >>>>>>> That's all well and good, but I want my help now :-)
> >>>>>>>
> >>>>>> +1!
> >>>>>>
> >>>>>>> jEdit 5.2 depends on java 1.7 so can't depend on JavaFX.
> >>>>>>> Even current stable (5.1) can be supported by HelpServer, not by
> >>>>>>> JavaFX.
> >>>>>>>
> >>>>>>
> >>>>>> I just tried the helpserver plugin and it is really nice!
> >>>>>> This is much easier to package with jEdit than JavaFX! Let's
> >>>>>> clone it in jEdit's git, and make it integrate nice and tight.
>
>
>
>
> ------------------------------------------------------------------------------
> Dive into the World of Parallel Programming The Go Parallel Website,
> sponsored
> by Intel and developed in partnership with Slashdot Media, is your hub for
> all
> things parallel software development, from weekly thought leadership blogs
> to
> news, videos, case studies, tutorials and more. Take a look and join the
> conversation now. http://goparallel.sourceforge.net/
> --
> -----------------------------------------------
> jEdit Developers' List
> jEd...@li...
> https://lists.sourceforge.net/lists/listinfo/jedit-devel
>

Hello Jesse,

thanks for your report.
I've created https://sourceforge.net/p/jedit/bugs/3913/ to track the bug
and will work on it.

Cheers,
Eric

Le Sat, 28 Mar 2015 19:12:22 -0400,
Jesse Pavel <jp...@al...> a écrit :

> Hello all,
> 
> The original BeanShell has a bug that causes do-while loops to skip
> checking its condition if a continue statement is encountered before
> the loop has completed its first iteration.
> 
> This is shown more clearly in the beanshell2 bug report:
> 
>   https://code.google.com/p/beanshell2/issues/detail?id=57
> 
> Looking at org.gjt.sp.jedit.bsh.BSHWhileStatement.java, it seems that
> jEdit's internal beanshell is subject to the same bug.
> 
> The beanshell2 project fixed it with a patch that (I think?) can be
> applied to jEdit's source as-is,
> 
> 
> https://code.google.com/p/beanshell2/source/diff?spec=svn100&r=100&format=side&path=/trunk/src/bsh/BSHWhileStatement.java
> 
> Best,
> Jesse