Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [gemini-dev] Gemini DBAccess: Hudson build and p2 Update Site of the Last Successful Build 
Hi Nepomuk, Cristiano,

Thanks! I have submitted the patch and triggered a maven build.

- Juergen

Am 06.03.2012 um 19:36 schrieb "Nepomuk Seiler" <nepomuk.seiler@xxxxxxxx<mailto:nepomuk.seiler@xxxxxxxx>>:

Hi,

That's correct. I already reported this back and created a fix.
https://bugs.eclipse.org/bugs/show_bug.cgi?id=372428

cheers,
Muki

Am 06.03.2012 19:14, schrieb Cristiano Gavião:
Hi Juergen,

I just found that you are not registering the mysql service with osgi.jdbc.driver.class property. you are using only the osgi.jdbc.driver.name. This way Gemini JPA can't find this service:

{org.osgi.service.jdbc.DataSourceFactory}={osgi.jdbc.driver.name=MySQL, service.id=39}
  Registered by bundle: org.eclipse.gemini.dbaccess.mysql_1.1.0.201202221656 [17]
  No bundles using service.

Derby is ok:
org.eclipse.gemini.dbaccess.derby_1.1.0.201202221656 [20]
  Id=20, Status=ACTIVE      Data Root=/Users/cvgaviao/Workspaces/jbehave-osgi-examples-indigo/.metadata/.plugins/org.eclipse.pde.core/TestJPA/org.eclipse.osgi/bundles/20/data
  Registered Services
    {org.osgi.service.jdbc.DataSourceFactory}={osgi.jdbc.driver.class=org.apache.derby.jdbc.EmbeddedDriver, osgi.jdbc.driver.version=3.0, osgi.jdbc.driver.name=Derby, service.id=40}
    {org.osgi.service.jdbc.DataSourceFactory}={osgi.jdbc.driver.class=org.apache.derby.jdbc.ClientDriver, osgi.jdbc.driver.version=3.0, osgi.jdbc.driver.name=Derby, service.id=41}
    {org.osgi.service.jdbc.DataSourceFactory}={osgi.jdbc.driver.class=org.apache.derby.jdbc.EmbeddedDriver, osgi.jdbc.driver.version=4.0, osgi.jdbc.driver.name=Derby, service.id=42}
    {org.osgi.service.jdbc.DataSourceFactory}={osgi.jdbc.driver.class=org.apache.derby.jdbc.ClientDriver, osgi.jdbc.driver.version=4.0, osgi.jdbc.driver.name=Derby, service.id=43}
  No services in use.
  No exported packages


regards,

Cristiano


On 26/02/12 20:23, Kissner, Juergen wrote:
Hi Cristiano,
thanks for interest in DBAccess.

I am not sure I exactly understand your suggestion. Do you like us to offer MySQL and (the latest version of) Derby through the eclipse orbit? For Derby 10.8.2.2 this should not be a problem. For MySQL the GPL license is, as far as I can tell, not compatible with the Eclipse license.

Best Regards,
  Juergen

Ps.:
I very briefly tried to look into you projects that your mentioned below. A quick check to sync and build your Utils  did not work for me (my maven version is 3.0.3):
>  mvn clean verify -P p2-all
complained about a non-existing file .options in com.c4biz.osgiutils.configuration.tests directory. However, I did not have the time for a closer look…



From: gemini-dev-bounces@xxxxxxxxxxx<mailto:gemini-dev-bounces@xxxxxxxxxxx> [mailto:gemini-dev-bounces@xxxxxxxxxxx] On Behalf Of Cristiano Gavião
Sent: Donnerstag, 23. Februar 2012 15:01
To: Gemini and sub-projects developer discussions
Subject: Re: [gemini-dev] Gemini DBAccess: Hudson build and p2 Update Site of the Last Successful Build

Hi Juergen,

what do you think about to include two more features in this p2. one for derby and another for mysql drivers ?

Derby already exists on orbit, but an old one...

I already did this in my own p2 https://github.com/cvgaviao/osgi-utils/tree/master/com.c4biz.osgiutils.feature.mysql and https://github.com/cvgaviao/osgi-utils/tree/master/com.c4biz.osgiutils.feature.derby

if you think it is valid let me know that I migrate it to dbaccess...

cheers

Cristiano

On 22/02/12 19:32, Kissner, Juergen wrote:
The name of the Hudson build job for DBAccess has changed from gemini-dbaccess-1.1-snapshot to gemini-dbaccess, leading to a new URL [1]. Please note that this also affects the URL of the p2 update site of the last successful build [2].

-Juergen

[1] https://hudson.eclipse.org/hudson/job/gemini-dbaccess/
[2] https://hudson.eclipse.org/hudson/job/gemini-dbaccess/lastSuccessfulBuild/artifact/gemini.dbaccess.updatesite/target/site/







_______________________________________________

gemini-dev mailing list

gemini-dev@xxxxxxxxxxx<mailto:gemini-dev@xxxxxxxxxxx>

https://dev.eclipse.org/mailman/listinfo/gemini-dev




_______________________________________________
gemini-dev mailing list
gemini-dev@xxxxxxxxxxx<mailto:gemini-dev@xxxxxxxxxxx>
https://dev.eclipse.org/mailman/listinfo/gemini-dev





_______________________________________________
gemini-dev mailing list
gemini-dev@xxxxxxxxxxx<mailto:gemini-dev@xxxxxxxxxxx>
https://dev.eclipse.org/mailman/listinfo/gemini-dev


_______________________________________________
gemini-dev mailing list
gemini-dev@xxxxxxxxxxx<mailto:gemini-dev@xxxxxxxxxxx>
https://dev.eclipse.org/mailman/listinfo/gemini-dev

Back to the top