RE: Maven 2 - POM Hookup Question
Hi Wendy, Projects are sitting inside Perforce - would you use the Perforce web interface to expose the pom? The Perforce web setup is basically the normal p4 client but web implementation (from my little experience with it). Thanks for the reply. Regards, Randall -Original Message- From: Wendy Smoak [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 22, 2007 9:22 PM To: continuum-users@maven.apache.org Subject: Re: Maven 2 - POM Hookup Question On 5/22/07, Randall Fidler <[EMAIL PROTECTED]> wrote: > When providing Continuum with a Maven POM via URL, what URL? POM's > sitting on a local Maven repository? The pom which is located in/on the > projects website (i.e. website generated by site goal in maven)? Where > is this POM located? Also, how does this work for multi-module POMs? > Assuming they'd have their own maven project and you can point to the > pom there? Usually, it's the pom sitting in the project's source control repository, which is often visible via a http or https url. Is that an option for your project? Once Continuum retrieves the pom, it uses the (different) url in the element to check out the source code. When the pom has modules, they will get added to the project group as individual projects. I'm not sure at which step that happens, but it does happen. -- Wendy
Re: Maven 2 - POM Hookup Question
On 5/22/07, Randall Fidler <[EMAIL PROTECTED]> wrote: When providing Continuum with a Maven POM via URL, what URL? POM's sitting on a local Maven repository? The pom which is located in/on the projects website (i.e. website generated by site goal in maven)? Where is this POM located? Also, how does this work for multi-module POMs? Assuming they'd have their own maven project and you can point to the pom there? Usually, it's the pom sitting in the project's source control repository, which is often visible via a http or https url. Is that an option for your project? Once Continuum retrieves the pom, it uses the (different) url in the element to check out the source code. When the pom has modules, they will get added to the project group as individual projects. I'm not sure at which step that happens, but it does happen. -- Wendy
Maven 2 - POM Hookup Question
Hello, Sorry if this has been asked before, but here goes... When providing Continuum with a Maven POM via URL, what URL? POM's sitting on a local Maven repository? The pom which is located in/on the projects website (i.e. website generated by site goal in maven)? Where is this POM located? Also, how does this work for multi-module POMs? Assuming they'd have their own maven project and you can point to the pom there? If there is an online reference to this subject a pointer to it would be outstanding. Thanks, Randall
Re: towards continuum 1.1 alpha 2
fyi once the maven-scm release is out, I'll be preparing this alpha-2 release.. just wanted to let everyone know jesse On 5/14/07, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: Trygve Laugstøl a écrit : > Jesse McConnell wrote: >> May 21 is fast approaching and that when I want to get the alpha-2 >> release of continuum out. >> >> The advances we have made since alpha-1 are mostly in the area of a >> few more bug fixes, redback integration and shifting off of the >> plexus-security-rbac-profile artifact for role management to the >> different implementation of role management that has an easier api >> into client applications like continuum. > > Will Emmanuel's XML-RPC work be included? Yes, it will be included. - New xml-rpc server included as a servlet so don't need a specific port - New xmlrpc client API that don't need all the Hashtable conversions - A maven continuum plugin. The first version will be to add projects in continuum > >> load up continuum trunk and take a look the following url to see the >> roles and role templates and what operations they grant access to, >> etc. >> >> http://localhost:9090/security/roleModel.action >> >> (you will need to log in and manually visit this url atm) >> >> Also on continuum trunk at the moment is some work from emmanual with >> regard to the xmlrpc bits and pieces of continuum. They are now authn >> an (increasing authz as its implemented) protected. The clients are >> pretty simple and its looking pretty nice. >> >> anyway, that is a little update on things as they stand. > > Thanks for keeping up. > > -- > Trygve > > > -- jesse mcconnell [EMAIL PROTECTED]
RE: User Interface Performance of 1.1
We're using the default db. -Original Message- From: Jesse McConnell [mailto:[EMAIL PROTECTED] Sent: Tuesday, May 22, 2007 12:29 PM To: continuum-users@maven.apache.org Subject: Re: User Interface Performance of 1.1 what kinda database are you using for it? if its the embedded one you'll have to copy the right stuff around, if its postgres or mysql it should just be a matter of pointing it at the db.. jesse On 5/22/07, McNaught, Ewen <[EMAIL PROTECTED]> wrote: > I've been running on continuum-20070502.03.tar > Will I be able to upgrade to the alpha-2 for the performance improvements > without having to re-add my projects? (We have over 70) > --Duncan > > -Original Message- > From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] > Sent: Tuesday, May 22, 2007 12:17 PM > To: continuum-users@maven.apache.org > Subject: Re: User Interface Performance of 1.1 > > Performance are fixed in alpha-2 that will be available in few days. > > Emmanuel > > Shaun Barriball a écrit : > > Are there any known ways to improve the performance of Continuum - as per > > the issue below? > > > >> Issue 2 - Performance > >> -- > >> Out of the box Continuum 1.1 appears much, much slower than 1.0.3. For > >> example, it takes 30 secs+ after I click "MyBigProject" to display the > >> contents of the Project Group which has 10 Projects. > >> > >> Are there any logging settings/go faster buttons that would help > >> improve performance? > > > > > > Regards, > > Shaun. > > > > > > > > > -- jesse mcconnell [EMAIL PROTECTED]
Re: Continuum 1.1 Alpha 1 and SCM : Build fresh option
Christophe Lechenne a écrit : Hi all, Where can I find Build fresh option description ? A build fresh is a build with a clean checkout before the build. You'll find it in the build definition. Another question is how can I configure continuum to make CVS update before building (as deafult in 1.0.3 version) ? You don't have to configure something, it's the default. Emmanuel
Re: Project build order for multiple Maven 2 projects - Alphabetical by Project Name?
It's better to keep modules in continuum for build order resolution. Later, we'll add the possibility to add new dependencies on projects, so modules will can be removed. Emmanuel Shaun Barriball a écrit : Hi Emmanual et al, After a few hours migrating our 15 plus projects to Continuum 1.1 we now have everything up and running. I've been impressed with 1.1 (great work). 2 issues thus far: Issue 1 - Do we delete Project sub-modules? Consider the scenario: Project Group "MyBigProject" Project A pom.xml Module 1 pom.xml Module 2 pom.xml Project B ... Project C * in Continuum 1.0.3 if you had a project of the above format when adding each Maven 2 project you would have to delete "Module 1" and "Module 2" to leave a single "Project A". You then delete the "-no-recurse" option on the Maven build line so it builds the whole project. In Continuum 1.1 it uses the dependencies to determine the build order. Given that the root pom of each projects do not have any of their 'own' dependencies (they just define dependencies used by sub-modules) should we still be deleting "Module 1", "Module 2" etc? Issue 2 - Performance -- Out of the box Continuum 1.1 appears much, much slower than 1.0.3. For example, it takes 30 secs+ after I click "MyBigProject" to display the contents of the Project Group which has 10 Projects. Are there any logging settings/go faster buttons that would help improve performance? Regards, Shaun. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: 21 May 2007 18:00 To: continuum-users@maven.apache.org Subject: Re: Project build order for multiple Maven 2 projects - Alphabetical by Project Name? You must readd all projects Emmanuel Shaun Barriball a écrit : We're just trying the upgrade to 1.1 now from 1.0.3. Is there an upgrade path for this which preserves the database or do we have to re-install all projects from scratch? 1.1 isn't mentioned on http://maven.apache.org/continuum/upgrade.html. Regards, Shaun. -Original Message- From: Jeffery, Mark [mailto:[EMAIL PROTECTED] Sent: 21 May 2007 11:38 To: continuum-users@maven.apache.org Subject: RE: Project build order for multiple Maven 2 projects - Alphabetical by Project Name? Yeah.I am battling with the same thing http://jira.codehaus.org/browse/CONTINUUM-998 Should be fixed in 1.1-alpha-# Jeff -Original Message- From: Shaun Barriball [mailto:[EMAIL PROTECTED] Sent: 21 May 2007 11:41 To: continuum-users@maven.apache.org Subject: Project build order for multiple Maven 2 projects - Alphabetical by Project Name? Hi all, We've been using Continuum (1.0.3) successfully as part of our automated build and deploy for 6 months or so. We have one big issue which I'd appreciate input on. We have a large software system with 15 or so separate Maven 2 projects (assume for simplicity Project A, Project B and Project C) which each have sub-modules. Assume the dependency tree is: A -> depends on C -> depends on B (for example). These dependencies are expressed using Maven 2 dependency hierarchy. The "Build All" function on Continuum appears to ignore any Maven 2 dependency hierarchy and simply builds them in alphabetical order of the Project Name. This therefore builds the above example out of order - often resulting in build failures. * Should continuum 'understand' the dependency tree? I've read some material which implies this should potentially be the case (http://jira.codehaus.org/browse/CONTINUUM-39). * If not, is there a way to organise the build order for "Build All" above and beyond altering the project names with "1.", "2." etc (which is obviously undesirable)? All help appreciated. Regards, Shaun. To read FirstRand Bank's Disclaimer for this email click on the following address or copy into your Internet browser: https://www.fnb.co.za/disclaimer.html If you are unable to access the Disclaimer, send a blank e-mail to [EMAIL PROTECTED] and we will send you a copy of the Disclaimer.
Continuum 1.1 Alpha 1 and SCM : Build fresh option
Hi all, Where can I find Build fresh option description ? Another question is how can I configure continuum to make CVS update before building (as deafult in 1.0.3 version) ? regards, Christophe
Re: Project build order for multiple Maven 2 projects - Alphabetical by Project Name?
On 22/05/07, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: We'll probably do one but not for 1.1-alpha-* Okay cool, we'll wait until then thanks. Mark
Re: Project build order for multiple Maven 2 projects - Alphabetical by Project Name?
We'll probably do one but not for 1.1-alpha-* Emmanuel Mark Hobson a écrit : On 21/05/07, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: You must readd all projects Is there no planned upgrade path from 1.0.3? We have 400+ projects in 1.0.3 and would like to upgrade to 1.1 - obviously this will take a few man years if done manually.. Cheers, Mark
Re: Project build order for multiple Maven 2 projects - Alphabetical by Project Name?
On 21/05/07, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: You must readd all projects Is there no planned upgrade path from 1.0.3? We have 400+ projects in 1.0.3 and would like to upgrade to 1.1 - obviously this will take a few man years if done manually.. Cheers, Mark
RE: Project build order for multiple Maven 2 projects - Alphabetical by Project Name?
Hi Emmanual et al, After a few hours migrating our 15 plus projects to Continuum 1.1 we now have everything up and running. I've been impressed with 1.1 (great work). 2 issues thus far: Issue 1 - Do we delete Project sub-modules? Consider the scenario: Project Group "MyBigProject" Project A pom.xml Module 1 pom.xml Module 2 pom.xml Project B ... Project C * in Continuum 1.0.3 if you had a project of the above format when adding each Maven 2 project you would have to delete "Module 1" and "Module 2" to leave a single "Project A". You then delete the "-no-recurse" option on the Maven build line so it builds the whole project. In Continuum 1.1 it uses the dependencies to determine the build order. Given that the root pom of each projects do not have any of their 'own' dependencies (they just define dependencies used by sub-modules) should we still be deleting "Module 1", "Module 2" etc? Issue 2 - Performance -- Out of the box Continuum 1.1 appears much, much slower than 1.0.3. For example, it takes 30 secs+ after I click "MyBigProject" to display the contents of the Project Group which has 10 Projects. Are there any logging settings/go faster buttons that would help improve performance? Regards, Shaun. -Original Message- From: Emmanuel Venisse [mailto:[EMAIL PROTECTED] Sent: 21 May 2007 18:00 To: continuum-users@maven.apache.org Subject: Re: Project build order for multiple Maven 2 projects - Alphabetical by Project Name? You must readd all projects Emmanuel Shaun Barriball a écrit : > We're just trying the upgrade to 1.1 now from 1.0.3. > Is there an upgrade path for this which preserves the database or do > we have to re-install all projects from scratch? 1.1 isn't mentioned > on http://maven.apache.org/continuum/upgrade.html. > > Regards, > Shaun. > > -Original Message- > From: Jeffery, Mark [mailto:[EMAIL PROTECTED] > Sent: 21 May 2007 11:38 > To: continuum-users@maven.apache.org > Subject: RE: Project build order for multiple Maven 2 projects - > Alphabetical by Project Name? > > Yeah.I am battling with the same thing > > http://jira.codehaus.org/browse/CONTINUUM-998 > > > Should be fixed in 1.1-alpha-# > > Jeff > > -Original Message- > From: Shaun Barriball [mailto:[EMAIL PROTECTED] > Sent: 21 May 2007 11:41 > To: continuum-users@maven.apache.org > Subject: Project build order for multiple Maven 2 projects - > Alphabetical by Project Name? > > Hi all, > We've been using Continuum (1.0.3) successfully as part of our > automated build and deploy for 6 months or so. > We have one big issue which I'd appreciate input on. > > We have a large software system with 15 or so separate Maven 2 > projects (assume for simplicity Project A, Project B and Project C) > which each have sub-modules. Assume the dependency tree is: > A -> depends on C -> depends on B (for example). These dependencies > are expressed using Maven 2 dependency hierarchy. > > The "Build All" function on Continuum appears to ignore any Maven 2 > dependency hierarchy and simply builds them in alphabetical order of > the Project Name. This therefore builds the above example out of order > - often resulting in build failures. > > * Should continuum 'understand' the dependency tree? I've read some > material which implies this should potentially be the case > (http://jira.codehaus.org/browse/CONTINUUM-39). > > * If not, is there a way to organise the build order for "Build All" > above > and beyond altering the project names with "1.", "2." etc (which is > obviously undesirable)? > > > All help appreciated. > Regards, > Shaun. > > > To read FirstRand Bank's Disclaimer for this email click on the > following address or copy into your Internet browser: > https://www.fnb.co.za/disclaimer.html > > If you are unable to access the Disclaimer, send a blank e-mail to > [EMAIL PROTECTED] and we will send you a copy of the > Disclaimer. > > > >
