Hi,

Change logs are not being produced for me when I run mvn site.
I'm using apache-maven-2.0.9

In my pom I have
<scm>
    <connection>scm:svn:https://repo.url/dir1/dir2</connection>
    
<developerConnection>scm:svn:https://repo.url/dir1/dir2</developerConnection>
    <url>https://repo.url/dir1/dir2</url>
  </scm>
 
And also
<reporting>
  <plugins>           
    <plugin>
      <groupId>org.apache.maven.plugins</groupId>
      <artifactId>maven-changelog-plugin</artifactId>                           
     
    </plugin>               
  </plugins>           
</reporting>

Firstly the command
  mvn changelog:changelog
shows
  Executing: svn --non-interactive log -v -r "{2009-02-04 10:51:07 
+0000}:{2009-03-07 10:51:07 +0000}" https://repo.url/dir1/dir2
the change log produced contains
<?xml version="1.0" encoding="ISO-8859-1"?>
<changelog>
    <changeset datePattern="yyyyMMdd HH:mm:ss z" start="20090204 10:51:07 GMT" 
end="20090307 10:51:07 GMT"></changeset>
</changelog>

If I issue the command
  svn --non-interactive log -v -r "{2009-02-04 10:51:07 +0000}:{2009-03-07 
10:51:07 +0000}" https://repo.url/dir1/dir2
the changes are listed   

If I issue the command
  mvn scm:changelog
The following appears on the console
  Executing: cmd.exe /X /C "svn --non-interactive log -v 
https://repo.url/dir1/dir2";
but no changes are listed

If I issue the command
  mvn -X scm:changelog
the changes are listed

and if I run
  cmd.exe /X /C "svn --non-interactive log -v https://repo.url/dir1/dir2";
the changes are also listed

I'm debugging through this locally on windows vista but ultimately I want this 
to work via hudson on a unix box.
Could the use of https in the scm connection be causing problems for maven ? 
but if this was the case mvn -X would not work and it does.
Is there anything else I could try to highlight where the problem could be ?

Many thanks

lgdeveloper



      

---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]

Reply via email to