Sounds like the respective sides reached agreement on all of the really substantive issues, but flopped on the most trivial yet most symbolic one. Oracle could gain a fair bit of goodwill (or perhaps reclaim some of what they've lost due to this charade) by just granting the trademark to the core devs (for free use by anyone, presumably). They could still sell Oracle Hudson Enterprise Continuous Integration Server or whatever.
Beyond that, I'd think their partners (e.g. Sonatype, which has its own commercial hudson-based product) would prefer to not be faced with a choice between Oracle Hudson and OSS Jenkins (where the latter would surely have the majority of heat and light).
I think it will damage their business in the long term, as today's developers gradually move to business positions.
Before Oracle acquired Sun, I was neutral toward them, and didn't really care. I thought they were a big enterprise vendor, with a supposedly very good (but pricey) database. If I were given the money to use their DB, I would use it.
Now, I really hate what they represent. 10 years from now, as a CTO, I will try my best to consider other options, even if I have the "money" for an Oracle DB. I already love Postgres, but with Oracle's recent behavior, I will push even more toward good open source projects and away from bloated enterprise solutions.
Plus, Postgres / RethinkDB / other OSS databases will be better in 10 years ;)
Beyond that, I'd think their partners (e.g. Sonatype, which has its own commercial hudson-based product) would prefer to not be faced with a choice between Oracle Hudson and OSS Jenkins (where the latter would surely have the majority of heat and light).