Re: [vote] Release Continuum 1.1 Final
+1 Stéphane On Nov 16, 2007 10:02 PM, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: > Hi, > > Continuum 1.1 Final is ready for release > > The highlights are > - bug fixes > - A new backup tool with xmlrpc for continuum db (not the users db) > > The Release Notes is available there: > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10540&styleName=Html&version=13605 > > The binaries are available there: > - Runtime: > http://people.apache.org/builds/maven/continuum/1.1/org/apache/maven/continuum/continuum-plexus-runtime/1.1/continuum-plexus-runtime-1.1-bin.tar.gz > - Webapp: > http://people.apache.org/builds/maven/continuum/1.1/org/apache/maven/continuum/continuum-webapp/1.1/continuum-webapp-1.1.war > - data management cli: > http://people.apache.org/builds/maven/continuum/1.1/org/apache/maven/continuum/data-management-cli/1.1/data-management-cli-1.1-app.jar > - xmlrpc backup tool : > http://people.apache.org/builds/maven/continuum/1.1/org/apache/maven/continuum/continuum-xmlrpc-backup/1.1/continuum-xmlrpc-backup-1.1-app.jar > > The file generated by the backup tool can be used with data management cli to > re-import data. > > Everyone is encouraged to vote and give their feedback. > > [ ] +1 Release it! > [ ] 0 > [ ] -1 Don't release it, because... > > > As we don't have a small bug fixes list, the vote will be open for one week > to let you test it. So, cast your votes now ;-) > > Here's my +1 > > Thanks, > Emmanuel > > > > > -- Large Systems Suck: This rule is 100% transitive. If you build one, you suck" -- S.Yegge
Re: [vote] Release Continuum 1.1-beta-2
+1 Stéphane On 8/14/07, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: > Hi, > > Continuum 1.1-beta-2 is ready for release > > The highlights are > - lot of bug fixes > - Installations/profiles screens improvement > - screen flow improvement in Add Project part > - cancellable builds > > The Release Notes is available there: > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10540&styleName=Html&version=13606 > > The binaries are available there: > - Runtime: > http://people.apache.org/builds/maven/continuum/1.1-beta-2/org/apache/maven/continuum/continuum-plexus-runtime/1.1-beta-2/continuum-plexus-runtime-1.1-beta-2-bin.tar.gz > - Webapp: > http://people.apache.org/builds/maven/continuum/1.1-beta-2/org/apache/maven/continuum/continuum-webapp/1.1-beta-2/continuum-webapp-1.1-beta-2.war > - data management cli: > http://people.apache.org/builds/maven/continuum/1.1-beta-2/org/apache/maven/continuum/data-management-cli/1.1-beta-2/data-management-cli-1.1-beta-2-app.jar > > Everyone is encouraged to vote and give their feedback. > > [ ] +1 Release it! > [ ] 0 > [ ] -1 Don't release it, because... > > > The vote will be open for 72 hours. So, cast your votes now ;-) > > Here's my +1 > > Thanks, > Emmanuel > > -- Large Systems Suck: This rule is 100% transitive. If you build one, you suck" -- S.Yegge
Re: [OT] Mini-interview with Emmanuel Venisse
sans blague! On 8/7/07, Jesse McConnell <[EMAIL PROTECTED]> wrote: > Emmanuel is French!?!?!?!?! :) > > On 8/6/07, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > Hi all, > > > > I already posted this to the users@ list, but I thought some folk > > here might be more particularly interested in what Emmanuel had to > > say when we talked recently: http://www.devzuz.org/?q=node/12. > > > > Enjoy! > > > > Cheers, > > Brett > > > > > > > -- > jesse mcconnell > [EMAIL PROTECTED] > -- Large Systems Suck: This rule is 100% transitive. If you build one, you suck" -- S.Yegge
Re: [vote] release continuum 1.1-beta-1
Cool. Do not forget to add something in the release note regarding the UTF-8 problem with Mysql. Cheers, Stéphane On 7/25/07, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: The vote has passed with 4 binding +1's from PMC members: Jesse, Wendy, Trygve, me 2 non-binding +1's from committers: Deng, Stephane I started to deployed all things and I'll send an announcement when all will be ready for users. Thanks, Emmanuel Emmanuel Venisse a écrit : > Hi, > > I'd like to do a release of the 1.1-beta-1 > > This version is very stable and usable in production. > > Highlights are: > - Continuum Profiles definition linked to build definitions. > - multi-builddefinitions on a project > > Release notes: > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10540&styleName=Html&version=13432 > > > I have staged it in this repo: > http://people.apache.org/~evenisse/stage/continuum-repo/ > This repo include too the continuum plugin and th xml-rpc client API > > Standalone version: > http://people.apache.org/~evenisse/stage/continuum-repo/org/apache/maven/continuum/continuum-plexus-runtime/1.1-beta-1/ > > Webapp version: > http://people.apache.org/~evenisse/stage/continuum-repo/org/apache/maven/continuum/continuum-webapp/1.1-beta-1/continuum-webapp-1.1-beta-1.war > > > The site will be updated in the next beta, only the download page will > be updated for this version. > > My +1 > > Emmanuel > > > -- Large Systems Suck: This rule is 100% transitive. If you build one, you suck" -- S.Yegge
Re: [vote] release continuum 1.1-beta-1
It would be nice to document the limitation with UTF-8 databases. Otherwise +1 Stéphane On 7/20/07, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: Hi, I'd like to do a release of the 1.1-beta-1 This version is very stable and usable in production. Highlights are: - Continuum Profiles definition linked to build definitions. - multi-builddefinitions on a project Release notes: http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10540&styleName=Html&version=13432 I have staged it in this repo: http://people.apache.org/~evenisse/stage/continuum-repo/ This repo include too the continuum plugin and th xml-rpc client API Standalone version: http://people.apache.org/~evenisse/stage/continuum-repo/org/apache/maven/continuum/continuum-plexus-runtime/1.1-beta-1/ Webapp version: http://people.apache.org/~evenisse/stage/continuum-repo/org/apache/maven/continuum/continuum-webapp/1.1-beta-1/continuum-webapp-1.1-beta-1.war The site will be updated in the next beta, only the download page will be updated for this version. My +1 Emmanuel -- Large Systems Suck: This rule is 100% transitive. If you build one, you suck" -- S.Yegge
Re: [vote] release continuum 1.1-beta-1
We switched to latin1 and it worked FYI. On 7/20/07, Stephane Nicoll <[EMAIL PROTECTED]> wrote: With a Mysql5 UTF-8 database I got this:
Re: [vote] release continuum 1.1-beta-1
With a Mysql5 UTF-8 database I got this: Error thrown executing CREATE TABLE `INSTALLATION` ( `NAME` VARCHAR(256) BINARY NOT NULL, `MODEL_ENCODING` VARCHAR(256) BINARY NULL, `INSTALLATIONTYPE` VARCHAR(256) BINARY NULL, `VAR_NAME` VARCHAR(256) BINARY NULL, `VAR_VALUE` VARCHAR(256) BINARY NULL, PRIMARY KEY (`NAME`) ) ENGINE=INNODB : Specified key was too long; max key length is 765 bytes com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Specified key was too long; max key length is 765 bytes at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:936) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2934) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1616) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1708) at com.mysql.jdbc.Connection.execSQL(Connection.java:3249) at com.mysql.jdbc.Connection.execSQL(Connection.java:3178) at com.mysql.jdbc.Statement.execute(Statement.java:711) at org.apache.tomcat.dbcp.dbcp.DelegatingStatement.execute(DelegatingStatement.java:264) at org.jpox.store.rdbms.table.AbstractTable.executeDdlStatement(AbstractTable.java:614) at org.jpox.store.rdbms.table.AbstractTable.executeDdlStatementList(AbstractTable.java:570) at org.jpox.store.rdbms.table.AbstractTable.create(AbstractTable.java:297) at org.jpox.store.rdbms.table.AbstractTable.exists(AbstractTable.java:341) at org.jpox.store.rdbms.RDBMSManager$ClassAdder.performTablesValidation(RDBMSManager.java:3052) at org.jpox.store.rdbms.RDBMSManager$ClassAdder.addClassTablesAndValidate(RDBMSManager.java:3313) at org.jpox.store.rdbms.RDBMSManager$ClassAdder.run(RDBMSManager.java:2554) at org.jpox.store.rdbms.RDBMSManager$MgmtTransaction.execute(RDBMSManager.java:2406) at org.jpox.store.rdbms.RDBMSManager.addClasses(RDBMSManager.java:821) at org.jpox.store.rdbms.RDBMSManager.addClass(RDBMSManager.java:835) at org.jpox.store.StoreManager.getDatastoreClass(StoreManager.java:1161) at org.jpox.store.rdbms.RDBMSManager.getExtent(RDBMSManager.java:1354) at org.jpox.AbstractPersistenceManager.getExtent(AbstractPersistenceManager.java:2312) at org.codehaus.plexus.jdo.PlexusJdoUtils.getAllObjectsDetached(PlexusJdoUtils.java:358) at org.codehaus.plexus.jdo.PlexusJdoUtils.getAllObjectsDetached(PlexusJdoUtils.java:342) at org.apache.maven.continuum.store.JdoContinuumStore.getAllObjectsDetached(JdoContinuumStore.java:1558) at org.apache.maven.continuum.store.JdoContinuumStore.getAllObjectsDetached(JdoContinuumStore.java:1543) at org.apache.maven.continuum.store.JdoContinuumStore.getAllProjectsByNameWithBuildDetails(JdoContinuumStore.java:892) at org.apache.maven.continuum.DefaultContinuum.initialize(DefaultContinuum.java:2304) at org.codehaus.plexus.personality.plexus.lifecycle.phase.InitializePhase.execute(InitializePhase.java:33) at org.codehaus.plexus.lifecycle.AbstractLifecycleHandler.start(AbstractLifecycleHandler.java:128) at org.codehaus.plexus.component.manager.AbstractComponentManager.startComponentLifecycle(AbstractComponentManager.java:142) at org.codehaus.plexus.component.manager.AbstractComponentManager.createComponentInstance(AbstractComponentManager.java:132) at org.codehaus.plexus.component.manager.ClassicSingletonComponentManager.getComponent(ClassicSingletonComponentManager.java:90) at org.codehaus.plexus.DefaultComponentLookupManager.lookup(DefaultComponentLookupManager.java:147) at org.codehaus.plexus.DefaultPlexusContainer.lookup(DefaultPlexusContainer.java:327) at org.codehaus.plexus.container.initialization.StartLoadOnStartComponentsPhase.execute(StartLoadOnStartComponentsPhase.java:68) at org.codehaus.plexus.DefaultPlexusContainer.initializePhases(DefaultPlexusContainer.java:886) at org.codehaus.plexus.DefaultPlexusContainer.initialize(DefaultPlexusContainer.java:834) at org.codehaus.plexus.DefaultPlexusContainer.construct(DefaultPlexusContainer.java:811) at org.codehaus.plexus.DefaultPlexusContainer.(DefaultPlexusContainer.java:222) at org.codehaus.plexus.DefaultPlexusContainer.(DefaultPlexusContainer.java:260) at org.codehaus.plexus.xwork.PlexusLifecycleListener.contextInitialized(PlexusLifecycleListener.java:76) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3827) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4334) at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:791) at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:771) at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:525) at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:626) at org.apache.catalina.startup.HostConfi
Re: svn commit: r555633 - /maven/continuum/trunk/continuum-model/src/main/mdo/continuum.xml
While you're at it, can you look to http://jira.codehaus.org/browse/CONTINUUM-1194 please? ;-) I've already looked into it, a simple catch would do it (at least prevent the build to be stuck in "building" Thanks, Stéphane On 7/12/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: Author: evenisse Date: Thu Jul 12 07:06:36 2007 New Revision: 555633 URL: http://svn.apache.org/viewvc?view=rev&rev=555633 Log: [CONTINUUM-1320] Increase the size of the commandLine field Modified: maven/continuum/trunk/continuum-model/src/main/mdo/continuum.xml Modified: maven/continuum/trunk/continuum-model/src/main/mdo/continuum.xml URL: http://svn.apache.org/viewvc/maven/continuum/trunk/continuum-model/src/main/mdo/continuum.xml?view=diff&rev=555633&r1=555632&r2=555633 == --- maven/continuum/trunk/continuum-model/src/main/mdo/continuum.xml (original) +++ maven/continuum/trunk/continuum-model/src/main/mdo/continuum.xml Thu Jul 12 07:06:36 2007 @@ -648,7 +648,7 @@ 1.0.9+ boolean - + commandLine 1.0.9+ String -- Large Systems Suck: This rule is 100% transitive. If you build one, you suck" -- S.Yegge
Re: DB schema migration
Hi, On 4/25/07, Trygve Laugstøl <[EMAIL PROTECTED]> wrote: Stephane Nicoll wrote: > Can I be sure at least that the DB model won't change as from alpha-1? > If so I can maybe drop completely my database and recreate my > projects. We've been over this before, but I'll repeat: Alphas give no guarantee of API (including DB) stability. Hopefully it won't change too much, but it should in no way stop the developers from breaking stuff. I agree. What is important here is the ability to dump the database to an external DB file (xml would be a natural choice) which can be read by a newer Continuum. As soon as this is in place, I'll migrate. Cheers, Stéphane Hopefully 1.1 will be pretty stable so it can be released ASAP and bugs can be fixed on a 1.1.x branch. -- Trygve > > Thanks, > Stéphane > > On 4/23/07, Brett Porter <[EMAIL PROTECTED]> wrote: >> This was one of the things I was going to try and have done before >> alpha-1 - I just forgot. >> >> Erik - the problem in upgrading is the changes in private tables >> between versions of jpox that we hadn't given explicit names to. We'd >> probably appreciate most help in future proofing our jpox use a bit >> more in case it's internal schema changes again. >> >> I already have the tools to do an xml export of the old tables, it >> just needs to somehow be set to run in dump mode using the old jpox, >> and import using the new one. I'll look at that during ApacheCon, I >> think. If anyone else wants to take the task while I'm on holidays, >> let me know... we should also make the tool work with 1.0.3 databases >> if possible. >> >> This is definitely one for the release notes, btw. alpha-1 will not >> work with 1.0.3 (or earlier 1.1 snapshot) databases. >> >> - Brett >> >> On 22/04/2007, at 2:10 PM, Erik Bengtson wrote: >> >> > If you guys need some tooling from JPOX, let me know and I could >> > plan to >> > implement some kind of "export" to XML, and "import" from XML. In >> > between >> > export/import you could apply Xqueries to transform data to match >> > the new >> > schema >> > >> > Quoting Stephane Nicoll <[EMAIL PROTECTED]>: >> > >> >> Hi, >> >> >> >> I'm currently running a 1.1-SNAPSHOT from February which runs ok >> >> except a few minor issues. I'd like to upgrade to 1.1 alpha 1 as soon >> >> as it's out to provide feedback & co. >> >> >> >> Last time I tried to upgrade, I had to revert because the model >> >> schema >> >> has changed and it was really difficult to update my existing >> >> data. Is >> >> there something scheduled for alpha1 regarding this (at least a >> >> manual >> >> procedure to upgrade my schema if necessary). >> >> >> >> Thanks, >> >> Stéphane >> >> >> > >> > >>
Re: DB schema migration
Can I be sure at least that the DB model won't change as from alpha-1? If so I can maybe drop completely my database and recreate my projects. Thanks, Stéphane On 4/23/07, Brett Porter <[EMAIL PROTECTED]> wrote: This was one of the things I was going to try and have done before alpha-1 - I just forgot. Erik - the problem in upgrading is the changes in private tables between versions of jpox that we hadn't given explicit names to. We'd probably appreciate most help in future proofing our jpox use a bit more in case it's internal schema changes again. I already have the tools to do an xml export of the old tables, it just needs to somehow be set to run in dump mode using the old jpox, and import using the new one. I'll look at that during ApacheCon, I think. If anyone else wants to take the task while I'm on holidays, let me know... we should also make the tool work with 1.0.3 databases if possible. This is definitely one for the release notes, btw. alpha-1 will not work with 1.0.3 (or earlier 1.1 snapshot) databases. - Brett On 22/04/2007, at 2:10 PM, Erik Bengtson wrote: > If you guys need some tooling from JPOX, let me know and I could > plan to > implement some kind of "export" to XML, and "import" from XML. In > between > export/import you could apply Xqueries to transform data to match > the new > schema > > Quoting Stephane Nicoll <[EMAIL PROTECTED]>: > >> Hi, >> >> I'm currently running a 1.1-SNAPSHOT from February which runs ok >> except a few minor issues. I'd like to upgrade to 1.1 alpha 1 as soon >> as it's out to provide feedback & co. >> >> Last time I tried to upgrade, I had to revert because the model >> schema >> has changed and it was really difficult to update my existing >> data. Is >> there something scheduled for alpha1 regarding this (at least a >> manual >> procedure to upgrade my schema if necessary). >> >> Thanks, >> Stéphane >> > >
Re: DB schema migration
Hi, On 4/23/07, Brett Porter <[EMAIL PROTECTED]> wrote: This is definitely one for the release notes, btw. alpha-1 will not work with 1.0.3 (or earlier 1.1 snapshot) databases. Too bad. Honestly, this will be a show stopper for people already using 1.0.3 (or 1.1-SNAPSHOT like me). Thanks for handling this anyway. Stéphane - Brett On 22/04/2007, at 2:10 PM, Erik Bengtson wrote: > If you guys need some tooling from JPOX, let me know and I could > plan to > implement some kind of "export" to XML, and "import" from XML. In > between > export/import you could apply Xqueries to transform data to match > the new > schema > > Quoting Stephane Nicoll <[EMAIL PROTECTED]>: > >> Hi, >> >> I'm currently running a 1.1-SNAPSHOT from February which runs ok >> except a few minor issues. I'd like to upgrade to 1.1 alpha 1 as soon >> as it's out to provide feedback & co. >> >> Last time I tried to upgrade, I had to revert because the model >> schema >> has changed and it was really difficult to update my existing >> data. Is >> there something scheduled for alpha1 regarding this (at least a >> manual >> procedure to upgrade my schema if necessary). >> >> Thanks, >> Stéphane >> > >
DB schema migration
Hi, I'm currently running a 1.1-SNAPSHOT from February which runs ok except a few minor issues. I'd like to upgrade to 1.1 alpha 1 as soon as it's out to provide feedback & co. Last time I tried to upgrade, I had to revert because the model schema has changed and it was really difficult to update my existing data. Is there something scheduled for alpha1 regarding this (at least a manual procedure to upgrade my schema if necessary). Thanks, Stéphane
Re: Preparing for continuum-1.1-alpha-1
On 3/7/07, Brett Porter <[EMAIL PROTECTED]> wrote: On 07/03/2007, at 9:52 AM, Jesse McConnell wrote: > > I think I'll start in on the data management bit now since that seems > like the biggest hurdle. I am not convinced we really need to worry > about a continuum 1.0.3 -> continuum 1.1 migration ability...its not a > difficult thing to get projects loaded back up into continuum...but > we'll see I guess. It is a pain, but having said that we could potentially add it in a later milestone. I wouldn't want a final version without it. +1
Re: Poll: release continuum alpha
On 2/23/07, Trygve Laugstøl <[EMAIL PROTECTED]> wrote: A milestone should focus on showing the fancy new features and bugs fixed. Stuff like security, upgrading existing databases etc are all secondary. I understand what you mean but I think database upgrade is very important because users will want to test continuum 1.1 with their data. This first release will also give you a chance to test your upgrade procedure. Stephane This will give the community the ability to check in on the latest development and make sure that the developers don't stray too far away from what the users actually need. > [+1/0/-1] I though you said that this wasn't a vote? ;) Thanks a whole lot for listening to me and taking the time to do this Jesse. I am very interested in getting 1.1 (or 1.0.4 if it has to be) out the door and can hopefully do some work for you guys. -- Trygve
Re: svn commit: r508033 - /maven/continuum/trunk/continuum-webapp/src/main/webapp/WEB-INF/jsp/admin/appearance.jsp
On 2/18/07, Brett Porter <[EMAIL PROTECTED]> wrote: No, I don't think so - I wonder if it is using the wrong local repository? Dunno. How can I know which repo it's using? Stéphane I used the Maven builder helper to obtain it, which should use the same location. - Brett On 16/02/2007, at 10:33 PM, Stephane Nicoll wrote: > I have also the following situation for the company pom. > > My company pom is: com.foo foo-parent. I have the v4 version of this > pom in the local repository used by continuum. > > continuum keeps on displaying that the company pom does not exist. Is > this fix related? > > Thanks, > Stéphane > > On 2/15/07, [EMAIL PROTECTED] <[EMAIL PROTECTED]> wrote: >> Author: brett >> Date: Thu Feb 15 09:44:11 2007 >> New Revision: 508033 >> >> URL: http://svn.apache.org/viewvc?view=rev&rev=508033 >> Log: >> handle companyPom being set, but fields being empty >> >> Modified: >> maven/continuum/trunk/continuum-webapp/src/main/webapp/WEB-INF/ >> jsp/admin/appearance.jsp >> >> Modified: maven/continuum/trunk/continuum-webapp/src/main/webapp/ >> WEB-INF/jsp/admin/appearance.jsp >> URL: http://svn.apache.org/viewvc/maven/continuum/trunk/continuum- >> webapp/src/main/webapp/WEB-INF/jsp/admin/appearance.jsp? >> view=diff&rev=508033&r1=508032&r2=508033 >> = >> = >> --- maven/continuum/trunk/continuum-webapp/src/main/webapp/WEB-INF/ >> jsp/admin/appearance.jsp (original) >> +++ maven/continuum/trunk/continuum-webapp/src/main/webapp/WEB-INF/ >> jsp/admin/appearance.jsp Thu Feb 15 09:44:11 2007 >> @@ -58,13 +58,13 @@ >> >> >> >> - >> + >> >> You have not yet specified a company POM. Select a Company POM >> >> >> >> - >> + >> >> Your selected company POM is below. If you would like to >> change the organization name, url or logo, you can >> edit the POM. >> @@ -113,4 +113,4 @@ >> >> >> >> - >> \ No newline at end of file >> + >> >> >>
