[Dspace-devel] [DuraSpace JIRA] Resolved: (DS-733) Tools for (load) testing
[ https://jira.duraspace.org/browse/DS-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Triggs resolved DS-733. -- Resolution: Fixed > Tools for (load) testing > > > Key: DS-733 > URL: https://jira.duraspace.org/browse/DS-733 > Project: DSpace > Issue Type: New Feature >Reporter: Graham Triggs >Assignee: Graham Triggs > Fix For: 1.7.0 > > > Tools that are useful for testing purposes. Currently, this contains: > - a class that will parse a medline.xml file from PubMed (containing multiple > records) into DSpace packages > (allows for a large number of realistic records to be generated simply) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-733) Tools for (load) testing
[ https://jira.duraspace.org/browse/DS-733?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Triggs updated DS-733: - Documentation Status: Not Required (was: Needed) Status: Open (was: Received) > Tools for (load) testing > > > Key: DS-733 > URL: https://jira.duraspace.org/browse/DS-733 > Project: DSpace > Issue Type: New Feature >Reporter: Graham Triggs >Assignee: Graham Triggs > Fix For: 1.7.0 > > > Tools that are useful for testing purposes. Currently, this contains: > - a class that will parse a medline.xml file from PubMed (containing multiple > records) into DSpace packages > (allows for a large number of realistic records to be generated simply) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-743) ItemImport fails on large batches with OutOfMemory exception
[ https://jira.duraspace.org/browse/DS-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Triggs updated DS-743: - Status: Open (was: Received) > ItemImport fails on large batches with OutOfMemory exception > > > Key: DS-743 > URL: https://jira.duraspace.org/browse/DS-743 > Project: DSpace > Issue Type: Bug >Reporter: Graham Triggs >Priority: Major > Fix For: 1.7.0 > > > On large imports, ItemImport will throw an OutOfMemory exception - this is > because the context isn't having the cache cleared, so the Item objects that > are created are building up in memory. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Resolved: (DS-743) ItemImport fails on large batches with OutOfMemory exception
[ https://jira.duraspace.org/browse/DS-743?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Triggs resolved DS-743. -- Resolution: Fixed > ItemImport fails on large batches with OutOfMemory exception > > > Key: DS-743 > URL: https://jira.duraspace.org/browse/DS-743 > Project: DSpace > Issue Type: Bug >Reporter: Graham Triggs >Priority: Major > Fix For: 1.7.0 > > > On large imports, ItemImport will throw an OutOfMemory exception - this is > because the context isn't having the cache cleared, so the Item objects that > are created are building up in memory. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Resolved: (DS-734) Improve database efficiency
[ https://jira.duraspace.org/browse/DS-734?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Triggs resolved DS-734. -- Resolution: Fixed > Improve database efficiency > --- > > Key: DS-734 > URL: https://jira.duraspace.org/browse/DS-734 > Project: DSpace > Issue Type: Improvement >Reporter: Graham Triggs >Assignee: Graham Triggs > Fix For: 1.7.0 > > > Improve various parts of database access - ie. > - PreparedStatement and parameterized access for getnextid() (relatively > expensive as a statement / unparameterized) > - Where possible, convert DatabaseManager.create() / DatabaseManager.update() > to DatabaseManager.row() / DatabaseManager.insert() (delay inserting records > until you have the rest of the data for the row, thereby reducing an INSERT / > UPDATE sequence to just an INSERT. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Resolved: (DS-739) Improve performance of Lucene indexing
[ https://jira.duraspace.org/browse/DS-739?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Triggs resolved DS-739. -- Resolution: Fixed > Improve performance of Lucene indexing > -- > > Key: DS-739 > URL: https://jira.duraspace.org/browse/DS-739 > Project: DSpace > Issue Type: Improvement >Reporter: Graham Triggs >Assignee: Graham Triggs > Fix For: 1.7.0 > > > Adds a batch processing mode for Lucene indexes. > Can be controlled by calling DSIndexer.setBatchProcessingMode(boolean). > NB: If you set batch processing mode to true, ensure that you set it to > 'false' at the end of the batch to flush any unwritten documents. > The size of the batch can be controlled by setting a numeric value in > dspace.cfg for the property: search.batch.documents > By default, the size of the batch is 20 documents. > Additionally, there is the possibility to create a 'delayed index flusher'. > If a web application pushes multiple search requests (ie. a barrage or sword > deposits, or multiple quick edits in the ui), then this will combine them > into a single index update (up to the limit of the batch defined above). > To use the delayed update, set the property 'search.index.delay' in > dspace.cfg to the number of milliseconds to wait for an update. eg. > search.index.delay = 5000 > will hold a Lucene update in a queue for up to 5 seconds. After 5 seconds - > or the batch limit above is reached - all waiting updates will be written to > the Lucene index. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Resolved: (DS-732) Improve performance of browse
[ https://jira.duraspace.org/browse/DS-732?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Graham Triggs resolved DS-732. -- Resolution: Fixed > Improve performance of browse > - > > Key: DS-732 > URL: https://jira.duraspace.org/browse/DS-732 > Project: DSpace > Issue Type: Improvement >Reporter: Graham Triggs >Assignee: Graham Triggs >Priority: Major > Fix For: 1.7.0 > > > Profile browse and find improvements in performance -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Closed: (DS-746 ) Agentes bióticos de deterioro en Bibliotecas
[ https://jira.duraspace.org/browse/DS-746?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Donohue closed DS-746. -- Documentation Status: Not Required (was: Needed) Resolution: Incomplete Hi Miryam, I'm unsure what this Issue was supposed to refer to. Perhaps you've accidentally submitted this document to the wrong place? This system is our DSpace Issue Tracker. It is used to report issues, problems or bugs you've encountered with DSpace software or its documentation. For the time being, I'm going to close this issue, as it doesn't look to describe a problem or bug with DSpace software. If there is a reason to reopen it, we can do so later on. Thanks, - Tim > Agentes bióticos de deterioro en Bibliotecas > > > Key: DS-746 > URL: https://jira.duraspace.org/browse/DS-746 > Project: DSpace > Issue Type: Sub-task >Reporter: Miryam Torres Londoño > Attachments: conservamos_no5_agentesbioticos_dedeterioro.pdf > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Closed: (DS-745 ) Prototipo de Repositorio Institucional desde el área d e Bibliotecologia
[ https://jira.duraspace.org/browse/DS-745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Donohue closed DS-745. -- Documentation Status: Not Required (was: Needed) Resolution: Incomplete Hi Miryam, I'm unsure what this Issue was supposed to refer to. Perhaps you've accidentally submitted this document to the wrong place? This system is our DSpace Issue Tracker. It is used to report issues, problems or bugs you've encountered with DSpace software or its documentation. For the time being, I'm going to close this issue, as it doesn't look to describe a problem or bug with DSpace software. If there is a reason to reopen it, we can do so later on. Thanks, - Tim > Prototipo de Repositorio Institucional desde el área de Bibliotecologia > --- > > Key: DS-745 > URL: https://jira.duraspace.org/browse/DS-745 > Project: DSpace > Issue Type: Documentation >Reporter: Miryam Torres Londoño > Attachments: a04n35.pdf > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Closed: (DS-747 ) Prototipo de repositorios Institucional desde el área de Bibliotecología
[ https://jira.duraspace.org/browse/DS-747?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Tim Donohue closed DS-747. -- Documentation Status: Not Required (was: Needed) Resolution: Incomplete Hi Miryam, I'm unsure what this Issue was supposed to refer to. Perhaps you've accidentally submitted this document to the wrong place? This system is our DSpace Issue Tracker. It is used to report issues, problems or bugs you've encountered with DSpace software or its documentation. For the time being, I'm going to close this issue, as it doesn't look to describe a problem or bug with DSpace software. If there is a reason to reopen it, we can do so later on. Thanks, - Tim > Prototipo de repositorios Institucional desde el área de Bibliotecología > - > > Key: DS-747 > URL: https://jira.duraspace.org/browse/DS-747 > Project: DSpace > Issue Type: Documentation >Reporter: Miryam Torres Londoño > Attachments: a04n35.pdf > > -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] Recent Bamboo build failures -- trying to track down exact cause
Hi Developers, For those who subscribe to our 'dspace-change...@lists.sourceforge.net' listserv, you've surely noticed that all recent Trunk commits have thrown errors from Bamboo, as it attempts to build & test the latest code. I've been trying to track down the exact cause of these errors, but honestly could use a fresh pair of eyes. So, I thought I'd write to describe what I've figured it out so far. (1) First off, this is a real error (it's not Bamboo being finicky, or a problem with a Bamboo agent). Something in our recent commits has actually broken a *portion* of our Maven build processes. Although most Maven build commands work fine (e.g. 'mvn clean package'), our DSpace build process can no longer successfully do both a *package* and a *unit test*. For example, the following will fail with errors: mvn package test -Dmaven.test.skip=false (Note the '-Dmaven.test.skip=false' is only necessary to ensure the tests are actually run -- since we decided to disable our unit tests by default. If tests were enabled by default, then 'mvn package test' would throw the same error) The error that is returned is the same one reported by recent Bamboo builds, for example: https://bamboo.duraspace.org/browse/DST-TRUNK-212 (2) Oddly enough, just doing 'mvn package' or just doing 'mvn test -Dmaven.test.skip=false' both work fine. It's the *combination* of packaging & unit testing that is failing. (3) As you can see from the reported Bamboo error (see the 'full build log' in the linked Bamboo report above), the failure seems to be that the 'dspace-discovery-xmlui-webapp' project fails to build as it cannot seem to copy over the necessary 'dspace-xmlui-api' dependency. Obviously, this all works fine if you just do a normal 'mvn package' -- it's only problematic when you do both a package and unit test. So, it seems that something is essentially 'locking' the 'dspace-xmlui-api' from being accessed -- possibly something in the unit testing. (4) As best as I can tell, this problem first started occurring around the time that we reworked all our pom.xml files to use the common 'dspace-pom' parent. So, it may be the result of some odd inheritance between pom.xml files, again possibly around the unit testing configs. Here's the commits where this issue seemed to have first begun: https://fisheye3.atlassian.com/changelog/dspace?cs=5796 https://fisheye3.atlassian.com/changelog/dspace?cs=5797 If anyone has any ideas, I'd be willing to entertain suggestions (I'll be on IRC most all day). In the meantime, I'll keep digging around in our pom.xml files to see if I can discover the root cause here. - Tim -- Tim Donohue Technical Lead for DSpace Project DuraSpace.org -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Created: (DS-748) COinS in XMLUI has invalid referrer Id and dc metadata; spans are not properly constructed
COinS in XMLUI has invalid referrer Id and dc metadata; spans are not properly constructed -- Key: DS-748 URL: https://jira.duraspace.org/browse/DS-748 Project: DSpace Issue Type: Bug Components: XMLUI Affects Versions: 1.6.2, 1.6.1, 1.6.0 Reporter: Bill Hays 1. The referrerId is hard-coded as "dryad.org" and there doesn't seem to be a reasonably simple way to either pull a HTTP request parameter or a DSpace config property value and use that instead since the xsl transform at that point cannot reach the dri document. 2. The format identifier "dc" implies strict Dublin Core according to the OpenURL spec and the COinS online docs. Selectively using qdc seems to go against that. But trying to crosswalk qdc to dc also seems very difficult in the Manakin context. 3. What can be easily fixed is the wrapping of the COinS spans around item titles which clearly goes against basic practice as discussed in the COinS online docs. The problem here is that mouse rollovers inappropriately display popups of the context objects. It is also unclear to me whether the placing of multiiple COinS on result screens is sensible across different consuming applications for COinS. The spans should have not content except some whitespace to force the existence of a closing tag. These first two issues don't appear to be easy to fix and there is no way to turn off COinS without editing the DIMHandler xsl. So, by default, any given DSpace instance will be rendering invalid COinSs, though they may work for certain COinS-consuming applications. If no one can fix these issues in the near term, I recommend that the COinS implementation be removed from the trunk and a separate patch be made available with instructions for customizations for those wanting this feature. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] Recent Bamboo build failures -- trying to track down exact cause
I note that the build seems to start in [DSpace-source] rather than [DSpace-source]/dspace. Strange things happen when doing that. I've never worked out why. It definitely makes the Reactor build in a different order. -- Mark H. Wood, Lead System Programmer mw...@iupui.edu Balance your desire for bells and whistles with the reality that only a little more than 2 percent of world population has broadband. -- Ledford and Tyler, _Google Analytics 2.0_ pgpsUkuYAdabZ.pgp Description: PGP signature -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] Recent Bamboo build failures -- trying to track down exact cause
Hi Mark W, Unfortunately, your suggestion to change directories doesn't seem to matter. Locally, on my own machine, I can achieve the same error messages whether I run this command from [dspace-source] or [dspace-source]/dspace/ mvn package test -Dmaven.test.skip=false So, I don't think it's a problem with Bamboo (or how Bamboo is setup to run). I think it's a problem with our Maven pom.xml files -- as I can achieve the same errors even without using Bamboo. From what I've been able to tell searching around online, it's possible Maven is getting confused about dependency management. Digging into our pom.xml files, we have a ton of repetition between POMs -- where a child POM overwrites dependencies/settings with the same values as their parent POM. I've done some cleaning of the Discovery POMs locally (which seem to be the messiest and most repetitive -- likely cause it used to be a totally separate module). I *believe* I just succeeded in fixing the error reported in the building & testing of 'dspace-discovery-xmlui-webapp'. Unfortunately, now I'm getting the *exact same* error in the building & testing of 'dspace-xmlui-webapp' (again, based on 'dspace-xmlui-api' being unable to be copied properly). So, this may not be a single problem caused by a single POM -- it may be a problem of how several of our POMs are currently interacting (especially those that depend on 'dspace-xmlui-api'). After some more testing, I will commit some of my initial cleanup. Even if it doesn't fix the entire problem yet, it seems to be getting closer to some sort of resolution. Essentially, I believe our POMs need some overhaul -- we aren't taking advantage of inheritance in many places, and it seems like it may be confusing Maven to some extent. The smaller we can make most of the POMs the better. - Tim On 11/11/2010 1:49 PM, Mark H. Wood wrote: > I note that the build seems to start in [DSpace-source] rather than > [DSpace-source]/dspace. Strange things happen when doing that. I've > never worked out why. It definitely makes the Reactor build in a > different order. > > > > > -- > Centralized Desktop Delivery: Dell and VMware Reference Architecture > Simplifying enterprise desktop deployment and management using > Dell EqualLogic storage and VMware View: A highly scalable, end-to-end > client virtualization framework. Read more! > http://p.sf.net/sfu/dell-eql-dev2dev > > > > ___ > Dspace-devel mailing list > Dspace-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dspace-devel -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] Recent Bamboo build failures -- trying to track down exact cause
Firstly, it shouldn't matter, but the build was originally configured to be in [dspace-source] and only peform packaging and test of the addons, not the complete assembly. Inbetween traveling and meetings I've determined the error is caused because the dspace-ui-shared war overlays artifact is not getting properly attached in the maven reactor. We use overlays inside [dspace-source]/dspace for discovery and languages. In the case of languages, its an asyncronous release and we have no problems. In the case of discovery, it is in the build and the overlay will break if tests are run in that directory. I'm researching if I can get the artifact properly registered in the maven reactor. Alternatives are... 1.) move the dspace-ui-share dependencies out of dspace-jspui-webapp and dspace-xmlui-webapp and only build at [dspace-source] with -Paddons 2.) move dspace-ui-share into "modules" and release it asynchronously. 3.) copy the contents of dspace-ui-shared into both dspace-xmlui-webapp and dspace-jspui-webapp and get rid of it, only test from [dspace-source] with -Paddons. Given my past opinion on the contents of dspace-ui-shared not just being copied into the two other webapps, I prefer (3) and tolerate (1). I feel we are not quite ready for (2) Mark e build is for test On Thu, Nov 11, 2010 at 11:49 AM, Mark H. Wood wrote: > I note that the build seems to start in [DSpace-source] rather than > [DSpace-source]/dspace. Strange things happen when doing that. I've > never worked out why. It definitely makes the Reactor build in a > different order. > > -- > Mark H. Wood, Lead System Programmer mw...@iupui.edu > Balance your desire for bells and whistles with the reality that only a > little more than 2 percent of world population has broadband. > -- Ledford and Tyler, _Google Analytics 2.0_ > > -- > Centralized Desktop Delivery: Dell and VMware Reference Architecture > Simplifying enterprise desktop deployment and management using > Dell EqualLogic storage and VMware View: A highly scalable, end-to-end > client virtualization framework. Read more! > http://p.sf.net/sfu/dell-eql-dev2dev > ___ > Dspace-devel mailing list > Dspace-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dspace-devel > > -- Mark R. Diggory @mire - www.atmire.com 533 2nd Street - Encinitas, CA 92024 - USA Technologielaan 9 - 3001 Heverlee - Belgium -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] Recent Bamboo build failures -- trying to track down exact cause
On 11/11/2010 2:07 PM, Mark Diggory wrote: > I'm researching if I can get the artifact properly registered in the > maven reactor. Alternatives are... > > 1.) move the dspace-ui-share dependencies out of dspace-jspui-webapp > and dspace-xmlui-webapp and only build at [dspace-source] with > -Paddons > 2.) move dspace-ui-share into "modules" and release it asynchronously. > 3.) copy the contents of dspace-ui-shared into both > dspace-xmlui-webapp and dspace-jspui-webapp and get rid of it, only > test from [dspace-source] with -Paddons. > > Given my past opinion on the contents of dspace-ui-shared not just > being copied into the two other webapps, I prefer (3) and tolerate > (1). I feel we are not quite ready for (2) I'd vote for #3 -- personally, I've never really liked having 5 javascript files be their own "dspace-ui-share" module. Each interface should use it's own javascript as it needs to -- and not be reliant on using the same version of scriptaculous JS as the other UIs. - Tim -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
Re: [Dspace-devel] Recent Bamboo build failures -- trying to track down exact cause
On Thu, Nov 11, 2010 at 12:06 PM, Tim Donohue wrote: > Hi Mark W, > > Unfortunately, your suggestion to change directories doesn't seem to > matter. Locally, on my own machine, I can achieve the same error > messages whether I run this command from [dspace-source] or > [dspace-source]/dspace/ > > mvn package test -Dmaven.test.skip=false > > So, I don't think it's a problem with Bamboo (or how Bamboo is setup to > run). I think it's a problem with our Maven pom.xml files -- as I can > achieve the same errors even without using Bamboo. As I said. And we will want to consider Bamboo a "test execution environment" we may do releasing there sometime soon. But doing the complete assembly there yet isn't a requirement for the release. > > From what I've been able to tell searching around online, it's possible > Maven is getting confused about dependency management. Digging into our > pom.xml files, we have a ton of repetition between POMs -- where a child > POM overwrites dependencies/settings with the same values as their > parent POM. yes, the dspace-ui-shared not getting attached. > > I've done some cleaning of the Discovery POMs locally (which seem to be > the messiest and most repetitive -- likely cause it used to be a totally > separate module). I *believe* I just succeeded in fixing the error > reported in the building & testing of 'dspace-discovery-xmlui-webapp'. > Unfortunately, now I'm getting the *exact same* error in the building & > testing of 'dspace-xmlui-webapp' (again, based on 'dspace-xmlui-api' > being unable to be copied properly). So, this may not be a single > problem caused by a single POM -- it may be a problem of how several of > our POMs are currently interacting (especially those that depend on > 'dspace-xmlui-api'). I don't think that discovery was the original problem I was experiencing on my end. And that you are now having the same problem I am. Whcih version maven are you building with, we need to try to be on 2.2.1 or greater. > > After some more testing, I will commit some of my initial cleanup. Even > if it doesn't fix the entire problem yet, it seems to be getting closer > to some sort of resolution. The fixes I proposed are about 6 lines of code that clearup the issue for getting bamboo to operate properly. Likewise, as long as tests are run as mvn test -Paddons from the [dspace-src] you should be safe with the assembly process working. > > Essentially, I believe our POMs need some overhaul -- we aren't taking > advantage of inheritance in many places, and it seems like it may be > confusing Maven to some extent. The smaller we can make most of the > POMs the better. We need to be very cautious about using inheritance in poms, the asyncronous release and the usage of dspace-pom as an external pom are there for a specific purpose. I've gone through the things that should and should not be inherited several time in tuning it up. The more you inherit, the fewer options you leave for turning things off in the children. > > - Tim > > On 11/11/2010 1:49 PM, Mark H. Wood wrote: >> I note that the build seems to start in [DSpace-source] rather than >> [DSpace-source]/dspace. Strange things happen when doing that. I've >> never worked out why. It definitely makes the Reactor build in a >> different order. >> >> >> >> >> -- >> Centralized Desktop Delivery: Dell and VMware Reference Architecture >> Simplifying enterprise desktop deployment and management using >> Dell EqualLogic storage and VMware View: A highly scalable, end-to-end >> client virtualization framework. Read more! >> http://p.sf.net/sfu/dell-eql-dev2dev >> >> >> >> ___ >> Dspace-devel mailing list >> Dspace-devel@lists.sourceforge.net >> https://lists.sourceforge.net/lists/listinfo/dspace-devel > > -- > Centralized Desktop Delivery: Dell and VMware Reference Architecture > Simplifying enterprise desktop deployment and management using > Dell EqualLogic storage and VMware View: A highly scalable, end-to-end > client virtualization framework. Read more! > http://p.sf.net/sfu/dell-eql-dev2dev > ___ > Dspace-devel mailing list > Dspace-devel@lists.sourceforge.net > https://lists.sourceforge.net/lists/listinfo/dspace-devel > -- Mark R. Diggory @mire - www.atmire.com 533 2nd Street - Encinitas, CA 92024 - USA Technologielaan 9 - 3001 Heverlee - Belgium -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Dspace-d
[Dspace-devel] [DuraSpace JIRA] Updated: (DS-525) Move item - inherit default policies of destination collection
[ https://jira.duraspace.org/browse/DS-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis updated DS-525: Attachment: [DS-525]_Move_item_-_inherit_default_policies_of_destination_collection_5827.patch Second version of the patch - same as before, but against trunk revision 5827, as a lot of code has changed since the patch was first written. > Move item - inherit default policies of destination collection > -- > > Key: DS-525 > URL: https://jira.duraspace.org/browse/DS-525 > Project: DSpace > Issue Type: New Feature > Components: DSpace API, JSPUI, XMLUI >Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0 >Reporter: Stuart Lewis >Priority: Major > Fix For: 1.7.0 > > Attachments: > [DS-525]_Move_item_-_inherit_default_policies_of_destination_collection.patch, > > [DS-525]_Move_item_-_inherit_default_policies_of_destination_collection_5827.patch > > > When using the UI to move an item, the item is moved, and it takes its authZ > policies with it, > However, a common use case is to move an item from a dark collection, to an > open collection. In this case, it is desired behaviour for the authZ policies > to be updated to the default policies of the destination collection. > This patch gives a new checkbox for jspui and xmlui to allow the destination > policy to be inherited. By default the checkbox is unchecked. > The API has been updated to add this as a boolean option on the Item.moveItem > method. > The patch also fixes two bugs with the xmlui move item function: > 1) When selecting which collection to move the item to, the collection that > is is currently in is no longer listed. > 2) Previously a new authZ policy was added to the item to allow the admin to > move the item. This was not removed once the item had been moved. If an item > was moved multiple times, lots of these policies were left in the item. > Instead, the patch updates it to set a temporary action allowing this, rather > than a policy. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Resolved: (DS-525) Move item - inherit default policies of destination collection
[ https://jira.duraspace.org/browse/DS-525?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Stuart Lewis resolved DS-525. - Documentation Status: Complete or Committed (was: Needed) Resolution: Fixed Assignee: Stuart Lewis Added documentation, with warning about embargoes: https://wiki.duraspace.org/pages/diffpages.action?pageId=22022835&originalId=22547177 > Move item - inherit default policies of destination collection > -- > > Key: DS-525 > URL: https://jira.duraspace.org/browse/DS-525 > Project: DSpace > Issue Type: New Feature > Components: DSpace API, JSPUI, XMLUI >Affects Versions: 1.5.0, 1.5.1, 1.5.2, 1.6.0 >Reporter: Stuart Lewis >Assignee: Stuart Lewis >Priority: Major > Fix For: 1.7.0 > > Attachments: > [DS-525]_Move_item_-_inherit_default_policies_of_destination_collection.patch, > > [DS-525]_Move_item_-_inherit_default_policies_of_destination_collection_5827.patch > > > When using the UI to move an item, the item is moved, and it takes its authZ > policies with it, > However, a common use case is to move an item from a dark collection, to an > open collection. In this case, it is desired behaviour for the authZ policies > to be updated to the default policies of the destination collection. > This patch gives a new checkbox for jspui and xmlui to allow the destination > policy to be inherited. By default the checkbox is unchecked. > The API has been updated to add this as a boolean option on the Item.moveItem > method. > The patch also fixes two bugs with the xmlui move item function: > 1) When selecting which collection to move the item to, the collection that > is is currently in is no longer listed. > 2) Previously a new authZ policy was added to the item to allow the admin to > move the item. This was not removed once the item had been moved. If an item > was moved multiple times, lots of these policies were left in the item. > Instead, the patch updates it to set a temporary action allowing this, rather > than a policy. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Assigned: (DS-640) Interal System Error when browsing with wrong argument
[ https://jira.duraspace.org/browse/DS-640?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kim Shepherd reassigned DS-640: --- Assignee: Kim Shepherd (was: Stuart Lewis) > Interal System Error when browsing with wrong argument > -- > > Key: DS-640 > URL: https://jira.duraspace.org/browse/DS-640 > Project: DSpace > Issue Type: Bug > Components: JSPUI, XMLUI >Affects Versions: 1.5.2, 1.6.0, 1.6.1, 1.6.2 >Reporter: Hardik Mishra >Assignee: Kim Shepherd >Priority: Major > Attachments: browse.patch > > > On Browsing Items: > If someone tries to use browse type for which browse index does not exist, > like browse=publisher > e.g. http://dspace.webinito.com/browse?type > OR > e.g. http://dspace.webinito.com/browse?type=xyz > You will get Internal System Error -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
[Dspace-devel] [DuraSpace JIRA] Commented: (DS-640) Interal System Error when browsing with wrong argument
[ https://jira.duraspace.org/browse/DS-640?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=18100#action_18100 ] Kim Shepherd commented on DS-640: - Hi Pere, thanks for the patch -- it's looking pretty good, but unfortunately isn't quite complete -- you'll need to run "svn add" on the NotFoundException and BadRequestException classes you've created/added for the XMLUI part of the patch, or 'svn diff' won't pick them up when you create a patch. Could you add these files to versioning, recreate your patch, and re-attach to this JIRA issue? I'll test and commit ASAP. > Interal System Error when browsing with wrong argument > -- > > Key: DS-640 > URL: https://jira.duraspace.org/browse/DS-640 > Project: DSpace > Issue Type: Bug > Components: JSPUI, XMLUI >Affects Versions: 1.5.2, 1.6.0, 1.6.1, 1.6.2 >Reporter: Hardik Mishra >Assignee: Kim Shepherd >Priority: Major > Attachments: browse.patch > > > On Browsing Items: > If someone tries to use browse type for which browse index does not exist, > like browse=publisher > e.g. http://dspace.webinito.com/browse?type > OR > e.g. http://dspace.webinito.com/browse?type=xyz > You will get Internal System Error -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: https://jira.duraspace.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira -- Centralized Desktop Delivery: Dell and VMware Reference Architecture Simplifying enterprise desktop deployment and management using Dell EqualLogic storage and VMware View: A highly scalable, end-to-end client virtualization framework. Read more! http://p.sf.net/sfu/dell-eql-dev2dev ___ Dspace-devel mailing list Dspace-devel@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-devel
