Standalone build should be available for 0.9.3

• Key: DIRSERVER-494
• Type: Improvement
• Status: Closed
• Resolution: Fixed
• Priority: Major
• Assignee: Alex Karasulu
• Reporter: Nick Faiz
• Fix Version/s: 1.0-RC1

Description

We need to identify the documentation which should be included in the standalone build. We also need to work out how the standalone argument should be used in the current release build script.

The current maven standalone goal, in main, can be leveraged for this purpose.

Comments

[Stefan Zoerner]

I would like to have a directory structure comparable to other (server) software like Tomcat, i.e. having sub directories like
- bin
- conf
- docs
- lib
- logs
(some are already there).

A non trivial example LDIF/DIT which can be used for tutorials and How-Tos would also be nice. How about a directory which contains these users (ASF members):
http://apache.org/foundation/members.html
If we do not use original E-Mail addresses, privacy of the members is respected, I think. We could also use the ASF structure for organizational units and so on.

[Stefan Zoerner]

In order to illustrate the LDIF idea, here is an example. It contains 128 person entries (inetOrgPerson) for the current ASF members. Alex has DN uid=alex,ou=people,dc=apache,dc=org, for instance.
I used HttpUnit to fetch the data from the page mentioned above. For the uid I have chosen the firstname. If not unique I appended a number (e.g. daniel2). Currently, only a few attributes are used (sn, cn, givenname, initials, labeledUri, uid).

Next steps would be:
* add groups for the different roles within ASF
* add groups for all projects (TLPs)
* fill groups with appropriate members
* add user passwords (e.g. in order to demonstrate Tomcat integration)
* add some JPEG photographs, if some members agree (to demonstrate binary data)

Maybe, we can place the finished file in a demo folder of the standalone ZIP build.

This is just for demonstration. Any ideas and feedback are welcome. Especially whether you think this is useful. If so, I will enhance/finish it.

[Nick Faiz]

Your suggested directory structure looks good.

The following doc files & directories are listed in directory/apacheds/trunk

 xdocs
README.txt
NOTICE.txt
LICENSE.txt
CHANGES.txt

I suppose everything but the README.txt and LICENSE.txt could be put into the docs directory you propose. The README and LICENSE would remain in the top level of the standalone structure.

The LDIF import example is a really good idea, although I don't think it needs to have 128 users to function as an example. Just let me know where you end up storing the demo LDIF.

I suppose I'll just move up the standalone goal in the project.xml of main to the trunk. It needs to be at this level, I think, to access the doc.s above.

[Alex Karasulu]

Take a look at the content of our existing distributions to see what is included. I guess all these should be somewhere in the tarball/zipball.

[Alex Karasulu]

this has been done with commmons-daemon and the various daemon installers.

[Emmanuel Lecharny]

Closing all issues created in 2005 and before which are marked resolved