[
https://issues.apache.org/jira/browse/CONNECTORS-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14149058#comment-14149058
]
Karl Wright edited comment on CONNECTORS-1048 at 9/26/14 11:38 AM:
-------------------------------------------------------------------
Looking quickly at what is in dist/lib, compared with what is included
typically in start.jar, and you see the following:
- lib contains 60 jars (in MCF 2.0), right now.
- start.jar references most of these, but not all. Only 54 jars are referenced.
- For multiprocess, only 40 jars in lib are referenced.
So in order to make this trick work, we would need to create distinct temporary
jar directories for each start.jar, probably under "build" not "dist", and
process those to create the manifest.
was (Author: [email protected]):
Looking quickly at what is in dist/lib, compared with what is included
typically in start.jar, and you see the following:
- lib contains 60 jars (in MCF 2.0), right now.
- start.jar references most of these, but not all. Only 54 jars are referenced.
- For multiprocess, only 40 jars in lib are referenced.
So in order to make this trick work, we would need to create distinct jar
directories for each start.jar, and process those to create the manifest.
> Find a way of including version numbers on dependent jars
> ---------------------------------------------------------
>
> Key: CONNECTORS-1048
> URL: https://issues.apache.org/jira/browse/CONNECTORS-1048
> Project: ManifoldCF
> Issue Type: Improvement
> Components: Build
> Affects Versions: ManifoldCF 2.0
> Reporter: Karl Wright
> Assignee: Karl Wright
> Fix For: ManifoldCF 2.0
>
>
> In order to attach version numbers to all jars in the build, we need to solve
> the problem of how to build start.jar manifest class paths without completely
> specifying the exact name of the jar. An idea (from Abe Shinichiro) is as
> follows:
> common-build.xml: Add artifact-version to dest.
> {code}
> + <get
> src="${maven-base-url}/${project-path}/${artifact-name}/${artifact-version}/${artifact-name}-${artifact-version}.${artifact-type}"
> dest="${target}/${artifact-name}-${artifact-version}.${artifact-type}"/>
> {code}
> framework/build.xml: New manifest-cp property setting works fine.
> {code}
> + <property name="liblocation" location="../lib" />
> + <path id="lib-jars">
> + <fileset dir="${liblocation}" includes="*.jar"/>
> + </path>
> + <pathconvert property="manifest-cp" refid="lib-jars" targetos="unix"
> pathsep=" ">
> + <map from="${liblocation}" to="../lib"/>
> + <map from="\" to="/"/>
> + </pathconvert>
> + <!-- <property name="manifest-cp" value="${manifest-cp-75}"/> -->
> {code}
> This still needs to be worked on a little because it requires there to be a
> directory with the jars needed for the classpath; the lib area also may
> contain non-jar content and it would be good to insure that wasn't an issue.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
