Hi Jun, glad to have you aboard.
The others have already answered your questions... For the moment what I suggest is that you checkout the code from SVN and work from there. For the community bonding period I would say to start from http://jira.xwiki.org/jira/browse/XECLIPSE-150 which, as Sergiu said, was created especially for you :) This will give us a stable, standard building environment to start with. Some history... The current building infrastructure is an ad-hoc solution to integrate Eclipse plugin build with Maven. This was done because at that time there was no standard solution to do this, and building Eclipse plugins from outside the the PDE was a pain. Now project Tycho seems to have inverted this trend and provides a nice and maven-oriented way to build Eclipse plugins (and features, and update sites, etc.) from the command line. Basically what we needed. Thanks, Fabio On Sun, May 1, 2011 at 8:24 PM, Jun Han <[email protected]> wrote: > Dear all, > > First of all, I am very glad that I can participate in the GSOC project > and thanks a lot for giving this great oppotunity. > > During the Community bonding period, I will look at the JIRA issues > about XEclipse. > > However, I have several questions about XEclipse development: > 1. Now the whole XWiki project is moving to github, where would XEclipse > project be hosted, in SVN or git? I searched for XEclipse in github, and > do not find a related entry. > > 2. what is the build method, using maven, Tycho or just in Eclipse IDE? > This is related to XEclipse-150 issue In JIRA, which requires the whole > XEclipse project to be built from maven and Tycho. I can already run > XEclipse from Eclipse IDE. But if maven is to be used, I think I will > learn some maven as well. > > Best regards > Jun Han > _______________________________________________ > devs mailing list > [email protected] > http://lists.xwiki.org/mailman/listinfo/devs > _______________________________________________ devs mailing list [email protected] http://lists.xwiki.org/mailman/listinfo/devs
