[
https://issues.apache.org/jira/browse/JENA-849?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14337664#comment-14337664
]
ASF GitHub Bot commented on JENA-849:
-------------------------------------
GitHub user stain opened a pull request:
https://github.com/apache/jena/pull/38
Jena 849 maven tools demo
Fixes JENA-849 in updated `jena-maven-tools/demo`
.. tries to not list the version numbers explicitly as they would go out of
date.
You can merge this pull request into a Git repository by running:
$ git pull https://github.com/stain/jena JENA-849-maven-tools-demo
Alternatively you can review and apply these changes as the patch at:
https://github.com/apache/jena/pull/38.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 #38
----
commit bdf57f582e4f55536d00932a7b057124516c59f8
Author: Stian Soiland-Reyes <st...@apache.org>
Date: 2015-02-26T00:32:29Z
Revert "JENA-731 JENA-732: revert pending dicussion."
This reverts commit 8532f01f41a016cb9ea1d27bfc25c9e13e5f6bbc.
commit f8a3b55793a12aa977015c8594fc81b2c0e26557
Author: Stian Soiland-Reyes <st...@apache.org>
Date: 2015-02-26T00:40:18Z
JENA-732 Test generated source directory
commit 9d791a273e02df931646b1ddce9b0b60e3e0c4f7
Author: Stian Soiland-Reyes <st...@apache.org>
Date: 2015-02-26T00:49:30Z
JENA-731: Test that target/classes also compiled the classes
Discuss: Should it still add to compile path when <source> was
overriden? It currently does not..
commit 68d3b8a57190dfa8c198f254e9db28351c55b6fa
Author: Stian Soiland-Reyes <st...@apache.org>
Date: 2015-02-26T01:05:04Z
JENA-731: document change of <output> default
> At the very least, this change should be documented in the changelog.
commit b35e5389dcfa6f69960f898de1d5129722fca242
Author: Stian Soiland-Reyes <st...@apache.org>
Date: 2015-02-26T01:20:03Z
JENA-732 <outputDirectory> - not <output> - to override
commit 1b0088833bd7fa7bcac16a19463e38616aec8f88
Author: Stian Soiland-Reyes <st...@apache.org>
Date: 2015-02-26T01:25:08Z
JENA-731 JENA-732 test custom <outputDirectory>
.. and that it compiles
commit a6db31dfc483d4ee3eec6a34c9df35a4d3561552
Author: Stian Soiland-Reyes <st...@apache.org>
Date: 2015-02-26T01:28:19Z
JENA-849 Updated outdated jena-maven-tools/demo versions
.. specially the new groupId/artifactId
(why isn't it jena-maven-plugin ?)
.. leaving <plugin><version> blank and RELEASE
for jena-core.
Ideally this should be proper versions updated by the release-plugin,
but then we would need to change to multiple modules.
----
> Incorrect version numbers in schemagen maven documentation
> ----------------------------------------------------------
>
> Key: JENA-849
> URL: https://issues.apache.org/jira/browse/JENA-849
> Project: Apache Jena
> Issue Type: Documentation
> Components: Maven Tools
> Affects Versions: Jena 2.12.1
> Reporter: Ian Dickinson
> Priority: Minor
>
> Reported by Alexander Willner.
> Documentation for the Schemagen maven plugin has the wrong maven config: it
> says
> {code:xml}
> <dependency>
> <groupId>org.apache.jena.tools</groupId>
> <artifactId>schemagen</artifactId>
> <version>0.2-SNAPSHOT</version>
> <type>maven-plugin</type>
> </dependency>
> {code}
> it should say:
> {code:xml}
> <dependency>
> <groupId>org.apache.jena</groupId>
> <artifactId>jena-maven-tools</artifactId>
> <version>0.7</version>
> <type>maven-plugin</type>
> </dependency>
> {code}
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
