[
https://issues.apache.org/jira/browse/CONNECTORS-92?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]
Jettro Coenradie updated CONNECTORS-92:
---------------------------------------
Attachment: move-to-maven-acf-framework.patch
This is a first go on moving to maven. I started refactoring the framework
part. This should give a good idea of what is possible. Of course we are nog
there. I did not really touch any of the scripts. There is also one dependency
you have to install locally. You'll see it when you try to run maven. Advice on
ho to install it locally is provided when it fails.
I am not sure if this patch will run, it is a big one. Hope for the best
When the patch is successfully applied, go to the modules/framework folder and
try:
mvn clean install
then step into crawler-ui and do
mvn clean jetty:run-war
Use you browser to go to localhost:8080 and you can see the crawler-ui web app.
If you connect to an existing database, you should be able to see the configure
connections lists. Not more than that, than we need to put the connectors on
the classpath.
I'd be happy to do something similar for the connectors. But than we must be
sure that this is the way to go. It takes a lot of time.
> Move from ant to maven or other build system with decent library management
> ---------------------------------------------------------------------------
>
> Key: CONNECTORS-92
> URL: https://issues.apache.org/jira/browse/CONNECTORS-92
> Project: Apache Connectors Framework
> Issue Type: Wish
> Components: Build
> Reporter: Jettro Coenradie
> Attachments: move-to-maven-acf-framework.patch, Screen shot
> 2010-08-23 at 16.31.07.png
>
>
> 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.
-
You can reply to this email to add a comment to the issue online.
