Hi Luiz, I do not know the exact differences, but high-level we tend to use the "release version" because:
- There are less files -> smaller size - It will download the compiled DSpace jars at build time so you don't have to build them yourself -> faster builds - Compared to cloning from the official Github repository, you don't have to upload the entire DSpace history to your Git server -> smaller Git footprint - There is a nice separation between the official DSpace code and your own customisations. The repository contains only our own modifications (except for the config files). [image: logo] Tom Desair 250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586 Esperantolaan 4, Heverlee 3001, Belgium www.atmire.com <http://atmire.com/website/?q=services&utm_source=emailfooter&utm_medium=email&utm_campaign=tomdesair> 2016-12-07 23:15 GMT+01:00 Luiz dos Santos <[email protected]>: > Sure, let me reformulate my question, what is the difference between the > build configuration in the "development version" and "release version", for > example, I got that the configuration of the maven "license-maven-plugin" > is different in the pom.xml is different, it makes sense, because in the > end of the day the files are not there, in the release version, so there is > less to check, but I wonder where else there is a difference (maybe > assembly plugin)? > > Sorry George, out of topic, but I am curious about it, and I guess your > question was already answered, right? > > Thanks > Luiz Claudio Santos > http://luizclaudiosantos.me/ > > On Wed, Dec 7, 2016 at 4:38 PM, Tom Desair <[email protected]> wrote: > >> No you cannot just delete them. You have to start from the correct format. >> >> DSpace is always released under two formats: a "release-src" archive that >> contains the full DSpace source as it can be found on Github and a >> "release" archive that only contains the configuration files and some >> folders where you can put Java customisations. The "release" version will >> download the (compiled) DSpace source code at build time from Maven. >> >> The example repository uses this "release" version. For DSpace 6, you can >> download that version here https://github.com/DSpace >> /DSpace/releases/download/dspace-6.0/dspace-6.0-release.tar.gz ( >> https://github.com/DSpace/DSpace/releases/tag/dspace-6.0) >> >> >> [image: logo] Tom Desair >> 250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586 >> Esperantolaan 4, Heverlee 3001, Belgium >> www.atmire.com >> <http://atmire.com/website/?q=services&utm_source=emailfooter&utm_medium=email&utm_campaign=tomdesair> >> >> >> 2016-12-07 21:31 GMT+01:00 Luiz dos Santos <[email protected]>: >> >>> Hi Tom, >>> >>> One question, the repository that you add the link there are some >>> folders missing, such as dspace-jspui, dspace-api, dspace-oai... How did >>> you do that? Just delete it? Do you add these as dependencies somewhere >>> else? >>> >>> Thanks in advance >>> Luiz Claudio Santos >>> http://luizclaudiosantos.me/ >>> >>> On Wed, Dec 7, 2016 at 3:19 PM, Tom Desair <[email protected]> >>> wrote: >>> >>>> Hi all, >>>> >>>> The general approach we use, is to download the release version of >>>> DSpace (note: note the src-release version) which is very small and push >>>> this to a Git repository. Then we save all our customisations in the >>>> relevant module directory. This process is described here: >>>> https://wiki.duraspace.org/display/DSDOC5x/Advanced+Customisation >>>> >>>> An open source example of a highly customised DSpace using this >>>> technique can be found here: https://github.com/milie >>>> uinfo/dspace54-atmire/tree/java-DEV >>>> >>>> Best regards, >>>> Tom >>>> >>>> >>>> [image: logo] Tom Desair >>>> 250-B Suite 3A, Lucius Gordon Drive, West Henrietta, NY 14586 >>>> Esperantolaan 4, Heverlee 3001, Belgium >>>> www.atmire.com >>>> <http://atmire.com/website/?q=services&utm_source=emailfooter&utm_medium=email&utm_campaign=tomdesair> >>>> >>>> 2016-12-07 20:45 GMT+01:00 Alan Orth <[email protected]>: >>>> >>>>> Hi, George. >>>>> >>>>> You should absolutely be using a git-based workflow. First, git is fun >>>>> and cool and much better in every way than CVS/SVN, but it's also the >>>>> official version control of the DSpace project itself since about 2014 >>>>> or so. This is important for cherry-picking patches, rebasing your >>>>> local changes on top of upstream point releases, etc. >>>>> >>>>> Second, GitHub is great. We forked DSpace's DSpace repository there >>>>> and I cherry-pick commits from their branch from time to time, as well >>>>> as rebase on their point releases as I mentioned above. Even though >>>>> I'm basically the only technical one doing DSpace on our team, I make >>>>> *extensive* use of GitHub other features like issues, pull requests, >>>>> and wikis. For example, when a user reports a bug or feature, I create >>>>> an issue to track it, then when I get time to address it I make a pull >>>>> request to my institution's repository from my personal repository. >>>>> >>>>> Here's our repo, where all of our code is (~25 Mirage 2 themes, custom >>>>> input forms, etc): >>>>> >>>>> https://github.com/ilri/DSpace >>>>> >>>>> On Wed, Dec 7, 2016 at 9:34 PM, Luiz dos Santos <[email protected]> >>>>> wrote: >>>>> > Hi, >>>>> > >>>>> > We have code in github and svn. The svn is old version that >>>>> Atmire >>>>> > folks are updating now. Soon, it's gonna github only, most of the >>>>> code of >>>>> > the code is in a maven repository, as a jar files, only the local >>>>> changes >>>>> > and config file are in the github repository. The developers have >>>>> their own >>>>> > maven profile in the main pom.xml, it helps a lot. >>>>> > >>>>> > Luiz Claudio Santos >>>>> > http://luizclaudiosantos.me/ >>>>> > >>>>> > On Wed, Dec 7, 2016 at 2:24 PM, Friesen, Darryl < >>>>> [email protected]> >>>>> > wrote: >>>>> >> >>>>> >> I’m very interested in this as well and would also love to hear >>>>> what the >>>>> >> community is doing. >>>>> >> >>>>> >> >>>>> >> >>>>> >> Our modifications have been very simple thus far -- a custom theme >>>>> based >>>>> >> on Mirage2; Shibboleth/authentication settings; facets >>>>> (discovery.xml); OAI >>>>> >> output formats; input forms (input-forms.xml); etc. No code >>>>> changes, just >>>>> >> config changes. >>>>> >> >>>>> >> >>>>> >> >>>>> >> Originally I tried keeping just changed files in our local SVN >>>>> repo, but >>>>> >> overlaying those changes onto the DSpace code, then building on out >>>>> dev, >>>>> >> test and prod boxes was a hassle. >>>>> >> >>>>> >> >>>>> >> >>>>> >> What I have now is a complete DSpace source tree committed to SVN. >>>>> I make >>>>> >> and test changes on our dev box, then commit to SVN when I have >>>>> things >>>>> >> working. Our test and prod boxes have working copies checked out >>>>> from SVN, >>>>> >> so I can do “svn update” to easily bring down my changes. I’m, not >>>>> super >>>>> >> happy with that either. >>>>> >> >>>>> >> >>>>> >> >>>>> >> We are moving from SVN to GitLab, so I’d like to investigate what >>>>> the >>>>> >> Continuous Integration features of GitLab might offer but I haven’t >>>>> had the >>>>> >> time. Another group on our campus is using Ansible to automate >>>>> deployment >>>>> >> of software (they specifically mentioned pulling code from Github, >>>>> applying >>>>> >> local customizations, then building and deploying – exactly what I >>>>> want for >>>>> >> DSpace). I haven’t had time to investigate that either. :( >>>>> >> >>>>> >> >>>>> >> >>>>> >> - Darryl >>>>> >> >>>>> >> >>>>> >> >>>>> >> >>>>> >> >>>>> >> ------------------------------------------------------------ >>>>> ---------- >>>>> >> >>>>> >> Darryl Friesen, B.Sc., Programmer/Analyst >>>>> [email protected] >>>>> >> >>>>> >> Library Systems & Information Technology, >>>>> http://library.usask.ca/ >>>>> >> >>>>> >> University of Saskatchewan Library >>>>> >> >>>>> >> ------------------------------------------------------------ >>>>> ---------- >>>>> >> >>>>> >> "Go not to the Elves for counsel, for they will say both no and yes" >>>>> >> >>>>> >> >>>>> >> >>>>> >> >>>>> >> >>>>> >> >>>>> >> >>>>> >> From: [email protected] [mailto:dspace-tech@googlegrou >>>>> ps.com] >>>>> >> On Behalf Of George Kozak >>>>> >> Sent: Wednesday, December 7, 2016 12:33 PM >>>>> >> To: DSpace Technical Support <[email protected]> >>>>> >> Subject: [dspace-tech] Question about DSpace code and version >>>>> control of >>>>> >> local mods >>>>> >> >>>>> >> >>>>> >> >>>>> >> Hi, >>>>> >> >>>>> >> I've been working with DSpace at Cornell University since 2002 and >>>>> for the >>>>> >> most part by myself, but now, with more people are working with me, >>>>> we would >>>>> >> like to have more version control over our local mods to the code >>>>> base. I >>>>> >> am curious as to how other people are dealing with this. Has anyone >>>>> placed >>>>> >> their local code mods in github and if so, what are they putting up >>>>> in >>>>> >> github? Just their local mods or the whole code base? >>>>> >> >>>>> >> >>>>> >> >>>>> >> -- >>>>> >> >>>>> >> *************************** >>>>> >> George Kozak >>>>> >> Digital Library Specialist >>>>> >> Cornell University Library - IT >>>>> >> 218 Olin Library >>>>> >> Cornell University >>>>> >> Ithaca, NY 14853 >>>>> >> 607-255-8924 >>>>> >> >>>>> >> [email protected] >>>>> >> >>>>> >> -- >>>>> >> You received this message because you are subscribed to the Google >>>>> Groups >>>>> >> "DSpace Technical Support" group. >>>>> >> To unsubscribe from this group and stop receiving emails from it, >>>>> send an >>>>> >> email to [email protected]. >>>>> >> To post to this group, send email to [email protected]. >>>>> >> Visit this group at https://groups.google.com/group/dspace-tech. >>>>> >> For more options, visit https://groups.google.com/d/optout. >>>>> >> >>>>> >> -- >>>>> >> You received this message because you are subscribed to the Google >>>>> Groups >>>>> >> "DSpace Technical Support" group. >>>>> >> To unsubscribe from this group and stop receiving emails from it, >>>>> send an >>>>> >> email to [email protected]. >>>>> >> To post to this group, send email to [email protected]. >>>>> >> Visit this group at https://groups.google.com/group/dspace-tech. >>>>> >> For more options, visit https://groups.google.com/d/optout. >>>>> > >>>>> > >>>>> > -- >>>>> > You received this message because you are subscribed to the Google >>>>> Groups >>>>> > "DSpace Technical Support" group. >>>>> > To unsubscribe from this group and stop receiving emails from it, >>>>> send an >>>>> > email to [email protected]. >>>>> > To post to this group, send email to [email protected]. >>>>> > Visit this group at https://groups.google.com/group/dspace-tech. >>>>> > For more options, visit https://groups.google.com/d/optout. >>>>> >>>>> >>>>> >>>>> -- >>>>> Alan Orth >>>>> [email protected] >>>>> https://englishbulgaria.net >>>>> https://alaninkenya.org >>>>> https://mjanja.ch >>>>> "In heaven all the interesting people are missing." ―Friedrich >>>>> Nietzsche >>>>> GPG public key ID: 0x8cb0d0acb5cd81ec209c6cdfbd1a0e09c2f836c0 >>>>> >>>>> -- >>>>> You received this message because you are subscribed to the Google >>>>> Groups "DSpace Technical Support" group. >>>>> To unsubscribe from this group and stop receiving emails from it, send >>>>> an email to [email protected]. >>>>> To post to this group, send email to [email protected]. >>>>> Visit this group at https://groups.google.com/group/dspace-tech. >>>>> For more options, visit https://groups.google.com/d/optout. >>>>> >>>> >>>> >>> >> > -- > You received this message because you are subscribed to the Google Groups > "DSpace Technical Support" group. > To unsubscribe from this group and stop receiving emails from it, send an > email to [email protected]. > To post to this group, send email to [email protected]. > Visit this group at https://groups.google.com/group/dspace-tech. > For more options, visit https://groups.google.com/d/optout. > -- You received this message because you are subscribed to the Google Groups "DSpace Technical Support" group. To unsubscribe from this group and stop receiving emails from it, send an email to [email protected]. To post to this group, send email to [email protected]. Visit this group at https://groups.google.com/group/dspace-tech. For more options, visit https://groups.google.com/d/optout.
