[jira] Commented: (MASSEMBLY-29) Possibility to aggrates sources from other modules

[ http://jira.codehaus.org/browse/MASSEMBLY-29?page=comments#action_61362 ] Allan Ramirez commented on MASSEMBLY-29: You mean that all the sources from the submodules would be bundled into one jar? > Possibility to aggrates sources from other modules

[jira] Updated: (MWAR-26) Do not overwrite target unless source is modified

[ http://jira.codehaus.org/browse/MWAR-26?page=all ] John Tolentino updated MWAR-26: --- Attachment: MWAR-26-maven-war-plugin-2.diff > Do not overwrite target unless source is modified > - > > Key: MWAR

[jira] Closed: (MEV-255) Problem with junit-addons 1.4

[ http://jira.codehaus.org/browse/MEV-255?page=all ] Carlos Sanchez closed MEV-255: -- Resolution: Fixed > Problem with junit-addons 1.4 > - > > Key: MEV-255 > URL: http://jira.codehaus.org/browse/MEV-255 >

[jira] Closed: (MWAR-26) Do not overwrite target unless source is modified

[ http://jira.codehaus.org/browse/MWAR-26?page=all ] Edwin Punzalan closed MWAR-26: -- Resolution: Fixed Patch applied. Thanks. > Do not overwrite target unless source is modified > - > > Key: MWA

[jira] Created: (MIDEA-39) In a multi-module project, idea plugin should generate module dependencies instead of creating libs with references to the repository

In a multi-module project, idea plugin should generate module dependencies instead of creating libs with references to the repository - Key: MIDEA-39

[jira] Created: (MJAVADOC-61) Adding custom source paths to javadoc

Adding custom source paths to javadoc - Key: MJAVADOC-61 URL: http://jira.codehaus.org/browse/MJAVADOC-61 Project: Maven 2.x Javadoc Plugin Type: New Feature Versions: 2.0-beta-3 Environment: FedoreCore 4 kernel 2.6.10-1.

[jira] Created: (CONTINUUM-634) Add notion of top level project with modules to prevent notification floods

Add notion of top level project with modules to prevent notification floods --- Key: CONTINUUM-634 URL: http://jira.codehaus.org/browse/CONTINUUM-634 Project: Continuum Type: Improvement Compo

[jira] Commented: (MNG-2050) Classloader.getResource() doesn't encode blanks

[ http://jira.codehaus.org/browse/MNG-2050?page=comments#action_61369 ] Roland Kofler commented on MNG-2050: I am not a comitter but a simple user that discovered this issue. > Classloader.getResource() doesn't encode blanks > --

[jira] Commented: (MNG-2050) Classloader.getResource() doesn't encode blanks

[ http://jira.codehaus.org/browse/MNG-2050?page=comments#action_61370 ] Carlos Sanchez commented on MNG-2050: - I think you are misunderstanding something. When do you execute getClass().getClassLoader().getResource(s), in a maven plugin , in a unit tes

[jira] Commented: (MNG-2050) Classloader.getResource() doesn't encode blanks

[ http://jira.codehaus.org/browse/MNG-2050?page=comments#action_61371 ] Carlos Sanchez commented on MNG-2050: - and have you tried 2.0.2 ? > Classloader.getResource() doesn't encode blanks > --- > > Key

[jira] Commented: (MIDEA-34) Add resources to source folders instead of module libraries

[ http://jira.codehaus.org/browse/MIDEA-34?page=comments#action_61372 ] Geoffrey De Smet commented on MIDEA-34: --- 1)One problem with setting resources as a source filter was that IntelliJ filters it's source dirs and doesn't include png etc by default.

[jira] Commented: (SCM-153) Continuum fails while trying to build from clearcase

[ http://jira.codehaus.org/browse/SCM-153?page=comments#action_61374 ] Kjetil Ødegaard commented on SCM-153: - I don't know if this is related, but I also get the "A registry entry already exists" every time I try to build a ClearCase project from Continu

[jira] Created: (MNGECLIPSE-88) doesn't make use of ~/.m2/settings.xml

doesn't make use of ~/.m2/settings.xml -- Key: MNGECLIPSE-88 URL: http://jira.codehaus.org/browse/MNGECLIPSE-88 Project: Maven 2.x Extension for Eclipse Type: Improvement Versions: 0.0.5 Environment: linux Reporter: J

[jira] Created: (MNG-2156) maven-jar-plugin doesn't accept element in configuration

maven-jar-plugin doesn't accept element in configuration --- Key: MNG-2156 URL: http://jira.codehaus.org/browse/MNG-2156 Project: Maven 2 Type: Bug Components: Plugins and Lifecycle Version

[jira] Commented: (MNG-2156) maven-jar-plugin doesn't accept element in configuration

[ http://jira.codehaus.org/browse/MNG-2156?page=comments#action_61375 ] Sachin Patel commented on MNG-2156: --- The element works, the plugin documentation is incorrect and should be updated. The manifestFile element needs to be specified under not under

[jira] Closed: (MNGECLIPSE-88) doesn't make use of ~/.m2/settings.xml

[ http://jira.codehaus.org/browse/MNGECLIPSE-88?page=all ] Eugene Kuleshov closed MNGECLIPSE-88: - Resolution: Duplicate > doesn't make use of ~/.m2/settings.xml > -- > > Key: MNGECLIPSE-88 >

[jira] Created: (MPLUGIN-14) Document how to define new lifecycle

Document how to define new lifecycle Key: MPLUGIN-14 URL: http://jira.codehaus.org/browse/MPLUGIN-14 Project: Maven 2.x Plugin Plugin Type: Improvement Versions: 2.1 Reporter: Andreas Ebbert-Karroum Please update th

[jira] Commented: (MNG-2050) Classloader.getResource() doesn't encode blanks

[ http://jira.codehaus.org/browse/MNG-2050?page=comments#action_61380 ] Gili commented on MNG-2050: --- Yes, this is being executed in a unit test and it is failing horribly :) Works perfectly in Maven 1 though. Yes, I have tried 2.0.2 and it has the same problem.

[jira] Updated: (MNG-32) Plugin test harness

[ http://jira.codehaus.org/browse/MNG-32?page=all ] Jesse McConnell updated MNG-32: --- Attachment: maven-project.patch > Plugin test harness > --- > > Key: MNG-32 > URL: http://jira.codehaus.org/browse/MNG-32 > Project:

[jira] Commented: (MNGECLIPSE-59) Allow artifact resolution from workspace projects

[ http://jira.codehaus.org/browse/MNGECLIPSE-59?page=comments#action_61392 ] Jochen Kuhnle commented on MNGECLIPSE-59: - I tried applying the attached patch (EclipseArtifactResolver.patch), but it seems garbled starting with line 862. Looks like a co

[jira] Created: (MEV-360) nanocontainer has invalid xpp3 dependency

nanocontainer has invalid xpp3 dependency - Key: MEV-360 URL: http://jira.codehaus.org/browse/MEV-360 Project: Maven Evangelism Type: Improvement Components: Dependencies Reporter: Wayne Fay http://www.ibiblio.org/ma

[jira] Commented: (MEV-360) nanocontainer has invalid xpp3 dependency

[ http://jira.codehaus.org/browse/MEV-360?page=comments#action_61393 ] Wayne Fay commented on MEV-360: --- Oops... That should have been: This should be updated to use a classifier instead: xpp3 xpp3 1.1.3.4 RC8_min > nanoconta

[jira] Created: (MEV-361) picocontainer has invalid xpp3 dependency

picocontainer has invalid xpp3 dependency - Key: MEV-361 URL: http://jira.codehaus.org/browse/MEV-361 Project: Maven Evangelism Type: Improvement Components: Dependencies Reporter: Wayne Fay http://www.ibiblio.org/ma

[jira] Commented: (MNGECLIPSE-59) Allow artifact resolution from workspace projects

[ http://jira.codehaus.org/browse/MNGECLIPSE-59?page=comments#action_61396 ] Mark J. Sinke commented on MNGECLIPSE-59: - Jochen, I apologize for the issue with the patch file. I'll try and fix the patch this weekend or the Monday after and upload a

[jira] Commented: (MNG-1665) allow changing plexus components implementations dynamically through embedder

[ http://jira.codehaus.org/browse/MNG-1665?page=comments#action_61397 ] Mark J. Sinke commented on MNG-1665: Milos, That is exactly right. The Plexus Embedder that is passed to lookupComponents is preloaded with the maven-embedder plexus.xml and depende

[jira] Created: (MPCHANGELOG-85) Download of changelog plugin fails due to unresolved artifact

Download of changelog plugin fails due to unresolved artifact - Key: MPCHANGELOG-85 URL: http://jira.codehaus.org/browse/MPCHANGELOG-85 Project: maven-changelog-plugin Type: Bug Reporter: Markus Klink

[jira] Created: (MECLIPSE-78) create eclipse projects which are m2eclipse ready

create eclipse projects which are m2eclipse ready - Key: MECLIPSE-78 URL: http://jira.codehaus.org/browse/MECLIPSE-78 Project: Maven 2.x Eclipse Plugin Type: New Feature Environment: Fedora Core 3, Sun JDK 1.5.0.06, E

[jira] Updated: (MECLIPSE-78) create eclipse projects which are m2eclipse ready

[ http://jira.codehaus.org/browse/MECLIPSE-78?page=all ] Joshua Nichols updated MECLIPSE-78: --- Attachment: m2eclipse.patch > create eclipse projects which are m2eclipse ready > - > > Key: MECLIPSE

[jira] Created: (MRAR-4) Rar Plugin should allow the user to set "rarName" like "jarName" in Jar Plugin

Rar Plugin should allow the user to set "rarName" like "jarName" in Jar Plugin -- Key: MRAR-4 URL: http://jira.codehaus.org/browse/MRAR-4 Project: Maven 2.x Rar Plugin Type: New Feature

[jira] Commented: (MNGECLIPSE-87) Enabling Maven on a project does not change the context sensitive menu

[ http://jira.codehaus.org/browse/MNGECLIPSE-87?page=comments#action_61408 ] Robert Elliot commented on MNGECLIPSE-87: - Narrowed it down - it's J2EE Standard Tools (JST) 1.0.1 that causes the problem. And it definitely does it to the Spring plugin,

[jira] Updated: (MNG-1954) Need better handling of malformed poms in local cache, like check for an update every run

[ http://jira.codehaus.org/browse/MNG-1954?page=all ] ruel loehr updated MNG-1954: Attachment: MNG-1954.txt > Need better handling of malformed poms in local cache, like check for an > update every run > -

[jira] Commented: (MNG-1954) Need better handling of malformed poms in local cache, like check for an update every run

[ http://jira.codehaus.org/browse/MNG-1954?page=comments#action_61410 ] ruel loehr commented on MNG-1954: - I made a patch which resolves the above issue. When the defaultArtifactResolver is handed an artifact to resolve, if that artifact is already located

[jira] Commented: (MNGECLIPSE-87) Enabling Maven on a project does not change the context sensitive menu

[ http://jira.codehaus.org/browse/MNGECLIPSE-87?page=comments#action_61411 ] Robert Elliot commented on MNGECLIPSE-87: - Eclipse bug here: https://bugs.eclipse.org/bugs/show_bug.cgi?id=132419 > Enabling Maven on a project does not change the context

[jira] Commented: (MPJALOPY-10) Jalopy removes import statements

[ http://jira.codehaus.org/browse/MPJALOPY-10?page=comments#action_61413 ] Lukas Theussl commented on MPJALOPY-10: --- The jalopy plugin 1.3.1 works fine for me (m11b3, java 1.4.2, Linux FC3), but I can't get it to work with the jalopy 1.5b5 or 1.5rc3 rel

[jira] Commented: (MPJALOPY-9) Jalopy Classes not found

[ http://jira.codehaus.org/browse/MPJALOPY-9?page=comments#action_61414 ] Lukas Theussl commented on MPJALOPY-9: -- I am not sure this is the right fix for this problem: how can the root classloader fix a ClassCastException? I checked that going back to t

[jira] Created: (MNG-2157) Properties defined in top-level profiles.xml do no propagate to child modules

Properties defined in top-level profiles.xml do no propagate to child modules - Key: MNG-2157 URL: http://jira.codehaus.org/browse/MNG-2157 Project: Maven 2 Type: Bug Components: POM

[jira] Commented: (MASSEMBLY-64) jar-with-dependencies has a last-one-copies-wins policy which can fail signed jars

[ http://jira.codehaus.org/browse/MASSEMBLY-64?page=comments#action_61420 ] Napoleon Esmundo C. Ramirez commented on MASSEMBLY-64: -- The reason why you get that SecurityException when running the uberjar is because of all the security fil