Sounds good, I'll happily switch to the link to the SVN changelog, and
keep quiet about it and hope you never get around to doing the second
part. :)
I still think you're adding more complexity for something that won't
gain that much more benefit, however the idea you're planning (svn
commits automatically updating the website) could be useful for other
things, so if you want to guinea pig the Change Log page I guess that's
OK. However, I'm not sure we would want to link website updates and the
running of SiteGeneratorTest (if I understand you correctly), as mvn
test -Dtest=SiteGeneratorTest has so far for me been a common command to
run, I don't think we'd want the website to update on account of anybody
running that command (if that's your plan). Perhaps using the
maven-exec-plugin to run a separate class (outside the tests) would be a
cleaner implementation.
Glen
On 06/15/2013 10:38 AM, Juan Pablo Santos RodrÃguez wrote:
Hi,
my idea was to move the site as another submodule, so every time a mvn
clean install is done, the site would keep updated b/c of SiteGeneratorTest
(there's a infra's JIRA on this, but I feel I'd better move that with
[email protected]). OTOH, I agree that linking directly to svn's changelog is way
better than having oudated info / manually repopulating the site
I'm having a sprained shoulder, so I'm somewhat limited when coding,
probably until next week, but let's do this: let's link to svn's changelog
right now so we display updated information. In the meantime, I'll make the
appropiate changes to automatically populate the site so we can have both a
nice and automatically up to date changelog page (the idea behind this was
to give contributions/contributors more visibility). Sounds reasonable?
rgrds,
juan pablo
On Sat, Jun 15, 2013 at 3:40 PM, Harry Metske <[email protected]>wrote:
Glen,
can't remember why we wanted this link , but a direct link to the svn
changelog file looks better to me too.
regards,
Harry
On 15 June 2013 15:33, Glen Mazza <[email protected]> wrote:
Hi JP, our website ChangeLog has fallen out of date:
http://incubator.apache.org/**jspwiki/development/changelog.**html<
http://incubator.apache.org/jspwiki/development/changelog.html>Again, can
we just switch to a link to our SVN repository of the changelog
file ( http://svn.apache.org/viewvc/**incubator/jspwiki/trunk/**
ChangeLog?view=co<
http://svn.apache.org/viewvc/incubator/jspwiki/trunk/ChangeLog?view=co>)
so it's always up-to-date 24/7? That should be sufficient, given that
the
vast majority of Apache projects don't even bother linking to a changelog
file to begin with. I don't see the project as having the time or
resources for busywork secretarial tasks like maintaining two ChangeLog
files. The time you have been devoting to this in order to have a HTML
change log that looks 10% better seems to well failing cost/benefit
analysis, especially since it's even out-of-date, so now it's *worse*
than
just directly linking to SVN.
Thanks,
Glen
<http://incubator.apache.org/**jspwiki/development/changelog.**html<
http://incubator.apache.org/jspwiki/development/changelog.html>
