[GitHub] incubator-streams issue #284: source and resource generation modules
Github user steveblackmon commented on the issue: https://github.com/apache/incubator-streams/pull/284 @BigBlueHat every release version and the latest snapshot version of every schema in the project is published on the streams website for the reasons you mention. See for example: http://streams.incubator.apache.org/site/latest/streams-project/streams-contrib/streams-provider-twitter/index.html I was not aware of schema-store.org but perhaps we could use them as a mirror to help developers discover our schemas. I'll work on merging this into master and polishing up website documentation on how to use the various plugins unless anyone objects in the next 48 hours. --- 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] incubator-streams issue #284: source and resource generation modules
Github user BigBlueHat commented on the issue: https://github.com/apache/incubator-streams/pull/284 The extraction of the JSON Schemas as standalone documents is actually a huge step forward for this project and a great "front door" to increase interest in activity here. OpenAPI (fka Swagger), RAML, and many other API generation/documentation tool kits all support JSON Schema. There's a growing interest (in part due to that) in JSON Schemas in general, and it can be expected that this will only increase in the coming years and that the JSON Schema community will grow and re-visit their in-progress v5, etc. Additionally, having a set of static resources (these JSON Schemas) as output from this project means vastly more people (not just Java developers) can not only benefit from them, but also contribute to them. Eventually, I'd love to see these published on the Apache Streams site directly and/or contributed to http://schemastore.org/json/ (and similar projects). The goal being here to provide "kit" (JSON Schemas mostly) that is broadly applicable to social stream data along side code that proves it's value (the Java bits). There's certainly more doors that open with this code than ones that close. --- 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] incubator-streams issue #284: source and resource generation modules
Github user steveblackmon commented on the issue: https://github.com/apache/incubator-streams/pull/284 If another TLP or incubator project were taking this on that would great. I looked but couldn't find anything at Apache. The only projects anywhere near this problem space are Velocity and Freemarker, but json / json schemas are completely foreign to their implementations and they definitely don't have any support for traversing links between schema references across the web. As to whether this is core or not, fair question. If we want to help developers actually use the json datasets that streams collects, some schema-aware binding with external systems and code is necessary. Nearly every streams module uses code generation from schema and all of the examples rely on at least one database that has a concept of schema, so I see this work as a consolidation of that reality. --- 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] incubator-streams issue #284: source and resource generation modules
Github user mfranklin commented on the issue: https://github.com/apache/incubator-streams/pull/284 OK. Just to make sure, there is no other project that offers what we need? Just looking to keep the surface area of maintained code core to what the project needs. --- 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] incubator-streams issue #284: source and resource generation modules
Github user steveblackmon commented on the issue: https://github.com/apache/incubator-streams/pull/284 org.jsonschema2pojo:jsonschema2pojo-maven-plugin was great early on, but: it only generates POJOs. it does so in a way that is not extensible to generating other types of artifacts. it is not easily over-ridden to (for example) change which annotations get added, or under what circumstances. by bringing the plugin in-house we gain adequate control to impact the generated artifacts as we see fit. this PR also establish a pattern for generating other types of artifacts from the schemas maintained by the project, with solid testing around those routines - and isolates schemas into modules apart from implementation which is an important early step toward supporting new vocabularies (AS 2.0, schema.org, etc...) --- 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] incubator-streams issue #284: source and resource generation modules
Github user mfranklin commented on the issue: https://github.com/apache/incubator-streams/pull/284 Just to be clear, the reason we needed a custom plugin here was because we wanted to be able to generate different output sources than what the default plugin offers, correct? --- 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. ---
