[jira] Commented: (MNG-2940) Add a method to the embedder to list available versions of an artifact

[ http://jira.codehaus.org/browse/MNG-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99740 ] Jason van Zyl commented on MNG-2940: So what? It's wrong. Who cares what the existing signature is? The question is whether

[jira] Commented: (MNG-2940) Add a method to the embedder to list available versions of an artifact

[ http://jira.codehaus.org/browse/MNG-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99738 ] Carlos Sanchez commented on MNG-2940: - It encapsulates ArtifactMetadataSource.retrieveAvailableVersions and uses the same s

[jira] Commented: (MNG-763) consider include source root

[ http://jira.codehaus.org/browse/MNG-763?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99732 ] Jason van Zyl commented on MNG-763: --- What does this mean exactly? > consider include source root > ---

[jira] Closed: (MNG-574) Add version info to plugins.xml and cache that in plugin-registry.xml

[ http://jira.codehaus.org/browse/MNG-574?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-574. - Resolution: Fixed registry is not used anymore > Add version info to plugins.xml and cache that in plugin-registr

[jira] Updated: (MNG-2938) Build error is ignored at the end of the build

[ http://jira.codehaus.org/browse/MNG-2938?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-2938: --- Affects Version/s: (was: 2.1-alpha-1) 2.1.x Fix Version/s: (was: Review

[jira] Closed: (MNG-1259) clean up/fix the plugin registry

[ http://jira.codehaus.org/browse/MNG-1259?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-1259. -- Resolution: Fixed It's gone from 2.1.x. > clean up/fix the plugin registry >

[jira] Moved: (DOXIA-119) How to deal with encoding and documentation

[ http://jira.codehaus.org/browse/DOXIA-119?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl moved MNG-1371 to DOXIA-119: -- Fix Version/s: (was: Documentation) Component/s: (was: Documentation: Gui

[jira] Closed: (MNG-2956) The documentation refers to system property "user.dir" when it should refer to "user.home"

[ http://jira.codehaus.org/browse/MNG-2956?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-2956. -- Resolution: Incomplete Tell us where, or the report of pretty much useless. > The documentation refers to syst

[jira] Commented: (MNG-2940) Add a method to the embedder to list available versions of an artifact

[ http://jira.codehaus.org/browse/MNG-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99719 ] Jason van Zyl commented on MNG-2940: I reviewed this and 1) Why multiple remote repositories? An artifact should only be a

[jira] Updated: (MNG-2940) Add a method to the embedder to list available versions of an artifact

[ http://jira.codehaus.org/browse/MNG-2940?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-2940: --- Affects Version/s: (was: 2.1-alpha-1) 2.1.x > Add a method to the embedder to list

[jira] Closed: (MNG-2943) Same package name is used in different modules

[ http://jira.codehaus.org/browse/MNG-2943?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-2943. -- Resolution: Fixed One bundle will be used, and no one wants to change all the packages around to satisfy OSGi

[jira] Updated: (MNG-2935) settings.xml errors are ignored

[ http://jira.codehaus.org/browse/MNG-2935?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-2935: --- Assignee: Jason van Zyl Affects Version/s: (was: 2.1-alpha-1) 2.1.x

[jira] Closed: (MNG-2886) Dynamically includes dependencies if subfolder is available

[ http://jira.codehaus.org/browse/MNG-2886?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-2886. -- Resolution: Fixed You must be explicit and that's the way it will stay. Adding a directory should not change m

[jira] Updated: (MNG-2875) Maven does not honour Plexus component lifecycles in embedded environment for singleton-keep-alive components

[ http://jira.codehaus.org/browse/MNG-2875?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-2875: --- Fix Version/s: (was: Reviewed Pending Version Assignment) 2.1.x Component/s:

[jira] Closed: (MNG-2779) Inconsistent dependency scope resolution

[ http://jira.codehaus.org/browse/MNG-2779?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-2779. -- Resolution: Incomplete Provide a sample project that demonstrates the problem. > Inconsistent dependency scope

[jira] Closed: (MNG-2810) Create a Windows Installer and update instructions on download site

[ http://jira.codehaus.org/browse/MNG-2810?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-2810. -- Resolution: Won't Fix Third parties can make installers, for example you can get one from Mergere. We're not p

[jira] Closed: (MNG-2791) Error parsing Maven 1 POM file with an extend tag

[ http://jira.codehaus.org/browse/MNG-2791?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-2791. -- Resolution: Fixed We don't parse m1 POMs. > Error parsing Maven 1 POM file with an extend tag > --

[jira] Closed: (MNG-2856) Maven Archetype Plugin Changes PNG images

[ http://jira.codehaus.org/browse/MNG-2856?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-2856. -- Resolution: Duplicate General binary resource filtering has already been raised in ARCHETYPE. > Maven Archetyp

[jira] Updated: (MNG-2966) Use optional transitive dependencies versions as dependencyManagement does

[ http://jira.codehaus.org/browse/MNG-2966?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-2966: --- Fix Version/s: (was: Reviewed Pending Version Assignment) 2.1.x > Use optional transit

[jira] Closed: (MNG-2526) Getting started sample fails several times, then it works suddenly

[ http://jira.codehaus.org/browse/MNG-2526?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-2526. -- Resolution: Cannot Reproduce Generally due to load on ibiblio but should not be the case anymore with the new

[jira] Closed: (MNG-2511) Need ability to redefine distribution management url

[ http://jira.codehaus.org/browse/MNG-2511?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-2511. -- Resolution: Fixed For deployment you can now specify and alternative distribution repository. The release plug

[jira] Updated: (MNG-2889) Generic readModel method missing in embedder

[ http://jira.codehaus.org/browse/MNG-2889?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-2889: --- Fix Version/s: (was: Reviewed Pending Version Assignment) 2.1.x > Generic readModel me

[jira] Commented: (MNG-2588) Rewrite of the maven-jdeveloper-plugin to use classes for IDE like in the Eclipse plugins

[ http://jira.codehaus.org/browse/MNG-2588?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99709 ] Jason van Zyl commented on MNG-2588: This is a not a core maven issue. Where do we want to put this stuff? > Rewrite of the

[jira] Commented: (MNG-2565) plugin version aren't taken from pluginManagement in a sub-sub-modules

[ http://jira.codehaus.org/browse/MNG-2565?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99708 ] Jason van Zyl commented on MNG-2565: Is this an issue? Or can this be closed? > plugin version aren't taken from pluginMana

[jira] Closed: (MNG-2559) Module Selection From Command Line Argument Broken

[ http://jira.codehaus.org/browse/MNG-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-2559. -- Resolution: Won't Fix > Module Selection From Command Line Argument Broken > --

[jira] Updated: (MNG-2559) Module Selection From Command Line Argument Broken

[ http://jira.codehaus.org/browse/MNG-2559?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl updated MNG-2559: --- Use profiles to define different modules and then invoke the profile with -P. > Module Selection From Command Li

[jira] Closed: (MNG-2602) maven-csharp-source-plugin:process-classes messes up outputDirectory and thereby indirectly messes up release plugin

[ http://jira.codehaus.org/browse/MNG-2602?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-2602. -- Resolution: Won't Fix This is not one of our plugins. Request to move it, as it looks more like an NMaven issu

[jira] Commented: (MNG-1436) Unable to load maven-model-2.0-all from a plugin

[ http://jira.codehaus.org/browse/MNG-1436?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99705 ] Jason van Zyl commented on MNG-1436: Brett, so can this be closed? > Unable to load maven-model-2.0-all from a plugin > ---

[jira] Closed: (MNG-2972) Ignores version of plugin dependency specified in my pom

[ http://jira.codehaus.org/browse/MNG-2972?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-2972. -- Resolution: Won't Fix This is not how plugin dependencies work. You actually specify the dependencies inside t

[jira] Closed: (MNG-2466) resursive build - modules using always using pom.xml

[ http://jira.codehaus.org/browse/MNG-2466?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Jason van Zyl closed MNG-2466. -- Resolution: Fixed Won't fix. You should use profiles to use different sets of dependencies and behavior. Encou

[jira] Commented: (MJAVADOC-106) Dependencies with scope "runtime" or "provided" are not used in the javadoc classpath

[ http://jira.codehaus.org/browse/MJAVADOC-106?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99699 ] Adam Hardy commented on MJAVADOC-106: - I am trying to run javadoc on the tests in my src/test/java directory, and I fin

[jira] Closed: (MNG-2434) Local snapshots should be preferred over remote ones

[ http://jira.codehaus.org/browse/MNG-2434?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kenney Westerhof closed MNG-2434. - Resolution: Fixed Fix Version/s: (was: Reviewed Pending Version Assignment)

[jira] Commented: (MNG-2434) Local snapshots should be preferred over remote ones

[ http://jira.codehaus.org/browse/MNG-2434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99698 ] Kenney Westerhof commented on MNG-2434: --- Thanks for testing! Marking this closed and fixed in 2.0.6. > Local snapshots s

[jira] Commented: (MNG-2434) Local snapshots should be preferred over remote ones

[ http://jira.codehaus.org/browse/MNG-2434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99697 ] Carsten Ziegeler commented on MNG-2434: --- Yes, this does not happen with maven 2.0.6 any more, so it seems that this is fi

[jira] Created: (MAVENUPLOAD-1604) release ognl 2.7

release ognl 2.7 Key: MAVENUPLOAD-1604 URL: http://jira.codehaus.org/browse/MAVENUPLOAD-1604 Project: maven-upload-requests Issue Type: Task Reporter: Jesse Kuhnert The 2.7 release has been made to a remote re

[jira] Commented: (MAVENUPLOAD-1603) Upload JIDE Common Layer to maven repository

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99694 ] David Qiao commented on MAVENUPLOAD-1603: - I just double checked. The bundle jar contains jide-oss-2.0.4-sources

[jira] Commented: (MAVENUPLOAD-1603) Upload JIDE Common Layer to maven repository

[ http://jira.codehaus.org/browse/MAVENUPLOAD-1603?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99693 ] Wim Deblauwe commented on MAVENUPLOAD-1603: --- I see that the bundle does not include the sources. This is very

[jira] Commented: (MNG-2434) Local snapshots should be preferred over remote ones

[ http://jira.codehaus.org/browse/MNG-2434?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99688 ] Kenney Westerhof commented on MNG-2434: --- Could this be tested again with 2.0.6? I think there's a fix for another issue

[jira] Closed: (MNG-2448) Can not exclude a dependency from a plugin

[ http://jira.codehaus.org/browse/MNG-2448?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kenney Westerhof closed MNG-2448. - Resolution: Won't Fix Just redeclare the dependency as you normally do inside . Since maven 2.0.5, (or po

[jira] Closed: (MNG-2826) Integration-test target runs integration tests twice

[ http://jira.codehaus.org/browse/MNG-2826?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kenney Westerhof closed MNG-2826. - Resolution: Won't Fix This is not a bug nor an issue; this should've been asked on the users list. what

[jira] Commented: (MNG-2340) Incorrect dependency version downloaded

[ http://jira.codehaus.org/browse/MNG-2340?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99682 ] Kenney Westerhof commented on MNG-2340: --- Maven 2.0.6 and 2.0.7 do it like this: - depMgt provides defaults; so if a child

[jira] Commented: (MNG-2241) Versions are required when it shouldn't with multi-modules projects and war dependencies

[ http://jira.codehaus.org/browse/MNG-2241?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99681 ] Kenney Westerhof commented on MNG-2241: --- Specifying in the dependencies in depMgt for deps that aren't jar should solve

[jira] Updated: (MNG-2915) No way to avoid adding artifactId to site urls

[ http://jira.codehaus.org/browse/MNG-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kenney Westerhof updated MNG-2915: -- Fix Version/s: (was: Reviewed Pending Version Assignment) 2.1-alpha-1 > No way t

[jira] Commented: (MNG-2915) No way to avoid adding artifactId to site urls

[ http://jira.codehaus.org/browse/MNG-2915?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99680 ] Kenney Westerhof commented on MNG-2915: --- Place to fix: maven-project/src/main/java/org/apache/maven/project/inheritance/D

[jira] Commented: (MNG-2199) Version ranges not supported for parent artifacts

[ http://jira.codehaus.org/browse/MNG-2199?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99678 ] Kenney Westerhof commented on MNG-2199: --- tempting to 'close - won't fix'. Whatever parent pom is present in the local rep

[jira] Closed: (MNG-2745) Do not allow System properties to be interpolated in the POM

[ http://jira.codehaus.org/browse/MNG-2745?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kenney Westerhof closed MNG-2745. - Resolution: Duplicate > Do not allow System properties to be interpolated in the POM > --

[jira] Closed: (MNG-3009) Maven 2.0.5+ fails to resolve ${project.version} on deployment

[ http://jira.codehaus.org/browse/MNG-3009?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kenney Westerhof closed MNG-3009. - Resolution: Duplicate > Maven 2.0.5+ fails to resolve ${project.version} on deployment >

[jira] Updated: (MNG-2569) Expressions not evaluated inside

[ http://jira.codehaus.org/browse/MNG-2569?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kenney Westerhof updated MNG-2569: -- Summary: Expressions not evaluated inside (was: The version tag within the parrent block does not ev

[jira] Commented: (MNG-2486) ${project.version} evaluated to timestamped version if referring to SNAPSHOT

[ http://jira.codehaus.org/browse/MNG-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99676 ] Kenney Westerhof commented on MNG-2486: --- This issue deals with the fact that whenever ${project.version} or ${pom.version

[jira] Updated: (MNG-2486) ${project.version} evaluated to timestamped version if referring to SNAPSHOT

[ http://jira.codehaus.org/browse/MNG-2486?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kenney Westerhof updated MNG-2486: -- Assignee: (was: Kenney Westerhof) Affects Version/s: 2.1-alpha-1

[jira] Commented: (MNG-2339) ${project.*} are interpreted in the wrong place

[ http://jira.codehaus.org/browse/MNG-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99673 ] Kenney Westerhof commented on MNG-2339: --- This issue deals with ${project.version}, or ${version}, or ${xxx.version} for t

[jira] Closed: (MNG-2647) Version not inherited for SNAPSHOT version

[ http://jira.codehaus.org/browse/MNG-2647?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kenney Westerhof closed MNG-2647. - Resolution: Duplicate > Version not inherited for SNAPSHOT version >

[jira] Closed: (MNG-2796) Yet another snapshot/timestamp version resolution problem

[ http://jira.codehaus.org/browse/MNG-2796?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kenney Westerhof closed MNG-2796. - Resolution: Duplicate > Yet another snapshot/timestamp version resolution problem > -

[jira] Closed: (MNG-2782) Version property in dependencies is not expanded correctly

[ http://jira.codehaus.org/browse/MNG-2782?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kenney Westerhof closed MNG-2782. - Resolution: Duplicate > Version property in dependencies is not expanded correctly >

[jira] Closed: (MNG-2653) using ${version} for subproject dependencies doesn't work (maven uses 2.4.1 version instead)

[ http://jira.codehaus.org/browse/MNG-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kenney Westerhof closed MNG-2653. - Assignee: Kenney Westerhof (was: Jason van Zyl) Resolution: Duplicate > using ${version} for subpr

[jira] Closed: (MNG-2651) POM interpolator treats ${pom.something} like ${something} and prefers system properties

[ http://jira.codehaus.org/browse/MNG-2651?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kenney Westerhof closed MNG-2651. - Resolution: Duplicate > POM interpolator treats ${pom.something} like ${something} and prefers system >

[jira] Closed: (ARCHETYPE-78) Dependencies listed as version ${project.version} in maven-archetype prevent the use of archetypes

[ http://jira.codehaus.org/browse/ARCHETYPE-78?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kenney Westerhof closed ARCHETYPE-78. - Resolution: Fixed Fix Version/s: 1.0 Dupe of MNG-2339. Fixed by removing ${project.ve

[jira] Updated: (MNG-2339) ${project.*} are interpreted in the wrong place

[ http://jira.codehaus.org/browse/MNG-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kenney Westerhof updated MNG-2339: -- Fix Version/s: (was: 2.0.6) 2.0.8 > ${project.*} are interpreted in the wrong pl

[jira] Reopened: (MNG-2339) ${project.*} are interpreted in the wrong place

[ http://jira.codehaus.org/browse/MNG-2339?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Kenney Westerhof reopened MNG-2339: --- this is not fixed. > ${project.*} are interpreted in the wrong place > -

[jira] Commented: (MNG-2653) using ${version} for subproject dependencies doesn't work (maven uses 2.4.1 version instead)

[ http://jira.codehaus.org/browse/MNG-2653?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99667 ] Kenney Westerhof commented on MNG-2653: --- I'm tempted to 'close - won't fix'. ${version} is evaluated to either a system pr

[jira] Commented: (ARCHETYPE-78) Dependencies listed as version ${project.version} in maven-archetype prevent the use of archetypes

[ http://jira.codehaus.org/browse/ARCHETYPE-78?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99666 ] Kenney Westerhof commented on ARCHETYPE-78: --- This is caused by the fact that -Dversion=0.1 is provided on the comm

[jira] Commented: (MNG-3001) Maven2 does not resolve version ranges correctly [PATCH INCLUDED]

[ http://jira.codehaus.org/browse/MNG-3001?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel#action_99664 ] Kenney Westerhof commented on MNG-3001: --- I think the specificiation is wrong. [1.0,) should resolve to 1.0, 1.0.1-SNAPSHO