Re: can't get alpha4 to work with java 5

2005-09-30 Thread Ashley Williams

This is a fresh download of continuum.
Just copied the app to my Applications directory using drag and drop  
in Mac OS X Finder.


Still fails, this is what i did:

 cd continuum
 mv apps/continuum apps/continuumbak
 bin/macosx/run.sh start

which resulted in

Running continuum...
bin/macosx/run.sh: line 173: /Applications/continuum-latest/bin/ 
macosx/wrapper: Permission denied
bin/macosx/run.sh: line 173: exec: /Applications/continuum-latest/bin/ 
macosx/wrapper: cannot execute: Unknown error: 0


so I changed the wrapper file which had no executed permissions (not  
sure why):

chmod 755 bin/maccosx/wrapper

and ran again:
 bin/macosx/run.sh start

which resulted in

Running continuum...
wrapper  | -- Wrapper Started as Console
dyld: lazy symbol binding failed: Symbol not found: _ftime
  Referenced from: /Applications/continuum-latest/bin/macosx/wrapper
  Expected in: /usr/lib/libcrypto.0.9.7.dylib

dyld: Symbol not found: _ftime
  Referenced from: /Applications/continuum-latest/bin/macosx/wrapper
  Expected in: /usr/lib/libcrypto.0.9.7.dylib

Trace/BPT trap


which makes no sense to me.


On 30 Sep 2005, at 09:54, Emmanuel Venisse wrote:


I use java 5, and it works fine.

Remove your apps/continuum directory, and run bin/YOUR_OS/run script

Do you have modified something in continuum conf?

Emmanuel

Ashley Williams a écrit :

Don't know if alpha4 is supposed to work with java 5 but I can't  
get  it to work, I just get the stack trace below. Yet when I  
switch back  to 1.4.2 it works fine. I'm actually trying to build  
a Java 5 project  so as a workaround is it possible to have a java  
4 continuum session  launch a Java 5 build?

Thanks
AW
1[main] DEBUG org.codehaus.plexus.PlexusContainer  - Found 3   
components to load on start
9[main] INFO  org.codehaus.plexus.PlexusContainer  - Loading  
on  start [role]: [org.apache.maven.continuum.Continuum]
285  [main] INFO  org.codehaus.plexus.jdo.JdoFactory  -  
Initializing  JDO.
3144 [main] INFO  JPOX.JDO  - PersistenceManagerFactory - Vendor:   
JPOX  Version: 1.1.0-beta-4
3146 [main] INFO  JPOX.JDO  - PersistenceManagerFactory  
initialised  for datastore URL=jdbc:derby:/Applications/continuum- 
latest/apps/ continuum/database;create=true   
driver=org.apache.derby.jdbc.EmbeddedDriver userName=sa
3863 [main] INFO  org.quartz.simpl.RAMJobStore  - RAMJobStore   
initialized.
3866 [main] INFO  org.quartz.impl.StdSchedulerFactory  - Quartz   
scheduler 'scheduler1' initialized from an externally provided   
properties instance.
3869 [main] INFO  org.quartz.impl.StdSchedulerFactory  - Quartz   
scheduler version: 1.4.5
3872 [main] INFO  org.quartz.core.QuartzScheduler  - Scheduler   
scheduler1_$_NON_CLUSTERED started.
3955 [main] INFO  org.apache.maven.continuum.Continuum  -   
Initializing Continuum.
3959 [main] INFO  org.apache.maven.continuum.Continuum  - Showing  
all  projects:
5325 [main] ERROR JPOX.RDBMS.SCHEMA  - Failed initialising  
database.  Please check that your database JDBC driver is  
accessible, and the  database URL and username/password are  
correct. Exception : Failed to  create database '/Applications/ 
continuum-latest/apps/continuum/ database', see the next exception  
for details.
SQL Exception: Failed to create database '/Applications/continuum-  
latest/apps/continuum/database', see the next exception for details.
at org.apache.derby.impl.jdbc.Util.newEmbedSQLException 
(Util.java)
at org.apache.derby.impl.jdbc.Util.newEmbedSQLException 
(Util.java)
at org.apache.derby.impl.jdbc.Util.generateCsSQLException  
(Util.java)
at org.apache.derby.impl.jdbc.EmbedConnection.newSQLException  
(EmbedConnection.java)
at org.apache.derby.impl.jdbc.EmbedConnection.createDatabase  
(EmbedConnection.java)
at org.apache.derby.impl.jdbc.EmbedConnection.init  
(EmbedConnection.java)
at org.apache.derby.impl.jdbc.EmbedConnection20.init  
(EmbedConnection20.java)
at org.apache.derby.impl.jdbc.EmbedConnection30.init  
(EmbedConnection30.java)
at org.apache.derby.jdbc.Driver30.getNewEmbedConnection  
(Driver30.java)

at org.apache.derby.jdbc.Driver169.connect(Driver169.java)
at java.sql.DriverManager.getConnection(DriverManager.java:525)
at java.sql.DriverManager.getConnection(DriverManager.java:171)
at org.jpox.DriverManagerDataSource.getConnection  
(DriverManagerDataSource.java:82)
at org.jpox.store.rdbms.RDBMSManager.init(RDBMSManager.java: 
219)
at org.jpox.store.rdbms.RDBMSManagerFactory.getStoreManager  
(RDBMSManagerFactory.java:59)
at org.jpox.AbstractPersistenceManager.init  
(AbstractPersistenceManager.java:194)
at org.jpox.PersistenceManagerImpl.init  
(PersistenceManagerImpl.java:34)
at  
org.jpox.PersistenceManagerFactoryImpl.getPersistenceManager  
(PersistenceManagerFactoryImpl.java:811)
at  
org.jpox.PersistenceManagerFactoryImpl.getPersistenceManager  
(PersistenceManagerFactoryImpl.java:786)
at   

Re: can't get alpha4 to work with java 5

2005-09-30 Thread Björn Sköld

On 30 sep 2005, at 16.51, Emmanuel Venisse wrote:

it's weird. With plexus.sh, it's a pure java, so perhaps there are  
a pb in derby with java 5.


It seems to be a derby problem with java5 on OS X. There is a  
workaround suggested here:


http://db.apache.org/derby/faq.html#createdb_OS_X

Mvh Björn





Re: can't get alpha4 to work with java 5

2005-09-30 Thread Emmanuel Venisse

Thanks Björn.

Emmanuel


Björn Sköld a écrit :

On 30 sep 2005, at 16.51, Emmanuel Venisse wrote:

it's weird. With plexus.sh, it's a pure java, so perhaps there are  a 
pb in derby with java 5.



It seems to be a derby problem with java5 on OS X. There is a  
workaround suggested here:


http://db.apache.org/derby/faq.html#createdb_OS_X

Mvh Björn