Re: Some continuum-jpa branch updates
On Jan 22, 2008 3:06 AM, Rahul Thakur [EMAIL PROTECTED] wrote: A Query object that wraps up criteria and is built programmatically affords us the ability to keep Store APIs lean and stable. That is the motivation behind building up queries programatically. IMHO, the current ContinuumStore is a bunch of methods that don't even vary that much underneath. I think the same can be easily achieved by using Query. With named queries, queries are cached in the persistence context so they don't need to be parsed each time. With named queries, an other good thing is that they can be overriden in the xml file if needed for performance for a specific DB and we can add query hints. The last thing is that with named queries, we know exactly which requests we execute so we can optimize the DB schema with some index, it isn't easy to do with dynamic queries. I don't say we won't use dynamic queries but only that it must be the majority of our requests and it's a JPA best practices. I am not sure if StringBuilder will be more performant than StringBuffer when you are concatenating only a few Strings. I think what is more important is a goal of a lean, test'able and clean API. It isn't important for a concatenation of few strings, but in your code, you do it in the Query generator. The concatenation will executed a lot because we execute lot of requests in all pages, so the benefit of StringBuilder is very important. I can't really comment on named queries (probably need to toy around with them a bit), and not sure how the implementation would end up making use of named queries, but if anyone else has any opinions, I am keen to understand. Cheers, Rahul Emmanuel Venisse wrote: As Christian said, named queries are pre-compiled to SQL. With dynamic queries, perf can be not good because for each execution, the JPQL request is recompile to SQL, so parsing, creation of the JPQL tree then SQL generation, and with your solution, you concatenate lot of String. It isn't important for one request but with lot of request, you use more time and cpu, for string concatenation, it is better to use StringBuilder that is more performant than String addition or StringBuffer. An other argument for named queries is that with dynamic queries, if they aren't written correctly (it isn't the case for your code ;) ), it is easy to introduce some malicious SQL code with parameters my two cents. Emmanuel On Jan 18, 2008 9:57 PM, Christian Edward Gruber[EMAIL PROTECTED] wrote: You can get some benefit from named queries in terms of query pre- compilation and caching on the underlying database. However, most database flavors and hibernate providers turn criteria queries into named queries (parameterized SQL) which is then cached, so, on the surface I suspect the performance characteristics will be similar. Christian. On 18-Jan-08, at 14:35 , Rahul Thakur wrote: Thanks Emmanuel! Responses inlined... Emmanuel Venisse wrote: Hi Rahul, After few days to look at JPA, I'm sure now it would be good to use it instead of the actual JDO/JPOX (I know JPOX 1.2 support JPA). The code is very easy to write and to read with JPA. About your continuum-jpa branch, I have few remarks: - I don't think it's good to use directly some OpenJPA APIs. If possible, I'd prefer to use only standard JPA APIs so we'll can choose later the implementation we want to use (OpenJPA, TopLink, JPOX...) Agree. The only place where OpenJPA APIs are being used directly currently are the unit tests. - why do you use some Spring code? Experimental. Spring has a good transaction management framework out of the box. - we don't need to store the model encoding (CommonUpdatableModelEntity class) Sure. Easily fix'able. :-) - can you explain dateCreated/dateUpdated fields? How are they managed? These are for audit puposes, and can be used as range search query criteria for fetching entities. These were an extension I thought will be good. 'dateCreated' gets set when an entity is first inserted into the underlying store, subsequent updates update the 'dateUpdated'. - all the model is fectched eagerly and it isn't acceptable for performance Yes, the model does needs review and tweaks to annotations where we know we don't need to fetch 'eagerly'. - I'm not sure your Query pattern is good. I'd prefer to use named queries but maybe you have a reason I think using a Query like we have on the JPA branch nicely provides for a flexible construction of queries (i.e, only the criteria passed in contributes to the query). I am not sure if such is available with named queries; but I am interested to know why named queries might be better. Cheers, Rahul That's all for the moment. Emmanuel On Jan 16, 2008 11:30 PM, Rahul Thakur [EMAIL PROTECTED] wrote: Just wondering
Re: Continuum update
The continuuum-1.x is created Emmanuel On Jan 21, 2008 11:08 PM, Emmanuel Venisse [EMAIL PROTECTED] wrote: 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: profile and projects/build definitions
A profile can't be applied to a project because generally, users want to build their projects for different environment. Maybe, we'll add a defaut project profile in future versions that can be overriden in the build definition Emmanuel On Jan 25, 2008 11:31 AM, Benoit Decherf [EMAIL PROTECTED] wrote: Hi I m' working on http://jira.codehaus.org/browse/CONTINUUM-1633 because it's blocker for us. I think that some other bugs on continuum release should be corrected if the release process is externalized to mvn. But there is a problem with CONTINUUM-1572 http://jira.codehaus.org/browse/CONTINUUM-1572. Actually, the profile is associated to a build definition. But the jdk version to use or the maven version should be associated to the component, don't you think ? I don't want to modify the core of continuum so have you plane to make a refactoring of the profile usage ? Or why a profile isn't associated to the project (or project group) ? Benoit
Re: [Discussion] Continuum 2.0 Roadmap
On Jan 30, 2008 9:05 AM, Rahul Thakur [EMAIL PROTECTED] wrote: Hi, Great to see version 2.0 discussions kicking off! Thanks for putting the ideas on confluence, Emmanuel. :-) Some notes around the ideas outlined on the wiki: 1) Architecture Moving to JSE 5 and JPA is a good idea \o/, it been fairly overdue ;-). 1-1)Can you please elaborate a bit on relationships among - services, various types of facades and entities. A concrete example would help. All the code will be in some services classes like builder service or entity modifier service. Facades will be the front-end for a specific technology like an EJB, a web service or something. The facade will delegate client calls to the service and doesn't do more. 1-2)I would like to bring Guice to the mix. I think it is worth investigating for Continuum 2.0 - WDYT? I don't think. I don't see the interest to look at it for Continuum. We already use Plexus that works fine, and if we decide to move to something else, it should be for the interest of the project and features we don't have in Continuum. But maybe you have some arguments about Guice. 2) Database I am not hard and fast on any particular JPA provider. If Toplink cuts it, we should go with it. I have been toying around with OpenJPA, but I haven't used Toplink to comment on how both compare. OpenJPA is comprehensively documented and has a good support available on mailing lists. Having said that, JPA providers would ultimately be swap'able under the hood. I don't have something to compare too. Also, I think we should stick with JPA annotations on model entities instead of using Modello. I hope writing the data access code from scratch implies the current ContinuumStore will be refactored into something which is less verbose than what we have currently, and so would the Continuum interface. I'm totally agree. We must decide too which datas are kept into the database and which datas will move to some XML files. I think some datas should be stored in XML files because we don't use them for requests and they are rarely accessed, like scm files list. About entities, we need to review the object model because some fields like scm fields in Project aren't in a good place, they should be in a sub-object even if we keep the actual db schema. 3) Builders Build definitions Just thinking out loud here... Does anyone else see the current Continuum model to be centered around 'Project'? What do you think about 'Build' or BuildDefinition being central? You can add one or more Projects to a Build - we don't need Project Groups, as all we deal with is a Build. Order and dependency can be imposed on a Build composed of more than one project. Notifiers are added to a Build and BuildResult(s) produced for a Build. I think the thing we have actually with project group that contains build definitions/notifiers is similar to your thoughts We'll can see later if we need to change the actual model. 4) Remote Builders I like this idea, but not sure how the build results will be aggregated from remote builders, but may be that is something that needs some more thought. I'll add more text about it 5) Plugins Is this similar to what AntHill Pro has? Are we going to have a notion of Build lifecycle (and phases) to support this? Is this something that can be borrowed in concept (and possibly implementation) from Maven? I don't know yet, all ideas are welcome about the design 6) External Access and UI improvements I am +1 for supporting different types of mechanisms to access and control Continuum. Web interface has been the primary interface until now and I totally agree that it needs to be improved to give a better user experience. I welcome the idea of using GWT for this. I am keen to focus more on Reporting as well for this version. As already outlined on the wiki, it would be nice if the reporting can be extended via plugins or some such mechanism. yep. 7) Documentation I would like to add and emphasize here on documenting the code itself as we write it. We are not going to get down to user documentation from day one but there will be users in the community who start consuming the code and contributing back as soon as we starting cooking it! :-) I would like to propose having Checkstyle to flag undocumented source code in codebase. I'm agree about the code documentation. Can you add it in the wiki? 8) Installation Lastly, I think it would nice to have a core Continuum install to be lean and small with features that can be added by dropping in relevant JARs (and minimal or no configuration). We can actually try different options with development releases before finalizing what should go into the main distro (if at all we break it up) - sounds reasonable? I'm agree. Thanks, Rahul Thanks for your comments, Emmanuel Emmanuel Venisse wrote: Hi I started a document [1] with my ideas about
Re: wiki was: [Discussion] Continuum 2.0 Roadmap
Thanks Brett. I'm +1 to open it. Emmanuel On Feb 13, 2008 8:43 AM, Brett Porter [EMAIL PROTECTED] wrote: no, permissions changes are non-destructive :) On 13/02/2008, at 6:33 PM, Rahul Thakur wrote: +1 as long as editing it requires a login :-) Should I hold off the migration from Codehaus? Rahul On Feb 13, 2008 6:32 PM, Brett Porter [EMAIL PROTECTED] wrote: On 13/02/2008, at 4:04 PM, Wendy Smoak wrote: On Feb 12, 2008 10:01 PM, Brett Porter [EMAIL PROTECTED] wrote: Ok, I've created two wiki's: ... http://cwiki.apache.org/confluence/display/CONTINUUMDEV/Index (exported to: http://cwiki.apache.org/CONTINUUMDEV/) This one is editable by developers only (accepts comments from anyone). This is for the roadmap and design docs. I only granted access to a few people that I could easily find - if you need to edit, just let me or a confluence admin know. Why would we not want to allow the community to participate in roadmap and design docs? The only reason I can think of to restrict access is to make sure we have a CLA for content we intend to redistribute. Both good points - I was following what we had in Maven already - what do others think - shall we just open it up? Or do we not even need the DEV space? - Brett -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/ -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/
Re: [Discussion] Continuum 2.0 Roadmap
Thanks Rahul. Emmanuel On Feb 20, 2008 4:44 AM, Rahul Thakur [EMAIL PROTECTED] wrote: Hi, I have re-organised and updated content related to Continuum 2.0 Roadmap here: http://cwiki.apache.org/confluence/display/CONTINUUMDEV/Draft+-+Continuum+2.0+Roadmap Would appreciate if others can review/update/comment as appropriate. Also, I think we start cutting out concrete JIRA tasks from those umbrella issues listed on that page above and assign them fix versions. Thanks, Rahul Emmanuel Venisse wrote: 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
Cool, great news. Thanks Brett (and others) Emmanuel On Feb 20, 2008 9:15 PM, Brett Porter [EMAIL PROTECTED] wrote: 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: ContinuumStore refactoring
As I already explained, I'm in favor of named queries On Fri, Feb 22, 2008 at 2:54 AM, Rahul Thakur [EMAIL PROTECTED] wrote: Hi, I'd like to go ahead and pick up something towards the next Continuum iteration. I am thinking refactoring ContinuumStore interface as was earlier discussed on this list and as I did on the 'continuum-jpa' branch. To this end, I need to get a clear picture on a few items: 1) Which JPA provider are we going ahead with then? I'd like to start with toplink provider. 2) Criteria vs Named Queries: I am not convinced (yet) that Named queries are the way to go. I did some digging around, they are indeed best practices for JPA but I think the decision merits other consideration(s). I still believe the Criteria Queries will help us define a cleaner Store interface. I'm always in favor of named queries. An other point about them that I haven't explain in previous threads (I think) is that with named queries, it is possible to modify queries externally with xml files so if with a DB we have some performance issues, it will be possible to override queries by a modified JPQL query or a native query. 3) Using Criteria Queries would mean that we use JPA extensions specific to provider. I don't see this as an issue as long as we are not expecting underlying JPA providers to be swapped. Thoughts? Continuum isn't a big application and I don't think we need provider extensions for now. Before to start the code, I'd like to see a DB model exported to an image so we'll can include it in the site. We must define too which datas will stay in the db and which datas will be externalized in some files. Look forward to hear. Cheers, Rahul
Re: ContinuumStore refactoring
On Fri, Feb 22, 2008 at 10:45 AM, Rahul Thakur [EMAIL PROTECTED] wrote: 2) Criteria vs Named Queries: I am not convinced (yet) that Named queries are the way to go. I did some digging around, they are indeed best practices for JPA but I think the decision merits other consideration(s). I still believe the Criteria Queries will help us define a cleaner Store interface. I'm always in favor of named queries. An other point about them that I haven't explain in previous threads (I think) is that with named queries, it is possible to modify queries externally with xml files so if with a DB we have some performance issues, it will be possible to override queries by a modified JPQL query or a native query. How do you see the refactored ContinuumStore interface using Named Queries? I suspect it will be just as verbose again. I don't want to see a new time a big class for the store part. it must be splitted in few domains. All named queries related to Project would be defined in the Project class, all named queries related to ProjectGroup would be defined in the ProjectGroup class... And we can add some more classes for particular results that aren't entities objects (we won't have a lot) With this, all concerns are separated and linked to a specific entity. Easy to code, easy to read, easy to understand. It's my opinion. Sorry, still not convinced ;-) I hope you are now ;-) Emmanuel Rahul
svn move (was: Re: Apache Continuum is now an Apache top level project)
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. Brett, when will can you do the move? Emmanuel On Thu, Feb 21, 2008 at 12:10 PM, Brett Porter [EMAIL PROTECTED] wrote: Hi Emmanuel, These are the incubator graduation steps and they mostly seem to apply here too: http://incubator.apache.org/guides/graduation.html#life-after-graduation . Many of them are for you to do directly. I've filed the infrastructure issue (INFRA-1532) and placed you in the chairs group already. Cheers, Brett On 21/02/2008, at 8:30 AM, Emmanuel Venisse wrote: Cool, great news. Thanks Brett (and others) Emmanuel On Feb 20, 2008 9:15 PM, Brett Porter [EMAIL PROTECTED] wrote: 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/ -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/
Re: svn move (was: Re: Apache Continuum is now an Apache top level project)
On Tue, Feb 26, 2008 at 12:47 AM, Brett Porter [EMAIL PROTECTED] wrote: On 26/02/2008, at 10:39 AM, Emmanuel Venisse 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. Brett, when will can you do the move? I'll lock it in for Friday morning here (about 3 days from now): http://timeanddate.com/worldclock/fixedtime.html?month=2day=29year=2008hour=8min=0sec=0p1=240 Thanks. Emmanuel
Re: ContinuumStore refactoring
I'll create some examples asap. Emmanuel On Thu, Feb 28, 2008 at 4:07 AM, Rahul Thakur [EMAIL PROTECTED] wrote: Hi, Some code using a couple of Entities as examples would be nice :-) I still think the API would be verbose. Thanks, Rahul On Fri, Feb 22, 2008 at 11:06 PM, Emmanuel Venisse [EMAIL PROTECTED] wrote: On Fri, Feb 22, 2008 at 10:45 AM, Rahul Thakur [EMAIL PROTECTED] wrote: 2) Criteria vs Named Queries: I am not convinced (yet) that Named queries are the way to go. I did some digging around, they are indeed best practices for JPA but I think the decision merits other consideration(s). I still believe the Criteria Queries will help us define a cleaner Store interface. I'm always in favor of named queries. An other point about them that I haven't explain in previous threads (I think) is that with named queries, it is possible to modify queries externally with xml files so if with a DB we have some performance issues, it will be possible to override queries by a modified JPQL query or a native query. How do you see the refactored ContinuumStore interface using Named Queries? I suspect it will be just as verbose again. I don't want to see a new time a big class for the store part. it must be splitted in few domains. All named queries related to Project would be defined in the Project class, all named queries related to ProjectGroup would be defined in the ProjectGroup class... And we can add some more classes for particular results that aren't entities objects (we won't have a lot) With this, all concerns are separated and linked to a specific entity. Easy to code, easy to read, easy to understand. It's my opinion. Sorry, still not convinced ;-) I hope you are now ;-) Emmanuel Rahul
Re: CI Server Poll
thx Rahul for this link. We are #2 now :) On Thu, Feb 28, 2008 at 4:51 AM, Rahul Thakur [EMAIL PROTECTED] wrote: Hi, Any one seen this: http://www.wakaleo.com/polls/18-what-continuous-integration-server-are-you-using-in-2008 Another 5 steps to get to #1 :-) Rahul
Re: svn commit: r632127 - /maven/continuum/branches/continuum-1.x/pom.xml
yes, it is an error.
Emmanuel
On Thu, Feb 28, 2008 at 11:13 PM, Brett Porter [EMAIL PROTECTED] wrote:
The users one seems to be missing the users. prefix in both - is there
a reason for that?
- Brett
On 29/02/2008, at 8:58 AM, [EMAIL PROTECTED] wrote:
Author: evenisse
Date: Thu Feb 28 13:58:44 2008
New Revision: 632127
URL: http://svn.apache.org/viewvc?rev=632127view=rev
Log:
Update markmail addresses
Modified:
maven/continuum/branches/continuum-1.x/pom.xml
Modified: maven/continuum/branches/continuum-1.x/pom.xml
URL:
http://svn.apache.org/viewvc/maven/continuum/branches/continuum-1.x/pom.xml?rev=632127r1=632126r2=632127view=diff
=
=
=
=
=
=
=
=
==
--- maven/continuum/branches/continuum-1.x/pom.xml (original)
+++ maven/continuum/branches/continuum-1.x/pom.xml Thu Feb 28
13:58:44 2008
@@ -41,22 +41,48 @@
inceptionYear2003/inceptionYear
mailingLists
mailingList
- nameContinuum Dev List/name
- subscribe[EMAIL PROTECTED]/subscribe
- unsubscribe[EMAIL PROTECTED]/
unsubscribe
- archive
http://mail-archives.apache.org/mod_mbox/maven-continuum-dev/
/archive
-/mailingList
-mailingList
nameContinuum User List/name
+ post[EMAIL PROTECTED]/post
subscribe[EMAIL PROTECTED]/
subscribe
unsubscribe[EMAIL PROTECTED]/
unsubscribe
archive
http://mail-archives.apache.org/mod_mbox/maven-continuum-users/
/archive
+ otherArchives
+otherArchive
http://www.mail-archive.com/[EMAIL PROTECTED]
/otherArchive
+otherArchive
http://www.nabble.com/Continuum---Users-f13868.html
/otherArchive
+otherArchivehttp://continuum.markmail.org//otherArchive
+ /otherArchives
+/mailingList
+mailingList
+ nameContinuum Developer List/name
+ postcontinuum-dev@maven.apache.org/post
+ subscribe[EMAIL PROTECTED]/subscribe
+ unsubscribe[EMAIL PROTECTED]/
unsubscribe
+ archive
http://mail-archives.apache.org/mod_mbox/maven-continuum-dev/
/archive
+ otherArchives
+otherArchive
http://www.mail-archive.com/continuum-dev@maven.apache.org
/otherArchive
+otherArchivehttp://www.nabble.com/Continuum---Dev-f13867.html
/otherArchive
+otherArchivehttp://dev.continuum.markmail.org//
otherArchive
+ /otherArchives
/mailingList
mailingList
- nameContinuum Commit List/name
+ nameContinuum Commits List/name
subscribe[EMAIL PROTECTED]/
subscribe
unsubscribe[EMAIL PROTECTED]/
unsubscribe
archive
http://mail-archives.apache.org/mod_mbox/maven-continuum-commits/
/archive
+ otherArchives
+otherArchive
http://www.mail-archive.com/[EMAIL PROTECTED]
/otherArchive
+otherArchivehttp://maven.continuum.commits.markmail.org//
otherArchive
+ /otherArchives
+/mailingList
+mailingList
+ nameContinuum Issues List/name
+ subscribe[EMAIL PROTECTED]/
subscribe
+ unsubscribe[EMAIL PROTECTED]/
unsubscribe
+ archive
http://mail-archives.apache.org/mod_mbox/maven-continuum-issues/
/archive
+ otherArchives
+otherArchive
http://www.mail-archive.com/[EMAIL PROTECTED]
/otherArchive
+otherArchive
http://www.nabble.com/Continuum---Issues-f29618.html
/otherArchive
+ /otherArchives
/mailingList
/mailingLists
scm
@@ -781,6 +807,11 @@
groupIdorg.codehaus.plexus.redback/groupId
artifactIdredback-data-management/artifactId
version${redback.version}/version
+ /dependency
+ dependency
+groupIdcommons-httpclient/groupId
+artifactIdcommons-httpclient/artifactId
+version3.1/version
/dependency
/dependencies
/dependencyManagement
--
Brett Porter
[EMAIL PROTECTED]
http://blogs.exist.com/bporter/
Re: svn move (was: Re: Apache Continuum is now an Apache top level project)
Thanks Brett. Emmanuel On Thu, Feb 28, 2008 at 11:27 PM, Brett Porter [EMAIL PROTECTED] wrote: 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/
Re: Confused about the branches
why 1.1.x? On Thu, Feb 28, 2008 at 11:45 PM, Brett Porter [EMAIL PROTECTED] 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/
Re: Confused about the branches
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. - Brett On Thu, Feb 28, 2008 at 11:45 PM, Brett Porter [EMAIL PROTECTED] 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/ -- Brett Porter [EMAIL PROTECTED] http://blogs.exist.com/bporter/
[jira] Closed: (CONTINUUM-188) Update notification in plexus according to proposal
[ http://jira.codehaus.org/browse/CONTINUUM-188?page=all ] Emmanuel Venisse closed CONTINUUM-188: -- Resolution: Fixed Done. Update notification in plexus according to proposal --- Key: CONTINUUM-188 URL: http://jira.codehaus.org/browse/CONTINUUM-188 Project: Continuum Type: Task Reporter: Jason van Zyl Assignee: Emmanuel Venisse Fix For: 1.0-alpha-3 Proposal for the modifcation of the notification mechanism can be found here: http://docs.codehaus.org/display/CONTINUUM/Notification -- 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] Resolved: (CONTINUUM-118) Update the JSW integration in the plexus runtime for Continuum
[ http://jira.codehaus.org/browse/CONTINUUM-118?page=all ] Emmanuel Venisse resolved CONTINUUM-118: Resolution: Fixed It work now on Windows Update the JSW integration in the plexus runtime for Continuum -- Key: CONTINUUM-118 URL: http://jira.codehaus.org/browse/CONTINUUM-118 Project: Continuum Type: Improvement Versions: 1.0-alpha-3 Reporter: Jason van Zyl Assignee: Trygve Laugstol Fix For: 1.0-alpha-3 It is most important for Continuum for multi-platform support to work and JSW seems to take care of this. This issue can be moved to Plexus if you like. -- 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] Closed: (CONTINUUM-33) Send build failure notification to an irc server and channel
[ http://jira.codehaus.org/browse/CONTINUUM-33?page=all ] Emmanuel Venisse closed CONTINUUM-33: - Resolution: Fixed Done. the message contains the build status. For add an url in the message, you can open an other issue. Send build failure notification to an irc server and channel Key: CONTINUUM-33 URL: http://jira.codehaus.org/browse/CONTINUUM-33 Project: Continuum Type: Wish Reporter: David Blevins Priority: Minor Fix For: 1.0-alpha-3 Would be cool to be able to have build failure events broadcasted to an irc channel. Something simple with a URL to view the details. -- 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] Closed: (CONTINUUM-219) Update to the latest Maven SCM
[ http://jira.codehaus.org/browse/CONTINUUM-219?page=all ] Emmanuel Venisse closed CONTINUUM-219: -- Resolution: Fixed done. Use Maven-SCM-1.0-alpha-2-SNAPSHOT Update to the latest Maven SCM -- Key: CONTINUUM-219 URL: http://jira.codehaus.org/browse/CONTINUUM-219 Project: Continuum Type: Task Reporter: Jason van Zyl Assignee: Emmanuel Venisse Fix For: 1.0-beta-1 -- 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] Closed: (CONTINUUM-193) Collapse the CheckoutScmResult and UpdateScmResult
[ http://jira.codehaus.org/browse/CONTINUUM-193?page=all ] Emmanuel Venisse closed CONTINUUM-193: -- Resolution: Fixed Done. collapsing in ScmResult object Collapse the CheckoutScmResult and UpdateScmResult -- Key: CONTINUUM-193 URL: http://jira.codehaus.org/browse/CONTINUUM-193 Project: Continuum Type: Task Components: continuum-web, continuum-core Reporter: Trygve Laugstol Assignee: Emmanuel Venisse Fix For: 1.0-beta-1 Having two separate objects for this is just overkill and makes life more complicated than it has to be. Right not the DefaultBuildController has to transform the CheckOutScmResult to a UpdateScmResult and that should be removed. -- 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] Closed: (CONTINUUM-213) Mail sender needs to be able to deal with authorization on the server
[ http://jira.codehaus.org/browse/CONTINUUM-213?page=all ] Emmanuel Venisse closed CONTINUUM-213: -- Resolution: Fixed Fixed. Mail sender needs to be able to deal with authorization on the server - Key: CONTINUUM-213 URL: http://jira.codehaus.org/browse/CONTINUUM-213 Project: Continuum Type: New Feature Reporter: Jason van Zyl Assignee: Emmanuel Venisse Fix For: 1.0-beta-1 -- 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-259) Fix url validation
Fix url validation -- Key: CONTINUUM-259 URL: http://jira.codehaus.org/browse/CONTINUUM-259 Project: Continuum Type: Bug Components: continuum-web Reporter: Emmanuel Venisse Priority: Critical Fix For: 1.0-alpha-4 -- 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] Closed: (CONTINUUM-214) Integrate and test the Jabber notifier
[ http://jira.codehaus.org/browse/CONTINUUM-214?page=all ] Emmanuel Venisse closed CONTINUUM-214: -- Resolution: Fixed Fix Version: (was: 1.0-alpha-4) 1.0-beta-1 we can't test it whith slimdog Integrate and test the Jabber notifier -- Key: CONTINUUM-214 URL: http://jira.codehaus.org/browse/CONTINUUM-214 Project: Continuum Type: Task Versions: 1.0-alpha-4 Reporter: Jason van Zyl Assignee: Emmanuel Venisse Fix For: 1.0-beta-1 The m2 test projects we have can be augmented to specify a jabber notifier so testing wouldn't require any additions to the web interface. -- 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-262) Create some base web test classes with jwebunit and replace slimdog tests with them
Create some base web test classes with jwebunit and replace slimdog tests with them --- Key: CONTINUUM-262 URL: http://jira.codehaus.org/browse/CONTINUUM-262 Project: Continuum Type: Task Components: continuum-web Reporter: Emmanuel Venisse Assigned to: Emmanuel Venisse Fix For: 1.0-beta-1 slimdog is too basic to correctly test the whole of continuum screens -- 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] Closed: (CONTINUUM-210) Use the new slimdog mojo for web testing
[ http://jira.codehaus.org/browse/CONTINUUM-210?page=all ] Emmanuel Venisse closed CONTINUUM-210: -- Resolution: Won't Fix Fix Version: (was: 1.0-alpha-4) 1.0-beta-1 CONTINUUM-262 Use the new slimdog mojo for web testing Key: CONTINUUM-210 URL: http://jira.codehaus.org/browse/CONTINUUM-210 Project: Continuum Type: Task Reporter: Jason van Zyl Assignee: Emmanuel Venisse Fix For: 1.0-beta-1 Thanks to John we can use a mojo. -- 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] Updated: (CONTINUUM-267) SizeLimitExceededException on upload M1 project file
[ http://jira.codehaus.org/browse/CONTINUUM-267?page=all ] Emmanuel Venisse updated CONTINUUM-267: --- Complexity: Novice (was: Intermediate) Remaining Estimate: 1 hour Original Estimate: 3600 SizeLimitExceededException on upload M1 project file Key: CONTINUUM-267 URL: http://jira.codehaus.org/browse/CONTINUUM-267 Project: Continuum Type: Bug Components: continuum-web Environment: Continuum builded from CVS. WinXP. jdk 142_09 Reporter: Anatol Pomozov Assignee: Emmanuel Venisse Priority: Minor Fix For: 1.0-alpha-4 Original Estimate: 1 hour Remaining: 1 hour When I try to upload M1 project.xml file I get following exception. Size of file is 23,5kb. I don't think that is too much for project file. 2005-08-17 13:05:39,828 [SocketListener0-2] ERROR RequestParameterParser - FileUpload failed org.apache.commons.fileupload.FileUploadBase$SizeLimitExceededException: the request was rejected because it's size exceeds allowed range at org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.java:317) at org.codehaus.plexus.summit.parameters.BaseRequestParameterParser.processFileUploadItems(BaseRequestParameterParser.java:175) at org.codehaus.plexus.summit.parameters.BaseRequestParameterParser.parse(BaseRequestParameterParser.java:127) at org.codehaus.plexus.summit.rundata.AbstractRunData.setRequest(AbstractRunData.java:156) at org.codehaus.plexus.summit.Summit.doGet(Summit.java:44) at org.codehaus.plexus.summit.Summit.doPost(Summit.java:108) at javax.servlet.http.HttpServlet.service(HttpServlet.java:615) at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:294) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567) at org.mortbay.http.HttpContext.handle(HttpContext.java:1807) at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:525) at org.mortbay.http.HttpContext.handle(HttpContext.java:1757) at org.mortbay.http.HttpServer.service(HttpServer.java:879) at org.mortbay.http.HttpConnection.service(HttpConnection.java:789) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:960) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:806) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:218) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:331) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:520) -- 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] Assigned: (CONTINUUM-267) SizeLimitExceededException on upload M1 project file
[ http://jira.codehaus.org/browse/CONTINUUM-267?page=all ] Emmanuel Venisse reassigned CONTINUUM-267: -- Assign To: Emmanuel Venisse SizeLimitExceededException on upload M1 project file Key: CONTINUUM-267 URL: http://jira.codehaus.org/browse/CONTINUUM-267 Project: Continuum Type: Bug Components: continuum-web Environment: Continuum builded from CVS. WinXP. jdk 142_09 Reporter: Anatol Pomozov Assignee: Emmanuel Venisse Priority: Minor Fix For: 1.0-alpha-4 When I try to upload M1 project.xml file I get following exception. Size of file is 23,5kb. I don't think that is too much for project file. 2005-08-17 13:05:39,828 [SocketListener0-2] ERROR RequestParameterParser - FileUpload failed org.apache.commons.fileupload.FileUploadBase$SizeLimitExceededException: the request was rejected because it's size exceeds allowed range at org.apache.commons.fileupload.FileUploadBase.parseRequest(FileUploadBase.java:317) at org.codehaus.plexus.summit.parameters.BaseRequestParameterParser.processFileUploadItems(BaseRequestParameterParser.java:175) at org.codehaus.plexus.summit.parameters.BaseRequestParameterParser.parse(BaseRequestParameterParser.java:127) at org.codehaus.plexus.summit.rundata.AbstractRunData.setRequest(AbstractRunData.java:156) at org.codehaus.plexus.summit.Summit.doGet(Summit.java:44) at org.codehaus.plexus.summit.Summit.doPost(Summit.java:108) at javax.servlet.http.HttpServlet.service(HttpServlet.java:615) at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:294) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567) at org.mortbay.http.HttpContext.handle(HttpContext.java:1807) at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:525) at org.mortbay.http.HttpContext.handle(HttpContext.java:1757) at org.mortbay.http.HttpServer.service(HttpServer.java:879) at org.mortbay.http.HttpConnection.service(HttpConnection.java:789) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:960) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:806) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:218) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:331) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:520) -- 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-295) Update modello file for jdo generation and remove continuum-store project
[ http://jira.codehaus.org/browse/CONTINUUM-295?page=comments#action_45062 ] Emmanuel Venisse commented on CONTINUUM-295: I'm not sure it's a good idea to try to create JdoStore class. In it we need to use several fetch group and I don't know for the moment how to generate it. Update modello file for jdo generation and remove continuum-store project - Key: CONTINUUM-295 URL: http://jira.codehaus.org/browse/CONTINUUM-295 Project: Continuum Type: Sub-task Reporter: Emmanuel Venisse Assignee: Emmanuel Venisse Fix For: 1.0-alpha-4 Original Estimate: 2 hours, 30 minutes Remaining: 2 hours, 30 minutes -- 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] Updated: (CONTINUUM-282) use build definitions
[ http://jira.codehaus.org/browse/CONTINUUM-282?page=all ] Emmanuel Venisse updated CONTINUUM-282: --- Remaining Estimate: 5 hours (was: 0 minutes) use build definitions - Key: CONTINUUM-282 URL: http://jira.codehaus.org/browse/CONTINUUM-282 Project: Continuum Type: New Feature Components: continuum-web Reporter: Brett Porter Assignee: Emmanuel Venisse Priority: Blocker Fix For: 1.0-alpha-4 Time Spent: 4 hours Remaining: 5 hours we need to write these into the web interface so that we have the functionality from alpha-3 http://people.apache.org/~brett/white-site/viewProject.html http://people.apache.org/~brett/white-site/addBuildDef.html just use default schedules and profiles to begin with. -- 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] Closed: (CONTINUUM-299) use build definitions
[ http://jira.codehaus.org/browse/CONTINUUM-299?page=all ] Emmanuel Venisse closed CONTINUUM-299: -- Resolution: Fixed done. use build definitions - Key: CONTINUUM-299 URL: http://jira.codehaus.org/browse/CONTINUUM-299 Project: Continuum Type: New Feature Components: continuum-web Reporter: Emmanuel Venisse Assignee: Emmanuel Venisse Priority: Blocker Fix For: 1.0-alpha-4 Original Estimate: 5 hours Time Spent: 5 hours Remaining: 0 minutes we need to write these into the web interface so that we have the functionality from alpha-3 http://people.apache.org/~brett/white-site/viewProject.html http://people.apache.org/~brett/white-site/addBuildDef.html just use default schedules and profiles to begin with. -- 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] Updated: (CONTINUUM-251) Add a Return to Notifiers button in notifier view
[ http://jira.codehaus.org/browse/CONTINUUM-251?page=all ] Emmanuel Venisse updated CONTINUUM-251: --- Assign To: Emmanuel Venisse Remaining Estimate: 10 minutes Original Estimate: 600 Add a Return to Notifiers button in notifier view --- Key: CONTINUUM-251 URL: http://jira.codehaus.org/browse/CONTINUUM-251 Project: Continuum Type: Improvement Components: continuum-web Versions: 1.0-alpha-4 Reporter: Emmanuel Venisse Assignee: Emmanuel Venisse Fix For: 1.0-alpha-4 Original Estimate: 10 minutes Remaining: 10 minutes -- 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] Closed: (CONTINUUM-251) Add a Return to Notifiers button in notifier view
[ http://jira.codehaus.org/browse/CONTINUUM-251?page=all ] Emmanuel Venisse closed CONTINUUM-251: -- Resolution: Fixed done. Add a Return to Notifiers button in notifier view --- Key: CONTINUUM-251 URL: http://jira.codehaus.org/browse/CONTINUUM-251 Project: Continuum Type: Improvement Components: continuum-web Versions: 1.0-alpha-4 Reporter: Emmanuel Venisse Assignee: Emmanuel Venisse Fix For: 1.0-alpha-4 Original Estimate: 10 minutes Time Spent: 10 minutes Remaining: 0 minutes -- 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] Updated: (CONTINUUM-252) Can't delete a notifier define in the pom
[ http://jira.codehaus.org/browse/CONTINUUM-252?page=all ] Emmanuel Venisse updated CONTINUUM-252: --- Remaining Estimate: 30 minutes Original Estimate: 1800 Can't delete a notifier define in the pom - Key: CONTINUUM-252 URL: http://jira.codehaus.org/browse/CONTINUUM-252 Project: Continuum Type: Bug Components: continuum-web Reporter: Emmanuel Venisse Fix For: 1.0-alpha-4 Original Estimate: 30 minutes Remaining: 30 minutes When we try to delete a notifier define in pom, we obtain this exception : ognl.MethodFailedException: Method removeNotifier failed for object [EMAIL PROTECTED] [javax.jdo.JDOUserException: Transient instances cant be deleted.] at ognl.OgnlRuntime.callAppropriateMethod(OgnlRuntime.java:796) at ognl.ObjectMethodAccessor.callMethod(ObjectMethodAccessor.java:61) at ognl.OgnlRuntime.callMethod(OgnlRuntime.java:819) at ognl.ASTMethod.getValueBody(ASTMethod.java:75) at ognl.SimpleNode.evaluateGetValueBody(SimpleNode.java:170) at ognl.SimpleNode.getValue(SimpleNode.java:210) at ognl.Ognl.getValue(Ognl.java:333) at ognl.Ognl.getValue(Ognl.java:378) at ognl.Ognl.getValue(Ognl.java:357) at org.apache.maven.continuum.web.action.CallApplicationModel.execute(CallApplicationModel.java:72) at org.codehaus.plexus.summit.pipeline.valve.ActionValve.invoke(ActionValve.java:67) at org.codehaus.plexus.summit.pipeline.AbstractPipeline.invoke(AbstractPipeline.java:70) at org.codehaus.plexus.summit.Summit.doGet(Summit.java:54) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:294) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567) at org.mortbay.http.HttpContext.handle(HttpContext.java:1807) at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:525) at org.mortbay.http.HttpContext.handle(HttpContext.java:1757) at org.mortbay.http.HttpServer.service(HttpServer.java:879) at org.mortbay.http.HttpConnection.service(HttpConnection.java:789) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:960) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:806) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:218) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:331) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:520) /-- Encapsulated exception \ javax.jdo.JDOUserException: Transient instances cant be deleted. at org.jpox.AbstractPersistenceManager.internalDeletePersistent(AbstractPersistenceManager.java:1107) at org.jpox.AbstractPersistenceManager.deletePersistent(AbstractPersistenceManager.java:1133) at org.apache.maven.continuum.store.JdoContinuumStore.attachAndDelete(JdoContinuumStore.java:1225) at org.apache.maven.continuum.store.JdoContinuumStore.removeNotifier(JdoContinuumStore.java:697) at org.apache.maven.continuum.core.DefaultContinuumCore.removeNotifier(DefaultContinuumCore.java:189) at org.apache.maven.continuum.DefaultContinuum.removeNotifier(DefaultContinuum.java:549) 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 ognl.OgnlRuntime.invokeMethod(OgnlRuntime.java:491) at ognl.OgnlRuntime.callAppropriateMethod(OgnlRuntime.java:785) at ognl.ObjectMethodAccessor.callMethod(ObjectMethodAccessor.java:61) at ognl.OgnlRuntime.callMethod(OgnlRuntime.java:819) at ognl.ASTMethod.getValueBody(ASTMethod.java:75) at ognl.SimpleNode.evaluateGetValueBody(SimpleNode.java:170) at ognl.SimpleNode.getValue(SimpleNode.java:210) at ognl.Ognl.getValue(Ognl.java:333) at ognl.Ognl.getValue(Ognl.java:378) at ognl.Ognl.getValue(Ognl.java:357) at org.apache.maven.continuum.web.action.CallApplicationModel.execute(CallApplicationModel.java:72) at org.codehaus.plexus.summit.pipeline.valve.ActionValve.invoke(ActionValve.java:67) at org.codehaus.plexus.summit.pipeline.AbstractPipeline.invoke(AbstractPipeline.java:70) at org.codehaus.plexus.summit.Summit.doGet(Summit.java:54) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595
[jira] Assigned: (CONTINUUM-252) Can't delete a notifier define in the pom
[ http://jira.codehaus.org/browse/CONTINUUM-252?page=all ] Emmanuel Venisse reassigned CONTINUUM-252: -- Assign To: Emmanuel Venisse Can't delete a notifier define in the pom - Key: CONTINUUM-252 URL: http://jira.codehaus.org/browse/CONTINUUM-252 Project: Continuum Type: Bug Components: continuum-web Reporter: Emmanuel Venisse Assignee: Emmanuel Venisse Fix For: 1.0-alpha-4 Original Estimate: 30 minutes Remaining: 30 minutes When we try to delete a notifier define in pom, we obtain this exception : ognl.MethodFailedException: Method removeNotifier failed for object [EMAIL PROTECTED] [javax.jdo.JDOUserException: Transient instances cant be deleted.] at ognl.OgnlRuntime.callAppropriateMethod(OgnlRuntime.java:796) at ognl.ObjectMethodAccessor.callMethod(ObjectMethodAccessor.java:61) at ognl.OgnlRuntime.callMethod(OgnlRuntime.java:819) at ognl.ASTMethod.getValueBody(ASTMethod.java:75) at ognl.SimpleNode.evaluateGetValueBody(SimpleNode.java:170) at ognl.SimpleNode.getValue(SimpleNode.java:210) at ognl.Ognl.getValue(Ognl.java:333) at ognl.Ognl.getValue(Ognl.java:378) at ognl.Ognl.getValue(Ognl.java:357) at org.apache.maven.continuum.web.action.CallApplicationModel.execute(CallApplicationModel.java:72) at org.codehaus.plexus.summit.pipeline.valve.ActionValve.invoke(ActionValve.java:67) at org.codehaus.plexus.summit.pipeline.AbstractPipeline.invoke(AbstractPipeline.java:70) at org.codehaus.plexus.summit.Summit.doGet(Summit.java:54) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:294) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567) at org.mortbay.http.HttpContext.handle(HttpContext.java:1807) at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:525) at org.mortbay.http.HttpContext.handle(HttpContext.java:1757) at org.mortbay.http.HttpServer.service(HttpServer.java:879) at org.mortbay.http.HttpConnection.service(HttpConnection.java:789) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:960) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:806) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:218) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:331) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:520) /-- Encapsulated exception \ javax.jdo.JDOUserException: Transient instances cant be deleted. at org.jpox.AbstractPersistenceManager.internalDeletePersistent(AbstractPersistenceManager.java:1107) at org.jpox.AbstractPersistenceManager.deletePersistent(AbstractPersistenceManager.java:1133) at org.apache.maven.continuum.store.JdoContinuumStore.attachAndDelete(JdoContinuumStore.java:1225) at org.apache.maven.continuum.store.JdoContinuumStore.removeNotifier(JdoContinuumStore.java:697) at org.apache.maven.continuum.core.DefaultContinuumCore.removeNotifier(DefaultContinuumCore.java:189) at org.apache.maven.continuum.DefaultContinuum.removeNotifier(DefaultContinuum.java:549) 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 ognl.OgnlRuntime.invokeMethod(OgnlRuntime.java:491) at ognl.OgnlRuntime.callAppropriateMethod(OgnlRuntime.java:785) at ognl.ObjectMethodAccessor.callMethod(ObjectMethodAccessor.java:61) at ognl.OgnlRuntime.callMethod(OgnlRuntime.java:819) at ognl.ASTMethod.getValueBody(ASTMethod.java:75) at ognl.SimpleNode.evaluateGetValueBody(SimpleNode.java:170) at ognl.SimpleNode.getValue(SimpleNode.java:210) at ognl.Ognl.getValue(Ognl.java:333) at ognl.Ognl.getValue(Ognl.java:378) at ognl.Ognl.getValue(Ognl.java:357) at org.apache.maven.continuum.web.action.CallApplicationModel.execute(CallApplicationModel.java:72) at org.codehaus.plexus.summit.pipeline.valve.ActionValve.invoke(ActionValve.java:67) at org.codehaus.plexus.summit.pipeline.AbstractPipeline.invoke(AbstractPipeline.java:70) at org.codehaus.plexus.summit.Summit.doGet(Summit.java:54) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595
[jira] Closed: (CONTINUUM-252) Can't delete a notifier define in the pom
[ http://jira.codehaus.org/browse/CONTINUUM-252?page=all ] Emmanuel Venisse closed CONTINUUM-252: -- Resolution: Fixed Fixed. We can now delete a notifier defined in pom, but it come back after a new checkout. Can't delete a notifier define in the pom - Key: CONTINUUM-252 URL: http://jira.codehaus.org/browse/CONTINUUM-252 Project: Continuum Type: Bug Components: continuum-web Reporter: Emmanuel Venisse Assignee: Emmanuel Venisse Fix For: 1.0-alpha-4 Original Estimate: 30 minutes Time Spent: 30 minutes Remaining: 0 minutes When we try to delete a notifier define in pom, we obtain this exception : ognl.MethodFailedException: Method removeNotifier failed for object [EMAIL PROTECTED] [javax.jdo.JDOUserException: Transient instances cant be deleted.] at ognl.OgnlRuntime.callAppropriateMethod(OgnlRuntime.java:796) at ognl.ObjectMethodAccessor.callMethod(ObjectMethodAccessor.java:61) at ognl.OgnlRuntime.callMethod(OgnlRuntime.java:819) at ognl.ASTMethod.getValueBody(ASTMethod.java:75) at ognl.SimpleNode.evaluateGetValueBody(SimpleNode.java:170) at ognl.SimpleNode.getValue(SimpleNode.java:210) at ognl.Ognl.getValue(Ognl.java:333) at ognl.Ognl.getValue(Ognl.java:378) at ognl.Ognl.getValue(Ognl.java:357) at org.apache.maven.continuum.web.action.CallApplicationModel.execute(CallApplicationModel.java:72) at org.codehaus.plexus.summit.pipeline.valve.ActionValve.invoke(ActionValve.java:67) at org.codehaus.plexus.summit.pipeline.AbstractPipeline.invoke(AbstractPipeline.java:70) at org.codehaus.plexus.summit.Summit.doGet(Summit.java:54) at javax.servlet.http.HttpServlet.service(HttpServlet.java:595) at javax.servlet.http.HttpServlet.service(HttpServlet.java:688) at org.mortbay.jetty.servlet.ServletHolder.handle(ServletHolder.java:358) at org.mortbay.jetty.servlet.WebApplicationHandler.dispatch(WebApplicationHandler.java:294) at org.mortbay.jetty.servlet.ServletHandler.handle(ServletHandler.java:567) at org.mortbay.http.HttpContext.handle(HttpContext.java:1807) at org.mortbay.jetty.servlet.WebApplicationContext.handle(WebApplicationContext.java:525) at org.mortbay.http.HttpContext.handle(HttpContext.java:1757) at org.mortbay.http.HttpServer.service(HttpServer.java:879) at org.mortbay.http.HttpConnection.service(HttpConnection.java:789) at org.mortbay.http.HttpConnection.handleNext(HttpConnection.java:960) at org.mortbay.http.HttpConnection.handle(HttpConnection.java:806) at org.mortbay.http.SocketListener.handleConnection(SocketListener.java:218) at org.mortbay.util.ThreadedServer.handle(ThreadedServer.java:331) at org.mortbay.util.ThreadPool$PoolThread.run(ThreadPool.java:520) /-- Encapsulated exception \ javax.jdo.JDOUserException: Transient instances cant be deleted. at org.jpox.AbstractPersistenceManager.internalDeletePersistent(AbstractPersistenceManager.java:1107) at org.jpox.AbstractPersistenceManager.deletePersistent(AbstractPersistenceManager.java:1133) at org.apache.maven.continuum.store.JdoContinuumStore.attachAndDelete(JdoContinuumStore.java:1225) at org.apache.maven.continuum.store.JdoContinuumStore.removeNotifier(JdoContinuumStore.java:697) at org.apache.maven.continuum.core.DefaultContinuumCore.removeNotifier(DefaultContinuumCore.java:189) at org.apache.maven.continuum.DefaultContinuum.removeNotifier(DefaultContinuum.java:549) 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 ognl.OgnlRuntime.invokeMethod(OgnlRuntime.java:491) at ognl.OgnlRuntime.callAppropriateMethod(OgnlRuntime.java:785) at ognl.ObjectMethodAccessor.callMethod(ObjectMethodAccessor.java:61) at ognl.OgnlRuntime.callMethod(OgnlRuntime.java:819) at ognl.ASTMethod.getValueBody(ASTMethod.java:75) at ognl.SimpleNode.evaluateGetValueBody(SimpleNode.java:170) at ognl.SimpleNode.getValue(SimpleNode.java:210) at ognl.Ognl.getValue(Ognl.java:333) at ognl.Ognl.getValue(Ognl.java:378) at ognl.Ognl.getValue(Ognl.java:357) at org.apache.maven.continuum.web.action.CallApplicationModel.execute(CallApplicationModel.java:72) at org.codehaus.plexus.summit.pipeline.valve.ActionValve.invoke(ActionValve.java:67) at org.codehaus.plexus.summit.pipeline.AbstractPipeline.invoke(AbstractPipeline.java:70) at org.codehaus.plexus.summit.Summit.doGet
[jira] Assigned: (CONTINUUM-171) exception in failed checkout is not helpful
[ http://jira.codehaus.org/browse/CONTINUUM-171?page=all ] Emmanuel Venisse reassigned CONTINUUM-171: -- Assign To: Emmanuel Venisse (was: Trygve Laugstol) exception in failed checkout is not helpful --- Key: CONTINUUM-171 URL: http://jira.codehaus.org/browse/CONTINUUM-171 Project: Continuum Type: Bug Reporter: Brett Porter Assignee: Emmanuel Venisse Fix For: 1.0-alpha-4 Original Estimate: 1 hour Time Spent: 1 hour Remaining: 0 minutes the exception propogated for a failed checkout doesn't report what actually went wrong (in my case, it attempted to use a directory 1 which was left over from before I had blown away the db, but already existed). -- 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] Closed: (CONTINUUM-171) exception in failed checkout is not helpful
[ http://jira.codehaus.org/browse/CONTINUUM-171?page=all ] Emmanuel Venisse closed CONTINUUM-171: -- Resolution: Fixed Fixed. Checkout errors are visible now in build screen. exception in failed checkout is not helpful --- Key: CONTINUUM-171 URL: http://jira.codehaus.org/browse/CONTINUUM-171 Project: Continuum Type: Bug Reporter: Brett Porter Assignee: Trygve Laugstol Fix For: 1.0-alpha-4 Original Estimate: 1 hour Time Spent: 1 hour Remaining: 0 minutes the exception propogated for a failed checkout doesn't report what actually went wrong (in my case, it attempted to use a directory 1 which was left over from before I had blown away the db, but already existed). -- 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] Assigned: (CONTINUUM-211) Improve error message when ScmUpdate fails
[ http://jira.codehaus.org/browse/CONTINUUM-211?page=all ] Emmanuel Venisse reassigned CONTINUUM-211: -- Assign To: Emmanuel Venisse (was: Trygve Laugstol) Improve error message when ScmUpdate fails -- Key: CONTINUUM-211 URL: http://jira.codehaus.org/browse/CONTINUUM-211 Project: Continuum Type: Improvement Reporter: Jason van Zyl Assignee: Emmanuel Venisse Fix For: 1.0-alpha-4 Add the maven-plexus-plugin POM to see an example currently of what the error message looks like. You can look in the logs but it would be nice to see on the console what the problem is. -- 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] Assigned: (CONTINUUM-208) If an SCM command fails it would be useful to see the command that caused the failure
[ http://jira.codehaus.org/browse/CONTINUUM-208?page=all ] Emmanuel Venisse reassigned CONTINUUM-208: -- Assign To: Emmanuel Venisse (was: Trygve Laugstol) If an SCM command fails it would be useful to see the command that caused the failure - Key: CONTINUUM-208 URL: http://jira.codehaus.org/browse/CONTINUUM-208 Project: Continuum Type: Improvement Reporter: Jason van Zyl Assignee: Emmanuel Venisse Fix For: 1.0-alpha-4 -- 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] Updated: (CONTINUUM-208) If an SCM command fails it would be useful to see the command that caused the failure
[ http://jira.codehaus.org/browse/CONTINUUM-208?page=all ] Emmanuel Venisse updated CONTINUUM-208: --- Description: Complexity: Novice Remaining Estimate: 3 hours Original Estimate: 10800 Environment: Need to add command line in all commands in Maven SCM If an SCM command fails it would be useful to see the command that caused the failure - Key: CONTINUUM-208 URL: http://jira.codehaus.org/browse/CONTINUUM-208 Project: Continuum Type: Improvement Reporter: Jason van Zyl Assignee: Emmanuel Venisse Fix For: 1.0-alpha-4 Original Estimate: 3 hours Remaining: 3 hours -- 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] Updated: (CONTINUUM-241) Added notifiers from web interface are removed after a new build
[ http://jira.codehaus.org/browse/CONTINUUM-241?page=all ] Emmanuel Venisse updated CONTINUUM-241: --- Remaining Estimate: 4 hours Original Estimate: 14400 Added notifiers from web interface are removed after a new build Key: CONTINUUM-241 URL: http://jira.codehaus.org/browse/CONTINUUM-241 Project: Continuum Type: Bug Components: continuum-web Versions: 1.0-alpha-4 Reporter: Emmanuel Venisse Fix For: 1.0-alpha-4 Original Estimate: 4 hours Remaining: 4 hours -- 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] Assigned: (CONTINUUM-241) Added notifiers from web interface are removed after a new build
[ http://jira.codehaus.org/browse/CONTINUUM-241?page=all ] Emmanuel Venisse reassigned CONTINUUM-241: -- Assign To: Emmanuel Venisse Added notifiers from web interface are removed after a new build Key: CONTINUUM-241 URL: http://jira.codehaus.org/browse/CONTINUUM-241 Project: Continuum Type: Bug Components: continuum-web Versions: 1.0-alpha-4 Reporter: Emmanuel Venisse Assignee: Emmanuel Venisse Fix For: 1.0-alpha-4 Original Estimate: 4 hours Remaining: 4 hours -- 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-302) Put back alarm clock or quartz alarm clock
Put back alarm clock or quartz alarm clock -- Key: CONTINUUM-302 URL: http://jira.codehaus.org/browse/CONTINUUM-302 Project: Continuum Type: Task Reporter: Emmanuel Venisse Priority: Blocker Fix For: 1.0-alpha-4 alarm clock have been removed, so continuum can't build project with an interval time but only manually -- 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] Assigned: (CONTINUUM-302) Put back alarm clock or quartz alarm clock
[ http://jira.codehaus.org/browse/CONTINUUM-302?page=all ] Emmanuel Venisse reassigned CONTINUUM-302: -- Assign To: Emmanuel Venisse Put back alarm clock or quartz alarm clock -- Key: CONTINUUM-302 URL: http://jira.codehaus.org/browse/CONTINUUM-302 Project: Continuum Type: Task Reporter: Emmanuel Venisse Assignee: Emmanuel Venisse Priority: Blocker Fix For: 1.0-alpha-4 Original Estimate: 5 hours Remaining: 5 hours alarm clock have been removed, so continuum can't build project with an interval time but only manually -- 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] Updated: (CONTINUUM-43) multiple schedules and schedule selection
[ http://jira.codehaus.org/browse/CONTINUUM-43?page=all ] Emmanuel Venisse updated CONTINUUM-43: -- Assign To: Emmanuel Venisse Remaining Estimate: 6 hours Original Estimate: 21600 multiple schedules and schedule selection - Key: CONTINUUM-43 URL: http://jira.codehaus.org/browse/CONTINUUM-43 Project: Continuum Type: New Feature Reporter: Brett Porter Assignee: Emmanuel Venisse Fix For: 1.0-alpha-4 Original Estimate: 6 hours Remaining: 6 hours it would be good to be able to add new schedules and be able to select them on a per project or per group basis. Some projects would like to be able to build much more frequently as they have frequent changes. -- 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-43) multiple schedules and schedule selection
[ http://jira.codehaus.org/browse/CONTINUUM-43?page=comments#action_45721 ] Emmanuel Venisse commented on CONTINUUM-43: --- I need now to add the schedule selection from build definition multiple schedules and schedule selection - Key: CONTINUUM-43 URL: http://jira.codehaus.org/browse/CONTINUUM-43 Project: Continuum Type: New Feature Reporter: Brett Porter Assignee: Emmanuel Venisse Fix For: 1.0-alpha-4 Original Estimate: 6 hours Time Spent: 5 hours Remaining: 1 hour it would be good to be able to add new schedules and be able to select them on a per project or per group basis. Some projects would like to be able to build much more frequently as they have frequent changes. -- 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-304) Need a cron expression validator
Need a cron expression validator Key: CONTINUUM-304 URL: http://jira.codehaus.org/browse/CONTINUUM-304 Project: Continuum Type: Improvement Components: continuum-web Reporter: Emmanuel Venisse Fix For: 1.0-beta-1 -- 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-264) Keep trying after scm failed updating
[ http://jira.codehaus.org/browse/CONTINUUM-264?page=comments#action_45826 ] Emmanuel Venisse commented on CONTINUUM-264: if an update failed, project state is set for the moment to ERROR and a mail is sended like a broken build. Continuum will try to update with the next trigger. Keep trying after scm failed updating - Key: CONTINUUM-264 URL: http://jira.codehaus.org/browse/CONTINUUM-264 Project: Continuum Type: Improvement Components: continuum-core Versions: 1.0-alpha-3 Environment: linux, sun jdk 1.4 (not important) Reporter: Torsten Curdt Fix For: 1.0-beta-1 Currently a failed update from the scm and a broken build are being treated the same. IMO it would be better just to set a warning state for that project and retry building with the next trigger. Whether the warning emits an email or not should be configurable. -- 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] Updated: (CONTINUUM-264) Keep trying after scm failed updating
[ http://jira.codehaus.org/browse/CONTINUUM-264?page=all ] Emmanuel Venisse updated CONTINUUM-264: --- Fix Version: (was: 1.0-alpha-4) 1.0-beta-1 Keep trying after scm failed updating - Key: CONTINUUM-264 URL: http://jira.codehaus.org/browse/CONTINUUM-264 Project: Continuum Type: Improvement Components: continuum-core Versions: 1.0-alpha-3 Environment: linux, sun jdk 1.4 (not important) Reporter: Torsten Curdt Fix For: 1.0-beta-1 Currently a failed update from the scm and a broken build are being treated the same. IMO it would be better just to set a warning state for that project and retry building with the next trigger. Whether the warning emits an email or not should be configurable. -- 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] Closed: (CONTINUUM-43) multiple schedules and schedule selection
[ http://jira.codehaus.org/browse/CONTINUUM-43?page=all ] Emmanuel Venisse closed CONTINUUM-43: - Resolution: Fixed Done. multiple schedules and schedule selection - Key: CONTINUUM-43 URL: http://jira.codehaus.org/browse/CONTINUUM-43 Project: Continuum Type: New Feature Reporter: Brett Porter Assignee: Emmanuel Venisse Fix For: 1.0-alpha-4 Original Estimate: 6 hours Time Spent: 6 hours Remaining: 0 minutes it would be good to be able to add new schedules and be able to select them on a per project or per group basis. Some projects would like to be able to build much more frequently as they have frequent changes. -- 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] Closed: (CONTINUUM-306) support for authenticated http:// urls
[ http://jira.codehaus.org/browse/CONTINUUM-306?page=all ] Emmanuel Venisse closed CONTINUUM-306: -- Assign To: Emmanuel Venisse Resolution: Fixed Fix Version: 1.0-alpha-4 Applied. Thanks. support for authenticated http:// urls -- Key: CONTINUUM-306 URL: http://jira.codehaus.org/browse/CONTINUUM-306 Project: Continuum Type: New Feature Reporter: Christoph Sturm Assignee: Emmanuel Venisse Fix For: 1.0-alpha-4 Attachments: diff this patch needs http://jira.codehaus.org/browse/PLX-155 -- 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] Updated: (CONTINUUM-300) Add delete confirmation screen for build definitions and notifiers
[ http://jira.codehaus.org/browse/CONTINUUM-300?page=all ] Emmanuel Venisse updated CONTINUUM-300: --- Assign To: Emmanuel Venisse Remaining Estimate: 1 hour Original Estimate: 3600 Add delete confirmation screen for build definitions and notifiers -- Key: CONTINUUM-300 URL: http://jira.codehaus.org/browse/CONTINUUM-300 Project: Continuum Type: New Feature Components: continuum-web Reporter: Emmanuel Venisse Assignee: Emmanuel Venisse Fix For: 1.0-alpha-4 Original Estimate: 1 hour Remaining: 1 hour -- 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] Closed: (CONTINUUM-300) Add delete confirmation screen for build definitions and notifiers
[ http://jira.codehaus.org/browse/CONTINUUM-300?page=all ] Emmanuel Venisse closed CONTINUUM-300: -- Resolution: Fixed done. Add delete confirmation screen for build definitions and notifiers -- Key: CONTINUUM-300 URL: http://jira.codehaus.org/browse/CONTINUUM-300 Project: Continuum Type: New Feature Components: continuum-web Reporter: Emmanuel Venisse Assignee: Emmanuel Venisse Fix For: 1.0-alpha-4 Original Estimate: 1 hour Time Spent: 1 hour Remaining: 0 minutes -- 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-308) continuum-web doesn't work due to plexus-summit beta-6
continuum-web doesn't work due to plexus-summit beta-6 -- Key: CONTINUUM-308 URL: http://jira.codehaus.org/browse/CONTINUUM-308 Project: Continuum Type: Bug Versions: 1.0-alpha-4 Reporter: Emmanuel Venisse Assigned to: Emmanuel Venisse Fix For: 1.0-alpha-4 -- 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] Updated: (CONTINUUM-257) Ability to not include the build result in the mails.
[ http://jira.codehaus.org/browse/CONTINUUM-257?page=all ] Emmanuel Venisse updated CONTINUUM-257: --- Assign To: Emmanuel Venisse Fix Version: (was: 1.0-beta-1) 1.0-alpha-4 Remaining Estimate: 1 hour Original Estimate: 3600 Ability to not include the build result in the mails. - Key: CONTINUUM-257 URL: http://jira.codehaus.org/browse/CONTINUUM-257 Project: Continuum Type: New Feature Reporter: Trygve Laugstol Assignee: Emmanuel Venisse Fix For: 1.0-alpha-4 Original Estimate: 1 hour Remaining: 1 hour Instead just point to the URL where the build result can be found. -- 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] Updated: (CONTINUUM-311) add JDK and OS name to the build result mail (web?)
[ http://jira.codehaus.org/browse/CONTINUUM-311?page=all ] Emmanuel Venisse updated CONTINUUM-311: --- Fix Version: (was: 1.0-beta-1) 1.0-alpha-4 add JDK and OS name to the build result mail (web?) --- Key: CONTINUUM-311 URL: http://jira.codehaus.org/browse/CONTINUUM-311 Project: Continuum Type: New Feature Reporter: Brett Porter Fix For: 1.0-alpha-4 if you can sneak this into alpha-4, that'd be great! -- 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] Closed: (CONTINUUM-311) add JDK and OS name to the build result mail (web?)
[ http://jira.codehaus.org/browse/CONTINUUM-311?page=all ] Emmanuel Venisse closed CONTINUUM-311: -- Resolution: Fixed Done in mail. I'll add it to the build result screen later. add JDK and OS name to the build result mail (web?) --- Key: CONTINUUM-311 URL: http://jira.codehaus.org/browse/CONTINUUM-311 Project: Continuum Type: New Feature Reporter: Brett Porter Assignee: Emmanuel Venisse Fix For: 1.0-alpha-4 Original Estimate: 30 minutes Time Spent: 30 minutes Remaining: 0 minutes if you can sneak this into alpha-4, that'd be great! -- 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] Closed: (CONTINUUM-246) Missing 'scm' element in the POM after a restart
[ http://jira.codehaus.org/browse/CONTINUUM-246?page=all ] Emmanuel Venisse closed CONTINUUM-246: -- Resolution: Cannot Reproduce Fix Version: (was: 1.0-beta-1) 1.0-alpha-4 Missing 'scm' element in the POM after a restart -- Key: CONTINUUM-246 URL: http://jira.codehaus.org/browse/CONTINUUM-246 Project: Continuum Type: Bug Versions: 1.0-alpha-3 Reporter: jeremi Joslin Fix For: 1.0-alpha-4 Attachments: Screenshot.png I add my pom.xml, all is Ok, my 3 projects are added and compile. my pom : https://svn.codehaus.org/oxyd/trunk/pom.xml after a restart of the server, i have this error at the build : Missing 'scm' element in the POM. --- org.apache.maven.continuum.execution.ContinuumBuildExecutorException: Error while mapping metadata. =09at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.u= pdateProjectFromCheckOut(MavenTwoBuildExecutor.java:92) =09at org.apache.maven.continuum.core.action.UpdateProjectFromWorkingDirect= oryContinuumAction.execute(UpdateProjectFromWorkingDirectoryContinuumAction= .java:45) =09at org.apache.maven.continuum.buildcontroller.DefaultBuildController.bui= ld(DefaultBuildController.java:183) =09at org.apache.maven.continuum.buildcontroller.BuildProjectTaskExecutor.e= xecuteTask(BuildProjectTaskExecutor.java:50) =09at org.codehaus.plexus.taskqueue.execution.ThreadedTaskQueueExecutor$Exe= cutorRunnable.run(ThreadedTaskQueueExecutor.java:103) =09at java.lang.Thread.run(Thread.java:534) Caused by: org.apache.maven.continuum.execution.maven.m2.MavenBuilderHelper= Exception: Missing 'scm' element in the POM. =09at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelp= er.getMavenProject(DefaultMavenBuilderHelper.java:203) =09at org.apache.maven.continuum.execution.maven.m2.DefaultMavenBuilderHelp= er.mapMetadataToProject(DefaultMavenBuilderHelper.java:77) =09at org.apache.maven.continuum.execution.maven.m2.MavenTwoBuildExecutor.u= pdateProjectFromCheckOut(MavenTwoBuildExecutor.java:88) =09... 5 more -- I have to delete all projects and to re-add it. after, it works until the next server restart. -- 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] Closed: (CONTINUUM-312) M1 build adds a new BuildDefinition
[ http://jira.codehaus.org/browse/CONTINUUM-312?page=all ] Emmanuel Venisse closed CONTINUUM-312: -- Resolution: Fixed Fixed M1 build adds a new BuildDefinition --- Key: CONTINUUM-312 URL: http://jira.codehaus.org/browse/CONTINUUM-312 Project: Continuum Type: Bug Components: continuum-core Versions: 1.0-alpha-4 Environment: OSX 10.4.2, JDK 1.4.2 Reporter: Björn Sköld Assignee: Emmanuel Venisse Fix For: 1.0-alpha-4 Attachments: patch.txt Original Estimate: 1 hour Time Spent: 1 hour Remaining: 0 minutes Every time a M1-project is built, a newBuildDefinition (the default) is added. The Projectinfo page is full of them after a while. Only happens with M1, M2 works as expected. Happens with both forced and scheduled builds. A quick patch for MavenOneIntegrationTest that exposes the problem is attached. -- 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-301) Email notifications list wrong building machine
[ http://jira.codehaus.org/browse/CONTINUUM-301?page=comments#action_46445 ] Emmanuel Venisse commented on CONTINUUM-301: perhaps, your /etc/hosts file Email notifications list wrong building machine --- Key: CONTINUUM-301 URL: http://jira.codehaus.org/browse/CONTINUUM-301 Project: Continuum Type: Bug Reporter: Alan Cabrera Assignee: Emmanuel Venisse Fix For: 1.0-beta-1 Email notifications list wrong building machine. Build statistics: State: Failed Previous State: Failed Started at: Wed, 31 Aug 2005 09:14:40 -0700 Finished at: Wed, 31 Aug 2005 09:21:42 -0700 Total time: 7m 1s Forced: false Exit code: 70 Building machine hostname: localhost The host name is not localhost. -- 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] Closed: (CONTINUUM-314) Remove border for company logo
[ http://jira.codehaus.org/browse/CONTINUUM-314?page=all ] Emmanuel Venisse closed CONTINUUM-314: -- Assign To: Emmanuel Venisse Resolution: Fixed Fix Version: 1.0-beta-1 Applied. Thanks. Remove border for company logo -- Key: CONTINUUM-314 URL: http://jira.codehaus.org/browse/CONTINUUM-314 Project: Continuum Type: Wish Components: continuum-web Versions: 1.0-alpha-4 Reporter: Yann Le Du Assignee: Emmanuel Venisse Priority: Minor Fix For: 1.0-beta-1 Attachments: CONTINUUM-314.txt Patch attached -- 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] Updated: (CONTINUUM-315) Checkout/update impossible with empty cvs password
[ http://jira.codehaus.org/browse/CONTINUUM-315?page=all ] Emmanuel Venisse updated CONTINUUM-315: --- Assign To: Emmanuel Venisse Fix Version: 1.0-beta-1 Checkout/update impossible with empty cvs password --- Key: CONTINUUM-315 URL: http://jira.codehaus.org/browse/CONTINUUM-315 Project: Continuum Type: Bug Components: continuum-core Versions: 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 Assignee: Emmanuel Venisse Priority: Blocker Fix For: 1.0-beta-1 Using scm url : scm:cvs:pserver:anoncvs:@ip:/local/cvs/Repository:module with empty password for user anoncvs doesn't work. Build error in continuum : Exception: Cannot checkout sources. Exception while executing SCM command. password is required. -- 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] Updated: (CONTINUUM-315) Checkout/update impossible with empty cvs password
[ http://jira.codehaus.org/browse/CONTINUUM-315?page=all ] Emmanuel Venisse updated CONTINUUM-315: --- Remaining Estimate: 2 hours Original Estimate: 7200 Checkout/update impossible with empty cvs password --- Key: CONTINUUM-315 URL: http://jira.codehaus.org/browse/CONTINUUM-315 Project: Continuum Type: Bug Components: continuum-core Versions: 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 Assignee: Emmanuel Venisse Priority: Blocker Fix For: 1.0-beta-1 Original Estimate: 2 hours Remaining: 2 hours Using scm url : scm:cvs:pserver:anoncvs:@ip:/local/cvs/Repository:module with empty password for user anoncvs doesn't work. Build error in continuum : Exception: Cannot checkout sources. Exception while executing SCM command. password is required. -- 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] Updated: (CONTINUUM-125) Export/Import projects, configuration and history
[ http://jira.codehaus.org/browse/CONTINUUM-125?page=all ] Emmanuel Venisse updated CONTINUUM-125: --- Assign To: (was: Emmanuel Venisse) Fix Version: (was: 1.0-beta-1) 1.1-alpha-1 Export/Import projects, configuration and history - Key: CONTINUUM-125 URL: http://jira.codehaus.org/browse/CONTINUUM-125 Project: Continuum Type: Task Components: continuum-xmlrpc, continuum-core Reporter: Trygve Laugstol Fix For: 1.1-alpha-1 -- 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] Updated: (CONTINUUM-41) sort by different columns
[ http://jira.codehaus.org/browse/CONTINUUM-41?page=all ] Emmanuel Venisse updated CONTINUUM-41: -- Fix Version: (was: 1.0-beta-1) 1.0 Environment: sort by different columns - Key: CONTINUUM-41 URL: http://jira.codehaus.org/browse/CONTINUUM-41 Project: Continuum Type: New Feature Reporter: Brett Porter Priority: Trivial Fix For: 1.0 it would be nice to be able to sort by the various columns in the summary page, in particular so you can elevate failed projects to the top. -- 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] Updated: (CONTINUUM-34) Keep trying till build works, notify via email what is required
[ http://jira.codehaus.org/browse/CONTINUUM-34?page=all ] Emmanuel Venisse updated CONTINUUM-34: -- Description: I don't know if this is relevant to continuum's style of building, but I have a script that scm updates then builds an m1 project with the default, i.e. using just 'maven' with no goals supplied. This works the majority of time, but every once in a while someone refactors something and i need to do a clean build to really get everything to build. The idea: Have the concept of escalating the depth of the build till it works (or until you've tried everything). If you find one that works send an email that lists the exact steps (or maven command) required to get your build to work again. Example scenario 1: $ cvs update -dP $ maven BUILD FAILED $ maven clean default BUILD SUCCESSFUL (email sent suggesting people do a 'maven clean default' after updating) Example scenario 2: $ cvs update -dP $ maven BUILD FAILED $ maven clean default BUILD FAILED $ cvs co alanparsons $ cd alanparsons $ maven BUILD SUCCESSFUL (email sent suggesting people get a clean checkout of the alanparsons project before attempting to build) was: I don't know if this is relevant to continuum's style of building, but I have a script that scm updates then builds an m1 project with the default, i.e. using just 'maven' with no goals supplied. This works the majority of time, but every once in a while someone refactors something and i need to do a clean build to really get everything to build. The idea: Have the concept of escalating the depth of the build till it works (or until you've tried everything). If you find one that works send an email that lists the exact steps (or maven command) required to get your build to work again. Example scenario 1: $ cvs update -dP $ maven BUILD FAILED $ maven clean default BUILD SUCCESSFUL (email sent suggesting people do a 'maven clean default' after updating) Example scenario 2: $ cvs update -dP $ maven BUILD FAILED $ maven clean default BUILD FAILED $ cvs co alanparsons $ cd alanparsons $ maven BUILD SUCCESSFUL (email sent suggesting people get a clean checkout of the alanparsons project before attempting to build) Fix Version: (was: 1.0-beta-1) 1.0 Environment: Keep trying till build works, notify via email what is required --- Key: CONTINUUM-34 URL: http://jira.codehaus.org/browse/CONTINUUM-34 Project: Continuum Type: Wish Reporter: David Blevins Priority: Minor Fix For: 1.0 I don't know if this is relevant to continuum's style of building, but I have a script that scm updates then builds an m1 project with the default, i.e. using just 'maven' with no goals supplied. This works the majority of time, but every once in a while someone refactors something and i need to do a clean build to really get everything to build. The idea: Have the concept of escalating the depth of the build till it works (or until you've tried everything). If you find one that works send an email that lists the exact steps (or maven command) required to get your build to work again. Example scenario 1: $ cvs update -dP $ maven BUILD FAILED $ maven clean default BUILD SUCCESSFUL (email sent suggesting people do a 'maven clean default' after updating) Example scenario 2: $ cvs update -dP $ maven BUILD FAILED $ maven clean default BUILD FAILED $ cvs co alanparsons $ cd alanparsons $ maven BUILD SUCCESSFUL (email sent suggesting people get a clean checkout of the alanparsons project before attempting to build) -- 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] Updated: (CONTINUUM-58) Build all dependent projects.
[ http://jira.codehaus.org/browse/CONTINUUM-58?page=all ] Emmanuel Venisse updated CONTINUUM-58: -- Fix Version: (was: 1.0-beta-1) 1.0 Build all dependent projects. - Key: CONTINUUM-58 URL: http://jira.codehaus.org/browse/CONTINUUM-58 Project: Continuum Type: New Feature Reporter: Trygve Laugstol Fix For: 1.0 When building foo-core, foo-web and foo-xml-rpc should be built aswell to make sure that any changes to the core didn't break anything downstream. -- 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] Updated: (CONTINUUM-145) Allow the creation of template project configurations
[ http://jira.codehaus.org/browse/CONTINUUM-145?page=all ] Emmanuel Venisse updated CONTINUUM-145: --- Fix Version: (was: 1.0-beta-1) 1.0 Allow the creation of template project configurations - Key: CONTINUUM-145 URL: http://jira.codehaus.org/browse/CONTINUUM-145 Project: Continuum Type: New Feature Reporter: Jason van Zyl Fix For: 1.0 For a given project type, say m2, allow the user the define template values that will be used when new projects of that type are created. -- 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] Updated: (CONTINUUM-39) build in the correct order
[ http://jira.codehaus.org/browse/CONTINUUM-39?page=all ] Emmanuel Venisse updated CONTINUUM-39: -- Description: I'm unsure if this is already the case - it didn't appear to be. If a project is going to depend on the output of another scheduled continuum build (ie dependency id including version matches that of the other project's id), then they should be built in the correct order, as in the reactor. was: I'm unsure if this is already the case - it didn't appear to be. If a project is going to depend on the output of another scheduled continuum build (ie dependency id including version matches that of the other project's id), then they should be built in the correct order, as in the reactor. Fix Version: (was: 1.0-beta-1) 1.0 Environment: build in the correct order -- Key: CONTINUUM-39 URL: http://jira.codehaus.org/browse/CONTINUUM-39 Project: Continuum Type: Improvement Versions: 1.0-alpha-3 Reporter: Brett Porter Priority: Critical Fix For: 1.0 I'm unsure if this is already the case - it didn't appear to be. If a project is going to depend on the output of another scheduled continuum build (ie dependency id including version matches that of the other project's id), then they should be built in the correct order, as in the reactor. -- 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] Updated: (CONTINUUM-244) Create an m1 plugin that will add/update m1 projects in Continuum
[ http://jira.codehaus.org/browse/CONTINUUM-244?page=all ] Emmanuel Venisse updated CONTINUUM-244: --- Fix Version: (was: 1.0-beta-1) 1.0 Create an m1 plugin that will add/update m1 projects in Continuum - Key: CONTINUUM-244 URL: http://jira.codehaus.org/browse/CONTINUUM-244 Project: Continuum Type: New Feature Reporter: Jason van Zyl Fix For: 1.0 Trygve and I chatted and figured that this approach might be easier then trying to pull in all the m1 code to read m1 POMs inside Continuum. The m1 Continuum plugin could read all the necessary project information (taking into account, property interpolation and entities) and submit it to a Continuum instance using the SOAP interface. -- 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] Updated: (CONTINUUM-175) package continuum as a war
[ http://jira.codehaus.org/browse/CONTINUUM-175?page=all ] Emmanuel Venisse updated CONTINUUM-175: --- Fix Version: (was: 1.0-beta-1) 1.0 package continuum as a war -- Key: CONTINUUM-175 URL: http://jira.codehaus.org/browse/CONTINUUM-175 Project: Continuum Type: New Feature Components: continuum-web Reporter: Ryan Sonnek Fix For: 1.0 the current bundling of continuum with a web server is convenient, but for organizations that already have a webserver setup, a WAR file would be the most convenient. -- 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] Updated: (CONTINUUM-250) Continuum should not update SCM url for Maven1 projects.
[ http://jira.codehaus.org/browse/CONTINUUM-250?page=all ]
Emmanuel Venisse updated CONTINUUM-250:
---
Fix Version: (was: 1.0-beta-1)
1.0
Continuum should not update SCM url for Maven1 projects.
Key: CONTINUUM-250
URL: http://jira.codehaus.org/browse/CONTINUUM-250
Project: Continuum
Type: Bug
Components: continuum-core
Reporter: Tomasz Pik
Fix For: 1.0
I've some Maven1 projects with parametrized SCM urls, in form of
scm:cvs:pserver:${scm1.server}:/root/to/repo:module
They are correct for Maven1 - SCM plugin works with them very good.
Continuum do not handle them as there's no way to specify value for
${scm1.server} property (and I think it's OK).
Continnum loads evaluated project.xml (with ${scm1.server} replaced by
correct value) and starts building peoject but after checkout updates in
internals (ContinuumProject) value for SCM url with one from project.xml
so in next build SCM url is invalid.
As a resolution for this I'd like to propose:
1. add an option to import Maven1 project using SCM url only (and read rest
of properties from loaded POM) so user may provide evaluated version (this is
a good thing to be done in plugin for Maven1)
2. do not update ContiuumProject.scmURL based on POM;
--
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] Updated: (CONTINUUM-320) Trouble with bad entry in the cron's expression of a new schedule
[ http://jira.codehaus.org/browse/CONTINUUM-320?page=all ] Emmanuel Venisse updated CONTINUUM-320: --- Assign To: Emmanuel Venisse Version: 1.0-alpha-4 Fix Version: 1.0-beta-1 Trouble with bad entry in the cron's expression of a new schedule - Key: CONTINUUM-320 URL: http://jira.codehaus.org/browse/CONTINUUM-320 Project: Continuum Type: Bug Components: continuum-core Versions: 1.0-alpha-4 Reporter: Emmanuel Venisse Assignee: Emmanuel Venisse Fix For: 1.0-beta-1 Original Estimate: 10 minutes Time Spent: 10 minutes Remaining: 0 minutes From Olivier Lamy: I have encountered a trouble by setting a bad cron expression for a new scheduler : 0 0 0,4,8,12,16,20 * * * instead of 0 0 0,4,8,12,16,20 * * ? The continuum application fails and stop. Then it's was impossible to restart the application (always failed during the startup). The only solution to delete and install again the application. I found this issue http://jira.codehaus.org/browse/CONTINUUM-304. It's probably difficult to write an good validator. But is it possible to correctly catch the exception ? -- 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] Closed: (CONTINUUM-320) Trouble with bad entry in the cron's expression of a new schedule
[ http://jira.codehaus.org/browse/CONTINUUM-320?page=all ] Emmanuel Venisse closed CONTINUUM-320: -- Resolution: Fixed Fixed. Trouble with bad entry in the cron's expression of a new schedule - Key: CONTINUUM-320 URL: http://jira.codehaus.org/browse/CONTINUUM-320 Project: Continuum Type: Bug Components: continuum-core Versions: 1.0-alpha-4 Reporter: Emmanuel Venisse Assignee: Emmanuel Venisse Fix For: 1.0-beta-1 Original Estimate: 10 minutes Time Spent: 10 minutes Remaining: 0 minutes From Olivier Lamy: I have encountered a trouble by setting a bad cron expression for a new scheduler : 0 0 0,4,8,12,16,20 * * * instead of 0 0 0,4,8,12,16,20 * * ? The continuum application fails and stop. Then it's was impossible to restart the application (always failed during the startup). The only solution to delete and install again the application. I found this issue http://jira.codehaus.org/browse/CONTINUUM-304. It's probably difficult to write an good validator. But is it possible to correctly catch the exception ? -- 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-325) Refactor configurationService tor store conf in database instead of configuration.xml
Refactor configurationService tor store conf in database instead of configuration.xml - Key: CONTINUUM-325 URL: http://jira.codehaus.org/browse/CONTINUUM-325 Project: Continuum Type: Task Components: continuum-core Reporter: Emmanuel Venisse Assigned to: Emmanuel Venisse Fix For: 1.0-beta-1 -- 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] Closed: (CONTINUUM-326) Create an initialization page for setup the continuum configuration
[ http://jira.codehaus.org/browse/CONTINUUM-326?page=all ] Emmanuel Venisse closed CONTINUUM-326: -- Resolution: Fixed Done. Create an initialization page for setup the continuum configuration --- Key: CONTINUUM-326 URL: http://jira.codehaus.org/browse/CONTINUUM-326 Project: Continuum Type: New Feature Components: continuum-web Reporter: Emmanuel Venisse Assignee: Emmanuel Venisse Fix For: 1.0-beta-1 -- 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-328) Cannot build continuum from scratch
[ http://jira.codehaus.org/browse/CONTINUUM-328?page=comments#action_47618 ] Emmanuel Venisse commented on CONTINUUM-328: jdbc jars come from transitive dependencies, we need to fix poms in repo for use only one name jaas come from a transitive dependency but we can exclude it in continuum Cannot build continuum from scratch --- Key: CONTINUUM-328 URL: http://jira.codehaus.org/browse/CONTINUUM-328 Project: Continuum Type: Bug Environment: continuum trunk 2005-10-01 + jdk 1.4.2 + maven 2 built from trunk Reporter: Arnaud Heritier I'm trying to build continuum for the first time (to try to see why the alpha4 and the last snapshot doesn't start on windows - same problem as emmanuel with the command line length) and I receive this error : [INFO] [INFO] Building Continuum Plexus Application [INFO]task-segment: [clean:clean, install] [INFO] [INFO] [clean:clean] [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Diagnosis: DEPRECATED: Mapped-prefix lookup of mojos are only supported from direct invocation. Please use specification of the form groupId:artifactId[: version]:goal instead. (Offending mojo: 'plexus:app', invoked via: 'install') [INFO] [INFO] [ERROR] FATAL ERROR [INFO] FATAL ERROR: Error executing Maven for a project Error stacktrace: org.apache.maven.reactor.ReactorException: Error executing project within the reactor at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:282) at org.apache.maven.cli.MavenCli.main(MavenCli.java:237) 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:324) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.lifecycle.LifecycleExecutionException: DEPRECATED: Mapped-prefix lookup of mojos are only supported from direct invocation. Please u se specification of the form groupId:artifactId[:version]:goal instead. (Offending mojo: 'plexus:app', invoked via: 'install') at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1154) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:831) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:798) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:298) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:152) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:217) ... 9 more I don't know if it's a problem with m2 or continuum. Some others questions : - Why do we need to have a jar called jdbc-2.0 and another called jdbc-ext-2.0. It seems that they are the same one. - Why do we need to download the jass 1.0 API which is bundle in jdk 1.4 (pre-requisite for continuum) ? -- 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] Closed: (CONTINUUM-328) Cannot build continuum from scratch
[ http://jira.codehaus.org/browse/CONTINUUM-328?page=all ] Emmanuel Venisse closed CONTINUUM-328: -- Assign To: Brett Porter Resolution: Fixed Fix Version: 1.0-beta-1 Fixed by brett Cannot build continuum from scratch --- Key: CONTINUUM-328 URL: http://jira.codehaus.org/browse/CONTINUUM-328 Project: Continuum Type: Bug Environment: continuum trunk 2005-10-01 + jdk 1.4.2 + maven 2 built from trunk Reporter: Arnaud Heritier Assignee: Brett Porter Fix For: 1.0-beta-1 I'm trying to build continuum for the first time (to try to see why the alpha4 and the last snapshot doesn't start on windows - same problem as emmanuel with the command line length) and I receive this error : [INFO] [INFO] Building Continuum Plexus Application [INFO]task-segment: [clean:clean, install] [INFO] [INFO] [clean:clean] [INFO] [ERROR] FATAL ERROR [INFO] [INFO] Diagnosis: DEPRECATED: Mapped-prefix lookup of mojos are only supported from direct invocation. Please use specification of the form groupId:artifactId[: version]:goal instead. (Offending mojo: 'plexus:app', invoked via: 'install') [INFO] [INFO] [ERROR] FATAL ERROR [INFO] FATAL ERROR: Error executing Maven for a project Error stacktrace: org.apache.maven.reactor.ReactorException: Error executing project within the reactor at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:282) at org.apache.maven.cli.MavenCli.main(MavenCli.java:237) 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:324) at org.codehaus.classworlds.Launcher.launchEnhanced(Launcher.java:315) at org.codehaus.classworlds.Launcher.launch(Launcher.java:255) at org.codehaus.classworlds.Launcher.mainWithExitCode(Launcher.java:430) at org.codehaus.classworlds.Launcher.main(Launcher.java:375) Caused by: org.apache.maven.lifecycle.LifecycleExecutionException: DEPRECATED: Mapped-prefix lookup of mojos are only supported from direct invocation. Please u se specification of the form groupId:artifactId[:version]:goal instead. (Offending mojo: 'plexus:app', invoked via: 'install') at org.apache.maven.lifecycle.DefaultLifecycleExecutor.getMojoDescriptor(DefaultLifecycleExecutor.java:1154) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.bindLifecycleForPackaging(DefaultLifecycleExecutor.java:831) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.constructLifecycleMappings(DefaultLifecycleExecutor.java:798) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeGoal(DefaultLifecycleExecutor.java:475) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.executeTaskSegments(DefaultLifecycleExecutor.java:298) at org.apache.maven.lifecycle.DefaultLifecycleExecutor.execute(DefaultLifecycleExecutor.java:152) at org.apache.maven.DefaultMaven.execute(DefaultMaven.java:217) ... 9 more I don't know if it's a problem with m2 or continuum. Some others questions : - Why do we need to have a jar called jdbc-2.0 and another called jdbc-ext-2.0. It seems that they are the same one. - Why do we need to download the jass 1.0 API which is bundle in jdk 1.4 (pre-requisite for continuum) ? -- 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] Closed: (CONTINUUM-318) Maven 2 build fails with a derby jdbc truncation error on a long scm connection string
[ http://jira.codehaus.org/browse/CONTINUUM-318?page=all ] Emmanuel Venisse closed CONTINUUM-318: -- Resolution: Fixed Fix Version: (was: 1.0-beta-2) 1.0-beta-1 I updated db schema for all possible long string Maven 2 build fails with a derby jdbc truncation error on a long scm connection string -- Key: CONTINUUM-318 URL: http://jira.codehaus.org/browse/CONTINUUM-318 Project: Continuum Type: Bug Versions: 1.0-alpha-4 Reporter: Cédric Vidal Assignee: Emmanuel Venisse Priority: Blocker Fix For: 1.0-beta-1 Attachments: wrapper.log Original Estimate: 30 minutes Remaining: 30 minutes It might be caused by a quite long subversion scm connection string: scm:svn:https://[EMAIL PROTECTED]/repos/proxiad/Socle/Passage%20%c3%a0%20Maven%202%20et%20WTP/Tentative%20de%20projets%20Maven%202%20sous%20Eclipse%20WTP%200.7 I have attached the full wrapper.log for the following scenario: start continuum, trigger build manually, stop continuum. The pom's scm configuration is as follows: scm connectionscm:svn:https://[EMAIL PROTECTED]/repos/proxiad/Socle/Passage%20%c3%a0%20Maven%202%20et%20WTP/Tentative%20de%20projets%20Maven%202%20sous%20Eclipse%20WTP%200.7/connection /scm -- 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] Updated: (CONTINUUM-272) add installation configuration to white site
[ http://jira.codehaus.org/browse/CONTINUUM-272?page=all ] Emmanuel Venisse updated CONTINUUM-272: --- Fix Version: (was: 1.0-beta-1) 1.0-beta-2 add installation configuration to white site Key: CONTINUUM-272 URL: http://jira.codehaus.org/browse/CONTINUUM-272 Project: Continuum Type: Sub-task Reporter: Brett Porter Fix For: 1.0-beta-2 -- 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] Updated: (CONTINUUM-273) implement screens for installation configuration
[ http://jira.codehaus.org/browse/CONTINUUM-273?page=all ] Emmanuel Venisse updated CONTINUUM-273: --- Fix Version: (was: 1.0-beta-1) 1.0-beta-2 implement screens for installation configuration Key: CONTINUUM-273 URL: http://jira.codehaus.org/browse/CONTINUUM-273 Project: Continuum Type: Sub-task Components: continuum-web Reporter: Brett Porter Fix For: 1.0-beta-2 -- 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] Updated: (CONTINUUM-278) associate project developers with continuum users
[ http://jira.codehaus.org/browse/CONTINUUM-278?page=all ] Emmanuel Venisse updated CONTINUUM-278: --- Fix Version: (was: 1.0-beta-1) 1.0-beta-2 associate project developers with continuum users - Key: CONTINUUM-278 URL: http://jira.codehaus.org/browse/CONTINUUM-278 Project: Continuum Type: Sub-task Reporter: Brett Porter Fix For: 1.0-beta-2 -- 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] Updated: (CONTINUUM-289) implement per group notifier handling
[ http://jira.codehaus.org/browse/CONTINUUM-289?page=all ] Emmanuel Venisse updated CONTINUUM-289: --- Fix Version: (was: 1.0-beta-1) 1.1 implement per group notifier handling - Key: CONTINUUM-289 URL: http://jira.codehaus.org/browse/CONTINUUM-289 Project: Continuum Type: New Feature Reporter: Brett Porter Fix For: 1.1 -- 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] Updated: (CONTINUUM-283) complete outstanding design for front page
[ http://jira.codehaus.org/browse/CONTINUUM-283?page=all ] Emmanuel Venisse updated CONTINUUM-283: --- Fix Version: (was: 1.0-beta-1) 1.1 complete outstanding design for front page -- Key: CONTINUUM-283 URL: http://jira.codehaus.org/browse/CONTINUUM-283 Project: Continuum Type: Sub-task Reporter: Brett Porter Fix For: 1.1 -- 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] Updated: (CONTINUUM-284) group display on front page
[ http://jira.codehaus.org/browse/CONTINUUM-284?page=all ] Emmanuel Venisse updated CONTINUUM-284: --- Fix Version: (was: 1.0-beta-1) 1.1 group display on front page --- Key: CONTINUUM-284 URL: http://jira.codehaus.org/browse/CONTINUUM-284 Project: Continuum Type: Sub-task Reporter: Brett Porter Fix For: 1.1 -- 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] Updated: (CONTINUUM-291) implement per project developer management
[ http://jira.codehaus.org/browse/CONTINUUM-291?page=all ] Emmanuel Venisse updated CONTINUUM-291: --- Fix Version: (was: 1.0-beta-1) 1.1 implement per project developer management -- Key: CONTINUUM-291 URL: http://jira.codehaus.org/browse/CONTINUUM-291 Project: Continuum Type: New Feature Reporter: Brett Porter Fix For: 1.1 -- 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] Updated: (CONTINUUM-292) implement group summary page
[ http://jira.codehaus.org/browse/CONTINUUM-292?page=all ] Emmanuel Venisse updated CONTINUUM-292: --- Fix Version: (was: 1.0-beta-1) 1.1 implement group summary page Key: CONTINUUM-292 URL: http://jira.codehaus.org/browse/CONTINUUM-292 Project: Continuum Type: New Feature Reporter: Brett Porter Fix For: 1.1 http://people.apache.org/~brett/white-site/viewGroup.html -- 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] Updated: (CONTINUUM-30) Project grouping features
[ http://jira.codehaus.org/browse/CONTINUUM-30?page=all ] Emmanuel Venisse updated CONTINUUM-30: -- Fix Version: (was: 1.0-beta-1) 1.1 Environment: Project grouping features - Key: CONTINUUM-30 URL: http://jira.codehaus.org/browse/CONTINUUM-30 Project: Continuum Type: New Feature Versions: 1.0-alpha-3 Reporter: Jason van Zyl Fix For: 1.1 It would be nice to start incorporating some functionality based on groupIds. Sorting by groupId, or a separate page for projects with the same groupId, or reports for a whole groupId. Say a summary failure report with links to details instead of 10 different emails. -- 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] Updated: (CONTINUUM-44) multiple profiles
[ http://jira.codehaus.org/browse/CONTINUUM-44?page=all ] Emmanuel Venisse updated CONTINUUM-44: -- Fix Version: (was: 1.0-beta-1) 1.0-beta-2 multiple profiles - Key: CONTINUUM-44 URL: http://jira.codehaus.org/browse/CONTINUUM-44 Project: Continuum Type: New Feature Reporter: Brett Porter Fix For: 1.0-beta-2 would like to be able to define a profile (which can include certain environmental things such as the version of m2 to use, the JDK version, etc). Profiles should be able to be used globally, per group or per project. In this way, you could build certain projects under a variety of different JDKs for example. -- 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] Updated: (CONTINUUM-140) Allow the use of the CC in the web UI
[ http://jira.codehaus.org/browse/CONTINUUM-140?page=all ] Emmanuel Venisse updated CONTINUUM-140: --- Fix Version: (was: 1.0-beta-1) 1.0-beta-2 Environment: Allow the use of the CC in the web UI - Key: CONTINUUM-140 URL: http://jira.codehaus.org/browse/CONTINUUM-140 Project: Continuum Type: New Feature Versions: 1.0-alpha-4 Reporter: Jason van Zyl Fix For: 1.0-beta-2 This will require some changes in the UI to make this work but we can assess in alpha-3 -- 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] Updated: (CONTINUUM-247) Add a scm password field for don't define it in scm url
[ http://jira.codehaus.org/browse/CONTINUUM-247?page=all ] Emmanuel Venisse updated CONTINUUM-247: --- Fix Version: (was: 1.0-beta-1) 1.1 Add a scm password field for don't define it in scm url --- Key: CONTINUUM-247 URL: http://jira.codehaus.org/browse/CONTINUUM-247 Project: Continuum Type: Improvement Components: continuum-web, continuum-core Versions: 1.0-alpha-4 Reporter: Emmanuel Venisse Fix For: 1.1 -- 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] Updated: (CONTINUUM-264) Keep trying after scm failed updating
[ http://jira.codehaus.org/browse/CONTINUUM-264?page=all ] Emmanuel Venisse updated CONTINUUM-264: --- Fix Version: (was: 1.0-beta-1) 1.0-beta-2 Keep trying after scm failed updating - Key: CONTINUUM-264 URL: http://jira.codehaus.org/browse/CONTINUUM-264 Project: Continuum Type: Improvement Components: continuum-core Versions: 1.0-alpha-3 Environment: linux, sun jdk 1.4 (not important) Reporter: Torsten Curdt Fix For: 1.0-beta-2 Currently a failed update from the scm and a broken build are being treated the same. IMO it would be better just to set a warning state for that project and retry building with the next trigger. Whether the warning emits an email or not should be configurable. -- 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] Updated: (CONTINUUM-329) Can't start continuum
[ http://jira.codehaus.org/browse/CONTINUUM-329?page=all ] Emmanuel Venisse updated CONTINUUM-329: --- Fix Version: (was: 1.0-beta-1) 1.0-beta-2 Can't start continuum - Key: CONTINUUM-329 URL: http://jira.codehaus.org/browse/CONTINUUM-329 Project: Continuum Type: Bug Versions: 1.0-alpha-4 Environment: tested with 1.0-alpha-4 and a daily snapshot Win XP JDK 1.4.2 Reporter: Arnaud Heritier Fix For: 1.0-beta-2 Attachments: CONTINUUM-329.log When I launch plexus.bat I receive the error : C:\Programs\dev\continuum-1.0-alpha-4\binplexus.bat Usage: java [-options] class [args...] (to execute a class) or java [-options] -jar jarfile [args...] (to execute a jar file) I attached the full log with echo enabled. My problem comes from the fact that my path ends with a \ : -Dplexus.system.path=C:\Programs\dev\php-4.3;C:\Programs\dev\svn\bin;C:\Programs\db\oracle\ora92\bin;C:\Programs\web\PuTTY;C:\Programs\dev\j2sdk1.4.2\BIN;C:\Programs\dev\apache-maven-dev\BIN;C:\Programs\dev\apache-ant-1.6.5\BIN;C:\Programs\dev\WinCvs1.3\CVSNT;C:\WINDOWS\SYSTEM32;C:\WINDOWS;C:\WINDOWS\SYSTEM32\WBEM;C:\PROGRAMS\DEV\TCL\BIN;C:\PROGRAMS\DEV\PYTHON23\.;C:\Program Files\Fichiers communs\Roxio Shared\DLLShared;C:\Program Files\Bureautique\UltraEdit;C:\Programs\dev\WinCvs1.3\CVSNT;C:\Program Files\System\Support Tools;C:\Program Files\Support Tools\;;C:\Programs\dev\maven-2\bin;C:\Programs\dev\TortoiseSVN\bin;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\Fichiers communs\Adobe\AGL;C:\Program Files\ATI Technologies\ATI.ACE\ If I change my path with : -Dplexus.system.path=C:\Programs\dev\php-4.3;C:\Programs\dev\svn\bin;C:\Programs\db\oracle\ora92\bin;C:\Programs\web\PuTTY;C:\Programs\dev\j2sdk1.4.2\BIN;C:\Programs\dev\apache-maven-dev\BIN;C:\Programs\dev\apache-ant-1.6.5\BIN;C:\Programs\dev\WinCvs1.3\CVSNT;C:\WINDOWS\SYSTEM32;C:\WINDOWS;C:\WINDOWS\SYSTEM32\WBEM;C:\PROGRAMS\DEV\TCL\BIN;C:\PROGRAMS\DEV\PYTHON23\.;C:\Program Files\Fichiers communs\Roxio Shared\DLLShared;C:\Program Files\Bureautique\UltraEdit;C:\Programs\dev\WinCvs1.3\CVSNT;C:\Program Files\System\Support Tools;C:\Program Files\Support Tools\;;C:\Programs\dev\maven-2\bin;C:\Programs\dev\TortoiseSVN\bin;C:\Program Files\ATI Technologies\ATI Control Panel;C:\Program Files\Fichiers communs\Adobe\AGL;C:\Program Files\ATI Technologies\ATI.ACE It works. To prevent this you can add do something like : -Dplexus.system.path=%PATH%;. -- 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] Updated: (CONTINUUM-309) add junit results report to website, failures to email
[ http://jira.codehaus.org/browse/CONTINUUM-309?page=all ] Emmanuel Venisse updated CONTINUUM-309: --- Fix Version: (was: 1.0-beta-1) 1.1 add junit results report to website, failures to email -- Key: CONTINUUM-309 URL: http://jira.codehaus.org/browse/CONTINUUM-309 Project: Continuum Type: New Feature Reporter: Brett Porter Fix For: 1.1 -- 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-264) Keep trying after scm failed updating
[ http://jira.codehaus.org/browse/CONTINUUM-264?page=comments#action_47757 ] Emmanuel Venisse commented on CONTINUUM-264: Need to check if it's fixed. Keep trying after scm failed updating - Key: CONTINUUM-264 URL: http://jira.codehaus.org/browse/CONTINUUM-264 Project: Continuum Type: Improvement Components: continuum-core Versions: 1.0-alpha-3 Environment: linux, sun jdk 1.4 (not important) Reporter: Torsten Curdt Fix For: 1.0-beta-2 Currently a failed update from the scm and a broken build are being treated the same. IMO it would be better just to set a warning state for that project and retry building with the next trigger. Whether the warning emits an email or not should be configurable. -- 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] Updated: (CONTINUUM-288) integrate per-project notifier handling
[ http://jira.codehaus.org/browse/CONTINUUM-288?page=all ] Emmanuel Venisse updated CONTINUUM-288: --- Fix Version: (was: 1.0-beta-1) 1.0-beta-2 integrate per-project notifier handling --- Key: CONTINUUM-288 URL: http://jira.codehaus.org/browse/CONTINUUM-288 Project: Continuum Type: New Feature Reporter: Brett Porter Fix For: 1.0-beta-2 -- 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] Updated: (CONTINUUM-175) package continuum as a war
[ http://jira.codehaus.org/browse/CONTINUUM-175?page=all ] Emmanuel Venisse updated CONTINUUM-175: --- Fix Version: (was: 1.0-beta-2) 1.1 package continuum as a war -- Key: CONTINUUM-175 URL: http://jira.codehaus.org/browse/CONTINUUM-175 Project: Continuum Type: New Feature Components: continuum-web Reporter: Ryan Sonnek Fix For: 1.1 the current bundling of continuum with a web server is convenient, but for organizations that already have a webserver setup, a WAR file would be the most convenient. -- 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] Updated: (CONTINUUM-143) We need to categorize error states and display them useful messages to the user
[ http://jira.codehaus.org/browse/CONTINUUM-143?page=all ] Emmanuel Venisse updated CONTINUUM-143: --- Fix Version: (was: 1.0-beta-2) 1.1 Environment: We need to categorize error states and display them useful messages to the user --- Key: CONTINUUM-143 URL: http://jira.codehaus.org/browse/CONTINUUM-143 Project: Continuum Type: Improvement Versions: 1.0-alpha-3 Reporter: Jason van Zyl Fix For: 1.1 Right now we're only tracking checkout errors but we need to categorize all error so that we can easily extract them and display useful messages to the user. -- 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
