From: Björn K. <Bj...@ka...> - 2015-04-17 23:35:00
|
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 > |