If there is a way to have the old php script run with 1.2.x - I'd like to know how to set it up - at least this way I could migrate to 1.2.x (once that required field bug is fixed) and then work on the other method separately.
 
so let me know ... thx again
KM

--- On Thu, 7/1/10, KM <info4km@yahoo.com> wrote:

From: KM <info4km@yahoo.com>
Subject: Re: [mantisbt-help] SVN plugin
To: "Help with Mantis" <mantisbt-help@lists.sourceforge.net>
Date: Thursday, July 1, 2010, 12:17 PM

 
FYI - I downloaded 1.2.0 and the old script is not part of it, and even if I copy it over it does not work.  You have no choice but to go to the newer version for source code control linkage. 
 
Also couldn't yet get the new method to work -
:-(
 
KM

--- On Wed, 6/30/10, John Reese <jreese@leetcode.net> wrote:

From: John Reese <jreese@leetcode.net>
Subject: Re: [mantisbt-help] SVN plugin
To: "Help with Mantis" <mantisbt-help@lists.sourceforge.net>
Date: Wednesday, June 30, 2010, 12:25 PM

On 06/30/2010 04:51 AM, Fabian Cenedese wrote:
> We expanded the original commit script to filter out unrelated
> commits, divide up commit messages for multiple bugs, find users
> if the svn user is different to the mantis user etc. Is this commit
> script still the way to go with the new system or is it not supported
> anymore? Is there another way to control the flow of data between
> subversion and mantis with the new plugin system?

Firstly, the script-based integration is still available in version 1.2, but it
is deprecated, and has been removed from the development branch slated for 1.3.
  So in the interest of preparing for the future, it would be best to begin work
on moving to the integration plugin, but the script you already have should
still work with 1.2.x.

The new integration plugins continue to offer, or improve upon, all the
supported functionality from the original integration scripts.  With a bit of
configuration as appropriate, it will continue to automatically resolve issues
given a certain message, and it actually contains built-in support for mapping
SVN usernames to accounts in MantisBT rather than needing custom scripting for
that.  However, the plugin doesn't (currently) allow for filtering inbound
changesets, so I'm curious why you were using or needed that in the first place;
perhaps there is another way to meet your requirements.

Cheers

--
John Reese
LeetCode.net

------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first
_______________________________________________
mantisbt-help mailing list
mantisbt-help@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mantisbt-help


-----Inline Attachment Follows-----

------------------------------------------------------------------------------
This SF.net email is sponsored by Sprint
What will you do first with EVO, the first 4G phone?
Visit sprint.com/first -- http://p.sf.net/sfu/sprint-com-first

-----Inline Attachment Follows-----

_______________________________________________
mantisbt-help mailing list
mantisbt-help@lists.sourceforge.net
https://lists.sourceforge.net/lists/listinfo/mantisbt-help