and then deleted the shiro
directory. Is there anything else required for Shiro? Aside from
this issue, I'm not aware of any other migration issues.
Thanks,
--
Les Hazlewood
Founder, Katasoft, Inc.
Application Security Products Professional Apache Shiro Support and Training:
http://www.katasoft.com
.
Best,
--
Les Hazlewood
Founder, Katasoft, Inc.
Application Security Products Professional Apache Shiro Support and Training:
http://www.katasoft.com
-
To unsubscribe, e-mail: general-unsubscr...@incubator.apache.org
Hi Greg,
For Shiro, we copied a referenced charter from the Incubator site listed here:
http://incubator.apache.org/guides/graduation.html#tlp-resolution
That section references a template and 3 projects from the 2006 Board
minutes. I don't remember the template link being there at the time
Thanks!
On Wed, Oct 6, 2010 at 11:10 PM, David Crossley cross...@apache.org wrote:
Les Hazlewood wrote:
Hi all,
As Apache Shiro has graduated to a TLP, the post graduation guidelines
[1] indicate that now is a good time to be removed from the Incubator
reporting schedule.
How do we ensure
Hi all,
As Apache Shiro has graduated to a TLP, the post graduation guidelines
[1] indicate that now is a good time to be removed from the Incubator
reporting schedule.
How do we ensure that we are removed?
Thanks,
Les
(Apache Shiro PMC Chair)
[1]
Thanks so much Niall for both the vote and the svn commit!
Les
On Wed, Aug 18, 2010 at 1:41 PM, Niall Pemberton
niall.pember...@gmail.com wrote:
On Tue, Aug 17, 2010 at 7:13 PM, Kalle Korhonen
kalle.o.korho...@gmail.com wrote:
Fixed both issues Sebb raised. I doubt either was an impediment to
On Tue, Aug 17, 2010 at 3:52 PM, Kevan Miller kevan.mil...@gmail.com wrote:
* Les Hazlewood (lhazlew...@apache.org)
* Kalle Korhonen (kao...@apache.org)
* Peter Ledbrook (pledbr...@apache.org)
* Jeremy Haile (jha...@apache.org)
* Craig L Russell (craig.russ
first stable release.
Best Regards,
Les Hazlewood
--
Release Notes are browsable online here:
https://issues.apache.org/jira/secure/ReleaseNote.jspa?projectId=12310950styleName=Htmlversion=12314078
And included here for convenience:
Release Notes - Shiro - Version 1.0.0-incubating
** Bug
The download page links to reposity.apache.org.
However repository.apache.org is not to be used for direct
publication to end users, it is for publishing to the main maven repo.
This wasn't clear on the apache infrastructure page - it states that
repository.apache.org is part of the
-
maybe I can lend you a hand
Cheers,
Siegfried Goeschl
On 01.06.10 22:26, Les Hazlewood wrote:
The download page links to reposity.apache.org.
However repository.apache.org is not to be used for direct
publication to end users, it is for publishing to the main maven repo
Yay! It has been a long time coming, to say the least :) Thanks to
all who helped us through our 1.0 release!
On Fri, May 28, 2010 at 4:42 PM, Craig L Russell
craig.russ...@oracle.com wrote:
Congratulations!
You're now on the slippery slope out of incubation. ;-)
Craig
On May 28, 2010, at
On Wed, May 26, 2010 at 7:12 AM, sebb seb...@gmail.com wrote:
The staging site appeared to be part of the vote as it was not
specifically excluded.
This was a mistake - it probably should have been excluded. AFAICT,
staging sites are _not_ considered release artifacts because they're
never
On Wed, May 26, 2010 at 8:11 AM, ant elder ant.el...@gmail.com wrote:
I can't find all the source for the release. AFAICT the only way to
recreate all the release artifacts would be from the svn tag but thats
not enough as an ASF release must include a source release. If I've
just missed it
Thanks Ant!
And we'll be updating the website today to have all the valid
disclaimers and links back to the Incubator website.
On Wed, May 26, 2010 at 11:02 AM, ant elder antel...@apache.org wrote:
On Wed, May 26, 2010 at 5:39 PM, Les Hazlewood l...@hazlewood.com wrote:
On Wed, May 26, 2010
Some of them barely mention Apache and the Incubator:
http://incubator.apache.org/shiro/
No disrespect, but I find this example unfounded. If you go to that
website, you see a _huge_ font (and a feather) that leaves absolutely
no room for interpretation that we're an Apache project. We have
Hi all,
When trying to learn about and set up Confluence Auto-Export for our
podling website, I never really understood the process - the
information I got was fragmented from difference sources - or minimal,
making assumptions about my knowledge of Apache infrastructure, of
which I had almost
been removed from incubator group
for some reason. I'm a committer in Shiro project, currently in
incubator. This happened some weeks ago (caused by the JIRA breach or
some restructuring?) and I'm certain I was part of the group before.
Les Hazlewood (lhazlewood, also a committer in the same
OAuth 2 support (client + server) is on the roadmap for Apache Shiro.
Does this mean we could have potentially 2 Apache implementations?
(Fine by me if necessary - let a million flowers bloom and all that
;)). Just curious...
Les
On Fri, Apr 30, 2010 at 10:17 AM, Alan D. Cabrera
maintained at
http://svn.apache.org/repos/asf/incubator/shiro/STATUS
On Fri, Apr 16, 2010 at 2:53 PM, Les Hazlewood lhazlew...@apache.org wrote:
I got home really late last night - doing it right now.
On Fri, Apr 16, 2010 at 6:42 AM, Kalle Korhonen
kalle.o.korho...@gmail.com wrote:
Traveling
Incubator list, please disregard this request - It has been posted.
Thanks!
Les
On Fri, Apr 16, 2010 at 3:07 PM, Les Hazlewood lhazlew...@apache.org wrote:
Hi all,
I'm having problems posting our incubator board report (Apache Shiro)
to the wiki - apparently my username/password
, 2009 at 3:09 PM, Les Hazlewood lhazlew...@apache.org
wrote:
Hi Alan,
Is there anything I can do to help with this?
I have updated the status page except for the following references
which needs to be moved first:
http://incubator.apache.org/ki/
http://cwiki.apache.org/confluence/display
Hi Alan,
Is there anything I can do to help with this?
- Les
On Thu, Oct 15, 2009 at 12:52 PM, Alan D. Cabrera l...@toolazydogs.com wrote:
I'm on it.
Regards,
Alan
On Oct 13, 2009, at 9:41 PM, Niclas Hedhman wrote:
I am calling upon the Mentors (Alan, Paul, Emmanuel, Craig) of Shiro
Thanks so much Niclas! I really appreciate it.
And yes, please write-disable the old Jira Ki project.
- Les
On Fri, Jul 3, 2009 at 12:35 AM, Niclas Hedhman nic...@hedhman.org wrote:
Hi,
I have created the JIRA project, its components and versions, and I
have moved all KI issues to SHIRO.
...@anjinllc.com [mailto:les.hazlew...@anjinllc.com] On
Behalf Of Les Hazlewood
Sent: Friday, 3 July 2009 6:37 AM
To: general@incubator.apache.org
Subject: Re: Ki or Shiro?
The final name moving forward is Apache Shiro. We just haven't been able
to
transfer the site over as the Confluence
The final name moving forward is Apache Shiro. We just haven't been able to
transfer the site over as the Confluence Shiro space hasn't been set up
yet. That hopefully will be done soon - I'll ping infra now to see if they
can escalate this. Thanks for the reminder ;)
Here's the Jira link for
Hi all,
The Incubator Ki to Shiro project name change was voted upon and passed
about 3 weeks ago. However, we've been having a a bit of a struggle
finishing infrastructural-related migration associated with the name change.
Could someone please shed some light on the following two issues?
The voting period has ended. I will post the result in a new thread.
Regards,
Les
On Tue, Jun 9, 2009 at 4:46 PM, vasusanka vasusa...@gmail.com wrote:
+1 Apache Shiro
Cheers,
Vasu.
Daniel J. Lauk wrote:
+1 Apache Aseca
Cheers,
DJ
--
View this message in context:
name suggestions to intermediate votes to final vote
- the entire process was driven and concluded by the entire Apache
community. Thanks to everyone for your help.
Best,
Les Hazlewood
Apache Shiro project member
+1 Apache Aseca
I had delayed my vote for a really long time because I honestly like both
about equally. But if I had to choose, I figured that a more obscure name
might be better, so I went with Aseca.
On Sun, Jun 7, 2009 at 9:26 PM, Brian Fox bri...@infinity.nu wrote:
+1 Apache Shira
On
Hi All,
This is the final vote for the Apache JSecurity/Ki project's new name
between the two proposed finalists. Please vote for only one of the
following two (alphabetically-ordered) names:
Apache Aseca - relevant letters in Application SECurity Api
Apache Shiro - castle in Japanese
suggested KeyPad, I meant to call it Apache KiPad, just a thought:-)
2009/6/3 Sune Lindberg Riedel sune.rie...@axiell.com
+1 for Apache Security (because that’s what it is!)
/Sune
From: les.hazlew...@anjinllc.com [mailto:les.hazlew...@anjinllc.com] On
Behalf Of Les Hazlewood
Sent: Friday
Hi everyone,
The period for name suggestions has ended, and we received many good
submissions. Thanks so much for all who submitted - naming is not an easy
task given the research that has to be done, and your efforts are much
appreciated.
Below is a list of all submissions that cleared TESS
...@googlemail.comwrote:
Hi,
I like the sound of Toran, it feels serene, yet being powerful.
Neil
2009/5/29 Les Hazlewood lhazlew...@apache.org
Hi everyone,
The period for name suggestions has ended, and we received many good
submissions.? Thanks so much for all who submitted - naming
back
to incubator general.
Ralph
On May 29, 2009, at 7:29 AM, Les Hazlewood wrote:
Hi everyone,
The period for name suggestions has ended, and we received many good
submissions. Thanks so much for all who submitted - naming is not an easy
task given the research that has to be done
It (Boahn:보안) means a 'security' in Korean, and a druid name in WarCraft.
;)
On Wed, May 20, 2009 at 1:01 AM, Les Hazlewood lhazlew...@apache.org
wrote:
Hi Apache Community.
It seems as if our recently changed name of Apache Ki is not free from
potential naming conflict problems, and we'll need
or Patents by performing a search [1]. Also
if you can get little or no results in Google and Yahoo, that would be a
great candidate too.
Name submission starts NOW.
We look forward to all name suggestions, and we appreciate anyone who wishes
to participate!
Thanks so much,
Les Hazlewood
Apache
Thanks!
On Tue, May 19, 2009 at 12:21 PM, sebb seb...@gmail.com wrote:
PANEKANA - apparently means security in Hawaiian.
No hits in TESS.
Google shows no hits relating to commercial enterprises.
On 19/05/2009, Les Hazlewood lhazlew...@apache.org wrote:
Hi Apache Community.
It seems
On Tue, May 12, 2009 at 2:22 PM, Alan D. Cabrera l...@toolazydogs.comwrote:
On Tue, May 12, 2009 at 5:14 PM, Alan D. Cabrera l...@toolazydogs.com
wrote:
...I'd like someone to come up with a concise argument that would allow
me to
let this go other than nope, it's not the same. Otherwise,
On Tue, May 12, 2009 at 3:55 PM, Bernd Fondermann
bernd.fonderm...@googlemail.com wrote:
What I don't get is why would anyone want to keep the name if there
are potential overlaps or troubles ahead?
I mean, there are probably better (coding) and harder (releasing,
graduating) things to do
Forwarding to the Incubator
-- Forwarded message --
From: Les Hazlewood lhazlew...@apache.org
Date: Fri, Mar 6, 2009 at 2:10 PM
Subject: [ANNOUNCE] JSecurity Name Changed to Ki
To: JSecurity User List jsecurity-u...@incubator.apache.org
Cc: JSecurity Developer List jsecurity
On Mon, Jan 12, 2009 at 11:40 AM, Noel J. Bergman n...@devtech.com wrote:
JSecurity: I really don't need to go follow URLs into SVN (or tracking down
e-mails as with some others) when assembling the report. Please follow the
practice of putting your report in the Wiki.
I'm happy to put it in
On Mon, Jan 12, 2009 at 12:25 PM, Emmanuel Lecharny elecha...@gmail.com wrote:
What is policy? I'm just trying to learn - thanks for any guidance!
Just as I said : write down the report (either as a simple mail, or in SVN),
and when validated by the team, then push the content to the wiki
Beautimous. That's my preference :)
On Mon, Jan 12, 2009 at 12:40 PM, Emmanuel Lecharny elecha...@gmail.com wrote:
Les Hazlewood wrote:
On Mon, Jan 12, 2009 at 12:25 PM, Emmanuel Lecharny elecha...@gmail.com
wrote:
What is policy? I'm just trying to learn - thanks for any guidance
own use cases as well as user
community feedback.
I hope that answers your question, this was a fairly high level answer, if
you'd like I can go over any of those features/differences in more detail
and point you at any code.
-Mikeal
On Aug 14, 2008, at August 14, 20081:40 PM, Les
Just out of curiosity, where does this fit in versus, say, Selenium, MaxQ,
Canoo WebTest, and others?
There's nothing wrong if Windmill does the same stuff - I'm just curious
what it can do in comparison.
Cheers,
Les
On Thu, Aug 14, 2008 at 4:32 PM, Mikeal Rogers [EMAIL PROTECTED]wrote:
This
+1 to Scott's comments.
I don't think the name is a significant conflict at all. Debian Etch is a
release codename - regular references to it will fade away as the next
release surfaces, and the Apache Etch name, if it is a successful project,
should last much longer. This would supplant
Where I think that there is a problem is when they ditch their old
infrastructure and exclusively use ASF's infrastructure to build, maintain,
and release non-ASF releases. To be sure in the case of JSecurity the final
artifacts will not use the ASF mirrors but that does not hide the fact
Let's turn this around and look at it from a different light. What's
stopping us from doing a 0.9.0 release in the incubator? I'm guessing that
you need the packages to be the same?
Yes, that is one of the biggest reasons I can see at the moment.
Probably more of a driving force though is
On Sat, Jul 26, 2008 at 5:47 AM, Martijn Dashorst
[EMAIL PROTECTED] wrote:
On Sat, Jul 26, 2008 at 10:20 AM, Bertrand Delacretaz
[EMAIL PROTECTED] wrote:
Can you provide one example? Just curious
While it was incubating, Wicket did a few non-ASF releases on their
old project site,
This brings up a follow-up question - when Wicket graduated to a TLP, were
you able to retain the history while working in the Incubator when you moved
to an SVN repo of your own?
On Sat, Jul 26, 2008 at 11:22 AM, Les Hazlewood [EMAIL PROTECTED] wrote:
On Sat, Jul 26, 2008 at 5:47 AM, Martijn
Really?
So if I make a commit for my project, and that is revision N, then if
someone immediately makes a commit for a totally different project, that
would be N+1?
I thought only the Incubator worked like that. Seems really bizzare to me
as an ASF newbie
On Sat, Jul 26, 2008 at 12:12 PM,
Cool, thanks very much!
On Fri, Jul 25, 2008 at 2:04 AM, Alan D. Cabrera [EMAIL PROTECTED]
wrote:
All set.
Regards,
Alan
On Jul 24, 2008, at 11:35 AM, Les Hazlewood wrote:
Alan, has this been resolved for JSecurity?
I visit http://incubator.apache.org/projects/jsecurity.html and I
Alan, has this been resolved for JSecurity?
I visit http://incubator.apache.org/projects/jsecurity.html and I get a 404
Also, JSecurity is not listed on incubator.apache.org on the right hand
side...
I don't know how this is supposed to work, so I'm hoping those more
knowledgeable than me will
I've used this framework in a production application already, and I
absolutely love it.
+1 (non binding)
On Mon, Jul 14, 2008 at 7:14 AM, Henning Schmiedehausen [EMAIL PROTECTED]
wrote:
This vote will run until Monday, July 21st, 2008.
[ ] +1 Accept Click for incubation
[ ] 0 Don't care
[
I'll just append that I, and I'm sure the huge majority of people in
the world that use Maven, would find it incredibly irritating if
incubator releases were not automatically available in the central
repository.
So a huge +1 to enable this.
On Thu, Jun 26, 2008 at 9:23 AM, Les Hazlewood [EMAIL
:23 PM, Les Hazlewood [EMAIL PROTECTED] wrote:
JSecurity also meets condition b)
Our users will scream bloody murder if they can no longer access
JSecurity from the central repository. So we'll continue to publish
there, even if it means publishing under the old org.jsecurity group
id
I don't know the exact usage, but I'm sure it is in lower thousands -
many people use our .jars directly, but probably many more use it via
3rd party plugins (Grails plugin, etc) that is built on top of
JSecurity.
It sounds as if waiting at the last possible second to move from
org.jsecurity.* to
Thanks to IntelliJ Idea, which updates our Spring and Hibernate files
automatically during refactoring already, even this isn't an issue for
us (thankfully). We should be good!
On Thu, Jun 26, 2008 at 11:49 AM, Emmanuel Lecharny
[EMAIL PROTECTED] wrote:
Les Hazlewood wrote:
I don't know
the incubator who already
publish to the main repo would probably retain their source code
packaging namespaces until the project graduates.
Is that acceptable?
On Thu, Jun 26, 2008 at 12:02 PM, Les Hazlewood [EMAIL PROTECTED] wrote:
Thanks to IntelliJ Idea, which updates our Spring and Hibernate
we'll use it as an opportunity to refactor some of the APIs in order to avoid
a double breakage in concurrent versions.
We have some minor refactoring to do as well and we've decided to do
the same thing - if there's going to be an inconvenience, you might as
well bundle it all at once (if you
Full JAAS integration is desired for the 1.0 final release to support
those who actually implement containers. JSecurity is usable in all
containers today, both web and non-web today, just not via JAAS yet.
The reason it is not in place now and hasn't been in 3 years is that
because the vast
Just a clarification:
JSecurity can be used in any environment - web or not, container or
not. The reason why the Filter approach is best known is that it is
the easiest to set up - Filters allow an 'interceptor' mechanism that
is common to any web container. When not using a Filter, you must
Of course we could do that, and we may have to in order to appease our
community. But we'd prefer not to for simplicity's sake.
On Mon, Jun 2, 2008 at 4:25 AM, Gilles Scokart [EMAIL PROTECTED] wrote:
2008/5/30 Jeremy Haile [EMAIL PROTECTED]:
Currently JSecurity has a community, is published
That's just the thing though:
At the end of the day, the vast majority of TLP end users could care less if
the TLP uses an incubator dependency or not, as long as it is Apache 2.0
compatible and easily available (i.e. in the central repo). They trust the
TLP to do their due diligence to ensure
Sure, that sounds good to me. I'll update the proposal...
On Mon, Jun 2, 2008 at 12:01 PM, Craig L Russell [EMAIL PROTECTED]
wrote:
One more nit comment on the proposal.
The mailing lists proposed are prefixed with jsec, but the project name and
mailing lists on codehaus.org are jsecurity.
[EMAIL PROTECTED]
wrote:
Les Hazlewood wrote:
Sure, that sounds good to me. I'll update the proposal...
Then maybe JSECURITY for Jira too might be good. Not sure... Depends if we
will have many sub-projects, which might be a good idea, regarding the
various funtionalities.
wdyt
Hi Craig,
We're definitely happy to have you as a mentor. Thanks for joining in!
Have you joined the developer list? I have at least one question to ask you
thus far, but I don't want to hijack this thread.
Thanks!
Les
On Sun, Jun 1, 2008 at 2:52 PM, Craig L Russell [EMAIL PROTECTED]
wrote:
The other thing about JSecurity's enterprise session support is that
it in many cases serves as a native basic Single Sign-On solution.
For example, the most common scenario that typically occurs is the
following (there are several current production environments that work
like this):
A session
at 9:55 AM, Les Hazlewood [EMAIL PROTECTED] wrote:
The other thing about JSecurity's enterprise session support is that
it in many cases serves as a native basic Single Sign-On solution.
For example, the most common scenario that typically occurs is the
following (there are several current
Noel,
Could you please help me understand the fundamental reasons why this
is important to the IPMC?
I mean, I as an end-user could care less about if the dependency
artifact is in incubation or not - as long as it solves the problems
in the way the development team deems necessary, all I want
saying that the
ASF endorses the software. Since it has not graduated from the
incubator, the ASF doesn't yet endorse it. This is the way I see it
at least.
On Fri, May 30, 2008 at 11:06 AM, Les Hazlewood [EMAIL PROTECTED] wrote:
Noel,
Could you please help me understand the fundamental
Hrm - I thought you had to have IP clearance before you even were
accepted as a podling. Or maybe its just that Alan is such a great
Champion for us, that he helped us along that path before we even
submitted our proposal ;)
Under this assumption (that IP clearance exists already), it makes
much
, May 30, 2008 at 11:43 AM, Les Hazlewood [EMAIL PROTECTED] wrote:
Hrm - I thought you had to have IP clearance before you even were
accepted as a podling. Or maybe its just that Alan is such a great
Champion for us, that he helped us along that path before we even
submitted our proposal
clearly documented and the CYA notion is covered.
On Fri, May 30, 2008 at 1:24 PM, sebb [EMAIL PROTECTED] wrote:
On 30/05/2008, Les Hazlewood [EMAIL PROTECTED] wrote:
My proposed solution:
1. A podling could not issue a release until after IP issues have
been cleared by the IPMC.
2. Once
Why is this necessary?
As an end user, I would _hate_ to have to change all of my code to
reference a totally new package structure after the podling graduates.
That's a major pain...
On Fri, May 30, 2008 at 4:49 PM, Brian E. Fox [EMAIL PROTECTED] wrote:
My proposed solution:
1. A podling
that the releases that are
approved are of decent enough quality to be available to the public at
large.
So, I would vote -1 in regards to creating a separate incubator Maven
repository.
Regards,
Les Hazlewood
On Thu, May 29, 2008 at 2:51 AM, Jukka Zitting [EMAIL PROTECTED] wrote:
Hi,
I'm
as a mentor. I've mentored a few times and
have some vested interest in security through Apache Directory (esp.
Triplesec).
Regards,
Alex
On Thu, May 8, 2008 at 1:15 PM, Les Hazlewood [EMAIL PROTECTED] wrote:
Thanks Paul! We're very happy to have your input. If you don't mind
] wrote:
Les Hazlewood wrote:
Hi Alex,
Sounds great. The JSecurity team has had an identity management
server in our heads for quite a while. Indeed much of the current
framework reflects flexibility that was designed into it with the
intention of making an identity server an easier
here before we
embark on incubation.
Regards,
Alan
On May 7, 2008, at 11:55 AM, Les Hazlewood wrote:
Hello all,
I've been a lurker for a while, attempting to get an overall feel for
the incubator process, and this is my first foray into (hopefully)
making things a reality
Fremantle [EMAIL PROTECTED] wrote:
I also volunteer to mentor this project.
Paul
On Thu, May 8, 2008 at 5:38 PM, Les Hazlewood [EMAIL PROTECTED] wrote:
Alan, this is fantastic news!
Thanks so much for offering your time and experience. We're really
looking forward to your input
Here's my response for those interested...
Hi Siegfried,
Please see my inline comments...
1) would it be possible to integrate non-Java application for SSO, e.g.
using agents communicating to a central server or is this not the scope of
the project (i.e. Java only) - might be a stupid
support - forums, mailing lists, jira:
http://www.jsecurity.org/support
JSecurity is Apache 2.0 licensed.
Thank you for any feedback and recommendations. We look forward to
your responses.
Best regards,
Les Hazlewood
JSecurity lead project founder
difficult to understand. I like how simple the JSecurity API
is. I'd be interested in seeing this become a podling. I don't know
if I'm qualified enough to be a champion for the project, though.
On Wed, May 7, 2008 at 2:55 PM, Les Hazlewood [EMAIL PROTECTED] wrote:
Hello all
... :-)
Cheers,
Siegfried Goeschl
Les Hazlewood wrote:
Hello all,
I've been a lurker for a while, attempting to get an overall feel for
the incubator process, and this is my first foray into (hopefully)
making things a reality for our project, JSecurity.
JSecurity (http://www.jsecurity.org
On Wed, May 7, 2008 at 8:33 PM, Angela Cymbalak [EMAIL PROTECTED]
wrote:
I'm concerned about the starting point from which to grow.
Apache committers have the Labs to get started and attract
a few interested people before coming to the Incubator.
A non-committer coming to the
85 matches
Mail list logo
