| RE: [ve-dev] Re: How to be a contributor to the VE project (was Re: VE Question.) |
Nick, I am not sure whether bringing this to your attention is necessary but I thought, what the heck, maybe someone else may benefit from this. I followed the procedure you set out at http://wiki.eclipse.org/VE/Building#Fetch_Sources. Everything downloaded correctly. Except for the following exception everything build smoothly. There are some compilation dependencies in the /org.eclipse.releng.basebuilder project which do not seem to resolve. 1. It depends on a j2ee.jar. 2. Some of the dependencies still reference older/previous versions of jar's (See attached image) I can resolve all the errors with outdated dependencies by replacing them with others in the plugins folder, but for the j2ee.jar I had to add j2ee.jar to my private library and include it in the project, even though the project seems to reference a j2ee.jar in "eclipsInternalBuildTools". I cannot find this location in the projects. -----Original Message----- From: Nick Boldt [mailto:nickboldt@xxxxxxxxx] Sent: 08 Oktober 2009 05:57 To: Discussions people developing code for the Visual Editor project Cc: Snyman, Marius M Subject: Re: [ve-dev] Re: How to be a contributor to the VE project (was Re: VE Question.) Yves: Thanks - does this mean that the HEAD of VE sources will only compile for Eclipse 3.5 now? Any comments on encouraging community participation in this project? N yves (yingmin) yang wrote: >> I have in the meantime discovered the main culprit for my errors was a dependency on the dependencies tab of plugin.xml. >> >> I had errors because the version of com.ibm.icu on Galileo is 4.0.1 and the expected dependency was 3.something > > In Fact, it is already fixed in CVS > > yves >> All the project now compile successfully. >> >> >> >> >> -----Original Message----- >> From: Nick Boldt [mailto:nickboldt@xxxxxxxxx] >> Sent: 05 October 2009 10:32 PM >> To: Snyman, Marius M; Discussions people developing code for the Visual Editor project >> Subject: How to be a contributor to the VE project (was Re: VE Question.) >> >> Marius: >> >> To answer your question, I've created a wiki page to capture how best to >> set up a workspace for building VE (and JEM, since we build that as well). >> >> http://wiki.eclipse.org/VE/Building >> >> Let me know if that helps! (Or if anything's missing.) >> >> -- >> >> As every project is run a bit differently, the best advice I can give >> you is to talk to the project leads &/or active developers, read the >> mailing list posts to see what's going on in the project, etc. Get >> involved! As people learn your name, and see what you're capable of >> (eg., fixing bugs, submitting patches, contributing to architectural >> discussions/planning), you'll rise from 'interested user' to >> 'contributor' and maybe eventually committer. >> >> I've copied your question to the ve-dev@ mailing list so other active >> participants can chime in with what they would like to see from new >> members, and so other interested contributors can test out the wiki'd >> instructions above and see if they work for them. >> >> (I'm the guy who pokes the builds & website from time to time, but I'm >> not actively involved in the planning, development, or management of >> this project beyond that.) >> >> Joe? Yves? Anything to add? >> >> Nick >> >> Snyman, Marius M wrote: >>> Nick, I noticed you did the VE 1.4.0 R build. If you would be so kind to >>> assist me in getting started with the VE stuff. >>> >>> >>> >>> I have never before been a contributor to open-source. The primary >>> reason is that I do not know howe to get started. >>> >>> >>> >>> >>> >>> I have checked out the VE-ALL projects. There are sub-projects under >>> some other projects. >>> >>> >>> >>> If I open the projects in Eclipse I have a lot of errors regarding >>> dependencies for logging and concurrency, etc.. >>> >>> >>> >>> I would like to understand this. >>> >>> Must the project structures remain exactly as checked out? >>> >>> Must I download the dependencies from their respective web-sites? I have >>> done this for the concurrency.jar and when I included it in the project >>> I get deprecation errors on the JDT sources. >>> >>> Are there some basic guidelines somewhere on how to get actively >>> involved in a project. >>> >>> >>> >>> >>> >>> >>> >>> >>> >>> Kind regards. >>> >>> >>> >>> Marius Snyman >>> >>> Marius.Snyman@xxxxxxxxxxxxxxxxxxx >>> >>> 011 269 5591 >>> >>> >>> >>> ** >>> >>> ** >>> >>> *Standard Bank email disclaimer and confidentiality note* >>> >>> Please go to >>> http://www.standardbank.co.za/site/homepage/emaildisclaimer.html to read >>> our email disclaimer and confidentiality note. Kindly email >>> disclaimer@xxxxxxxxxxxxxxxxxx <mailto:disclaimer@xxxxxxxxxxxxxxxxxx> (no >>> content or subject line necessary) if you cannot view that page and we >>> will email our email disclaimer and confidentiality note to you. >>> >>> >>> > -- Nick Boldt :: http://nick.divbyzero.com Release Engineer :: Eclipse Modeling & Dash Athena
Attachment:
Dependencies Problem.png
Description: Dependencies Problem.png
