add list of assignees by duplicates
add more probable assignee with points
if stacktrace contains assignee more points
and majority in duplicates

proper code style in maven

make private HashMap in vcs

let git part indentify which language we are using

Issue Tracjer

svn with username

parse complex ticket with outter text form user

IssueTracker package +
VCS package +
main in the root +

test with curl

if succeed creating tasks and so on for parallel working
possible improve in performance

Nested class in files in Repo should be able to find Nested Classes in stackTrace

parse by semicolon

positive and negative tests for schema
in unit test - create range of files
passing and falling
two functions

in getTraceInfo for to foreach if possible

Needed to test youtrack on my own server/cloud youtrack
mainly check if set assignee working properly.
check correct access to tickets.

servlet version with enabling using of deleting themselves from isssue

For parsing stacktraces with non simple java file entry, create procedure and structure to organise working with whole java project code.
Here is defined the structure of java code Tree.

testing on kotlin repo
with assigned tickets
compare blameinspector result, with given

make stacktrace parser to read all type of exceptions

Add YouTrack support as an IssueTrackerService.

function that returns string of zero length or string with stacktrace
manually testing

write script
or make target after build

Create simple, using anonymous class in java visitor to walk through the javacode tree, generated by antlr parser(watch ticket) [https://github.com//issues/30]

Find library for proper work with command line argiments

Add --all
Add usage examples
Add range examples

make key
that allows to generate report
manuall generate html - with links if possible

install linux on vb
and run using -d key
resolve issue with file.separator

storing info about tickets
adding two keys: with updating base, and real time resolving
storing all possible useful data:
hashmap with blames and lines
hasmap with files

make possible create report on existing database
two scenarios:
with base : all tickets
with out base: range of tickets

necessary arguments
group which all connected

issue tracker srervice
vcs

httpconection in issue

проверять в settings есть ли ошибка в типе vcs и типе ist

create map from fullqualified method name
to String path

watch git ls

1. based on java.util.Properties
2. username, password, path to local repo, tracker url

testing duplicates of tickets

Find big project on gihub
for git and svn

Code Refactoring:

• Main -- wrap all process comand line in try catch, watch about parse int
• Make final static fields for "-p", "-t" and so on
• delete System.exit from printStackTrace
• make main System.exit(0), and try on level of main
• make constructor instead of init -- create BlameInspector for each project
• init remove nesting exceptions, make it on level below -- in services factory.
• make standartizeStackTrace - running once
• make separarate function for testing in unittest
• make versioncontrolservice return structure
• no passing exception to ticketinfo constructor
• make not equals -- "Can not get blame" , enum or something more intelligent
• single return in ticketHandler -- return null if no assignee available
• checkstyle -- getTraceInfo spaces between the binary operands
• Property Service constructor throw single type of exception
• package names in lowercase: watch java code conventions
• think of possible making propertyService singletone
• wrapp runtime exceptions in services factory
• make interfaces starting with I
• reformat code in project (using idea on something like this) -- corect spaces and so on
• make exception for each package -- especially report ReportPrinters
• Two classes test:
  • Property test
  • StackTrace parser test
  • and separate Tests

TESTS ARE THE MAIN

• make node static -- because no connection

Add svn tests including:

• interference with sorceforge;
• interference with svn itself;
• migh be some optimisation doing annotate in svn;

may be add packages
change achitecture, add above class to resolve every action class after main

Split init to effective ticket managment

make links in duplicates in tickets

who can be assgined
and where error
generate html

Variants:

• trusted, not trusted;
• exception analization:
  get true type
  • how many steps from the top of stacktrace;

catch exception

change slashes to file separator in all files paths

1. Use maven target
2. or create self made script

StackTraceTree

Usage

The created structure must implement such method as:

• adding tickets and returning corresponding information on return;
• get how many duplicates for this ticket's stacktrace;

Implementation:

At start simple n-ary tree, with vertexes of two types:

• intermediate;
• final:
  Intermediate vertex contains parent link, children links. Final vertex, contains link on parent, ticketNumber field.

Strip all lines inside of tags

split by space or in anltr
create tests with file

separate classes of blameinspector
and duplicate from tree
make report printers choose what type of intom to show

mailformed xml

make vcs working on svn
make its chan tickets

make dupplicates in html

Create another instance, using ANLTR, of parser of C# stacktraces. To build parser use antlr project of java stacktrace parser. Change parsing, might using C# stacktrace parser on C# , in anltr code, and use it polymorphical in blameInspector.