As of 0.5, the current version, the schemagen plugin defaults to
writing into target/generated-sources. This directory is usually the
home of multiple sets of generated source; for example, a typical
Maven 3.0.4 build creates an 'annotations' directory in there.
That directory isn't automatically compiled.
In the simplest case, I find that I want to generate the sources and
include them in the build. But there are less simple cases, where, for
example, people want to run the plugin explicitly and check in the
results.
The existing configuration scheme is fine for the less-simple cases:
for the simple case, it at least needs the help of the
build-helper-maven-plugin.
On the dev list, I've proposed a change to make it possible to do the
simple case simply: to just provide a single output directory,
defaulted to target/generated-sources/jena, that would be
automatically added as a source root.
We could:
a: not do this
b: make adding the source root an optional behavior and leave the
pathname specification as it is
c: add a new means of pathname configuration that triggers the simple case
d: while we are at it, change the default to add the extra level of directory
Do users of the plugin have preferences?
writing into target/generated-sources. This directory is usually the
home of multiple sets of generated source; for example, a typical
Maven 3.0.4 build creates an 'annotations' directory in there.
That directory isn't automatically compiled.
In the simplest case, I find that I want to generate the sources and
include them in the build. But there are less simple cases, where, for
example, people want to run the plugin explicitly and check in the
results.
The existing configuration scheme is fine for the less-simple cases:
for the simple case, it at least needs the help of the
build-helper-maven-plugin.
On the dev list, I've proposed a change to make it possible to do the
simple case simply: to just provide a single output directory,
defaulted to target/generated-sources/jena, that would be
automatically added as a source root.
We could:
a: not do this
b: make adding the source root an optional behavior and leave the
pathname specification as it is
c: add a new means of pathname configuration that triggers the simple case
d: while we are at it, change the default to add the extra level of directory
Do users of the plugin have preferences?