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

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

It looks to me like you adopted the one-jar-per-maven-script approach, with no 
coalescing of jars, but instead introducing /src/main under each of the 
subtargets within framework.  I'd really like instead to make our job easier by 
at least combining the framework main jars together into one target first, 
along the lines I described above.  I'd also like to get a sense of the overall 
picture before proceeding, so can we discuss what individual maven targets 
there are that you are proposing, and what each of them is, before we undertake 
any changes of this kind?  The individual connector ones are obvious, but I'm 
concerned about stuff like the integration tests and the quick-start jetty 
package.  How do you cover those in a maven build?









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

Reply via email to