My comments are inline, and I've added another idea to the bottom.
Please, read on! :)
Thanks,
--john
On Jul 12, 2007, at 9:46 PM, Piotr Tabor wrote:
* medium_real_project: (153,151,150,151 seconds) - YES - THREE
TIME LONGER - I am also in shock
So I am sure - we cannot just comment
a) and c) seem like essentially the same amount of work (to code and to
execute) but c) feels cleaner.
-Original Message-
From: Piotr Tabor [mailto:[EMAIL PROTECTED]
Sent: Thursday, July 12, 2007 9:46 PM
To: Maven Developers List
Subject: Re: MNG-1323 - discussion about available fixes
I prepare more statistics:
I tested the problem on two projects:
* it0124 (from MNG-1323) ( 3 artifacts)
* medium_real_project(40 artifacts)
The current version on maven (2.0.8-SNAPSHOT) with "-X -o":
it0124 : 9 seconds; 8 seconds; 9 seconds (all didn't finish
I prepare more statistics:
I tested the problem on two projects:
* it0124 (from MNG-1323) ( 3 artifacts)
* medium_real_project(40 artifacts)
The current version on maven (2.0.8-SNAPSHOT) with "-X -o":
it0124 : 9 seconds; 8 seconds; 9 seconds (all didn't finish
I will prepare detailed statistics tonight. The statistic bellow was
from "dirty" environment (eclipse, another processes working, etc.).
Thanks,
Piotr
Carlos Sanchez pisze:
> I have seen other caching problems when using the embedder, like
> plugin versions not updated if the pom changes. I wou
I'd tend to agree, though caching in some situations has been the
only thing to save us from some serious API shortcomings. For
example, the fact that you cannot access the MavenProject instance
corresponding to a resolved Artifact...the cache in the project
builder is the only thing keepin
I have seen other caching problems when using the embedder, like
plugin versions not updated if the pom changes. I would go for
correctness first and speed second
On 7/12/07, John Casey <[EMAIL PROTECTED]> wrote:
So, if we don't ever cache the plugin container, it's a 2-second
penalty on a singl
So, if we don't ever cache the plugin container, it's a 2-second
penalty on a single project using debug output with corrected algorithm?
-john
On Jul 12, 2007, at 11:29 AM, Piotr Tabor wrote:
John Casey pisze:
While #3 might have the best performance in terms of speed, I really
wonder abo
John Casey pisze:
> While #3 might have the best performance in terms of speed, I really
> wonder about memory performance. Leaving all those old antrun plugin
> instances laying around but still reachable means that in very large
> projects that use antrun, we'll have some pretty significant memor
e go to the model of reloading (or
loading new) plugin containers...
-john
On Jul 12, 2007, at 1:43 AM, Piotr Tabor wrote:
Hi,
I'm working on http://jira.codehaus.org/browse/MNG-1323. It's issue
with
24 votes and many other issues depending on it. It's fully repeatable
(h
Hi,
I'm working on http://jira.codehaus.org/browse/MNG-1323. It's issue with
24 votes and many other issues depending on it. It's fully repeatable
(has attached maven-integration-test)
and there are some ways to fix it.
Business (user's) problem:
The problem is that mav
r, read
the previous answers
and don't use the dev list for user questions
On 5/2/07, Petr V. wrote:
>
> I am using 2.0.6 and still hitting this issue.
>
> http://jira.codehaus.org/browse/MNG-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:changehistory-tabpanel
>
> Has
asking the same question over and over won't give you an answer, read
the previous answers
and don't use the dev list for user questions
On 5/2/07, Petr V. <[EMAIL PROTECTED]> wrote:
I am using 2.0.6 and still hitting this issue.
http://jira.codehaus.org/brow
I am using 2.0.6 and still hitting this issue.
http://jira.codehaus.org/browse/MNG-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:changehistory-tabpanel
Has this been fixed? Any help would be really appreciated.
I can run mvn install from sub project directory but from root project
ìt's open so no, it's not fixed
On 5/2/07, Petr V. <[EMAIL PROTECTED]> wrote:
I am using 2.0.6 and still hitting this issue.
http://jira.codehaus.org/browse/MNG-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:changehistory-tabpanel
Has this been fixed? Any help
I am using 2.0.6 and still hitting this issue.
http://jira.codehaus.org/browse/MNG-1323?page=com.atlassian.jira.plugin.system.issuetabpanels:changehistory-tabpanel
Has this been fixed? Any help would be really appreciated.
I can run mvn install from sub project directory but from root project
[ 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
[ http://jira.codehaus.org/browse/MNG-1323?page=comments#action_54948 ]
Brett Porter commented on MNG-1323:
---
workaround is to include the dependency in the first antrun plugin instance
encountered. one way to guarantee would be to include this in the root
[ http://jira.codehaus.org/browse/MNG-1323?page=comments#action_54941 ]
ruel loehr commented on MNG-1323:
-
Are there any suggested work arounds for this issue?Hence, if I wish to use
a custom ant task in a child module (which would require a dependency
[ 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
[ http://jira.codehaus.org/browse/MNG-1323?page=comments#action_54612 ]
Georges Polyzois commented on MNG-1323:
---
Is this beeing resolved? I have exactly this problem as Kenney stated on
04/Nov/05.
I am using Maven 2.0.1 and even changed to using
[ 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
[ http://jira.codehaus.org/browse/MNG-1323?page=comments#action_50268 ]
John Casey commented on MNG-1323:
-
It looks like some of the work I did to get the ant-mojo support up and running
was related to this. Kenney's 04/Nov/2005 post was related to m
[ http://jira.codehaus.org/browse/MNG-1323?page=all ]
Kenney Westerhof reopened MNG-1323:
---
The issue is a bit different - i got it reproducible now.
It seems, in the following situation:
root/pom.xml, modules: a, b
a/pom.xml: define antrun
[ 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
[ http://jira.codehaus.org/browse/MNG-1323?page=comments#action_50012 ]
Kenney Westerhof commented on MNG-1323:
---
I don't think so - inheritance doesn't play a role. The parent-pom is just an
empty pom stating 1 module -> the pom discusse
[ http://jira.codehaus.org/browse/MNG-1323?page=all ]
Brett Porter updated MNG-1323:
--
Description:
I've added a dependency on an Ant Task in
project/build/plugins/plugin[artifactId='maven-antrun-plugin']/dependencies/
and run that an
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
29 matches
Mail list logo
