AW: AW: Update release plugin to allow more fine-grained releases

2013-02-16 Thread christofer.d...@c-ware.de
/02/2013, at 7:24 PM, christofer.d...@c-ware.de christofer.d...@c-ware.de wrote: Hi Chris, Well the project consists of about 80 modules. The main reason for this is that the application is a big Swing application distributed via some web-start similar technology. The reason for releasing

AW: Update release plugin to allow more fine-grained releases

2013-02-15 Thread christofer.d...@c-ware.de
, christofer.d...@c-ware.de christofer.d...@c-ware.de wrote: But thanks for that hint to check 2.3.2 ... I'll have a look at that this weekend :-) Von: Robert Scholte [rfscho...@apache.org] Gesendet: Donnerstag, 14. Februar 2013 11:59 An: Maven Developers List

AW: Update release plugin to allow more fine-grained releases

2013-02-14 Thread christofer.d...@c-ware.de
version for you, so you can keep the unreleasable projects on their old SNAPSHOT version. Robert Op Wed, 13 Feb 2013 20:30:39 +0100 schreef christofer.d...@c-ware.de christofer.d...@c-ware.de: Hi, I was experimenting a little with the release plugin. In one of my experiments I gave it a really

AW: Update release plugin to allow more fine-grained releases

2013-02-14 Thread christofer.d...@c-ware.de
on their old SNAPSHOT version. Robert Op Wed, 13 Feb 2013 20:30:39 +0100 schreef christofer.d...@c-ware.de christofer.d...@c-ware.de: Hi, I was experimenting a little with the release plugin. In one of my experiments I gave it a really long list of dev- and release-versions for a lot of artifacts

Update release plugin to allow more fine-grained releases

2013-02-13 Thread christofer.d...@c-ware.de
Hi, I was experimenting a little with the release plugin. In one of my experiments I gave it a really long list of dev- and release-versions for a lot of artifacts using the -Dproject.rel. and -Dproject.dev. properties. Then I limited my maven build to only process a hand full of modules.

Is it a bug? (install plugin deploys poms with variables in artifact.version and parent.version)

2012-10-15 Thread christofer.d...@c-ware.de
Hi, I just opened an issue regarding the install plugin (I think that's the module responsible). http://jira.codehaus.org/browse/MNG-5358 The general problem is that I am using variables for defining the versions of artifacts, dependencies and parent projects. The install plugin installs the

AW: Is it a bug? (install plugin deploys poms with variables in artifact.version and parent.version)

2012-10-15 Thread christofer.d...@c-ware.de
[stephen.alan.conno...@gmail.com] Gesendet: Montag, 15. Oktober 2012 16:32 An: Maven Developers List Betreff: Re: Is it a bug? (install plugin deploys poms with variables in artifact.version and parent.version) On 15 October 2012 15:13, christofer.d...@c-ware.de christofer.d...@c-ware.de wrote: Hi, I

AW: Is it a bug? (install plugin deploys poms with variables in artifact.version and parent.version)

2012-10-15 Thread christofer.d...@c-ware.de
in trying to square this circle On 15 October 2012 16:18, christofer.d...@c-ware.de christofer.d...@c-ware.de wrote: I know that property substitution in those places seems to be unavailable. But there seems to be one case where it's seems to be explicitly allowed: If the parent artifacts version

AW: Is it a bug? (install plugin deploys poms with variables in artifact.version and parent.version)

2012-10-15 Thread christofer.d...@c-ware.de
are using System properties, there may be some unintended expansion of those in /project/parent BUT I REPEAT... STOP! Don't do it. Many kittens will be killed if you persist in trying to square this circle On 15 October 2012 16:18, christofer.d...@c-ware.de christofer.d...@c-ware.de wrote: I know

AW: the simplest possible maven plugin, sort of

2012-09-11 Thread christofer.d...@c-ware.de
In Flexmojos you have to run the build twice (The first with minimal profile turned on), because otherwise maven will complain about the plugin not being available. As soon as there is any artifact with that name I am able to build with only one run, because the build replaces/updates the

Problem configuring plugins

2012-05-08 Thread christofer.d...@c-ware.de
Hi, I am currently working on some Issues in the flexmojos projects build. One is sort of me. I assume there have been some changes in Maven that now prevent the plugin configuration from working the same way it did with earlier maven versions. I have a Plugin flexmojos-maven-plugin and the

AW: Problem configuring plugins

2012-05-08 Thread christofer.d...@c-ware.de
Ok ... I resolved this Issue myself. The problem was, that internally the build was using Maven 3.0.2 for executing sub-tests. It seems that this type of configuration is only possible in Maven 3.0.3 and higher. Chris Von: christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de

AW: Implementing ModelValidators for Plugins

2011-11-08 Thread christofer.d...@c-ware.de
. Inf. Christofer Dutz Karlstraße. 104, 64285 Darmstadt fon:  0 61 51 / 27315 - 61 fax:  0 61 51 / 27315 - 64 mobil:  0171 / 7 444 2 33 email:  christofer.d...@c-ware.de http://www.c-ware.de UStId-Nr. DE195700962 -Ursprüngliche Nachricht- Von: Olivier Lamy [mailto:ol...@apache.org] Gesendet

AW: Implementing ModelValidators for Plugins

2011-11-04 Thread christofer.d...@c-ware.de
:  christofer.d...@c-ware.de http://www.c-ware.de UStId-Nr. DE195700962 -Ursprüngliche Nachricht- Von: christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de] Gesendet: Donnerstag, 3. November 2011 09:50 An: dev@maven.apache.org Betreff: Implementing ModelValidators for Plugins Hi, I am

Implementing ModelValidators for Plugins

2011-11-03 Thread christofer.d...@c-ware.de
Hi, I am currently working on a way to report common configuration problems of the flexmojos plugin. The reason for this ist hat about 99% of the problems users on the mailinglist are having are all related to mis-configurations. 90% of those adress a small hand-full of mistakes. We would