ote:
>
> > any reference to what you call "project dependency"?
> > how is it different from a classic dependency? a dependency in a reactor?
> >
> > Regards,
> >
> > Hervé
> >
> > Le mercredi 11 juin 2014 17:18:05 Simon Wang a écrit :
>
^_^
sorry for that, just don't know what's the status for it.
Regards
Simon
2014-06-12 5:54 GMT+08:00 Karl Heinz Marbaise :
> Hi Simon,
>
> you seemed to be very impatient...
>
> Kind regards
> Karl-Heinz...
>
> BTW: I will take care within the next few days...
>
>
>
> > May I know who is hand
I can't attend it, but +1. ^_^
Things are changing faster. Maven need to change also.
It's better to have a considerate roadmap for maven:
I tried about one month on gradle, lots of interesting ideas that maven
could reference:
1. stable incremental build
2. project dependency support
3. elegant
Since we're thinking about model-5.0.
Is it possible to support project dependency in 5.0?
Project dependency could benefit users a lot.
They needn't care about whether others dependent projects(might changed)
are installed or not.
And users needn't always run maven build with parent pom.
Regards
May I know who is handling this PR?
https://github.com/apache/maven-enforcer/pull/13
any comments or concerns?
Regards
Simon
2014-05-30 10:38 GMT+08:00 Wang YunFeng :
> Hi, Karl,
>
> Real case happened in our company is:
> There are bunch of repositories using. For specific application, need t
