[GitHub] opennlp pull request #210: OPENNLP-979: Update lemmatizer doc after API chan...

2017-05-17 Thread ragerri
GitHub user ragerri opened a pull request:

https://github.com/apache/opennlp/pull/210

OPENNLP-979: Update lemmatizer doc after API change

Thank you for contributing to Apache OpenNLP.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### For all changes:
- [X ] Is there a JIRA ticket associated with this PR? Is it referenced 
 in the commit message?

- [ X] Does your PR title start with OPENNLP- where  is the JIRA 
number you are trying to resolve? Pay particular attention to the hyphen "-" 
character.

- [ X] Has your PR been rebased against the latest commit within the target 
branch (typically master)?

- [ X] Is your initial contribution a single, squashed commit?

### For code changes:
- [ X] Have you ensured that the full suite of tests is executed via mvn 
clean install at the root opennlp folder?
- [ ] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
- [ ] If applicable, have you updated the LICENSE file, including the main 
LICENSE file in opennlp folder?
- [ ] If applicable, have you updated the NOTICE file, including the main 
NOTICE file found in opennlp folder?

### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in 
which it is rendered?

### Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and submit an update to your PR as soon as possible.


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ragerri/opennlp opennlp-979

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/opennlp/pull/210.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #210


commit ee9fdb8aad0e4c43bba85e50be3687475bf2221d
Author: Rodrigo Agerri <rage...@apache.org>
Date:   2017-05-17T21:04:23Z

OPENNLP-979 Update lemmatizer doc after API change




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] opennlp pull request #209: Update README for release 1.8.0 RC

2017-05-17 Thread ragerri
GitHub user ragerri opened a pull request:

https://github.com/apache/opennlp/pull/209

Update README for release 1.8.0 RC

Thank you for contributing to Apache OpenNLP.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### For all changes:
- [ ] Is there a JIRA ticket associated with this PR? Is it referenced 
 in the commit message?

- [ ] Does your PR title start with OPENNLP- where  is the JIRA 
number you are trying to resolve? Pay particular attention to the hyphen "-" 
character.

- [ ] Has your PR been rebased against the latest commit within the target 
branch (typically master)?

- [ ] Is your initial contribution a single, squashed commit?

### For code changes:
- [ ] Have you ensured that the full suite of tests is executed via mvn 
clean install at the root opennlp folder?
- [ ] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
- [ ] If applicable, have you updated the LICENSE file, including the main 
LICENSE file in opennlp folder?
- [ ] If applicable, have you updated the NOTICE file, including the main 
NOTICE file found in opennlp folder?

### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in 
which it is rendered?

### Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and submit an update to your PR as soon as possible.


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ragerri/opennlp master

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/opennlp/pull/209.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #209


commit 61100ad2b890ddd3fb5046d505008aa94cfe92aa
Author: Rodrigo Agerri <rage...@apache.org>
Date:   2017-05-17T20:00:10Z

Update README for release 1.8.0 RC




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] opennlp pull request #202: OPENNLP-1061 Add functionality to DictionaryLemma...

2017-05-16 Thread ragerri
GitHub user ragerri opened a pull request:

https://github.com/apache/opennlp/pull/202

OPENNLP-1061 Add functionality to DictionaryLemmatizer to output seve…

…ral lemmas for a given word postag pair

Thank you for contributing to Apache OpenNLP.

In order to streamline the review of the contribution we ask you
to ensure the following steps have been taken:

### For all changes:
- [X ] Is there a JIRA ticket associated with this PR? Is it referenced 
 in the commit message?

- [ X] Does your PR title start with OPENNLP- where  is the JIRA 
number you are trying to resolve? Pay particular attention to the hyphen "-" 
character.

- [ X] Has your PR been rebased against the latest commit within the target 
branch (typically master)?

- [ X] Is your initial contribution a single, squashed commit?

### For code changes:
- [ X] Have you ensured that the full suite of tests is executed via mvn 
clean install at the root opennlp folder?
- [ X] Have you written or updated unit tests to verify your changes?
- [ ] If adding new dependencies to the code, are these dependencies 
licensed in a way that is compatible for inclusion under [ASF 
2.0](http://www.apache.org/legal/resolved.html#category-a)? 
- [ ] If applicable, have you updated the LICENSE file, including the main 
LICENSE file in opennlp folder?
- [ ] If applicable, have you updated the NOTICE file, including the main 
NOTICE file found in opennlp folder?

### For documentation related changes:
- [ ] Have you ensured that format looks appropriate for the output in 
which it is rendered?

### Note:
Please ensure that once the PR is submitted, you check travis-ci for build 
issues and submit an update to your PR as soon as possible.


You can merge this pull request into a Git repository by running:

$ git pull https://github.com/ragerri/opennlp opennlp-1061

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/opennlp/pull/202.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #202


commit f9753001dd1380c58467ae19e3294912b81f
Author: Rodrigo Agerri <rage...@apache.org>
Date:   2017-05-16T10:35:22Z

OPENNLP-1061 Add functionality to DictionaryLemmatizer to output several 
lemmas for a given word postag pair




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] opennlp pull request #112: OPENNLP-904: Harmonize Lemmatizer API and multipl...

2017-03-03 Thread ragerri
Github user ragerri closed the pull request at:

https://github.com/apache/opennlp/pull/112


---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---


[GitHub] opennlp pull request #112: OPENNLP-904

2017-02-07 Thread ragerri
GitHub user ragerri opened a pull request:

https://github.com/apache/opennlp/pull/112

OPENNLP-904

Lemmatizer Interface changed to harmonize use across Dictionary, Morfologik 
and LemmatizerME lemmatizers.

You can merge this pull request into a Git repository by running:

$ git pull https://github.com/apache/opennlp 904

Alternatively you can review and apply these changes as the patch at:

https://github.com/apache/opennlp/pull/112.patch

To close this pull request, make a commit to your master/trunk branch
with (at least) the following in the commit message:

This closes #112


commit 060a4d0f81bfc2d2f2d3e8d80284d64dcbf9d2a7
Author: Rodrigo Agerri <rage...@apache.org>
Date:   2017-02-03T15:00:38Z

OPENNLP-904 insert decoding in statistical lemmatize method

commit f65d4d3efdeefa1f757eaabb508b17e60d2ae847
Author: Rodrigo Agerri <rage...@erribera.eus>
Date:   2017-02-04T16:58:55Z

OPENNLP-904 move encoding of lemmas to training logic

commit 53cd0ddf5e3d38247ecce6585a3fc53bea74463a
Author: Rodrigo Agerri <rage...@apache.org>
Date:   2017-02-06T22:42:29Z

OPENNLP-904 add function to LemmatizerME to get every lemma for a token and 
pos tag combination

commit 0e7c49aeb89e718d5e439a9efedf969f84826ee8
Author: Rodrigo Agerri <rage...@apache.org>
Date:   2017-02-07T08:49:16Z

OPENNLP-904 improve import minor change




---
If your project is set up for it, you can reply to this email and have your
reply appear on GitHub as well. If your project does not have this feature
enabled and wishes so, or if the feature is enabled but not working, please
contact infrastructure at infrastruct...@apache.org or file a JIRA ticket
with INFRA.
---