Re: [Dspace-tech] Changes to Messages.properties not being recognized

2009-12-10 Thread Christian Voelker

Am 10.12.2009 um 20:41 schrieb liss RR:

> I have the same problem that Eric (Changes to Messages.properties not being 
> recognized)
> I've read the solutions that you sugest him, I've made it all could you 
> please help me?
> I'm working the 1.5.1 version of dspace on windows server

Hello,

why don't you use the latest stable DSpace 1.5.2?
Can you be a bit more verbose about what you did exactly already to solve your 
problem?
E.g. what does your source and installed path look like?
Did you make your changes in the source/.../resources or in the target 
directory?
Did you run mvn package and ant update afterwards?
Were your changes copied over to the next directory as expected?
Did you windiff the unpacked version in the webapps with your source?
Did you restart your service?
Did you clear your browser cache?
Did your clear the tomcat work directory?
Did I forget a thing?

Bye, Christian


--
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech


Re: [Dspace-tech] Changes to Messages.properties not being recognized

2009-12-10 Thread liss RR

 Hi Gary:

 

I'm member of the dspace list...

I have the same problem that Eric (Changes to Messages.properties not being 
recognized)

I've read the solutions that you sugest him, I've made it all could you please 
help me?

I'm working the 1.5.1 version of dspace on windows server

 

thanks...
  
_
Nuevo Windows 7
http://www.windows.com.mx--
Return on Information:
Google Enterprise Search pays you back
Get the facts.
http://p.sf.net/sfu/google-dev2dev
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech


Re: [Dspace-tech] Changes to Messages.properties not being recognized

2009-03-27 Thread Kurzenberger, Eric
The issue with the server.xml file looks like it was just me putting the 
context path in the wrong place.  But I think I'm going to throw in the towel 
for now; faced with having an odd button or redoing my entire DSpace install, 
I'll live with the odd button.  This is just a test install for a future setup 
anyway, so I'll make sure to install the source release if we go forward with 
DSpace and hopefully avoid the issue.

Thanks for all the help, Gary.

Cheers,

Eric

-Original Message-
From: Gary Browne [mailto:g.bro...@library.usyd.edu.au]
Sent: Friday, March 27, 2009 1:24 AM
To: DSpace-tech@lists.sourceforge.net
Subject: Re: [Dspace-tech] Changes to Messages.properties not being recognized

Hi Eric,

Just starting to think about the weekend here...so maybe not in the
right brainspace to answer this well.

It might be helpful if you posted the relevant parts of your tomcat
server.xml file (ie: your Host element and the contained Context element
- are there only one of each, or do you have multiple hosts in tomcat?).

To try out the source release, firstly backup your database and
assetstore (if possible). It might be worth replicating the db and using
this replicated db to try out the source release. Just set the relevant
(replicated) db parameters, and (different from existing) dspace.dir and
assetstore.dir in [dspace-source]/dspace/config/dspace.cfg, then follow
the previous steps that I've outlined. Alternatively, you could just try
a fresh_install with different db parameters, since it's not really
changes in the db that you're interested in testing.

