ANN: JIRA Plugin 0.1.4.6

Just uploaded to the plugin repository, changelog here:

http://tinyurl.com/3y72v

One thing to note, in order to attempt to fix the problem some people are
reporting with invalid/bad XML coming out of JIRA, I've added the option
to explicity disable validation. The downside of this, now that I'm also
explicity enabling validation - the plugin doesn't work AT ALL when
validation is turned on. ( Those comments at the top of the RSS are a
nasty naughtyness that will be getting JIRA issues from me very shortly,
hopefully in time for 1.6. Issue is JRA-3122 at:

http://jira.atlassian.com/secure/ViewIssue.jspa?key=JRA-3122

Please add comments about RSS exceptions you guys are getting to this
issue.

So - could -everyone- disable validation before you all start complaining
to me :)

This build also has working adding/appending of @jira javadoc annotations,
give it a try. Theres an action for a quick-popup ( like the recent files
) but its not currently bound to a keystroke, I was wanting to use
ctrlaltshift+i which is what I have it mapped to, but the plugin.xml
didn't want to like me specifying that :( Bound to have missed something
there.

For the next build, my main aim is to get the multi-project stuff in place
which alot of you have been asking for, I've been having some thoughts on
it and will post a message later with some thoughts for you guys to
comment on.

2 comments


Mark Derricutt wrote:

Just uploaded to the plugin repository, changelog here:

http://tinyurl.com/3y72v


Mark, I'm having a hard time determining what is new from the changelog.
0.1.4.6 is not a released version and all the issues are marked as
unresolved. Should I just assume that all /are/ resolved but you have
not yet had a chance to close them?

0

On Wed, 11 Feb 2004 07:25:18 -0600, Barry Kaplan wrote:


Mark Derricutt wrote:

>> Just uploaded to the plugin repository, changelog here:
>>
>> http://tinyurl.com/3y72v


Mark, I'm having a hard time determining what is new from the changelog.
0.1.4.6 is not a released version and all the issues are marked as
unresolved. Should I just assume that all /are/ resolved but you have not
yet had a chance to close them?


Darn my bad, 0.1.4.5 is what I released not .6 :(

And it seems setting the parser to NOT validate doesn't solve anything
with the bad XML jira is sending out ;(

0

Please sign in to leave a comment.