Re: org.codehaus.mojo: scmchangelog-maven-plugin problems

[Remy Sanlaville]

Hi Martin,

Thanks for your interest about our scmchangelog-maven-plugin

It's better to send you request to the mojo-user mailing list rather than to us.
Some other people can help you and it can also help other people which
have the same problem.

> I have been trying to get your scm changes plugin to work with no success.
> I have attached a log file. It appears to be me that the xml output from the
> svn log is incorrectly parsed and therefore all I get are the names of the
> tags, branches and trunk without any history whatsoever.
>
> Perhaps you could help me?

It seems that you forget to attached your log file.
Could you please send us your log ?

Which maven version do you use ?
Our plugin does not works anymore with maven 2.0.x due to doxia.
We added an enforcer rule for that (available just in svn for the moment).

> Another question - why  are you depending on the existence of the svn binary?
> Is there a licensing issue? I am quite familiar with SVNKit, and you can produce
> these reports with it.

It's because maven community asked us to use Maven-SCM
see http://jira.codehaus.org/browse/MCHANGES-78 for more details
"we have Maven-SCM for all scm communications and we must use it in
maven plugins."

Rémy

---------------------------------------------------------------------
To unsubscribe from this list, please visit:

    http://xircles.codehaus.org/manage_email

[ehsavoie]

Hi,
For the svn in the $PATh this is because at that time we can't use Maven SCM since it is missing some attributes (the XML log for svn and the fact that I need the BetterChangeset instead of their ChangeSet) but the code is more than just similar, it is just an adaptation. SVNKit should be a problem, but I am not very familiar with it and I did'nt have time to look into it, but of course any help is welcome.
I am surprised by the XML parsing erreor, as we use Subversion own schemas to generate the parsing code. Maybe it has evolved since, but that would surprise me ? It seems like there is n exception thrown could you please give us the traces so we could see where the issue comes from ? Maybe you could create a JIRA issue o you could attach your log file (and your SVNKit patch :-P )
Emmanuel

On Thu, Nov 5, 2009 at 4:32 PM, Rémy Sanlaville <remy.sanlaville@...> wrote:

Hi Martin,

Thanks for your interest about our scmchangelog-maven-plugin

It's better to send you request to the mojo-user mailing list rather than to us.
Some other people can help you and it can also help other people which
have the same problem.

> I have been trying to get your scm changes plugin to work with no success.
> I have attached a log file. It appears to be me that the xml output from the
> svn log is incorrectly parsed and therefore all I get are the names of the
> tags, branches and trunk without any history whatsoever.
>
> Perhaps you could help me?

It seems that you forget to attached your log file.
Could you please send us your log ?

Which maven version do you use ?
Our plugin does not works anymore with maven 2.0.x due to doxia.
We added an enforcer rule for that (available just in svn for the moment).

> Another question - why  are you depending on the existence of the svn binary?
> Is there a licensing issue? I am quite familiar with SVNKit, and you can produce
> these reports with it.

It's because maven community asked us to use Maven-SCM
see http://jira.codehaus.org/browse/MCHANGES-78 for more details
"we have Maven-SCM for all scm communications and we must use it in
maven plugins."

Rémy

[ehsavoie]

Hi,
Rémy sent me your log file.It looks like your  commetns are not respecting the grammar format which explains why the messages are not displayed. If you use the ALL grammar all the messages should appear. Could you please try it ?
Emmanuel

On Fri, Nov 6, 2009 at 11:58 AM, Emmanuel Hugonnet <ehsavoie73@...> wrote:

Hi,
For the svn in the $PATh this is because at that time we can't use Maven SCM since it is missing some attributes (the XML log for svn and the fact that I need the BetterChangeset instead of their ChangeSet) but the code is more than just similar, it is just an adaptation. SVNKit should be a problem, but I am not very familiar with it and I did'nt have time to look into it, but of course any help is welcome.
I am surprised by the XML parsing erreor, as we use Subversion own schemas to generate the parsing code. Maybe it has evolved since, but that would surprise me ? It seems like there is n exception thrown could you please give us the traces so we could see where the issue comes from ? Maybe you could create a JIRA issue o you could attach your log file (and your SVNKit patch :-P )
Emmanuel

On Thu, Nov 5, 2009 at 4:32 PM, Rémy Sanlaville <remy.sanlaville@...> wrote:

Hi Martin,

Thanks for your interest about our scmchangelog-maven-plugin

It's better to send you request to the mojo-user mailing list rather than to us.
Some other people can help you and it can also help other people which
have the same problem.

> I have been trying to get your scm changes plugin to work with no success.
> I have attached a log file. It appears to be me that the xml output from the
> svn log is incorrectly parsed and therefore all I get are the names of the
> tags, branches and trunk without any history whatsoever.
>
> Perhaps you could help me?

