If you don't log the error thrown back here it gets lost in a sea of backtraces.

This should help let users diagnose changelog problems for themselves


git-svn-id: https://svn.apache.org/repos/asf/maven/maven-1/plugins/trunk@112862 13f79535-47bb-0310-9956-ffa450edef68

changelog/src/main/org/apache/maven/changelog/ChangeLog.java

@@ -87,7 +87,7 @@ import org.apache.maven.project.Developer;
  * @author <a href="mailto:dion@multitask.com.au">dIon Gillard</a>
  * @author <a href="mailto:bodewig@apache.org">Stefan Bodewig</a>
  * @author <a href="mailto:peter@apache.org">Peter Donald</a>
- * @version $Id: ChangeLog.java,v 1.2 2003/02/07 11:47:13 evenisse Exp $
+ * @version $Id: ChangeLog.java,v 1.3 2003/02/08 23:53:13 bwalding Exp $
  */
 public class ChangeLog
 {
@@ -249,6 +249,9 @@ public class ChangeLog
                 LOG.info("ChangeLog found: " + getEntries().size() 
                     + " entries");
             }
+        } catch (IOException e) {
+            LOG.warn(e.getLocalizedMessage(), e);
+            throw e;
         }
         finally
         {