How to manage from snapshot to release? When should we use automated builds?

Hi, I have been searching the maven website and articles but not sure if i get the best practice for managing snapshots and release. Specifically, if continuous builds produce maven snapshot builds, then when will i produce maven release builds using maven release plug-in? Will I ever produce a

Re: How to manage from snapshot to release? When should we use automated builds?

Well, for example, we don't release automatically. We launch manually it via a special release plugin through hudson, itself launching a maven release through the maven-release-plugin. This makes it easier to keep a clean release environment. Releasing from a development machine would add risk

Re: How to manage from snapshot to release? When should we use automated builds?

We've had similar questions where I work. The question has been related to how and when to create tags in CVS (preferrably using the maven-release-plugin). Some people advocate tagging every build so that it can be recreated in case it was fit for delivery. This is a problem when using CVS since

Re: How to manage from snapshot to release? When should we use automated builds?

Yes, this is a typical, almost specific CVS problem that's understandable. As the versioning is done at the file level, and not at the repo one, it can be necessary to tag to be able to identify the code corresponding to a snapshot (even if, imo, if you're depending on a snapshot revision, and try

Re: package question

Am Dienstag, den 14.09.2010, 21:37 +0200 schrieb per-henrik hedman: And given that it's within Tomcat it probably exists at Central, so you won't need to add a repository declaration to your pom.xml. Hey per, thanks for your reply. Yes i am talking about a jar, i mentioned as package. So the

Re: package question

Hello Daniel, you only need to define your dependency in your pom.xml and then maven will take care of it, but you will have to define it for yourself, as the version of the javamail needs to be correct, and only you know what version you are using, right? Cheers, Per-Henrik On Wed, Sep 15, 2010

Re: package question

1. Get yourself a repo manager. I suggest Nexus, but there are others. 2. Deploy the jar to a repo in the manager. 3. Declare the dependency in your pom the normal Maven way. This has been discussed several times on the list and there are also numerous blog posts. Here's one:

Mixing local repo and managed repo

Hi, I came across a continuous integration server hosting both an Hudson and an Archiva (as a proxy to our central). The settings.xml used in maven builds declare as the local repo the managed repository of the archiva (same directory). Is that wrong to use as a local repository (declared in the

Re: package question

Am Mittwoch, den 15.09.2010, 10:20 +0200 schrieb per-henrik hedman: you only need to define your dependency in your pom.xml and then maven will take care of it, but you will have to define it for yourself, as the version of the javamail needs to be correct, and only you know what version you

Re: Mixing local repo and managed repo

Hi, Yes, first local and remote maven repository doesn't contain the same metadata. And by the way, accessing a local repository by many instances isn't concurrent-safe (at least, in maven 2, I don't know precisely what's been done for maven 3, particularly along the parallel build evolution).

Re: package question

Hi, Setting up a nexus is two minutes work, and then makes you easier the ongoing config/add every days. But anyway, yes, you can install properly a resource into the local repository. Just google install:install-file to find doc about that goal. Before doing that, you should triple-check on the

New Eclipse Plugin - hot Deployment for application servers

Hi, I have started a new Eclipse Plugin project to support hot deployment and incremental deployment of Multi-Module Projects into App servers like Glassfish or JBoss. In most cases when the maven project contains more than one ejb or web modules the deployment from Eclipse WTP Plugin

Re: package question

if you get the md5 sum of the jar file, then a nexus instance that is configured will let you search by md5 or sha1 sum for the artifact. for example if you go to repository.sonatype.org, click on advanced search and then change to checksum search you can get it to search for the jar on central.

Re: How to manage from snapshot to release? When should we use automated builds?

Thanks for your input Baptiste, Yes, we have been debating the relase process a bit here. Keeping the relase process separate would e g mean that we know beforehand that we want to build a release candidate. We could then start with the tagging and then checkout on this tag for the build of the

Re: Mixing local repo and managed repo

Didn't know metadata were different, as I quoted from maven website: the local and remote repositories are structured the same way. Thank you for the great answer, couldn't expect less from an ig2k student ;) Em. On Wed, Sep 15, 2010 at 11:16 AM, Baptiste MATHUS m...@batmat.net wrote: Hi,

A wsdl file as an artifact

How do people manage wsdl files in their repo. Do you manage them in a jar artifact or any other way?

Re: A wsdl file as an artifact

Hi, You can probably try to share this with Maven Remote Resources Plugin. 2010/9/15 Anders Hammar and...@hammar.net: How do people manage wsdl files in their repo. Do you manage them in a jar artifact or any other way? -- Olivier http://twitter.com/olamy http://www.linkedin.com/in/olamy

Re: A wsdl file as an artifact

Hi ANders Anders Hammar wrote: How do people manage wsdl files in their repo. Do you manage them in a jar artifact or any other way? Use the build-helper plugin. We manage xsd files as artifacts: == % == plugin groupIdorg.codehaus.mojo/groupId

