Re: Rationale behind non-standard dependency scopes

2013-07-30 Thread Francesco Mari
abused for what is really a marker question for > plugins, IMHO > > > On 30 July 2013 15:39, Francesco Mari wrote: > >> Correct. I don't want to duplicate the configuration twice, the first >> time in my plugin and the second time in the section to >> let Maven c

Re: Rationale behind non-standard dependency scopes

2013-07-30 Thread Francesco Mari
Correct. I don't want to duplicate the configuration twice, the first time in my plugin and the second time in the section to let Maven correctly compute the build plan. 2013/7/30 Stephen Connolly : > On 30 July 2013 14:23, Francesco Mari wrote: > >> I missed to describe my use

Re: Rationale behind non-standard dependency scopes

2013-07-30 Thread Francesco Mari
pache/sling/maven/projectsupport/LaunchpadPluginLifecycleParticipant.java 2013/7/30 Francesco Mari : > I missed to describe my use case. I will try to do it as detailed as I > can, but it can be quite verbose. > > I have a project which is built by aggregating other artifacts with > diff

Re: Rationale behind non-standard dependency scopes

2013-07-30 Thread Francesco Mari
is > automatically excluded from transitive dependencies. > > But what I'd really like to understand is what you think you need these > custom scopes for... because perhaps I am being arrogant and assuming I > have thought of all the valid use cases and you can show me the

Rationale behind non-standard dependency scopes

2013-07-30 Thread Francesco Mari
Hi, I was wondering why using custom dependency scopes issues a warning when the POM model is validated. Why Maven just don't ignore dependecy scopes he cannot understand? I was thinking to treat dependency scopes in a different way. The only logic I've found about dependency scopes is in [1] and

Re: Passing information between goals

2013-07-24 Thread Francesco Mari
Thank you all for the useful isnights. 2013/7/24 Stephen Connolly > getPluginContext() is the one you want. Use that to stash your info. > > > On 24 July 2013 15:15, Francesco Mari wrote: > > > Thank you for the link, but I don't need to coordinate multiple projects

Re: Passing information between goals

2013-07-24 Thread Francesco Mari
> 2. Easiest way may just be to serialize the value into a string form > and > > > set a project property with a non-maven resolvable name to the string > > > value. For example I do not think it is possible to have a Maven > property > > > start with the null cha

Passing information between goals

2013-07-24 Thread Francesco Mari
Hi, I wrote some MOJOs which use common data. This data depends on the structure of the project and can't be changed at runtime. I would like to compute this information at the beginiing of the build process, and re-use it in each related goal. Ideally, the first goal should compute the data, and

Re: Missing dependencies in Apache Snapshots Repo

2013-02-18 Thread Francesco Mari
Maybe the question is a little bit off-topic, but what's the point in having a mirror on GitHub if you switched to your own git? Do you have any plan for those mirrors? 2013/2/18 Francesco Mari : > I think the issue is that I'm using the GitHub mirror. I think I > should switch

Re: Missing dependencies in Apache Snapshots Repo

2013-02-18 Thread Francesco Mari
t repo and not the old svn repo? > > /Anders > > > On Mon, Feb 18, 2013 at 4:44 PM, Anders Hammar wrote: > >> Those artifacts have been released (v2.4), so we need to update out poms. >> Until then you can do that yourself locally. >> >> /Anders >> >

Missing dependencies in Apache Snapshots Repo

2013-02-18 Thread Francesco Mari
Hi, I tried to build Maven from scratch. I have the following error when building Maven Aether Provider 3.1.-SNAPSHOT: [ERROR] Failed to execute goal on project maven-aether-provider: Could not resolve dependencies for project org.apache.maven:maven-aether-provider:jar:3.1-SNAPSHOT: The following