Re: Activating profiles based on OS doesn't seem to work right

use the 1.4 version or an earlier one. To solve the problem for my self... I use mac and linux for the two profiles. Hope that helps! Matt Brozowski ____ ___ Matt Brozowski, OpenNMS Maintainer Main: +1 919 812 4984 The Op

Re: [PROPOSAL] Maven 2.1 assembly type.

might just need to have a and tags to make one special :) I did something like this by making a tgz-plugin that calls assembly and used tgz I think its a great idea! Matt ____ ___ Matt Brozowski, OpenNMS Maintainer M

Re: Review of maven-dependency-plugin documentation

org.apache.maven.plugin. I think it should be org.apache.maven.plugins (with an 's') Matt Brozowski ____ ___ Matt Brozowski, OpenNMS Maintainer Main: +1 919 812 4984 The OpenNMS

Re: Review of maven-dependency-plugin documentation

dency-maven- plugin' rather than 'maven-dependency-plugin' Matt Brozowski ____ ___ Matt Brozowski, OpenNMS Maintainer Main: +1 919 812 4984 The OpenNMS Group, Inc.

Re: [discussion] Integration testing location

possibly package and deploy. But it seems like I've seen plenty of discussions on the list that ask how that can do X right before they and Y right before they deploy, etc. As a result I would +1 this one. Matt ____ ___

[jira] Created: (MNG-1858) forkMode=pertest fails to call setUp

Reporter: Matt Brozowski Attachments: surefire-sample.zip The surefire plugin is failing to call the setUp method when forkMode=pertest. I will attach a very simple test project that will make it easy to verify this. Below is the 'trimmed' output if mvn -X -DforkMode=pertest test for

Re: [m2] jalopy plugin

Matt ___ Matt Brozowski, OpenNMS Maintainer Main: +1 919 812 4984 The OpenNMS Group, Inc. Fax:+1 503 961 7746 Email: [EMAIL PROTECTED]

[jira] Created: (MEV-260) [WARNING] POM for 'plexus:plexus-compiler-api:pom:1.4' is invalid.

nvalid POM Reporter: Matt Brozowski [WARNING] POM for 'plexus:plexus-compiler-api:pom:1.4' is invalid. It will be ignored for artifact resolution. Reason: Parse error reading POM. Reason: expected START_TAG or END_TAG not TEXT (position: TEXT seen ...pompom should be removed. (NOTE: This i

[jira] Created: (MEV-258) Reason: Parent: null:plexus-compiler:jar:1.4 of project: unknown:plexus-compiler-api has wrong packaging: jar. Must be 'pom'

URL: http://jira.codehaus.org/browse/MEV-258 Project: Maven Evangelism Type: Bug Components: Invalid POM Reporter: Matt Brozowski no packaging is listed in the plexus-compiler POM file and is causing an error with 2.0.1 which apparently is checking more strictly. Just need to a

[jira] Updated: (MEV-243) xmlrpc:xmlrpc:1.2 depends on relocated servlet api

[ http://jira.codehaus.org/browse/MEV-243?page=all ] Matt Brozowski updated MEV-243: --- Attachment: xmlrpc-1.2.patch > xmlrpc:xmlrpc:1.2 depends on relocated servlet api > -- > >

[jira] Updated: (MEV-243) xmlrpc:xmlrpc:1.2 depends on relocated servlet api

[ http://jira.codehaus.org/browse/MEV-243?page=all ] Matt Brozowski updated MEV-243: --- Attachment: xmlrpc-1.2.patch.correct sorry somehow the first file get double up.. use this patch instead > xmlrpc:xmlrpc:1.2 depends on relocated servlet

[jira] Created: (MEV-243) xmlrpc:xmlrpc:1.2 depends on relocated servlet api

xmlrpc:xmlrpc:1.2 depends on relocated servlet api -- Key: MEV-243 URL: http://jira.codehaus.org/browse/MEV-243 Project: Maven Evangelism Type: Bug Components: Dependencies Reporter: Matt Brozowski Attachments

[jira] Reopened: (MEV-241) commons-attribute-compiler has direct dependency on tools.jar and fails on MacOSX

[ http://jira.codehaus.org/browse/MEV-241?page=all ] Matt Brozowski reopened MEV-241: It's been two days and these updates have not made it to the central repo. I don't know the process of how that works so I'm going to reopen in case

[jira] Commented: (MEV-241) commons-attribute-compiler has direct dependency on tools.jar and fails on MacOSX

[ http://jira.codehaus.org/browse/MEV-241?page=comments#action_52441 ] Matt Brozowski commented on MEV-241: I copied the groupid that the maven integration test it0063 uses. Does it really matter what group id is used for system scope dependencies? As

[jira] Updated: (MEV-241) commons-attribute-compiler has direct dependency on tools.jar and fails on MacOSX

[ http://jira.codehaus.org/browse/MEV-241?page=all ] Matt Brozowski updated MEV-241: --- Attachment: commons-attributes-compiler.patch created using svn diff commons-attributes >From the repository directory > commons-attribute-compiler has

[jira] Created: (MEV-241) commons-attribute-compiler has direct dependency on tools.jar and fails on MacOSX

Reporter: Matt Brozowski commons-attributes-compiler-2.1.pom has the following dependency: java tools 1.4 ${java.home}/../lib/tools.jar system This breaks on MacOSX which doesn't have a tools.jar. After discussing this with brett he pointed me to it00

[jira] Commented: (MNGECLIPSE-9) Classpath entries based on M2_REPO interfere with plugin classpath entries

[ http://jira.codehaus.org/browse/MNGECLIPSE-9?page=comments#action_52353 ] Matt Brozowski commented on MNGECLIPSE-9: - Wouldn't it make sense to completely blow away the .classpath when enabling the mavenNature (or at least rename it or some

[jira] Created: (MEV-105) [Maven 2] xdoclet-maven-plugin depends on xdoclet/xjavadoc-1.1 but it isn't in the maven2 repository

oject: Maven Evangelism Type: Bug Components: Dependencies Reporter: Matt Brozowski xdoclet-maven-plugin depends on xdoclet/xjavadoc-1.1 but it isn't in the maven2 repository. There is an xdoclet/xjavadoc-1.0.x and there is an xjavadoc/xjavadoc-1.1. I don't know which is the c