Continuum Archiva on Tomcat together and appserver.base variable
Hello, Continuum and Archiva share the same use of appserver.base variable. This is a problem when they are deployed together, in Tomcat for example. How to specify one appserver.base for continuum and one for Archiva ? I don't know where to report that in Jira, Continuum or Archiva bug/enhancement ? Plexus one ? Thanks Damien Lecan
Re: Continuum Archiva on Tomcat together and appserver.base variable
What is the problem? Emmanuel Damien Lecan a écrit : Hello, Continuum and Archiva share the same use of appserver.base variable. This is a problem when they are deployed together, in Tomcat for example. How to specify one appserver.base for continuum and one for Archiva ? I don't know where to report that in Jira, Continuum or Archiva bug/enhancement ? Plexus one ? Thanks Damien Lecan
Continuum 1.2 Roadmap
Hi, We are near the end of 1.1, it's time to discuss of 1.2 roadmap :) For this new version, my vision is: - Rewrite all the UI with a full GWT site. I want to migrate to GWT because we need better performance on the UI even if it is correct now. The second point is that with GWT (and Ajax in general) we'll can add nice features (maybe not in 1.2) to users like auto-refresh of small part of pages, users spaces, dynamic chart... And the last point of the GWT choice is all the code is written in java with a verification of all parts by the compiler (properties undeclared or unused, css style doesn't exist,...) so we'll reduce typo errors that we got sometimes. - Externalization of all the configuration. In this version, I want to move all the conf that is actually embedded in application.xml to a file more visible by the user. We can use plexus-registry for this. - Better support of XML-RPC and other remote access (XFire, ...). For this point, I think it would be good to share the code with the GWT part with some services classes that will embed all the remote code with security checks - Better support of maven projects. Actually, we detect if a build is required by looking at scm changes and dependencies changes. The problem is in dependencies changes. We look only at dependencies that are a continuum project too, it would be good to check repositories to find if a new version exists like maven do it. An other problem with dependencies changes is we don't really check if a new version exists but only if a new build result was created, it's a problem in case of projects with more than one build definition (for example clean install and site). If a site is generated, a new build result is created and continuum consider it as a dependency change so it rebuild all dependent projects in the next step. About GWT, I found few guys (6) that want to spend some time to do the migration and investigate on some new UI features. This roadmap is short because I don't want to wait a new time a long wait before to release a new 1.x version and I'd like to attract new users. I'd like to release 1.2 betfore the end of the year. I'll send a new mail in few weeks about 2.0 roadmap that will require more work. wdyt? Emmanuel
Re: Continuum 1.2 Roadmap
On 10/3/07, Emmanuel Venisse [EMAIL PROTECTED] wrote: We are near the end of 1.1, it's time to discuss of 1.2 roadmap :) For this new version, my vision is: Sounds good in general. I'm not thrilled with GWT-- I'm suspicious of code generation-- but since I'm not doing the work I'm not going to complain (too much) (until it breaks). If you're going to completely change the UI, then this is going to feel like a 2.0 even if not much changes behind the scenes functionality wise. We've talked about Continuum being distributed-- having a master server that farms out builds to others, or at least consolidates the build results from all of the others. That might be something for 2.0 (or 3.0, see above. :) though ). Thanks! -- Wendy
Re: Continuum 1.2 Roadmap
On 10/3/07, Emmanuel Venisse [EMAIL PROTECTED] wrote: We are near the end of 1.1, it's time to discuss of 1.2 roadmap :) For this new version, my vision is: Sounds good in general. I'm not thrilled with GWT-- I'm suspicious of code generation-- but since I'm not doing the work I'm not going to complain (too much) (until it breaks). GWT seems to be good and easy to use. All GWT users I met don't want to change now and they work on some very big applications If you're going to completely change the UI, then this is going to feel like a 2.0 even if not much changes behind the scenes functionality wise. I don't think to change completely the UI in 1.2, only the web framework and some new UI features but pages will be approximatively the same we have actually. Big UI changes will be for 2.0, if we need to do big changes. We've talked about Continuum being distributed-- having a master server that farms out builds to others, or at least consolidates the build results from all of the others. That might be something for 2.0 (or 3.0, see above. :) though ). About the consolidation/dashboard, maybe we'll can add it in 1.2 but I don't think. But I'm sure distributed builds will be in 2.0, we'll can't wait 3.0 ;) Emmanuel
