-Re: [jira] [Commented] (ACCUMULO-721) Reloading of lib/ext classloader causes LinkageError
Re: mailing the dev list. Sure. Will do.
By the way, I'm not sure that this is an "incorrect" usage of JIRA. I
think it's a matter of consensus and consistency. I'm still getting
the hang of this consensus building concept for lazy consensus... I
should have used the dev list instead of just talking to a few people.
For the record, I Keith Turner did point out that there is a valid
case where you would put an unreleased version in the "affected
version". That would be when you know it is a bug that won't be fixed
by the time that version is released, so it will become an issue
against an existing release at some point in the future.
I'm ambivalent on the "right way" to use JIRA, though like to be
consistent, and to offer my help to clean up inconsistencies.
On Thu, Sep 6, 2012 at 10:39 PM, Josh Elser <[EMAIL PROTECTED]> wrote:
> Ah, I see your point. I think I'll admit to using JIRA incorrectly in that I
> really wanted to see "current issues on trunk". I think I should save a
> search and approach it that way instead.
> Can you shoot a note out to the dev list next time? I had thought you were
> just updating incorrect tickets, so I was a little confused when I saw you
> removing the affected versions from some of my open issues.
> I appreciate it and thanks for cleaning things up :D
> -------- Original Message --------
> Subject: [jira] [Commented] (ACCUMULO-721) Reloading of lib/ext
> classloader causes LinkageError
> Date: Fri, 7 Sep 2012 12:30:07 +1100 (NCT)
> From: Christopher Tubbs (JIRA) <[EMAIL PROTECTED]>
> To: [EMAIL PROTECTED]
> Christopher Tubbs commented on ACCUMULO-721:
> 1.5.0 isn't a released version. It can't have things wrong with it because
> it doesn't technically exist (yet). If the version(s) affected are only
> current working branches, an "affected version" tag isn't necessary, and
> might be confusing. If older, released versions are affected by this bug,
> that would be useful to tag for documentation/search, even if we don't fix
> it until 1.5.0.
> At least, that's what I seem to understand is a reasonable thing to do from
> talking to Billie and Keith. Maybe I'm wrong?
>> Reloading of lib/ext classloader causes LinkageError
>> Key: ACCUMULO-721
>> URL: https://issues.apache.org/jira/browse/ACCUMULO-721
>> Project: Accumulo
>> Issue Type: Bug
>> Components: tserver
>> Reporter: Josh Elser
>> Assignee: Keith Turner
>> Fix For: 1.5.0
>> Attachments: ACCUMULO-721-classpath,
>> I was writing an iterator that takes advantage of some classes in
>> Google's guava-libraries. I placed my jar and the guava-13.0-rc2.jar into
>> I then ran a simple Java class which opened a Scanner to a table with my
>> customer Iterator in Eclipse. The first attempt succeeded. I then changed my
>> iterator, recompiled the jar, and placed it in lib/ext. The
>> AccumuloClassLoader message said it picked up the changes. Then, trying to
>> run my class in the same manner, I got a java.lang.LinkageError relating to
>> the classloader having two different Class objects for a class defined in
>> the guava jar (which hadn't changed).
>> Moving the guava jar from lib/ext to lib/ and retrying this experiment
>> did not net the same LinkageError.
>> I'll attach full stack traces and the output of `accumulo classpath`
> This message is automatically generated by JIRA.
> If you think it was sent incorrectly, please contact your JIRA
> For more information on JIRA, see: http://www.atlassian.com/software/jira