Can anyone think of anything else that needs to be done to avoid
overwriting the existing setup? If possible try the whole setup on a
different machine so you're guaranteed of no cross-contamination. If the
fresh_install works, you can then copy your existing db and assetstore
to the new setup (along with any code changes you've made, if any),
rebuild and deploy (mvn package, ant update, ant init_configs). You also
might want to keep your old logs if you have people viewing the stats
regularly.

I'd be interested to see if this works, 'cause I'm stumped as to why
it's not with your current setup.

I'll think about it over the weekend... ;)

Cheers
Gary


Gary Browne
Development Programmer
Library IT Services
University of Sydney
ph: 9351-5946


> -Original Message-
> From: Kurzenberger, Eric [mailto:eric.kurzenber...@yale.edu]
> Sent: Friday, 27 March 2009 3:09 AM
> To: Gary Browne; DSpace-tech@lists.sourceforge.net
> Subject: Re: [Dspace-tech] Changes to Messages.properties not
> being recognized
>
> Hi Gary,
>
> I am indeed using 1.5.1.  Sorry about the confusion, but I
> confirmed that Messages.properties is indeed in
>
> /[my dspace-source]/dspace/modules/jspui/src/main/resources
>
> I made sure the dspace user was the owner of both the dspace
> source and tomcat directories, then followed the four steps
> you outlined successfully.  But when I attempted to define a
> context path in Tomcat for JSPUI and restarted Tomcat, I got
> a 404 error when loading the dspace webpage with the message
> "The requested resource () is not available."  Undoing the
> change I made to the tomcat server.xml file and copying the
> JSPUI webapp to Tomcat's webapps directory worked, but my
> changes to Messages.properties still aren't reflected.
>
> When changing the tomcat server.xml file, I also made sure to
> specify my dspace install directory and that the changes were
> made within the host element.
>
> FYI, changing the owner to the dspace user did indeed take
> care of those "failure to delete" build errors I was getting.
>
> You also mentioned trying the source release rather than the
> default release.  Would I be able to change my install to the
> source release without overwriting my current configuration and data?
>
> I appreciate all the help.
>
> Cheers,
>
> Eric
>
>
> On 3/25/09 6:23 PM, "Gary Browne"
>  wrote:
>
> Hello again Eric,
>
> This is a little puzzling, but I know I've been more than
> puzzled by Messages.properties in the past. I don't like to
> be defeated by one little flat file, so I'm going to ask a
> few more questions...
>
> Firstly, it looks like and I'm assuming you are on 1.5.1. Correct?
>
> The reason I asked if you had your Messages.properties in the
> [dspace-source]/dspace/modules/jspui/src/main/resources/
> directory was that in your original email it was listed as
> [Dspace-source]/modules/jspui/main/resources. So I'll just
> get you to double check that directory for me.
>
> Also, I haven't tried the default release but I couldn't find
> any mention of .war files in the install instru

Re: [Dspace-tech] Changes to Messages.properties not being recognized

2009-03-26 Thread Gary Browne
Hi Eric,

Just starting to think about the weekend here...so maybe not in the
right brainspace to answer this well.

It might be helpful if you posted the relevant parts of your tomcat
server.xml file (ie: your Host element and the contained Context element
- are there only one of each, or do you have multiple hosts in tomcat?).

To try out the source release, firstly backup your database and
assetstore (if possible). It might be worth replicating the db and using
this replicated db to try out the source release. Just set the relevant
(replicated) db parameters, and (different from existing) dspace.dir and
assetstore.dir in [dspace-source]/dspace/config/dspace.cfg, then follow
the previous steps that I've outlined. Alternatively, you could just try
a fresh_install with different db parameters, since it's not really
changes in the db that you're interested in testing.

Can anyone think of anything else that needs to be done to avoid
overwriting the existing setup? If possible try the whole setup on a
different machine so you're guaranteed of no cross-contamination. If the
fresh_install works, you can then copy your existing db and assetstore
to the new setup (along with any code changes you've made, if any),
rebuild and deploy (mvn package, ant update, ant init_configs). You also
might want to keep your old logs if you have people viewing the stats
regularly.

I'd be interested to see if this works, 'cause I'm stumped as to why
it's not with your current setup.

I'll think about it over the weekend... ;)

Cheers
Gary


Gary Browne
Development Programmer
Library IT Services
University of Sydney
ph: 9351-5946
 

> -Original Message-
> From: Kurzenberger, Eric [mailto:eric.kurzenber...@yale.edu] 
> Sent: Friday, 27 March 2009 3:09 AM
> To: Gary Browne; DSpace-tech@lists.sourceforge.net
> Subject: Re: [Dspace-tech] Changes to Messages.properties not 
> being recognized
> 
> Hi Gary,
> 
> I am indeed using 1.5.1.  Sorry about the confusion, but I 
> confirmed that Messages.properties is indeed in
> 
> /[my dspace-source]/dspace/modules/jspui/src/main/resources
> 
> I made sure the dspace user was the owner of both the dspace 
> source and tomcat directories, then followed the four steps 
> you outlined successfully.  But when I attempted to define a 
> context path in Tomcat for JSPUI and restarted Tomcat, I got 
> a 404 error when loading the dspace webpage with the message 
> "The requested resource () is not available."  Undoing the 
> change I made to the tomcat server.xml file and copying the 
> JSPUI webapp to Tomcat's webapps directory worked, but my 
> changes to Messages.properties still aren't reflected.
> 
> When changing the tomcat server.xml file, I also made sure to 
> specify my dspace install directory and that the changes were 
> made within the host element.
> 
> FYI, changing the owner to the dspace user did indeed take 
> care of those "failure to delete" build errors I was getting.
> 
> You also mentioned trying the source release rather than the 
> default release.  Would I be able to change my install to the 
> source release without overwriting my current configuration and data?
> 
> I appreciate all the help.
> 
> Cheers,
> 
> Eric
> 
> 
> On 3/25/09 6:23 PM, "Gary Browne" 
>  wrote:
> 
> Hello again Eric,
> 
> This is a little puzzling, but I know I've been more than 
> puzzled by Messages.properties in the past. I don't like to 
> be defeated by one little flat file, so I'm going to ask a 
> few more questions...
> 
> Firstly, it looks like and I'm assuming you are on 1.5.1. Correct?
> 
> The reason I asked if you had your Messages.properties in the 
> [dspace-source]/dspace/modules/jspui/src/main/resources/ 
> directory was that in your original email it was listed as 
> [Dspace-source]/modules/jspui/main/resources. So I'll just 
> get you to double check that directory for me.
> 
> Also, I haven't tried the default release but I couldn't find 
> any mention of .war files in the install instructions. Maybe 
> you could try one of the alternative deployment methods (see 
> below). But first, can I get you to confirm that you have 
> followed each of these steps:
> 
> i) cd [dspace-source]/dspace
> ii) mvn package
> iii) cd target/dspace-[version].dir
> iv) ant init_configs
> 
> Having followed these procedures, can you then either:
> 
> A) DEFINE A CONTEXT PATH IN TOMCAT FOR THE JSPUI
> 
> Add the following to your [tomcat-home]/conf/server.xml, 
> within the  element:
> 
> 
>  
>  docBase="[dspace-install-directory]\webapps\jspui" debug="0"
> reloadable="true" cachingA

Re: [Dspace-tech] Changes to Messages.properties not being recognized

2009-03-26 Thread Kurzenberger, Eric
Hi Gary,

I am indeed using 1.5.1.  Sorry about the confusion, but I confirmed that 
Messages.properties is indeed in

/[my dspace-source]/dspace/modules/jspui/src/main/resources

I made sure the dspace user was the owner of both the dspace source and tomcat 
directories, then followed the four steps you outlined successfully.  But when 
I attempted to define a context path in Tomcat for JSPUI and restarted Tomcat, 
I got a 404 error when loading the dspace webpage with the message "The 
requested resource () is not available."  Undoing the change I made to the 
tomcat server.xml file and copying the JSPUI webapp to Tomcat's webapps 
directory worked, but my changes to Messages.properties still aren't reflected.

When changing the tomcat server.xml file, I also made sure to specify my dspace 
install directory and that the changes were made within the host element.

FYI, changing the owner to the dspace user did indeed take care of those 
"failure to delete" build errors I was getting.

You also mentioned trying the source release rather than the default release.  
Would I be able to change my install to the source release without overwriting 
my current configuration and data?

I appreciate all the help.

Cheers,

Eric


On 3/25/09 6:23 PM, "Gary Browne"  wrote:

Hello again Eric,

