RE: Release plugin woes

The following work around may help: 1) In the folder containing all the modules add an aggegrator pom that has one module - the parent of the flat structure. 2) Add the information needed by the release (release plugin, scm info, etc.) to that pom. 3) Do your release from that pom. It needs no ot

AW: Maven consultant

Sonatype is also offering support: http://www.sonatype.com Best regards, Eric > -Ursprüngliche Nachricht- > Von: James William Dumay [mailto:[EMAIL PROTECTED] > Gesendet: Sonntag, 7. Dezember 2008 06:44 > An: Maven Users List > Betreff: Re: Maven consultant > > Id recommend getting in

Re: release ${properties} in pom.xml to make different sites

Hi Anders, There's already variables that I guess you could use for your use case. Did you try putting something like this? : http://my-site.xxx/sites/common/${pom.groupId}/${pom.artifactId}/${pom.version} I'm not sure I got all yo

release ${properties} in pom.xml to make different sites

Hi I am working with at wish to make a site per release of my artifact assume the following The trunk: for "my-project" http://my-site.xxx/sites/common/my-project This means that the URL http://my-site.xxx/sites/common/my-project/ contains the site. When I release the 3.0 version of my-p

[ANNOUNCEMENT] - AspectJ compiler Maven Plugin 1.1 released

The AspectJ compiler Maven Plugin team is pleased to announce the aspectj-maven-plugin-1.1 release! Handles AspectJ usage within maven. Functionality provided is: weaving of aspects (or existing aspects from libraries) with the test and/or main classes, weaving of pre-existing jars and aj

[ANNOUNCEMENT] - Maven Axis Tools Plugin 1.2 released

The Maven Axis Tools Plugin team is pleased to announce the axistools-maven-plugin-1.2 release! This plugin supports the wsdl2java and java2wsdl tools from the Apache Axis (1) project. Changes in this version include: Fixed Bugs: o nsInclude and nsExclude only works for a single namespace Is