On Tue 7 Nov 2017 at 01:18, Charles Honton wrote:
> So doesn’t this require a new directive such as ‘ transitive=false”> scope or similar regardless of safe/rally points?
No. The plugin would have its descriptor metadata for the goal contain a
flag
Then the plugin is responsible for deciding w
On Tue 7 Nov 2017 at 01:32, Charles Honton wrote:
> Are these integration test for the plugin or do the integration tests use
> the plugin?
The integration tests use the plugin. (Though there are other use cases too)
If the former, then the invoker plugin is appropriate. If the latter, then
>
Are these integration test for the plugin or do the integration tests use the
plugin? If the former, then the invoker plugin is appropriate. If the latter,
then a non-code, non-transitive dependency scope is a possibility. Again, this
new scope has the backwards compatibility problem..
> On
So doesn’t this require a new directive such as ‘
scope or similar regardless of safe/rally points? And to provide backwards
compatibility, there must be a split between the legacy consumer view of the
pom and the new producer view of the pom?
> On Nov 5, 2017, at 11:30 PM, Stephen Connolly
Thinking some more, this might be something we could leverage for
incremental builds.
If we save state at the end of each phase (last modified time stamps, hash
of dependencies, etc, also attached artifacts, additional source/resource
roots etc) then, on subsequent builds, if the state file is pre
Samsung Galaxy-smartphone.
> Oorspronkelijk bericht Van: Stephen Connolly <
> stephen.alan.conno...@gmail.com> Datum: 05-11-17 18:57 (GMT+01:00) Aan:
> Maven Developers List Onderwerp: Reactor
> safe/rally points
> There are two sets of problems that, assuming we want to
On Mon 6 Nov 2017 at 01:48, Charles Honton wrote:
> Both these use cases sound like adding incredible complexity to support
> less than 1% situations, and worse, encouraging monolithic builds.
>
> In the first case, the module creating a shaded jar can mark its
> constituent jars as optional; pre
Both these use cases sound like adding incredible complexity to support less
than 1% situations, and worse, encouraging monolithic builds.
In the first case, the module creating a shaded jar can mark its constituent
jars as optional; preventing the transitive dependencies.
In the second case,
alaxy-smartphone.
Oorspronkelijk bericht Van: Stephen Connolly
Datum: 05-11-17 18:57 (GMT+01:00) Aan:
Maven Developers List Onderwerp: Reactor safe/rally
points
There are two sets of problems that, assuming we want to fix, both need
some way to rally a concurrent multimodule
alaxy-smartphone.
Oorspronkelijk bericht Van: Stephen Connolly
Datum: 05-11-17 18:57 (GMT+01:00) Aan:
Maven Developers List Onderwerp: Reactor safe/rally
points
There are two sets of problems that, assuming we want to fix, both need
some way to rally a concurrent multimodule
There are two sets of problems that, assuming we want to fix, both need
some way to rally a concurrent multimodule build at.
1. There is the shade like class of problems, where a plugin wants to
modify the effective transitive dependencies of a module.
2. There is the extensibility class of probl
11 matches
Mail list logo