This is a little puzzling, but I know I've been more than puzzled by
Messages.properties in the past. I don't like to be defeated by one
little flat file, so I'm going to ask a few more questions...

Firstly, it looks like and I'm assuming you are on 1.5.1. Correct?

The reason I asked if you had your Messages.properties in the
[dspace-source]/dspace/modules/jspui/src/main/resources/ directory was
that in your original email it was listed as
[Dspace-source]/modules/jspui/main/resources. So I'll just get you to
double check that directory for me.

Also, I haven't tried the default release but I couldn't find any
mention of .war files in the install instructions. Maybe you could try
one of the alternative deployment methods (see below). But first, can I
get you to confirm that you have followed each of these steps:

i) cd [dspace-source]/dspace
ii) mvn package
iii) cd target/dspace-[version].dir
iv) ant init_configs

Having followed these procedures, can you then either:

A) DEFINE A CONTEXT PATH IN TOMCAT FOR THE JSPUI

Add the following to your [tomcat-home]/conf/server.xml, within the
 element:





OR:

B) COPY YOUR JSPUI WEBAPP TO TOMCAT'S WEBAPPS DIRECTORY

cp -r  [dspace-install-directory]/webapps/jspui [tomcat-home]/webapps/


AFAIK the default and source releases should behave the same in terms of
building and deployment, but someone else could confirm or deny this?

I look forward to your reply (or indeed anyone else's thoughts on this
issue).

Gary

P.S. Has the "failure to delete" error been resolved as a result of
permissions changes?


Gary Browne
Development Programmer
Library IT Services
University of Sydney
ph: 9351-5946


> -Original Message-
> From: Kurzenberger, Eric [mailto:eric.kurzenber...@yale.edu]
> Sent: Thursday, 26 March 2009 6:53 AM
> To: Gary Browne; DSpace-tech@lists.sourceforge.net
> Subject: Re: [Dspace-tech] Changes to Messages.properties not
> being recognized
>
> Hi Gary,
>
> I already had the Messages.properties file in
> [dspace-source]/dspace/modules/jspui/src/main/resources/
> prior to building and deploying, following the instructions
> in the Dspace wiki (which Van Ly also sent in response to
> this thread).  No luck.  Could this be because I'm using the
> default release and not the source release?  I can't for the
> life of me figure out why the dspace install would be
> ignoring the Messages.properties file.
>
> Cheers,
>
> Eric
>
> On 3/24/09 11:08 PM, "Gary Browne"
>  wrote:
>
> Hi Eric,
>
> Upon further investigation, the path to your source
> Messages.properties appears to be incorrect. I have:
>
> [dspace-source]/dspace/modules/jspui/src/main/resources/Messag
> es.propert
> ies
>
> Try sticking your Messages.properties file in that location
> and going through the build and deploy steps again.
>
> The 'failure to delete' error looks like a permissions
> problem. Make sure all your source files are owned by the
> 'dspace' user (or whatever you choose to call the user which
> runs tomcat).
>
> Good luck.
> Cheers
> Gary
>
>
> Gary Browne
> Development Programmer
> Library IT Services
> University of Sydney
> ph: 9351-5946
>
>
> > -Original Message-
> > From: Kurzenberger, Eric [mailto:eric.kurzenber...@yale.edu]
> > Sent: Wednesday, 25 March 2009 2:00 PM
> > To: Gary Browne; DSpace-tech@lists.sourceforge.net
> > Subject: Re: [Dspace-tech] Chan

Re: [Dspace-tech] Changes to Messages.properties not being recognized

2009-03-25 Thread Gary Browne
Hi Eric,

One more thought which I forgot to mention in my last reply was maybe
you could try with the source release? Is this a new installation or an
existing populated repository?

Cheers
Gary


Gary Browne
Development Programmer
Library IT Services
University of Sydney
ph: 9351-5946
 

