Re: Logging for dependencies of Maven plugin

Hi Sander, the next line of the documentation should interest you: The following system properties are supported to configure the behavior of this logger: So you can set them programmatically as well or by cmdline, no need to use the simplelogger.properties. If I understand you correctly,

Re: what are some best practices for maven artifact naming when multiple code branches exist?

I would add a suffix to the version for each branch. For example, if trunk is 1.0.0-SNAPSHOT, feature branch A would get version 1.0.0-featureA-SNAPSHOT. /Anders On Sat, Apr 18, 2015 at 9:10 PM, Nikita Tovstoles nikita.tovsto...@gmail.com wrote: Suppose we have an app that's being developed

Packaging Maven Core Extensions

Hi, I have just finished a small maven core extension containing an EventSpy. It's working nicely if I include it into my build using Maven 3.3.1 and a .mvn/extensions.xml, but I couldn't get it working by copying the jar to the MAVEN_HOME/lib/ext directory (I even tried a shaded jar). All I

what are some best practices for maven artifact naming when multiple code branches exist?

Suppose we have an app that's being developed on trunk and a couple of branches simultaneously - and we'd like to publish artifacts from each dev branch into our maven repo (so that we can run a cluster for each code branch). Currently the 'V' in GAV equals our CI's build plan execution number.

Re: Packaging Maven Core Extensions

Where's the code for the extension. They are expected to work in both places, you shouldn't have to do anything special other than making sure your dependencies are correctly marked as provided. On Apr 18, 2015, at 12:26 PM, Christofer Dutz christofer.d...@c-ware.de wrote: Hi, I have

Re: Packaging Maven Core Extensions

Hi, are you running from within Jenkins ? On 4/18/15 6:26 PM, Christofer Dutz wrote: Hi, I have just finished a small maven core extension containing an EventSpy. It's working nicely if I include it into my build using Maven 3.3.1 and a .mvn/extensions.xml, but I couldn't get it working by

AW: Packaging Maven Core Extensions

Hi, the code is here: https://github.com/apache/flex-utilities/tree/develop/mavenizer/maven-extension The provided scope was the tip that got my fat-jar running in lib/ext for Maven 3.1.1 ... Unfortunately it seems to only run in Maven 3.3.1 ... if I try it in 3.2.2 or 3.1.1 I get errors :-(

RE: what are some best practices for maven artifact naming when multiple code branches exist?

Makes sense - thanks! On Apr 18, 2015 12:43 PM, Sander Verhagen san...@sanderverhagen.net wrote: I've searched a lot about this subject in the past. And we're currently using what Anders described. For completeness sake: you could possibly abuse classifiers for this as well. Sander

RE: what are some best practices for maven artifact naming when multiple code branches exist?

I've searched a lot about this subject in the past. And we're currently using what Anders described. For completeness sake: you could possibly abuse classifiers for this as well. Sander Verhagen [ san...@sanderverhagen.net ] NOTICE: my e-mail address has changed. You may still e-mail me

AJ to Java converter plugin?

Good Evening Gentlemen glad you could take a brief respite from eating red-hot texas chili and riding broncing bucks I am seeking a plugin to convert aspectj (aj) files to plain java does such a plugin exist? Enjoy Austin! Martin __