shiro-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From lhazlew...@apache.org
Subject svn commit: r733555 - /incubator/jsecurity/board/2009-01.txt
Date Mon, 12 Jan 2009 00:44:00 GMT
Author: lhazlewood
Date: Sun Jan 11 16:43:59 2009
New Revision: 733555

URL: http://svn.apache.org/viewvc?rev=733555&view=rev
Log:
modifed report per mailing list suggestions - # of mentor votes and 2 build systems

Modified:
    incubator/jsecurity/board/2009-01.txt

Modified: incubator/jsecurity/board/2009-01.txt
URL: http://svn.apache.org/viewvc/incubator/jsecurity/board/2009-01.txt?rev=733555&r1=733554&r2=733555&view=diff
==============================================================================
--- incubator/jsecurity/board/2009-01.txt (original)
+++ incubator/jsecurity/board/2009-01.txt Sun Jan 11 16:43:59 2009
@@ -13,11 +13,11 @@
 
 After the November final release, there has been lengthy discussion
 for the month and half following about JSecurity's name and whether
-or not it should be changed to something else.  3 of the 5 project
-mentors for the project voted in favor of changing the name from
-JSecurity to something else, citing concerns of a few external
-(3rd party) products that might cause a name conflict.  Concensus
-was not reached, resulting in the vote.  However, it is considered
+or not it should be changed to something else.  3 mentors voted in favor
+of chainging the name to something else, 1 voted against, and 1 abstained.
+Those voting in favor cited concerns of a few external
+(3rd party) products that might cause a name conflict.  Concensus was
+not reached, resulting in the vote.  However, it is considered
 still an open issue with continued discussion as other IPMC members
 are contributing to the discussion.
 
@@ -26,7 +26,9 @@
 delineate the differnece of jsecurity core versus web support and
 3rd party support.  The team came to concensus about an initial
 directory organization and the ant build files were modified to
-reflect the new structure.
+reflect the new structure.  It was also discussed that two build
+systems, both Ant+Ivy and Maven, could be used to build the framework,
+allowing the one building to choose based on their preference.
 
 Infrastructure migration (noted in our STATUS file) is almost
 complete - all that needs to be done is migration of the jsecurity.org



Mime
View raw message