AW: How to test with multiple versions

2013-11-12 Thread christofer.d...@c-ware.de
Well in the Flexmojos Project we have a testsuite that tests a plugin against several Versions of SDK (Compiler + Libs). The trick is that in the tests, we generate poms with different Versions and spawn different child maven builds for each of These using the maven-invoker-plugin. You can have

Name of a new Apache plugin for maven?

2013-08-06 Thread christofer.d...@c-ware.de
Hi, I am part of the Apache Flex Team and am currently working on Setting up a new Maven plugin for building Apache Flex applications. This will be an official Apache maven plugin, so would I be allowed to Name it maven-flex-plugin or should flex-maven-plugin be used instead? I would prefer

AW: Name of a new Apache plugin for maven?

2013-08-06 Thread christofer.d...@c-ware.de
Ok ... well I did read that naming info, I was just confused how to actually read it :-) Apache Maven plugin or Apache Maven plugin ... you see there are two semantics on how you could understand this. In my case it would actually be a Maven plugin from an Apache Project, but it's not a

AW: mvn release:prepare does not update parent version

2013-07-23 Thread christofer.d...@c-ware.de
Hi, is there actually a reason why only the artifacts in the build are updated? I would agree that without providing versions for artifacts manually, this could cause problems, but when using the feature described here:

AW: Maven and JPA/EclipseLink Configuration...

2013-07-11 Thread christofer.d...@c-ware.de
You could have a look at my Wiki article about multiple persistence.xml files: https://dev.c-ware.de/confluence/display/PUBLIC/Multiple+persistence.xml+in+a+multi-module+application Here you could separate your JPA entities from the platform dependent Options. In your case you could create your

AW: Maven and JPA/EclipseLink Configuration...

2013-07-11 Thread christofer.d...@c-ware.de
... That looks like a Spring only solution I wonder is there a pure JavaEE counterpart On 11 July 2013 09:56, christofer.d...@c-ware.de christofer.d...@c-ware.dewrote: You could have a look at my Wiki article about multiple persistence.xml files: https://dev.c-ware.de/confluence/display/PUBLIC

AW: Is there any generic Maven code generator?

2013-03-01 Thread christofer.d...@c-ware.de
for that is not bound to a phase by default. /Anders On Thu, Feb 28, 2013 at 10:57 AM, christofer.d...@c-ware.de christofer.d...@c-ware.de wrote: Ahem ... this wasn't quite the path I was indenting to go with my question. What I am looking for is a generator-plugin that uses a template

AW: Is there any generic Maven code generator?

2013-02-28 Thread christofer.d...@c-ware.de
maven poms could be used toward EA to get ceratin artiacs visualized for better understanding, that would be almost a very good step into proper direction. Josef -Ursprüngliche Nachricht- Von: christofer.d...@c-ware.de [mailto:christofer.d...@c-ware.de] Gesendet: Mittwoch, 27. Februar

Is there any generic Maven code generator?

