AR
Aron Roberts
Wed, Jun 29, 2011 10:01 PM
Hi Rhiannon,
The quickest way to get this environment variable in place is to
type or paste in this line, at a prompt in your Terminal application:
export JBOSS_HOME=/Users/Rbettivia/Downloads/jboss/jboss-4.2.3.GA
At the next prompt in that same terminal window, you can then type:
echo $JBOSS_HOME
to verify that this has worked.
This won't make that change permanent; you'll need to type this each
time you open a new window or tab in your Terminal application, which
can be inconvenient. But at least this is a fast way to see this work
right away. It will also help verify that your 'shell', as it's
called - the program that lets you run commands from the Terminal
application - is the so-called 'bash' shell. (If the above doesn't
work, then we can figure out something else together.)
As noted in the v1.5 installation guide
(http://wiki.collectionspace.org/display/CSPACE15/Installing+1.5+on+Generic+Unix-like+or+Windows+Systems),
you'll need to set at least five environment variables:
export JBOSS_HOME=/Users/Rbettivia/Downloads/jboss/jboss-4.2.3.GA
export DB_USER=myusername
export DB_PASSWORD=mypassword
export ANT_OPTS="-XX:MaxPermSize=512m -Xmx512m"
export MAVEN_OPTS="-XX:MaxPermSize=512m -Xmx512m"
Rather than typing each one of these, every time you open a new
Terminal window or tab, you can store these so they'll always be
loaded into your environment. You can use your text editor (e.g.
TextWrangler, TextMate, BBEdit, etc.) to open this file:
/Users/Rbettivia/.bashrc
(yes, there's a "." before "bashrc" in the above). Then paste in the
five lines above at the end of that file, if it already exists (or
anywhere in the file if it's brand new). In that file, you can then
change 'myusername' and 'mypassword', above, to the username and
password, respectively, of your MySQL user that has administrative
privileges, and save your changes to this file. Finally, you can
close your current window or tab in Terminal, and open a new window or
tab. You should then be able to type, for instance:
echo $JBOSS_HOME
or
echo $DB_USER
and see the value of each environment variable printed on the screen.
Aron Roberts
P.S. One technique you mentioned you were using, to edit the launchd
config file, is a Mac-specific mechanism that is another way of
setting environment variables, and one that is reported to work widely
across Mac OS X "shells" and GUI applications. However, it's one that
we're (or at least I'm) not very familiar with, and at least one user
has reported problems when doing so:
http://stackoverflow.com/questions/5826565/setting-global-environment-variables-via-etc-launchd-conf-on-mac-os-x-10-6-does
The technique suggested above, editing your ".bashrc" file, is similar
to the way you'd do this under many of the Linux environments on which
CollectionSpace is frequently run, and one with which we'll likely be
able to more effectively help you on the Mac, as well.
On Wed, Jun 29, 2011 at 2:28 PM, Rhiannon Bettivia
rhiannonbettivia@gmail.com wrote:
Hello Aron,
Thank you for your speedy reply. When I echo JBOSS_HOME, I get a blank
line. I did set JBOSS_HOME by exporting the environment variable according
to both the installation wiki and an additional and helpful email sent by
Glen Jackson. Also, I added JBOSS_HOME to my global environment variables
by using this command:
setenv JBOSS_HOME /Users/Rbettivia/Downloads/jboss/jboss-4.2.3.GA
in a text editor to edit the launchd config file. Yet when I echo, I get a
blank line. What might I do to address this? Additionally, we definitely
did add the driver to the JBoss lib file.
Thanks! Looking forward to getting this working!
-Rhiannon Bettivia
On Wed, Jun 29, 2011 at 4:12 PM, Aron Roberts aron@socrates.berkeley.edu
wrote:
Hi Rhiannon,
Thanks for writing again to the Talk list! Let's see if we can get
you up and running this time.
When trying to do the ant build, the program is unable to find the jdbc
driver when it hits somewhere around line 217 in the build.xml file.
Some steps to help remotely diagnose what may be at issue:
If you type this command at a prompt in your Terminal application:
echo $JBOSS_HOME
Does this output the path to a directory, or a blank line?
If that outputs the path to a directory, if you type this command:
cd $JBOSS_HOME
Do you successfully change into that directory, or do you see an error
message?
If that succeeds, if you type this command:
cd $JBOSS_HOME/server/cspace/lib
Do you successfully change into that directory, as well, or do you see
an error message?
If you can successfully change to that directory, when you type this
command, are any files listed? Specifically, do you see a file named
'mysql-connector-java-5.1.7-bin.jar'?
ls mysql*
If that succeeds, can you copy and paste the output from typing these
three (separate) commands into a follow-up message?
echo $JBOSS_HOME
pwd
ls -l
Thanks!
Aron Roberts
(for the CollectionSpace project team)
P.S. Something else for you or your software developer to try might
be to insert an 'echo' statement in the build.xml file, just before
the line where the failure occurs; something like this:
<classpath>
<!-- Add the following line here: -->
<echo message="path to database driver
file=${db.driver.jar}" />
<pathelement path="${db.driver.jar}"/>
</classpath>
When you run 'ant create_db', what does this print out?
Some background:
According to the build.properties file, located in the same directory
as the build.xml file, the value of the ${db.driver.jar} variable
should be set to this path:
db.driver.jar=${jboss.lib.cspace}/mysql-connector-java-5.1.7-bin.jar
Effectively, that means this file should be present on your system:
$JBOSS_HOME/server/cspace/lib/mysql-connector-java-5.1.7-bin.jar
where $JBOSS_HOME, in turn, is an environment variable that should
contain the full path to your JBoss folder.
On Tue, Jun 28, 2011 at 5:32 PM, Rhiannon Bettivia
rhiannonbettivia@gmail.com wrote:
Hello Everyone,
I emailed a couple of months ago that I was trying to install and run
Collection Space on Mac OS X.6, but consistently received a jdbc driver
error when it came to the Apache-Ant database build. I very much
appreciate the suggestions I received for correcting the error, and
followed
them all most carefully. I was not ever able to actually get around
this
difficulty, and chalked it up to my own inadequate skills with Java and
JBoss. I recently made contact at my new institution with a software
developer who agreed to help me with the installation, and he is quite
familiar with the components involved in Collection Space. After
starting
with a clean computer with no previous installations of any of the
component
softwares, we came up against the same jdbc driver error
(/Users/RBettivia/Downloads/jboss/v1.5/build.xml:217: Class Not Found:
JDBC
driver com.mysql.jdbc.Driver could not be loaded).
When trying to do the ant build, the program is unable to find the jdbc
driver when it hits somewhere around line 217 in the build.xml file. We
tried setting global environment variables, paths and classpaths, and
downloading and saving the driver in a number of places, to no avail.
At this point, I am wondering if anyone else has successfully installed
the
program on a Mac, and if so how this was done. If not, can someone
suggest
how the build file might be modified or another step we might take in
order
to get past this step in the installation process?
Many thanks,
Rhiannon Bettivia
Graduate School of Library and Information Science
University of Illinois, Urbana-Champaign
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Hi Rhiannon,
The quickest way to get this environment variable in place is to
type or paste in this line, at a prompt in your Terminal application:
export JBOSS_HOME=/Users/Rbettivia/Downloads/jboss/jboss-4.2.3.GA
At the next prompt in that same terminal window, you can then type:
echo $JBOSS_HOME
to verify that this has worked.
This won't make that change permanent; you'll need to type this each
time you open a new window or tab in your Terminal application, which
can be inconvenient. But at least this is a fast way to see this work
right away. It will also help verify that your 'shell', as it's
called - the program that lets you run commands from the Terminal
application - is the so-called 'bash' shell. (If the above doesn't
work, then we can figure out something else together.)
As noted in the v1.5 installation guide
(http://wiki.collectionspace.org/display/CSPACE15/Installing+1.5+on+Generic+Unix-like+or+Windows+Systems),
you'll need to set at least five environment variables:
export JBOSS_HOME=/Users/Rbettivia/Downloads/jboss/jboss-4.2.3.GA
export DB_USER=myusername
export DB_PASSWORD=mypassword
export ANT_OPTS="-XX:MaxPermSize=512m -Xmx512m"
export MAVEN_OPTS="-XX:MaxPermSize=512m -Xmx512m"
Rather than typing each one of these, every time you open a new
Terminal window or tab, you can store these so they'll always be
loaded into your environment. You can use your text editor (e.g.
TextWrangler, TextMate, BBEdit, etc.) to open this file:
/Users/Rbettivia/.bashrc
(yes, there's a "." before "bashrc" in the above). Then paste in the
five lines above at the end of that file, if it already exists (or
anywhere in the file if it's brand new). In that file, you can then
change 'myusername' and 'mypassword', above, to the username and
password, respectively, of your MySQL user that has administrative
privileges, and save your changes to this file. Finally, you can
close your current window or tab in Terminal, and open a new window or
tab. You should then be able to type, for instance:
echo $JBOSS_HOME
or
echo $DB_USER
and see the value of each environment variable printed on the screen.
Aron Roberts
P.S. One technique you mentioned you were using, to edit the launchd
config file, is a Mac-specific mechanism that is another way of
setting environment variables, and one that is reported to work widely
across Mac OS X "shells" and GUI applications. However, it's one that
we're (or at least I'm) not very familiar with, and at least one user
has reported problems when doing so:
http://stackoverflow.com/questions/5826565/setting-global-environment-variables-via-etc-launchd-conf-on-mac-os-x-10-6-does
The technique suggested above, editing your ".bashrc" file, is similar
to the way you'd do this under many of the Linux environments on which
CollectionSpace is frequently run, and one with which we'll likely be
able to more effectively help you on the Mac, as well.
On Wed, Jun 29, 2011 at 2:28 PM, Rhiannon Bettivia
<rhiannonbettivia@gmail.com> wrote:
> Hello Aron,
> Thank you for your speedy reply. When I echo JBOSS_HOME, I get a blank
> line. I did set JBOSS_HOME by exporting the environment variable according
> to both the installation wiki and an additional and helpful email sent by
> Glen Jackson. Also, I added JBOSS_HOME to my global environment variables
> by using this command:
> setenv JBOSS_HOME /Users/Rbettivia/Downloads/jboss/jboss-4.2.3.GA
> in a text editor to edit the launchd config file. Yet when I echo, I get a
> blank line. What might I do to address this? Additionally, we definitely
> did add the driver to the JBoss lib file.
> Thanks! Looking forward to getting this working!
> -Rhiannon Bettivia
>
> On Wed, Jun 29, 2011 at 4:12 PM, Aron Roberts <aron@socrates.berkeley.edu>
> wrote:
>>
>> Hi Rhiannon,
>>
>> Thanks for writing again to the Talk list! Let's see if we can get
>> you up and running this time.
>>
>> > When trying to do the ant build, the program is unable to find the jdbc
>> > driver when it hits somewhere around line 217 in the build.xml file.
>>
>> Some steps to help remotely diagnose what may be at issue:
>>
>> If you type this command at a prompt in your Terminal application:
>>
>> echo $JBOSS_HOME
>>
>> Does this output the path to a directory, or a blank line?
>>
>> If that outputs the path to a directory, if you type this command:
>>
>> cd $JBOSS_HOME
>>
>> Do you successfully change into that directory, or do you see an error
>> message?
>>
>> If that succeeds, if you type this command:
>>
>> cd $JBOSS_HOME/server/cspace/lib
>>
>> Do you successfully change into that directory, as well, or do you see
>> an error message?
>>
>> If you can successfully change to that directory, when you type this
>> command, are any files listed? Specifically, do you see a file named
>> 'mysql-connector-java-5.1.7-bin.jar'?
>>
>> ls mysql*
>>
>> If that succeeds, can you copy and paste the output from typing these
>> three (separate) commands into a follow-up message?
>>
>> echo $JBOSS_HOME
>>
>> pwd
>>
>> ls -l
>>
>> Thanks!
>> Aron Roberts
>> (for the CollectionSpace project team)
>>
>> P.S. Something else for you or your software developer to try might
>> be to insert an 'echo' statement in the build.xml file, just before
>> the line where the failure occurs; something like this:
>>
>> <classpath>
>> <!-- Add the following line here: -->
>> <echo message="path to database driver
>> file=${db.driver.jar}" />
>> <pathelement path="${db.driver.jar}"/>
>> </classpath>
>>
>> When you run 'ant create_db', what does this print out?
>>
>> Some background:
>>
>> According to the build.properties file, located in the same directory
>> as the build.xml file, the value of the ${db.driver.jar} variable
>> should be set to this path:
>>
>> db.driver.jar=${jboss.lib.cspace}/mysql-connector-java-5.1.7-bin.jar
>>
>> Effectively, that means this file should be present on your system:
>>
>> $JBOSS_HOME/server/cspace/lib/mysql-connector-java-5.1.7-bin.jar
>>
>> where $JBOSS_HOME, in turn, is an environment variable that should
>> contain the full path to your JBoss folder.
>>
>> On Tue, Jun 28, 2011 at 5:32 PM, Rhiannon Bettivia
>> <rhiannonbettivia@gmail.com> wrote:
>> > Hello Everyone,
>> > I emailed a couple of months ago that I was trying to install and run
>> > Collection Space on Mac OS X.6, but consistently received a jdbc driver
>> > error when it came to the Apache-Ant database build. I very much
>> > appreciate the suggestions I received for correcting the error, and
>> > followed
>> > them all most carefully. I was not ever able to actually get around
>> > this
>> > difficulty, and chalked it up to my own inadequate skills with Java and
>> > JBoss. I recently made contact at my new institution with a software
>> > developer who agreed to help me with the installation, and he is quite
>> > familiar with the components involved in Collection Space. After
>> > starting
>> > with a clean computer with no previous installations of any of the
>> > component
>> > softwares, we came up against the same jdbc driver error
>> > (/Users/RBettivia/Downloads/jboss/v1.5/build.xml:217: Class Not Found:
>> > JDBC
>> > driver com.mysql.jdbc.Driver could not be loaded).
>> > When trying to do the ant build, the program is unable to find the jdbc
>> > driver when it hits somewhere around line 217 in the build.xml file. We
>> > tried setting global environment variables, paths and classpaths, and
>> > downloading and saving the driver in a number of places, to no avail.
>> > At this point, I am wondering if anyone else has successfully installed
>> > the
>> > program on a Mac, and if so how this was done. If not, can someone
>> > suggest
>> > how the build file might be modified or another step we might take in
>> > order
>> > to get past this step in the installation process?
>> > Many thanks,
>> > Rhiannon Bettivia
>> > Graduate School of Library and Information Science
>> > University of Illinois, Urbana-Champaign
>> > _______________________________________________
>> > Talk mailing list
>> > Talk@lists.collectionspace.org
>> >
>> > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>> >
>> >
>
>
B
bahlin@tmora.org
Tue, Jul 5, 2011 3:40 PM
Hello all: We are currently evaluating different collections management
systems for implementation at our museum. Our organization runs Mac OS X
exclusively and I have been trying off and on for a few weeks now to install
a test copy of CollectionSpace for us to evaluate with no success. I am
encountering the exact same problem as Rhiannon Bettivia. All of the first
stages of the installation seem to go just fine, but when I get to the ant
create_db import step I receive the same JDBC driver error. Please keep me
updated about any possible solutions to this problem that arise. Is there
anyone out there who has experience successfully installing CollectionSpace
on OS X? We are running OS X Snow Leopard 10.6.8. I have tried both version
1.5 and version 1.7 of CollectionSpace to no avail. Best regards, Brinton
Ahlin The Museum of Russian Art Minneapolis, MN
Hello all: We are currently evaluating different collections management
systems for implementation at our museum. Our organization runs Mac OS X
exclusively and I have been trying off and on for a few weeks now to install
a test copy of CollectionSpace for us to evaluate with no success. I am
encountering the exact same problem as Rhiannon Bettivia. All of the first
stages of the installation seem to go just fine, but when I get to the ant
create_db import step I receive the same JDBC driver error. Please keep me
updated about any possible solutions to this problem that arise. Is there
anyone out there who has experience successfully installing CollectionSpace
on OS X? We are running OS X Snow Leopard 10.6.8. I have tried both version
1.5 and version 1.7 of CollectionSpace to no avail. Best regards, Brinton
Ahlin The Museum of Russian Art Minneapolis, MN
AR
Aron Roberts
Tue, Jul 5, 2011 3:56 PM
Hi Brinton,
We're delighted that you're considering CollectionSpace as a
collections management system for your museum! (As you may be aware,
another Minneapolis institution - the Walker Art Center - is one of
the early implementation partners in CollectionSpace.)
Over the last six month, we've had at least two developers on the
project team successfully running CollectionSpace under Mac OS X, with
CollectionSpace releases dating back at least to 1.7, possibly
earlier. One of those developers is still actively using it
day-to-day.
The troubleshooting steps suggested for Rhiannon, which you may have
seen in the message threads on this Talk list, are appropriate to
setting up CollectionSpace for your evaluation, as well. The first
step, as described in the most recent two messages in that thread, is
to ensure that your JBOSS_HOME environment variable is pointing to the
directory for your JBoss folder, and that there is a server/cspace/lib
directory within that folder, containing a .jar file for the MySQL
JDBC driver.
If you need further help with this, or run into any other issues,
please feel free to follow up here on this list.
Best wishes - and keep us posted!
Aron Roberts
On Tue, Jul 5, 2011 at 8:40 AM, bahlin@tmora.org wrote:
Hello all: We are currently evaluating different collections management
systems for implementation at our museum. Our organization runs Mac OS X
exclusively and I have been trying off and on for a few weeks now to install
a test copy of CollectionSpace for us to evaluate with no success. I am
encountering the exact same problem as Rhiannon Bettivia. All of the first
stages of the installation seem to go just fine, but when I get to the ant
create_db import step I receive the same JDBC driver error. Please keep me
updated about any possible solutions to this problem that arise. Is there
anyone out there who has experience successfully installing CollectionSpace
on OS X? We are running OS X Snow Leopard 10.6.8. I have tried both version
1.5 and version 1.7 of CollectionSpace to no avail. Best regards, Brinton
Ahlin The Museum of Russian Art Minneapolis, MN
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Hi Brinton,
We're delighted that you're considering CollectionSpace as a
collections management system for your museum! (As you may be aware,
another Minneapolis institution - the Walker Art Center - is one of
the early implementation partners in CollectionSpace.)
Over the last six month, we've had at least two developers on the
project team successfully running CollectionSpace under Mac OS X, with
CollectionSpace releases dating back at least to 1.7, possibly
earlier. One of those developers is still actively using it
day-to-day.
The troubleshooting steps suggested for Rhiannon, which you may have
seen in the message threads on this Talk list, are appropriate to
setting up CollectionSpace for your evaluation, as well. The first
step, as described in the most recent two messages in that thread, is
to ensure that your JBOSS_HOME environment variable is pointing to the
directory for your JBoss folder, and that there is a server/cspace/lib
directory within that folder, containing a .jar file for the MySQL
JDBC driver.
If you need further help with this, or run into any other issues,
please feel free to follow up here on this list.
Best wishes - and keep us posted!
Aron Roberts
On Tue, Jul 5, 2011 at 8:40 AM, <bahlin@tmora.org> wrote:
> Hello all: We are currently evaluating different collections management
> systems for implementation at our museum. Our organization runs Mac OS X
> exclusively and I have been trying off and on for a few weeks now to install
> a test copy of CollectionSpace for us to evaluate with no success. I am
> encountering the exact same problem as Rhiannon Bettivia. All of the first
> stages of the installation seem to go just fine, but when I get to the ant
> create_db import step I receive the same JDBC driver error. Please keep me
> updated about any possible solutions to this problem that arise. Is there
> anyone out there who has experience successfully installing CollectionSpace
> on OS X? We are running OS X Snow Leopard 10.6.8. I have tried both version
> 1.5 and version 1.7 of CollectionSpace to no avail. Best regards, Brinton
> Ahlin The Museum of Russian Art Minneapolis, MN
>
>
> _______________________________________________
> Talk mailing list
> Talk@lists.collectionspace.org
> http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>
AR
Aron Roberts
Wed, Jul 6, 2011 4:08 AM
Hi Rhiannon,
Tonight, we began a new install of CollectionSpace on an OS X 10.6.x
(Snow Leopard) system here, in part to help document the installaiton
process, and to assist you, Brinton, and others wishing to evaluate
CollectionSpace on the Mac.
One salient fact we learned that the environment variables - the set
of values you 'stash' away in the shell environment, that are needed
to configure and run CollectionSpace - have to be set in your
$HOME/.bash_profile file, rather than in your $HOME/.bashrc file, to
become active when you open a new Mac OS Terminal.app window. So you
can substitute /Users/Rbettivia/.bash_profile for
/Users/Rbettivia/.bashrc in the instructions below.
Aron
P.S. This also may well apply to Brinton's query/problem report earlier today.
On Wed, Jun 29, 2011 at 3:01 PM, Aron Roberts
aron@socrates.berkeley.edu wrote:
Hi Rhiannon,
The quickest way to get this environment variable in place is to
type or paste in this line, at a prompt in your Terminal application:
export JBOSS_HOME=/Users/Rbettivia/Downloads/jboss/jboss-4.2.3.GA
At the next prompt in that same terminal window, you can then type:
echo $JBOSS_HOME
to verify that this has worked.
This won't make that change permanent; you'll need to type this each
time you open a new window or tab in your Terminal application, which
can be inconvenient. But at least this is a fast way to see this work
right away. It will also help verify that your 'shell', as it's
called - the program that lets you run commands from the Terminal
application - is the so-called 'bash' shell. (If the above doesn't
work, then we can figure out something else together.)
As noted in the v1.5 installation guide
(http://wiki.collectionspace.org/display/CSPACE15/Installing+1.5+on+Generic+Unix-like+or+Windows+Systems),
you'll need to set at least five environment variables:
export JBOSS_HOME=/Users/Rbettivia/Downloads/jboss/jboss-4.2.3.GA
export DB_USER=myusername
export DB_PASSWORD=mypassword
export ANT_OPTS="-XX:MaxPermSize=512m -Xmx512m"
export MAVEN_OPTS="-XX:MaxPermSize=512m -Xmx512m"
Rather than typing each one of these, every time you open a new
Terminal window or tab, you can store these so they'll always be
loaded into your environment. You can use your text editor (e.g.
TextWrangler, TextMate, BBEdit, etc.) to open this file:
/Users/Rbettivia/.bashrc
(yes, there's a "." before "bashrc" in the above). Then paste in the
five lines above at the end of that file, if it already exists (or
anywhere in the file if it's brand new). In that file, you can then
change 'myusername' and 'mypassword', above, to the username and
password, respectively, of your MySQL user that has administrative
privileges, and save your changes to this file. Finally, you can
close your current window or tab in Terminal, and open a new window or
tab. You should then be able to type, for instance:
echo $JBOSS_HOME
or
echo $DB_USER
and see the value of each environment variable printed on the screen.
Aron Roberts
P.S. One technique you mentioned you were using, to edit the launchd
config file, is a Mac-specific mechanism that is another way of
setting environment variables, and one that is reported to work widely
across Mac OS X "shells" and GUI applications. However, it's one that
we're (or at least I'm) not very familiar with, and at least one user
has reported problems when doing so:
http://stackoverflow.com/questions/5826565/setting-global-environment-variables-via-etc-launchd-conf-on-mac-os-x-10-6-does
The technique suggested above, editing your ".bashrc" file, is similar
to the way you'd do this under many of the Linux environments on which
CollectionSpace is frequently run, and one with which we'll likely be
able to more effectively help you on the Mac, as well.
On Wed, Jun 29, 2011 at 2:28 PM, Rhiannon Bettivia
rhiannonbettivia@gmail.com wrote:
Hello Aron,
Thank you for your speedy reply. When I echo JBOSS_HOME, I get a blank
line. I did set JBOSS_HOME by exporting the environment variable according
to both the installation wiki and an additional and helpful email sent by
Glen Jackson. Also, I added JBOSS_HOME to my global environment variables
by using this command:
setenv JBOSS_HOME /Users/Rbettivia/Downloads/jboss/jboss-4.2.3.GA
in a text editor to edit the launchd config file. Yet when I echo, I get a
blank line. What might I do to address this? Additionally, we definitely
did add the driver to the JBoss lib file.
Thanks! Looking forward to getting this working!
-Rhiannon Bettivia
On Wed, Jun 29, 2011 at 4:12 PM, Aron Roberts aron@socrates.berkeley.edu
wrote:
Hi Rhiannon,
Thanks for writing again to the Talk list! Let's see if we can get
you up and running this time.
When trying to do the ant build, the program is unable to find the jdbc
driver when it hits somewhere around line 217 in the build.xml file.
Some steps to help remotely diagnose what may be at issue:
If you type this command at a prompt in your Terminal application:
echo $JBOSS_HOME
Does this output the path to a directory, or a blank line?
If that outputs the path to a directory, if you type this command:
cd $JBOSS_HOME
Do you successfully change into that directory, or do you see an error
message?
If that succeeds, if you type this command:
cd $JBOSS_HOME/server/cspace/lib
Do you successfully change into that directory, as well, or do you see
an error message?
If you can successfully change to that directory, when you type this
command, are any files listed? Specifically, do you see a file named
'mysql-connector-java-5.1.7-bin.jar'?
ls mysql*
If that succeeds, can you copy and paste the output from typing these
three (separate) commands into a follow-up message?
echo $JBOSS_HOME
pwd
ls -l
Thanks!
Aron Roberts
(for the CollectionSpace project team)
P.S. Something else for you or your software developer to try might
be to insert an 'echo' statement in the build.xml file, just before
the line where the failure occurs; something like this:
<classpath>
<!-- Add the following line here: -->
<echo message="path to database driver
file=${db.driver.jar}" />
<pathelement path="${db.driver.jar}"/>
</classpath>
When you run 'ant create_db', what does this print out?
Some background:
According to the build.properties file, located in the same directory
as the build.xml file, the value of the ${db.driver.jar} variable
should be set to this path:
db.driver.jar=${jboss.lib.cspace}/mysql-connector-java-5.1.7-bin.jar
Effectively, that means this file should be present on your system:
$JBOSS_HOME/server/cspace/lib/mysql-connector-java-5.1.7-bin.jar
where $JBOSS_HOME, in turn, is an environment variable that should
contain the full path to your JBoss folder.
On Tue, Jun 28, 2011 at 5:32 PM, Rhiannon Bettivia
rhiannonbettivia@gmail.com wrote:
Hello Everyone,
I emailed a couple of months ago that I was trying to install and run
Collection Space on Mac OS X.6, but consistently received a jdbc driver
error when it came to the Apache-Ant database build. I very much
appreciate the suggestions I received for correcting the error, and
followed
them all most carefully. I was not ever able to actually get around
this
difficulty, and chalked it up to my own inadequate skills with Java and
JBoss. I recently made contact at my new institution with a software
developer who agreed to help me with the installation, and he is quite
familiar with the components involved in Collection Space. After
starting
with a clean computer with no previous installations of any of the
component
softwares, we came up against the same jdbc driver error
(/Users/RBettivia/Downloads/jboss/v1.5/build.xml:217: Class Not Found:
JDBC
driver com.mysql.jdbc.Driver could not be loaded).
When trying to do the ant build, the program is unable to find the jdbc
driver when it hits somewhere around line 217 in the build.xml file. We
tried setting global environment variables, paths and classpaths, and
downloading and saving the driver in a number of places, to no avail.
At this point, I am wondering if anyone else has successfully installed
the
program on a Mac, and if so how this was done. If not, can someone
suggest
how the build file might be modified or another step we might take in
order
to get past this step in the installation process?
Many thanks,
Rhiannon Bettivia
Graduate School of Library and Information Science
University of Illinois, Urbana-Champaign
Talk mailing list
Talk@lists.collectionspace.org
http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
Hi Rhiannon,
Tonight, we began a new install of CollectionSpace on an OS X 10.6.x
(Snow Leopard) system here, in part to help document the installaiton
process, and to assist you, Brinton, and others wishing to evaluate
CollectionSpace on the Mac.
One salient fact we learned that the environment variables - the set
of values you 'stash' away in the shell environment, that are needed
to configure and run CollectionSpace - have to be set in your
$HOME/.bash_profile file, rather than in your $HOME/.bashrc file, to
become active when you open a new Mac OS Terminal.app window. So you
can substitute /Users/Rbettivia/.bash_profile for
/Users/Rbettivia/.bashrc in the instructions below.
Aron
P.S. This also may well apply to Brinton's query/problem report earlier today.
On Wed, Jun 29, 2011 at 3:01 PM, Aron Roberts
<aron@socrates.berkeley.edu> wrote:
> Hi Rhiannon,
>
> The quickest way to get this environment variable in place is to
> type or paste in this line, at a prompt in your Terminal application:
>
> export JBOSS_HOME=/Users/Rbettivia/Downloads/jboss/jboss-4.2.3.GA
>
> At the next prompt in that same terminal window, you can then type:
>
> echo $JBOSS_HOME
>
> to verify that this has worked.
>
> This won't make that change permanent; you'll need to type this each
> time you open a new window or tab in your Terminal application, which
> can be inconvenient. But at least this is a fast way to see this work
> right away. It will also help verify that your 'shell', as it's
> called - the program that lets you run commands from the Terminal
> application - is the so-called 'bash' shell. (If the above doesn't
> work, then we can figure out something else together.)
>
> As noted in the v1.5 installation guide
> (http://wiki.collectionspace.org/display/CSPACE15/Installing+1.5+on+Generic+Unix-like+or+Windows+Systems),
> you'll need to set at least five environment variables:
>
> export JBOSS_HOME=/Users/Rbettivia/Downloads/jboss/jboss-4.2.3.GA
> export DB_USER=myusername
> export DB_PASSWORD=mypassword
> export ANT_OPTS="-XX:MaxPermSize=512m -Xmx512m"
> export MAVEN_OPTS="-XX:MaxPermSize=512m -Xmx512m"
>
> Rather than typing each one of these, every time you open a new
> Terminal window or tab, you can store these so they'll always be
> loaded into your environment. You can use your text editor (e.g.
> TextWrangler, TextMate, BBEdit, etc.) to open this file:
>
> /Users/Rbettivia/.bashrc
>
> (yes, there's a "." before "bashrc" in the above). Then paste in the
> five lines above at the end of that file, if it already exists (or
> anywhere in the file if it's brand new). In that file, you can then
> change 'myusername' and 'mypassword', above, to the username and
> password, respectively, of your MySQL user that has administrative
> privileges, and save your changes to this file. Finally, you can
> close your current window or tab in Terminal, and open a new window or
> tab. You should then be able to type, for instance:
>
> echo $JBOSS_HOME
>
> or
>
> echo $DB_USER
>
> and see the value of each environment variable printed on the screen.
>
> Aron Roberts
>
> P.S. One technique you mentioned you were using, to edit the launchd
> config file, is a Mac-specific mechanism that is another way of
> setting environment variables, and one that is reported to work widely
> across Mac OS X "shells" and GUI applications. However, it's one that
> we're (or at least I'm) not very familiar with, and at least one user
> has reported problems when doing so:
>
> http://stackoverflow.com/questions/5826565/setting-global-environment-variables-via-etc-launchd-conf-on-mac-os-x-10-6-does
>
> The technique suggested above, editing your ".bashrc" file, is similar
> to the way you'd do this under many of the Linux environments on which
> CollectionSpace is frequently run, and one with which we'll likely be
> able to more effectively help you on the Mac, as well.
>
> On Wed, Jun 29, 2011 at 2:28 PM, Rhiannon Bettivia
> <rhiannonbettivia@gmail.com> wrote:
>> Hello Aron,
>> Thank you for your speedy reply. When I echo JBOSS_HOME, I get a blank
>> line. I did set JBOSS_HOME by exporting the environment variable according
>> to both the installation wiki and an additional and helpful email sent by
>> Glen Jackson. Also, I added JBOSS_HOME to my global environment variables
>> by using this command:
>> setenv JBOSS_HOME /Users/Rbettivia/Downloads/jboss/jboss-4.2.3.GA
>> in a text editor to edit the launchd config file. Yet when I echo, I get a
>> blank line. What might I do to address this? Additionally, we definitely
>> did add the driver to the JBoss lib file.
>> Thanks! Looking forward to getting this working!
>> -Rhiannon Bettivia
>>
>> On Wed, Jun 29, 2011 at 4:12 PM, Aron Roberts <aron@socrates.berkeley.edu>
>> wrote:
>>>
>>> Hi Rhiannon,
>>>
>>> Thanks for writing again to the Talk list! Let's see if we can get
>>> you up and running this time.
>>>
>>> > When trying to do the ant build, the program is unable to find the jdbc
>>> > driver when it hits somewhere around line 217 in the build.xml file.
>>>
>>> Some steps to help remotely diagnose what may be at issue:
>>>
>>> If you type this command at a prompt in your Terminal application:
>>>
>>> echo $JBOSS_HOME
>>>
>>> Does this output the path to a directory, or a blank line?
>>>
>>> If that outputs the path to a directory, if you type this command:
>>>
>>> cd $JBOSS_HOME
>>>
>>> Do you successfully change into that directory, or do you see an error
>>> message?
>>>
>>> If that succeeds, if you type this command:
>>>
>>> cd $JBOSS_HOME/server/cspace/lib
>>>
>>> Do you successfully change into that directory, as well, or do you see
>>> an error message?
>>>
>>> If you can successfully change to that directory, when you type this
>>> command, are any files listed? Specifically, do you see a file named
>>> 'mysql-connector-java-5.1.7-bin.jar'?
>>>
>>> ls mysql*
>>>
>>> If that succeeds, can you copy and paste the output from typing these
>>> three (separate) commands into a follow-up message?
>>>
>>> echo $JBOSS_HOME
>>>
>>> pwd
>>>
>>> ls -l
>>>
>>> Thanks!
>>> Aron Roberts
>>> (for the CollectionSpace project team)
>>>
>>> P.S. Something else for you or your software developer to try might
>>> be to insert an 'echo' statement in the build.xml file, just before
>>> the line where the failure occurs; something like this:
>>>
>>> <classpath>
>>> <!-- Add the following line here: -->
>>> <echo message="path to database driver
>>> file=${db.driver.jar}" />
>>> <pathelement path="${db.driver.jar}"/>
>>> </classpath>
>>>
>>> When you run 'ant create_db', what does this print out?
>>>
>>> Some background:
>>>
>>> According to the build.properties file, located in the same directory
>>> as the build.xml file, the value of the ${db.driver.jar} variable
>>> should be set to this path:
>>>
>>> db.driver.jar=${jboss.lib.cspace}/mysql-connector-java-5.1.7-bin.jar
>>>
>>> Effectively, that means this file should be present on your system:
>>>
>>> $JBOSS_HOME/server/cspace/lib/mysql-connector-java-5.1.7-bin.jar
>>>
>>> where $JBOSS_HOME, in turn, is an environment variable that should
>>> contain the full path to your JBoss folder.
>>>
>>> On Tue, Jun 28, 2011 at 5:32 PM, Rhiannon Bettivia
>>> <rhiannonbettivia@gmail.com> wrote:
>>> > Hello Everyone,
>>> > I emailed a couple of months ago that I was trying to install and run
>>> > Collection Space on Mac OS X.6, but consistently received a jdbc driver
>>> > error when it came to the Apache-Ant database build. I very much
>>> > appreciate the suggestions I received for correcting the error, and
>>> > followed
>>> > them all most carefully. I was not ever able to actually get around
>>> > this
>>> > difficulty, and chalked it up to my own inadequate skills with Java and
>>> > JBoss. I recently made contact at my new institution with a software
>>> > developer who agreed to help me with the installation, and he is quite
>>> > familiar with the components involved in Collection Space. After
>>> > starting
>>> > with a clean computer with no previous installations of any of the
>>> > component
>>> > softwares, we came up against the same jdbc driver error
>>> > (/Users/RBettivia/Downloads/jboss/v1.5/build.xml:217: Class Not Found:
>>> > JDBC
>>> > driver com.mysql.jdbc.Driver could not be loaded).
>>> > When trying to do the ant build, the program is unable to find the jdbc
>>> > driver when it hits somewhere around line 217 in the build.xml file. We
>>> > tried setting global environment variables, paths and classpaths, and
>>> > downloading and saving the driver in a number of places, to no avail.
>>> > At this point, I am wondering if anyone else has successfully installed
>>> > the
>>> > program on a Mac, and if so how this was done. If not, can someone
>>> > suggest
>>> > how the build file might be modified or another step we might take in
>>> > order
>>> > to get past this step in the installation process?
>>> > Many thanks,
>>> > Rhiannon Bettivia
>>> > Graduate School of Library and Information Science
>>> > University of Illinois, Urbana-Champaign
>>> > _______________________________________________
>>> > Talk mailing list
>>> > Talk@lists.collectionspace.org
>>> >
>>> > http://lists.collectionspace.org/mailman/listinfo/talk_lists.collectionspace.org
>>> >
>>> >
>>
>>
>