adding video capture to the continuum site
Hi, I'd like to add some wink captures to the site (as adding a project for newbies etc...) As this files can be huge, I don't really want to add this in sources trunk (It can be long to checkout the sources) But in order to publish them, they must be in a site module. That's why I'd like to remove the site module from this current path and move it to https://svn.apache.org/repos/asf/maven/continuum/. svn mv https://svn.apache.org/repos/asf/maven/continuum/trunk/continuum-site/ https://svn.apache.org/repos/asf/maven/continuum . The parent pom of this module will be last org.apache.maven:maven-parent pom. An other question is what I have to add in svn : wnk and swf files or only swf ? Let me know if there is any objections concerning this, -- Olivier
Re: adding video capture to the continuum site
Yes displaying the page containing this swf could be long. But in the link to these pages we can indicate this. For not storing this files in svn but in an other place, it looks possible to deploy it manually to people.apache.org /www/maven.apache.org/continuum. But I'm not sure it's a good solution to have an automatic process to deploying site with mvn and an other manual to deploy this files. -- Olivier 2007/9/19, Rahul Thakur <[EMAIL PROTECTED]>: > > How will this affect users on dial-up/slow connections browsing those > pages on the continuum site? > > Is it possible to have these swf (or wnk) resources live outside SVN and > be included from an external URL? > > Rahul > > - Original Message - > From: "olivier lamy" <[EMAIL PROTECTED]> > To: > Sent: Wednesday, September 19, 2007 6:42 PM > Subject: adding video capture to the continuum site > > > > Hi, > > I'd like to add some wink captures to the site (as adding a project > > for > > newbies etc...) > > As this files can be huge, I don't really want to add this in sources > > trunk > > (It can be long to checkout the sources) > > But in order to publish them, they must be in a site module. > > That's why I'd like to remove the site module from this current path > > and > > move it to https://svn.apache.org/repos/asf/maven/continuum/. > > svn mv > > https://svn.apache.org/repos/asf/maven/continuum/trunk/continuum-site/ > > https://svn.apache.org/repos/asf/maven/continuum . > > > > The parent pom of this module will be last > > org.apache.maven:maven-parent > > pom. > > > > An other question is what I have to add in svn : wnk and swf files or > > only > > swf ? > > > > Let me know if there is any objections concerning this, > > > > -- > > Olivier > > > > -- Olivier
Re: [vote] Release Continuum 1.1-beta-3
+1 -- Olivier 2007/9/19, Emmanuel Venisse <[EMAIL PROTECTED]>: > > Hi, > > Continuum 1.1-beta-3 is ready for release > > The highlights are > - lot of bug fixes > - LDAP support for authentication (thanks jesse) > - performance improvement > - committer mail notification > > The Release Notes is available there: > http://jira.codehaus.org/secure/ReleaseNote.jspa?projectId=10540&styleName=Html&version=13661 > > The binaries are available there: > - Runtime: > http://people.apache.org/builds/maven/continuum/1.1-beta-3/org/apache/maven/continuum/continuum-plexus-runtime/1.1-beta-3/continuum-plexus-runtime-1.1-beta-3-bin.tar.gz > - Webapp: > http://people.apache.org/builds/maven/continuum/1.1-beta-3/org/apache/maven/continuum/continuum-webapp/1.1-beta-3/continuum-webapp-1.1-beta-3.war > - data management cli: > http://people.apache.org/builds/maven/continuum/1.1-beta-3/org/apache/maven/continuum/data-management-cli/1.1-beta-3/data-management-cli-1.1-beta-3-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 > > > > > >
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: "build definition used" on build result
Hi, * Yes it's stored in the database with the buildResult (like a clone and add of the buildDefinition). * Yes it is in the email. * It looks we have to store the buildDefinition even if the scm update/checkout failed -- Olivier 2007/9/23, Brett Porter <[EMAIL PROTECTED]>: > > A couple of questions/issues on this new feature: > > * is this stored with the build result, or is it referring to what is > in the database now? (ie, what happens to the result if the build > definition is later removed?) > * is it in the email template? (haven't looked yet) > * issue: it shows up on builds that are in error as empty: http:// > maven.zones.apache.org/continuum/buildResult.action? > buildId=23999&projectId=272&projectGroupId=8 > > Cheers, > Brett > > -- > Brett Porter - [EMAIL PROTECTED] > Blog: http://www.devzuz.org/blogs/bporter/ > > -- Olivier
Re: adding video capture to the continuum site
Hi, I have made two samples : - starting continuum and add a project http://people.apache.org/~olamy/continuum/flash/start-continuum.htm - using the build definition template new feature http://people.apache.org/~olamy/continuum/flash/build-definition-template.htm It's two flash files. Too see the size : http://people.apache.org/~olamy/continuum/flash Note : we can reduce the size (I have used my default screen resolution 1280x800). -- Olivier 2007/9/21, Emmanuel Venisse <[EMAIL PROTECTED]>: > > > > Wendy Smoak a écrit : > > On 9/18/07, olivier lamy <[EMAIL PROTECTED]> wrote: > > > >> I'd like to add some wink captures to the site (as adding a project for > >> newbies etc...) > > > > Great idea. :) > > yes. > with or without voice? > > > > >> As this files can be huge, I don't really want to add this in sources > trunk > >> (It can be long to checkout the sources) > >> But in order to publish them, they must be in a site module. > > > > Not necessarily... they can be hosted anywhere that can handle the > > bandwidth, and linked to. Is YouTube an appropriate option? (Or can > > you convert to a format that can be hosted there or somewhere > > similar?) > > yes, it's an appropriate option. I don't think YouTube remove files after > few days/months > > > > >> That's why I'd like to remove the site module from this current path > and > >> move it to https://svn.apache.org/repos/asf/maven/continuum/. > >> svn mv > >> https://svn.apache.org/repos/asf/maven/continuum/trunk/continuum-site/ > >> https://svn.apache.org/repos/asf/maven/continuum . > > > > I'm not in favor of moving the site somewhere it doesn't get checked > > out with the project. But I also don't think the ASF Subversion repo > > is the right place for "documentation" video files. (It would be > > different if they were *part* of the product itself.) > > If we put video files in svn, it will be only wink files but I'm not sure > if it's the right place. > I'm not sure we have a quota in svn but wink files will use lot of places. > > How many files do you want to do? How many minutes? > > > > > Are any other projects offering video examples? How do they handle it? > > I don't know one at ASF. > > Emmanuel > > -- Olivier
Re: how to install continuum betat 2 into tomcat?
Please use user mailing list for user questions. http://docs.codehaus.org/display/CONTINUUMUSER/Continuum+on+Tomcat 2007/9/25, I am Who i am <[EMAIL PROTECTED]>: > > Is there any doc available for this? > -- Olivier
Re: how to install continuum betat 2 into tomcat?
You need datasources. That's why you have to configure them in a context file. -- Olivier 2007/9/26, I am Who i am <[EMAIL PROTECTED]>: > > can i just install the war file as any other war file to tomcat, or i > still > need to do that configuration shown on the wiki page ? > > Please advise > Thanks > > On 9/26/07, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: > > > > On the continuum site ;) > > > > Emmanuel > > > > I am Who i am a écrit : > > > where is beta-3 ? > > > > > > On 9/25/07, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: > > >> It would be better to use 1.1-beta-3 if you don't want to migrate > your > > db > > >> between versions. I released it and I'll do the official announce in > > few > > >> hours when all files will be mirrored. > > >> > > >> but the continuum doc for tomcat is available there: > > >> http://docs.codehaus.org/display/CONTINUUMUSER/Continuum+on+Tomcat > > >> > > >> Emmanuel > > >> > > >> > > >> I am Who i am a écrit : > > >>> Is there any doc available for this? > > >>> > > >> > > > > > > > >
Re: CONTINUUM-310 - customizable email templates
Hi,
File in ${user.home} can cause trouble if you have two continuum instances
started with the same user/id and if you need different configurations
between instances.
But we can think about something which merge between $CONTINUUM_HOME/conf
and ${user.home) (I think plexus-registry can do this because it use
commons-configuration) with configuration in $CONTINUUM_HOME/conf wins.
--
Olivier
2007/10/2, Emmanuel Venisse <[EMAIL PROTECTED]>:
>
>
>
> Wendy Smoak a écrit :
> > On 10/2/07, Emmanuel Venisse <[EMAIL PROTECTED]> wrote:
> >> We can't move all in the db because schema updates can be a pain.
> >> In 1.2 all the conf, actually written in application.xml, will be move
> to an external file. This file will can be stored in ${user.home} so each
> installs will can use it like it is done in
> >> archiva-configuration.
> >
> > ... or $CONTINUUM_HOME/conf, I assume?
>
> of course :)
>
> >
> > Rahul, not sure if that was meant for me, but I'm not in favor of
> > putting either the configuration or the email templates in the
> > database. Plain text rules. :)
> >
> > Assuming they are loaded from the classpath, then the
> > path/package/filename goes in continuum.xml, and the files themselves
> > go somewhere that they end up on the classpath.
> >
>
>
--
Olivier
Re: CONTINUUM-310 - customizable email templates
Are you using plexus-runtime or tomcat ?
If it works with tomcat (adding the template in
WEB-INF/classes/${templatepath}).
It looks a classLoader issue with plexus-jetty because WEB-INF/classes must
wins against WEB-INF/lib.
--
Olivier
2007/10/2, Tomislav Stojcevich <[EMAIL PROTECTED]>:
>
> >
> > Can you write up a page on the wiki explaining where things are and
> > how to do this?
> >
> > http://docs.codehaus.org/display/CONTINUUMUSER/Home
> >
> I would if it actually worked. I just tried putting the templates in
> the WEB-INF/classes (using the same fully qualified path that they
> have in the core.jar) and made some changes. My modified ones in
> WEB-INF/classes are not getting picked up.
>
> --
> tom
>
--
Olivier
Re: Documentation Plan
Agree to remove old content. The home need some work : adding the download link, google search box as in maven home and some more words on the project. -- Olivier 2007/10/5, Emmanuel Venisse < [EMAIL PROTECTED]>: > > What do you think if I remove "Old versions" from the menu? We don't have > a 1.0.x doc so we don't need it and I don't know what toput in this part. > It can be used with next versions > > Emmanuel > > Emmanuel Venisse a écrit : > > I created a branch for the new site > > (http://svn.apache.org/repos/asf/maven/continuum/branches/continuum-site_1.1/ > ) > > and I added the structure and some content. > > > > Please, review and comment before I (and all other that want to help) > > start to write the doc. > > > > Emmanuel > > > > Emmanuel Venisse a écrit : > >> Hi, > >> > >> Here is the structure of the documentation I'd like to have for > >> 1.1-final . > >> > >> > >> Installation/Upgrade Guides > >> Installation (standalone, webapp, service...) > >> Release Notes > >> Upgrade > >> Administrator's Guides > >> Managing Users and Security > >> Adding Project Group > >> Managing Builders > >> Managing JDKs > >> Managing Profiles > >> Managing Schedules > >> Managing General Configuration (configuration and appearance) > >> Developer's Guides > >> SVN repository structure > >> XML-RPC > >> TO BE DEFINED > >> User's Guides > >> Managing a project > >> Add (maven1, maven2, Ant, Shell), Remove, Edit > >> SCM security hints > >> Managing Build Definitions > >> Managing Notification > >> mail to an address, mail to latest committers, irc, > >> jabber, msn, wagon, alwaysSend... > >> Building a project > >> Release Management > >> Knowledge Base > >> FAQ (sorted by categories, maybe one menu entry by category) > >> Old versions > >> 1.0.x site > >> > >> > >> About videos, I don't know yet where to put them. Maybe a video > >> attached to a page (like Add Maven2 project) instead of a specific > >> videos page in the menu. > >> > >> WDYT? > >> > >> Emmanuel > >> > >> > >> > > > > > > > > -- Olivier
Re: Improvement
Hi, I think there are some related/similar issues to this (CONTINUUM-703, CONTINUUM-1332). And fixing this is not really complicated. Others : agree to move this issues to 1.1-beta-4 ? (I can work on this this week) -- Olivier 2007/10/15, Christophe Lechenne <[EMAIL PROTECTED]>: > > Hi, > > When we look project list in a group, we can see in tab, one column > "Group" > which seems useless, it could be better to print the date of last built > for > this project instead, wdyt ? > > Regards, > Christophe >
Re: next release
Hi, A version like 1.1-rc1 is not possible ? I will try to work on adding others pages. -- Olivier 2007/10/17, Emmanuel Venisse <[EMAIL PROTECTED]>: > > Hi, > > In jira, we have now 3 issues opened, I don't think I'll can fix > CONTINUUM-1388 before the release because it require changes and releases of > remote-resources-plugin, apache-jar-resource-bundle and > maven parent pom. > > I'm not sure to fix CONTINUUM-1475 too. > > About the docs, we have already few pages done, I'll can work on others in > next days. > > What do you think about the version to use for the continuum release? We > have two choices: 1.1-beta-4 or 1.1 final. > Personnally, I'd prefer 1.1 final. I tested all parts and all seems to be > ok, I just need to test more the ANT/shell part. > > I'd like to prepare the Continuum release next week. > > Emmanuel > >
Re: continuum-site branch
+1 -- Olivier 2007/10/23, Emmanuel Venisse <[EMAIL PROTECTED]>: > > Hi, > > I'd like to merge continuum-site_1.1 branch in trunk tomorrow (before to > start the release process of 1.1-beta-4) > > Are you ok? > > Emmanuel > >
Re: [vote] Release Continuum 1.1-beta-4
+1 -- Olivier 2007/10/25, Emmanuel Venisse <[EMAIL PROTECTED]>: > Hi, > > Continuum 1.1-beta-4 is ready for release > > The highlights are > - lot of bug fixes > - A new page to view the build queue > - Customization of mail subject > > The Release Notes is available there: > http://jira.codehaus.org/secure/IssueNavigator.jspa?reset=true&pid=10540&fixfor=13727 > > The binaries are available there: > - Runtime: > http://people.apache.org/builds/maven/continuum/1.1-beta-4/org/apache/maven/continuum/continuum-plexus-runtime/1.1-beta-4/continuum-plexus-runtime-1.1-beta-4-bin.tar.gz > - Webapp: > http://people.apache.org/builds/maven/continuum/1.1-beta-4/org/apache/maven/continuum/continuum-webapp/1.1-beta-4/continuum-webapp-1.1-beta-4.war > - data management cli: > http://people.apache.org/builds/maven/continuum/1.1-beta-4/org/apache/maven/continuum/data-management-cli/1.1-beta-4/data-management-cli-1.1-beta-4-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 > >
Re: [vote] Release Continuum 1.1-beta-4
Hi, It's duplicate with CONTINUUM-1492. Can you detailled what kind of proxy you use ? (NTLM authentification ?). Because as I have explained in CONTINUUM-1492, I have tested this successfully with adding -Dhttp.proxyHost=proxyhost.com, -Dhttp.proxyPort=80 (but with auth in the proxy) in the cli. Have you try this [1]? -- Olivier [1] http://java.sun.com/j2se/1.5.0/docs/guide/net/properties.html 2007/10/25, Damien Lecan <[EMAIL PROTECTED]>: > 2007/10/25, Emmanuel Venisse <[EMAIL PROTECTED]>: > > Hmm, file an issue and I'll try to fix it (but I don't have a proxy to do a > > real test) > > http://jira.codehaus.org/browse/CONTINUUM-1536 > > Damien > -- Olivier
Fwd: [continuum build trunk - SKIPPED - checkout] Thu Nov 8 01:00:01 GMT 2007
Hi, Is it possible someone with karma maven.zones kill processes ? Thanks, -- Olivier -- Forwarded message -- From: [EMAIL PROTECTED] <[EMAIL PROTECTED]> Date: 8 nov. 2007 02:00 Subject: [continuum build trunk - SKIPPED - checkout] Thu Nov 8 01:00:01 GMT 2007 To: [EMAIL PROTECTED] ci_continuum.sh already running... exiting continuu 24880 24200 0 Oct 24 ? 0:00 /bin/sh /export/home/continuum/ci_continuum.sh checkout continuu 24200 24169 0 Oct 24 ? 0:00 /bin/sh /export/home/continuum/ci_continuum.sh checkout continuu 24169 24167 0 Oct 24 ? 0:00 /bin/sh /export/home/continuum/ci_continuum.sh checkout
Re: [vote] Release Continuum 1.1 Final
+1
--
Olivier
2007/11/19, Emmanuel Venisse <[EMAIL PROTECTED]>:
>
> I fixed it.
>
> About the doc, I'll work on it this week and it will be deploywhen the
> vote will be ok.
>
> Emmanuel
>
> Emmanuel Venisse a écrit :
> > I'll fix it today and will resend a message when you'll can retest.
> >
> > Emmanuel
> >
> > Stuart James Penrose a écrit :
> >> Emmanuel Venisse wrote:
> >>>
> >>> The binaries are available there: ...
> >>>
> 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
> >>>
> >> The data management tool looks like it needs some 'assembly' work
> >> ('java -jar data-management-cli-1.1-app.jar' doesn't work):
> >> 1) If you list the root of the jar you see a list of *.jar entries,
> >> not root package names
> >> 2) It appears that the main class is missing (DataManagementCli)
> >>
> >>> - 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.
> >>>
> >> How does the xml backup tool relate to the cli tool & the recommended
> >> backup/restore/upgrade strategy in general? Should the upgrade page
> >> make mention of this new tool
> >> (
> http://maven.apache.org/continuum/documentation/1_1/installation/upgrade.html
> )?
> >>
> >>
> >>> Everyone is encouraged to vote and give their feedback.
> >>>
> >>> [ ] +1 Release it!
> >>> [ ] 0
> >>> [ ] -1 Don't release it, because...
> >> -1 Don't release it, because the data management tool is broken and as
> >> a result it's not clear how to upgrade 1.1-betaX installs to 1.1 final.
> >>
> >> Stu Penrose
> >>
> >>
> >
> >
> >
>
>
Re: Continuum and "Build Profiles"
Hi, No objection from me. -- Olivier 2007/12/14, Wendy Smoak <[EMAIL PROTECTED]>: > > I'm having trouble communicating about profiles in Continuum. > > The problem is that Maven already has something called "Build > Profiles". See: > http://maven.apache.org/guides/introduction/introduction-to-profiles.html > > And now Continuum has a page titled "Build Profiles" that is not at > all the same thing: > http://example.com/continuum/admin/profilesList!list.action > > We need to call ours something else. So far I've been calling them > "Continuum Profiles" instead. > > Other suggestions? Any objection to changing the heading on that page? > > Thanks, > -- > Wendy >
Re: Stack Overflow in Continuum XMLRPC server
Hi,
Can you load an issue in jira ?
And if you have a patch it will be helpfull.
Thanks,
--
Olivier
2007/12/22, Laurent Forêt <[EMAIL PROTECTED]>:
> Maybe, it is not usefull at line 231 in the private method to call
> checkViewProjectGroupAuthorization()
>
> Laurent.
>
> On Dec 22, 2007 7:20 PM, Laurent Forêt <[EMAIL PROTECTED]> wrote:
>
> > Today I had exactly the same trouble with a freshly installed continuum
> > 1.1 server.
> >
> > The simple client code is :
> >
> > public static void main( String[] args )
> > {
> > try {
> > ContinuumXmlRpcClient client = new ContinuumXmlRpcClient(new
> > URL(" http://localhost:8080/continuum/xmlrpc";), "admin", "manager1");
> > List projectGroups =
> > client.getAllProjectGroupsWithAllDetails ();
> > for (ProjectGroup pg : projectGroups) {
> > System.out.println("PGID : "+pg.getId());
> > client.getProjects(pg.getId());
> > }
> >
> > } catch (Exception ex) {
> > ex.printStackTrace();
> > }
> > }
> >
> > Client Output is :
> >
> > PGID : 1
> > org.apache.xmlrpc.XmlRpcException: Failed to invoke method getProjects in
> > class org.apache.maven.continuum.xmlrpc.server.ContinuumServiceImpl : null
> > at org.apache.xmlrpc.client.XmlRpcStreamTransport.readResponse(
> > XmlRpcStreamTransport.java:184)
> > at org.apache.xmlrpc.client.XmlRpcStreamTransport.sendRequest(
> > XmlRpcStreamTransport.java:145)
> > at org.apache.xmlrpc.client.XmlRpcHttpTransport.sendRequest(
> > XmlRpcHttpTransport.java:94)
> > at org.apache.xmlrpc.client.XmlRpcSunHttpTransport.sendRequest(
> > XmlRpcSunHttpTransport.java:39)
> > at org.apache.xmlrpc.client.XmlRpcClientWorker.execute (
> > XmlRpcClientWorker.java:53)
> > at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java
> > :166)
> > at org.apache.xmlrpc.client.XmlRpcClient.execute(XmlRpcClient.java
> > :136)
> > at org.apache.xmlrpc.client.XmlRpcClient.execute (
> > XmlRpcClient.java:125)
> > at org.apache.xmlrpc.client.util.ClientFactory$1.invoke(
> > ClientFactory.java:104)
> > at $Proxy33.getProjects(Unknown Source)
> > at
> > org.apache.maven.continuum.xmlrpc.client.ContinuumXmlRpcClient.getProjects(
> > ContinuumXmlRpcClient.java:112)
> > at org.laurentforet.continuum11.client.App.main(App.java:22)
> > at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
> > at sun.reflect.NativeMethodAccessorImpl.invoke (
> > NativeMethodAccessorImpl.java:39)
> > at sun.reflect.DelegatingMethodAccessorImpl.invoke(
> > DelegatingMethodAccessorImpl.java:25)
> > at java.lang.reflect.Method.invoke(Method.java:585)
> > at org.codehaus.mojo.exec.ExecJavaMojo$1.run (ExecJavaMojo.java
> > :271)
> > at java.lang.Thread.run(Thread.java:595)
> >
> >
> >
> > The server output is :
> >
> >
> > jvm 1| 2007-12-22 19:15:03,421 [SocketListener0-1] ERROR
> > org.apache.xmlrpc.server.XmlRpcStreamServer - execute: Err
> > or while performing request
> > jvm 1| org.apache.xmlrpc.XmlRpcException: Failed to invoke method
> > getProjects in class org.apache.maven.continuum.xm
> > lrpc.server.ContinuumServiceImpl: null
> > jvm 1| at
> > org.apache.maven.continuum.xmlrpc.server.ContinuumXmlRpcMetaDataHandler.invoke
> > (ContinuumXmlRpcMetaDat
> > aHandler.java:164)
> > jvm 1| at
> > org.apache.maven.continuum.xmlrpc.server.ContinuumXmlRpcMetaDataHandler.execute(ContinuumXmlRpcMetaDa
> > taHandler.java:133)
> > jvm 1| at org.apache.xmlrpc.server.XmlRpcServerWorker.execute(
> > XmlRpcServerWorker.java:43)
> > jvm 1| at org.apache.xmlrpc.server.XmlRpcServer.execute(
> > XmlRpcServer.java :83)
> > jvm 1| at org.apache.xmlrpc.server.XmlRpcStreamServer.execute(
> > XmlRpcStreamServer.java:182)
> > jvm 1| at org.apache.xmlrpc.webserver.XmlRpcServletServer.execute
> > (XmlRpcServletServer.java:103)
> > jvm 1| at
> > org.apache.maven.continuum.xmlrpc.server.ContinuumXmlRpcServlet.doPost(
> > ContinuumXmlRpcServlet.java:19
> > 3)
> > jvm 1| at javax.servlet.http.HttpServlet.service(HttpServlet.java
> > :709)
> > jvm 1| at javax.servlet.http.HttpServlet.service (
> > HttpServlet.java:802)
> > jvm 1| at org.mortbay.jetty.servlet.ServletHolder.handle(
> > ServletHolder.java:428)
> > jvm 1| at
> > org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(
> > WebApplicationHandler.java :830)
> > jvm 1| at
> > com.opensymphony.webwork.dispatcher.FilterDispatcher.doFilter(
> > FilterDispatcher.java:189)
> > jvm 1| at
> > org.mortbay.jetty.servlet.WebApplicationHandler$CachedChain.doFilter(
> > WebApplicationHandler.java :821)
> > jvm 1| at
> > com.opensymphony.module.sitemesh.filter.PageFilter.parsePage(
> > PageFilter.java:118)
> > jvm 1| at
> > com.op
Re: Splitting the website and documentation
2007/12/29, Wendy Smoak <[EMAIL PROTECTED]>: > On Dec 28, 2007 7:51 PM, Brett Porter <[EMAIL PROTECTED]> wrote: > > > > On 29/12/2007, at 1:35 PM, Wendy Smoak wrote: > > > I was just going to leave it under continuum/trunk as continuum-docs > > > and continuum-site. > > > > Cool, thanks for that. Should be pretty straightforward to move the > > site up at a later date if needed. > > This is done. The versioned docs are in continuum-docs, publishing to > /continuum/docs/$version. > > I moved the 1.1 docs to http://maven.apache.org/continuum/docs/1.1 and > added a redirect (from /continuum/documentation/1_1) to the .htaccess > file. > > This does leave us without a way to edit and re-publish the existing > 1.1 docs, since this new module "belongs" to 1.2-SNAPSHOT. > > I don't want to branch all of Continuum unless we're doing a 1.1.1 > release, but we could branch just the continuum-docs module. > Thoughts? Why not a 1.1.1 bug fix release? We can walk on jira issues and move some to 1.1.1 Others ? > > -- > Wendy > -- Olivier
Re: Continuum update
Hi, +1 We could release a 1.2 bug fixes because currently they are some blocking issues. -- Olivier 2008/1/21, Emmanuel Venisse <[EMAIL PROTECTED]>: > Hi, > > I'll probably create a new branch for 1.x dev and will reserve the trunk for > 2.x dev. I think I'll do it this week or the next (if you're agree, of > course :) ) > > I'll try to send at the same time my ideas for 2.x so we'll can discuss > about them. > > Emmanuel >
Re: Some work on docs
Hi, There are here http://people.apache.org/~olamy/continuum/flash/ . I used http://www.debugmode.com/wink/ to build this. Sorry I can't use Snapz Pro X on my laptop :-) . -- Olivier 2008/2/3, Wendy Smoak <[EMAIL PROTECTED]>: > I did some work on the Release Management docs today. I'm doing this > in a timeboxed fashion, and when the time is up, it gets committed. > Otherwise it will sit here on my hard drive and never get finished. :) > > Today I spent most of my time capturing screen shots, so there's not > much text. I'm not especially attached to any of it, so if you want > to delete, rearrange, or add to it, feel free! > > http://maven.apache.org/continuum/docs/1.2-SNAPSHOT/user_guides/release/index.html > > Olivier, what ever happened to the video captures you did? I was > playing with that too today, using Snapz Pro X. > > -- > Wendy >
Re: [vote] Request Graduation to a TLP
+1 -- Olivier 2008/2/6, Emmanuel Venisse <[EMAIL PROTECTED]>: > Hi, > > Below is the current proposal for the Continuum TLP. > Please vote on whether to make this proposal a formal request to the Maven > PMC to apply for graduation. > > [ ] +1 > [ ] 0 > [ ] -1 > > Cheers, > Emmanuel > > > Establish the Apache Continuum Project > > WHEREAS, the Board of Directors deems it to be in the best > interests of the Foundation and consistent with the Foundation's > purpose to establish a Project Management Committee charged with > the creation and maintenance of open-source software related to > the domain of continuous integration. > > NOW, THEREFORE, BE IT RESOLVED, that a Project Management > Committee (PMC), to be known as the "Apache Continuum PMC", be and > hereby is established pursuant to Bylaws of the Foundation; and > be it further > > RESOLVED, that the Apache Continuum PMC be and hereby is > responsible for the creation and maintenance of software related > to the domain of continuous integration based on software licensed > to the Foundation; and be it further > > RESOLVED, that the office of "Vice President, Apache Continuum" be > and hereby is created, the person holding such office to serve > at the direction of the Board of Directors as the chair of the > Apache Continuum PMC, and to have primary responsibility for > management of the projects within the scope of responsibility of > the Apache Continuum PMC; and be it further > > RESOLVED, that the persons listed immediately below be and > hereby are appointed to serve as the initial members of the > Apache Continuum PMC: > > - Maria Odea Ching ([EMAIL PROTECTED]) > - Joakim Erdfelt ([EMAIL PROTECTED]) > - Olivier Lamy ([EMAIL PROTECTED]) > - Trygve Laugstol ([EMAIL PROTECTED]) > - Jesse McConnell ([EMAIL PROTECTED]) > - Brett Porter ([EMAIL PROTECTED]) > - Edwin Punzalan ([EMAIL PROTECTED]) > - Carlos Sanchez ([EMAIL PROTECTED]) > - Wendy Smoak ([EMAIL PROTECTED]) > - Rahul Thakur ([EMAIL PROTECTED]) > - Emmanuel Venisse ([EMAIL PROTECTED]) > - Kenney Westerhof ([EMAIL PROTECTED]) > - Andrew Williams ([EMAIL PROTECTED]) > > > NOW, THEREFORE, BE IT FURTHER RESOLVED, that Emmanuel Venisse be > appointed to the office of Vice President, Apache Continuum, to > serve in accordance with and subject to the direction of the > Board of Directors and the Bylaws of the Foundation until death, > resignation, retirement, removal or disqualification, or until a > successor is appointed; and be it further > > RESOLVED, that the initial Apache Continuum PMC be and hereby is > tasked with the creation of a set of bylaws intended to > encourage open development and increased participation in the > Apache Continuum Project; and be it further > > RESOLVED, that the initial Apache Continuum PMC be and hereby is > tasked with the migration and rationalization of the Apache > Maven PMC Continuum subproject; and be it further > > RESOLVED, that all responsibility pertaining to the Maven Continuum > sub-project and encumbered upon the Apache Maven PMC > are hereafter discharged. >
Re: [Discussion] Continuum 2.0 Roadmap
Hi, This looks very exciting (I love the plugin idea). As all of this features can be long to implement, I agree with Brett to separate into different millestones releases. (IMHO a full "big bang" will be very long). And currently they are some blocking issues in the 1.1 release. -- Olivier 2008/1/29, Emmanuel Venisse <[EMAIL PROTECTED]>: > Hi > > I started a document [1] with my ideas about Continuum 2. > As you can see in this doc, I want to add lot of things in the next version. > > Feel free to comment on it. > > > [1] > http://docs.codehaus.org/display/CONTINUUM/Continuum+2.0+Design+Discussion > > Emmanuel >
Re: Apache Continuum is now an Apache top level project
Wonderful ! -- Olivier 2008/2/20, Brett Porter <[EMAIL PROTECTED]>: > Hi all, > > Congratulations - the board passed the resolution we submitted. > > We'll have some work to do to get set up over the next month, but > other than that it's business as usual. Certainly shouldn't interrupt > the planning for the next release :) > > Cheers, > Brett > > > -- > Brett Porter > [EMAIL PROTECTED] > http://blogs.exist.com/bporter/ > >
Re: svn move (was: Re: Apache Continuum is now an Apache top level project)
Hi, What about the sandbox content ? [1] Not sure it's well maintained code ;-). -- Olivier [1] : https://svn.apache.org/repos/asf/maven/sandbox/trunk/continuum/ 2008/2/28, Brett Porter <[EMAIL PROTECTED]>: > This has been done (and switch works just fine). No other changes > should be needed on your end. > > > - Brett > > > On 26/02/2008, at 12:02 PM, Wendy Smoak wrote: > > > On Mon, Feb 25, 2008 at 4:39 PM, Emmanuel Venisse > > <[EMAIL PROTECTED]> wrote: > >> I created the svn group with all pmc members. The next step will be > >> the svn > >> move to the new location. > >> > >> I'd like to see the move done for the end of the week, so if you > >> have some > >> changes to commit, you must do it asap. > > > > If you have local changes you don't want to commit, I think 'svn > > switch' will work afterwards to point an existing working copy at a > > new url. > > > > -- > > Wendy > > > -- > Brett Porter > [EMAIL PROTECTED] > http://blogs.exist.com/bporter/ > >
Continuum fisheye hosting
Hi, As continuum has moved in the apache svn. The project is no longer available here http://fisheye6.cenqua.com. I have created an issue [1] to ask the hosting. Is there any objections before notifying/asking infra ? Thanks, -- Olivier [1] https://support.atlassian.com/browse/FSH-580
Re: Confused about the branches
Agree on this. Currently there is a blocking issue with xml-rpc CONTINUUM-1590 which prevent using xml-rpc :-(. If no objections, I will change root pom to not have anymore maven pom as parent. -- Olivier 2008/3/4, Brett Porter <[EMAIL PROTECTED]>: > > On 29/02/2008, at 10:04 AM, Emmanuel Venisse wrote: > > > On Thu, Feb 28, 2008 at 11:55 PM, Brett Porter <[EMAIL PROTECTED]> > > wrote: > > > >> > >> On 29/02/2008, at 9:52 AM, Emmanuel Venisse wrote: > >> > >>> why 1.1.x? > >> > >> in case there was a bugfix release on 1.1? I thought that was what > >> the > >> branch was for... maintenance of 1.1. > >> > >> or is there going to be 2 completely different strands of > >> development? > > > > > > I thought to do 1.x in the branch instead of only maintenance in > > 1.1.xbecause I don't know how many time we'll need for the first > > 2.0 release. User will probably need some new small feature before the > > 2.0release and not only maintenance. > > With the roadmap discussion recently, I thought it was going to be an > incremental move towards 2.0 on trunk - 1.2 will have some parts and > refactorings, 1.3, 1.4 and so on. I'm not sure why there would need to > be two streams of development? I think there's a real danger of > getting lost in the 2.0 trap (c.f. Maven 1.0, Maven 2.0 and Maven 2.1 :) > > I'm actually keen to do a couple of small things myself and get a > release out: > - a few small bug fixes, like the lost change sets for some builds > - better error handling > - switch to a Jetty runtime without the plexus appserver so we can use > jetty 6 > - add a call to svn info --xml to check whether to do an svn update to > speed up working copy updates > > Just stuff I see from running vmbuild and the maven zone. > > I think that and a couple of other refactorings that are being > discussed on here would make a good 1.2 in the next couple of months. > WDYT? > > - Brett > > > -- > Brett Porter > [EMAIL PROTECTED] > http://blogs.exist.com/bporter/ > >
Re: Confused about the branches
2008/3/4, Brett Porter <[EMAIL PROTECTED]>: > > On 04/03/2008, at 10:47 AM, Olivier Lamy wrote: > > > Agree on this. > > Currently there is a blocking issue with xml-rpc CONTINUUM-1590 which > > prevent using xml-rpc :-(. > > > Cool - shall we just start using the 1.2 bucket in JIRA? There are > only 14 issues there now so maybe we could keep that to 20-30 issues > all together and release it. +1 > > I found these changes on trunk that are not on the branch: r617400. > (The rest is documentation) > > I found these changes on the branch that are not on trunk: r627196, > r620613, r620612, r620611 > > I think we should just merge all those from the branch to trunk, set > it as v1.2, and close the branch for now? +1. (Perso, I don't really like the idea of starting a parrallel branch/trunk "a la" mvn 2.1 :-) ) > > > > If no objections, I will change root pom to not have anymore maven pom > > as parent. > > > Sounds good - do you think we should have a Continuum parent POM like > we do for Archiva? https://svn.apache.org/repos/asf/continuum/parent/trunk ? A new pom without parent ? (I can certainly copy some contents from the maven parent pom) Question : do we have to change the groupId in the poms : org.apache.maven.continuum -> org.apache.continuum ( java package too ? looks a big bang) > > Cheers, > > Brett > > -- > Brett Porter > [EMAIL PROTECTED] > http://blogs.exist.com/bporter/ > >
Re: svn commit: r633704 - in /continuum/branches/continuum-1.x: ./ continuum-api/ continuum-commons/ continuum-configuration/ continuum-core-it/ continuum-core/ continuum-data-management/ continuum-da
2008/3/5, Brett Porter <[EMAIL PROTECTED]>:
>
> On 05/03/2008, at 10:28 AM, [EMAIL PROTECTED] wrote:
>
> > use new continuum parent
> > change groupId to org.apache.continuum (continuun is now TLP :-) )
>
> Will this be merged to trunk too?
Yep
>
> >
> >
> >
> > -
> > org.apache.maven.continuum.management.DataManagementCli > mainClass>
> > +
> > org.apache.continuum.management.DataManagementCli > mainClass>
> >
> >
> >
> ...
> >
> >
> >
> >
> > - org.apache.maven.continuum
> > + org.apache.continuum
> > continuum-xmlrpc-client
> > ${project.version}
> >
> > @@ -60,7 +60,7 @@
> >
> > -classpath
> >
> > -
> > org.apache.maven.continuum.xmlrpc.backup.Backup
> > +org.apache.continuum.xmlrpc.backup.Backup > argument>
> > -h
> >
> >
> > @@ -73,7 +73,7 @@
> > src/assembly/app.xml
> >
> >
> > -
> > org.apache.maven.continuum.xmlrpc.backup.Backup
> > + org.apache.continuum.xmlrpc.backup.Backup > mainClass>
> >
> >
> >
> >
> ...
> >
> >
> > -
> > org.apache.maven.continuum.xmlrpc.client.SampleClient > argument>
> > +
> > org.apache.continuum.xmlrpc.client.SampleClient
> >
> >
> >
> >
> ...
> >
> >
> >
> > -
> > <
> > role
> > >org.apache.maven.continuum.xmlrpc.server.ContinuumXmlRpcComponent > role>
> > +
> > org.apache.continuum.xmlrpc.server.ContinuumXmlRpcComponent > role>
> > per-lookup > strategy>
> >
> >
> >
>
> These all look to be in error because they refer to packages (not yet
> migrated).
>
Yep good catch error
> - Brett
>
>
> --
> Brett Porter
> [EMAIL PROTECTED]
> http://blogs.exist.com/bporter/
>
>
Re: Build Error against trunk - First Build
Oops. I have fixed that in the branch but not in the trunk. (my bad !!). The parent pom is deployed in the apache snapshot repo. You can fix that by adding the following repo in your settings. people.apache.org Apache Snapshot Development Repository http://people.apache.org/repo/m2-snapshot-repository false Again sorry I will fix that. -- Olivier 2008/3/7, Wendy Smoak <[EMAIL PROTECTED]>: > On Fri, Mar 7, 2008 at 10:13 AM, murali mohan <[EMAIL PROTECTED]> wrote: > > > Downloaded the source from svn trunk. Trying to compile, but get this error > > - * > > > > org.apache.maven.reactor.MavenExecutionException: Cannot find parent: > > org.apache > > .continuum:continuum-parent for project: > > org.apache.continuum:continuum:pom:2.0- > > SNAPSHOT for project org.apache.continuum:continuum:pom:2.0-SNAPSHOT* > > Sorry about that, we're still under construction during the move to a > top-level project. > > I suspect it's this one: > http://svn.apache.org/repos/asf/continuum/parent/trunk/ > > Try checking that out and building it locally, then building Continuum again. > > -- > > Wendy >
Re: Trouble building maven-plugins parent pom in Continuum
Hi, Currently the max size for this field is 512. ChangeFile org.apache.maven.continuum.model.scm 1.0.9+ name 1.0.9+ String Which doens't look enough. 1024 ? -- Olivier 2008/3/9, Brett Porter <[EMAIL PROTECTED]>: > I think Continuum needs to allow longer values in here - it certainly > should not error out. > > > On 10/03/2008, at 7:13 AM, Wendy Smoak wrote: > > > On Sun, Mar 9, 2008 at 12:48 PM, Brett Porter <[EMAIL PROTECTED]> > > wrote: > >> Even though it uses --non-recursive to build, the checkout does not > >> exclude any subdirectories. This would occur in the checkout/update > >> and building changesets. > > > > Is a build error and "Please correct your data!" the right response > > here, or can Continuum do something useful like truncate the data and > > keep going? > > > > -- > > Wendy > > > -- > > Brett Porter > [EMAIL PROTECTED] > > http://blogs.exist.com/bporter/ > >
Re: VMBuild needs volunteers
Hi, If I can help I will (propably not a 24/7 support :-) ). 2008/3/8, Wendy Smoak <[EMAIL PROTECTED]>: > We have a Continuum instance available for ASF projects to use: > http://vmbuild.apache.org/continuum/groupSummary.action > > This is our (internal) public face, and it would be great to have more > volunteers keeping an eye on it! > > It was down this morning, so I re-started it (at 11AM MST.) I didn't > investigate why it was unhappy. > > One thing we really need to do is upgrade it to the latest version. > I'm hesitant to take that on alone, but maybe someone else is braver > than I, or 2-3 people might collaborate to get it done and documented. > Sure won't be so easy (is all the build history important ?) > And there are 11 open issues: > > https://issues.apache.org/jira/secure/IssueNavigator.jspa?reset=true&&pid=10410&component=12311662&resolution=-1&sorter/field=priority&sorter/order=DESC > > There is some documentation here: > http://cwiki.apache.org/confluence/display/vmbuild/Home > (This needs to be moved into svn to better conform with other infra > documentation, something that's been on my list for a while now...) Ok but where ? (something like https://svn.apache.org/repos/asf/vmbuild or https://svn.apache.org/repos/asf/continuum/vmbuild). Using a site write with the maven format (apt xdoc) ? > > -- > > Wendy >
Re: Confused about the branches
2008/3/4, Brett Porter <[EMAIL PROTECTED]>: > > On 05/03/2008, at 5:18 AM, Olivier Lamy wrote: > > > 2008/3/4, Brett Porter <[EMAIL PROTECTED]>: > >> > >> On 04/03/2008, at 10:47 AM, Olivier Lamy wrote: > >> > >>> Agree on this. > >>> Currently there is a blocking issue with xml-rpc CONTINUUM-1590 > >>> which > >>> prevent using xml-rpc :-(. > >> > >> > >> Cool - shall we just start using the 1.2 bucket in JIRA? There are > >> only 14 issues there now so maybe we could keep that to 20-30 issues > >> all together and release it. > > > > +1 > > > ok, I'll get my stuff in there > > > > > > > >> > >> I found these changes on trunk that are not on the branch: r617400. > >> (The rest is documentation) > >> > >> I found these changes on the branch that are not on trunk: r627196, > >> r620613, r620612, r620611 > >> > >> I think we should just merge all those from the branch to trunk, set > >> it as v1.2, and close the branch for now? > > > > +1. (Perso, I don't really like the idea of starting a parrallel > > branch/trunk "a la" mvn 2.1 :-) ) > > > I'll merge the changes to trunk - but will wait to hear other's > opinions on this too before changing the branch It looks we don't have any objections/opinions. All changes from branch has been merged. I will rename the version in the trunk to 1.2 (tomorow). > > > > > > > >> > >> > >>> If no objections, I will change root pom to not have anymore maven > >>> pom > >>> as parent. > >> > >> > >> Sounds good - do you think we should have a Continuum parent POM like > >> we do for Archiva? > > > > https://svn.apache.org/repos/asf/continuum/parent/trunk ? > > A new pom without parent ? (I can certainly copy some contents from > > the maven parent pom) > > > With an ASF parent instead of the Maven one, yep. > > > > > > > > Question : do we have to change the groupId in the poms : > > org.apache.maven.continuum -> org.apache.continuum ( java package too > > ? looks a big bang) > > > I don't see any downside to doing this :) > > > - Brett > > > -- > Brett Porter > [EMAIL PROTECTED] > http://blogs.exist.com/bporter/ > >
Re: Confused about the branches
IMHO, we can remove. 2008/3/10, Rahul Thakur <[EMAIL PROTECTED]>: > > There are some other branches residing in Continuum SVN. Should we > remove any (or all) of the following if they are not in active > development? I know (id-refactor and key-based-refactor can go) > > # continuum-acegi > # continuum-site_1.1 > # gbuild > # id-refactor > # key-based-refactor > # osworkflow-integration > # release-integration > > Cheers, > Rahul > > > Brett Porter wrote: > > Hi, > > > > I'm a bit confused about the current branch scenarios, we have 1.2 on a > > branch and 2.0 on trunk. Several changes have been made on each, and > > none merged to the other. > > > > Can I suggest we merge all branch changes to trunk, rename trunk to > > 1.2-SNAPSHOT, and the branch to continuum-1.1.x (1.1.1-SNAPSHOT) and use > > that for bugfixes only? > > > > WDYT? > > > > > - Brett > > > > -- > > Brett Porter > > [EMAIL PROTECTED] > > http://blogs.exist.com/bporter/ > > > > >
[jira] Created: (CONTINUUM-317) Unable to setup the port used by the xmlrpc service
Unable to setup the port used by the xmlrpc service --- Key: CONTINUUM-317 URL: http://jira.codehaus.org/browse/CONTINUUM-317 Project: Continuum Type: Improvement Components: continuum-xmlrpc Versions: 1.0-alpha-1, 1.0-alpha-2, 1.0-alpha-3, 1.0-alpha-4 Environment: uname -a : SunOS hostname 5.9 Generic_112233-08 sun4u sparc SUNW,Sun-Blade-100 $JAVA_HOME/bin/java -version : Java(TM) 2 Runtime Environment, Standard Edition (build 1.4.2_01-b06) Java HotSpot(TM) Client VM (build 1.4.2_01-b06, mixed mode) cvs -version : Concurrent Versions System (CVS) 1.11.5 (client/server) maven -v : v. 1.1-beta-2 Reporter: Olivier Lamy Fix For: 1.0-beta-1 The xml rpc service always start with the port 8000. I don't know (maybe I can't change it) -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-323) Project Summary with maven1 project doesn't display dependencies and developers
Project Summary with maven1 project doesn't display dependencies and developers --- Key: CONTINUUM-323 URL: http://jira.codehaus.org/browse/CONTINUUM-323 Project: Continuum Type: Bug Components: continuum-web Versions: 1.0-beta-1 Reporter: Olivier Lamy Attachments: tmp.png Project Summary with maven1 project doesn't display dependencies and developers -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-327) Two Email Notifiers with two differents address send two emails with all address.
Two Email Notifiers with two differents address send two emails with all address. - Key: CONTINUUM-327 URL: http://jira.codehaus.org/browse/CONTINUUM-327 Project: Continuum Type: Bug Versions: 1.0-beta-1 Reporter: Olivier Lamy Priority: Minor I record two email notifiers on the same project with differents recipients. The email is sending twice time with the differents recipients. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-403) cvs update with empty r argument generate error
cvs update with empty r argument generate error --- Key: CONTINUUM-403 URL: http://jira.codehaus.org/browse/CONTINUUM-403 Project: Continuum Type: Bug Components: continuum-core Versions: 1.0 Reporter: Olivier Lamy Priority: Blocker The cvs update command with an emty -r argument. This generate an error. This append when editing a project and simply updating the version of the continuum project. The only workaround is to delete and recording again the project. 2005-10-31 08:00:10,300 [Thread-1] INFO org.apache.maven.scm.manager.ScmManager - Executing: cvs - f -q update -d -r 2005-10-31 08:00:10,300 [Thread-1] INFO org.apache.maven.scm.manager.ScmManager - Working director y: /local/maven/continuum/continuum-1.0/apps/continuum/working-directory/14 2005-10-31 08:00:10,363 [Thread-1] WARN org.apache.maven.continuum.scm.ContinuumScm - Error while updating the code for project: 'tcclient', id: '14' to '/local/maven/continuum/continuum-1.0/apps/co ntinuum/working-directory/14' with branch/tag . 2005-10-31 08:00:10,364 [Thread-1] WARN org.apache.maven.continuum.scm.ContinuumScm - Command outp ut: update: option requires an argument -- r Usage: cvs update [-APCdflRp] [-k kopt] [-r rev] [-D date] [-j rev] [-I ign] [-W spec] [files...] -A Reset any sticky tags/date/kopts. -P Prune empty directories. -C Overwrite locally modified files with clean repository copies. -d Build directories, like checkout does. -f Force a head revision match if tag/date not found. -l Local directory only, no recursion. -R Process directories recursively. -p Send updates to standard output (avoids stickiness). -k kopt Use RCS kopt -k option on checkout. (is sticky) -r rev Update using specified revision/tag (is sticky). -D date Set date to update from (is sticky). -j rev Merge in changes made between current revision and rev. -I ign More files to ignore (! to reset). -W spec Wrappers specification line. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Created: (CONTINUUM-558) unavailable scm (cvs) during a build, next scheduled build doesn't start whereas the scm (cvs) is now up
unavailable scm (cvs) during a build, next scheduled build doesn't start whereas the scm (cvs) is now up - Key: CONTINUUM-558 URL: http://jira.codehaus.org/browse/CONTINUUM-558 Project: Continuum Type: Bug Versions: 1.0.2 Environment: solaris Reporter: Olivier Lamy unavailable scm (cvs) during a build, next scheduled build doesn't start whereas the scm (cvs) is now up -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-558) unavailable scm (cvs) during a build, next scheduled build doesn't start whereas the scm (cvs) is now up
[ http://jira.codehaus.org/browse/CONTINUUM-558?page=comments#action_56324 ] Olivier Lamy commented on CONTINUUM-558: which level you need, I have changed all level to INFO. But it's very difficult to shutdown the scm which is shared. I will try to send if I'm always in life ;-) > unavailable scm (cvs) during a build, next scheduled build doesn't start > whereas the scm (cvs) is now up > - > > Key: CONTINUUM-558 > URL: http://jira.codehaus.org/browse/CONTINUUM-558 > Project: Continuum > Type: Bug > Versions: 1.0.2 > Environment: solaris > Reporter: Olivier Lamy > > > unavailable scm (cvs) during a build, next scheduled build doesn't start > whereas the scm (cvs) is now up -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Commented: (CONTINUUM-462) Relative path not honoured in cvs commands for flat project layout
[ http://jira.codehaus.org/browse/CONTINUUM-462?page=comments#action_57629 ] Olivier Lamy commented on CONTINUUM-462: You can do it with continum by overriding the scm url in all modules (I use this with continuum 1.0.2) Workaround works for continuum but not for http://jira.codehaus.org/browse/MRELEASE-6 Olivier > Relative path not honoured in cvs commands for flat project layout > -- > > Key: CONTINUUM-462 > URL: http://jira.codehaus.org/browse/CONTINUUM-462 > Project: Continuum > Type: Bug > Versions: 1.0, 1.0.1 > Environment: affects all environments > Reporter: Christian Schulte > > > Continuum does not implement the flat project layout as described at > <http://maven.apache.org/guides/mini/guide-ide-eclipse.html> at the end of > the site correctly. The checkout via ViewCVS does work but during building > continuum does not propagate the relative path to the modules and the parent > correctly to the cvs commands it executes making the build fail because of > cvs errors about unknown modules. > Example: > REPOROOT > |--ROOT > |pom.xml > |--MODULE1 > |pom.xml > |--MODULE2 > |pom.xml > Just directories below REPOROOT. The ViewCVS URL to import such a project > into continuum looks something like this... > http://somehost/viewcvs/*checkout*/REPOROOT/ROOT/pom.xml > and the SCM URL inside ROOT/pom.xml looks like this... > > scm:cvs:pserver:[EMAIL PROTECTED]:/cvs:/REPOROOT/ROOT > Continuum can successfully build the project inside ROOT but fails for all > projects defined like this in ROOT/pom.xml. > > ../MODULE1 > ../MDOULE2 > > That is because it tries to do the cvs checkouts wihtout the correct relative > path as it did during initial checkout via ViewCVS. > 21212715 [Thread-1] WARN org.apache.maven.continuum.scm.ContinuumScm - > Command output: cvs server: cannot find module `REPOROOT/ROOT/MODULE1' - > ignored > cvs [checkout aborted]: cannot expand modules > Here it should have used REPOROOT/ROOT/../MODULE1. The workaround to get this > structure working in continuum is to specify the SCM URL inside every single > pom.xml of the whole project with the correct path. Continuum then does > support the flat project layout. Without the SCM URLs inside every pom it > only honours the structure during initial checkout via ViewCVS but not during > the cvs commands executed. -- This message is automatically generated by JIRA. - If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa - For more information on JIRA, see: http://www.atlassian.com/software/jira
