[
https://issues.apache.org/jira/browse/CONNECTORS-92?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=12904324#action_12904324
]
Karl Wright commented on CONNECTORS-92:
---------------------------------------
Another way you can determine what's supposed to be a dependency is to look at
the start.jar produced by the ant build:
<attribute name="Class-Path" value="lib/commons-codec.jar
lib/commons-collections.jar lib/commons-el.jar lib/commons-fileupload.jar
lib/commons-httpclient-acf.jar lib/commons-io.jar lib/commons-logging.jar
lib/derbyclient.jar lib/derby.jar lib/derbyLocale_cs.jar
lib/derbyLocale_de_DE.jar lib/derbyLocale_es.jar lib/derbyLocale_fr.jar
lib/derbyLocale_hu.jar lib/derbyLocale_it.jar lib/derbyLocale_ja_JP.jar
lib/derbyLocale_ko_KR.jar lib/derbyLocale_pl.jar lib/derbyLocale_pt_BR.jar
lib/derbyLocale_ru.jar lib/derbyLocale_zh_CN.jar lib/derbyLocale_zh_TW.jar
lib/derbynet.jar lib/derbyrun.jar lib/derbytools.jar lib/eclipse-ecj.jar
lib/jasper-6.0.24.jar lib/jasper-el-6.0.24.jar lib/jdbcpool-0.99.jar
lib/jetty-6.1.22.jar lib/jetty-util-6.1.22.jar
lib/jsp-api-2.1-glassfish-9.1.1.B60.25.p2.jar lib/json.jar lib/acf-agents.jar
lib/acf-core.jar lib/acf-jetty-runner.jar lib/acf-pull-agent.jar
lib/acf-ui-core.jar lib/log4j-1.2.jar lib/postgresql.jar lib/serializer.jar
lib/servlet-api-2.5-20081211.jar lib/tomcat-juli-6.0.24.jar lib/xalan2.jar
lib/xercesImpl-lcf.jar lib/xml-apis.jar"/>
Note that commons-httpclient-acf.jar is our own version of commons-httpclient,
and must therefore NOT be an external dependency.
> 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
> Assignee: Karl Wright
> Attachments: maven-poms-including-start-jar.patch,
> maven-poms-problem-starting-jetty-and-derby.patch,
> 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.
