Maybe just latency? The JIRA plugin periodically scans, I think. Maybe you just checked at a bad time?
-Patrick -- Patrick Linskey BEA Systems, Inc. _______________________________________________________________________ Notice: This email message, together with any attachments, may contain information of BEA Systems, Inc., its subsidiaries and affiliated entities, that may be confidential, proprietary, copyrighted and/or legally privileged, and is intended solely for the use of the individual or entity named in this message. If you are not the intended recipient, and have received this message in error, please immediately return this by email and then delete it. > -----Original Message----- > From: Kevin Sutter [mailto:[EMAIL PROTECTED] > Sent: Wednesday, February 07, 2007 3:13 PM > To: open-jpa-dev@incubator.apache.org > Subject: Re: JIRA / svn integration > > Yes, this is nice. Another good reason to use the JIRA > report number in > your commit message. The strange thing is that this doesn't > always seem to > work. Every once in a while, the svn commit changes don't > get documented in > the JIRA report, even when the commit message indicates the > JIRA report. > Not sure what causes the random anomaly... Does the > committer have to be > the assignee of the JIRA report? Network glitch with no > retry logic? Any > other ideas? > > Kevin > > On 2/6/07, Patrick Linskey <[EMAIL PROTECTED]> wrote: > > > > Hi, > > > > I just discovered that Apache's JIRA install runs the JIRA / svn > > integration plugin. Take a look at the svn information towards the > > bottom of https://issues.apache.org/jira/browse/OPENJPA-119 for an > > example, and the "Subversion Commits" tab on the > browse-project page: > > https://issues.apache.org/jira/secure/BrowseProject.jspa > > > > Neat! > > > > -Patrick > > > > -- > > Patrick Linskey > > BEA Systems, Inc. > > > > > ______________________________________________________________ > _________ > > Notice: This email message, together with any attachments, > may contain > > information of BEA Systems, Inc., its subsidiaries and > affiliated > > entities, that may be confidential, proprietary, > copyrighted and/or > > legally privileged, and is intended solely for the use of > the individual > > or entity named in this message. If you are not the > intended recipient, > > and have received this message in error, please immediately > return this > > by email and then delete it. > > >
