<commit_before>apigee-deploy-grunt-plugin
==========================

The purpose essentially is to extend the apigee maven plugin.

Will include custom built Grunt Plugin which can make use of Apigee Management APIs to bundle, managet and deploy API Proxies, API Products and Developer Apps.



Basic Ideas

   - Should extend Java provided in io.apigee.buildTools.enterprise4g.utils


Here are some of the Java stuff that well need to think about which is current used in the maven build. :

- com.google.http-client - 1.10.3-beta
- org.slf4j - 1.6.6
- commons-logging - 1.1.1
- org.apache.commons- 3.1
- com.google.guava - 12.0
- com.google.code.gson - 2.2.2
- xalan - 2.7.1
- org.eclipse.jgit 3.3.2.201404171909-r
- org.apache.axis2 - 1.3
- jakarta-httpcore-niossl
- httpcore
- org.apache.httpcomponents
- org.apache.httpcomponents
- org.apache.woden
- org.apache.axis2


This is how we can mashup grunt with maven

We will use the ant-run plugin together with the ant-exe to call out to Grunt from the existing build process so it can build your API Sepecification  blueprints, run tests and so on..




<commit_msg>switching accounts<commit_after>apigee-deploy-grunt-plugin
==========================

The purpose essentially is to extend the apigee maven plugin.

Will include custom built Grunt Plugin which can make use of Apigee Management APIs to bundle, managet and deploy API Proxies, API Products and Developer Apps.



Basic Ideas

   - Should extend Java provided in io.apigee.buildTools.enterprise4g.utils


Here are some of the Java stuff that well need to think about which is current used in the maven build. :

- com.google.http-client - 1.10.3-beta
- org.slf4j - 1.6.6
- commons-logging - 1.1.1
- org.apache.commons- 3.1
- com.google.guava - 12.0
- com.google.code.gson - 2.2.2
- xalan - 2.7.1
- org.eclipse.jgit 3.3.2.201404171909-r
- org.apache.axis2 - 1.3
- jakarta-httpcore-niossl
- httpcore
- org.apache.httpcomponents
- org.apache.httpcomponents
- org.apache.woden
- org.apache.axis2


This is how we can mashup grunt with maven

We will use the ant-run plugin together with the ant-exe to call out to Grunt from the existing build process so it can build your API Sepecification  blueprints, run tests and so on.





{'fraction_non_alphanumeric': 0.10195903829029386, 'fraction_numerical': 0.037399821905609976, 'mean_word_length': 3.3294797687861273, 'pattern_counts': {'":': 0, '<': 3, '<?xml version=': 0, '>': 3, 'https://': 0, 'lorem ipsum': 0, 'www.': 0, 'xml': 0}, 'pii_count': 2, 'substrings_counts': 0, 'word_list_counts': {'cursed_substrings.json': 2, 'profanity_word_list.json': 0, 'sexual_word_list.json': 0, 'zh_pornsignals.json': 0}}
{'dir': 'git-commits-cleaned', 'id': '34382', 'n_tokens_mistral': 801, 'n_tokens_neox': 723, 'n_words': 265}