On Sep 26, 2008, at 10:36 AM, Blanco, Jose wrote: > Mark: > > It turns out that we always get the log4j error, even on 1.5 which > works > fine. So that is not an issue. > > I do follow the instructions you pointed out below. > > The reason I hard code the dspace.cfg file is that I have two > repositories - a prod and a dev, and whe I was working with 1.5 it was > looking at the wrong repostiory, and you told me to hard code the path > in that file.
I told you to do that? Maybe that was my evil twin... ok, I'll fes up and take ownership, yes I do that sometimes as well. Heres what we do now for prod, test, dev instances running on the same (and/or different) machines. I set this up this last summer during our last upgrade sprint as a means to preserve the deployment details of our distributions. This may help your deployments play nicer together.... 1.) Define different dspace.cfg for each instance (prod, test, dev) http://libstaff.mit.edu/svn/repos/distributions/dspace.mit.edu/trunk/dspace/config/ 2.) Write a few different scripts that will do the dirty work of deploying to each of those cases, see for instance the shell scripts located in: http://libstaff.mit.edu/svn/repos/distributions/dspace.mit.edu/trunk/dspace/ http://libstaff.mit.edu/svn/repos/distributions/dspace.mit.edu/trunk/dspace/src/main/scripts/ This will allow you to take the same source tree and deploy it to 1 or more separate locations, each configured with a different dspace.cfg, you can then rid yourself of the hardcoded web.xml and rely instead on deploying it to test location. Are you doing testing/debugging inside Eclipse or are you updating the webapp and testing from the [dspace.dir]/webapps? > > > I don't understand why after I do step 1 and 2 I don't have a WEB-INF > dir in the dev-151/dspace/modules/jspui/src/main/webapp. I have > placed > all my customized jsp changes in this directory. This is because Maven does the overlay process in the dev-151/dspace/ modules/jspui/target directory and not directly in the src directory where it would get confused with your customizations. In the past I have used Eclipse, Sysdo, WTP and Tomcat to launch test instances of the webapplication within the Eclipse IDE that I can trace and debug directly on, I did this by using the target/webapp directory as the mount point for the webapplication in eclipse. However, this still required pushing the mvn package button in that project to get it refresh. I gave up on this approach and now just deploy to the [dspace.dir]/webapps using mvn package/ant update- webapps and attach to a remote debugger in Eclipse instead, this seems a bit more stable for me to work against. > > > If you find this too confusing to deal over email, I can give you my > phone. Posting to the list is good in that it can help others out in the future. Cheers, Mark > > > Thanks! > > Jose > > -----Original Message----- > From: Diggory Mark [mailto:[EMAIL PROTECTED] > Sent: Friday, September 26, 2008 12:00 PM > To: Tech DSpace > Subject: Re: [Dspace-tech] Upgrading to 151 > > Jose, > > I'm concerned that your possibly trying to build DSpace differently > than > we outline currently in the documentation. > > 1.) go to [dspace-source]/dspace and run mvn clean package > > 2.) go to [dspace-source]/target/dspace-1.5.1-build.dir and run "ant > fresh_install" for a fresh installation or "ant update" to update > compiled code/webapps that you are deploying > > You should not need to hardcode the "dspace.dir" of dspace.cfg in the > web.xml or anywhere else other than your [dspace-source/dspace/config/ > dspace.cfg file. The Ant install process transforms this file whenever > you run ant update or ant fresh_install. > > Please give better details about the system your deploying on, which > distribution you are using (release or src-release), all the > customizations your trying to make and the steps your taking to build > DSpace. Without this level of detail we can not provide an adequate > diagnosis of why you are getting results inconsistent with the > documented build process. The two issues outline below are very > different in nature. > > Sincerely, > Mark > > > On Sep 26, 2008, at 8:06 AM, Blanco, Jose wrote: > >> I was able to >> >> /l/local/bin/mvn package >> >> to complete and then I did the update to creat the webapp. But now >> when I try to deploy it, I'm getting this error: >> >> log4j:WARN No appenders could be found for logger >> (org.apache.commons.digester.Digester.sax). >> log4j:WARN Please initialize the log4j system properly. >> No update on poolMap! >> >> >> Also, with dspace 1.5 I had hardcoded the dspace.cfg file path in the >> file: >> >> dspace/modules/jspui/src/main/webapp/WEB-INF/web.xml >> >> But I don't see this file when I build 1.5.1 >> >> -Jose >> >> -----Original Message----- >> From: Sands Fish [mailto:[EMAIL PROTECTED] >> Sent: Thursday, September 25, 2008 3:58 PM >> To: Blanco, Jose >> Cc: [email protected] >> Subject: Re: [Dspace-tech] Upgrading to 151 >> >> Jose, >> >> Also, for future trouble-shooting reference, you can use a web- >> browser to verify that the artifact Maven is complaining about is >> there, e.g... >> >> From the error, you can get the repositories it is attempting to >> download the artifact from... >> http://maven.dspace.org/snapshot >> >> and then navigate through the tree structure to make sure the JAR of >> the artifact exists. Maven deploys artifacts based on 3 criteria, >> which are mapped to the directory structure you will see in any Maven >> repository: >> >> groupId (e.g. "dspace") >> artifactId (e.g. "dspace-api-lang") >> and >> version (e.g. "1.5.0.1-SNAPSHOT" although in this case, it is >> looking for any version within the range 1.5.0.0 - 1.6.0.0 as noted >> in > >> the error below) >> >> Hence, the URL to check: >> >> http://maven.dspace.org/snapshot/org/dspace/dspace-api-lang/ >> 1.5.0.1-SNAPSHOT/ >> >> >> Much easier to just start at the top though: >> >> http://maven.dspace.org/snapshot >> >> >> -- >> sands fish >> Software Engineer >> MIT Libraries >> Technology Research & Development >> [EMAIL PROTECTED] >> E25-131 >> >> >> * Please consider the environment before printing this email >> >> >> >> >> On Sep 25, 2008, at 3:02 PM, Blanco, Jose wrote: >> >>> I'm getting the following message when I do >>> >>> /l/local/bin/mvn package >>> >>> [INFO] Building jar: >>> /l1/dspace/build/dev-151/dspace-api/target/dspace-api-1.5.1.jar >>> [INFO] >>> --------------------------------------------------------------------- >>> - >> >>> -- >>> [INFO] Building DSpace XML-UI (Manakin) :: API and Core Aspects >>> [INFO] task-segment: [package] >>> [INFO] >>> --------------------------------------------------------------------- >>> - >> >>> -- >>> [INFO] [resources:resources] >>> [INFO] Using default encoding to copy filtered resources. >>> [INFO] artifact org.dspace:dspace-api-lang: checking for updates >>> from > >>> central [WARNING] repository metadata for: 'artifact >>> org.dspace:dspace-api- lang' >>> could not be retrieved from repository: central due to an error: >>> Error >>> transferring file >>> [INFO] Repository 'central' will be blacklisted [INFO] >>> --------------------------------------------------------------------- >>> - >> >>> -- >>> [ERROR] BUILD ERROR >>> [INFO] >>> --------------------------------------------------------------------- >>> - >> >>> -- >>> [INFO] Failed to resolve artifact. >>> >>> No versions are present in the repository for the artifact with a >>> range >>> [1.5.0.0,1.6.0.0) >>> org.dspace:dspace-api-lang:jar:null >>> >>> from the specified remote repositories: >>> central (http://repo1.maven.org/maven2), maven.dspace.org/snapshot >>> (http://maven.dspace.org/snapshot) >>> >>> How should I resolve this? >>> >>> Thanks! >>> Jose >>> >>> --------------------------------------------------------------------- >>> - >> >>> --- >>> This SF.Net email is sponsored by the Moblin Your Move Developer's >>> challenge Build the coolest Linux based applications with Moblin SDK >>> & win great prizes Grand prize is a trip for two to an Open Source >>> event anywhere in the world >>> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >>> _______________________________________________ >>> DSpace-tech mailing list >>> [email protected] >>> https://lists.sourceforge.net/lists/listinfo/dspace-tech >> >> >> > ------------------------------------------------------------------------ > - >> This SF.Net email is sponsored by the Moblin Your Move Developer's >> challenge >> Build the coolest Linux based applications with Moblin SDK & win >> great prizes >> Grand prize is a trip for two to an Open Source event anywhere in >> the world >> http://moblin-contest.org/redirect.php?banner_id=100&url=/ >> _______________________________________________ >> DSpace-tech mailing list >> [email protected] >> https://lists.sourceforge.net/lists/listinfo/dspace-tech > > > ------------------------------------------------------------------------ > - > This SF.Net email is sponsored by the Moblin Your Move Developer's > challenge > Build the coolest Linux based applications with Moblin SDK & win great > prizes > Grand prize is a trip for two to an Open Source event anywhere in the > world > http://moblin-contest.org/redirect.php?banner_id=100&url=/ > _______________________________________________ > DSpace-tech mailing list > [email protected] > https://lists.sourceforge.net/lists/listinfo/dspace-tech ------------------------------------------------------------------------- This SF.Net email is sponsored by the Moblin Your Move Developer's challenge Build the coolest Linux based applications with Moblin SDK & win great prizes Grand prize is a trip for two to an Open Source event anywhere in the world http://moblin-contest.org/redirect.php?banner_id=100&url=/ _______________________________________________ DSpace-tech mailing list [email protected] https://lists.sourceforge.net/lists/listinfo/dspace-tech
