[jira] [Resolved] (FC-18) Convert Config to non-singleton

[ https://issues.apache.org/jira/browse/FC-18?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-18. -- Resolution: Fixed Assignee: Chris Pike Fix Version/s: 1.0.1 task completed by Chris Pike

[jira] [Created] (FC-170) [ fortress-realm ] update to use non-static config

Shawn McKinney created FC-170: - Summary: [ fortress-realm ] update to use non-static config Key: FC-170 URL: https://issues.apache.org/jira/browse/FC-170 Project: FORTRESS Issue Type

Additions / Changes to Apache Directory Wikipedias

Howdy, An update about some shenanigans on our wikipedia pages. First I added this one: http://en.wikipedia.org/wiki/Apache_Fortress I asked community for some help on supplying references here:

[jira] [Commented] (FC-169) Can we change Dates and Times to be real dates and times

[ https://issues.apache.org/jira/browse/FC-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15257174#comment-15257174 ] Shawn McKinney commented on FC-169: --- I agree, but finding the time to work on it is another matter

[jira] [Commented] (FC-169) Can we change Dates and Times to be real dates and times

[ https://issues.apache.org/jira/browse/FC-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15256927#comment-15256927 ] Shawn McKinney commented on FC-169: --- Which brings me to the question of rationale. Why do you see

[jira] [Commented] (FC-169) Can we change Dates and Times to be real dates and times

[ https://issues.apache.org/jira/browse/FC-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15256921#comment-15256921 ] Shawn McKinney commented on FC-169: --- yeah the code to do the tranforms and validations are hidden behind

[jira] [Commented] (FC-169) Can we change Dates and Times to be real dates and times

[ https://issues.apache.org/jira/browse/FC-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15256889#comment-15256889 ] Shawn McKinney commented on FC-169: --- er what I mean to say is that we will need to continue to support dates

[jira] [Commented] (FC-169) Can we change Dates and Times to be real dates and times

[ https://issues.apache.org/jira/browse/FC-169?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15256881#comment-15256881 ] Shawn McKinney commented on FC-169: --- It will take a moderate amount of work but not complicated. Would

Re: Contribution of a declaritive SCIM based identity solution to the Apache Directory project

Pennsylshawn, It seems Emmanuel is out galavanting around the Greek Isles in search of new kinds of bugs and what not. ;-) So, we may have to wait until he decides to come back for a response. Arkanshawn > On Apr 20, 2016, at 1:52 PM, SHAWN E SMITH wrote: > > All, > > We

Apache Fortress 1.0.0 released

The Apache Directory Project announces the third release of Fortress. - Version 1.0.0: • http://directory.apache.org/fortress/downloads.html - Apache Fortress™ is a standards-based access management system, written in Java, that provides role-based access control, delegated

Re: Help with task: Fortress Doc Writers

> On Apr 16, 2016, at 2:11 PM, Steve Moyer wrote: > > > I can do a case study on how we're using Fortress for the Friends of Penn > State accounts (currently 3M users about 2M have one or more assigned roles). > We've could obviously generate a bunch of "how-tos" from our

Re: Help with task: Fortress Doc Writers

> On Apr 16, 2016, at 11:24 AM, Ghassan Maslamani > wrote: > > > I would like to help out with the task listed at > https://helpwanted.apache.org/task.html?c7e01e62 Ghassan, Welcome! Your timing is good as we could use help with the fortress project website:

Re: [RESULT][VOTE] Release Apache Directory Fortress 1.0.0

> On Apr 16, 2016, at 6:14 AM, Emmanuel Lécharny wrote: > > Le 16/04/16 11:36, Pierre Smits a écrit : >> Shawn, >> >> As far as I can tell we can't call this a successful vote. Many have >> expresses congratulations and have said testing it (or willingness to >> test), but

[RESULT][VOTE] Release Apache Directory Fortress 1.0.0

I am closing the vote with: 3 votes for: Emmanuel, Colm, me 3 non-binding votes for: Jiajai, Chris, Pennsylshawn Thanks for the help and support with this release, Shawn

Re: [VOTE] Release Apache Directory Fortress 1.0.0

> On Apr 13, 2016, at 1:52 PM, Stefan Seelmann wrote: > > I probably won't have time before Monday to check. Are there any > significant changes since the previous release? Mostly small bug fixes and software dependency upgrades. Also completely removed dependency on

[jira] [Resolved] (FC-163) [ fortress-core ] fortress.properties is not required

[ https://issues.apache.org/jira/browse/FC-163?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-163. --- Resolution: Fixed > [ fortress-core ] fortress.properties is not requi

Re: [VOTE] Release Apache Directory Fortress 1.0.0

> On Apr 13, 2016, at 4:20 AM, Emmanuel Lécharny wrote: > > Packages tested, source code from git tested, signatures tested, N > checked, we are all good ! > > Great job Shawn ! years of dedication to finally get a 1.0 out, hat down ! > > Let's get the beast out ! Code

Re: [VOTE] Release Apache Directory Fortress 1.0.0

> On Apr 13, 2016, at 3:24 AM, Emmanuel Lécharny wrote: > > There are things that are annoying : > - there are many source packages in > https://repository.apache.org/content/repositories/orgapachedirectory-1091/org/apache/directory/fortress/fortress-core/1.0.0/. > The only

Re: [VOTE] Release Apache Directory Fortress 1.0.0

> On Apr 13, 2016, at 3:44 AM, Emmanuel Lécharny wrote: > > One more thing : in order to test core, the > https://github.com/apache/directory-fortress-core/blob/master/README-QUICKSTART-APACHEDS.md > describes how to setup ApacheDS. That's fine, but there is a faster way, >

[VOTE] Release Apache Directory Fortress 1.0.0

Once again we vote for a release of Apache Directory Fortress core, realm, rest and web components. This version is 1.0.0 and a temporary tag has been created in git: ‘1.0.0'. The staging repo on Nexus: - core: https://repository.apache.org/content/repositories/orgapachedirectory-1091 -

Re: Task #a1384e00: Fortress Testers

> > On Apr 11, 2016, at 7:41 PM, Pratik Joshi wrote: > > Hello, > > I came across this "Help Wanted!" section enquiring about those interested in > helping with the testing aspect of Fortress. I am interested in providing > whatever help I can. Kindly let me know

[Fortress] Notice to cut a new release - 1.0.0

Hello, With the 1.0-RC42 release now successfully behind us it is time for the 1.0.0 GA. I will now begin working on this. Let me know if you have questions or concerns. Shawn

[jira] [Resolved] (FC-165) [ fortress-core ] getRootDn bug with tenant context

[ https://issues.apache.org/jira/browse/FC-165?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-165. --- Resolution: Fixed > [ fortress-core ] getRootDn bug with tenant cont

[jira] [Resolved] (FC-164) Remove dependency on ant

[ https://issues.apache.org/jira/browse/FC-164?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-164. --- Resolution: Fixed still dependent on ant-maven plugin to call targets in build-config.xml but separate

[jira] [Created] (FC-165) [ fortress-core ] getRootDn bug with tenant context

Shawn McKinney created FC-165: - Summary: [ fortress-core ] getRootDn bug with tenant context Key: FC-165 URL: https://issues.apache.org/jira/browse/FC-165 Project: FORTRESS Issue Type: Bug

[jira] [Created] (FC-164) Remove dependency on ant

Shawn McKinney created FC-164: - Summary: Remove dependency on ant Key: FC-164 URL: https://issues.apache.org/jira/browse/FC-164 Project: FORTRESS Issue Type: Improvement Affects Versions

Re: Apache Fortress 1.0-RC42 released

> On Mar 29, 2016, at 1:59 PM, Pierre Smits wrote: > > > It has been shared @twitter Cool, thanks Pierre.

Apache Fortress 1.0-RC42 released

Apache Fortress 1.0-RC42 released: http://directory.apache.org/fortress/downloads.html The Apache Directory Project announces the second release of Fortress which includes the Core, Realm, Rest and Web packages. - Apache Fortress™ is a standards based Access Management System for LDAPv3

[jira] [Commented] (FC-163) [ fortress-core ] fortress.properties is not required

[ https://issues.apache.org/jira/browse/FC-163?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15213780#comment-15213780 ] Shawn McKinney commented on FC-163: --- Tested web component by adding these params to catalina.sh: JAVA_OPTS

[jira] [Created] (FC-163) [ fortress-core ] fortress.properties is not required

Shawn McKinney created FC-163: - Summary: [ fortress-core ] fortress.properties is not required Key: FC-163 URL: https://issues.apache.org/jira/browse/FC-163 Project: FORTRESS Issue Type

[RESULT][VOTE] Release Apache Directory Fortress 1.0-RC42 (Take 2)

I am closing the vote with: 3 votes for: Emmanuel, Stefan, me and 1 non-binding vote for: Jiajai Thanks, Shawn > On Mar 20, 2016, at 2:55 AM, Shawn McKinney <smckin...@apache.org> wrote: > > Once again we vote to release of Apache Directory Fortress core, realm, rest > an

[jira] [Created] (FC-162) [ fortress-rest ] Upgrade to Apache CXF 3.x (and latest Spring)

Shawn McKinney created FC-162: - Summary: [ fortress-rest ] Upgrade to Apache CXF 3.x (and latest Spring) Key: FC-162 URL: https://issues.apache.org/jira/browse/FC-162 Project: FORTRESS Issue

Re: [VOTE] Release Apache Directory Fortress 1.0-RC42 (Take 2)

> > On Mar 21, 2016, at 2:51 PM, Stefan Seelmann wrote: > > > PS: Possible mprovements: > * Update dependencies (e.g. Wicket 6.19->6.22|7.2 or Spring 4.0.0->4.2.5) > * Automate instructions from quickstart / ten-minute-guide, e.g. using > Docker The upgrade to Wicket

[jira] [Created] (FC-161) add fortress indexes to apachds setup

Shawn McKinney created FC-161: - Summary: add fortress indexes to apachds setup Key: FC-161 URL: https://issues.apache.org/jira/browse/FC-161 Project: FORTRESS Issue Type: Bug Affects

Re: [VOTE] Release Apache Directory Fortress 1.0-RC42 (Take 2)

lity and listings for the produced web archives of web and rest components. This testing was performed on Centos7 64-bit machine using Java 8. Thanks, Shawn > On Mar 20, 2016, at 2:55 AM, Shawn McKinney <smckin...@apache.org> wrote: > > Once again we vote to release of Apache Dire

[jira] [Resolved] (FC-151) Possible deadlock condition in roleutil

[ https://issues.apache.org/jira/browse/FC-151?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-151. --- Resolution: Fixed Fix Version/s: 1.0.0-RC40 passed load testing using jmeter for createSession

[jira] [Created] (FC-160) [ fortress-web ] sonar testing major problems due to css

Shawn McKinney created FC-160: - Summary: [ fortress-web ] sonar testing major problems due to css Key: FC-160 URL: https://issues.apache.org/jira/browse/FC-160 Project: FORTRESS Issue Type: Bug

Re: [Fortress] Legal files cleanup (was Re: [VOTE] Release Apache Directory Fortress 1.0-RC42)

> On Mar 16, 2016, at 7:10 PM, Stefan Seelmann wrote: > > > Done for fortress-rest, please carefully review. I generally followed > [1] but also got inspiration from Syncope project as they also > distribute a web application with many dependencies. > > * Renamed file

[VOTE] Release Apache Directory Fortress 1.0-RC42 (Take 2)

Once again we vote to release of Apache Directory Fortress core, realm, rest and web version=1.0-RC42. A temporary tag has been created in git: 1.0-RC42. The staging repo on Nexus: https://repository.apache.org/content/repositories/orgapachedirectory-1086/ The source distros:

Re: [Fortress] Legal files cleanup (was Re: [VOTE] Release Apache Directory Fortress 1.0-RC42)

> On Mar 19, 2016, at 1:53 PM, Stefan Seelmann wrote: > > I also changed fortress-core and fortress-realm. I removed all 3rd party > licenses from lib folders and put the default NOTICE file. > > I think the 3rd party licenses and additional notices are not required >

[jira] [Resolved] (FC-159) [ fortress-web ] Upgrade to Spring Version 4

[ https://issues.apache.org/jira/browse/FC-159?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-159. --- Resolution: Fixed > [ fortress-web ] Upgrade to Spring Versio

[jira] [Created] (FC-159) [ fortress-web ] Upgrade to Spring Version 4

Shawn McKinney created FC-159: - Summary: [ fortress-web ] Upgrade to Spring Version 4 Key: FC-159 URL: https://issues.apache.org/jira/browse/FC-159 Project: FORTRESS Issue Type: Improvement

Re: [VOTE] Release Apache Directory Fortress 1.0-RC42

> On Mar 14, 2016, at 1:37 PM, Stefan Seelmann wrote: > > If noone else works on those issues till Wednesday, I can try to fix as > much as possible till then. Go for it Stefan, I won’t be able to work on it before then. Thanks Shawn

Re: [VOTE] Release Apache Directory Fortress 1.0-RC42

> On Mar 13, 2016, at 6:04 AM, Stefan Seelmann wrote: > > I have to vote -1. > > The blocker is that fortress-rest.war and fortress-web.war don't include > required licenses and notices. > * slf4j: permission notice needs to be included in LICENSE file > * accelerator:

Re: [VOTE] Release Apache Directory Fortress 1.0-RC42

> On Mar 12, 2016, at 9:52 PM, Zheng, Kai wrote: > > I checked the instructions Shawned initiated for the release vote, I have to > say that it's pretty complex or involves much overhead, particularly for me, > a guy that never has the time to absorb the complexity or

Re: [VOTE] Release Apache Directory Fortress 1.0-RC42

> On Mar 12, 2016, at 4:12 PM, Emmanuel Lécharny wrote: > > The third option that you have not listed : we were extremelly busy > until this week-end. I had to work all days and most of the nights for > the last 4 days, and I just had time to test Kerby in the train. Today

Re: [VOTE] Release Apache Directory Fortress 1.0-RC42

> On Mar 12, 2016, at 7:20 AM, Chris Pike wrote: > > I'm new to the process and I think it would help if you provided a basic > overview... Who is allowed vote, how does someone vote, what happens when a > vote is passed, what is expected of someone who votes yes, etc...?

Re: [VOTE] Release Apache Directory Fortress 1.0-RC42

> On Mar 12, 2016, at 6:48 AM, Shawn McKinney <smckin...@apache.org> wrote: > >> >> >> On Mar 12, 2016, at 6:17 AM, Stefan Seelmann <m...@stefan-seelmann.de> wrote: >> >> Instead I'd like to encourage the Fortress community (Chris, Jan,

Re: [VOTE] Release Apache Directory Fortress 1.0-RC42

> On Mar 12, 2016, at 6:17 AM, Stefan Seelmann <m...@stefan-seelmann.de> wrote: > > > On 03/12/2016 12:13 PM, Shawn McKinney wrote: >> The fact that we’re now 70 hours in w/out a response tells me one of two >> things. Either nobody’s interested, or th

Re: [VOTE] Release Apache Directory Fortress 1.0-RC42

> On Mar 9, 2016, at 8:54 AM, Shawn McKinney <smckin...@apache.org> wrote: > > The distributions are available for download: > http://home.apache.org/~smckinney/ > > If you are to test, you may follow either one of these README’s, located in > the root folder of the

Re: [VOTE] Release Apache Kerby 1.0.0-RC2

+1 Downloaded source bundle, to CentOS 7 64-bit, extracted and ran mvn clean install with both openjdk versions 1.7.0.91 & 1.8.0_71. Built and tests ran successfully. Shawn > On Mar 10, 2016, at 4:57 AM, Emmanuel Lécharny wrote: > > My binding +1. > > Packages tested,

Re: [Fortress] Problem generating the source release distro for the realm

> On Mar 9, 2016, at 2:08 PM, Stefan Seelmann wrote: > > The source package is *the* package we vote on, so it is always required. > ok > > On Mar 9, 2016, at 2:08 PM, Stefan Seelmann wrote: > > The source release package is generated

[jira] [Resolved] (FC-38) Potential issues on synchronized protected elements

[ https://issues.apache.org/jira/browse/FC-38?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-38. -- Resolution: Fixed Fix Version/s: (was: 1.0.0-RC41) 1.0.0-RC42 ehcache

[jira] [Resolved] (FC-3) Update the N files

[ https://issues.apache.org/jira/browse/FC-3?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-3. - Resolution: Done Fix Version/s: (was: 1.0.0-RC41) 1.0.0-RC42 done > Update th

[jira] [Resolved] (FC-82) upgrade CXF in rest component

[ https://issues.apache.org/jira/browse/FC-82?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-82. -- Resolution: Fixed delay upgrade to 3.x for another time. > upgrade CXF in rest compon

[jira] [Resolved] (FC-41) Not sure it's valuable to check the attributes on the client side

[ https://issues.apache.org/jira/browse/FC-41?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-41. -- Resolution: Not A Problem for the time being will leave client side validations in place. > Not sure i

[jira] [Commented] (FC-38) Potential issues on synchronized protected elements

[ https://issues.apache.org/jira/browse/FC-38?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15188165#comment-15188165 ] Shawn McKinney commented on FC-38: -- resolved here > Potential issues on synchronized protected eleme

[jira] [Closed] (FC-46) Prepare core rest client

[ https://issues.apache.org/jira/browse/FC-46?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney closed FC-46. Resolution: Not A Problem Fix Version/s: (was: 1.0.0-RC41) 1.0.0-RC42 unclear what

[jira] [Resolved] (FC-76) Firefox 36.0 breaks Fortress Web on Ubuntu 14.04

[ https://issues.apache.org/jira/browse/FC-76?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-76. -- Resolution: Fixed Fix Version/s: (was: 1.0.0-RC41) 1.0.0-RC42 fixed > Fire

[jira] [Commented] (FC-76) Firefox 36.0 breaks Fortress Web on Ubuntu 14.04

[ https://issues.apache.org/jira/browse/FC-76?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15188150#comment-15188150 ] Shawn McKinney commented on FC-76: -- using these dependencies problem goes away

[jira] [Commented] (FC-82) upgrade CXF in rest component

[ https://issues.apache.org/jira/browse/FC-82?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15188148#comment-15188148 ] Shawn McKinney commented on FC-82: -- currently at 2.7.18 which is last stable 2.x release. > upgrade

[jira] [Resolved] (FC-126) ApacheDS Quickstart

[ https://issues.apache.org/jira/browse/FC-126?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-126. --- Resolution: Fixed > ApacheDS Quickstart > --- > >

[jira] [Resolved] (FC-125) OpenLDAP Quickstart

[ https://issues.apache.org/jira/browse/FC-125?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-125. --- Resolution: Fixed > OpenLDAP Quickstart > --- > >

[jira] [Resolved] (FC-124) Quickstarts

[ https://issues.apache.org/jira/browse/FC-124?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-124. --- Resolution: Fixed > Quickstarts > --- > > Key: FC-124 >

[jira] [Resolved] (FC-153) [ fortress-web ] pwpolicy name contains its rdn value

[ https://issues.apache.org/jira/browse/FC-153?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-153. --- Resolution: Fixed fixed > [ fortress-web ] pwpolicy name contains its rdn va

[VOTE] Release Apache Directory Fortress 1.0-RC42

Hello, This vote is for the release of Apache Directory Fortress 1.0-RC42. Since it's been almost a year since the last release, and even then it was just the core and not the rest (pun intended:), there's a long list of fixed issues - over 50:

Re: [Fortress] Problem generating the source release distro for the realm

> On Mar 9, 2016, at 2:04 AM, Stefan Seelmann wrote: > > Quick check from my side: the pom.xml of realm project (1) skips the > maven-assembly-plugin from the apache-release profile and (2) it's own > configuration is commented out. I'm not sure if a custom assembly >

Re: [Fortress] Problem generating the source release distro for the realm

code the apache way…. :-) Thanks for all the help, Shawn > On Mar 8, 2016, at 6:19 PM, Shawn McKinney <smckin...@apache.org> wrote: > > Hello, > > another problem: > > When I perform this step: > > -- > Step 6 : Build the Site > $ cd target/chec

[Fortress] Problem generating the source release distro for the realm

Hello, another problem: When I perform this step: -- Step 6 : Build the Site $ cd target/checkout $ mvn site -- It does not create the release packages. in other words when I run this search from realm’s package root: find -name *source-release.zip* It comes up empty. There are

Re: [Fortress] Release Status - Can't close staging repo

> On Mar 8, 2016, at 4:24 PM, Stefan Seelmann wrote: > > > No, not the PGP/GPG fingerprint, your SSH key. > >cat ~/.ssh/id_rsa.pub (or similar) > > and then put the whole content into the > >SSH Key (authorized_keys line): > > field. ah yes that did the

Re: [Fortress] Release Status - Can't close staging repo

> On Mar 8, 2016, at 3:59 PM, Stefan Seelmann wrote: > > Yes, that server is now home.apache.org, and you can no longer ssh to > it, only sftp is possible. No problem there. > > On Mar 8, 2016, at 3:59 PM, Stefan Seelmann wrote: > > To

Re: [Fortress] Release Status - Can't close staging repo

> On Mar 8, 2016, at 2:31 PM, Stefan Seelmann wrote: > > > please check https://www.apache.org/dev/release-signing.html and especially > > * upload the public key to a keyserver: [1] > > * append the public key to our KEYS file: [2] > (our KEYS file is [3], you

[Fortress] Release Status - Can't close staging repo

Hello, I have succeeded in staging the fortress components to nexus. Which gets me to Step 5 of the release instructions: http://directory.staging.apache.org/fortress/developer-guide.html#releasing-a-point-release-committers-only - Step 5 Now, you have to close the staged project on

[jira] [Commented] (FC-152) Upgrade to kendo wicket.kendo-ui.version 6.15.0

[ https://issues.apache.org/jira/browse/FC-152?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15184873#comment-15184873 ] Shawn McKinney commented on FC-152: --- https://groups.google.com/forum/#!topic/wicket-jquery-ui/ZjNExOSgnZc

[jira] [Created] (FC-153) [ fortress-web ] pwpolicy name contains its rdn value

Shawn McKinney created FC-153: - Summary: [ fortress-web ] pwpolicy name contains its rdn value Key: FC-153 URL: https://issues.apache.org/jira/browse/FC-153 Project: FORTRESS Issue Type: Bug

[jira] [Resolved] (FC-152) Upgrade to kendo wicket.kendo-ui.version 6.15.0

[ https://issues.apache.org/jira/browse/FC-152?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-152. --- Resolution: Fixed > Upgrade to kendo wicket.kendo-ui.version 6.1

[jira] [Created] (FC-152) Upgrade to kendo wicket.kendo-ui.version 6.15.0

Shawn McKinney created FC-152: - Summary: Upgrade to kendo wicket.kendo-ui.version 6.15.0 Key: FC-152 URL: https://issues.apache.org/jira/browse/FC-152 Project: FORTRESS Issue Type: Improvement

Re: [Fortress] Need Karma to publish release artifacts

> On Mar 6, 2016, at 4:47 PM, Shawn McKinney <smckin...@apache.org> wrote: > >> >> On Mar 6, 2016, at 1:39 PM, Stefan Seelmann <m...@stefan-seelmann.de> wrote: >> >> Were you able to do an "mvn deploy" of the snapshots before starting the &g

Re: [Fortress] Need Karma to publish release artifacts

Hey Stefan, thanks for the quick response. > On Mar 6, 2016, at 1:39 PM, Stefan Seelmann wrote: > > can you login to https://repository.apache.org/ and do you see on the > left-hand side the "Staging Repositories" link? Yes > On Mar 6, 2016, at 1:39 PM, Stefan

[Fortress] Need Karma to publish release artifacts

Got this error today while performing release on core. How do I get the proper access? [INFO] [INFO] [INFO] [INFO] BUILD FAILURE [INFO] [INFO]

[jira] [Created] (FC-151) Possible deadlock condition in roleutil

Shawn McKinney created FC-151: - Summary: Possible deadlock condition in roleutil Key: FC-151 URL: https://issues.apache.org/jira/browse/FC-151 Project: FORTRESS Issue Type: Bug Affects

Re: Trouble releasing 1.0.0-RC41

> On Mar 1, 2016, at 4:22 PM, Emmanuel Lécharny wrote: > > and I can't remove it. > > Here, I have 2 options : > - either someone tells me how to get rid of this version > - or I switch to 1.0-RC42 > > Frankly, the second solution seems to me the simpler. > > > If

[Fortress] Notice to cut a new release - 1.0-RC41

Hello, This release will include the four components, core, realm, rest and web. The goal is to use this release to get everything in order for a 1.0 GA to follow soon after (as in a couple of weeks). Important note: To date there has only been one release of fortress, 1.0-RC40, and that

[jira] [Created] (FC-147) [ fortress-web ] Upgrade to Wicket Version 7

Shawn McKinney created FC-147: - Summary: [ fortress-web ] Upgrade to Wicket Version 7 Key: FC-147 URL: https://issues.apache.org/jira/browse/FC-147 Project: FORTRESS Issue Type: Improvement

Re: Write access in Confluence

> On Feb 16, 2016, at 3:48 PM, Jan Sindberg <jan.sindb...@gmail.com> wrote: > > We would like to start using Confluence for Fortress documentation and > development documents. Shawn McKinney have created a space. Is there a way > for me to be allowed to edit within that sp

[jira] [Resolved] (FC-133) Change audit flags

[ https://issues.apache.org/jira/browse/FC-133?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-133. --- Resolution: Fixed 1. corrected audit flag usage in properties 2. fixed slapd.conf acl's 3

[jira] [Resolved] (FC-145) Jmeter test improvements

[ https://issues.apache.org/jira/browse/FC-145?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-145. --- Resolution: Fixed 1. Added test cases for AccelMgr and AccessMgr sessionPermissions & createSession

[jira] [Commented] (FC-144) Ability to assign groups to roles

[ https://issues.apache.org/jira/browse/FC-144?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15125416#comment-15125416 ] Shawn McKinney commented on FC-144: --- The use case here is federated and multi-tenant login into openstack

[jira] [Resolved] (FC-143) Let LdapClientTrustStoreManager read trust store from jar

[ https://issues.apache.org/jira/browse/FC-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-143. --- Resolution: Fixed I tested with apacheds both use cases. Truststore on classapth, truststore fully

[jira] [Commented] (FC-143) Let LdapClientTrustStoreManager read trust store from jar

[ https://issues.apache.org/jira/browse/FC-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15125556#comment-15125556 ] Shawn McKinney commented on FC-143: --- Applied patch. It works both for file on classpath or fully qualified

[jira] [Created] (FC-145) Jmeter test improvements

Shawn McKinney created FC-145: - Summary: Jmeter test improvements Key: FC-145 URL: https://issues.apache.org/jira/browse/FC-145 Project: FORTRESS Issue Type: Improvement Affects Versions

[jira] [Commented] (FC-143) Let LdapClientTrustStoreManager read trust store from jar

[ https://issues.apache.org/jira/browse/FC-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15123584#comment-15123584 ] Shawn McKinney commented on FC-143: --- Jan, here is what I think needs to be done here: 1. remove

[jira] [Reopened] (FC-143) Let LdapClientTrustStoreManager read trust store from jar

[ https://issues.apache.org/jira/browse/FC-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney reopened FC-143: --- need to do some more work down in here > Let LdapClientTrustStoreManager read trust store from

[jira] [Resolved] (FC-143) Let LdapClientTrustStoreManager read trust store from jar

[ https://issues.apache.org/jira/browse/FC-143?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-143. --- Resolution: Fixed Fix Version/s: 1.0.0-RC41 Applied the patch. Had to correct a minor error where

[jira] [Resolved] (FC-142) Config.getExternalConfig sets LDAP_ADMIN_POOL_MAX as int but all other ints as string

[ https://issues.apache.org/jira/browse/FC-142?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-142. --- Resolution: Fixed changed to: config.setProperty( GlobalIds.LDAP_ADMIN_POOL_MAX, szValue

[jira] [Commented] (FC-140) System properties cannot override values for trust store

[ https://issues.apache.org/jira/browse/FC-140?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121616#comment-15121616 ] Shawn McKinney commented on FC-140: --- another good catch > System properties cannot override val

[jira] [Resolved] (FC-140) System properties cannot override values for trust store

[ https://issues.apache.org/jira/browse/FC-140?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ] Shawn McKinney resolved FC-140. --- Resolution: Fixed Fix Version/s: 1.0.0-RC41 applied change as recommended > System propert

[Fortress]Developers List

Fellow Dev's, We’ve just added a new committer to fortress, and my goal is to add a few more before long. My question is which list to use for communicating? In the past, with our limited discussions, we’ve used the fortress list. But that list is (supposed to be) for users. We could use

[jira] [Commented] (FC-143) Let LdapClientTrustStoreManager read trust store from jar

[ https://issues.apache.org/jira/browse/FC-143?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121552#comment-15121552 ] Shawn McKinney commented on FC-143: --- I think this is a good idea. > Let LdapClientTrustStoreManager r

[jira] [Commented] (FC-141) Config from repository is adding instead of overriding

[ https://issues.apache.org/jira/browse/FC-141?page=com.atlassian.jira.plugin.system.issuetabpanels:comment-tabpanel=15121565#comment-15121565 ] Shawn McKinney commented on FC-141: --- nice catch > Config from repository is adding instead of overrid

<    5   6   7   8   9   10   11   12   13   14   >