Re: [CMS PATCH] for documentation/tools/schemagen-maven
x.y.z sounds good to me. Each mention of in that patch already has a corresponding paragraph about where to find the latest version. On 26 Feb 2015 10:03, "Rob Vesse" wrote: > We typically avoid putting specific version numbers in the documentation > because it quickly becomes out of date. > > Usually we just put x.y.z as the version and refer people to Maven central > to find the latest version > > Rob > > On 26/02/2015 00:28, "Stian Soiland-Reyes" wrote: > > >This should fix https://issues.apache.org/jira/browse/JENA-849 > > > >The examples still needs information about adding the > >target/generated-sources to the compile path (as the plugin doesn't > >yet - JENA-731 JENA-732 are dormant since June :-/ > > > >On 26 February 2015 at 00:20, Stian Soiland-Reyes > >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 also with update links. > >> > >> 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`: > >> > >> - > >> - org.apache.jena.tools > >> - schemagen > >> - 0.2-SNAPSHOT > >> - maven-plugin > >> - > >> + > >> + > >> + > >> + org.apache.jena > >> + jena-maven-tools > >> + 0.7 > >> + > >> + > >> + schemagen > >> + > >> +translate > >> + > >> + > >> + > >> + > >> + > >> + > >> + > >> + > >> + org.apache.jena > >> + jena-core > >> + 2.12.1 > >> + > >> + > >> > >> +Replace the `` 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 `/` section: > >> +In Maven, all such configuration information is provided via the > >>`pom.xml` file. We tell > >> +Maven to use the plugin via the ` ` section: > >> > >> > >> > >> > >> - org.openjena.tools > >> - schemagen > >> - 0.2-SNAPSHOT > >> + org.apache.jena > >> + jena-maven-tools > >> + 0.7 > >> > >> > >> > >> @@ -75,6 +96,11 @@ > >> > >> > >> > >> +*Replace the `` 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 `` > >>section. > >> > >> ### Specifying files to process > >> @@ -93,7 +119,7 @@ > >> > >> Options are, in general, given in the `` section. A given > >> `` refers to one input sou
Re: [CMS PATCH] for documentation/tools/schemagen-maven
We typically avoid putting specific version numbers in the documentation because it quickly becomes out of date. Usually we just put x.y.z as the version and refer people to Maven central to find the latest version Rob On 26/02/2015 00:28, "Stian Soiland-Reyes" wrote: >This should fix https://issues.apache.org/jira/browse/JENA-849 > >The examples still needs information about adding the >target/generated-sources to the compile path (as the plugin doesn't >yet - JENA-731 JENA-732 are dormant since June :-/ > >On 26 February 2015 at 00:20, Stian Soiland-Reyes >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 also with update links. >> >> 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`: >> >> - >> - org.apache.jena.tools >> - schemagen >> - 0.2-SNAPSHOT >> - maven-plugin >> - >> + >> + >> + >> + org.apache.jena >> + jena-maven-tools >> + 0.7 >> + >> + >> + schemagen >> + >> +translate >> + >> + >> + >> + >> + >> + >> + >> + >> + org.apache.jena >> + jena-core >> + 2.12.1 >> + >> + >> >> +Replace the `` 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 `/` section: >> +In Maven, all such configuration information is provided via the >>`pom.xml` file. We tell >> +Maven to use the plugin via the ` ` section: >> >> >> >> >> - org.openjena.tools >> - schemagen >> - 0.2-SNAPSHOT >> + org.apache.jena >> + jena-maven-tools >> + 0.7 >> >> >> >> @@ -75,6 +96,11 @@ >> >> >> >> +*Replace the `` 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 `` >>section. >> >> ### Specifying files to process >> @@ -93,7 +119,7 @@ >> >> Options are, in general, given in the `` section. A given >> `` refers to one input source - one file - as named by the >> -` name. The actual option names are taken from the RDF [config >> +`` 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 `` tags below with the latest versions as >>found by >> +browsing >>[jena-maven-tools](http://central.maven.org
Re: [CMS PATCH] for documentation/tools/schemagen-maven
This should fix https://issues.apache.org/jira/browse/JENA-849 The examples still needs information about adding the target/generated-sources to the compile path (as the plugin doesn't yet - JENA-731 JENA-732 are dormant since June :-/ On 26 February 2015 at 00:20, Stian Soiland-Reyes 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 also with update links. > > 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`: > > - > - org.apache.jena.tools > - schemagen > - 0.2-SNAPSHOT > - maven-plugin > - > + > + > + > + org.apache.jena > + jena-maven-tools > + 0.7 > + > + > + schemagen > + > +translate > + > + > + > + > + > + > + > + > + org.apache.jena > + jena-core > + 2.12.1 > + > + > > +Replace the `` 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 `/` section: > +In Maven, all such configuration information is provided via the `pom.xml` > file. We tell > +Maven to use the plugin via the ` ` section: > > > > > - org.openjena.tools > - schemagen > - 0.2-SNAPSHOT > + org.apache.jena > + jena-maven-tools > + 0.7 > > > > @@ -75,6 +96,11 @@ > > > > +*Replace the `` 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 `` section. > > ### Specifying files to process > @@ -93,7 +119,7 @@ > > Options are, in general, given in the `` section. A given > `` refers to one input source - one file - as named by the > -` name. The actual option names are taken from the RDF [config > +`` 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 `` 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.* > + > + > > - > - > - org.openjena.tools > - schemagen > - 0.2-SNAPSHOT > - > - > - src/main/vocabs/*.ttl > - src/main/vocabs/foaf.rdf > - > - > -
