you can file it in core component. Emmanuel
[EMAIL PROTECTED] said: > > > > > Brett, have you filled an issue in JIRA for this, or should I do it? If > so, > in which component? > > - Fabrice > >> Yes, it sounds like a bug. The version in plugin management should be > used. >> >> -U is only for when the version is unspecified. >> >> - Brett >> >> On 11/4/05, fabrice belingard wrote: >> > >> > OK, but then, the question is: the version of a plugin declared in the >> > <pluginManagement> section is not part of its "configuration"? I mean, > if I >> > have the following in my POM: >> > >> > <build> >> > ... >> > <pluginManagement> >> > <plugins> >> > ... >> > <plugin> >> > > <groupId>org.apache.maven.plugins</groupId> >> > >> > <artifactId>maven-surefire-plugin</artifactId> >> > <version>2.0</version> >> > </plugin> >> > </plugins> >> > </pluginManagement> >> > </build> >> > >> > , doesn't that mean that I want my subprojects to use version 2.0 of > the >> > surefire plugin? >> > It seems that it doesn't, as Maven does not try to download this > version >> > but uses the 2.0-beta-1 that is installed locally... > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
