manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Karl Wright (JIRA)" <>
Subject [jira] [Created] (CONNECTORS-1048) Find a way of including version numbers on dependent jars
Date Fri, 26 Sep 2014 09:16:33 GMT
Karl Wright created CONNECTORS-1048:

             Summary: Find a way of including version numbers on dependent jars
                 Key: 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.
+ <get src="${maven-base-url}/${project-path}/${artifact-name}/${artifact-version}/${artifact-name}-${artifact-version}.${artifact-type}"

framework/build.xml: New manifest-cp property setting works fine.


+        <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}"/> -->

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

View raw message