The short answer is that 1.2.0.Final is good to go: We haven't released because
we're updating the docs (well spotted!).
The longer answer is that Eric did some refactoring to change 'Service' =>
'API' and 'Application' => 'Client App'. This changes various
URIs, object names, etc, around apiman, which is likely to require some refactoring in
your scripts.
Regards,
Marc
On 11/01/2016 16:23, Paul Blair wrote:
Currently using 1.1.9.Final.
On 1/11/16, 11:19 AM, "Marc Savy" <marc.savy(a)redhat.com> wrote:
> Are you currently using 1.1.x or some other 1.2.x tag?
>
> On 11/01/2016 16:03, Paul Blair wrote:
>> I'm noticing in Github there is a 1.2.0.Final tag based on commit a
>> commit with message "Prepared apiman for release: 1.2.0.Final". Is
the
>> release good to go if I build it from source?
>>
>> (I'm getting an exception when publishing an API but unfortunately it's
>> not giving me interesting information because of a NullPointerException
>> in the GatewayClient's exception handler for PublishingException. I
>> noticed that this exception handler is fixed in the 1.2 stream, so I'm
>> eager to grab that release.)
>>
>>
>> _______________________________________________
>> Apiman-user mailing list
>> Apiman-user(a)lists.jboss.org
>>
https://lists.jboss.org/mailman/listinfo/apiman-user
>>
>