<commit_before>- Add context properties SSCApplicationVersion and FoDRelease to specify sources by name
  - For now, add a utility class like SSC/FoDConnectionFactory that has a private IContext interface
    that can hold either id or name (format Application:Version/Release) and a static
    getApplicationId(Context)/getReleaseId(context) method that either returns the provided
    id directly, or looks up the id for the provided name.
  - In the future, see whether we can integrate this in ContextProperty directly
    (i.e. allow to have an alternative context property (name) that sets another context property (id)
    
- Add support for specifying a mapping from one context property value to multiple other property values
  - For example given an FoD release name, set the corresponding JIRA project key
  - If FoDReleaseId is not specified, run the process runners for all FoDReleaseId's
    specified in this mapping
    
- Add support for ContextProperty instances to run some method to provide a default value
  (probably necessary for next point)
  
- Add support for loading additional context properties from SSC/FoD application (version) attributes,
  i.e. have an SSC application attribute containing the JIRA project identifier to which vulnerabilities
  for this application version need to be filed.
  If no SSC application version is provided, load all appversions for which this application attribute has been set


    
- TODO: create repo's for fortify-maven-support and bugtracker-add-existing-bug, and commit code
 <commit_msg>Updates ideas.txt<commit_after>- Add context properties SSCApplicationVersion and FoDRelease to specify sources by name
  - For now, add a utility class like SSC/FoDConnectionFactory that has a private IContext interface
    that can hold either id or name (format Application:Version/Release) and a static
    getApplicationId(Context)/getReleaseId(context) method that either returns the provided
    id directly, or looks up the id for the provided name.
  - In the future, see whether we can integrate this in ContextProperty directly
    (i.e. allow to have an alternative context property (name) that sets another context property (id)
    
- Add support for specifying a mapping from one context property value to multiple other property values
  - For example given an FoD release name, set the corresponding JIRA project key
  - If FoDReleaseId is not specified, run the process runners for all FoDReleaseId's
    specified in this mapping
  Essentially works, requires some more work
  Add implementations for getting all projects with for example 'JiraProjectKey' application version attribute set,
  and automatically map application version context property to jira project key context property
    
- Add support for ContextProperty instances to run some method to provide a default value
  For example to read usernames/passwords from console only once for all processor invocations


    
TODO: 
- create repo's for fortify-maven-support and bugtracker-add-existing-bug, and commit code
- Change add/getContextPropertyDefinitions to use a map of ContextPropertyDefinition instances indexed by name
  (to avoid duplicates from multiple processors)
- Check whether IContextAware is being used, otherwise remove this functionality as it complicates some code


 
{'fraction_non_alphanumeric': 0.03269346130773845, 'fraction_numerical': 0.0, 'mean_word_length': 4.353130016051364, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 0, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 0, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '6540633', 'n_tokens_mistral': 783, 'n_tokens_neox': 747, 'n_words': 441}