Maven <module> != Git module. (I have never used git modules.)
Jena's <module>s are directories under the common root pulled together
by the top POM. jena-jdbc has <module>s within that <module>.
Andy
On 11/10/14 23:34, Bruno P. Kinoshita wrote:
I think a submodule is not necessary for this case - and it is may become hard
to manage these submodules, as you have to update recursively sometimes to work
locally with them.
My guess is that just creating a directory would be fine, though we might
probably wait for someone who knows more about the project and code structure
to comment here.
Bruno
From: Claude Warren <[email protected]>
To: [email protected]; Bruno P. Kinoshita <[email protected]>
Sent: Saturday, October 11, 2014 7:29 PM
Subject: Re: Query Builder
Looking through the git documentation, I see there is a submodule
operation, however it does not appear that we are using it.
I assume that I should just create a sub directory under the jena directory
and add it to the jena git repository. I have not done this under git so
I want to make sure that I am doing it correctly.
Claude
On Sat, Oct 11, 2014 at 9:37 PM, Bruno P. Kinoshita <
[email protected]> wrote:
+1 not binding.
I think any of the suggested names (or even jena-contrib) would be fine,
as long as there was some kind of documentation explaining what goes there
- so thanks for already creating a web page for that.
CheersBruno
From: Andy Seaborne <[email protected]>
To: [email protected]
Sent: Saturday, October 11, 2014 2:01 PM
Subject: Re: Query Builder
+1
On 11/10/14 16:58, Claude Warren wrote:
Should we use the name
Lab
Util
Extras
I'm leaning toward jena-extras as the top level maven module and a web
page
that explains that these are packages outside the normal package that may
make development of some projects easier. That the list includes
utilities
as well as packages that are bigger than simple utilities.
If there is no objection I will set up jena-extras with jena-querybuilder
and jena-commons-config as sub-modules.
Claude
