|
|
|
[
Permlink
| « Hide
]
David Peterson - 27/Mar/08 04:29 AM
For the record, the 'labels' key will list labels on the space itself, while 'labels in content' is supposed to list labels which are attached to content in the space.
Hi Nick,
I actually can't replicate the problem using Reporting 2.0.2 and Confluence 2.7.1. Is it possible that it is actually a problem with Confluence 2.5 rather than the Reporting plugin? Could you test with Confluence 2.7 and let me know your results. In a slightly-related issue, I did uncover a bug in Confluence where it does not correctly generate the URL for team labels. I've logged it with Atlassian here Hi David,
On my test installation of confluence 2.7.3. the space labels recipe (using labels in content) produces the following error: Error formatting macro: report-block: net.customware.confluence.reporting.supplier.SupplierValueException: Error while comparing 'space:name': null I've attached the stack trace. Nick ps This installation has v.2.0.1 of the reproting plugin. Hi Nick,
Could you please do a test run again with Reporting 2.1.0 (just released - may take a few minutes to hit the repository) and let me know what the results are. If it's still failing, could you please copy-n-paste the exact markup you're using and I'll try to replicate it. Hi David - I've ugpraded the plugin to 2.1.0. The error is still occurring as reported above. The markup was copied from the space labels recipe wiki page:
{report-block:output=wiki}
{space-reporter:space=@all}
{text-sort:space:name}
{space-reporter}
{report-body}
h2. {report-info:space:title|link=true}
{report-table}
{local-reporter:space:labels in content}
{text-sort:label:title}
{local-reporter}
{report-column:title=Label}{report-info:label:title|link=true}{report-column}
{report-column:title=#}{report-info:label:content count}{report-column}
{report-column:title=Content}{report-info:label:content|link=true}{report-column}
{report-table}
{report-body}
{report-block}
Hi Nick,
I've copy-n-pasted your example into my test server and it works flawlessly. Is it possible you have some bad data in your server which is causing an unexpected condition for the reporting macros? In any case, could you see if a fuller error stack is in your log files? I've had a quick look for that error message and found the place it's thrown, but it's unclear at what point the NullPointerException is being thrown. The stack trace should have line numbers, which would be most useful. Nick - I've created a new issue for this specific problem -
|
|||||||||||||||||||||||||||||||||||||||||||||||||||||||||