I'd tested, but it was only SVN which appears to work.
I think it might be better to introduce the methods to Repository in
maven.mdo. I'll do this all together at some point today.
Thanks,
Brett
Arnaud HERITIER wrote:
Hi all,
I worked a little bit on this problem.
My idea, is that it could be better to copy existing services (getScmType, ...)
about SCM repositories from maven 1.0.2 core to the
maven 1.1 one (in an utilities class for example).
But if we do that we'll not be able to keep the compatibility for the xdoc
plugin with maven 1.1 and maven 1.0.2.
Thus I think that actually it is more interesting to have this code in the xdoc
plugin.
Thoughts ?
Arnaud
Hi guys,
Yesterday night I found a new issue with the xdoc plugin
and maven 1.1.
The generated cvs-usage page is empty.
I quickly look at the problem and I think I found its origin.
In maven 1.0, we defined our own model for the POM, and
some services were added to the beans representing POM elements.
For exemple in org.apache.maven.project.Repository we
found a method getScmType().
With the new generated maven-model we don't have this method.
Or it is used in the template for cvs-usage.
I haven't yet open an issue but what do you think about this ?
Should we bypass this problem and warn users about this
problem in maven beta 1.
Should we fix it before the beta 1 ? in the xdoc plugin
or in maven core ??
Arnaud
---------------------------------------------------------------------
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]
