3/4/2013 5:09:31 PM
shouldn't return null.
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
3/2/2013 11:49:43 PM
introduced a regression as
payment methods were tied to plugins, not instances.
I'm not sure though if using the OSGI service name in the long run is
the way to go. Could we instead auto-discover at runtime which plugin
is supposed to handle a given payment method?
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
3/2/2013 9:59:07 PM
Pierre-Alexandre Meyer <pierre@ning.com>
|
3/1/2013 11:19:09 PM
is generic enough to have it in the PaymentPluginApi.
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
3/1/2013 9:31:59 PM
match the value passed in the
addPaymentMethod call. Tests broke after 00dc2dbadd8ec3e2cdd524b9e683f955dac67a8f.
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
3/1/2013 9:00:38 PM
may not have a default payment method yet.
Signed-off-by: Pierre-Alexandre Meyer <pierre@ning.com>
|
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>
|
