[
https://jira.jboss.org/jira/browse/WELDSE-1?page=com.atlassian.jira.plugi...
]
Ceki Gulcu commented on WELDSE-1:
---------------------------------
As of SLF4J version 1.6.0, if no binding is found on the class path, then slf4j-api will
default to a no-operation implementation discarding all log requests. Thus, instead of
throwing an exception, SLF4J will emit a single warning message about the absence of a
binding and proceed to discard all log requests without further protest. If Weld's
distribution includes slf4j-api.jar but no binding, then even in the absence of any SLF4J
binding on the class path, Weld's distribution will still work out-of-the-box, and
without requiring the end-user to download a binding from SLF4J's web-site. Only when
the end-user wishes to enable logging will she need to install a binding.
Add org.jboss.weld.environment.se.StartMain as the Main-Class
-------------------------------------------------------------
Key: WELDSE-1
URL:
https://jira.jboss.org/jira/browse/WELDSE-1
Project: Weld support for Java SE
Issue Type: Feature Request
Reporter: George Gastaldi
Attachments: WELDSE-1.patch
Add Main-Class in MANIFEST.MF of JavaSE Extension of WELD, so may be invoked using
java -cp myapp.jar -jar weld-se.jar arguments
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
https://jira.jboss.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira