Brett Porter wrote:
On 11/08/2006 3:20 AM, [EMAIL PROTECTED] wrote:
Modified: maven/plugins/trunk/maven-site-plugin/pom.xml
URL:
http://svn.apache.org/viewvc/maven/plugins/trunk/maven-site-plugin/pom.xml?rev=430446&r1=430445&r2=430446&view=diff
==============================================================================
--- maven/plugins/trunk/maven-site-plugin/pom.xml (original)
+++ maven/plugins/trunk/maven-site-plugin/pom.xml Thu Aug 10 10:20:32
2006
@@ -79,7 +79,7 @@
<dependency>
<groupId>org.apache.maven.reporting</groupId>
<artifactId>maven-reporting-api</artifactId>
- <version>2.0.2</version>
+ <version>2.1-SNAPSHOT</version>
</dependency>
<dependency>
<groupId>org.codehaus.plexus</groupId>
This will block a release of the site plugin until after Maven 2.1,
which is not desirable.
I know. I've posted a mail on this about 7 mails up in the dev list..
Two questions:
a) does this change actually make it always require Maven 2.1, or is it
only if you use the multi page feature that will trigger the code?
Only the latter, actually. But at runtime it will still require the new
code in the maven-reporting-api.
b) can we create a branch for it anyway?
A branch for what, exactly?
I think the answer to a) is that it does, so it needs a <prerequisites>
element, and it also makes b) a must for now.
Please take a look at the full problem description in the other mail.
Maybe we've got a bigger design issue here..
-- Kenney
Cheers,
Brett
---------------------------------------------------------------------
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]
