Re: Maven Exec - Inheritance - Multi Module Build

Hi Anders, what you mentioned is correct, but this does not solve my problem... BTW: The usage works for MVN 2.2.1 and MVN 3.0 - Alpha 5...but i've checked the docs and you're right... Anders Hammar wrote: > > I just wanted to mention that defining two plugin sections of the same > plugin (exe

Enabling fileset packaging with archetype-metadata.xml

I trying to set up my Maven archetype so the directory layout for ActionScript files can be updated through the package setting. This provides ActionScript with the same functionality available to Java files. I've read http://maven.apache.org/plugins/maven-archetype-plugin/advanced-usage.html and

Re: To use version for maven.plugins or not to use, that is the question :)

On Tue, Dec 15, 2009 at 7:09 AM, Qureshi,Shahzad [Ontario] wrote: > Hi all, > > I wanna know the standard and the reasons behind it. > > I want to find out if I should specify a version for a maven plugins, lets > say maven-javadoc-plugin, or not to specify it and in which case the default > one

[ANN] Maven Doxia Tools 1.2 Released

The Maven team is pleased to announce the release of the Maven Doxia Tools, version 1.2 This shared component has some utilities that are useful when integrating Doxia in Maven, mainly for site generation and report creation. The main entry point is the SiteTool Plexus component. http://maven.apa

Re: To use version for maven.plugins or not to use, that is the question :)

And Maven 3 will also complain (well, inform) about this. /Anders On Mon, Dec 14, 2009 at 22:09, Justin Edelson wrote: > Yes - use a version. > > Set up an organizational pom and use it as the parent for all of your > projects. Use the pluginManagement section of the organizational pom to > decl

[ANN] Sonar 1.12 Released

The Sonar Team is pleased to announce the 8th and last major Sonar release of the year. Around 60 improvements and bug fixes are contained in this new version and the main features are : * Ability to manage authentication and authorization by project * Ability to ignore violations with the new

Re: To use version for maven.plugins or not to use, that is the question :)

Yes - use a version. Set up an organizational pom and use it as the parent for all of your projects. Use the pluginManagement section of the organizational pom to declare plugin versions. Unless you do this, your builds aren't fully reproduceable. Justin On Mon, Dec 14, 2009 at 3:39 PM, Qureshi

Re: Maven PDF Plugin Problems

The pdf plugin doesn't support multi-module projects (yet): http://jira.codehaus.org/browse/MPDF-8 HTH, -Lukas On Mon, Dec 14, 2009 at 6:20 PM, Neil Chaudhuri < nchaudh...@potomacfusion.com> wrote: > I am attempting to use the latest Maven PDF plugin just published with > my multi-module Maven

Re: maven assembly plugin - the artefact size is multiplied by 2

I've tried to use winzip, 7-zip, and to extract with the jar command. It's always the same message, this archive is not a valid archive. So I can't see its contents. Just a precision, my assembly work fine on windows, the problem is just on debian. The JDK I use is 1.6.0_16-b01 >But, when

To use version for maven.plugins or not to use, that is the question :)

Hi all, I wanna know the standard and the reasons behind it. I want to find out if I should specify a version for a maven plugins, lets say maven-javadoc-plugin, or not to specify it and in which case the default one will be used. At this point, I don't specify versions I recently setup Nexus

Re: filteredExtensions doesn't work

