I tend to monitor dev lists from other projects and the traffic goes right in my Inbox. Once I see commit messages on a list, the mail filter goes in and all dev traffic goes to a folder. Not sure if I'm unique in this respect, but I guess I would cast my vote for sending commit messages to forge-commits and not forge-dev.
On Jul 24, 2012, at 7:21 PM, Lincoln Baxter, III wrote:
Trying this out. We'll see if it gets too annoying. Feedback welcome! let me know if you like it or hate it.
~Lincoln
On Tue, Jul 24, 2012 at 7:17 PM,
<Lincoln.Baxter@lists.jboss.org> wrote:
Branch: refs/heads/master
Home: https://github.com/forge/core
Commit: 28facae30d4113862eb3c55f82c00c73680afc53
https://github.com/forge/core/commit/28facae30d4113862eb3c55f82c00c73680afc53
Author: Ivan Ivanov <ivan.ivanov@sap.com>
Date: 2012-07-23 (Mon, 23 Jul 2012)
Changed paths:
M parser-java-api/src/main/java/org/jboss/forge/parser/java/Visibility.java
Log Message:
-----------
Fixed a bug in setting scope to new methods
When you add a method to a forge-generated class, you may specify this method's scope (private, default, protected, public). Whenever you specify a scope different than public, an exception used to be thrown.
Commit: b0acceac790c4c4f854a11627cf5a5b4c6c9bedf
https://github.com/forge/core/commit/b0acceac790c4c4f854a11627cf5a5b4c6c9bedf
Author: Ivan Ivanov <ivan.ivanov@sap.com>
Date: 2012-07-23 (Mon, 23 Jul 2012)
Changed paths:
M parser-java/src/test/java/org/jboss/forge/test/parser/java/MethodSignatureTest.java
Log Message:
-----------
A test case for the visibility fix
Commit: ee1675943df124702f684a7f95ca23877e150116
https://github.com/forge/core/commit/ee1675943df124702f684a7f95ca23877e150116
Author: Lincoln Baxter, III <lincolnbaxter@gmail.com>
Date: 2012-07-23 (Mon, 23 Jul 2012)
Changed paths:
M parser-java-api/src/main/java/org/jboss/forge/parser/java/Visibility.java
M parser-java/src/test/java/org/jboss/forge/test/parser/java/MethodSignatureTest.java
Log Message:
-----------
Merge pull request #176 from ivannov/master
Fixed a bug in setting scope to new methods
Compare: https://github.com/forge/core/compare/8b9fa056f00a...ee1675943df1
_______________________________________________
forge-dev mailing list
forge-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev
--
Lincoln Baxter, III
http://ocpsoft.org
"Simpler is better."
_______________________________________________
forge-dev mailing list
forge-dev@lists.jboss.org
https://lists.jboss.org/mailman/listinfo/forge-dev