Re: [jdt-ui-dev] Regarding build of eclipse.jdt.ui

[Parag Jain <parag00991@xxxxxxxxx>]

Are you talking about importing all the code in eclipse IDE?

And instead of submitting my changes to gerrit , can't I submit a pull request on github as I'm not familiar about gerrit.

On Sat, Jan 16, 2016 at 6:53 PM, Stephan Herrmann <stephan.herrmann@xxxxxxxxx> wrote:

As to building: Eclipse takes care of it, just check that the following
menu option is enabled: Project > Build automatically.

As to testing: You'll write your own JUnit tests and execute them
via "Run as ... > JUnit Plug-in Test".

As to checking whether you've broken anything: either run all JUnit
tests locally, or submit your change to gerrit and let hudson do
the testing.

You can read all the details in the mentioned wiki page.
Look for "Unit Testing" and "Contributing a change".


best,
Stephan

On 01/16/2016 02:17 PM, Parag Jain wrote:

But suppose, if I improve any feature or fixed some bug , then how would I get to know whether the bug is fixed or the new feature
has been added or not without executing or building the code. Don't you think there should be some building process for the code?

On Sat, Jan 16, 2016 at 6:38 PM, Stephan Herrmann <stephan.herrmann@xxxxxxxxx <mailto:stephan.herrmann@xxxxxxxxx>> wrote:

    Hi Parag,

    Have you seen https://wiki.eclipse.org/JDT_UI/How_to_Contribute ?
    Once you have the projects in your workspace, you should be
    ready to code, no additional build steps required.

    HTH,
    Stephan

_______________________________________________
jdt-ui-dev mailing list
jdt-ui-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/jdt-ui-dev