manifoldcf-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From "Shinichiro Abe (JIRA)" <j...@apache.org>
Subject [jira] [Reopened] (CONNECTORS-1048) Find a way of including version numbers on dependent jars
Date Sun, 28 Sep 2014 06:04:34 GMT

     [ https://issues.apache.org/jira/browse/CONNECTORS-1048?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel
]

Shinichiro Abe reopened CONNECTORS-1048:
----------------------------------------

CmisConnector test failed because chemistry-opencmis-server-inmemory.war file name doesn'
have version number. What would we do? Hardcoded version on test.java?

{noformat}
    [junit] [main] INFO org.eclipse.jetty.server.Server - jetty-7.5.4.v20111024
    [junit] [main] WARN org.eclipse.jetty.webapp.WebInfConfiguration - Web application not
found ../../../lib/chemistry-opencmis-server-inmemory.war
    [junit] [main] WARN org.eclipse.jetty.webapp.WebAppContext - Failed startup of context
o.e.j.w.WebAppContext{/chemistry-opencmis-server-inmemory,null},../../../lib/chemistry-opencmis-server-inmemory.war
    [junit] java.io.FileNotFoundException: ../../../lib/chemistry-opencmis-server-inmemory.war
{noformat}

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

Mime
View raw message