Re: Continuum Model and Modello
Rahul Thakur a écrit : I have been wanting to pop this questions for sometime now. For generation/maintenance of continuum-model: a) Why are we using Modello? More specifically what does it buy us? I know the model is expressed as xml and separate from Java sources, but I don't see a benefit of having it in XML as opposed to annotations in java sources. modello file generate for use all model POJOs and the jpox metadata file. With it, we can define old fields that doesn't exist in the nex version and the migration tool use the model to do the db conversion. I don't think we can all of that with annotations. b) Since 1.1 is in final stages, also wanted to see what other think about brainstorming ideas for the next Continuum release on wiki. But this might be a candidate for a separate thread. Yes, it's a separate thread ;) Emmanuel Thoughts? Thanks, Rahul
Upgrade Mysql database from Continuum 1.1-beta-2 to beta-3
Hello, I would like to upgrade my continuum 1.1-beta-2 instance running with Mysql to continuum beta-3 version. I tried to use data-management-cli-1.1-beta-3-app.jar but it doesn't seem to support Mysql database. This tool always wants to use Derby JDBC driver. How to specify JDBC driver ? Any doc somewhere about this tool ? Thanks Damien
Re: Upgrade Mysql database from Continuum 1.1-beta-2 to beta-3
Hi, Commands to run will be available when we'll update the site for the release of 1.1-beta-3 For the moment, it isn't possible to migrate a mysql db (and other db that isn't derby) with this tool. We'll fix it in next version. But maybe you can write a patch for it so you'll can migrate, I can explain to you the codee to modify, it's a simple patch to write. Emmanuel Damien Lecan a écrit : Hello, I would like to upgrade my continuum 1.1-beta-2 instance running with Mysql to continuum beta-3 version. I tried to use data-management-cli-1.1-beta-3-app.jar but it doesn't seem to support Mysql database. This tool always wants to use Derby JDBC driver. How to specify JDBC driver ? Any doc somewhere about this tool ? Thanks Damien
Re: Upgrade Mysql database from Continuum 1.1-beta-2 to beta-3
2007/9/21, Emmanuel Venisse [EMAIL PROTECTED]: Commands to run will be available when we'll update the site for the release of 1.1-beta-3 For the moment, it isn't possible to migrate a mysql db (and other db that isn't derby) with this tool. We'll fix it in next version. But maybe you can write a patch for it so you'll can migrate, I can explain to you the codee to modify, it's a simple patch to write. Ok, let's try, i've just checkout continuum 1.1 beta-3 source code. Damien
Re: Upgrade Mysql database from Continuum 1.1-beta-2 to beta-3
http://jira.codehaus.org/browse/CONTINUUM-1481 Emmanuel Venisse a écrit : Changes must be done in http://svn.apache.org/repos/asf/maven/continuum/trunk/continuum-data-management/data-management-cli/src/main/java/org/apache/maven/continuum/management/DataManagementCli.java Look at the end to see derby parameters. A good patch would be to add an OTHER supported db that take parameters from the cli args Emmanuel Damien Lecan a écrit : 2007/9/21, Emmanuel Venisse [EMAIL PROTECTED]: Commands to run will be available when we'll update the site for the release of 1.1-beta-3 For the moment, it isn't possible to migrate a mysql db (and other db that isn't derby) with this tool. We'll fix it in next version. But maybe you can write a patch for it so you'll can migrate, I can explain to you the codee to modify, it's a simple patch to write. Ok, let's try, i've just checkout continuum 1.1 beta-3 source code. Damien
Re: Continuum Model and Modello
On 21/09/2007, at 5:31 PM, Emmanuel Venisse wrote: Rahul Thakur a écrit : I have been wanting to pop this questions for sometime now. For generation/maintenance of continuum-model: a) Why are we using Modello? More specifically what does it buy us? I know the model is expressed as xml and separate from Java sources, but I don't see a benefit of having it in XML as opposed to annotations in java sources. modello file generate for use all model POJOs and the jpox metadata file. With it, we can define old fields that doesn't exist in the nex version and the migration tool use the model to do the db conversion. I don't think we can all of that with annotations. The DB conversion is less than ideal though. I think the tools that OpenJPA already provide for doing such things are superior (from the brief look I've had). I'm thinking the model conversion is a bit of a seemed like a good idea at the time thing that I did... I'd be happier with coding it up by hand now and making the store simpler. In making the store simpler, and carefully mapping to tables, I think we can avoid the need for conversion anyway by trying to only make additions. I'd be willing to experiment with alternatives - perhaps it would be best to do this piece by piece though, rather than one big conversion (as the impl. currently leaks out all over - we need to better isolate the lazy loading and fetching of data through the actions before safely extracting pieces). Cheers, Brett -- Brett Porter - [EMAIL PROTECTED] Blog: http://www.devzuz.org/blogs/bporter/
Re: Upgrade Mysql database from Continuum 1.1-beta-2 to beta-3
Damien Lecan a écrit : 2007/9/21, Emmanuel Venisse [EMAIL PROTECTED]: http://jira.codehaus.org/browse/CONTINUUM-1481 Ok, I've got a patch which allows data-management-cli (dmc) to use Mysql jdbc driver class or any other driver BUT : - dmc always fails to download dependencies. It doesn't seem to use settings.xml configuration file (I'm working behind a proxy). I found a workaround to do my patch but many people will have problems with that - dmc fails to export data with the following error : NestedThrowablesStackTrace: com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Unknown column 'ELEMENT.ALWAYS_BUILD' in 'field list' at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:936) ... at org.apache.maven.continuum.management.DataManagementCli.main(DataManagementCli.java:164) The export tool itself fails to read old database schema. Something else to configure ? to export 1.1-beta-2 db, you must use dmc 1.1-beta-2 and to import in 1.1-beta-3 db, dmc 1.1-beta-3 About the settings.xml that isn't use, I fixed it this morning in trunk. Emmanuel
Re: Upgrade Mysql database from Continuum 1.1-beta-2 to beta-3
2007/9/21, Emmanuel Venisse [EMAIL PROTECTED]: http://jira.codehaus.org/browse/CONTINUUM-1481 Ok, I've got a patch which allows data-management-cli (dmc) to use Mysql jdbc driver class or any other driver BUT : - dmc always fails to download dependencies. It doesn't seem to use settings.xml configuration file (I'm working behind a proxy). I found a workaround to do my patch but many people will have problems with that - dmc fails to export data with the following error : NestedThrowablesStackTrace: com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Unknown column 'ELEMENT.ALWAYS_BUILD' in 'field list' at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:936) ... at org.apache.maven.continuum.management.DataManagementCli.main(DataManagementCli.java:164) The export tool itself fails to read old database schema. Something else to configure ? Damien
Re: relative path
It isn't too late for 1.1, we're releasing beta-3 and final won't be normally before one month. For your patch, please attach it to an issue. Emmanuel CAUSSE David MTP CAP GEM a écrit : Hi, I send to the list a patch to add better support for SCM providers that honour the relativePath field in ScmCheckoutResult. The idea is to add a new field in project because I think it's project specific and not build specific. This patch allow group builds to work with SCM like clearcase or SYNERGY (I'll send a scm patch soon for this one). I hope it is not too late for 1.1... -- David Causse DECLIC - DTE - Génie Logiciel - GCCL Tél: 04 67 04 79 09 Post-scriptum La Poste Ce message est confidentiel. Sous réserve de tout accord conclu par écrit entre vous et La Poste, son contenu ne représente en aucun cas un engagement de la part de La Poste. Toute publication, utilisation ou diffusion, même partielle, doit être autorisée préalablement. Si vous n'êtes pas destinataire de ce message, merci d'en avertir immédiatement l'expéditeur.
Re: [discuss] Graduate Continuum to its own TLP
- Original Message - From: Emmanuel Venisse [EMAIL PROTECTED] To: continuum-dev@maven.apache.org Sent: Saturday, September 22, 2007 3:57 AM Subject: [discuss] Graduate Continuum to its own TLP Hi, At the begin, Continuum was designed to support maven2 projects so we thought it was good to put it under the maven umbrella. But now it supports other project types (ANT, shell scripts) too so it isn't centered on maven projects. An other thing is that we have lot of users (not only maven users) with actually 450 subscribers to the users list, and I think we can get more with a TLP project. My last point is that with the maven project, it isn't easy to add new committers because a new committer have the hand on all maven umbrella code and not only one project. So I think it would be good for Continuum to become a Top Level Project at ASF and the continuum community will have more chance to grow. My concern for the moment is we don't have enough committer from different companies, To be stable, at least 3 committers from different companies would be good. While I am for Continuum as TLP, I don't understand the rationale behind having committers from different companies. How would this help to make Continuum more stable? Cheers, Rahul WDYT? Emmanuel
Re: [discuss] Graduate Continuum to its own TLP
I agree, I think continuum would make a good TLP and move out from the direct maven umbrella. We can attract committers that might not be totally driven with the maven2 koolaid if we are not strictly associated with that project. I know there are a lot of plans for continuum in the relatively near future and I think its an ideal time to take continuum up as a TLP. As for more committers, I think they will come with time and some of the work that is planned. Emm and I work for the same company but olamy is really active and new committer, and Rahul will probably be stepping up some more as we start working on some of the refactoring bits that have been discussed some (and he gets that whole marriage deal worked out). Anyway, I support this and it has been kicked around in the background for a while now. jesse On 9/21/07, Emmanuel Venisse [EMAIL PROTECTED] wrote: Hi, At the begin, Continuum was designed to support maven2 projects so we thought it was good to put it under the maven umbrella. But now it supports other project types (ANT, shell scripts) too so it isn't centered on maven projects. An other thing is that we have lot of users (not only maven users) with actually 450 subscribers to the users list, and I think we can get more with a TLP project. My last point is that with the maven project, it isn't easy to add new committers because a new committer have the hand on all maven umbrella code and not only one project. So I think it would be good for Continuum to become a Top Level Project at ASF and the continuum community will have more chance to grow. My concern for the moment is we don't have enough committer from different companies, To be stable, at least 3 committers from different companies would be good. WDYT? Emmanuel -- jesse mcconnell [EMAIL PROTECTED]
Re: [discuss] Graduate Continuum to its own TLP
Hi, +1. It will help to find more committers to implement all great new features. -- Olivier 2007/9/21, Emmanuel Venisse [EMAIL PROTECTED]: Hi, At the begin, Continuum was designed to support maven2 projects so we thought it was good to put it under the maven umbrella. But now it supports other project types (ANT, shell scripts) too so it isn't centered on maven projects. An other thing is that we have lot of users (not only maven users) with actually 450 subscribers to the users list, and I think we can get more with a TLP project. My last point is that with the maven project, it isn't easy to add new committers because a new committer have the hand on all maven umbrella code and not only one project. So I think it would be good for Continuum to become a Top Level Project at ASF and the continuum community will have more chance to grow. My concern for the moment is we don't have enough committer from different companies, To be stable, at least 3 committers from different companies would be good. WDYT? Emmanuel -- Olivier
Re: [discuss] Graduate Continuum to its own TLP
On 22/09/2007, at 7:34 AM, Rahul Thakur wrote: So I think it would be good for Continuum to become a Top Level Project at ASF and the continuum community will have more chance to grow. I agree. It is effectively running itself already. My concern for the moment is we don't have enough committer from different companies, To be stable, at least 3 committers from different companies would be good. While I am for Continuum as TLP, I don't understand the rationale behind having committers from different companies. How would this help to make Continuum more stable? Stability from a community point of view. Firstly, we need to ensure we have enough committers in the first place - for example, to ensure that if Emmanuel decided he could no longer participate, the project would need to be able to survive (though obviously, miss him greatly :) Having those committers from a diverse set of companies is an extra safeguard to ensure that no single company either controls the direction of the project, or could cause it problems by withdrawing people's time on it. To be clear, there's no reason to suspect this is a problem now - it's just a worthy thing to have in a project. I think everything is on track here - the first focus should be on getting 1.1 out of course, but if we keep doing what we are doing this totally makes sense. Cheers, Brett -- Brett Porter - [EMAIL PROTECTED] Blog: http://www.devzuz.org/blogs/bporter/