Re: A wsdl file as an artifact

Thanks! Jörg's approach is what I was thinking of. The only drawback is bad/incorrect metadata (pom packaging). That could be fixed though. The nice thing is that this would also work great with a ws registry containing wsdl files, which could quite easily be proxied by a repo manager as a maven

Re: Mixing local repo and managed repo

I'm not totally sure, but I think this sentence refers to the structure (groupId(dots replaced with subdirs)/artifactId/version), not compulsorily the attached metadata. I just checked on my box and on our internal archiva instance, for example, maven-metadata.xml on the server is renamed locally

Re: A wsdl file as an artifact

Hi Anders, Anders Hammar wrote: Thanks! Jörg's approach is what I was thinking of. The only drawback is bad/incorrect metadata (pom packaging). That could be fixed though. The nice thing is that this would also work great with a ws registry containing wsdl files, which could quite easily

Re: A wsdl file as an artifact

I don't necessarily want a jar. I'm just wondering if anyone have run into issues using either one of the approaches. I'm thinking about classpaths, plugins etc. The packaging type is metadata and should be correct. For the this project the wsdl file is the primary artifact, but if the packing

Re: package question

Am Mittwoch, den 15.09.2010, 11:04 +0100 schrieb Stephen Connolly: if you get the md5 sum of the jar file, then a nexus instance that is configured will let you search by md5 or sha1 sum for the artifact. I have done this: === 8 === $ md5sum /usr/share/java/javamail.jar

Running Findbugs with Maven fails

Hi, I am trying to analyze a Maven project with Findbugs, as follows: mvn org.codehaus.mojo:findbugs-maven-plugin:2.3.1:findbugs The build is successful, but there is no trace of the analysis reports and I also get the following output: [INFO] [findbugs:findbugs {execution: default-cli}] [INFO]

scm problems wtih release plugin

hi, i have a multi module project (40 projects) with cvs as scm. when i try to create a release i got the error [INFO] Tagging release with the label xxx-5_6_986... [INFO] [ERROR] BUILD FAILURE [INFO]

Re: A wsdl file as an artifact

On Wednesday 15 September 2010 7:26:04 am Anders Hammar wrote: Thanks! Jörg's approach is what I was thinking of. The only drawback is bad/incorrect metadata (pom packaging). That could be fixed though. The nice thing is that this would also work great with a ws registry containing wsdl

Release Notes Plugin

Hi Folks, Does anyone knows about a plugin that can attach/generate an internal release notes? For instance, I'm trying to generate a report based on SVN changelog filtering, as that might be interesting for testers that use the component to perform system testing. I've looked at some

RE: Release Notes Plugin

Site? Curt Yanko | Continuous Integration Services | UnitedHealth Group IT CT039-05C | office: 860.702.9059 | email: c...@uhc.com | intranet: cis.uhc.com Making IT Happen, one build at a time -Original Message- From: Felipe Roos

Re: Release Notes Plugin

We use the Changes Plugin, which has goals for creating and emailing announcements for releases. The contents of the release notes can currently come in 3 flavors: a (hand edited) changes.xml file or from one of the issue trackers JIRA or Trac. On 2010-09-15 18:56, Felipe Roos wrote: Hi Folks,

Re: A wsdl file as an artifact

Hi Anders, Anders Hammar wrote: I don't necessarily want a jar. I'm just wondering if anyone have run into issues using either one of the approaches. I'm thinking about classpaths, plugins etc. The packaging type is metadata and should be correct. For the this project the wsdl file is the

Re: A wsdl file as an artifact

Ok, thank you all for your input! /Anders On Wed, Sep 15, 2010 at 20:05, Jörg Schaible joerg.schai...@gmx.de wrote: Hi Anders, Anders Hammar wrote: I don't necessarily want a jar. I'm just wondering if anyone have run into issues using either one of the approaches. I'm thinking about

[PLEASE TEST] Apache Maven 3.0-RC1

Hi, in preparation for the release of Apache Maven 3.0, the Maven team is seeking your help to discover regressions since Maven 2.x. Everybody interested in taking a preview of the upcoming release for a test drive can get source and binary bundles from this URL:

Re: How to manage from snapshot to release? When should we use automated builds?

Does anyone have a Best Practice already written for this? From what I understand: a) since releases are immutable, you can only deploy a release once. b) you are allowed to deploy snapshots as often as you want c) a human being needs to decide when you are starting to build releases. d) you

Re: archetype-catalog.xml and its properties and goals elements, what populates them?

Anyone have any info/background on the goals and properties sections of archetype-catalog.xml ? -- View this message in context: http://maven.40175.n5.nabble.com/archetype-catalog-xml-and-its-properties-and-goals-elements-what-populates-them-tp2799170p2841463.html Sent from the Maven - Users