You are viewing a plain text version of this content. The canonical link for it is here.

Posted to commits@hivemind.apache.org by hi...@jakarta.apache.org on 2004/04/28 16:38:34 UTC

[Jakarta HiveMind Wiki] Updated: PrivatesProposal

   Date: 2004-04-28T07:38:34
   Editor: 138.189.119.133 <>
   Wiki: Jakarta HiveMind Wiki
   Page: PrivatesProposal
   URL: http://wiki.apache.org/jakarta-hivemind/PrivatesProposal

   no comment

Change Log:

------------------------------------------------------------------------------
@@ -13,3 +13,7 @@
 = Discussion =
 
 At the risk of violating ["YAGNI"], perhaps better scoping rules are needed.  That is, something reminiscent of Java's protected modified, where a extension point would be visible within sub-modules.  But what defines a sub-module?  A module which has the current (exporting) module's id as a prefix?
+
+KnutWannheden: The solution (it's really a workaround) to the corresponding problem in Ant (private targets) is to prefix the target name with a dash (e.g. {{{<target name="-internal"/>}}}).  The target can't be invoked because the Ant command line frontend would parse it as an option (which doesn't exist).  I suppose a pragmatic solution like this wouldn't work in HiveMind nor would it be desirable...
+
+To minimize the knowledge needed by the user maybe a best practice would often suffice. The private and public parts could be split into two modules, as common in Java with ''.internal'' and ''.impl'' packages.

---------------------------------------------------------------------
To unsubscribe, e-mail: hivemind-cvs-unsubscribe@jakarta.apache.org
For additional commands, e-mail: hivemind-cvs-help@jakarta.apache.org