You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@directory.apache.org by "Nick Faiz (JIRA)" <di...@incubator.apache.org> on 2005/09/20 02:13:28 UTC
[jira] Created: (DIREVE-264) Standalone build should be available for 0.9.3
Standalone build should be available for 0.9.3
----------------------------------------------
Key: DIREVE-264
URL: http://issues.apache.org/jira/browse/DIREVE-264
Project: Directory Server
Type: Improvement
Versions: 0.9.3
Reporter: Nick Faiz
Assigned to: Alex Karasulu
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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Resolved: (DIRSERVER-494) Standalone build should be
available for 0.9.3
Posted by "Alex Karasulu (JIRA)" <ji...@apache.org>.
[ http://issues.apache.org/jira/browse/DIRSERVER-494?page=all ]
Alex Karasulu resolved DIRSERVER-494:
-------------------------------------
Fix Version: 1.0-RC1
Resolution: Fixed
this has been done with commmons-daemon and the various daemon installers.
> Standalone build should be available for 0.9.3
> ----------------------------------------------
>
> Key: DIRSERVER-494
> URL: http://issues.apache.org/jira/browse/DIRSERVER-494
> Project: Directory ApacheDS
> Type: Improvement
> Reporter: Nick Faiz
> Assignee: Alex Karasulu
> Fix For: 1.0-RC1
> Attachments: apache.ldif
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (DIRSERVER-494) Standalone build should be available
for 0.9.3
Posted by "Emmanuel Lecharny (JIRA)" <ji...@apache.org>.
[ https://issues.apache.org/jira/browse/DIRSERVER-494?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Lecharny closed DIRSERVER-494.
---------------------------------------
Closing all issues created in 2005 and before which are marked resolved
> Standalone build should be available for 0.9.3
> ----------------------------------------------
>
> Key: DIRSERVER-494
> URL: https://issues.apache.org/jira/browse/DIRSERVER-494
> Project: Directory ApacheDS
> Issue Type: Improvement
> Reporter: Nick Faiz
> Assigned To: Alex Karasulu
> Fix For: 1.0-RC1
>
> Attachments: apache.ldif
>
>
> 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.
--
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.
[jira] Updated: (DIREVE-264) Standalone build should be available for 0.9.3
Posted by "Stefan Zoerner (JIRA)" <di...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/DIREVE-264?page=all ]
Stefan Zoerner updated DIREVE-264:
----------------------------------
Attachment: apache.ldif
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.
> Standalone build should be available for 0.9.3
> ----------------------------------------------
>
> Key: DIREVE-264
> URL: http://issues.apache.org/jira/browse/DIREVE-264
> Project: Directory Server
> Type: Improvement
> Versions: 0.9.3
> Reporter: Nick Faiz
> Assignee: Alex Karasulu
> Attachments: apache.ldif
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (DIREVE-264) Standalone build should be available for 0.9.3
Posted by "Nick Faiz (JIRA)" <di...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/DIREVE-264?page=comments#action_12330003 ]
Nick Faiz commented on DIREVE-264:
----------------------------------
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.
> Standalone build should be available for 0.9.3
> ----------------------------------------------
>
> Key: DIREVE-264
> URL: http://issues.apache.org/jira/browse/DIREVE-264
> Project: Directory Server
> Type: Improvement
> Versions: 0.9.3
> Reporter: Nick Faiz
> Assignee: Alex Karasulu
> Attachments: apache.ldif
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (DIREVE-264) Standalone build should be available for 0.9.3
Posted by "Alex Karasulu (JIRA)" <di...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/DIREVE-264?page=comments#action_12330007 ]
Alex Karasulu commented on DIREVE-264:
--------------------------------------
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.
> Standalone build should be available for 0.9.3
> ----------------------------------------------
>
> Key: DIREVE-264
> URL: http://issues.apache.org/jira/browse/DIREVE-264
> Project: Directory Server
> Type: Improvement
> Versions: 0.9.3
> Reporter: Nick Faiz
> Assignee: Alex Karasulu
> Attachments: apache.ldif
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Commented: (DIREVE-264) Standalone build should be available for 0.9.3
Posted by "Stefan Zoerner (JIRA)" <di...@incubator.apache.org>.
[ http://issues.apache.org/jira/browse/DIREVE-264?page=comments#action_12329972 ]
Stefan Zoerner commented on DIREVE-264:
---------------------------------------
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.
> Standalone build should be available for 0.9.3
> ----------------------------------------------
>
> Key: DIREVE-264
> URL: http://issues.apache.org/jira/browse/DIREVE-264
> Project: Directory Server
> Type: Improvement
> Versions: 0.9.3
> Reporter: Nick Faiz
> Assignee: Alex Karasulu
>
> 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.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira