Hello, > Benjamin Li wrote: >> Hi, >> >> I'm kinda new to dspace and used eclipse before, but only for >> self-contained projects. >> >> So we're trying to customize dspace, and we want to use eclipse to do >> this because the tomcat plugin makes it alot easier. We've checked >> out >> the source fine from the But we also want our customizations to be on >> a source control system like subversion. >> >> So does anyone have any idea how to setup eclipse to manage this? >> Should I setup a new project that checks out sources from the >> subversion repo, using Maven or something? I'm not quite sure how to >> do that.
Am 04.08.2007 um 05:00 schrieb zxie.dspace: > http://wiki.dspace.org/index.php/Guide_to_Developing_with_DSpace I bet, that is not the whole answer, although there were a lot of helpful hints added to the wiki recently, notably to this page: <http://wiki.dspace.org/index.php/IDE_Integration:_DSpace% 2C_Eclipse_and_Tomcat> I personally dont get my feet on the ground with eclipse. Yesterday I tried again and did not succeed. For me, it is a problematic thing that the whole project and its whole structure depend more an more and working with eclipse which might be prohibitive to some people. Eclipse loads updates over several hours, adding up to hundreds of megabytes per month, much more than the initial download and restarts itself several times during this process. I have never seen such a complicated online update in any system. And you cant remove any of the update sources that you did not add yourself even if you are not interested in the functionality they provide. Ok, but after telling about my personal annoyance with eclipse that everybody else seems to love, back to working with two source code repositories. You can add several repositories to Eclipse but you cant change between them for the same projects as far as I can see. This is because the administrative data inside you source tree makes assumptions about the upstream repo to compare with when telling you things about current status in your local directory. This is the same problem that I have when working with the command line client and my favourite text editor. I solved for me by deciding that I dont follow the current source. Instead, I download the latest stable release and put everything inside my local svn repo. I look into the official repo from time to time, read commit messages and would merge manually if there were some security fixes or major functional enhancements, but that has not been the case so far. All the tips about branching and merging in the svn book, which BTW helped me a lot does not touch this issue. I dont think that this is DSpace specific although DSpace users might be more willing to develop their own branch than is usual with other Open Source Projects. To a certain extent, this has to do with the missing feature of templates for front end design. So with manakin, there will go away one major reason for keeping you own tree. For me, the best solution would be a Subversion feature that allows you to specify different repos for trunk and branch. You would merge to branch then, which is your local repo. In a sense that means sup- porting three way diff from ground up. I you are about to write a feature request for subversion, I would join in. Bye, Christian ------------------------------------------------------------------------- This SF.net email is sponsored by: Splunk Inc. Still grepping through log files to find problems? Stop. Now Search log events and configuration files using AJAX and a browser. Download your FREE copy of Splunk now >> http://get.splunk.com/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
