incubator-connectors-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Wright (JIRA)" <>
Subject [jira] [Commented] (CONNECTORS-92) Move from ant to maven or other build system with decent library management
Date Sat, 02 Apr 2011 11:48:06 GMT


Karl Wright commented on CONNECTORS-92:

This issue has stalled.  The work done so far has created a reasonable directory structure
with a pom.xml everywhere it needs to be.  However, beyond that, nothing more has happened.

It might be worth researching ant with ivy at this point, since that would be a natural extension
of the current built system, rather than trying to go the maven route entirely.

> Move from ant to maven or other build system with decent library management
> ---------------------------------------------------------------------------
>                 Key: CONNECTORS-92
>                 URL:
>             Project: ManifoldCF
>          Issue Type: Wish
>          Components: Build
>            Reporter: Jettro Coenradie
>            Assignee: Karl Wright
>         Attachments: Screen shot 2010-08-23 at 16.31.07.png, maven-poms-including-start-jar.patch,
maven-poms-problem-starting-jetty-and-derby.patch, maven-start-jar.patch, move-to-maven-acf-framework.patch,
> I am looking at the current project structure. If we want to make another build tool
available I think we need to change the directory structure. I tried to place a suggestion
in an image. Can you please have a look at it. If we agree that this is a good way to go,
than I will continue to work on a patch. Which might be a bit hard with all these changing
directories, but I'll do my best to at least get an idea whether it would be working.
> So I have three questions:
> - Do you want to move to maven or put maven next to ant?
> - Do you prefer another build mechanism [ant with ivy, gradle, maven3]
> - Do you have an idea about the amount of scripts that need to be changed if we change
the project structure
> The image of a possible project layout (that is based on the maven standards) is attached
to the issue

This message is automatically generated by JIRA.
For more information on JIRA, see:

View raw message