[ 
https://issues.apache.org/jira/browse/CONNECTORS-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12901811#action_12901811
 ] 

Karl Wright commented on CONNECTORS-92:
---------------------------------------

bq. Web projects are no problem at all. You can even have dependencies between 
webproject. Althought I would try to make dependencies on jars only.

The question is, who would *want* to depend on any individual ACF war files?  
If there's a need, then fine, but I don't see one here.  The only use case I 
can come up with for anybody depending on ACF is on the main framework jars, 
which could be consolidated into one jar quite readily.  I would therefore 
propose breaking up modules/framework into two pieces: 
"modules/framework-core", and "modules/framework", or some such.  
"framework-core" would contain what's currently in framework/core, 
framework/ui-core, framework/agents, and framework/pull-agent, and would have 
both an ant build and a maven build that wraps it.  "framework" would contain 
"crawler-ui", "api', "authorityservice", and the jetty stuff, and would have a 
straight ant build and an ant-with-ivy build wrapping that.  Each connector 
would have an ant build and a wrapping ant-ivy build also.

Thoughts?


> 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: 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.

Reply via email to