Hm, perhaps a better alternative is to build the Cocoon dist and cherry-pick 
the classes I modified out of the build and drop them in my DSpace/Vireo 
instance.  I'm really just trying to trace the pipeline execution to find out 
why i'm mysteriously getting redirected to the login page when I thought I'd 
extracted all of the authentication hooks for the student submission intf.


On Dec 8, 2011, at 3:23 PM, Scott Phillips wrote:


Unfortunately if you take the approach of building a cocoon with all the 
dependencies then you'll get a lot of version miss-matches between the 
libraries that cocoon is pulling in and the libraries that DSpace uses. 
Basically if you compile a full cocoon you will be pulling in every single line 
of java ever written (not really, but close)

Scott--

On Thu, Dec 8, 2011 at 2:19 PM, DeVries, Joe 
<[email protected]<mailto:[email protected]>> wrote:
It sounds like then the default build would only potentially have additional 
blocks specified (any that you omitted), and wouldn’t be missing any.  Then 
would it be likely that a jar built with the default blocks would work with 
DSpace 1.5.1/Vireo?

Joe

--
Joe DeVries
Sr Software Developer/Analyst
Digital Library Services, TDL
University of Texas at Austin
512-495-4639<tel:512-495-4639>
PCL 1.335 / S5477

From: Scott Phillips 
[mailto:[email protected]<mailto:[email protected]>]
Sent: Thursday, December 08, 2011 1:54 PM
To: 
[email protected]<mailto:[email protected]> 
Devel

Subject: Re: [Dspace-devel] Custom Cocoon Build - Source?



Sands,

Yeah, I built the copy of cocoon that those older builds are going against. 
That version of cocoon was before they moved to a maven build system. Their 
previous build system was this crazy custom ant-based solution that created the 
concept of 'blocks'. We use to have the source code in a repository here at A&M 
but that was long ago and we're not using that repository anymore. As Joe, 
mentioned, really the only special thing is the blocks included. I just looked 
at the list of blocks and only included what seem remotely relevant to keep the 
jar as small as possible.

Scott--
On Wed, Dec 7, 2011 at 12:12 PM, Sands Alden Fish 
<[email protected]<mailto:[email protected]>> wrote:
Thanks Joe, that's helpful.  Good to know there aren't any patches I'm missing. 
 I've got a copy of the 2.1.9 source I'm playing with now.  If you come across 
them, any other details would be great.
-Sands


On Dec 7, 2011, at 1:07 PM, DeVries, Joe wrote:


Hi Sands,
I did some checking around, and apparently the custom Cocoon jar, was built 
from unmodified 2.1.9 source with certain cocoon blocks specified to be 
included/excluded at build time.  We currently don’t know what those block are, 
but I will do a little more investigating.

Joe



--
Joe DeVries
Sr Software Developer/Analyst
Digital Library Services / Texas Digital Library
University of Texas at Austin
512-495-4639<tel:512-495-4639>
PCL 1.335 / S5477

From: Sands Alden Fish [mailto:[email protected]<mailto:[email protected]>]
Sent: Tuesday, December 06, 2011 1:48 PM
To: Tim Donohue
Cc: 
[email protected]<mailto:[email protected]> 
Devel
Subject: Re: [Dspace-devel] Custom Cocoon Build - Source?

Yup, definitely my intention to integrate it with trunk-state XMLUI if it 
translates.  (I haven't really had too much opportunity to play around in the 
3.x versions of Cocoon and I know a lot is different.  It'll save me a lot of 
pain in the future even outside of Vireo.

--
sands fish
Senior Software Engineer
MIT Libraries
Technology Research & Development
[email protected]<mailto:[email protected]>
E25-131




On Dec 6, 2011, at 2:30 PM, Tim Donohue wrote:

A big +1 to "add in some logging for actual useful sitemap/pipeline tracing". 
If you discover anything in your work, it'd make a great addition to DSpace 
itself (I think we all can get frustrated by the lack of informative info 
logged when there are sitemap issues, etc)

- Tim

On Tuesday, December 06, 2011 1:23:50 PM, Sands Alden Fish wrote:
I believe their more recent work is lining Vireo up with more recent
versions of DSpace, so I don't believe it will be an issue for long.
I'm trying to add in some logging for actual useful sitemap/pipeline
tracing, spurred by trouble debugging some behavior in the XMLUI in
Vireo, so my solution should roughly apply to most other versions of
Cocoon. If the patching turns out well, I'll share it with the list. I
know a lot of my time debugging the XMLUI is spent digging through
opaque Cocoon stack-traces.
--
Tim Donohue
Technical Lead for DSpace Project
DuraSpace.org<http://DuraSpace.org/>



------------------------------------------------------------------------------
Cloud Services Checklist: Pricing and Packaging Optimization
This white paper is intended to serve as a reference, checklist and point of
discussion for anyone considering optimizing the pricing and packaging model
of a cloud services business. Read Now!
http://www.accelacomm.com/jaw/sfnl/114/51491232/
_______________________________________________
Dspace-devel mailing list
[email protected]<mailto:[email protected]>
https://lists.sourceforge.net/lists/listinfo/dspace-devel



------------------------------------------------------------------------------
Cloud Services Checklist: Pricing and Packaging Optimization
This white paper is intended to serve as a reference, checklist and point of 
discussion for anyone considering optimizing the pricing and packaging model 
of a cloud services business. Read Now!
http://www.accelacomm.com/jaw/sfnl/114/51491232/
_______________________________________________
Dspace-devel mailing list
[email protected]
https://lists.sourceforge.net/lists/listinfo/dspace-devel

Reply via email to