Hi
Roland Asmann wrote:
Another request about this plugin:
Would it be possible to change the newlines in the comments to <br/>-tags in
HTML? We sometimes use lists to summarize our changes in files and these
lists become pretty much unreadable in HTML without the line-breaks.
I've added this request to JIRA:
http://jira.codehaus.org/browse/MCHANGELOG-59
Thanks.
On Monday 26 March 2007 11:26, Roland Asmann wrote:
OK, so I found it... the 'basedir' parameter for the changelog-plugin
points to the source-dir per default. If I change that to
${project.basedir} I indeed get all changes.
Maybe this should be changed as the default setting?
On Monday 26 March 2007 11:08, Roland Asmann wrote:
On Saturday 24 March 2007 17:33, Dennis Lundberg wrote:
Roland Asmann wrote:
Hi,
I thought the changelog-plugin might do some nice things for me, but
I've got a feeling it's not doing exactly what it is supposed to
do... So, my question would be: Am i right if I say that the plugin
ONLY checks changes on projects that have java-sources?
No, that's wrong. It checks for changes to all files in your SCM
system.
I wanted to use the plugin on a small project we have, that bundles
only Resources for use in multiple other projects (and we don't want
to copy the Resources around, that's the thing we use the
dependencies in Maven for!). Is this a bug in the plugin or is it
really planned to work this way?
You probably haven't configured your SCM system correctly in your
pom.xml file.
Here is the configuration, which should be fine in my opinion... I mean,
how come the source-changes ARE found with the current configuration and
the other changes aren't?
<scm>
<connection>scm:cvs:pserver:maven:[EMAIL PROTECTED]:/applications:cfc-bugzilla
-p lugin</connection>
<developerConnection>scm:cvs:pserver:${cvs.username}:
[EMAIL PROTECTED]:/applications:cfc-bugzilla-plugin</developerConnec
ti on> </scm>
As for the configuration of the changelog-plugin:
<configuration>
<type>tag</type>
<tags>
<tag>${artifactId}-${previous.tag.version}</tag>
</tags>
</configuration>
And yes, the variable ${previous.tag.version} is defined, so that's also
not the problem!
Also, I personally would like to see ALL changes, even those in the
POM, since those can have some rather big impacts on a project as
well!
Wow, I only planned to ask 1 question, ended up with 2 and a half
(well, sort of)... Anyway, thanks for any info you guys can give me
on this!
--
Dennis Lundberg
---------------------------------------------------------------------
To unsubscribe, e-mail: [EMAIL PROTECTED]
For additional commands, e-mail: [EMAIL PROTECTED]
