xml-output not detected

Bug #159370 reported by Torsten Spindler
2
Affects Status Importance Assigned to Milestone
Bazaar Plugin for Eclipse
Invalid
Undecided
Unassigned

Bug Description

I updated to the latest eclipse plugin 0.0.14.200711010129 and my existing xmloutput plugin is no longer detected. On the commandline 'bzr annotate --xml FILENAME' works fine.

Revision history for this message
Torsten Spindler (tspindler) wrote :
Revision history for this message
Guillermo Gonzalez (verterok) wrote :

Torsten,
 which version of xmloutput do you haave installed?
 I ask you this, because the 0.0.14.x needs the latest trunk or version >= 0.2 (there is a source tarball available at: https://launchpad.net/bzr-xmloutput/+download)

Revision history for this message
Torsten Spindler (tspindler) wrote : Re: [Bug 159370] Re: xml-output not detected

Here some info:

% bzr info
Standalone tree (format: dirstate)
Location:
  branch root: .

Related branches:
  parent branch:
http://bazaar.launchpad.net/~guillo.gonzo/bzr-xmloutput/0.16/

% bzr info
Standalone tree (format: dirstate)
Location:
  branch root: .

Related branches:
  parent branch:
http://bazaar.launchpad.net/~guillo.gonzo/bzr-xmloutput/0.16/

Revision history for this message
Torsten Spindler (tspindler) wrote :

% bzr log | head
------------------------------------------------------------
revno: 15
committer: Guillermo Gonzalez <email address hidden>
branch nick: 0.16
timestamp: Wed 2007-08-15 01:33:14 -0300
message:
   * patch provided by beuno for Bug #132316 applied

Revision history for this message
Guillermo Gonzalez (verterok) wrote :

The problem is that you are using an abandones branch. the url to trunk is: https://code.launchpad.net/~guillo.gonzo/bzr-xmloutput/trunk
The trunk isn'yt compatible with Bazaar <= 0.16.
If you need support for bazaar 0.16, I can make a backport to 0.16.

Regards.

Revision history for this message
Torsten Spindler (tspindler) wrote :

I removed my old branch of xml-output and moved to trunk, now it's
working fine. Thanks!

Revision history for this message
Guillermo Gonzalez (verterok) wrote :

should this bug be marked as an invalid?

Revision history for this message
Torsten Spindler (tspindler) wrote :

Yes, Invalid is good.

Changed in bzr-eclipse:
status: New → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.