Interesting ... so if we want to change the build system ... what should 
we choose (better than ant obviously) ?
Imho there are others besides maven & I've seen a presso from Hans 
Dockter on Gradle where he wasn't very maven oriented :)

Wondering if we could fit in all the stuff we currently have in 
http://hudson.drizzle.org/job/OpenGrok/

hmm?
L

On 18.1.2010 13:42, Jorgen Austvik - Sun Norway wrote:
> On 01/16/10 08:07 PM, Lubos Kosco wrote:
>> Julio C?sar Rocha wrote:
>>> Greetings. It seems that there is not a Maven repository for OpenGrok.
>>> I would gladly generate the artifact so it could be published on the
>>> maven central repository. Let me know if you are interested.
>>
>> Sorry for my ignorance, but what is a maven repository ? And where is it
>> located ?
>
> It is a place where our binaries would be stored after a build.
>
>> Obviously if maven repository is good for something/someone and doesn't
>> have a problem with CDDL license feel free to do it ... from where I
>> stand I cannot say if it is worth creating ;)
>
> It is also a build and dependency system. It would let us remove the 
> jar files from the lib/ directory, and instead make maven download 
> them when someone needs them on build.
>
>> Note that if you want to fork the source, I'd like to hear the reason;
>> we try to accept patches and ideas from community and imho mercurial and
>> ant are quite easy to use for development ...
>
> This is no fork.
>
> I would love to move from ant to maven (to get rid of the lib/ 
> directory and to get two modules: cli and web), but our ant files are 
> pretti hairy (for the tests), so I think creating a maven pom is not 
> exactly straight forward.
>
> -J
>
>
> _______________________________________________
> opengrok-discuss mailing list
> opengrok-discuss at opensolaris.org
> http://mail.opensolaris.org/mailman/listinfo/opengrok-discuss
>    

-------------- next part --------------
An HTML attachment was scrubbed...
URL: 
<http://mail.opensolaris.org/pipermail/opengrok-discuss/attachments/20100118/30b0054d/attachment.html>

Reply via email to