Re: Taglibs-all Jenkins build

[Konstantin Kolinko <kn...@gmail.com>]

2012/3/19 Jeremy Boynes <jb...@apache.org>:
> On Mar 18, 2012, at 3:33 PM, Jeremy Boynes wrote:
>
>> On Mar 18, 2012, at 10:42 AM, Konstantin Kolinko wrote:
>>
>>> 2012/3/18 Jeremy Boynes <jb...@apache.org>:
>>>> Since this release, I've updated the parent pom to move all the site information into the site module. I plan to fix the duplicate file issue soon. Were there an other issues with the last release before doing V2? If not, I'll also start preparing a release of the tags themselves.
>>>
>>> Do you know, why Taglibs-All [1] at Jenkins is failing?
>>
>> I think it may be because jenkins is checking things out in different location and the relative paths don't work. I think we should remove those now we have a released parent pom and always use the repo version.
>>
>> However, I don't have permission to kick off a build though Jenkins. Could someone please grant me the necessary.
>
> I changed extended and rdc to use the released pom. Hopefully Jenkins will trigger off the commit.
>
> It looks like the Jenkins configuration also includes site but I fail to see the point of that as there's no testing. I suggest we remove it from the config.

I do not know what the original intention was,  but I suppose that it
tests that the site builds OK.
Though it should be possible to remove the Site build from
"Taglibs-All" and configure it as a separate build.

Just recently we had a build failure in Tomcat 7 documentation,
because of unescaped '&' in the changelog (that should have been
'&amp;).  So documentation build can fail.

Best regards,
Konstantin Kolinko

---------------------------------------------------------------------
To unsubscribe, e-mail: dev-unsubscribe@tomcat.apache.org
For additional commands, e-mail: dev-help@tomcat.apache.org