You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@directory.apache.org by ak...@apache.org on 2005/01/05 21:40:48 UTC
svn commit: r124271 - /incubator/directory/ads/trunk/INCUBATOR-DISCLAIMER.txt /incubator/directory/ads/trunk/LICENSE.txt /incubator/directory/ads/trunk/NOTICE.txt /incubator/directory/ads/trunk/project.xml
Author: akarasulu
Date: Wed Jan 5 12:40:46 2005
New Revision: 124271
URL: http://svn.apache.org/viewcvs?view=rev&rev=124271
Log:
taking Bretts advice with copies of notices and preparing for the move
Added:
incubator/directory/ads/trunk/INCUBATOR-DISCLAIMER.txt
- copied unchanged from r124251, incubator/directory/INCUBATOR-DISCLAIMER.txt
incubator/directory/ads/trunk/LICENSE.txt
- copied unchanged from r124251, incubator/directory/LICENSE.txt
incubator/directory/ads/trunk/NOTICE.txt
- copied unchanged from r124251, incubator/directory/NOTICE.txt
Modified:
incubator/directory/ads/trunk/project.xml
Copied: incubator/directory/ads/trunk/INCUBATOR-DISCLAIMER.txt (from r124251, incubator/directory/INCUBATOR-DISCLAIMER.txt)
Url: http://svn.apache.org/viewcvs/incubator/directory/ads/trunk/INCUBATOR-DISCLAIMER.txt?view=diff&rev=124271&p1=incubator/directory/INCUBATOR-DISCLAIMER.txt&r1=124251&p2=incubator/directory/ads/trunk/INCUBATOR-DISCLAIMER.txt&r2=124271
==============================================================================
Copied: incubator/directory/ads/trunk/LICENSE.txt (from r124251, incubator/directory/LICENSE.txt)
Url: http://svn.apache.org/viewcvs/incubator/directory/ads/trunk/LICENSE.txt?view=diff&rev=124271&p1=incubator/directory/LICENSE.txt&r1=124251&p2=incubator/directory/ads/trunk/LICENSE.txt&r2=124271
==============================================================================
Copied: incubator/directory/ads/trunk/NOTICE.txt (from r124251, incubator/directory/NOTICE.txt)
Url: http://svn.apache.org/viewcvs/incubator/directory/ads/trunk/NOTICE.txt?view=diff&rev=124271&p1=incubator/directory/NOTICE.txt&r1=124251&p2=incubator/directory/ads/trunk/NOTICE.txt&r2=124271
==============================================================================
Modified: incubator/directory/ads/trunk/project.xml
Url: http://svn.apache.org/viewcvs/incubator/directory/ads/trunk/project.xml?view=diff&rev=124271&p1=incubator/directory/ads/trunk/project.xml&r1=124270&p2=incubator/directory/ads/trunk/project.xml&r2=124271
==============================================================================
--- incubator/directory/ads/trunk/project.xml (original)
+++ incubator/directory/ads/trunk/project.xml Wed Jan 5 12:40:46 2005
@@ -3,7 +3,7 @@
<project>
<groupId>incubator-directory</groupId>
<artifactId>eve-parent</artifactId>
- <name>Eve Directory Server</name>
+ <name>Apache Directory Server</name>
<currentVersion>0.8-SNAPSHOT</currentVersion>
<organization>
@@ -13,13 +13,13 @@
</organization>
<inceptionYear>2003</inceptionYear>
- <package>org.apache.eve</package>
+ <package>org.apache.ldap.server</package>
<logo>http://incubator.apache.org/directory/images/apache-directory-logo.png</logo>
- <url>http://incubator.apache.org/directory/eve/</url>
+ <url>http://incubator.apache.org/directory/ads/</url>
- <issueTrackingUrl>http://issues.apache.org/jira/browse/DIREVE</issueTrackingUrl>
+ <issueTrackingUrl>http://issues.apache.org/jira/browse/DIRADS</issueTrackingUrl>
<siteAddress>directory.apache.org</siteAddress>
<!-- TODO: ... -->
<siteDirectory>/home/akarasulu/public_html</siteDirectory>
@@ -31,33 +31,33 @@
<repository>
<connection>
- scm:svn:http://svn.apache.org/repos/asf/incubator:directory/eve/trunk/${module.path}
+ scm:svn:http://svn.apache.org/repos/asf/incubator:directory/ads/trunk/${module.path}
</connection>
<url>
- http://svn.apache.org/viewcvs.cgi/incubator/directory/eve/trunk/${module.path}/?root=Apache-SVN
+ http://svn.apache.org/viewcvs.cgi/incubator/directory/ads/trunk/${module.path}/?root=Apache-SVN
</url>
<developerConnection>
- https://svn.apache.org/repos/asf/incubator/directory/eve/trunk/${module.path}
+ https://svn.apache.org/repos/asf/incubator/directory/ads/trunk/${module.path}
</developerConnection>
</repository>
- <shortDescription>Eve Directory Server</shortDescription>
+ <shortDescription>Apache Directory Server</shortDescription>
<description>
- Eve is an embeddable LDAPv3 directory server based on a SEDA
- architecture. Eve is designed to be completely pluggable in every aspect
+ The Apache Directory Server (ADS) is an embeddable LDAPv3 directory
+ server. ADS is designed to be completely pluggable in every aspect
including backends and frontend handlers making making it an ideal
experimentation platform for LDAP protocol testing, and for use
in building other tools like like meta directories, and virtual
- directories. Eve introduces stored procedures, triggers, views, and
- queues to the world of LDAP.
+ directories. ADS aims to introduces stored procedures, triggers,
+ views, and queues to the world of LDAP.
</description>
<mailingLists>
<mailingList>
- <name>Apache Directory Developement - use [eve] prefix</name>
+ <name>Apache Directory Developement - use [dirserv] prefix</name>
<subscribe>
directory-dev-subscribe@incubator.apache.org
</subscribe>
@@ -99,7 +99,7 @@
<!-- TODO: required? -->
<excludes>
- <exclude>**/Abstract*Test*</exclude>
+ <exclude>**/Abstract*Test*</exclude>
</excludes>
<!-- TODO: are all these required? Should have a src/test/resources directory -->
@@ -119,32 +119,31 @@
</unitTest>
<!-- TODO: are all these required? Should have a src/main/resources directory -->
- <resources>
- <resource>
- <directory>${basedir}/src/java</directory>
- <includes>
- <include>**/*.dtd</include>
- <include>**/*.gif</include>
- <include>**/*.properties</include>
- <include>**/*.ldif</include>
- <include>**/*.x*</include>
- </includes>
- </resource>
+ <resources>
+ <resource>
+ <directory>${basedir}/src/java</directory>
+ <includes>
+ <include>**/*.dtd</include>
+ <include>**/*.gif</include>
+ <include>**/*.properties</include>
+ <include>**/*.ldif</include>
+ <include>**/*.x*</include>
+ </includes>
+ </resource>
- <!-- TODO: Is this really appropriate given the svn layout? probably breaks on tags/branches - make a local copy instead -->
- <resource>
- <directory>${basedir}/../../../</directory>
- <targetPath>META-INF</targetPath>
- <includes>
- <include>LICENSE.txt</include>
- <include>NOTICE.txt</include>
- <include>INCUBATOR-DISCLAIMER.txt</include>
- </includes>
- </resource>
-
- </resources>
- <jars></jars>
- </build>
+ <resource>
+ <directory>${basedir}</directory>
+ <targetPath>META-INF</targetPath>
+ <includes>
+ <include>LICENSE.txt</include>
+ <include>NOTICE.txt</include>
+ <include>INCUBATOR-DISCLAIMER.txt</include>
+ </includes>
+ </resource>
+
+ </resources>
+ <jars></jars>
+ </build>
<developers>
<developer>
@@ -160,10 +159,10 @@
</developers>
- <!-- TODO: Clover? -->
- <reports>
- <report>maven-license-plugin</report>
- </reports>
+ <!-- TODO: Clover? -->
+ <reports>
+ <report>maven-license-plugin</report>
+ </reports>
</project>
Re: ADS vs Directory vs Server :)
Posted by Alex Karasulu <ao...@bellsouth.net>.
Brett Porter wrote:
>Quoting Alex Karasulu <ao...@bellsouth.net>:
>
>
>>+ Email Subject Prefix: [server]
>>+ Apache Directory Server SVN Folder: server
>>+ JIRA Subproject: DIRSERVER
>>- Package Name: org.apache.ldap.server
>>Executable jar with bundled deps: dir-server-${version}.jar
>>
>>
>
>The only reason I was confused about package was that I thought the server did
>more than just ldap.
>
Yeah that's true but the code that is not LDAP specific is not in the
heart of the server and kept in separate packages/subprojects. These
non-LDAP addons are more like 'components' that snaps in like the
Kerberos 'component' for example.
>Anyway, this is all good - go for it.
>
>
Coolio I'll start soon after some sleep ... :)
Thanks for the recommendations they did help.
Alex
Re: ADS vs Directory vs Server :)
Posted by Brett Porter <br...@apache.org>.
Quoting Alex Karasulu <ao...@bellsouth.net>:
> I thought we could but it does not look like I can darn (&**%^#)^#. I
> gotta rename DIRSNICKERS, DIRSEDA and DIREVE though. Any ideas on how
> we can do this? Perhaps I just need to create the new JIRA project and
> migrate issues.
That'll work. You can bulk move, and the old URLs should still work.
> + Email Subject Prefix: [server]
> + Apache Directory Server SVN Folder: server
> + JIRA Subproject: DIRSERVER
> - Package Name: org.apache.ldap.server
> Executable jar with bundled deps: dir-server-${version}.jar
The only reason I was confused about package was that I thought the server did
more than just ldap. Anyway, this is all good - go for it.
- Brett
Re: ADS vs Directory vs Server :)
Posted by Alex Karasulu <ao...@bellsouth.net>.
Brett Porter wrote:
>Hi,
>
>Thought I'd chime in with my opinion here. This is really just my opinion, so
>feel free to just say no :)
>
>
:)
>I'll reference the specific examples from the last POM, but in summary:
>- I suggest just using "directory" where appropriate
>- if already following directory, use /directory/server/ instead of
>/directory/directory/
>
>
We can do 'server' for the folder name sure. I guess it also makes
sense to use it as the prefix in email subjects. However there may be
many variants of the server or multiple servers that result. Perhaps
I'm trying to read too far into the future here.
>I understand the pain this is: Maven suffers from this more now that it is both
>a project (with subprojects) and something itself.
>
>
Tell me about it. Balancing these names is getting frustrating. I want
to make sure we factor in all opinions but as you note there are some
reasons behind these decisions due to all the parts. I just need to
outline the reasons one by one and we can take another pass.
>>- <package>org.apache.eve</package>
>>+ <package>org.apache.ldap.server</package>
>>
>>
I used this package name because in the ldap subproject their are
clients and common libraries. The client code uses the o.a.ldap.client
package and the common code (used in the server and clients) is within
the o.a.ldap.common package. I thought if others want to avoid 'ads' as
the package base (which btw I think is short and sweet) then I'll make
the base symetric by building on this existing packaging scheme with
o.a.ldap.server. Only natural no?
>
>why not just o.a.directory since the other packages are not including
>.directory? Or if they are, o.a.d.server?
>
>
Good point but directory alone does not reflect that the code in the
package is specifically for the server. It gets a little confusing
IMO. I'd reather go with org.apache.ldap.server or org.apache.ads.
>>
>>- <url>http://incubator.apache.org/directory/eve/</url>
>>+ <url>http://incubator.apache.org/directory/ads/</url>
>>
>>
>
>I think when following /directory/, /server/ is better than ads.
>
>
Ok let's do that then. We can use DIRSERVER for issue tracking as
well. See below ...
>
>
>>
>>-
>><issueTrackingUrl>http://issues.apache.org/jira/browse/DIREVE</issueTrackingUrl>
>>+
>><issueTrackingUrl>http://issues.apache.org/jira/browse/DIRADS</issueTrackingUrl>
>>
>>
>
>
>This was a bit premature? Can these actually be changed?
>
>
I thought we could but it does not look like I can darn (&**%^#)^#. I
gotta rename DIRSNICKERS, DIRSEDA and DIREVE though. Any ideas on how
we can do this? Perhaps I just need to create the new JIRA project and
migrate issues.
>If so, I'd simply go for DIRECTORY.
>
>
But what about how we use DIR as the prefix for the subprojects? Also
we already have a DIRECTORY jira for tasks/issues that do not apply to a
specific subproject. If we go with the folder name of 'server' then we
can do DIRSERVER and that works with the present jira scheme.
>scm:svn:http://svn.apache.org/repos/asf/incubator:directory/ads/trunk/${module.path}
>
>again, in SVN I'd go for directory/server
>
>
>
Yep I'm liking this choice the more I read on.
>>+ The Apache Directory Server (ADS) is an embeddable LDAPv3 directory
>>
>>
>
>I really don't like that three-letter-acronym :)
>
>
Why do I always like names others dislike or ones that infringe on TMs.
What bothers you about ads? Just curious. I like it even though it
sounds like ADvertisementS. It keeps names short and is the acronym for
the name of the server. Just how much confusion will it really cause.
I'm not convinced it would cause all that much confusion.
You might get a chuckle out of this one - someone ;) emailed me off list
and suggested Apache Information Directory Server or AIDS for short as a
joke.
>>+ <name>Apache Directory Developement - use [dirserv] prefix</name>
>>
>>
>
>[server] ?
>
>
k np we'll use that. So just to summarize the things (+ for agree and -
disagree with my preference):
+ Email Subject Prefix: [server]
+ Apache Directory Server SVN Folder: server
+ JIRA Subproject: DIRSERVER
- Package Name: org.apache.ldap.server
Executable jar with bundled deps: dir-server-${version}.jar
If these choices are cool with everyone I can immediately start
refactoring package names and tidying up. I'd like to have the sitedocs
massaged, and jars generated for folks to take a look before another
release attempt within the week.
Thanks,
Alex
RE: ADS vs Directory vs Server :)
Posted by Stephen McConnell <mc...@apache.org>.
+1 to everything below.
> -----Original Message-----
> From: Brett Porter [mailto:brett@apache.org]
> Sent: 06 January 2005 09:03
> To: directory-dev@incubator.apache.org
> Subject: ADS vs Directory vs Server :)
>
> Hi,
>
> Thought I'd chime in with my opinion here. This is really just my
opinion,
> so
> feel free to just say no :)
>
> I'll reference the specific examples from the last POM, but in
summary:
> - I suggest just using "directory" where appropriate
> - if already following directory, use /directory/server/ instead of
> /directory/directory/
>
> I understand the pain this is: Maven suffers from this more now that
it is
> both
> a project (with subprojects) and something itself.
>
> > - <package>org.apache.eve</package>
> > + <package>org.apache.ldap.server</package>
> >
>
> why not just o.a.directory since the other packages are not including
> .directory? Or if they are, o.a.d.server?
>
> >
> > - <url>http://incubator.apache.org/directory/eve/</url>
> > + <url>http://incubator.apache.org/directory/ads/</url>
>
> I think when following /directory/, /server/ is better than ads.
>
> >
> > -
> >
>
<issueTrackingUrl>http://issues.apache.org/jira/browse/DIREVE</issueTrac
ki
> ngUrl>
> > +
> >
>
<issueTrackingUrl>http://issues.apache.org/jira/browse/DIRADS</issueTrac
ki
> ngUrl>
>
>
> This was a bit premature? Can these actually be changed?
>
> If so, I'd simply go for DIRECTORY.
>
> >
>
scm:svn:http://svn.apache.org/repos/asf/incubator:directory/ads/trunk/${
mo
> dule.path}
>
> again, in SVN I'd go for directory/server
>
> > + The Apache Directory Server (ADS) is an embeddable LDAPv3
> directory
>
> I really don't like that three-letter-acronym :)
>
> > + <name>Apache Directory Developement - use [dirserv]
> prefix</name>
>
> [server] ?
>
> HTH,
> Brett
RE: ADS vs Directory vs Server :)
Posted by "Noel J. Bergman" <no...@devtech.com>.
Brett,
Fair points. I don't know that this is a right answer, although there may
be wrong ones. At this point, I would not worry overly about it. We are
not exposing that much --- the surface area should be small. And we are
still under the Incubator. No one should count on packages not to change.
By the time we are really ready to "freeze" packages, we may be hiding from
most clients everything that isn't under org.apache.naming, but we'll see.
--- Noel
ADS vs Directory vs Server :)
Posted by Brett Porter <br...@apache.org>.
Hi,
Thought I'd chime in with my opinion here. This is really just my opinion, so
feel free to just say no :)
I'll reference the specific examples from the last POM, but in summary:
- I suggest just using "directory" where appropriate
- if already following directory, use /directory/server/ instead of
/directory/directory/
I understand the pain this is: Maven suffers from this more now that it is both
a project (with subprojects) and something itself.
> - <package>org.apache.eve</package>
> + <package>org.apache.ldap.server</package>
>
why not just o.a.directory since the other packages are not including
.directory? Or if they are, o.a.d.server?
>
> - <url>http://incubator.apache.org/directory/eve/</url>
> + <url>http://incubator.apache.org/directory/ads/</url>
I think when following /directory/, /server/ is better than ads.
>
> -
> <issueTrackingUrl>http://issues.apache.org/jira/browse/DIREVE</issueTrackingUrl>
> +
> <issueTrackingUrl>http://issues.apache.org/jira/browse/DIRADS</issueTrackingUrl>
This was a bit premature? Can these actually be changed?
If so, I'd simply go for DIRECTORY.
>
scm:svn:http://svn.apache.org/repos/asf/incubator:directory/ads/trunk/${module.path}
again, in SVN I'd go for directory/server
> + The Apache Directory Server (ADS) is an embeddable LDAPv3 directory
I really don't like that three-letter-acronym :)
> + <name>Apache Directory Developement - use [dirserv] prefix</name>
[server] ?
HTH,
Brett