Return-Path: Delivered-To: apmail-directory-dev-archive@www.apache.org Received: (qmail 38307 invoked from network); 10 Jul 2007 00:05:13 -0000 Received: from hermes.apache.org (HELO mail.apache.org) (140.211.11.2) by minotaur.apache.org with SMTP; 10 Jul 2007 00:05:13 -0000 Received: (qmail 42643 invoked by uid 500); 10 Jul 2007 00:05:15 -0000 Delivered-To: apmail-directory-dev-archive@directory.apache.org Received: (qmail 42432 invoked by uid 500); 10 Jul 2007 00:05:15 -0000 Mailing-List: contact dev-help@directory.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: "Apache Directory Developers List" Delivered-To: mailing list dev@directory.apache.org Received: (qmail 42421 invoked by uid 99); 10 Jul 2007 00:05:15 -0000 Received: from herse.apache.org (HELO herse.apache.org) (140.211.11.133) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Jul 2007 17:05:15 -0700 X-ASF-Spam-Status: No, hits=2.9 required=10.0 tests=HTML_10_20,HTML_MESSAGE,SPF_PASS X-Spam-Check-By: apache.org Received-SPF: pass (herse.apache.org: domain of akarasulu@gmail.com designates 64.233.162.234 as permitted sender) Received: from [64.233.162.234] (HELO nz-out-0506.google.com) (64.233.162.234) by apache.org (qpsmtpd/0.29) with ESMTP; Mon, 09 Jul 2007 17:05:11 -0700 Received: by nz-out-0506.google.com with SMTP id o1so724556nzf for ; Mon, 09 Jul 2007 17:04:50 -0700 (PDT) DKIM-Signature: a=rsa-sha1; c=relaxed/relaxed; d=gmail.com; s=beta; h=domainkey-signature:received:received:message-id:date:from:sender:to:subject:mime-version:content-type:x-google-sender-auth; b=Pbh740jmTgOgcmhsLDiRoEY/TzdFUlMydphAn3IUJr/IaguA+GHF/fx64GuxaJdq1au59TvpE+3Zg9dplFZTqzRjqcGQbK3h6WOOq6ETxnMGsZpXv30dbBKMI7ohaARsUYNiud7J0H8lASR4kdcp5inwaTGemvuvRRpXKncPpKo= DomainKey-Signature: a=rsa-sha1; c=nofws; d=gmail.com; s=beta; h=received:message-id:date:from:sender:to:subject:mime-version:content-type:x-google-sender-auth; b=pGfSWDigudYlh23x3bDITVhpBB+1nVkVp4ZI6LDUE6w0WmojOKPhZh+sRHH5SY+p6X/ofbFLbyZQxW6CetaerjnycVngIWlO+EXEZGBxRbYjFf7xvoGSvv9kKIwro0+8tMDXUK4Yv+FmZ0lj+tjq+ks6YeeEIk4MUwRl7g4HWpY= Received: by 10.142.78.10 with SMTP id a10mr271443wfb.1184025889576; Mon, 09 Jul 2007 17:04:49 -0700 (PDT) Received: by 10.142.77.21 with HTTP; Mon, 9 Jul 2007 17:04:49 -0700 (PDT) Message-ID: Date: Mon, 9 Jul 2007 20:04:49 -0400 From: "Alex Karasulu" Sender: akarasulu@gmail.com To: "Apache Directory Developers List" Subject: [ApacheDS] [Maven] How can we have one authoritative copy of the server.xml file? MIME-Version: 1.0 Content-Type: multipart/alternative; boundary="----=_Part_166883_3743746.1184025889556" X-Google-Sender-Auth: 67d310604166ed62 X-Virus-Checked: Checked by ClamAV on apache.org ------=_Part_166883_3743746.1184025889556 Content-Type: text/plain; charset=ISO-8859-1; format=flowed Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi all, I'm fed up with having to apply changes between the server.xml file in the server-main project to the server-installers project which also contains a server.xml file in it and vice versa. Some times there are slight differences in these files and diffs get out of wack so I cannot tell which file is the most up to date. I'd like to centralize and have a single authoritative copy in all of the ApacheDS project. I'd like to make maven reuse this same server.xml where ever it may be needed. There is no XML artifact (packaging type in Maven jargon). If there was then we could create a module with a dependency on this server.xml and reuse it all over without having to worry about keeping multiple copies in sync. This is an even greater issue in Triplesec btw so it's a problem worth solving. Does anyone know or recommend a way we can use some Maven magic to solve this problem? Thanks, Alex ------=_Part_166883_3743746.1184025889556 Content-Type: text/html; charset=ISO-8859-1 Content-Transfer-Encoding: 7bit Content-Disposition: inline Hi all,

I'm fed up with having to apply changes between the server.xml file in the server-main project
to the server-installers project which also contains a server.xml file in it and vice versa.  Some
times there are slight differences in these files and diffs get out of wack so I cannot tell which
file is the most up to date.

I'd like to centralize and have a single authoritative copy in all of the ApacheDS project.  I'd like
to make maven reuse this same server.xml where ever it may be needed.  There is no XML
artifact (packaging type in Maven jargon). If there was then we could create a module with a
dependency on this server.xml and reuse it all over without having to worry about keeping
multiple copies in sync.  This is an even greater issue in Triplesec btw so it's a problem worth
solving.

Does anyone know or recommend a way we can use some Maven magic to solve this problem?

Thanks,
Alex

------=_Part_166883_3743746.1184025889556--