Ansible
PS DSC
Downloads:
4,359
Downloads of v 2.0.0-M9:
462
Last Update:
28 Jul 2015
Package Maintainer(s):
Software Author(s):
- Apache
Tags:
apache ldap activedirectory- Software Specific:
- Software Site
- Software License
- Package Specific:
- Possible Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Apache Directory Studio
This is a prerelease version of Apache Directory Studio.
- 1
- 2
- 3
2.0.0-M9 | Updated: 28 Jul 2015
- Software Specific:
- Software Site
- Software License
- Package Specific:
- Possible Package Source
- Package outdated?
- Package broken?
- Contact Maintainers
- Contact Site Admins
- Software Vendor?
- Report Abuse
- Download
Downloads:
4,359
Downloads of v 2.0.0-M9:
462
Maintainer(s):
Software Author(s):
- Apache
Apache Directory Studio 2.0.0-M9
This is a prerelease version of Apache Directory Studio.
- 1
- 2
- 3
Some Checks Have Failed or Are Not Yet Complete
Not All Tests Have Passed
Validation Testing Unknown
Verification Testing Unknown
Scan Testing Successful:
No detections found in any package files
WARNING
This package is unlisted and hidden from package listings.
Description
Apache Directory Studio is a complete directory tooling platform intended to be used with any LDAP server however it is particularly designed for use with ApacheDS. It is an Eclipse RCP application, composed of several Eclipse (OSGi) plugins, that can be easily upgraded with additional ones. These plugins can even run within Eclipse itself.
Files
tools\bins.ps1
<#
.SYNOPSIS
Create a .ignore file for a package binary.
.DESCRIPTION
Chocolatey automatically creates a "shim" in a special folder, on your
machine's PATH, for any executables found in the package's installation
directory. This is helpful when installing ZIP packages or any kind of
command line tools.
Chocolatey can be instructed to ignore a particular binary by creating a file
at the same path with the same name as the binary to ignore, except ending
with the file extension ".ignore".
This function creates that file, given the binary's path.
.PARAMETER Path
The path of the binary to ignore.
This parameter also accepts multiple paths or pipeline input.
.EXAMPLE
New-IgnoreBin -Path "foo.exe"
.EXAMPLE
New-IgnoreBin -Path $foo, $bar
.EXAMPLE
Get-ChildItem "$content\foo\*.exe" | New-IgnoreBin
.LINK
https://github.com/AnthonyMastrean/chocolateypackages/blob/master/helpers/bins.ps1
#>
function New-IgnoreBin {
[CmdletBinding()]
param(
[Parameter(Mandatory = $true, ValueFromPipeline = $true)]
[ValidateNotNullOrEmpty()]
[ValidateScript({ Test-Path $_ })]
[string[]] $Path
)
PROCESS {
foreach($item in $Path) {
New-Item "$(Resolve-Path $item).ignore" -Type "File" -Force | Out-Null
}
}
}
<#
.SYNOPSIS
Create a .gui file for a package binary.
.DESCRIPTION
Chocolatey automatically creates a "shim" in a special folder, on your
machine's PATH, for any executables found in the package's installation
directory. This is helpful when installing ZIP packages or any kind of
command line tools.
Chocolatey can be instructed to treat a particular binary as a GUI application,
meaning it will START the binary in a separate process and not block the
console, by creating a file at the same path with the same name as the binary,
except ending with the file extension ".gui".
This function creates that file, given the binary's path.
.PARAMETER Path
The path of the binary to treat as a GUI application.
This parameter also accepts multiple paths or pipeline input.
.EXAMPLE
New-GuiBin -Path "foo.exe"
.EXAMPLE
New-GuiBin -Path $foo, $bar
.EXAMPLE
Get-ChildItem "$content\foo\*.exe" | New-GuiBin
.LINK
https://github.com/AnthonyMastrean/chocolateypackages/blob/master/helpers/bins.ps1
#>
function New-GuiBin {
[CmdletBinding()]
param(
[Parameter(Mandatory = $true, ValueFromPipeline = $true)]
[ValidateNotNullOrEmpty()]
[ValidateScript({ Test-Path $_ })]
[string[]] $Path
)
PROCESS {
foreach($item in $Path) {
New-Item "$(Resolve-Path $item).gui" -Type "File" -Force | Out-Null
}
}
}
tools\chocolateyInstall.ps1
tools\chocolateyUninstall.ps1
$id = "apachedirectorystudio"
$name = "Apache Directory Studio"
$tools = Split-Path $MyInvocation.MyCommand.Definition
. $tools\shortcut.ps1
Remove-Shortcut -Link $name -SpecialFolder "CommonPrograms"
tools\shortcut.ps1
<#
.SYNOPSIS
New-Shortcut creates a new shortcut to a file or program.
.DESCRIPTION
New-Shortcut wraps the COM Object, Wscript.Shell, and its arguments to create
a shortcut to a file or program. It requires some very specific input, please
review the notes on each parameter.
.PARAMETER Link
The shortcut to create.
The underlying COM Object requires an absolute path. This function will
attempt to properly expand that path, especially if you provide a
SpecialFolder as a root directory.
The underlying COM Object also requires that the link's path/name end in
either .lnk or .url. This function will attempt to add that file extension if
it is not provided.
The underlying COM Object will fail silently in many cases, especially due to
improperly formatted link paths. This function will test the existence of the
expected link using this parameter and fail if it is not found.
.PARAMETER Target
The target of the shortcut.
This path must exist. This function will attempt to expand the path to its
absolute value.
.PARAMETER SpecialFolder
The Windows special folder to contain this shortcut.
If you want to create a shortcut at one of the system managed paths, such as
the Desktop or the Start Menu, you should use the special tokens provided.
The most commonly used are
* CommonDesktop
* CommonStartup
* CommonPrograms
If you provide a special folder, the Link parameter may contain a simple
"name" and not a file path.
The full list of special folders can be found here:
https://msdn.microsoft.com/en-us/library/system.environment.specialfolder(v=vs.110).aspx
.PARAMETER Icon
The icon of the shortcut.
This can take several forms and, due to this, is not validated carefully. You
can provide an absolute file path (this is your responsibility), like
"C:\Windows\notepad.exe"
Or, you can provide an absolute file path and an index into the resources of
that program, like
"C:\Windows\notepad.exe, 1"
.PARAMETER Description
The tooltip to display on the shortcut.
.EXAMPLE
New-Shortcut -Link "foo" -Target "foo.exe" -SpecialFolder "CommonDesktop" -Description "The Foo program"
.EXAMPLE
Remove-Shortcut -Link "foo" -SpecialFolder "CommonDesktop"
.LINK
https://github.com/AnthonyMastrean/chocolateypackages/blob/master/helpers/shortcut.ps1
#>
function New-Shortcut {
[CmdletBinding()]
param(
[Parameter(Mandatory = $true)]
[ValidateNotNullOrEmpty()]
[string] $Link,
[Parameter(Mandatory = $true)]
[ValidateNotNullOrEmpty()]
[ValidateScript({ Test-Path $_ })]
[string] $Target,
[string] $SpecialFolder,
[string] $Icon,
[string] $Description
)
$Link = Resolve-ShortcutLink -Link $Link -SpecialFolder $SpecialFolder
$shell = New-Object -ComObject 'Wscript.Shell'
$shortcut = $shell.CreateShortcut($Link)
$shortcut.TargetPath = (Resolve-Path $Target)
$shortcut.WorkingDirectory = (Split-Path (Resolve-Path $Target))
if($Icon) {
$shortcut.IconLocation = $Icon
}
if($Description) {
$shortcut.Description = $Description
}
$shortcut.Save()
if(-not(Test-Path $Link)) {
throw "Failed to create shortcut: $Link"
}
}
function Remove-Shortcut {
[CmdletBinding()]
param(
[Parameter(Mandatory = $true)]
[ValidateNotNullOrEmpty()]
[string] $Link,
[string] $SpecialFolder
)
$Link = Resolve-ShortcutLink -Link $Link -SpecialFolder $SpecialFolder
Remove-Item $Link -Force | Out-Null
}
function Resolve-ShortcutLink {
param(
[Parameter(Mandatory = $true)]
[ValidateNotNullOrEmpty()]
[string] $Link,
[string] $SpecialFolder
)
if(-not($Link.ToLower().EndsWith('.lnk') -or $Link.ToLower().EndsWith('.url'))) {
$Link = "$Link.lnk"
}
if($SpecialFolder) {
$Link = Join-Path ([System.Environment]::GetFolderPath($SpecialFolder)) $Link
}
$ExecutionContext.SessionState.Path.GetUnresolvedProviderPathFromPSPath($Link)
}
tools\uninstall.ps1
<#
.SYNOPSIS
Get the uninstaller location for most Windows software.
.DESCRIPTION
This function finds the correct uninstaller given just an application name.
Find the name from the Programs and Features Control Panel window.
.PARAMETER Name
The name of the application, as found in the Programs and Features applet
in the Control Panel.
.EXAMPLE
Uninstall-ChocolateyPackage 'foo' 'EXE' '/S' (Get-Uninstaller -Name 'Foo')
.LINK
https://github.com/AnthonyMastrean/chocolateypackages/blob/master/helpers/uninstall.ps1
#>
function Get-Uninstaller {
[CmdletBinding()]
param(
[Parameter(Mandatory = $true)]
[ValidateNotNullOrEmpty()]
[string] $Name
)
$local_key = 'HKCU:\Software\Microsoft\Windows\CurrentVersion\Uninstall\*'
$machine_key32 = 'HKLM:\SOFTWARE\Microsoft\Windows\CurrentVersion\Uninstall\*'
$machine_key64 = 'HKLM:\SOFTWARE\Wow6432Node\Microsoft\Windows\CurrentVersion\Uninstall\*'
@($local_key, $machine_key32, $machine_key64) `
| ?{ Test-Path $_ } `
| Get-ItemProperty `
| ?{ $_.DisplayName -eq $Name } `
| Select-Object -ExpandProperty UninstallString
}
Virus Scan Results
Log in or click on link to see number of positives.
In cases where actual malware is found, the packages are subject to removal. Software sometimes has false positives. Moderators do not necessarily validate the safety of the underlying software, only that a package retrieves software from the official distribution point and/or validate embedded software against official distribution point (where distribution rights allow redistribution).
Chocolatey Pro provides runtime protection from possible malware.
Version History
| Add to Builder | Version | Downloads | Last Updated | Status |
|---|---|---|---|---|
| Apache Directory Studio 2.0.0-M17 | 686 | Sunday, July 25, 2021 | Exempted | |
| Apache Directory Studio 2.0.0-M16 | 376 | Monday, February 22, 2021 | Exempted | |
| Apache Directory Studio 2.0.0-M15 | 179 | Saturday, January 16, 2021 | Exempted | |
| Apache Directory Studio 2.0.0-M12 | 428 | Monday, December 19, 2016 | Exempted | |
| Apache Directory Studio 2.0.0-M10 | 392 | Wednesday, May 11, 2016 | Exempted |
Dependencies
-
- javaruntime (≥ 7.0 && < 8.0)
Discussion for the Apache Directory Studio Package
Ground Rules:
- This discussion is only about Apache Directory Studio and the Apache Directory Studio package. If you have feedback for Chocolatey, please contact the Google Group.
- This discussion will carry over multiple versions. If you have a comment about a particular version, please note that in your comments.
- The maintainers of this Chocolatey Package will be notified about new comments that are posted to this Disqus thread, however, it is NOT a guarantee that you will get a response. If you do not hear back from the maintainers after posting a message below, please follow up by using the link on the left side of this page or follow this link to contact maintainers. If you still hear nothing back, please follow the package triage process.
- Tell us what you love about the package or Apache Directory Studio, or tell us what needs improvement.
- Share your experiences with the package, or extra configuration or gotchas that you've found.
- If you use a url, the comment will be flagged for moderation until you've been whitelisted. Disqus moderated comments are approved on a weekly schedule if not sooner. It could take between 1-5 days for your comment to show up.