aboutsummaryrefslogtreecommitdiffstats
path: root/parent
Commit message (Collapse)AuthorAgeFilesLines
* Bump athenz versionMorten Tokle2019-02-051-1/+1
|
* Do not provide commons-codec at build time.gjoranv2019-01-211-0/+5
| | | | | - We effectively stopped providing it runtime since https://github.com/vespa-engine/vespa/pull/7696
* Disable offline link detectiongjoranv2019-01-211-0/+3
| | | | | Error message: Error fetching link: /Users/gv/git/vespa/testutil/target/site/apidocs/package-list. Ignored it.
* Generate html5 javadocgjoranv2019-01-211-22/+0
|
* Do not provide apache httpclient and httpcore.gjoranv2019-01-211-0/+12
|
* Upgrade maven-shade-plugin for JDK 11gjoranv2019-01-211-10/+3
| | | | - Uses asm 7
* Upgrade asm to 7 and use Opcodes.ASM7gjoranv2019-01-211-1/+1
|
* Upgrade maven-plugin-tools artifacts, and use a version propertygjoranv2019-01-211-3/+4
|
* Use JDK 11gjoranv2019-01-211-3/+3
|
* 6-SNAPSHOT -> 7-SNAPSHOTArnstein Ressem2019-01-211-2/+2
|
* Use JDK 10gjoranv2019-01-211-3/+3
|
* Use JDK 9.gjoranv2019-01-211-2/+5
|
* Revert "Revert "Enable ABI checking on modules with public APIs""Ilpo Ruotsalainen2019-01-091-0/+16
| | | | This reverts commit cd470d8ac8a58c943748f028a37d864507628e99.
* Revert "Enable ABI checking on modules with public APIs"Håkon Hallingstad2019-01-041-16/+0
|
* Merge pull request #7964 from vespa-engine/iruotsalainen/enable-abi-checkIlpo Ruotsalainen2019-01-041-0/+16
|\ | | | | Enable ABI checking on modules with public APIs
| * Move abi-check-plugin configuration to parent.Ilpo Ruotsalainen2018-12-211-0/+16
| | | | | | | | | | Instead of configuring in each module separately, put all configuration to parent and let the relevant modules just enable the plugin.
* | Configserver flags REST APIHåkon Hallingstad2018-12-301-14/+14
|/ | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | | Adds a new ZooKeeper backed flag source. It is defined in a new module configserver-flags to allow as many as possible config server modules to depend on it by minimizing dependencies. The content of the ZK backed flag source can be viewed and modified through REST API on the config server/controller. The data stored per flag looks like { "rules": [ { "conditions": [ { "type": "whitelist", "dimension": "hostname", "values": ["host1"] } ], "value": true } ] } typical for enabling a feature flag on host1. 2 types of conditions are so far supported: whitelist and blacklist. All the conditions must match in order for the value to apply. If the value is null (or absent), the default value will be used. At the time the flag's value is retrieved, it is resolved against the conditions with the current zone, hostname, and/or application. The same data structure is used for FileFlagSource for files in /etc/vespa/flags with the ".2" extension. The FlagSource component injected in the config server is changed to: 1. Return the flag value if specified in /etc/vespa/flags, or otherwise 2. return flag value from ZooKeeper (same as REST API) The current flags (module) is also changed: - All flags must be defined in com.yahoo.vespa.flags.Flags. This allows the ZK backed flag source additional sanity checking when modifying flags. - If it makes sense to have different flag value depending on e.g. the application, then at some point before the value is retrieved, one has to bind the flag to that application (using with() to set up the fetch vector). Future changes would be to 0. make a merged FlagSource in host admin, 1. add support for viewing and modifying feature flags in dashboard, 2. in hv tool.
* Update to latest ph-javacc-maven-plugin.gjoranv2018-12-061-1/+1
| | | | | | | | | - Update FastCharStream method names to follow changes in generated CharStream class. - Update expected test output due to improvements in generated code. - Improve ability to debug tests by more clearly printing out the diff between expected and actual output.
* Manage ph-javacc-maven-plugin config in parent pom.gjoranv2018-12-061-5/+13
| | | | + Remove unused management for old javacc plugin.
* Use AssertJ to improve assertionsBjørn Christian Seime2018-11-271-0/+5
|
* Use tensorflow 1.12Henning Baldersheim2018-11-191-1/+1
|
* Use TF 1.11.0 everywhereJon Bratseth2018-11-151-0/+11
|
* Revert "Update maven-dependency-plugin to 3.1.1"Bjørn Christian Seime2018-11-091-1/+1
|
* Update maven-dependency-plugin to 3.1.1Bjørn Christian Seime2018-11-091-1/+1
|
* upgrade depKristian Aune2018-10-211-1/+1
|
* Use a property for versionHenning Baldersheim2018-09-261-1/+2
|
* Revert "Revert "Balder/add native fadvise""Henning Baldersheim2018-09-261-1/+6
|
* Revert "Balder/add native fadvise"Jon Marius Venstad2018-09-261-6/+1
|
* Add jna dependencyHenning Baldersheim2018-09-261-1/+6
|
* Upgrade to latest maven-compiler-plugin.gjoranv2018-09-241-1/+1
|
* Revert "Upgrade to Curator 2.12.0"Harald Musum2018-08-311-1/+1
|
* Upgrade to Curator 2.12.0Harald Musum2018-08-301-1/+1
|
* Install model-evaluation in standaloneJon Bratseth2018-08-281-0/+1
|
* Add logoJon Bratseth2018-08-201-0/+1
|
* Generate public+protected javadoc onlyJon Bratseth2018-08-201-1/+4
|
* Upgrade to newest 3.4 ZooKeeperHarald Musum2018-08-141-1/+1
|
* Use the guava version from container-dep-versions everywhere.gjoranv2018-07-191-5/+0
|
* add lang detection and opennlp stemmersJefim Matskin2018-07-171-0/+10
| | | | https://github.com/vespa-engine/vespa/issues/6403
* Upgrade enforcer plugin.gjoranv2018-07-111-1/+1
|
* Merge pull request #6379 from vespa-engine/gjoranv/manage-enforcer-plugingjoranv2018-07-111-0/+5
|\ | | | | Add version management for enforcer-plugin.
| * Add version management for enforcer-plugin.gjoranv2018-07-111-0/+5
| |
* | Update TODO after creating issue to the Felix team.gjoranv2018-07-101-1/+1
|/
* Java 10: use latest javadoc plugingjoranv2018-07-021-1/+1
| | | | - This fell out of an earlier commit that claimed to do the same.
* Java 10: Add -noee workaround for bnd/maven-bundle-plugin.gjoranv2018-06-291-0/+6
| | | | Workaround for: Require-Capability: osg.ee=UNKNONWN
* Java 10: Update asm and use latest asm for maven-shade-plugin.gjoranv2018-06-291-1/+10
| | | | | | | | | Problem shading JAR vespa-http-client.jar entry com/yahoo/vespa/http/client/Result$ResultType.class: java.lang.IllegalArgumentException IllegalArgumentException at org.objectweb.asm.ClassReader.<init> (ClassReader.java:160)
* Java 10: Use latest maven-javadoc-plugin.gjoranv2018-06-291-0/+21
| | | | | | * NPE was thrown * Set html version for javadoc-plugin to avoid warning. (jdk-based activation of profile)
* Java 10: Use latest maven-plugin-plugingjoranv2018-06-291-1/+1
| | | | | - IllegalArgumentException: Failed to analyze com/yahoo/config/codegen/LeafCNode$NoClassNoDefaultLeafCNode.class
* Remove Scala remnants from Maven build filesOlli Virtanen2018-06-251-58/+0
|
* Add wrapper for ZPEBjørn Christian Seime2018-06-201-0/+5
|
* Remove aries.spifly and asm-debug-all.gjoranv2018-06-061-8/+0
| | | | | | - asm-debug-all does not yet exist in a Java 9 compatible version. - aries.spifly (pulls in aries-util and asm-debug-all) is no longer required by jetty-util.