Re: [CMS PATCH] documentation/tools/schemagen-maven.mdtext
Thanks - I failed to check the staging site. On 3 March 2015 at 12:03, Rob Vesse rve...@dotnetrdf.org wrote: Yes I already applied it with some minor tweaks, as with your other patch see the staging version http://jena.staging.apache.org/documentation/tools/schemagen-maven.html Rob On 03/03/2015 02:28, Stian Soiland-Reyes st...@apache.org wrote: Any feedback on this? On 26 February 2015 at 14:46, Stian Soiland-Reyes st...@apache.org wrote: Clone URL (Committers only): https://cms.apache.org/redirect?new=stain;action=diff;uri=http://jena.apa che.org/documentation%2Ftools%2Fschemagen-maven.mdtext now with x.y.z -- st...@apache.org Index: trunk/content/documentation/tools/schemagen-maven.mdtext === --- trunk/content/documentation/tools/schemagen-maven.mdtext (revision 1655891) +++ trunk/content/documentation/tools/schemagen-maven.mdtext (working copy) @@ -10,15 +10,15 @@ constants from the ontology. For some projects, invoking `schemagen` from the command line, perhaps via `ant`, -is sufficient. For projects organised around Apache maven, it would be convenient to integrate -the schemagen translation step into maven's normal build process. This plugin +is sufficient. For projects organised around Apache Maven, it would be convenient to integrate +the schemagen translation step into Maven's normal build process. This plugin provides a means to do just that. ## Pre-requisites -This plugin adds a step to the maven build process to automatically translate RDFS +This plugin adds a step to the Maven build process to automatically translate RDFS and OWL files, encoded as RDF/XML, Turtle or N-triples into Java source files. -This plugin is designed to be used with a Java project that is already using Apache maven to +This plugin is designed to be used with a Java project that is already using Apache Maven to control the build. Non-Java projects do not need this tool. Projects that are not using Maven should see the [schemagen documentation](schemagen.html) for ways to run `schemagen` from the command line. @@ -29,13 +29,34 @@ Schemagen is available from the maven central repository. To use it, add the following dependency to your `pom.xml`: -dependency - groupIdorg.apache.jena.tools/groupId - artifactIdschemagen/artifactId - version0.2-SNAPSHOT/version - typemaven-plugin/type -/dependency +build + plugins +plugin + groupIdorg.apache.jena/groupId + artifactIdjena-maven-tools/artifactId + versionx.y.z/version + executions +execution + idschemagen/id + goals +goaltranslate/goal + /goals +/execution + /executions +/plugin + /plugins +/build +dependencies + dependency + groupIdorg.apache.jena/groupId + artifactIdjena-core/artifactId + versionx.y.z/version + /dependency +/dependencies +Replace the `versionx.y.z` tags above with the latest versions as found by +browsing [jena-maven-tools](http://central.maven.org/maven2/org/apache/jena/jena-m aven-tools/) +and [jena-core](http://central.maven.org/maven2/org/apache/jena/jena-core/) in Maven Central. ## Configuration: basic principles @@ -52,15 +73,15 @@ * a mechanism to specify common options for all input files * a mechanism to specify per-file unique options -In maven, all such configuration information is provided via the `pom.xml` file. We tell -maven to use the plugin via the `build/plugins` section: +In Maven, all such configuration information is provided via the `pom.xml` file. We tell +Maven to use the plugin via the `build plugins` section: build plugins plugin - groupIdorg.openjena.tools/groupId - artifactIdschemagen/artifactId - version0.2-SNAPSHOT/version + groupIdorg.apache.jena/groupId + artifactIdjena-maven-tools/artifactId + versionx.y.z/version configuration /configuration executions @@ -75,6 +96,11 @@ /plugins /build +*Replace the `versionx.y` tags above with the latest versions as found by +browsing [jena-maven-tools](http://central.maven.org/maven2/org/apache/jena/jena-m aven-tools/) + in Maven Central.* + + The configuration options all nest inside the `configuration` section. ### Specifying files to process @@ -93,7 +119,7 @@ Options are, in general, given in the `fileOptions` section. A given `source` refers to one input source - one file - as named by the -`input name. The actual option names are taken from the RDF [config +`input` name. The actual option names are taken from the RDF [config file property names](http://jena.apache.org/documentation/tools/schemagen.html), omitting the namespace: @@
Re: [CMS PATCH] documentation/tools/schemagen-maven.mdtext
Yes I already applied it with some minor tweaks, as with your other patch see the staging version http://jena.staging.apache.org/documentation/tools/schemagen-maven.html Rob On 03/03/2015 02:28, Stian Soiland-Reyes st...@apache.org wrote: Any feedback on this? On 26 February 2015 at 14:46, Stian Soiland-Reyes st...@apache.org wrote: Clone URL (Committers only): https://cms.apache.org/redirect?new=stain;action=diff;uri=http://jena.apa che.org/documentation%2Ftools%2Fschemagen-maven.mdtext now with x.y.z -- st...@apache.org Index: trunk/content/documentation/tools/schemagen-maven.mdtext === --- trunk/content/documentation/tools/schemagen-maven.mdtext (revision 1655891) +++ trunk/content/documentation/tools/schemagen-maven.mdtext (working copy) @@ -10,15 +10,15 @@ constants from the ontology. For some projects, invoking `schemagen` from the command line, perhaps via `ant`, -is sufficient. For projects organised around Apache maven, it would be convenient to integrate -the schemagen translation step into maven's normal build process. This plugin +is sufficient. For projects organised around Apache Maven, it would be convenient to integrate +the schemagen translation step into Maven's normal build process. This plugin provides a means to do just that. ## Pre-requisites -This plugin adds a step to the maven build process to automatically translate RDFS +This plugin adds a step to the Maven build process to automatically translate RDFS and OWL files, encoded as RDF/XML, Turtle or N-triples into Java source files. -This plugin is designed to be used with a Java project that is already using Apache maven to +This plugin is designed to be used with a Java project that is already using Apache Maven to control the build. Non-Java projects do not need this tool. Projects that are not using Maven should see the [schemagen documentation](schemagen.html) for ways to run `schemagen` from the command line. @@ -29,13 +29,34 @@ Schemagen is available from the maven central repository. To use it, add the following dependency to your `pom.xml`: -dependency - groupIdorg.apache.jena.tools/groupId - artifactIdschemagen/artifactId - version0.2-SNAPSHOT/version - typemaven-plugin/type -/dependency +build + plugins +plugin + groupIdorg.apache.jena/groupId + artifactIdjena-maven-tools/artifactId + versionx.y.z/version + executions +execution + idschemagen/id + goals +goaltranslate/goal + /goals +/execution + /executions +/plugin + /plugins +/build +dependencies + dependency + groupIdorg.apache.jena/groupId + artifactIdjena-core/artifactId + versionx.y.z/version + /dependency +/dependencies +Replace the `versionx.y.z` tags above with the latest versions as found by +browsing [jena-maven-tools](http://central.maven.org/maven2/org/apache/jena/jena-m aven-tools/) +and [jena-core](http://central.maven.org/maven2/org/apache/jena/jena-core/) in Maven Central. ## Configuration: basic principles @@ -52,15 +73,15 @@ * a mechanism to specify common options for all input files * a mechanism to specify per-file unique options -In maven, all such configuration information is provided via the `pom.xml` file. We tell -maven to use the plugin via the `build/plugins` section: +In Maven, all such configuration information is provided via the `pom.xml` file. We tell +Maven to use the plugin via the `build plugins` section: build plugins plugin - groupIdorg.openjena.tools/groupId - artifactIdschemagen/artifactId - version0.2-SNAPSHOT/version + groupIdorg.apache.jena/groupId + artifactIdjena-maven-tools/artifactId + versionx.y.z/version configuration /configuration executions @@ -75,6 +96,11 @@ /plugins /build +*Replace the `versionx.y` tags above with the latest versions as found by +browsing [jena-maven-tools](http://central.maven.org/maven2/org/apache/jena/jena-m aven-tools/) + in Maven Central.* + + The configuration options all nest inside the `configuration` section. ### Specifying files to process @@ -93,7 +119,7 @@ Options are, in general, given in the `fileOptions` section. A given `source` refers to one input source - one file - as named by the -`input name. The actual option names are taken from the RDF [config +`input` name. The actual option names are taken from the RDF [config file property names](http://jena.apache.org/documentation/tools/schemagen.html), omitting the namespace: @@ -115,38 +141,50 @@ ## Example configuration +*Note: Replace the `versionx.y.z` tags below with the
Re: [CMS PATCH] documentation/tools/schemagen-maven.mdtext
Any feedback on this? On 26 February 2015 at 14:46, Stian Soiland-Reyes st...@apache.org wrote: Clone URL (Committers only): https://cms.apache.org/redirect?new=stain;action=diff;uri=http://jena.apache.org/documentation%2Ftools%2Fschemagen-maven.mdtext now with x.y.z -- st...@apache.org Index: trunk/content/documentation/tools/schemagen-maven.mdtext === --- trunk/content/documentation/tools/schemagen-maven.mdtext(revision 1655891) +++ trunk/content/documentation/tools/schemagen-maven.mdtext(working copy) @@ -10,15 +10,15 @@ constants from the ontology. For some projects, invoking `schemagen` from the command line, perhaps via `ant`, -is sufficient. For projects organised around Apache maven, it would be convenient to integrate -the schemagen translation step into maven's normal build process. This plugin +is sufficient. For projects organised around Apache Maven, it would be convenient to integrate +the schemagen translation step into Maven's normal build process. This plugin provides a means to do just that. ## Pre-requisites -This plugin adds a step to the maven build process to automatically translate RDFS +This plugin adds a step to the Maven build process to automatically translate RDFS and OWL files, encoded as RDF/XML, Turtle or N-triples into Java source files. -This plugin is designed to be used with a Java project that is already using Apache maven to +This plugin is designed to be used with a Java project that is already using Apache Maven to control the build. Non-Java projects do not need this tool. Projects that are not using Maven should see the [schemagen documentation](schemagen.html) for ways to run `schemagen` from the command line. @@ -29,13 +29,34 @@ Schemagen is available from the maven central repository. To use it, add the following dependency to your `pom.xml`: -dependency - groupIdorg.apache.jena.tools/groupId - artifactIdschemagen/artifactId - version0.2-SNAPSHOT/version - typemaven-plugin/type -/dependency +build + plugins +plugin + groupIdorg.apache.jena/groupId + artifactIdjena-maven-tools/artifactId + versionx.y.z/version + executions +execution + idschemagen/id + goals +goaltranslate/goal + /goals +/execution + /executions +/plugin + /plugins +/build +dependencies + dependency + groupIdorg.apache.jena/groupId + artifactIdjena-core/artifactId + versionx.y.z/version + /dependency +/dependencies +Replace the `versionx.y.z` tags above with the latest versions as found by +browsing [jena-maven-tools](http://central.maven.org/maven2/org/apache/jena/jena-maven-tools/) +and [jena-core](http://central.maven.org/maven2/org/apache/jena/jena-core/) in Maven Central. ## Configuration: basic principles @@ -52,15 +73,15 @@ * a mechanism to specify common options for all input files * a mechanism to specify per-file unique options -In maven, all such configuration information is provided via the `pom.xml` file. We tell -maven to use the plugin via the `build/plugins` section: +In Maven, all such configuration information is provided via the `pom.xml` file. We tell +Maven to use the plugin via the `build plugins` section: build plugins plugin - groupIdorg.openjena.tools/groupId - artifactIdschemagen/artifactId - version0.2-SNAPSHOT/version + groupIdorg.apache.jena/groupId + artifactIdjena-maven-tools/artifactId + versionx.y.z/version configuration /configuration executions @@ -75,6 +96,11 @@ /plugins /build +*Replace the `versionx.y` tags above with the latest versions as found by +browsing [jena-maven-tools](http://central.maven.org/maven2/org/apache/jena/jena-maven-tools/) + in Maven Central.* + + The configuration options all nest inside the `configuration` section. ### Specifying files to process @@ -93,7 +119,7 @@ Options are, in general, given in the `fileOptions` section. A given `source` refers to one input source - one file - as named by the -`input name. The actual option names are taken from the RDF [config +`input` name. The actual option names are taken from the RDF [config file property names](http://jena.apache.org/documentation/tools/schemagen.html), omitting the namespace: @@ -115,38 +141,50 @@ ## Example configuration +*Note: Replace the `versionx.y.z` tags below with the latest versions as found by +browsing [jena-maven-tools](http://central.maven.org/maven2/org/apache/jena/jena-maven-tools/) +and [jena-core](http://central.maven.org/maven2/org/apache/jena/jena-core/) in Maven
[CMS PATCH] documentation/tools/schemagen-maven.mdtext
Clone URL (Committers only): https://cms.apache.org/redirect?new=stain;action=diff;uri=http://jena.apache.org/documentation%2Ftools%2Fschemagen-maven.mdtext now with x.y.z -- st...@apache.org Index: trunk/content/documentation/tools/schemagen-maven.mdtext === --- trunk/content/documentation/tools/schemagen-maven.mdtext(revision 1655891) +++ trunk/content/documentation/tools/schemagen-maven.mdtext(working copy) @@ -10,15 +10,15 @@ constants from the ontology. For some projects, invoking `schemagen` from the command line, perhaps via `ant`, -is sufficient. For projects organised around Apache maven, it would be convenient to integrate -the schemagen translation step into maven's normal build process. This plugin +is sufficient. For projects organised around Apache Maven, it would be convenient to integrate +the schemagen translation step into Maven's normal build process. This plugin provides a means to do just that. ## Pre-requisites -This plugin adds a step to the maven build process to automatically translate RDFS +This plugin adds a step to the Maven build process to automatically translate RDFS and OWL files, encoded as RDF/XML, Turtle or N-triples into Java source files. -This plugin is designed to be used with a Java project that is already using Apache maven to +This plugin is designed to be used with a Java project that is already using Apache Maven to control the build. Non-Java projects do not need this tool. Projects that are not using Maven should see the [schemagen documentation](schemagen.html) for ways to run `schemagen` from the command line. @@ -29,13 +29,34 @@ Schemagen is available from the maven central repository. To use it, add the following dependency to your `pom.xml`: -dependency - groupIdorg.apache.jena.tools/groupId - artifactIdschemagen/artifactId - version0.2-SNAPSHOT/version - typemaven-plugin/type -/dependency +build + plugins +plugin + groupIdorg.apache.jena/groupId + artifactIdjena-maven-tools/artifactId + versionx.y.z/version + executions +execution + idschemagen/id + goals +goaltranslate/goal + /goals +/execution + /executions +/plugin + /plugins +/build +dependencies + dependency + groupIdorg.apache.jena/groupId + artifactIdjena-core/artifactId + versionx.y.z/version + /dependency +/dependencies +Replace the `versionx.y.z` tags above with the latest versions as found by +browsing [jena-maven-tools](http://central.maven.org/maven2/org/apache/jena/jena-maven-tools/) +and [jena-core](http://central.maven.org/maven2/org/apache/jena/jena-core/) in Maven Central. ## Configuration: basic principles @@ -52,15 +73,15 @@ * a mechanism to specify common options for all input files * a mechanism to specify per-file unique options -In maven, all such configuration information is provided via the `pom.xml` file. We tell -maven to use the plugin via the `build/plugins` section: +In Maven, all such configuration information is provided via the `pom.xml` file. We tell +Maven to use the plugin via the `build plugins` section: build plugins plugin - groupIdorg.openjena.tools/groupId - artifactIdschemagen/artifactId - version0.2-SNAPSHOT/version + groupIdorg.apache.jena/groupId + artifactIdjena-maven-tools/artifactId + versionx.y.z/version configuration /configuration executions @@ -75,6 +96,11 @@ /plugins /build +*Replace the `versionx.y` tags above with the latest versions as found by +browsing [jena-maven-tools](http://central.maven.org/maven2/org/apache/jena/jena-maven-tools/) + in Maven Central.* + + The configuration options all nest inside the `configuration` section. ### Specifying files to process @@ -93,7 +119,7 @@ Options are, in general, given in the `fileOptions` section. A given `source` refers to one input source - one file - as named by the -`input name. The actual option names are taken from the RDF [config +`input` name. The actual option names are taken from the RDF [config file property names](http://jena.apache.org/documentation/tools/schemagen.html), omitting the namespace: @@ -115,38 +141,50 @@ ## Example configuration +*Note: Replace the `versionx.y.z` tags below with the latest versions as found by +browsing [jena-maven-tools](http://central.maven.org/maven2/org/apache/jena/jena-maven-tools/) +and [jena-core](http://central.maven.org/maven2/org/apache/jena/jena-core/) in Maven Central.* + + build - plugins -plugin - groupIdorg.openjena.tools/groupId - artifactIdschemagen/artifactId - version0.2-SNAPSHOT/version -
