OK, then. Unless there are any further ideas (or objections), I will
prepare the import with the following structure:
guacamole/
client/
server/
and we can continue molding the repo from there with an overall README.md,
as well as other required files.
Thanks, all.
- Mike
On Feb 12, 2016 12:38 AM, "Jean-Baptiste Onofré" <[email protected]> wrote:
> Good point, I forgot about this point.
>
> At least a small README.md ;)
>
> Regards
> JB
>
> On 02/12/2016 09:37 AM, Mike Jumper wrote:
>
>> On Feb 11, 2016 9:10 PM, "Jean-Baptiste Onofré" <[email protected]> wrote:
>>
>>>
>>> +1
>>>
>>> but I would add a parent pom to simplify the way of building.
>>>
>>>
>> A parent pom wouldn't work for the combined repository because
>> guacamole-server is a native C project. It is built using GNU Autotools,
>> not Maven like guacamole-client.
>>
>> To clarify:
>>
>> guacamole-server is the parent project of six subprojects (and a few
>> convenience libraries) written in C99, all of which build using GNU
>> Autotools:
>>
>> * guacd
>> * libguac
>> * libguac-client-rdp
>> * libguac-client-ssh
>> * libguac-client-telnet
>> * libguac-client-vnc
>>
>> Building guacamole-server builds and installs each of those subprojects
>> automatically (through a traditional recursive build).
>>
>> guacamole-client is the parent project of seven Java / JavaScript
>> subprojects, and is already set up with a proper parent pom:
>>
>> * guacamole
>> * guacamole-auth-jdbc
>> * guacamole-auth-ldap
>> * guacamole-auth-noauth
>> * guacamole-common
>> * guacamole-common-js
>> * guacamole-ext
>>
>> Building guacamole-client builds all subprojects due to the existing
>> parent
>> pom.
>>
>> - Mike
>>
>>
> --
> Jean-Baptiste Onofré
> [email protected]
> http://blog.nanthrax.net
> Talend - http://www.talend.com
>