2013-02-27 Thread christofer.d...@c-ware.de
I just posted this to Stackoverflow, but after posting I realized, that I should have come here first :-( I am currently working on a project, that makes intense usage of code generation for various purposes. One generator generates SQL scripts from jpa entities. Another generates DTOs from

[ANN] Flexmojos 6.0.0 Relesed

2013-02-25 Thread christofer.d...@c-ware.de
Flexmojos, the maven plugin for building applications using Adobe Flex / Apache Flex, has just been released in version 6.0.0. The main difference to older Flexmojos releases, is that this version is able to use Flex SDKs generated by the Apache Mavenizer tool. This way you can use Flexmojos

Strange plugin dependency problem

2013-02-13 Thread christofer.d...@c-ware.de
Hi, I am currently confronted with a strange problem. I am trying to get a Maven project using AspectJ Compile Time Weaving in IntelliJ. The source code level is set to 1.7 and uses some 1.7 language features. The aspectjtools-1.6.11 which is used by the aspectj-maven-plugin per default can't

AW: Way to limit the projects in the reactor of a maven build started with the invoker plugin

2013-02-13 Thread christofer.d...@c-ware.de
... but it is kind of handy if its an internal project that is well documented. Thanks, Roy Lyons Senior Configuration Engineer On 2/13/13 2:40 PM, christofer.d...@c-ware.de christofer.d...@c-ware.de wrote: Hi, I'm currently trying to use the invoker plugin to start a maven build

AW: How to tell release:perform only to deploy specific modules

2013-02-12 Thread christofer.d...@c-ware.de
-plugin/perform-mojo.html#arguments Op Sat, 09 Feb 2013 19:13:23 +0100 schreef christofer.d...@c-ware.de christofer.d...@c-ware.de: Hi, this is a relatively special case and I am sort of running out of options. I am trying to setup a build that it allows minor releases of individual

How to tell release:perform only to deploy specific modules

2013-02-09 Thread christofer.d...@c-ware.de
Hi, this is a relatively special case and I am sort of running out of options. I am trying to setup a build that it allows minor releases of individual projects (I don't want to get into a discussion about if this is a good thing ... please). Now I am using release:prepare to prepare the

AW: Maven release:prepare

2013-01-05 Thread christofer.d...@c-ware.de
Hi Sundeep, I doubt you can skip the last 2 steps, but you could configure the plugin to change the development version to exactly the same version as the release version. Haven't tried this though: mvn release:prepare -DreleaseVersion={release-version} -DdevelopmentVersion={release-version}

AW: Release plugin ${project.version} dependencies

2012-12-13 Thread christofer.d...@c-ware.de
Actually the release plugin allows you to specify a release and a development version for any module in your build: http://maven.apache.org/plugins/maven-release-plugin/examples/non-interactive-release.html Even if this means you have to configure a comandline that is insanely long. I recently

Implementing a Maven plugin with alternate mojo/component implementations?

2012-12-02 Thread christofer.d...@c-ware.de
Hi, I am currently setting up a new Maven plugin project and am currently faced with the following problem: I have fefined a dafaultLifecycle which defines which mojos should generally be invoked in which phase. My problem now is that I would like to have different implementations used for

AW: Implementing a Maven plugin with alternate mojo/component implementations?

2012-12-02 Thread christofer.d...@c-ware.de
with a default taskId, and users can overrule it. I think this meets your requirements. Good luck, Robert Op Sun, 02 Dec 2012 12:33:43 +0100 schreef christofer.d...@c-ware.de christofer.d...@c-ware.de: Hi, I am currently setting up a new Maven plugin project and am currently faced

Excluding a Plugin dependency

2012-11-07 Thread christofer.d...@c-ware.de
Hi, I am currently having a really stupid problem, that I am currently stuck on: The thing I am currently working on is a maven plugin (Flexmojos). As Flex is now an Apache project, I am working on supporting Apache FDKs in the project, The problem is that the compiler is a direct dependency of

AW: Maven Dependency Type

2012-10-26 Thread christofer.d...@c-ware.de
Hi John, the problem is that Eclipse doesn't know any difference between the normal classpath of an application and a test classpath that includes tests. For eclipse everything (application and test classes) are thrown into one basket. That's why you are able to build in Eclipse. As Jörg

AW: Independent module release strategies

2012-10-23 Thread christofer.d...@c-ware.de
strategies On 16 October 2012 07:45, christofer.d...@c-ware.de christofer.d...@c-ware.de wrote: As described in my other response. Simply keeping the versions in sync is not an option for us due to the donwtime this would mean for our clients and the load this would generate on the central

AW: integration-test, testNG, and a CI server

2012-10-18 Thread christofer.d...@c-ware.de
Hi, I guess what you want to do, is to have the daily build job build and deploy the latest jars without running the integration tests, am I correct? You then want to be able to run the integration tests without deploying first, am I correct? Well in that case I would suggest to tell the

AW: Independent module release strategies

2012-10-16 Thread christofer.d...@c-ware.de
Well as soon as a major release is out the door, in that branch only bugfixes are added that have agreat effect on the application. So I am sure that mostly 2-3 Modules change. I know that in general updating a client with about 20mb doesn't sound that bad in our days, but imagine the load on

Independent module release strategies

2012-10-15 Thread christofer.d...@c-ware.de
Hi, I am currently working on finetuning the workflows on a large application that was migrated from an Ant based build to one based upon Maven. The build itself is running smoothly but, what I'm currently working on is getting the release workflow optimized. The project consists of about 50

Implementing ModelValidators for Plugins

2011-11-01 Thread christofer.d...@c-ware.de
Hi, I am currently working on a way to report common configuration problems of the flexmojos plugin. Which extensionpoints does Maven offer to implement something like this? I found the ModelValidator interface together with its DefaultModelValidator class, but could not find any way to