Return-Path: X-Original-To: archive-asf-public-internal@cust-asf2.ponee.io Delivered-To: archive-asf-public-internal@cust-asf2.ponee.io Received: from cust-asf.ponee.io (cust-asf.ponee.io [163.172.22.183]) by cust-asf2.ponee.io (Postfix) with ESMTP id 2095F200B65 for ; Wed, 17 Aug 2016 19:11:43 +0200 (CEST) Received: by cust-asf.ponee.io (Postfix) id 1F0F3160A8C; Wed, 17 Aug 2016 17:11:43 +0000 (UTC) Delivered-To: archive-asf-public@cust-asf.ponee.io Received: from mail.apache.org (hermes.apache.org [140.211.11.3]) by cust-asf.ponee.io (Postfix) with SMTP id 677C8160A6C for ; Wed, 17 Aug 2016 19:11:42 +0200 (CEST) Received: (qmail 43025 invoked by uid 500); 17 Aug 2016 17:11:41 -0000 Mailing-List: contact users-help@qpid.apache.org; run by ezmlm Precedence: bulk List-Help: List-Unsubscribe: List-Post: List-Id: Reply-To: users@qpid.apache.org Delivered-To: mailing list users@qpid.apache.org Received: (qmail 43006 invoked by uid 99); 17 Aug 2016 17:11:40 -0000 Received: from pnap-us-west-generic-nat.apache.org (HELO spamd4-us-west.apache.org) (209.188.14.142) by apache.org (qpsmtpd/0.29) with ESMTP; Wed, 17 Aug 2016 17:11:40 +0000 Received: from localhost (localhost [127.0.0.1]) by spamd4-us-west.apache.org (ASF Mail Server at spamd4-us-west.apache.org) with ESMTP id 6477BC041B for ; Wed, 17 Aug 2016 17:11:40 +0000 (UTC) X-Virus-Scanned: Debian amavisd-new at spamd4-us-west.apache.org X-Spam-Flag: NO X-Spam-Score: -3.748 X-Spam-Level: X-Spam-Status: No, score=-3.748 tagged_above=-999 required=6.31 tests=[RCVD_IN_DNSWL_MED=-2.3, RCVD_IN_MSPIKE_H4=-0.01, RCVD_IN_MSPIKE_WL=-0.01, RP_MATCHES_RCVD=-1.426, SPF_HELO_PASS=-0.001, SPF_PASS=-0.001] autolearn=disabled Received: from mx2-lw-us.apache.org ([10.40.0.8]) by localhost (spamd4-us-west.apache.org [10.40.0.11]) (amavisd-new, port 10024) with ESMTP id jcXIqb1YaUk8 for ; Wed, 17 Aug 2016 17:11:39 +0000 (UTC) Received: from mx6-phx2.redhat.com (mx6-phx2.redhat.com [209.132.183.39]) by mx2-lw-us.apache.org (ASF Mail Server at mx2-lw-us.apache.org) with ESMTPS id 25E8A5FBB5 for ; Wed, 17 Aug 2016 17:11:39 +0000 (UTC) Received: from zmail16.collab.prod.int.phx2.redhat.com (zmail16.collab.prod.int.phx2.redhat.com [10.5.83.18]) by mx6-phx2.redhat.com (8.14.4/8.14.4) with ESMTP id u7HHBWJI055947 for ; Wed, 17 Aug 2016 13:11:32 -0400 Date: Wed, 17 Aug 2016 13:11:32 -0400 (EDT) From: Ernest Allen To: users@qpid.apache.org Message-ID: <1606690201.2469241.1471453892088.JavaMail.zimbra@redhat.com> In-Reply-To: <868243df-566f-a9ba-09e8-33b04255ce23@redhat.com> References: <7335436C-B960-4BAF-BF58-14C629AA95D5@paypal.com> <868243df-566f-a9ba-09e8-33b04255ce23@redhat.com> Subject: Using symlinks in the qpid dispatch router console MIME-Version: 1.0 Content-Type: text/plain; charset=utf-8 Content-Transfer-Encoding: 7bit X-Originating-IP: [10.10.60.222] X-Mailer: Zimbra 8.0.6_GA_5922 (ZimbraWebClient - FF48 (Linux)/8.0.6_GA_5922) Thread-Topic: Using symlinks in the qpid dispatch router console Thread-Index: UQ4h9pH2dLv8Z4i5mgsaZ4GxzrsB9Q== archived-at: Wed, 17 Aug 2016 17:11:43 -0000 Summary: Are there any problems associated with checking in symlinks? Here is the situation: qpid-dispatch/ console/ stand-alone/ hawtio/ Basically the stand-alone and hawtio versions of the qpid dispatch router use several of the same (html, js, css) files. I see some possibile scenarios: 1) Store duplicate versions of the files in the stand-alone/ and hawtio/ directories. Not ideal from a development/maintenance perspective. 2) Store the common files in a qpid-dispatch/console/common/ directory and use releative references in the stand-alone and hawtio code. This prevents a user from copying the stand-alone/ directory into a web server since they would also need the common/ dir. Also, this complicates the hawtio pom.xml file greatly since some of the source would be under hawtio/ and some would be under ../common/. 3) Store the actual files in the stand-alone/ directory and use relative references in the hawtio build. This still has the problem of complicating the hawtio build greatly. 4) Store the actual files in the stand-alone/ directory and use symlinks in the hawtio directory. This solves both problems. Hawtio builds just fine with symlinks and the stand-alone/ directory can be copied because it actually contains the files. So, is using symlinks in this manner acceptable? Thanks, -Ernie --------------------------------------------------------------------- To unsubscribe, e-mail: users-unsubscribe@qpid.apache.org For additional commands, e-mail: users-help@qpid.apache.org