> -Original Message-
> From: Kurzenberger, Eric [mailto:eric.kurzenber...@yale.edu] 
> Sent: Thursday, 26 March 2009 6:53 AM
> To: Gary Browne; DSpace-tech@lists.sourceforge.net
> Subject: Re: [Dspace-tech] Changes to Messages.properties not 
> being recognized
> 
> Hi Gary,
> 
> I already had the Messages.properties file in 
> [dspace-source]/dspace/modules/jspui/src/main/resources/ 
> prior to building and deploying, following the instructions 
> in the Dspace wiki (which Van Ly also sent in response to 
> this thread).  No luck.  Could this be because I'm using the 
> default release and not the source release?  I can't for the 
> life of me figure out why the dspace install would be 
> ignoring the Messages.properties file.
> 
> Cheers,
> 
> Eric
> 
> On 3/24/09 11:08 PM, "Gary Browne" 
>  wrote:
> 
> Hi Eric,
> 
> Upon further investigation, the path to your source 
> Messages.properties appears to be incorrect. I have:
> 
> [dspace-source]/dspace/modules/jspui/src/main/resources/Messag
> es.propert
> ies
> 
> Try sticking your Messages.properties file in that location 
> and going through the build and deploy steps again.
> 
> The 'failure to delete' error looks like a permissions 
> problem. Make sure all your source files are owned by the 
> 'dspace' user (or whatever you choose to call the user which 
> runs tomcat).
> 
> Good luck.
> Cheers
> Gary
> 
> 
> Gary Browne
> Development Programmer
> Library IT Services
> University of Sydney
> ph: 9351-5946
> 
> 
> > -Original Message-----
> > From: Kurzenberger, Eric [mailto:eric.kurzenber...@yale.edu]
> > Sent: Wednesday, 25 March 2009 2:00 PM
> > To: Gary Browne; DSpace-tech@lists.sourceforge.net
> > Subject: Re: [Dspace-tech] Changes to Messages.properties not being 
> > recognized
> >
> > Thanks for the response, Gary.  I followed the steps you 
> outlined, but 
> > still am not seeing my changes reflected.
> > Messages.properties did not get copied to the 
> > [dspace-install-directory]/webapps/jspui/WEB-INF/classes/
> > directory (which is empty) after running both "ant 
> init_configs" and 
> > "ant update."  I copied it manually and restarted tomcat, but still 
> > didn't see my changes reflected.
> > I also tried copying Messages.properties to 
> > [dspace-install-directory]/config, but that didn't work either.
> >
> > I did get the following build error when running "mvn clean 
> package:"
> >
> > Failed to delete directory:
> > /usr/local/dspace-1.5.1-release/dspace/modules/xmlui/target.
> > Reason: Unable to delete file
> > /usr/local/dspace-1.5.1-release/dspace/modules/xmlui/target/xm
> > lui-1.5.1/WEB-INF/lib/activation-1.1.jar
> >
> > But the build was successful, and since I'm using jspui, 
> not xmlui, I 
> > don't see why this would be an issue.
> >
> > Do you have any other suggestions?
> >
> > Cheers,
> >
> > Eric
> >
> >
> > On 3/23/09 6:38 PM, "Gary Browne"
> >  wrote:
> >
> > Hi Eric,
> >
> > Looks like noone has replied to you AFAICS. Let's see how we go...
> >
> > I don't copy the war files, just point tomcat to the 
> > [dspace-install-directory]/webapps/jspui directory (in 
> server.xml), so 
> > not sure if this will work with your setup.
> >
> > So it looks like you have the Messages.properties file in the right 
> > location (I think, from memory) in the source directory. 
> Then you need 
> > to run from the [dspace-source]/dspace directory:
> >
> > mvn clean package
> >
> > Then change to your dspace-1.5.1-build.dir directory (cd
> > target/dspace-1.5.1-build.dir) and run:
> >
> > ant init_configs (or maybe 'ant update', if that doesn't work
> > - sorry, just back from 3 months off and a bit rusty).
> >
> > How can you check if it has worked? Check the 
> > [dspace-install-directory]/webapps/jspui/WEB-INF/classes/
> > directory for your (updated) Messages.properties file. It should be 
> > copied here. Then of course, check your button.
> >
> > Hope this is of help in some small way.
> >
> > Kind regards
> > Gary
> &g

Re: [Dspace-tech] Changes to Messages.properties not being recognized

2009-03-25 Thread Gary Browne
Hello again Eric,

This is a little puzzling, but I know I've been more than puzzled by
Messages.properties in the past. I don't like to be defeated by one
little flat file, so I'm going to ask a few more questions...

Firstly, it looks like and I'm assuming you are on 1.5.1. Correct?

The reason I asked if you had your Messages.properties in the
[dspace-source]/dspace/modules/jspui/src/main/resources/ directory was
that in your original email it was listed as
[Dspace-source]/modules/jspui/main/resources. So I'll just get you to
double check that directory for me.

Also, I haven't tried the default release but I couldn't find any
mention of .war files in the install instructions. Maybe you could try
one of the alternative deployment methods (see below). But first, can I
get you to confirm that you have followed each of these steps:

i) cd [dspace-source]/dspace
ii) mvn package
iii) cd target/dspace-[version].dir
iv) ant init_configs

Having followed these procedures, can you then either:

A) DEFINE A CONTEXT PATH IN TOMCAT FOR THE JSPUI

Add the following to your [tomcat-home]/conf/server.xml, within the
 element:





OR:

B) COPY YOUR JSPUI WEBAPP TO TOMCAT'S WEBAPPS DIRECTORY

cp -r  [dspace-install-directory]/webapps/jspui [tomcat-home]/webapps/


AFAIK the default and source releases should behave the same in terms of
building and deployment, but someone else could confirm or deny this?

I look forward to your reply (or indeed anyone else's thoughts on this
issue).

Gary

P.S. Has the "failure to delete" error been resolved as a result of
permissions changes?


Gary Browne
Development Programmer
Library IT Services
University of Sydney
ph: 9351-5946
 

> -Original Message-
> From: Kurzenberger, Eric [mailto:eric.kurzenber...@yale.edu] 
> Sent: Thursday, 26 March 2009 6:53 AM
> To: Gary Browne; DSpace-tech@lists.sourceforge.net
> Subject: Re: [Dspace-tech] Changes to Messages.properties not 
> being recognized
> 
> Hi Gary,
> 
> I already had the Messages.properties file in 
> [dspace-source]/dspace/modules/jspui/src/main/resources/ 
> prior to building and deploying, following the instructions 
> in the Dspace wiki (which Van Ly also sent in response to 
> this thread).  No luck.  Could this be because I'm using the 
> default release and not the source release?  I can't for the 
> life of me figure out why the dspace install would be 
> ignoring the Messages.properties file.
> 
> Cheers,
> 
> Eric
> 
> On 3/24/09 11:08 PM, "Gary Browne" 
>  wrote:
> 
> Hi Eric,
> 
> Upon further investigation, the path to your source 
> Messages.properties appears to be incorrect. I have:
> 
> [dspace-source]/dspace/modules/jspui/src/main/resources/Messag
> es.propert
> ies
> 
> Try sticking your Messages.properties file in that location 
> and going through the build and deploy steps again.
> 
> The 'failure to delete' error looks like a permissions 
> problem. Make sure all your source files are owned by the 
> 'dspace' user (or whatever you choose to call the user which 
> runs tomcat).
> 
> Good luck.
> Cheers
> Gary
> 
> 
> Gary Browne
> Development Programmer
> Library IT Services
> University of Sydney
> ph: 9351-5946
> 
> 
> > -Original Message-
> > From: Kurzenberger, Eric [mailto:eric.kurzenber...@yale.edu]
> > Sent: Wednesday, 25 March 2009 2:00 PM
> > To: Gary Browne; DSpace-tech@lists.sourceforge.net
> > Subject: Re: [Dspace-tech] Changes to Messages.properties not being 
> > recognized
> >
> > Thanks for the response, Gary.  I followed the steps you 
> outlined, but 
> > still am not seeing my changes reflected.
> > Messages.properties did not get copied to the 
> > [dspace-install-directory]/webapps/jspui/WEB-INF/classes/
> > directory (which is empty) after running both "ant 
> init_configs" and 
> > "ant update."  I copied it manually and restarted tomcat, but still 
> > didn't see my changes reflected.
> > I also tried copying Messages.properties to 
> > [dspace-install-directory]/config, but that didn't work either.
> >
> > I did get the following build error when running "mvn clean 
> package:"
> >
> > Failed to delete directory:
> > /usr/local/dspace-1.5.1-release/dspace/modules/xmlui/target.
> > Reason: Unable to delete file
> > /usr/local/dspace-1.5.1-release/dspace/modules/xmlui/target/xm
> > lui-1.5.1/WEB-INF/lib/activation-1.1.jar
> >
> > But the build was successful, and since I'm using jspui, 
> not xmlui, I 
> > don't see why this would be an issue.
> >
> > Do you have any other suggest

