3/1/2013 8:45:21 PM
build
It looks like the builds are failing now because the logs are getting
too big:
The command "mvn clean install -Ptravis" exited with 0.
The log length has exceeded the limit of 4 Megabytes (this usually means
that test suite is raising the same exception over and over).
The build has been terminated.
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
3/1/2013 8:35:22 PM
is not installed by default.
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
3/1/2013 8:34:31 PM
plugin name is specified, the default one will be used. Make sure we store its
name, not NULL.
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
3/1/2013 8:12:33 PM
body for accountId since it's in the URL.
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
3/1/2013 8:11:24 PM
argument of the addPaymentMethod call.
Since the payment method is not yet created when Killbill calls the
plugin, it's the only way the plugin can tie it back to an account.
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
3/1/2013 7:27:36 PM
Pierre-Alexandre Meyer <pierre@ning.com>
|
3/1/2013 7:27:05 PM
fields, set sane defaults.
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
3/1/2013 7:06:07 PM
potential NPE - AccountData doesn't return any primitive.
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
3/1/2013 6:37:24 PM
relying on third-party libraries using slf4j (e.g.
config-magic), there needs to be a slf4j implementation that bridges
with LogServices. Otherwise, slf4j will default to a no-op
implementation (resulting in the loss of messages).
This new library is designed to bridge that gap. To use it, simply add
it to your OSGI bundle and call: StaticLoggerBinder.getSingleton().setLogService(logService);
in the start method of your activator (logService is the
OSGIKillbillLogService provided by KillbillActivatorBase).
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
3/1/2013 5:00:02 PM
parameter wasn't used. This may fix the compilation with javac 1.6.0_24.
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
