[jira] Closed: (MNG-2056) Exception when starting new page with AbstractMavenMultiPageReport

[ http://jira.codehaus.org/browse/MNG-2056?page=all ] Kenney Westerhof closed MNG-2056. - Assignee: Kenney Westerhof Resolution: Won't Fix The AbstractMavenMultiPage report has never worked and no longer exists. Instead, use the latest maven-site-p

[jira] Commented: (MNG-1922) Rename maven-it-plugin plugin as its name implies it is for performing integration tests in general

[ http://jira.codehaus.org/browse/MNG-1922?page=comments#action_85444 ] Kenney Westerhof commented on MNG-1922: --- You may be right - it can only execute maven projects, embedded (that's where most original embedder code came from actually ;)

[jira] Commented: (MNG-900) snapshots without metadata are not resolved

[ http://jira.codehaus.org/browse/MNG-900?page=comments#action_85446 ] Kenney Westerhof commented on MNG-900: -- This issue has regressed again at 2.1-snap. > snapshots without metadata are not resolved > -

[jira] Closed: (MPH-21) Help;effective-pom: don't aggregrate when called from lifecycle

[ http://jira.codehaus.org/browse/MPH-21?page=all ] Kenney Westerhof closed MPH-21. --- Assignee: Kenney Westerhof Resolution: Fixed Fix Version/s: 2.0.2 Fixed in svn revision r497785 > Help;effective-pom: don't aggregrate when called from li

[jira] Created: (MPH-21) Help;effective-pom: don't aggregrate when called from lifecycle

Help;effective-pom: don't aggregrate when called from lifecycle --- Key: MPH-21 URL: http://jira.codehaus.org/browse/MPH-21 Project: Maven 2.x Help Plugin Issue Type: Bug Affect

[jira] Commented: (MNG-2811) issue description: 'Plugin dependencies override maven core artifacts causing NoClassDefFoundErrors'

[ http://jira.codehaus.org/browse/MNG-2811?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_86956 ] Kenney Westerhof commented on MNG-2811: --- It looks like the dependencies brought in by the plugin (maven-model, plexus-uti

[jira] Commented: (MNG-2293) maven-plugin-descriptor: Not possible to define a default implementation for a field defined by its interface

[ http://jira.codehaus.org/browse/MNG-2293?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89690 ] Kenney Westerhof commented on MNG-2293: --- Added a comment to MWEBSTART-18. I think the invalid use of 'implementation="${.

[jira] Commented: (MNG-2771) Provide a means of loading custom substitute components instead of default Maven components

[ http://jira.codehaus.org/browse/MNG-2771?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_89691 ] Kenney Westerhof commented on MNG-2771: --- There are currently 3 ways this works in 2.1-SNAPSHOT. The first way is to place

[jira] Closed: (MNG-2410) adding a method in AbstractMavenReport to obtain newSink()

[ http://jira.codehaus.org/browse/MNG-2410?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kenney Westerhof closed MNG-2410. - Resolution: Fixed Fix Version/s: (was: 2.1.x) 2.1-alpha-1 This has been fix

[jira] Commented: (MNG-2172) 's are not used when evaluating

[ http://jira.codehaus.org/browse/MNG-2172?page=comments#action_61775 ] Kenney Westerhof commented on MNG-2172: --- Related sources: maven-project/.../DefaultMavenProjectBuilder.java, line 320: call to createManagedVersionMap. Proposal: move to MavenProj

[jira] Updated: (MNG-2054) Multiple Inheritence causes plugin executions to run multiple times (Test Case Attached)

[ http://jira.codehaus.org/browse/MNG-2054?page=all ] Kenney Westerhof updated MNG-2054: -- Attachment: antrun2.tgz > Multiple Inheritence causes plugin executions to run multiple times (Test > Case Attached) > ---

[jira] Reopened: (MSUREFIRE-53) Make forked mode console output look the same as non-forked mode console output

[ http://jira.codehaus.org/browse/MSUREFIRE-53?page=all ] Kenney Westerhof reopened MSUREFIRE-53: --- Assign To: Kenney Westerhof (was: Jason van Zyl) The System.out/System.err is NOT correctly printed to standard out when using fork mode. This

[jira] Closed: (MSUREFIRE-53) Make forked mode console output look the same as non-forked mode console output

[ http://jira.codehaus.org/browse/MSUREFIRE-53?page=all ] Kenney Westerhof closed MSUREFIRE-53: - Resolution: Fixed Fixed in revision 390651. > Make forked mode console output look the same as non-forked mode console > output >

[jira] Closed: (MJAR-21) JarSign cleanups

[ http://jira.codehaus.org/browse/MJAR-21?page=all ] Kenney Westerhof closed MJAR-21: Resolution: Fixed Fixed in revision 393197. I undid the changes to make two methods private instead of package protected, since this constitutes an API change. I

[jira] Closed: (MJAR-22) Allow to programatically identify between types of sign failures

[ http://jira.codehaus.org/browse/MJAR-22?page=all ] Kenney Westerhof closed MJAR-22: Resolution: Fixed Applied patch in revision 393202. Applied some code formatting. > Allow to programatically identify between types of sign failures > ---

[jira] Closed: (MJAR-23) Add a global property for skipping jar signing

[ http://jira.codehaus.org/browse/MJAR-23?page=all ] Kenney Westerhof closed MJAR-23: Resolution: Fixed Committed in revision 393203. > Add a global property for skipping jar signing > -- > > Key

[jira] Closed: (MJAR-24) don't sign already signed jars (also allow for in-place jar signing)

[ http://jira.codehaus.org/browse/MJAR-24?page=all ] Kenney Westerhof closed MJAR-24: Assign To: Kenney Westerhof Resolution: Fixed Committed in revision 393237, with minor modifications. > don't sign already signed jars (also allow for in-pla

[jira] Commented: (MNG-1323) Plugin extensions (dependencies) not resolved in reactor build

[ http://jira.codehaus.org/browse/MNG-1323?page=comments#action_63562 ] Kenney Westerhof commented on MNG-1323: --- Hm.. this problem is really annoying and there is no workaround. Now I even get a weirder error: java.lang.NoSuchMethodError: java_cup.run

[jira] Created: (WAGONSSH-46) Allow use of both password and private key

Allow use of both password and private key -- Key: WAGONSSH-46 URL: http://jira.codehaus.org/browse/WAGONSSH-46 Project: wagon-ssh Type: Improvement Reporter: Kenney Westerhof We have corporate m2 repository over http wi

[jira] Created: (MRESOURCES-18) System properties and cmdline params not filtered without filter file

System properties and cmdline params not filtered without filter file - Key: MRESOURCES-18 URL: http://jira.codehaus.org/browse/MRESOURCES-18 Project: Maven 2.x Resources Plugin Type: Bug Report

[jira] Updated: (MRESOURCES-18) System properties and cmdline params not filtered without filter file

[ http://jira.codehaus.org/browse/MRESOURCES-18?page=all ] Kenney Westerhof updated MRESOURCES-18: --- Version: 2.2 2.1 Fix Version: 2.2 This bug exists in 2.1 and 2.2-20060403.015736-1. However, the latest version in svn doe

[jira] Closed: (MRESOURCES-18) System properties and cmdline params not filtered without filter file

[ http://jira.codehaus.org/browse/MRESOURCES-18?page=all ] Kenney Westerhof closed MRESOURCES-18: -- Assign To: Kenney Westerhof Resolution: Fixed Added a regression test it0105 in svn revision 398452. This should ideally be moved to the pl

[jira] Reopened: (MASSEMBLY-14) assembly plugin does not include dependencies for all artifacts in reactor.

[ http://jira.codehaus.org/browse/MASSEMBLY-14?page=all ] Kenney Westerhof reopened MASSEMBLY-14: --- There are some major issues with this commit (revision 327855). The only way to run the assembly plugin in a reactor is to bind it to the lifecycl

[jira] Commented: (MNG-2280) Make inheritance of reports configurable

[ http://jira.codehaus.org/browse/MNG-2280?page=comments#action_64854 ] Kenney Westerhof commented on MNG-2280: --- The report plugins already have a tag . What you're doing here is not really configure inheritance - you're specifying wheter modules (if

[jira] Created: (MSITE-129) modules list empty if modules don't use this project as parent in reactor build

modules list empty if modules don't use this project as parent in reactor build --- Key: MSITE-129 URL: http://jira.codehaus.org/browse/MSITE-129 Project: Maven 2.x Site Plugin Type: Bug

[jira] Updated: (MANTRUN-51) Can't find plugin dependency in multiproject

[ http://jira.codehaus.org/browse/MANTRUN-51?page=all ] Kenney Westerhof updated MANTRUN-51: Description: I'm using antrun in my project to create an IzPack installation. The plugin configuration is below. When maven is run from the top-level pr

[jira] Commented: (MANTRUN-49) seems ignoring classpath

[ http://jira.codehaus.org/browse/MANTRUN-49?page=comments#action_65189 ] Kenney Westerhof commented on MANTRUN-49: - First, use the xdoclet-maven-plugin. It's an extension to the antrun plugin that contains all the needed xdoclet dependencies. Secon

[jira] Updated: (MDEP-2) Sibling Dependency Not Included in copy-dependencies output during multi-project build

[ http://jira.codehaus.org/browse/MDEP-2?page=all ] Kenney Westerhof updated MDEP-2: Fix Version: (was: 1.0) 1.1 > Sibling Dependency Not Included in copy-dependencies output during > multi-project build > --

[jira] Closed: (MDEP-1) multi-module builds don't unpack-dependencies with dependency-maven-plugin:1.0

[ http://jira.codehaus.org/browse/MDEP-1?page=all ] Kenney Westerhof closed MDEP-1: --- Resolution: Fixed Fix Version: 1.1 > multi-module builds don't unpack-dependencies with dependency-maven-plugin:1.0 > ---

[jira] Closed: (MDEP-2) Sibling Dependency Not Included in copy-dependencies output during multi-project build

[ http://jira.codehaus.org/browse/MDEP-2?page=all ] Kenney Westerhof closed MDEP-2: --- Assign To: Kenney Westerhof (was: Brian Fox) Resolution: Fixed Fix Version: 1.0 Fixed in svn revision 1896. This is a plugin bug only, it has nothing to d

[jira] Commented: (MDEP-2) Sibling Dependency Not Included in copy-dependencies output during multi-project build

[ http://jira.codehaus.org/browse/MDEP-2?page=comments#action_65207 ] Kenney Westerhof commented on MDEP-2: - Hm, indeed, the maven repo has one too. It is NOT moved, it is copied! Where's my cluebat... :) Shall we delete the dependency from the mojo pr

[jira] Updated: (MNG-2293) maven-plugin-descriptor: Not possible to define a default implementation for a field defined by its interface

[ http://jira.codehaus.org/browse/MNG-2293?page=all ] Kenney Westerhof updated MNG-2293: -- Attachment: (was: testcase.diff) > maven-plugin-descriptor: Not possible to define a default implementation for > a field defined by its interface > -

[jira] Commented: (MSITE-129) modules list empty if modules don't use this project as parent in reactor build

[ http://jira.codehaus.org/browse/MSITE-129?page=comments#action_65334 ] Kenney Westerhof commented on MSITE-129: Hi John, You're quite right. In effect, there are 2 trees, which usually overlap: the parent->child(module) tree, and the child->parent

[jira] Closed: (MNG-2282) If a repo is down, maven stops the buid instead of trying other repos

[ http://jira.codehaus.org/browse/MNG-2282?page=all ] Kenney Westerhof closed MNG-2282: - Assign To: Kenney Westerhof Resolution: Fixed fixed in revision 406673: also catch TransferFailedException in maven-wagon-manager's DefaultWagonManager, s

[jira] Closed: (MNG-2295) Stack trace is printed during download when a SocketException happens

[ http://jira.codehaus.org/browse/MNG-2295?page=all ] Kenney Westerhof closed MNG-2295: - Assign To: Kenney Westerhof Resolution: Fixed Fix Version: 2.0.5 All global fatal errors are printed as stacktraces. After fixing MNG-2285, which is

[jira] Closed: (MNG-2282) If a repo is down, maven stops the buid instead of trying other repos

[ http://jira.codehaus.org/browse/MNG-2282?page=all ] Kenney Westerhof closed MNG-2282: - Resolution: Fixed merged changes to the 2.0.x branch. > If a repo is down, maven stops the buid instead of trying other repos > ---

[jira] Commented: (MNG-2206) bad properties interpolation with profiles

[ http://jira.codehaus.org/browse/MNG-2206?page=comments#action_65638 ] Kenney Westerhof commented on MNG-2206: --- I don't see any 'activeByDefault' in the issue description. If you activate both profiles then currently they're both activated, which is

[jira] Created: (MNG-2309) Profile activation order is random

Profile activation order is random -- Key: MNG-2309 URL: http://jira.codehaus.org/browse/MNG-2309 Project: Maven 2 Type: Bug Components: Reactor and workspace Versions: 2.0, 2.0.1, 2.0.2, 2.0.3, 2.0.4 Environment: all

[jira] Closed: (MNG-2309) Profile activation order is random

[ http://jira.codehaus.org/browse/MNG-2309?page=all ] Kenney Westerhof closed MNG-2309: - Assign To: Kenney Westerhof Resolution: Fixed Fix Version: 2.1 2.0.5 Fixed in trunk revision 408021. Merged in 2.0.x branch in revi

[jira] Commented: (MEJB-6) Make the ejb-jar.xml deployment descriptor optional

[ http://jira.codehaus.org/browse/MEJB-6?page=comments#action_65790 ] Kenney Westerhof commented on MEJB-6: - Having a version tag is definitely the way to go. There's a maven-ejb3-plugin in the sandbox, for quite some time now, which created an ejb3 arc

[jira] Created: (MPH-13) Show _ALL_ plugins and settings in help:effective-pom

Show _ALL_ plugins and settings in help:effective-pom - Key: MPH-13 URL: http://jira.codehaus.org/browse/MPH-13 Project: Maven 2.x Help Plugin Type: Improvement Reporter: Kenney Westerhof Currently running 'm

[jira] Commented: (MSUREFIRE-115) Classloading problem for getting a resource

[ http://jira.codehaus.org/browse/MSUREFIRE-115?page=comments#action_66152 ] Kenney Westerhof commented on MSUREFIRE-115: API doc for java.lang.Class: {noformat} public ClassLoader getClassLoader() Returns the class loader for the class. So

<    1   2   3   4   5