Re: [Discussion] Continuum 2.0 Roadmap
Maria Odea Ching wrote: Anyway, +1 on the things in the wiki. All the ideas are exciting :) As what have been mentioned already in the thread, I agree that it would be easier and more manageable to implement these plans in milestones not just in one blow. Smaller iterations and more frequent releases is a very good idea. If the transition from 1.0.3 to 1.1 had been done in smaller iterations I think Continuum would have been a lot more popular today than it is now. (Frequent releases seem to be one of the things that attract people to Hudson...) And if Continuum will be switching databases, I'd go with JPA. Comparing my experience in using JPA and JPOX, I'd say that it has been more pleasant with JPA. I also think switching from Plexus to a different framework would attract more contributors as a lot of people outside the Maven community aren't really very familiar on how to use Plexus. If I could choose between Jpox and JPA and Plexus and Spring, I'd chosen JPA and Spring in a heartbeat. However, if you haven't got any really _need_ for functionality only provided by JPA or Spring/whatever, the value added to Continuum compared to the cost of implementation is not worth it IMHO. I also want to address the wish to "attract more contributors". As some of you might know, I have developed an extension to Continuum that I now call Backward Compatibility Tester [1]. I thus feel that I can give feedback with regards to how it is to start developing on Continuum. IMHO the most serious showstoppers are 1. I'm unable to run tests that extend AbstractContinuumTest in my IDE (IntelliJ) 2. I'm unable to run tests that extend AbstractContinuumTest in my IDE (IntelliJ) 3. I'm unable to run tests that extend AbstractContinuumTest in my IDE (IntelliJ) 4. Lack of documentation. E.g., I haven't found a single design diagram/description that explains how the 30~ modules interact... 5. There are 30 or so modules in the same maven project. 5.1 The build is horribly slow (6min 28secs on a Intel Core2 6300 CPU @ 1.86GHz with 2GB ram). 5.2 It is hard to grasp the underlaying architecture. 5.3. Are really all these modules needed to check out some code from a repository and run mvn clean install? Yes, I try to suggest that some of the functionality should be moved to separate projects. Perhaps a plugin-based architecture is the solution, but I think much can be achieved by refactoring to a smaller set of libraries that different products can use. (This might be a first step towards Continuum with distributed builds.) Perhaps continuum-model, continuum-xmlrpc or maven-continuum-plugin can be split out to separate maven projects? 6. JPOX is buggy, hard to debug and difficult to work with. [1] https://bct.dev.java.net/ (only a prototype, not production ready) -- Regards Erik Drolshammer Sherriff @ #continuum and #maven
Re: JUnit tests in intellij
LAMY Olivier wrote: I don't know how does it work on IntelliJ but on eclipse I had in my junit configuration this directory continuum-model/target/classes in the junit classpath. This directory includes META-INF/package.jdo. Didn't work unfortunately. Any other tips? Is anyone using INtelliJ sucessfully at all? -- Thanks, Erik Drolshammer
Re: PoC to show new feature
Hi! I plan to write the further work section of my thesis within the next couple of days. If anyone have any comments on my todo list, I would really appreciate to hear them. The report can still be found at http://folk.ntnu.no/drolsham/temp/report-snapshot.pdf, if anyone is interested. -- Regards Erik Drolshammer
PoC to show new feature
Hi! I have written a PoC to illustrate the concept we have discussed earlier (search for thread with topic "Does this feature already exist?"). The PoC works for add/remove projects, but don't support add/remove depencies in the pom or in the list of derived dependencies. I must work on my report now, so I haven't planned any more programming before delivery. As it is, it's pretty useless, but I can work more on it later, if the community is interested. A rough todo list would then be: * Port the PoC to trunk or continuum-1.1-alpha. * Implement update (i.e., add and remove dependencies from pom.xml) * Add reference to original project in the derived projects * Add reference to original dependency in the derived dependencies * Read derived dependencies from xml-file (enable/disable in xml-file). (log4j:log4j:1.2.14, commons-logging:commons-logging:1.1 and jmock:jmock:1.1.0 are now set as derived dependencies) * Remove all java 1.5 syntax to conform with java 1.4 syntax * GUI: tree structure (click to maximize and show the derived projects) + clean up the code and proper tests Comments? Is tool support for the concept useful? Given proper code, syntax, etc. is it probable that it would be accepted into continuum? Links: PoC src-code: http://svn.fjas.no/continuum-1.0.3-ed/ TestProject: http://svn.fjas.no/test/modularTestProject/ Report: http://folk.ntnu.no/drolsham/temp/report-snapshot.pdf -- Erik Drolshammer
Strange behaviour
Hi!
My PoC-extension to Continuum is nearly finished, but I have come across
a couple of weird problems:
1.
The state icon (success, error, etc.) on the frontpage (Summary.vm) does
not correspond to the state logged and the state shown in the detailed
view (ProjectBuild.vm). I.e., error is displayed while the build is
successful.
Anyone care to guess how I have accomplished that?
Is the following log message related?
2007-04-11 14:15:07,639 [SocketListener0-0] ERROR VelocityComponent
- RHS of #set statement is null. Context will not be modified.
screens/ProjectBuild.vm [line 103, column 3]
This odd behaviour is only true for my original projects, not the
derived projects.
2.
projectsList = getProjectsInBuildOrder(); (DefaultContinuum.java)
which calls getAllProjectsByNameWithDependencies()
only returns original projects, not derived projects, causing the "Build
all" button to only build original projects.
("Build Now" on each derived project works fine.)
I'm unsure if it is related, but all derived projects have the same
projectGroup as the original project.
(And I have verified that all projects are successfully persisted.)
--
Kindly regards
Erik Drolshammer
Re: Write access to wiki - attachment as link
Erik Drolshammer wrote: Erik Drolshammer wrote: See attachment for a rough draft of the conceptual solution. And attachments was obviously filtered; http://www.idi.ntnu.no/~drolsham/temp/concept.pdf Good night! -- Regards Erik
Re: Write access to wiki - attachment
Erik Drolshammer wrote: Se attachment for a rough draft of the conceptual solution. -- Regards Erik
Re: Write access to wiki
Jesse McConnell wrote: you might more active feedback if you just correspond with the mailing list like this, at least in my opinion.. Yes, Trygve said so as well. I planned to use email for questions and the wiki for more in-depth information and pictures. as for the wiki access, that might be possible, what kinda stuff will you be adding there? information specific to your implementation? where would that implementation be located? are you just going to create and maintain a patchset on continuum trunk? inquiring minds want to know! :) The idea was to post some background information on the concept and some dependency graphs. I would also like to discuss implementation specific details. All in all it would be nice to use the wiki as means of communication to supplement email. anyway, I for one am interested in some more information on your thesis, the sentence you provide sounds like it is already a feature of continuum If so I will feel pretty stupid :P Se attachment for a rough draft of the conceptual solution. -- Regards Erik
Write access to wiki
Hi! I'm writing a proof of concept (PoC) implementation as my master thesis which extends Continuum. Problem text: "The purpose of this Master thesis is to improve existing techniques for Continuous Integration. The focus is on determining whether a new version of a module breaks the build of old clients or builds successfully. One possible approach is to continuously integrate the clients with the new implementation. The task is to write a PoC implementation using Continuum as the underlaying build engine." I have Trygve Laugstøl as my counselor and he suggested that I try to report on my progress on the wiki and hopefully obtain some feedback from the active developers. Can I get write access to your wiki? It looks like my project is related to an existing wiki page [1], but perhaps it is simpler to start a new page? [1] http://docs.codehaus.org/display/CONTINUUM/Triggering+a+build+if+dependencies+are+changed -- Regards Erik Drolshammer, username Sherriff
Dependency and ProjectDependency
Hi! I'm looking at the 1.0.3 code and I have a few questions; 1. Where can I find Dependency.java? (Is it generated? How?) 2. What is the difference between Dependency and ProjectDependency? Where and how are the two classes used? 3. Is there any documentation of the data models available? (I'm trying to add some reporting-plugins, but without great success so far. I think it is just Maven technical problems so I'll keep at it a bit more.) Thanks in advance, -- Erik Drolshammer
