On 2015-01-11 14:48, Hervé BOUTEMY wrote:
The change does not affect classloading of "normal" maven runtime, so
>there is no need to update the diagram or documentation.
IIUC, in the Wiki, what is currently described as "system classloader" is now
"initial classloader, containing classworlds",
ence/display/MAVEN/Maven+3.x+Class+Loading>
> > Le jeudi 8 janvier 2015 13:09:10 ifedore...@apache.org a écrit :
> >> Repository: maven
> >>
> >> Updated Branches:
> >>refs/heads/master 5f71f9789 -> bb4988496
> >>
> >> better plu
pdated Branches:
refs/heads/master 5f71f9789 -> bb4988496
better plugin/extensions realm parent classloader
Signed-off-by: Igor Fedorenko
Project: http://git-wip-us.apache.org/repos/asf/maven/repo
Commit: http://git-wip-us.apache.org/repos/asf/maven/commit/bb498849
Tree: http://git-wip-u
https://cwiki.apache.org/confluence/display/MAVEN/Maven+3.x+Class+Loading
Le jeudi 8 janvier 2015 13:09:10 ifedore...@apache.org a écrit :
> Repository: maven
> Updated Branches:
> refs/heads/master 5f71f9789 -> bb4988496
>
>
> better plugin/extensions realm parent classloader
>
&g
It is an optimisation to ensure you don't need to look at all of the
plugins first. Possibly a better alternative is to resolve plugins in
two phases (get all the plugins up front, figure this stuff out, get
dependencies of the plugins later when the code is actually executed). I
think that is
Hi,
I was wondering if the true couldn't be auto-detected
by maven by looking at the components.xml in the plugin's jar or something
similar, or wheter it could on by default.
It seems that when a plugin defines packaging/lifecycle extensions and you
do not specify true you get a
ComponentLookup
[ http://jira.codehaus.org/browse/MNG-1323?page=all ]
John Casey updated MNG-1323:
Fix Version: (was: 2.0.3)
2.0.4
> Plugin extensions (dependencies) not resolved in reactor bu
project.
> Plugin extensions (dependencies) not resolved in reactor build
> --
>
> Key: MNG-1323
> URL: http://jira.codehaus.org/browse/MNG-1323
> Project: Maven 2
> Type: Bug
>
upon the
antrun plugin), how would I accomplish it, or is it impossible at this time?
> Plugin extensions (dependencies) not resolved in reactor build
> --
>
> Key: MNG-1323
> URL: http://jira.codehaus
[ http://jira.codehaus.org/browse/MNG-1323?page=comments#action_54633 ]
Brett Porter commented on MNG-1323:
---
note above that this is scheduled for 2.0.3 (Feb release).
> Plugin extensions (dependencies) not resolved in reactor bu
antrun version 1.1-SNAPSHOT -
with no sucess.
> Plugin extensions (dependencies) not resolved in reactor build
> --
>
> Key: MNG-1323
> URL: http://jira.codehaus.org/browse/MNG-1323
> Project: Mave
[ http://jira.codehaus.org/browse/MNG-1323?page=all ]
John Casey updated MNG-1323:
Fix Version: (was: 2.0.1)
2.0.2
> Plugin extensions (dependencies) not resolved in reactor bu
cies in it.
NOW, as for the latest incarnation of the problem, this is undoubtedly caused
by Maven not disposing of plugin containers between project builds. If we did
this, we would have the added benefit of cleaning out plugin-extensions (though
we'd have to be *very* careful about this
, with any tasks (like )
b/pom.xml: define antrun, with section.
When run from 'root', dependencies are not resolved for plugin antrun in
project b.
Probably because the plugin is already 'resolved' the different
for
this instance are not resolved.
> Plugin extens
[ http://jira.codehaus.org/browse/MNG-1323?page=comments#action_50020 ]
Brett Porter commented on MNG-1323:
---
did you test it with 2.0 or 2.0.1? Maybe this should be closed as cannot
reproduce?
> Plugin extensions (dependencies) not resolved in reac
[ http://jira.codehaus.org/browse/MNG-1323?page=all ]
Kenney Westerhof closed MNG-1323:
-
Resolution: Fixed
Somehow the problem has gone away!
> Plugin extensions (dependencies) not resolved in reactor bu
d above.
I'll find the it for it and augment it for this issue.
> Plugin extensions (dependencies) not resolved in reactor build
> --
>
> Key: MNG-1323
> URL: http://jira.codehaus.org/browse
nment:
is this because they are not inherited, rather than anything to do with the
reactor?
> Plugin extensions (dependencies) not resolved in reactor build
> --
>
> Key: MNG-1323
> URL: http://ji
Plugin extensions (dependencies) not resolved in reactor build
--
Key: MNG-1323
URL: http://jira.codehaus.org/browse/MNG-1323
Project: Maven 2
Type: Bug
Components: maven-core
Versions: 2.0
19 matches
Mail list logo
