[svn.haxx.se] · SVN Dev · SVN Users · SVN Org · TSVN Dev · TSVN Users · Subclipse Dev · Subclipse Users · this month's index

RE: [Subclipse-dev] FW: package org.tigris.subversion.javahl

From: Brad Harper <brad.harper_at_epsiia.com>
Date: 2007-02-01 18:36:45 CET

I can see that issue tracking is sufficiently ubiquitous to consider it
as an extension-point that is separate from a hypothetical plugin like
one I was attempting to describe, below.

   -----Original Message-----
   From: Brad Harper
   Sent: Thursday, February 01, 2007 9:40 AM
   To: dev
   Subject: [Subclipse-dev] FW: package org.tigris.subversion.javahl

   Per Mark's request ...
   The title, from the original thread, doesn't represent the direction
   that our off-line dialog had taken.
    -----Original Message-----
   From: Mark Phippard [mailto:markphip@verizon.net]
   Sent: Thursday, February 01, 2007 9:18 AM
   To: Brad Harper
   Subject: Re: package org.tigris.subversion.javahl

   Can we have any future conversation about this idea on the
   dev@subclipse.tigris.org mailing list?
   ----- Original Message ----
   From: Brad Harper <brad.harper@epsiia.com>
   To: markphip <markphip@verizon.net>
   Sent: Thursday, February 1, 2007 9:49:06 AM
   Subject: RE: package org.tigris.subversion.javahl
   To help me understand how this would fit within the context of
   Subclipse, I see it integrating
   with the hypothetical extension via the commit log message text.
   The hypothetical plugin would supply a ui containing whatever input
   fields it chose, validate
   user input, interpret results, then construct the log message in a
   format compatible with
   the local environment.
   Subclipse would simply take the log message it was given and pass it
   to SVN in the commit
   operation. Default behavior might be equivalent what's provided

      -----Original Message-----
      From: Mark Phippard [mailto:markphip@verizon.net]
      Sent: Wednesday, January 31, 2007 1:03 PM
      To: Brad Harper
      Subject: Re: package org.tigris.subversion.javahl

      We'd have to work that out. It could be they are used as a fall
      back if there are no plugins installed which use the extension
      point, or it could be that we provider a "Bugtraq" plugin that
      fills the extension point and use those properties to get its
      I recall someone submitted a patch for some of this to the dev@
      list a couple of months ago. It lacked some of the things we
      would want/need though, such as letting their be multiple possible
      plugins that use the extension point. Could be a starting point.
      The Eclipse Mylar plugin also needs to be considered. Part of why
      we have held off is that there has been some talk of them creating
      a generic issue tracking extension point that we could then reuse.

      ----- Original Message ----
      From: Brad Harper <brad.harper@epsiia.com>
      To: markphip <markphip@verizon.net>
      Sent: Wednesday, January 31, 2007 1:18:05 PM
      Subject: RE: package org.tigris.subversion.javahl
      I understand.
      Yes, I am interested -- but I'm reluctant to sign on without a
      better idea
      of what "invest the effort" means [to both you and me].
      As I mentioned in an earlier e-mail, I'm new to Eclipse plugin
      development. If
      I understand correctly, you're suggesting the addition of plugin
      extension points to
      the Subclipse plugin. Would this approach mean basically replacing
      [current] implementation where svn bugtraq properties are used to
      the Subclipse plugin's ui and behavior?

         -----Original Message-----
         From: Mark Phippard [mailto:markphip@verizon.net]
         Sent: Tuesday, January 30, 2007 7:12 PM
         To: Brad Harper
         Subject: Re: package org.tigris.subversion.javahl

         We wouldn't be directly interested, but I and others have given
         thoughts to how we could add Eclipse extensions points so that
         this sort of functionality could be added by a plugin. That
         would be the "Eclipse way" to do it. I think the problem is we
         have to consider the scenario where there might be multiple
         plugins that want to contribute, or plugin A for project A and
         plugin B for project B and it then becomes easy to just put it
         I do not want to direct you to another product, and I think
         Subclipse is the best one, but have you looked at Subversive?
         I ask, because the company developing it has added a lot of
         extension points like this so that they can extend the base
         product with their own proprietary tools. They might already
         have an extension point you could use to add this feature and
         that would at least save you from maintaining customizations.
         That being said, if you wanted to invest the effort to help us
         do this right, it is possible we could get this into Subclipse.

         ----- Original Message ----
         From: Brad Harper <brad.harper@epsiia.com>
         To: markphip <markphip@verizon.net>
         Sent: Tuesday, January 30, 2007 4:36:44 PM
         Subject: RE: package org.tigris.subversion.javahl
         We're wanting to enforce entry of specific information, beyond
         possible with a template. E.g. introduce separate input
         components for 'code
         reviewer' and an indication when work associated with the
         operation requires documentation change(s). This and other info
         will help in
         the automatic extraction of release notes content.
         How interested is your team in this sort of customization? In

            -----Original Message-----
            From: Mark Phippard [mailto:markphip@verizon.net]
            Sent: Tuesday, January 30, 2007 3:00 PM
            To: Brad Harper
            Subject: Re: package org.tigris.subversion.javahl

            You need svnjavahl.jar for that package, which is the
            Subversion JavaHL source code. You will eventually likely
            need svnkit.jar or the source code for SVNKit as well.
            If you are going to customize Subclipse, I'd recommend just
            checking out from the tag, which will include everything you
            need to have it all setup for development.

            ----- Original Message ----
            From: Brad Harper <brad.harper@epsiia.com>
            To: markphip <markphip@tigris.org>
            Sent: Tuesday, January 30, 2007 10:42:11 AM
            Subject: package org.tigris.subversion.javahl
            Hello Mark:
            I'm trying to build subclipse plugin from the source
            'subclipse-source-1.0.4.zip' before attempting modifications
            will support local process requirements. [I'm new to Eclipse
            I find compiler error messages complaining that the subject
            package does not exist. Have I missed jar files that should
            added to the project's build path?





Received on Thu Feb 1 18:37:16 2007

This is an archived mail posted to the Subclipse Dev mailing list.