GitHub user zuny25 opened a pull request:
https://github.com/apache/incubator-zeppelin/pull/817
[ZEPPELIN-792]Misspelt words and Wrong method parameters
### What is this PR for?
Fix misspelt words and wrong method parameter on zeppelin-interpreter
https://issues.apache.org/jira/browse/ZEPPELIN-792
### What type of PR is it?
Bug Fix
### Todos
* [ ] - Fix misspelt variable
* [ ] - Fix wrong method parameter
### What is the Jira issue?
* [ZEPPELIN-792](https://issues.apache.org/jira/browse/ZEPPELIN-792)
### How should this be tested?
1. Edit Interpreter dep package
2. Run DependencyResolverTest
### Screenshots (if appropriate)
### Questions:
* Does the licenses files need update? No
* Is there breaking changes for older versions? No
* Does this needs documentation? No
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/zuny25/incubator-zeppelin
feature/InterpreterDependency
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/incubator-zeppelin/pull/817.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 #817
----
commit d1e6da31a9b32d4124bb51d36911b13f61dc71d5
Author: Rusty Phillips <[email protected]>
Date: 2016-04-06T02:13:45Z
errata
classpathFlter -> classpathFilter
commit d174f1c0346cd9a445d2907bc6c5d774dfdc98de
Author: haden.kim <[email protected]>
Date: 2016-04-06T02:18:36Z
Method Usage Fix
org.sonatype.aether/aether-api/1.12 /
org.sonatype.aether.repository.RemoteRepository
public RemoteRepository setPolicy( boolena snapshot, RepositoryPolicy
policy)
org.sonatype.aether/aether-api/1.12 /
org.sonatype.aether.repository.RepositoryPolicy
public More ...RepositoryPolicy( boolean enabled, String updatePolicy,
String checksumPolicy )
I think two paraemter have to changed its position
----
---
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 [email protected] or file a JIRA ticket
with INFRA.
---
