Thanks Brian,
Here's the result of 'mvn dependency:analyze' on the beta-3 code:
[INFO] [dependency:analyze]
[INFO] Used declared dependencies:
[INFO] org.apache.maven:maven-settings:jar:2.0.4:compile
[INFO] org.apache.maven.doxia:doxia-core:jar:1.0-alpha-9:compile
[INFO] org.apache.maven.reporting:maven-reporting-impl:jar:2.0.4:compile
[INFO] commons-lang:commons-lang:jar:2.1:compile
[INFO] javax.mail:mail:jar:1.4:compile
[INFO] org.codehaus.plexus:plexus-velocity:jar:1.1.7:compile
[INFO] org.apache.maven.doxia:doxia-site-renderer:jar:1.0-alpha-9:compile
[INFO] org.apache.maven.reporting:maven-reporting-api:jar:2.0.4:compile
[INFO] commons-httpclient:commons-httpclient:jar:3.0.1:compile
[INFO] Used undeclared dependencies:
[WARNING] junit:junit:jar:3.8.1:compile
[WARNING] velocity:velocity-dep:jar:1.4:runtime
[WARNING] plexus:plexus-utils:jar:1.0.2:compile
[WARNING] org.apache.maven:maven-plugin-api:jar:2.0.4:compile
[WARNING] plexus:plexus-container-default:jar:1.0-alpha-6:compile
[WARNING] plexus:plexus-mail-sender-api:jar:1.0-alpha-2:compile
[WARNING] org.apache.maven:maven-project:jar:2.0.4:compile
[WARNING] xml-apis:xml-apis:jar:1.0.b2:compile
[WARNING] org.apache.maven:maven-model:jar:2.0.4:compile
[WARNING] org.apache.maven.doxia:doxia-sink-api:jar:1.0-alpha-7:compile
[INFO] Unused declared dependencies:
[INFO] commons-logging:commons-logging:jar:1.1:compile
[INFO]
org.apache.maven.doxia:doxia-decoration-model:jar:1.0-alpha-9:compile
[INFO] commons-collections:commons-collections:jar:3.0:compile
[INFO] plexus:plexus-mail-sender-simple:jar:1.0-alpha-2:compile
[INFO]
org.codehaus.plexus:plexus-container-default:jar:1.0-alpha-20:compile
[INFO] plexus:plexus-mail-sender-javamail:jar:1.0-alpha-2:compile
[INFO] velocity:velocity:jar:1.4:compile
[WARNING] Potential problems discovered.
I guess that the presence of
[WARNING] "plexus:plexus-container-default:jar:1.0-alpha-6:compile"
is a bad sign?
Is the right way to fix this, to excluding this from whichever
dependency is pulling it in?
I'll try to run 'mvn package -X' and see is I can find where it's coming
from, or is there an easier/better way?
Brian E. Fox wrote:
Take a look to see if the new container stuff is sneaking in and confusing
things. I had lots of trouble with dependency, but was able to sort it out
using exclusions and the enforcer to warn me.
-----Original Message-----
From: Stephane Nicoll [mailto:[EMAIL PROTECTED]
Sent: Sunday, September 16, 2007 11:41 AM
To: Maven Developers List
Subject: Re: [VOTE] release maven-changes-plugin 2.0-beta-3
Arg. Crap. I fixed many things but I haven't that one.
Plexus dependencies seem to change all the time across alpha's, this
is very confusing. Thanks for the report, Dennis, I'm rolling it back.
Stéphane
On 9/16/07, Dennis Lundberg <[EMAIL PROTECTED]> wrote:
-1
The plugin doesn't work properly in its current state. There is a
problem in the dependency chain that I haven't been able to fully track
down the cause of.
Steps to reproduce:
- Install maven-changes-plugin 2.0-beta-3 into your local repository
- Check out the trunk of maven-changes-plugin
- Alter the reporting section of the pom to use maven-changes-plugin,
version 2.0-beta-3.
- Run "mvn site" using Maven 2.0.7, 2.0.6, 2.0.5 or 2.0.4
(those are the ones I tried)
Results:
[ERROR] BUILD ERROR
[INFO]
------------------------------------------------------------------------
[INFO] Error getting reports from the plugin
'org.apache.maven.plugins:maven-changes-plugin': Unable to find the mojo
'org.apache.maven.plugins:maven-changes-plugin:2.0-beta-3:changes-report'
in the plugin 'org.apache.maven.plugins:maven-changes-plugin'
org/codehaus/plexus/util/xml/XmlStreamReader
Solution:
By adding this dependency to the pom I was able to get the site build again:
<dependency>
<groupId>org.codehaus.plexus</groupId>
<artifactId>plexus-utils</artifactId>
<version>1.4.5</version>
</dependency>
However, that only works in 2.0.6 and 2.0.7, which has a shaded version
of plexus-utils.
I haven't been able to find out which dependency is using
org/codehaus/plexus/util/xml/XmlStreamReader, if that is the cause of
the problem.
Stephane Nicoll wrote:
Hi,
I'd like to release maven-changes-plugin 2.0-beta-3. Significant fixes
are available in trunk and the latest release is almost one year old.
Release Notes - Maven 2.x Changes Plugin - Version 2.0-beta-3
** Bug
* [MCHANGES-1] - Annoucement generates announcement for wrong type
of package
* [MCHANGES-9] - HTML inside <action/> is swallowed
* [MCHANGES-11] - improve error reporting when changes.xml not found
* [MCHANGES-13] - Exception thrown when running
changes:announcement-generate
* [MCHANGES-16] - release history hyperlinks don't work
* [MCHANGES-19] - bad URL/404 on JIRA report results in exception
* [MCHANGES-23] - docs should use short goal names
* [MCHANGES-50] - Handle JIRA authentication failure
* [MCHANGES-51] - Table not correctly closed in
ChangesReportGenerator#constructActions()
* [MCHANGES-54] - jira-report with filter specified gives 500 error
* [MCHANGES-56] - Default announcement.vm doesn't check issue type
correctly.
* [MCHANGES-57] - How does the plugin know what issues were fixed
in this version?
* [MCHANGES-63] - Custom filters can not be added to a JIRA query.
* [MCHANGES-64] - The changes plugin should not push an "external
link" image into the output renderer
* [MCHANGES-68] - The changes plugin uses anchors and links that
don't match.
* [MCHANGES-70] - NPE if the version attribute is not set properly
in the changes.xml file
** Improvement
* [MCHANGES-49] - javax.mail dependency should be optional
* [MCHANGES-55] - Add ability to turn off download URL in email
* [MCHANGES-77] - Document the variables available to the
announcement template.
* [MCHANGES-81] - Use a less noisy version of plexus-velocity
* [MCHANGES-87] - Ability to specify the mail sender explicitely
** New Feature
* [MCHANGES-25] - I'd like to have changes:announcement-mail be
able to support authentication
* [MCHANGES-26] - Allow user to create custom velocity template
for announcement
* [MCHANGES-27] - Add 'disable jira' flag
* [MCHANGES-28] - Renderer html code provided in an action record
* [MCHANGES-79] - Allow for overriding the announcement email from address
The staging bits are available here:
http://people.apache.org/~snicoll/maven-staging/repo/org/apache/maven/plugins/
Votes open for 72 hours.
My +1
Thanks,
Stéphane
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
