Re: [Dspace-tech] web.xml file location and contents in 182
Great! Thank you! Jose -Original Message- From: Tim Donohue [mailto:tdono...@duraspace.org] Sent: Wednesday, March 14, 2012 11:38 AM To: Blanco, Jose Cc: dspace-tech@lists.sourceforge.net Subject: Re: [Dspace-tech] web.xml file location and contents in 182 Hi Jose, On 3/14/2012 9:27 AM, Blanco, Jose wrote: > I'm upgrading from 170 to 182, and I have noticed two things that have me > confused. > > 1. I have made some changes to: > > dspace-jspui/dspace-jspui-webapp/src/main/webapp/WEB-INF/web.xml > > But my changes are not showing up in the target area : > > ./dspace/modules/jspui/target/war/work/org.dspace/dspace-jspui-webapp/ > WEB-INF/web.xml > ./dspace/modules/jspui/target/jspui-1.8.2/WEB-INF/web.xml > ./dspace/target/dspace-1.8.2-build/webapps/jspui/WEB-INF/web.xml As noted in the 1.8.x Upgrade documentation (see the yellow note at the top of the page), there have been a few changes to the 'source release' structure: https://wiki.duraspace.org/display/DSDOC18/Upgrading+From+1.7.x+to+1.8.x These changes are described in more detail at (under the heading "DSpace Source Release"): https://wiki.duraspace.org/display/DSDOC18/Advanced+Customisation Specifically, the way Maven builds DSpace is now *slightly* different in 1.8.x and above: 1. Running 'mvn package' from [dspace-src]/dspace/ will *ONLY* re-apply any Maven Overlays (i.e. ONLY rebuilds code in [dspace-src]/dspace/modules/). This is a "Quick Build" option which doesn't require you to rebuild *all* of DSpace. So, if you put your web.xml changes in a file named [dspace-src]/dspace/modules/jspui/src/main/webapp/WEB-INF/web.xml then it will be "overlayed" properly in the final result. 2. Alternatively, running 'mvn package' from [dspace-src] (parent directory) will do a full rebuild of *all* DSpace code (takes a bit longer as it rebuilds all sub-directories of [dspace-src] one-by-one). So, this is what you'd want to run to rebuild the entire [dspace-src]/dspace-jspui/ directory. It should be noted that we recommend using Maven Overlays when you can (i.e. put your customizations under [dspace-src]/dspace/modules/). It helps keep your changes separate from the core DSpace code. More information at: https://wiki.duraspace.org/display/DSDOC18/Advanced+Customisation > > 2. The target area layout seems to be different from 170 to 182. Why? > In actuality, the main thing that has changed here is the DSpace version number. Look closely below and you'll see that nearly all the directories are identical except that paths containing "1.7.0" now contain "1.8.2". Also, it's worth noting that most of these various target directories can be ignored (it's just Maven doing it's own backend processing). The only target directory that really matters is: [dspace-src]/target/dspace-[version]-build/.. That directory contains the build of your DSpace (with all Maven overlays applied). All other 'target' directories are just generated by Maven while Maven is attempting to assemble DSpace into [dspace-src]/target. > In 170: > ./dspace-jspui/dspace-jspui-webapp/src/main/webapp/WEB-INF/web.xml > ./dspace-jspui/dspace-jspui-webapp/target/dspace-jspui-webapp-1.7.0/WE > B-INF/web.xml > ./dspace/modules/jspui/target/war/work/org.dspace/dspace-jspui-webapp/ > WEB-INF/web.xml > ./dspace/modules/jspui/target/jspui-1.7.0/WEB-INF/web.xml > ./dspace/target/dspace-1.7.0-build.dir/webapps/jspui/WEB-INF/web.xml > > > In 182: > ./dspace-jspui/dspace-jspui-webapp/src/main/webapp/WEB-INF/web.xml > ./dspace/modules/jspui/target/war/work/org.dspace/dspace-jspui-webapp/ > WEB-INF/web.xml > ./dspace/modules/jspui/target/jspui-1.8.2/WEB-INF/web.xml > ./dspace/target/dspace-1.8.2-build/webapps/jspui/WEB-INF/web.xml Hopefully that helps! - Tim -- Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech -- Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] web.xml file location and contents in 182
Whoops! I made a typo in my previous message. See below.. On 3/14/2012 10:38 AM, Tim Donohue wrote: >> 2. The target area layout seems to be different from 170 to 182. Why? >> > > In actuality, the main thing that has changed here is the DSpace version > number. Look closely below and you'll see that nearly all the > directories are identical except that paths containing "1.7.0" now > contain "1.8.2". > > Also, it's worth noting that most of these various target directories > can be ignored (it's just Maven doing it's own backend processing). The > only target directory that really matters is: > > [dspace-src]/target/dspace-[version]-build/.. Sorry, this directory should be (accidentally left off the "/dspace" subdirectory): [dspace-src]/dspace/target/dspace-[version]-build/.. > > That directory contains the build of your DSpace (with all Maven > overlays applied). All other 'target' directories are just generated by > Maven while Maven is attempting to assemble DSpace into > [dspace-src]/target. > >> In 170: >> ./dspace-jspui/dspace-jspui-webapp/src/main/webapp/WEB-INF/web.xml >> ./dspace-jspui/dspace-jspui-webapp/target/dspace-jspui-webapp-1.7.0/WEB-INF/web.xml >> >> ./dspace/modules/jspui/target/war/work/org.dspace/dspace-jspui-webapp/WEB-INF/web.xml >> >> ./dspace/modules/jspui/target/jspui-1.7.0/WEB-INF/web.xml >> ./dspace/target/dspace-1.7.0-build.dir/webapps/jspui/WEB-INF/web.xml >> >> >> In 182: >> ./dspace-jspui/dspace-jspui-webapp/src/main/webapp/WEB-INF/web.xml >> ./dspace/modules/jspui/target/war/work/org.dspace/dspace-jspui-webapp/WEB-INF/web.xml >> >> ./dspace/modules/jspui/target/jspui-1.8.2/WEB-INF/web.xml >> ./dspace/target/dspace-1.8.2-build/webapps/jspui/WEB-INF/web.xml > > Hopefully that helps! > > - Tim -- Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
Re: [Dspace-tech] web.xml file location and contents in 182
Hi Jose, On 3/14/2012 9:27 AM, Blanco, Jose wrote: > I'm upgrading from 170 to 182, and I have noticed two things that have me > confused. > > 1. I have made some changes to: > > dspace-jspui/dspace-jspui-webapp/src/main/webapp/WEB-INF/web.xml > > But my changes are not showing up in the target area : > > ./dspace/modules/jspui/target/war/work/org.dspace/dspace-jspui-webapp/WEB-INF/web.xml > ./dspace/modules/jspui/target/jspui-1.8.2/WEB-INF/web.xml > ./dspace/target/dspace-1.8.2-build/webapps/jspui/WEB-INF/web.xml As noted in the 1.8.x Upgrade documentation (see the yellow note at the top of the page), there have been a few changes to the 'source release' structure: https://wiki.duraspace.org/display/DSDOC18/Upgrading+From+1.7.x+to+1.8.x These changes are described in more detail at (under the heading "DSpace Source Release"): https://wiki.duraspace.org/display/DSDOC18/Advanced+Customisation Specifically, the way Maven builds DSpace is now *slightly* different in 1.8.x and above: 1. Running 'mvn package' from [dspace-src]/dspace/ will *ONLY* re-apply any Maven Overlays (i.e. ONLY rebuilds code in [dspace-src]/dspace/modules/). This is a "Quick Build" option which doesn't require you to rebuild *all* of DSpace. So, if you put your web.xml changes in a file named [dspace-src]/dspace/modules/jspui/src/main/webapp/WEB-INF/web.xml then it will be "overlayed" properly in the final result. 2. Alternatively, running 'mvn package' from [dspace-src] (parent directory) will do a full rebuild of *all* DSpace code (takes a bit longer as it rebuilds all sub-directories of [dspace-src] one-by-one). So, this is what you'd want to run to rebuild the entire [dspace-src]/dspace-jspui/ directory. It should be noted that we recommend using Maven Overlays when you can (i.e. put your customizations under [dspace-src]/dspace/modules/). It helps keep your changes separate from the core DSpace code. More information at: https://wiki.duraspace.org/display/DSDOC18/Advanced+Customisation > > 2. The target area layout seems to be different from 170 to 182. Why? > In actuality, the main thing that has changed here is the DSpace version number. Look closely below and you'll see that nearly all the directories are identical except that paths containing "1.7.0" now contain "1.8.2". Also, it's worth noting that most of these various target directories can be ignored (it's just Maven doing it's own backend processing). The only target directory that really matters is: [dspace-src]/target/dspace-[version]-build/.. That directory contains the build of your DSpace (with all Maven overlays applied). All other 'target' directories are just generated by Maven while Maven is attempting to assemble DSpace into [dspace-src]/target. > In 170: > ./dspace-jspui/dspace-jspui-webapp/src/main/webapp/WEB-INF/web.xml > ./dspace-jspui/dspace-jspui-webapp/target/dspace-jspui-webapp-1.7.0/WEB-INF/web.xml > ./dspace/modules/jspui/target/war/work/org.dspace/dspace-jspui-webapp/WEB-INF/web.xml > ./dspace/modules/jspui/target/jspui-1.7.0/WEB-INF/web.xml > ./dspace/target/dspace-1.7.0-build.dir/webapps/jspui/WEB-INF/web.xml > > > In 182: > ./dspace-jspui/dspace-jspui-webapp/src/main/webapp/WEB-INF/web.xml > ./dspace/modules/jspui/target/war/work/org.dspace/dspace-jspui-webapp/WEB-INF/web.xml > ./dspace/modules/jspui/target/jspui-1.8.2/WEB-INF/web.xml > ./dspace/target/dspace-1.8.2-build/webapps/jspui/WEB-INF/web.xml Hopefully that helps! - Tim -- Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
[Dspace-tech] web.xml file location and contents in 182
I'm upgrading from 170 to 182, and I have noticed two things that have me confused. 1. I have made some changes to: dspace-jspui/dspace-jspui-webapp/src/main/webapp/WEB-INF/web.xml But my changes are not showing up in the target area : ./dspace/modules/jspui/target/war/work/org.dspace/dspace-jspui-webapp/WEB-INF/web.xml ./dspace/modules/jspui/target/jspui-1.8.2/WEB-INF/web.xml ./dspace/target/dspace-1.8.2-build/webapps/jspui/WEB-INF/web.xml 2. The target area layout seems to be different from 170 to 182. Why? In 170: ./dspace-jspui/dspace-jspui-webapp/src/main/webapp/WEB-INF/web.xml ./dspace-jspui/dspace-jspui-webapp/target/dspace-jspui-webapp-1.7.0/WEB-INF/web.xml ./dspace/modules/jspui/target/war/work/org.dspace/dspace-jspui-webapp/WEB-INF/web.xml ./dspace/modules/jspui/target/jspui-1.7.0/WEB-INF/web.xml ./dspace/target/dspace-1.7.0-build.dir/webapps/jspui/WEB-INF/web.xml In 182: ./dspace-jspui/dspace-jspui-webapp/src/main/webapp/WEB-INF/web.xml ./dspace/modules/jspui/target/war/work/org.dspace/dspace-jspui-webapp/WEB-INF/web.xml ./dspace/modules/jspui/target/jspui-1.8.2/WEB-INF/web.xml ./dspace/target/dspace-1.8.2-build/webapps/jspui/WEB-INF/web.xml Thank you! Jose -- Virtualization & Cloud Management Using Capacity Planning Cloud computing makes use of virtualization - but cloud computing also focuses on allowing computing to be delivered as a service. http://www.accelacomm.com/jaw/sfnl/114/51521223/ ___ DSpace-tech mailing list DSpace-tech@lists.sourceforge.net https://lists.sourceforge.net/lists/listinfo/dspace-tech
