[
https://issues.apache.org/jira/browse/DIRKRB-134?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel&focusedCommentId=14316208#comment-14316208
]
Lin Chen commented on DIRKRB-134:
---------------------------------
Hi Kai,
Sorry for late response. Actually, I generate dependent jars by
maven-dependency-plugin and then copy them to kerby-dist, so the test related
jars are also included. To avoid that, there are two ways:
1. Specify the jars we need to copy. This way means we need to specify a list
of paths in pom.xml, for example:
{code}
<copy file="kerby-kerb/kerb-common/target/kerb-common-${project.version}.jar"
tofile="${server.dist.directory}/kerb-common-${project.version}.jar"/>
<copy file="kerby-kerb/kerb-core/target/kerb-core-${project.version}.jar"
tofile="${server.dist.directory}/kerb-core-${project.version}.jar"/>
<copy file="kerby-kerb/kerb-crypto/target/kerb-crypto-${project.version}.jar"
tofile="${server.dist.directory}/kerb-crypto-${project.version}.jar"/>
......
{code}
2. As you suggested, remove the test jars after copying.
Do you think which way is better?
> Installation packaging and service wrapper
> ------------------------------------------
>
> Key: DIRKRB-134
> URL: https://issues.apache.org/jira/browse/DIRKRB-134
> Project: Directory Kerberos
> Issue Type: Sub-task
> Reporter: Kai Zheng
> Assignee: Lin Chen
> Attachments: DIRKRB-134_v1.patch, wrapper.conf, wrapper.stop.conf
>
>
> This is for having installation packaging and service wrapper for the KDC
> server. We can borrow the existing artifacts from Directory Server.
--
This message was sent by Atlassian JIRA
(v6.3.4#6332)
