Hi,
I've been using odl-parent 1.6.0-Beryllium, yangtools (& yang-maven-plugin)
0.8.0-Beryllium, yang-jmx-generator-plugin 0.4.0-Beryllium and
maven-sal-api-gen-plugin 0.7.0-Lithium.
Now I've also tried with odl-parent 1.7.1-Boron-SR1,
yangtools 1.0.1-Boron-SR1, yang-jmx-generator-plugin 0.5.1-Boron-SR1 and
maven-sal-api-gen-plugin 0.7.4-Lithium-SR4, though I get the same kind of
results.
Is there any other way for me to inspect what could be causing this?
Thank you.
Best regards,
Ricardo Santos
On 11 November 2016 at 19:46, Robert Varga <n...@hq.sk> wrote:
> On 11/11/2016 06:27 PM, Ricardo Santos wrote:
> > Hi,
> >
> > (Apologies if this is not the correct list for this question)
> >
> > Today when I was compiling my project after cleaning previously
> > generated source files, I noticed that the code generator plugin was not
> > working properly when generating the sources from my module yang model.
> >
> > For example, the following line is generated:
> > public static final QName QNAME =
> > (urn:opendaylight:params:xml:ns:yang:controller:config:
> main-impl?revision=2016-03-01)main-impl;
> >
> > Instead of something like this (don't mind the namespaces, they're from
> > different projects):
> > public static final QName QNAME =
> > org.opendaylight.yangtools.yang.common.QName.cachedReference(org.
> opendaylight.yangtools.yang.common.QName.create("urn:
> opendaylight:pathcalculator:main-impl","2014-05-28","main-impl"));
> >
> > This obviously makes the maven compiler plugin not so happy, when
> > following the build process.
>
> Hello,
>
> current master works just fine for me and this smells of a templating
> problem -- instead of encapsulating the QName it gets .toString()ed.
>
> What is your toolchain version?
>
> Thanks,
> Robert
>
>
_______________________________________________
controller-dev mailing list
controller-dev@lists.opendaylight.org
https://lists.opendaylight.org/mailman/listinfo/controller-dev