Re: [Dspace-tech] Changes to Messages.properties not being recognized

2009-03-25 Thread Kurzenberger, Eric
Hi Gary,

I already had the Messages.properties file in 
[dspace-source]/dspace/modules/jspui/src/main/resources/ prior to building and 
deploying, following the instructions in the Dspace wiki (which Van Ly also 
sent in response to this thread).  No luck.  Could this be because I'm using 
the default release and not the source release?  I can't for the life of me 
figure out why the dspace install would be ignoring the Messages.properties 
file.

Cheers,

Eric

On 3/24/09 11:08 PM, "Gary Browne"  wrote:

Hi Eric,

Upon further investigation, the path to your source Messages.properties
appears to be incorrect. I have:

[dspace-source]/dspace/modules/jspui/src/main/resources/Messages.propert
ies

Try sticking your Messages.properties file in that location and going
through the build and deploy steps again.

The 'failure to delete' error looks like a permissions problem. Make
sure all your source files are owned by the 'dspace' user (or whatever
you choose to call the user which runs tomcat).

Good luck.
Cheers
Gary


Gary Browne
Development Programmer
Library IT Services
University of Sydney
ph: 9351-5946


> -Original Message-
> From: Kurzenberger, Eric [mailto:eric.kurzenber...@yale.edu]
> Sent: Wednesday, 25 March 2009 2:00 PM
> To: Gary Browne; DSpace-tech@lists.sourceforge.net
> Subject: Re: [Dspace-tech] Changes to Messages.properties not
> being recognized
>
> Thanks for the response, Gary.  I followed the steps you
> outlined, but still am not seeing my changes reflected.
> Messages.properties did not get copied to the
> [dspace-install-directory]/webapps/jspui/WEB-INF/classes/
> directory (which is empty) after running both "ant
> init_configs" and "ant update."  I copied it manually and
> restarted tomcat, but still didn't see my changes reflected.
> I also tried copying Messages.properties to
> [dspace-install-directory]/config, but that didn't work either.
>
> I did get the following build error when running "mvn clean package:"
>
> Failed to delete directory:
> /usr/local/dspace-1.5.1-release/dspace/modules/xmlui/target.
> Reason: Unable to delete file
> /usr/local/dspace-1.5.1-release/dspace/modules/xmlui/target/xm
> lui-1.5.1/WEB-INF/lib/activation-1.1.jar
>
> But the build was successful, and since I'm using jspui, not
> xmlui, I don't see why this would be an issue.
>
> Do you have any other suggestions?
>
> Cheers,
>
> Eric
>
>
> On 3/23/09 6:38 PM, "Gary Browne"
>  wrote:
>
> Hi Eric,
>
> Looks like noone has replied to you AFAICS. Let's see how we go...
>
> I don't copy the war files, just point tomcat to the
> [dspace-install-directory]/webapps/jspui directory (in
> server.xml), so not sure if this will work with your setup.
>
> So it looks like you have the Messages.properties file in the
> right location (I think, from memory) in the source
> directory. Then you need to run from the
> [dspace-source]/dspace directory:
>
> mvn clean package
>
> Then change to your dspace-1.5.1-build.dir directory (cd
> target/dspace-1.5.1-build.dir) and run:
>
> ant init_configs (or maybe 'ant update', if that doesn't work
> - sorry, just back from 3 months off and a bit rusty).
>
> How can you check if it has worked? Check the
> [dspace-install-directory]/webapps/jspui/WEB-INF/classes/
> directory for your (updated) Messages.properties file. It
> should be copied here. Then of course, check your button.
>
> Hope this is of help in some small way.
>
> Kind regards
> Gary
>
>
> Gary Browne
> Development Programmer
> Library IT Services
> University of Sydney
> ph: 9351-5946
>
>
> > -Original Message-
> > From: Kurzenberger, Eric [mailto:eric.kurzenber...@yale.edu]
> > Sent: Saturday, 21 March 2009 2:36 AM
> > To: DSpace-tech@lists.sourceforge.net
> > Subject: [Dspace-tech] Changes to Messages.properties not being
> > recognized
> >
> > Hi all,
> >
> > I made a couple changes to my Messages.properties file (to
> take care
> > of the ???jsp.mydspace.request.export.community.???
> > button issue, amongst other things) and did a rebuild of
> DSpace, but
> > my changes aren't being recognized.  Since I'm using the default
> > release of 1.5.1 and not the source release, I had to get the
> > Messages.properties file from the DSpace SourceForge repository and
> > copy it to [Dspace-source]/modules/jspui/main/resources, which I've
> > read worked for other users, then did a rebuild of DSpace and
> > restarted Tomcat.  But the cha