By default, Maven only recognizes a limited set of languages. When a language is recognized then Maven performs filtering on files ending in the language suffix (such as *.java). This example demonstrates the filtering difference between Java (recognized) and ActionScript (unrecognized) files: [

Re: Maven Exec - Inheritance - Multi Module Build

I just wanted to mention that defining two plugin sections of the same plugin (exec-maven-plugin in your case) is incorrect. I believe there is a bug in som Maven versions that allow that, but it's not te corredt way of doing things. Instead, you should specify two execution sections in the same pl

Re: AW: pom.xml : element

Am 14.12.2009 um 13:08 schrieb Mark Struberg: > the element in the pom is used for every SCM action in maven, e.g. if > you do a mvn release:prepare / mvn release:perform and stuff. > > Since Hudson and other CI environments often do not rely on the build system > for updating the project, they

Re: Memory Issues with site and javadoc reports.

Update... I've solved this in my build by using the 2.3 version of maven-javadoc-plugin instead of the 2.6.1. I'll test other versions between 2.3 and 2.6.1 as time permits. Thanks, -Ryan On Mon, Dec 14, 2009 at 1:11 PM, Ryan Connolly wrote: > Hello, I'm hoping someone may be able to assist me

Getting Flex to respond like Java to the package argument

Files that end with a java suffix respond to the package argument by [DEBUG] Processing fileset src/main/java (Filtered-Packaged) [**/*.java -- ] This results in their directory layout being updated to reflect the value of the package argument. It appears that all other file suffixes are eithe

Memory Issues with site and javadoc reports.

Hello, I'm hoping someone may be able to assist me with a Maven Site generation issue I've been having ever since I added a fourth module to my multi-module build. The issue appears to be linked to the maven-javadoc-plugin and I'm hoping someone here may have some insight into how I may be able to

Re: maven assembly plugin - the artefact size is multiplied by 2

>    But, when the size of my ear is more than 20Mo, the size is multiplied by > 2 in the destination folder. >    I thought that it just makes a copy. Use Winzip or similar to unpack the Ear and look at the contents. You can probably figure out what's going on with a little more information, but

Doxia macro for links to xref sources

Hi, does anybody out there has any experience how linking to the xref sources should be done? I'd like to just add the FQN for my class and let doxia do the rest... Any ideas? Johannes - To unsubscribe, e-mail: users-unsubscr..

Re: Info report license LGPL

Isn't there anyone who ran in the same issue before or, at least, has a hint where to dig? Am 10.12.2009 um 14:56 schrieb Martin Scholl: Hi, I have a maven project, where I specified "LGPL" as license. If the project site is generated (or the license goal is explicitly invoked) the resu

Maven PDF Plugin Problems

I am attempting to use the latest Maven PDF plugin just published with my multi-module Maven project. Even though site generation is working for me, I am having some issues with the PDF plugin and have a few questions: 1) Why must I have a "site" directory in every module? 2) When I

maven assembly plugin - the artefact size is multiplied by 2

Hello, I'm working on a multi-module project. This project contains an ear artifact, which is correctly generated. I'm also using maven-assembly-plugin (tried with version 2.2-beta-2 to 2.2-beta-4), to group all the artifact I've generated in a specific folder, call it destination fo

Maven Exec - Inheritance - Multi Module Build

Hi, i'm testing a setup with Maven and a combination of Java/Non Java Projects (using RPM plugin etc.)... I'm using a parent to bind some calls to exec plugin to particular phases: org.codehaus.mojo exec-maven-plugin 1.1.1

Re: Error using element in

Duh. My bad. I figured it had to be something simple. Thanks! On Mon, Dec 14, 2009 at 7:10 AM, Justin Edelson wrote: > It needs to be > > *  * >     >         org.datanucleus >         datanucleus-core >         2.0.0-m4 >    ...more... >     >  * * > > > See > http://maven.apache.org/ref/2.

Re: Error using element in

It needs to be * * org.datanucleus datanucleus-core 2.0.0-m4 ...more... * * See http://maven.apache.org/ref/2.2.1/maven-model/maven.html#class_dependencyManagement Ju

Error using element in

Hi all, I'm trying to support different JPA implementations in my build. According to http://maven.apache.org/guides/introduction/introduction-to-profiles.html, I can specify the element in a build profile. However, when I do, I get a POM parse error with the following error reason: Reason: Pa

Howto configure Logging format of Maven3 console output

Hi, I want to change the format of the console output in order to get timestamps for each logging entry. The only information I found (http://jira.codehaus.org/browse/MNG-519) with respect to this issue is for maven 2 and does not match to maven 3. How can the logging format been changed in mav

AW: pom.xml : element

the element in the pom is used for every SCM action in maven, e.g. if you do a mvn release:prepare / mvn release:perform and stuff. Since Hudson and other CI environments often do not rely on the build system for updating the project, they have the ability to do this their self (otoh, some CI

Re: pom.xml : element

Mainly it's used by maven-scm-plugin and maven-release-plugin. Or any other plugin that uses this metadata. The POM is all about describing a project. This info/metadata can then be used by any plugin or tool. For instance, the scm info is also used by M2Eclipse if you want to checkout a project ba

pom.xml : element

Hello, What is the purpose of the element defined in the pom.xml. I can't understand its usefulness. In Hudson, the link to the SCM is configured in the job. When I make a release (maven-release-plugin), I feel that the plugin is based on information contained in the workspace. http://maven.apa

Re: modules are built but not copied to local repository?

Executing mvn install gives me this: [INFO] Building examples in J2ME with juliac [INFO] [INFO] [site:attach-descriptor {execution: default-attach-descriptor}] [INFO] --

Re: SOLVED I guess. Re: What happens to cause a build to not work after blowing out your repo - how to force so things are always checked locally?

Please never change the subject. It appears as a new thread, and if someone finds the original entry, he won't see this one in the end... Thanks. 2009/12/12 Rick R > After more googling I found this discussion > > http://www.yeap.de/blog2.0/archives/183-Upgrading-flex-mojos-2.0.0-to-flexmojos-m