[jbossseam-issues] [JBoss JIRA] Created: (JBSEAM-2271) Changes to the security event names totally broke loging redirection in examples and seam-gen, and docs were not updated
1:22 p.m.
Changes to the security event names totally broke loging redirection in examples and
seam-gen, and docs were not updated
------------------------------------------------------------------------------------------------------------------------
Key: JBSEAM-2271
URL: http://jira.jboss.com/jira/browse/JBSEAM-2271
Project: JBoss Seam
Issue Type: Bug
Components: Security
Reporter: Gavin King
Priority: Blocker
Why are we breaking pubished APIs in a point release? Why are we changing public APIs
without testing? Very unprofessional!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:26 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2271) Changes to the security event names totally broke login redirection in examples and seam-gen, and docs were not updated
[ http://jira.jboss.com/jira/browse/JBSEAM-2271?page=all ]
Gavin King updated JBSEAM-2271:
-------------------------------
Summary: Changes to the security event names totally broke login redirection in
examples and seam-gen, and docs were not updated (was: Changes to the security event
names totally broke loging redirection in examples and seam-gen, and docs were not
updated)
Changes to the security event names totally broke login redirection
in examples and seam-gen, and docs were not updated
-----------------------------------------------------------------------------------------------------------------------
Key: JBSEAM-2271
URL: http://jira.jboss.com/jira/browse/JBSEAM-2271
Project: JBoss Seam
Issue Type: Bug
Components: Security
Reporter: Gavin King
Priority: Blocker
Why are we breaking published APIs in a point release? Why are we changing published APIs
without testing? Why is it OK to change published APIs and not update the documentation?
Very unprofessional!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
1:26 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2271) Changes to the security event names totally broke loging redirection in examples and seam-gen, and docs were not updated
[ http://jira.jboss.com/jira/browse/JBSEAM-2271?page=all ]
Gavin King updated JBSEAM-2271:
-------------------------------
Description: Why are we breaking published APIs in a point release? Why are we
changing published APIs without testing? Why is it OK to change published APIs and not
update the documentation? Very unprofessional! (was: Why are we breaking pubished APIs in
a point release? Why are we changing public APIs without testing? Very unprofessional!)
Changes to the security event names totally broke loging redirection
in examples and seam-gen, and docs were not updated
------------------------------------------------------------------------------------------------------------------------
Key: JBSEAM-2271
URL: http://jira.jboss.com/jira/browse/JBSEAM-2271
Project: JBoss Seam
Issue Type: Bug
Components: Security
Reporter: Gavin King
Priority: Blocker
Why are we breaking published APIs in a point release? Why are we changing published APIs
without testing? Why is it OK to change published APIs and not update the documentation?
Very unprofessional!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
5:45 a.m.
New subject: [jbossseam-issues] [JBoss JIRA] Updated: (JBSEAM-2271) Remove deprecated events from Identity
[ http://jira.jboss.com/jira/browse/JBSEAM-2271?page=all ]
Shane Bryzak updated JBSEAM-2271:
---------------------------------
Summary: Remove deprecated events from Identity (was: Changes to the security
event names totally broke login redirection in examples and seam-gen, and docs were not
updated)
Fix Version/s: 2.1.0.GA
Assignee: Shane Bryzak
The previous event keys have been re-added to Identity (so both the old and new events are
called now) - we should remove the old events for the next major release of Seam.
Remove deprecated events from Identity
--------------------------------------
Key: JBSEAM-2271
URL: http://jira.jboss.com/jira/browse/JBSEAM-2271
Project: JBoss Seam
Issue Type: Bug
Components: Security
Reporter: Gavin King
Assigned To: Shane Bryzak
Priority: Blocker
Fix For: 2.1.0.GA
Why are we breaking published APIs in a point release? Why are we changing published APIs
without testing? Why is it OK to change published APIs and not update the documentation?
Very unprofessional!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
10:45 p.m.
New subject: [jbossseam-issues] [JBoss JIRA] Closed: (JBSEAM-2271) Remove deprecated events from Identity
[ http://jira.jboss.com/jira/browse/JBSEAM-2271?page=all ]
Shane Bryzak closed JBSEAM-2271.
--------------------------------
Resolution: Done
Deprecated events removed.
Remove deprecated events from Identity
--------------------------------------
Key: JBSEAM-2271
URL: http://jira.jboss.com/jira/browse/JBSEAM-2271
Project: JBoss Seam
Issue Type: Bug
Components: Security
Reporter: Gavin King
Assigned To: Shane Bryzak
Priority: Blocker
Fix For: 2.1.0.GA
Why are we breaking published APIs in a point release? Why are we changing published APIs
without testing? Why is it OK to change published APIs and not update the documentation?
Very unprofessional!
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://jira.jboss.com/jira/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
6172
days inactive
6245
days old
4 comments
2 participants
participants (2)
-
Gavin King (JIRA) -
Shane Bryzak (JIRA)