Re: [Dspace-tech] Changes to Messages.properties not being recognized

2009-03-24 Thread Van Ly
Hi Eric,

Have a look at

 http://wiki.dspace.org/index.php/Fix_%3F%3F%3Fsome.key.name%3F%3F%3F_%28JSP%29

-- Van Ly 

 



From: Kurzenberger, Eric
Sent: Wed 25/03/2009 1:59 PM
To: Gary Browne; DSpace-tech@lists.sourceforge.net
Subject: Re: [Dspace-tech] Changes to Messages.properties not being recognized


Thanks for the response, Gary.  I followed the steps you outlined, but still am 
not seeing my changes reflected.  Messages.properties did not get copied to the 
[dspace-install-directory]/webapps/jspui/WEB-INF/classes/ directory (which is 
empty) after running both "ant init_configs" and "ant update."  I copied it 
manually and restarted tomcat, but still didn't see my changes reflected.  I 
also tried copying Messages.properties to [dspace-install-directory]/config, 
but that didn't work either.

I did get the following build error when running "mvn clean package:"

Failed to delete directory: 
/usr/local/dspace-1.5.1-release/dspace/modules/xmlui/target. Reason: Unable to 
delete file 
/usr/local/dspace-1.5.1-release/dspace/modules/xmlui/target/xmlui-1.5.1/WEB-INF/lib/activation-1.1.jar

But the build was successful, and since I'm using jspui, not xmlui, I don't see 
why this would be an issue.

Do you have any other suggestions?

Cheers,

Eric


On 3/23/09 6:38 PM, "Gary Browne"  wrote:

Hi Eric,

Looks like noone has replied to you AFAICS. Let's see how we go...

I don't copy the war files, just point tomcat to the
[dspace-install-directory]/webapps/jspui directory (in server.xml), so
not sure if this will work with your setup.

So it looks like you have the Messages.properties file in the right
location (I think, from memory) in the source directory. Then you need
to run from the [dspace-source]/dspace directory:

mvn clean package

Then change to your dspace-1.5.1-build.dir directory (cd
target/dspace-1.5.1-build.dir) and run:

ant init_configs (or maybe 'ant update', if that doesn't work - sorry,
just back from 3 months off and a bit rusty).

How can you check if it has worked? Check the
[dspace-install-directory]/webapps/jspui/WEB-INF/classes/ directory for
your (updated) Messages.properties file. It should be copied here. Then
of course, check your button.

Hope this is of help in some small way.

Kind regards
Gary


Gary Browne
Development Programmer
Library IT Services
University of Sydney
ph: 9351-5946


> -Original Message-
> From: Kurzenberger, Eric [mailto:eric.kurzenber...@yale.edu]
> Sent: Saturday, 21 March 2009 2:36 AM
> To: DSpace-tech@lists.sourceforge.net
> Subject: [Dspace-tech] Changes to Messages.properties not
> being recognized
>
> Hi all,
>
> I made a couple changes to my Messages.properties file (to
> take care of the ???jsp.mydspace.request.export.community.???
> button issue, amongst other things) and did a rebuild of
> DSpace, but my changes aren't being recognized.  Since I'm
> using the default release of 1.5.1 and not the source
> release, I had to get the Messages.properties file from the
> DSpace SourceForge repository and copy it to
> [Dspace-source]/modules/jspui/main/resources, which I've read
> worked for other users, then did a rebuild of DSpace and
> restarted Tomcat.  But the changes I made aren't showing up
> when I go back into DSpace.
>
> One note: the rebuild instructions on the wiki indicate to
> copy the .war files from the build directory in
> [dspace-source] to [tomcat], but I don't see a build
> directory anywhere in my [dspace-source].  I do have a
> "dspace-1.5.1-build.dir" directory, but hat doesn't contain
> any .war files.  Could this be the source of the issue?
>
> Thanks for all your help!
>
> Cheers,
>
> Eric
>
>
> --
> 
> Apps built with the Adobe(R) Flex(R) framework and Flex
> Builder(TM) are powering Web 2.0 with engaging,
> cross-platform capabilities. Quickly and easily build your
> RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial.
> http://p.sf.net/sfu/www-adobe-com
> ___
> DSpace-tech mailing list
> DSpace-tech@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>

--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com

Re: [Dspace-tech] Changes to Messages.properties not being recognized

2009-03-24 Thread Gary Browne
Hi Eric,

Upon further investigation, the path to your source Messages.properties
appears to be incorrect. I have:

[dspace-source]/dspace/modules/jspui/src/main/resources/Messages.propert
ies

Try sticking your Messages.properties file in that location and going
through the build and deploy steps again.

The 'failure to delete' error looks like a permissions problem. Make
sure all your source files are owned by the 'dspace' user (or whatever
you choose to call the user which runs tomcat).

Good luck.
Cheers
Gary


Gary Browne
Development Programmer
Library IT Services
University of Sydney
ph: 9351-5946
 

