Re: svn commit: r1604930 - in /maven/plugins/trunk/maven-dependency-plugin/src: it/mdep-450-project-with-ancestor/ it/mdep-450-project-without-ancestor/ main/java/org/apache/maven/plugin/dependency/ s

useful info but couldn't it be added to dependency:tree, instead of a new goal? here is actual output [1] parents could be added before actual dependencies, in reverse order: parent-of-parent parent pom \- dependency WDYT? Regards, Hervé [1] http://svn.apache.org/repos/asf/maven/plugins/trunk

[GitHub] maven-shared pull request: MSHARED-341: New API to support to anal...

GitHub user wangyf2010 opened a pull request: https://github.com/apache/maven-shared/pull/8 MSHARED-341: New API to support to analyze artifact's dependencies Need new API to analyze artifact's dependencies too. Later could leverage this API to enhance maven-dependency-plugin to

maven-scm-provider-gitexe test failures

Hi I am running into test failures Linux: ( git version 1.7.9.5) Failed tests: GitCheckInCommandNoBranchTest.testCheckinNoBranch:75->ScmTestCase.assertResult GitCheckInCommandTest.testCheckinAfterRename:113->ScmTestCase.assertResultIsSu windows ( cygwin gitt version 1.7.9) Failed tests: Git

Re: Maven Developer Hangout

Same time? I guess this will drive me to get out of bed and in the office early :) On 24 Jun 2014, at 5:28, Jason van Zyl wrote: Here's the link for the developer hangout this week. Hopefully we can continue the conversation about the evolution of the POM: https://plus.google.com/u/0/events/

Re: "supplies" concept proposal (was "provides" could be "proffers")

Write up your proposal and start a separate thread for it... no hijacking ;-) On 21 June 2014 15:48, Benson Margulies wrote: > At the risk of redundancy, my favorite was the scm element. We > implement or consider all kinds of nasty kludges to sneak scm-specific > information through the tiny

Re: "supplies" concept proposal (was "provides" could be "proffers")

*http://jira.codehaus.org/browse/MNG-5652 * On 21 June 2014 15:28, Jason van Zyl wrote: > Throw it into a JIRA and tag the component FDPFC. I can only find 8 issues > related to features requiring POM format changes. I seem to recall more. > > On Jun 20

[PROPOSAL] Advanced Lifecycle Handling

PROPOSAL 1: PerProject and PerPhase Executions I've recently introduced the installAtEnd/deployAtEnd as an experimental feature which should improve the behavior of Maven without having to wait for the implementation in Maven Core, which would have a huge impact. The reason is that you only w

Re: [mojo-dev] Re: MVERSIONS-258 Add mojo display-ancestors which will output the line of heritage for parent poms

OK, I just moved this issue to https://jira.codehaus.org/browse/MDEP-450. On Mon, Jun 23, 2014 at 1:08 AM, Stephen Connolly wrote: > Ancestors are dependencies, you cannot build a project without its parent... > You just don't reference them in a dependencies section is all! > > I think it actual

Maven Developer Hangout

Here's the link for the developer hangout this week. Hopefully we can continue the conversation about the evolution of the POM: https://plus.google.com/u/0/events/c1hfpekl285un5rkmgt10iijpf0 We switched the day to Thursday based on feedback. Thanks, Jason -

Re: [VOTE] Release Apache Maven JAR Plugin version 2.5

Hi, the vote has passed with the following result: +1 (binding): Hervé Boutemy, Robert Scholte, Oliver Lamy. 0: none -1: none I will promote the artifacts to Maven Central. Many thanks. Kind regards Karl-Heinz Marbaise > Hi, We solved 10 issues: http://jira.codehaus.org/secure/ReleaseNote

Re: Inject Maven components/parameters to Plexus components

Thanks a lot for the clarification Jason, much more than appreciated! All the best! -Simo http://people.apache.org/~simonetripodi/ http://twitter.com/simonetripodi On Mon, Jun 23, 2014 at 3:00 PM, Jason van Zyl wrote: > The short answer is that you can't right now. We do not create bindings in

Re: Inject Maven components/parameters to Plexus components

The short answer is that you can't right now. We do not create bindings in the normal JSR330 for configuration injection, we historically use a tool called the PluginParameterExpressionEvaluator to pass over the component once it's instantiated. We did this long before we used any container. As

Inject Maven components/parameters to Plexus components

Hi all mates, I am a little lost and I would like to kindly ask you if anyone knows how to request, via Plexus annotations, the injection of Maven parameters/components. While for components I guess it is more or less the same as in MOJOs, just using different kind annotations, it is not clear to