Re: [ANN] maven-issues-plugin

Antonio Petrelli wrote: Cool! But since you already licensed with Apache License v2, why don't you donate it to the Maven Changes Plugin? Hello Antonio, thank you for your reply! One reason for not trying to contribute to the changes plugin was that this plugin requires to run on Java

[ANN] maven-issues-plugin

We are pleased to announce the release of maven-issues-plugin 0.4.0! https://project.smartics.de/maven-issues-plugin/ https://project.smartics.de/maven-issues-plugin/ This Maven 2 plugin generates reports on issues retrieved from an issue management system. Currently only Bugzilla

[ANN] maven-buildmetadata-plugin

We are pleased to announce the release of maven-buildmetadata-plugin 1.0.0! https://project.smartics.de/maven-buildmetadata-plugin/ This Maven 2 plugin is a little helper to easily add build meta data to the generated archive artifacts. Imagine the product is running on

Proper use of checkstyle's xrefLocation for aggregated jxr report

Hello *! My question is: How can I configure the checkstyle plugin so that the checkstyle report of the subprojects reference the jxr report of the module project in the parent folder? The destination of the jxr generated files is in the root project of the multi-project. The structure of the

RE: jar does not attach to reactor?

Hello Brian, thank you for your reply! I think I did not make my problem clear... I already follow your hint by using 'unpack-dependencies', so my question is basically how to get artifacts in the reactor, not out of it. But your answer confirms me that I am correctly accessing artifacts from

RE: jar does not attach to reactor?

Hi Brian, what I am trying to accomplish (and what actually works) is this: I have a module that implements the persistency layer with JPA. This module provides (currently) all implementation and tests against an in-memory database with a specific JPA implementation (this is the core module).

RE: jar does not attach to reactor?

Hi Brian, sorry that I forgot the dependency. It is declared in the variations-parent POM: dependency groupIdde.smartics.timesheet/groupId artifactIdtimesheet-ejb-core/artifactId version${depVersion.timesheet-ejb-core}/version classifiertests/classifier scopetest/scope /dependency

Re: Multi-module site, why must I do mvn clean install site?

Hi Paul G, I faced a similar problem today. We have a multi-project-build and the site plugin does not fetch the artifacts from the reactor, but tries to download them from the local repo. Therefore the artifacts need to be installed. I think this might be your problem, too. There is a bug

jar does not attach to reactor?

Hi! is it true that the jar plugin does not add the generated artifact to the reactor to share it with other projects in a multi-project-build? They get installed and deployed, but I failed to notice that the dependency-plugin will still grab the specified artifacts from the local repo (instead

Re: Resources with different encoding

exclude**/*.xml/exclude exclude**/*.properties/exclude /excludes /resource /resources /project For more information, kindly take a look at [1]. Cheers, Franz [1] http://maven.apache.org/plugins/maven-resources-plugin/ Robert Reiner wrote: Hi

Re: checkstyles

Trevor Torrez wrote: What is the best way to have all subprojects use the same checkstyles file? Hi Trevor, I do not know what the best way is, but this is how it works for me: I have a parent POM to all POMs of my subprojects. In this I declare my checkstyle configuration as an

Resources with different encoding

Hi! I have a question concerning the maven-resources-plugin: In my resource folder I have files with different encodings. The XML files are UTF-8, the properties files are ISO-8859-1. Since I set the encoding for copying the files to UTF-8, my property files are not copied properly. A

Inheritance

Hi! I have written an ant mojo I want to bind to a phase. This mojo should be configured (I currently only want to specify the version) in a parent POM and inherited to a POM used for a jar project. So I define in the *.mojos.xml ... pluginMetadata mojos mojo callnative2ascii/call