> -Original Message-
> From: Kurzenberger, Eric [mailto:eric.kurzenber...@yale.edu] 
> Sent: Wednesday, 25 March 2009 2:00 PM
> To: Gary Browne; DSpace-tech@lists.sourceforge.net
> Subject: Re: [Dspace-tech] Changes to Messages.properties not 
> being recognized
> 
> Thanks for the response, Gary.  I followed the steps you 
> outlined, but still am not seeing my changes reflected.  
> Messages.properties did not get copied to the 
> [dspace-install-directory]/webapps/jspui/WEB-INF/classes/ 
> directory (which is empty) after running both "ant 
> init_configs" and "ant update."  I copied it manually and 
> restarted tomcat, but still didn't see my changes reflected.  
> I also tried copying Messages.properties to 
> [dspace-install-directory]/config, but that didn't work either.
> 
> I did get the following build error when running "mvn clean package:"
> 
> Failed to delete directory: 
> /usr/local/dspace-1.5.1-release/dspace/modules/xmlui/target. 
> Reason: Unable to delete file 
> /usr/local/dspace-1.5.1-release/dspace/modules/xmlui/target/xm
> lui-1.5.1/WEB-INF/lib/activation-1.1.jar
> 
> But the build was successful, and since I'm using jspui, not 
> xmlui, I don't see why this would be an issue.
> 
> Do you have any other suggestions?
> 
> Cheers,
> 
> Eric
> 
> 
> On 3/23/09 6:38 PM, "Gary Browne" 
>  wrote:
> 
> Hi Eric,
> 
> Looks like noone has replied to you AFAICS. Let's see how we go...
> 
> I don't copy the war files, just point tomcat to the 
> [dspace-install-directory]/webapps/jspui directory (in 
> server.xml), so not sure if this will work with your setup.
> 
> So it looks like you have the Messages.properties file in the 
> right location (I think, from memory) in the source 
> directory. Then you need to run from the 
> [dspace-source]/dspace directory:
> 
> mvn clean package
> 
> Then change to your dspace-1.5.1-build.dir directory (cd
> target/dspace-1.5.1-build.dir) and run:
> 
> ant init_configs (or maybe 'ant update', if that doesn't work 
> - sorry, just back from 3 months off and a bit rusty).
> 
> How can you check if it has worked? Check the 
> [dspace-install-directory]/webapps/jspui/WEB-INF/classes/ 
> directory for your (updated) Messages.properties file. It 
> should be copied here. Then of course, check your button.
> 
> Hope this is of help in some small way.
> 
> Kind regards
> Gary
> 
> 
> Gary Browne
> Development Programmer
> Library IT Services
> University of Sydney
> ph: 9351-5946
> 
> 
> > -Original Message-
> > From: Kurzenberger, Eric [mailto:eric.kurzenber...@yale.edu]
> > Sent: Saturday, 21 March 2009 2:36 AM
> > To: DSpace-tech@lists.sourceforge.net
> > Subject: [Dspace-tech] Changes to Messages.properties not being 
> > recognized
> >
> > Hi all,
> >
> > I made a couple changes to my Messages.properties file (to 
> take care 
> > of the ???jsp.mydspace.request.export.community.???
> > button issue, amongst other things) and did a rebuild of 
> DSpace, but 
> > my changes aren't being recognized.  Since I'm using the default 
> > release of 1.5.1 and not the source release, I had to get the 
> > Messages.properties file from the DSpace SourceForge repository and 
> > copy it to [Dspace-source]/modules/jspui/main/resources, which I've 
> > read worked for other users, then did a rebuild of DSpace and 
> > restarted Tomcat.  But the changes I made aren't showing up 
> when I go 
> > back into DSpace.
> >
> > One note: the rebuild instructions on the wiki indicate to copy the 
> > .war files from the build directory in [dspace-source] to [tomcat], 
> > but I don't see a build directory anywhere in my 
> [dspace-source].  I 
> > do have a "dspace-1.5.1-build.dir" directory, but hat 
> doesn't contain 
> > any .war files.  Could this be the source of the issue?
>

Re: [Dspace-tech] Changes to Messages.properties not being recognized

2009-03-24 Thread Kurzenberger, Eric
Thanks for the response, Gary.  I followed the steps you outlined, but still am 
not seeing my changes reflected.  Messages.properties did not get copied to the 
[dspace-install-directory]/webapps/jspui/WEB-INF/classes/ directory (which is 
empty) after running both "ant init_configs" and "ant update."  I copied it 
manually and restarted tomcat, but still didn't see my changes reflected.  I 
also tried copying Messages.properties to [dspace-install-directory]/config, 
but that didn't work either.

I did get the following build error when running "mvn clean package:"

Failed to delete directory: 
/usr/local/dspace-1.5.1-release/dspace/modules/xmlui/target. Reason: Unable to 
delete file 
/usr/local/dspace-1.5.1-release/dspace/modules/xmlui/target/xmlui-1.5.1/WEB-INF/lib/activation-1.1.jar

But the build was successful, and since I'm using jspui, not xmlui, I don't see 
why this would be an issue.

Do you have any other suggestions?

Cheers,

Eric


On 3/23/09 6:38 PM, "Gary Browne"  wrote:

Hi Eric,

Looks like noone has replied to you AFAICS. Let's see how we go...

I don't copy the war files, just point tomcat to the
[dspace-install-directory]/webapps/jspui directory (in server.xml), so
not sure if this will work with your setup.

So it looks like you have the Messages.properties file in the right
location (I think, from memory) in the source directory. Then you need
to run from the [dspace-source]/dspace directory:

mvn clean package

Then change to your dspace-1.5.1-build.dir directory (cd
target/dspace-1.5.1-build.dir) and run:

ant init_configs (or maybe 'ant update', if that doesn't work - sorry,
just back from 3 months off and a bit rusty).

How can you check if it has worked? Check the
[dspace-install-directory]/webapps/jspui/WEB-INF/classes/ directory for
your (updated) Messages.properties file. It should be copied here. Then
of course, check your button.

Hope this is of help in some small way.

Kind regards
Gary


Gary Browne
Development Programmer
Library IT Services
University of Sydney
ph: 9351-5946


