JDO api's 1.3 in central.
Hi. I'm not sure where to find this, but whoever's maintaining javax.jdo has uploaded this: javax.jdo:jdo2-api:jar:2.3-20090302111651 There are two problems - firstly, it doesn't have CRC/hash files. Secondly, it looks like it was a snapshot that was released. It does worry me a little, especially since it's an API/spec. How do we find out who's maintaining the maven metadata for this? (no contributor/ developer tags that I could find.) cheers, Christian Edward Gruber christianedwardgru...@gmail.com http://www.geekinasuit.com/ - To unsubscribe, e-mail: users-unsubscr...@maven.apache.org For additional commands, e-mail: users-h...@maven.apache.org
Presentation at Agile2008
Hey all, I'll be giving a presentation at Agile2008 next week called: "Maven and Continuum - an infrastructure for reducing cycle-time in Agile and Lean development." I wanted to drop the basic outline here and make sure there isn't anything that "absolutely must be talked about". It's a tutorial, so it's going to involve the theory, but will also get into real examples of setting up projects, modules/ parents, plugins, and site reports. I'll mention Hudson/Cruise- control, and others, and Nexus and Archiva will also be mentioned, but I have doubts as to whether any of that will be covered. Anyway, let me know if there's anything off this list that strikes you as needing to be on it. It's a 3 hour tutorial, and when I timed this material, I found it quite hard to fit it in, especially with Q&A. Cheers, Christian. P.S. Please don't spam the users lists with replies - reply to me, unless there's a genuine topic in your comment. I'm looking for suggestions, not to put a lot of extra traffic onto these lists. Thanks. -cg. Introduction Discussion of build environments, and their effects on developer efficiency, quality, etc. Part 1 - Apache Maven2 Basic Introduction Dependency Management Modules and Recursive Builds Eclipse IDE integration Q&A Part 2 - Apache Maven2 Reports “Site” plugin Project Metadata Almost Plain Text Developer Reports Additional Documentation Q&A Break Part 3 - Apache Continuum 1.1 Introduction to Apache Continuum Basic Setup Adding projects Schedules and Build Definitions Q&A Part 4 - Advanced Topics non-java builds (native, .NET) integration test strategies maven ant tasks software release process More Q&A if desired - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Renaming an artifact...
Hey, I was looking for examples of the following, or instructions. I have a plugin (maven-flex2-plugin) that really should be called (maven- flex-plugin), since it can run flex2 or flex3. I'd like to rename the artifactId, but somehow have the original there redirecting to the new artifact. I seem to recall there was some metadata that I could use to do this, but cannot for the life of me find an example. Any clues? Christian. - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Release a multi modules project using Continuum
If the company superpom is not in a repository that your continuum server or the user under which that server runs (via settings.xml) knows about, then it will not find it. One solution is to import the superpom separately and build it within continuum, because then it will be in the local repository for the user executing continuum. Christian. On 18-Feb-08, at 11:19 , bfontaine wrote: Hello ; I'm currently try to get the continuum's release button to work for my project. My project is a multi-module project with this kind of structure : projectRoot -pom.xml -subProjectMain -- subProjectMain files -- pom.xml - subProjectDependency -- subProjectDependency files -- pom.xml ... and so on Every subProject pom inherit of the projectRoot pom, which, himself, inherit of my compagny superpom. When I execute the release:prepare goal with maven, everything works just fine. But when I'm trying to use continuum, I get an error at the second step of the process (generate-reactor-projects). I copied the stacktrace in the error.txt file http://www.nabble.com/file/p15546915/Error.txt Error.txt Obviously, maven can't find my compagny superpom. I would like to know if there is a way to configure the release plugin of Continuum so that my release would work. -- View this message in context: http://www.nabble.com/Release-a-multi-modules-project-using-Continuum-tp15546915p15546915.html Sent from the Continuum - Users mailing list archive at Nabble.com.
Re: [ANNOUNCE] Good news! Maven 2 talk accepted at JavaOne 2008
No, but I will be submitting a talk about build systems (using Maven2 as the implementation) and their effect on architecture and process change efforts at Agile2008. regards, Christian. On 6-Feb-08, at 09:30 , Jim Bethancourt wrote: Hi everyone, I found out last week that my presentation proposal, "Migrating to Maven 2 Demystified", was accepted for presentation at this year's JavaOne. In the presentation, I will be showing how to Mavenize Google's Guice framework one step at a time, while being minimally invasive to the codebase as possible. It will be useful to folks curious about Maven 2 but on the fence because of the migration process, or who want to learn about how to manage multi-module builds that leverage the reactor. I don't know the exact date and time yet, but I will gladly post this information so it can be included on the Apache Maven website. If anyone has tips on how you have found explaining Maven 2 to be most effective, I most definitely welcome them. :-) Is anyone else presenting on Maven 2 this year at JavaOne? Cheers, Jim - To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
Re: Problem to use 2 projects (trunk and branch) in the same continuum
Typically, one would have branches have a different version. For
example, trunk would be on 2.0-SNAPSHOT, but the 1.x branch would be
on 1.2-SNAPSHOT. A lot of this depends on one's branching strategy.
If you use branches for teams or experimental features, then I would
build a branch portion into your versions. A short code at the
beginning of the branch version.
1.0-SNAPSHOT (trunk)
1.0-TEAM1-SNAPSHOT
1.0-TEAM2-SNAPSHOT
or
1.0-SNAPSHOT (trunk)
TEAM1-1.0-SNAPSHOT
TEAM2-1.0-SNAPSHOT
The above is a problematic strategy for branching, but it is used, and
this way you have everything nicely separated. At some points, where
we had non-version-oriented branching (experimental branches) we had a
property set in the active parent (the one that all things got their
versions from) that defined the version for itself and all children.
...
${providedversion}
...
1.0-SNAPSHOT
and then we changed it into EXP-BLAH-1.0-SNAPSHOTprovidedversion> for the experimental work that didn't follow our
"branch for maintenance" strategy.
Christian.
On 23-Jan-08, at 11:40 , Emmanuel Venisse wrote:
You must use a different version for your projects.
An uniq id for a project is groupId+artifactId+version
Emmanuel
On Jan 23, 2008 4:24 PM, Claudio Ranieri <[EMAIL PROTECTED]>
wrote:
Hi,
I added 2 M2_projects in continuum. The trunk version and branch
version
of the one project.
But the continuum only detect changes in the branch version. The
continuum
doesn´t detect changes in trunk version.
I saw the continuum log and I got:
12646035 [defaultScheduler_Worker-11] WARN
org.apache.maven.continuum.Continuum:default - Project
'ReplicacaoNova:publicacao:bin' is duplicated in the reactor
groupId: ReplicacaoNova
artifactoryId: publicacao
version: bin
How can I resolve this problem?
Thanks
Re: Forced builds
Complex projects with lots of external dependencies, particularly dependencies on external snapshot versions of code. Also, we run a nightly integration test against external systems (we only run Unit tests on the normal non-forced build, or they'd take too long), and changes in the underlying database, or changes in the test data would cause test failures that need to be identified. I feel that this attitude Wayne cites (no delta, no build) is quite common, but makes a lot of assumptions about one's environment, and I think is unrealistic in many large-scale development environments. It may be perfectly reasonable in Wayne's context, or many others, mind you. But especially in large, highly interconnected development environments (like a big bank), you want to have relevant information communicated between groups and architectural layers as quickly as possible to identify any defect or change in assumptions, so a set of system/integration tests run on a schedule (hourly, daily, whatever) are entirely appropriate, and may identify defects regardless of code-changes. The good news, Alexander, is that 1.1 will have such a feature (Jesse committed this a few weeks ago - not so much a forced build, but a fresh cut of the workspace, which has the same effect), so when 1.1 is released you can do exactly this. I frankly run a trunk build, because for all its little instabilities, it's so feature-superior to 1.0.3 that for me it's worth the hassle. One of the main "gets" for our organization is the forced scheduled build. Continuum (1.1-SNAPSHOT) has proven to be quite handy at decreasing latency in communication of API changes, underlying business cases (test data), or other issues by forcing the issues faster, when used this way... even when humans forget to talk to humans. Cheers, Christian. Wayne Fay wrote: > No changes in code == no reason to build, right? I don't see the > usefulness of this enhancement, personally... Unless of course some > PHB has laid down a "build all projects every 3 hrs" kind of mandate > in your organization. > > Wayne > > On 11/20/06, Emmanuel Venisse <[EMAIL PROTECTED]> wrote: >> Not yet, why? >> >> Emmanuel >> >> Morgovsky, Alexander (US - Glen Mills) a écrit : >> > Is it possible to have Continuum force build every n hours even if the >> > code in the source code repository hasn't changed? >> > >> > >> > This message (including any attachments) contains confidential >> information intended for a specific individual and purpose, and is >> protected by law. If you are not the intended recipient, you should >> delete this message. >> > >> > >> > Any disclosure, copying, or distribution of this message, or the >> taking of any action based on it, is strictly prohibited. [v.E.1] >> > >> >> > -- *christian** gruber + process coach and architect* *Israfil Consulting Services Corporation* *email** [EMAIL PROTECTED] + bus 905.640.1119 + mob 416.998.6023*
Re: SCM URL field not sticky/not updating on web interface
What I did is create a user on the continuum machine (call it builder for kicks), and an identical name on the SVN server (CVS would work this way as well). I made sure the [EMAIL PROTECTED] can ssh via certificates without passphrases to [EMAIL PROTECTED]'s account. Then I have builder own the continuum installation location, and start it up as that user. Any non-anonymous checkouts will (unless otherwise instructed) use the builder id, who checks out of the repository normally. (If you had fine grained access control, you could make him a read-only user, but then you couldn't do releases with the 1.1 release mechanism. Anyway. That set has worked without trouble. Otherwise, I've setup projects wtih scm urls containing maven variables that are resolved from profiles. These variables would be for username, etc. I've had less success with the latter approach, though it's arguably good to do in any case, if you can get it right. Christian. Michael Kearney wrote: > (intro removed) > >> I'm running Continuum 1.0.3 on Solaris 10 and I >> originally ran as root but switched to user 'continuum'. Any idea what I >> might >> have done to myself? >> >> Thanks, >>Michael >> >> >> > Michael Kearney comcast.net> writes: > Well, it was a self-inflicted problem. > I want to use the RUN_AS_USER setting to be 'continuum'. > When I do that, the continuum user can't write the .pid file so > I changed the permissions on the directory but now the GUI doesn't work. > > I reinstalled and am running sucessfully as root. > > So my general question is: > > Has anyone sucessfully configured Continuum on a Unix machine to run > under a different (non-root) userid? > What are the best practices for the userid that owns the CVS database, > published website, and other build products? > > Best Regards, > Michael > > > > > -- *christian** gruber + process coach and architect* *Israfil Consulting Services Corporation* *email** [EMAIL PROTECTED] + bus 905.640.1119 + mob 416.998.6023*
Re: Build rollback
Anoop kumar V wrote: > I was wondering if Continuum offers a way of automated rollback of a > failed > build? This would be a very high priority requirement when using > Continuum > on production systems, where in the event of a build failure, the > continuous > integration tool would just revert back to the last successful build, > thereby avoiding a production outage. I'm not sure I understand what that means. How would failing to build a system in CI result in a production outage? Please tell me you're not auto-deploying your production system from a continuous integration system!! regards, Christian. -- *christian** gruber + process coach and architect* *Israfil Consulting Services Corporation* *email** [EMAIL PROTECTED] + bus 905.640.1119 + mob 416.998.6023*
Re: Company Logo
Brad Harper wrote: That did it. Thank you. Brad No problem. -- *christian** gruber + process coach and architect* *Israfil Consulting Services Corporation* *email** [EMAIL PROTECTED] + bus 905.640.1119 + mob 416.998.6023*
Re: Company Logo
Brad Harper wrote: Hello: I've attempted to set the company logo field in the configuration of Continuum, without success. Is there a specific location where the image file should be placed? Brad It's a url, if I'm not mistaken. regards, Christian.
Re: error when building multiple projects joined by maven2 module
Jesse McConnell wrote: well first off, you shouldn't need the SCM sections in the child poms, maven uses the name of the module in the parent pom to determine how to check out the children Does it use the module name, or the artifactId? It used to append the artifactId on the end, which royally screwed me up trying to use a parent scm url. I must have missed the change to the SCM component. In my case, we simply implemented an SCM tag in each sub-project. Irritating, but it worked. Christian.