It seems that you forget to attached your log file.
Could you please send us your log ?

Which maven version do you use ?
Our plugin does not works anymore with maven 2.0.x due to doxia.
We added an enforcer rule for that (available just in svn for the moment).

> Another question - why  are you depending on the existence of the svn binary?
> Is there a licensing issue? I am quite familiar with SVNKit, and you can produce
> these reports with it.

It's because maven community asked us to use Maven-SCM
see http://jira.codehaus.org/browse/MCHANGES-78 for more details
"we have Maven-SCM for all scm communications and we must use it in
maven plugins."

Rémy

[ehsavoie]

This is expected, as your comments don't respect any grammar we can't extract the bug id and so include a link to the bug.
If you could provide a regexp to extract your issue ids this would work.
By the way, I am not familiar with JIRA integration with SVN, if you could provide such information we would gladly integrate it into our plugin.
Emmanuel

On Fri, Nov 6, 2009 at 5:13 PM, Martin Todorov <carlspring@...> wrote:

Hi Emmanuel,

Thanks!

This has solved the SVN log problem I was running into.

Now I am facing another problem - there are no JIRA issues/links in the produced reports.
I have an isssueManagement described as follows:
    <issueManagement>
        <system>JIRA</system>
        <url>http://myJira/jira/BrowseProject.jspa?id=10390</url>

        <!--<url>http://myJira/jira/browse/UICC</url>-->
        <!--<url>https://myJira/jira/browse/UICC?report=com.atlassian.jira.plugin.system.project:changelog-panel</url>-->
    </issueManagement>

And the settings for the plugin are as follows

            <plugin>
                <groupId>org.codehaus.mojo</groupId>
                <artifactId>scmchangelog-maven-plugin</artifactId>
                <version>1.3</version>

                <configuration>
                    <trackerType>jira</trackerType>
                    <trackerUrlPattern>http://myJira/jira/BrowseProject.jspa?id=10390</trackerUrlPattern>

                    <connectionUrl>scm:svn:https://mySVN/subversion/uicc/production/hpl2/trunk/</connectionUrl>
                    <tagBase>https://mySVN/subversion/uicc/production/hpl2/tags/</tagBase>
                    <grammar>ALL</grammar>

                </configuration>
            </plugin>

There is no output concerning the JIRA links whatsoever, so I can't attach a useful log.

Maybe I haven't configured something...?

My JIRA and SVN usernames/passwords are different and I can't change them. Could this be the problem?

Thanks again and I hope you have some more hints!
All the best,

Martin

On Fri, Nov 6, 2009 at 3:18 PM, Emmanuel Hugonnet <ehsavoie73@...> wrote:

Hi,
Rémy sent me your log file.It looks like your  commetns are not respecting the grammar format which explains why the messages are not displayed. If you use the ALL grammar all the messages should appear. Could you please try it ?
Emmanuel

On Fri, Nov 6, 2009 at 11:58 AM, Emmanuel Hugonnet <ehsavoie73@...> wrote:

Hi,
For the svn in the $PATh this is because at that time we can't use Maven SCM since it is missing some attributes (the XML log for svn and the fact that I need the BetterChangeset instead of their ChangeSet) but the code is more than just similar, it is just an adaptation. SVNKit should be a problem, but I am not very familiar with it and I did'nt have time to look into it, but of course any help is welcome.
I am surprised by the XML parsing erreor, as we use Subversion own schemas to generate the parsing code. Maybe it has evolved since, but that would surprise me ? It seems like there is n exception thrown could you please give us the traces so we could see where the issue comes from ? Maybe you could create a JIRA issue o you could attach your log file (and your SVNKit patch :-P )
Emmanuel

On Thu, Nov 5, 2009 at 4:32 PM, Rémy Sanlaville <remy.sanlaville@...> wrote:

Hi Martin,

Thanks for your interest about our scmchangelog-maven-plugin

It's better to send you request to the mojo-user mailing list rather than to us.
Some other people can help you and it can also help other people which
have the same problem.

> I have been trying to get your scm changes plugin to work with no success.
> I have attached a log file. It appears to be me that the xml output from the
> svn log is incorrectly parsed and therefore all I get are the names of the
> tags, branches and trunk without any history whatsoever.
>
> Perhaps you could help me?

It seems that you forget to attached your log file.
Could you please send us your log ?

Which maven version do you use ?
Our plugin does not works anymore with maven 2.0.x due to doxia.
We added an enforcer rule for that (available just in svn for the moment).

> Another question - why  are you depending on the existence of the svn binary?
> Is there a licensing issue? I am quite familiar with SVNKit, and you can produce
> these reports with it.

It's because maven community asked us to use Maven-SCM
see http://jira.codehaus.org/browse/MCHANGES-78 for more details
"we have Maven-SCM for all scm communications and we must use it in
maven plugins."

Rémy