Some Eclipse Foundation services are deprecated, or will be soon. Please ensure you've read this important communication.
Bug 365454 - Document local building on wiki
Summary: Document local building on wiki
Status: RESOLVED FIXED
Alias: None
Product: Linux Tools
Classification: Tools
Component: Project (show other bugs)
Version: unspecified   Edit
Hardware: PC Linux
: P3 normal (vote)
Target Milestone: ---   Edit
Assignee: Daniel Henrique Barboza CLA
QA Contact:
URL:
Whiteboard:
Keywords:
Depends on:
Blocks:
 
Reported: 2011-12-02 11:13 EST by Andrew Overholt CLA
Modified: 2011-12-14 15:15 EST (History)
2 users (show)

See Also:


Attachments

Note You need to log in before you can comment on or make changes to this bug.
Description Andrew Overholt CLA 2011-12-02 11:13:49 EST
In bug 364198, Daniel hinted that he had difficulties building locally using maven:

> After the tips from Jeff I was able to build Linuxtools successfully, with all
> Helgrind tests plug-in passing the tests.

Daniel, could you add those tips to the wiki somewhere?  I'm thinking a new "Building Locally" section on this page:

  http://wiki.eclipse.org/Linux_Tools_Project/Getting_Involved

Just log in with your bugzilla credentials.  Thanks!
Comment 1 Daniel Henrique Barboza CLA 2011-12-13 07:02:12 EST
Hi Andrew,

Just checked that there is already a section named "Building locally". It's in the middle of the text of the Automated Builds section:


"We use the Eclipse Hudson server to run continuous integration builds when changes are pushed to our Git repository. Every 6 hours we poll for Git changes and if they have occurred, we run a full build using Tycho and run all unit tests. See instructions for **building locally** for how to perform a full local build."

The instructions of the page are accurate, I would just add something about building while skipping unit tests and how to not build from an specific directory (ex: helgrind)  to avoid getting dependencies not resolved from the parent dir.


Do you want me to just add these info in the existing page or should I go on and (re)create the section at the Getting Involved page?
Comment 2 Andrew Overholt CLA 2011-12-13 10:05:03 EST
It would be best if you could add your comments to the existing section and put a link to it on the Getting Involved page.

Thanks, Daniel!
Comment 3 Daniel Henrique Barboza CLA 2011-12-14 11:12:31 EST
I'm experiencing the following error when trying to edit the contents of the page:

"You do not have permission to do that, for the following reason:
The action you have requested is limited to users in the group user."


Probably someone needs to give me permission to edit the wiki ... or simply add the lines

* You can add the parameter "-Dmaven.test.skip=true" for debug purposes, but remember that no patch that breaks the unit tests will be acceptable.
* Some components have dependencies between then, for example Valgrind plug-ins. In that case, always build the whole valgrind suite instead of one particular plug-in.

At the "Building locally" section of the page

http://wiki.eclipse.org/Linux_Tools_Project/Releng#Building_locally

The section "Automated Builds" already have a link for this section above.
Comment 4 Andrew Overholt CLA 2011-12-14 11:34:15 EST
(In reply to comment #3)
> I'm experiencing the following error when trying to edit the contents of the
> page:
> 
> "You do not have permission to do that, for the following reason:
> The action you have requested is limited to users in the group user."

Are you logged in with your bugzilla username/password?  That's all you need.  There are no special permissions for the page.
Comment 5 Daniel Henrique Barboza CLA 2011-12-14 12:50:25 EST
Hmmm my Firefox made me a fool ... I was logged in but probably with session expired. Tried a logout/login and now I can edit the page :)

I've changed the text a bit and now it looks like this:



* You can add the parameter "-Dmaven.test.skip=true" for debug purposes, but remember that no contribution that breaks the unit tests will be accepted.

* Some components have dependencies between then, for example Valgrind plug-ins. In that case, always build the whole Valgrind suite instead of one
particular plug-in.


I've saved these changes. Let me know if I need to change/add something.
Comment 6 Andrew Overholt CLA 2011-12-14 15:15:17 EST
It looks great, Daniel.  Thanks!