> -Original Message-
> From: Kurzenberger, Eric [mailto:eric.kurzenber...@yale.edu]
> Sent: Saturday, 21 March 2009 2:36 AM
> To: DSpace-tech@lists.sourceforge.net
> Subject: [Dspace-tech] Changes to Messages.properties not
> being recognized
>
> Hi all,
>
> I made a couple changes to my Messages.properties file (to
> take care of the ???jsp.mydspace.request.export.community.???
> button issue, amongst other things) and did a rebuild of
> DSpace, but my changes aren't being recognized.  Since I'm
> using the default release of 1.5.1 and not the source
> release, I had to get the Messages.properties file from the
> DSpace SourceForge repository and copy it to
> [Dspace-source]/modules/jspui/main/resources, which I've read
> worked for other users, then did a rebuild of DSpace and
> restarted Tomcat.  But the changes I made aren't showing up
> when I go back into DSpace.
>
> One note: the rebuild instructions on the wiki indicate to
> copy the .war files from the build directory in
> [dspace-source] to [tomcat], but I don't see a build
> directory anywhere in my [dspace-source].  I do have a
> "dspace-1.5.1-build.dir" directory, but hat doesn't contain
> any .war files.  Could this be the source of the issue?
>
> Thanks for all your help!
>
> Cheers,
>
> Eric
>
>
> --
> 
> Apps built with the Adobe(R) Flex(R) framework and Flex
> Builder(TM) are powering Web 2.0 with engaging,
> cross-platform capabilities. Quickly and easily build your
> RIAs with Flex Builder, the Eclipse(TM)based development
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial.
> http://p.sf.net/sfu/www-adobe-com
> ___
> DSpace-tech mailing list
> DSpace-tech@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
>

--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech


--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are

Re: [Dspace-tech] Changes to Messages.properties not being recognized

2009-03-23 Thread Gary Browne
Hi Eric,

Looks like noone has replied to you AFAICS. Let's see how we go...

I don't copy the war files, just point tomcat to the
[dspace-install-directory]/webapps/jspui directory (in server.xml), so
not sure if this will work with your setup.

So it looks like you have the Messages.properties file in the right
location (I think, from memory) in the source directory. Then you need
to run from the [dspace-source]/dspace directory:

mvn clean package

Then change to your dspace-1.5.1-build.dir directory (cd
target/dspace-1.5.1-build.dir) and run:

ant init_configs (or maybe 'ant update', if that doesn't work - sorry,
just back from 3 months off and a bit rusty).

How can you check if it has worked? Check the
[dspace-install-directory]/webapps/jspui/WEB-INF/classes/ directory for
your (updated) Messages.properties file. It should be copied here. Then
of course, check your button.

Hope this is of help in some small way.

Kind regards
Gary


Gary Browne
Development Programmer
Library IT Services
University of Sydney
ph: 9351-5946
 

> -Original Message-
> From: Kurzenberger, Eric [mailto:eric.kurzenber...@yale.edu] 
> Sent: Saturday, 21 March 2009 2:36 AM
> To: DSpace-tech@lists.sourceforge.net
> Subject: [Dspace-tech] Changes to Messages.properties not 
> being recognized
> 
> Hi all,
> 
> I made a couple changes to my Messages.properties file (to 
> take care of the ???jsp.mydspace.request.export.community.??? 
> button issue, amongst other things) and did a rebuild of 
> DSpace, but my changes aren't being recognized.  Since I'm 
> using the default release of 1.5.1 and not the source 
> release, I had to get the Messages.properties file from the 
> DSpace SourceForge repository and copy it to 
> [Dspace-source]/modules/jspui/main/resources, which I've read 
> worked for other users, then did a rebuild of DSpace and 
> restarted Tomcat.  But the changes I made aren't showing up 
> when I go back into DSpace.
> 
> One note: the rebuild instructions on the wiki indicate to 
> copy the .war files from the build directory in 
> [dspace-source] to [tomcat], but I don't see a build 
> directory anywhere in my [dspace-source].  I do have a 
> "dspace-1.5.1-build.dir" directory, but hat doesn't contain 
> any .war files.  Could this be the source of the issue?
> 
> Thanks for all your help!
> 
> Cheers,
> 
> Eric
> 
> 
> --
> 
> Apps built with the Adobe(R) Flex(R) framework and Flex 
> Builder(TM) are powering Web 2.0 with engaging, 
> cross-platform capabilities. Quickly and easily build your 
> RIAs with Flex Builder, the Eclipse(TM)based development 
> software that enables intelligent coding and step-through debugging.
> Download the free 60 day trial. 
> http://p.sf.net/sfu/www-adobe-com 
> ___
> DSpace-tech mailing list
> DSpace-tech@lists.sourceforge.net
> https://lists.sourceforge.net/lists/listinfo/dspace-tech
> 

--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech


[Dspace-tech] Changes to Messages.properties not being recognized

2009-03-20 Thread Kurzenberger, Eric
Hi all,

I made a couple changes to my Messages.properties file (to take care of the 
???jsp.mydspace.request.export.community.??? button issue, amongst other 
things) and did a rebuild of DSpace, but my changes aren't being recognized.  
Since I'm using the default release of 1.5.1 and not the source release, I had 
to get the Messages.properties file from the DSpace SourceForge repository and 
copy it to [Dspace-source]/modules/jspui/main/resources, which I've read worked 
for other users, then did a rebuild of DSpace and restarted Tomcat.  But the 
changes I made aren't showing up when I go back into DSpace.

One note: the rebuild instructions on the wiki indicate to copy the .war files 
from the build directory in [dspace-source] to [tomcat], but I don't see a 
build directory anywhere in my [dspace-source].  I do have a 
"dspace-1.5.1-build.dir" directory, but hat doesn't contain any .war files.  
Could this be the source of the issue?

Thanks for all your help!

Cheers,

Eric


--
Apps built with the Adobe(R) Flex(R) framework and Flex Builder(TM) are
powering Web 2.0 with engaging, cross-platform capabilities. Quickly and
easily build your RIAs with Flex Builder, the Eclipse(TM)based development
software that enables intelligent coding and step-through debugging.
Download the free 60 day trial. http://p.sf.net/sfu/www-adobe-com
___
DSpace-tech mailing list
DSpace-tech@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/dspace-tech