[
https://jira.codehaus.org/browse/MRM-1659?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Olivier Lamy closed MRM-1659.
-----------------------------
Resolution: Fixed
Apologize for delay on that.
So I have added
{code}
<dependency>
<groupId>cglib</groupId>
<artifactId>cglib</artifactId>
<version>2.2.2</version>
</dependency>
{code}
Doesn't look to have any side effect.
Let us know.
If you are using builds from
https://builds.apache.org/view/A-F/view/Archiva/job/archiva-all-maven-3.x-jdk-1.6/
that will be available with #1498
> Cannot connect to PostgreSQL
> ----------------------------
>
> Key: MRM-1659
> URL: https://jira.codehaus.org/browse/MRM-1659
> Project: Archiva
> Issue Type: Bug
> Components: system
> Affects Versions: 1.4-M3
> Environment: Windows XP Professional, Archiva as a .war deployed on
> Tomcat 7.0.26 (base separated from installation), PostgreSQL 9.1 used for
> FileSystem, DataStore, and Persistence Manager.
> Reporter: Chris Harris
> Assignee: Olivier Lamy
> Priority: Blocker
> Fix For: 1.4-M3
>
> Attachments: archiva.log, localhost.2012-09-06.log
>
>
> Archiva 1.4-M3 cannot start. I'm getting this error
> "java.sql.SQLFeatureNotSupportedException: Method
> org.postgresql.jdbc4.Jdbc4Statement.setQueryTimeout(int) is not yet
> implemented."
> I've tried archiva-webapp-js-1.4-M3-SNAPSHOT.war and
> archiva-webapp-1.4-M3-SNAPSHOT.war. Archiva will start if I use
> apache-archiva-1.4-M2.war. I have changed archiva.xml each time to point to
> the respective .war file.
> I tried using postgresql-9.1-901.jdbc4.jar and postgresql-9.1-902.jdbc4.jar,
> but neither worked. I get the same PostgreSQL-related error message.
> I've attached the Tomcat 7 log and archiva.log.
--
This message is automatically generated by JIRA.
If you think it was sent incorrectly, please contact your JIRA administrators:
https://jira.codehaus.org/secure/ContactAdministrators!default.jspa
For more information on JIRA, see: http://www.atlassian.com/software/jira
