Thanks, the improvement fix just just made it into 3.1.10,
http://git-wip-us.apache.org/repos/asf/cxf/commit/10fd399c
as far as the DefaultSwaggerSerializers is concerned, a
'javadocProvider' property referring to
org.apache.cxf.jaxrs.model.doc.JavaDocProvider bean has to be used
Cheers, Ser
Hi,
cleaned up (no more runtime weaving)
+ tomcat7-maven-plugin (integration test)
2017-01-27 14:27 GMT+04:00 Sergey Beryozkin :
> Thanks for preparing it,
>
> Can you please add a Jetty or Tomcat plugin which can be used to run the
> demo ? I was hoping to do a quick try this morning, I've trie
Thanks for preparing it,
Can you please add a Jetty or Tomcat plugin which can be used to run the
demo ? I was hoping to do a quick try this morning, I've tried Jetty9,
older Jetty Maven plugins, dropped it into a standalone Tomcat 8, the
demo fails to start for various reasons (no runt time w
This is example project
https://github.com/slavb18/testjavadoc
2017-01-24 16:28 GMT+04:00 Sergey Beryozkin :
> Sure, I see what you mean, I did not think of it at a time.
> If you could set up a Maven test project where a javadocs jar is on the
> classpath then it will be easier for me to priorit
Sure, I see what you mean, I did not think of it at a time.
If you could set up a Maven test project where a javadocs jar is on the
classpath then it will be easier for me to prioritize and experiment
with the parser code, otherwise a creating a dedicated CXF test module
will take time.
Cheer
No, I am talking about different (may be found impossible by author)
realisation of javadoc parsing
Since it is regular jar, and packaged as dependency, its contents accesible
as regular classpath resource.
Point.class.getResource("Point.html") - e.g. this is working, can get
javadoc of class
20
Hi
Freeman did it for a java2wadl, where JavaDocs info gets collected
during the build time, but at the runtime JavaDocs are only visible from
the dedicated jar.
I do not know how would one load a javadocs jar without knowing the full
Jar name, perhaps it can be done based on some convention..
Hi!
I have configured javadoc using this config:
But this jar is regular war dependency lib, is there possibility to
configure javadoc using regular classpath, not referencing actual jar
version?
2017-01-17 17:08 GMT+04:00 Francesco Chicchiriccò :
>
> The Defau
Thanks!
2017-01-17 17:08 GMT+04:00 Francesco Chicchiriccò :
> On 17-jan-17, at 13:44, Vjacheslav V. Borisov slav...@gmail.com wrote:
>
> > Hi!
> >
> > Playing with
> > https://github.com/apache/cxf/tree/master/distribution/src/
> main/release/samples/jax_rs/spring_boot
> >
> > Added Javadoc to
On 17-jan-17, at 13:44, Vjacheslav V. Borisov slav...@gmail.com wrote:
> Hi!
>
> Playing with
> https://github.com/apache/cxf/tree/master/distribution/src/main/release/samples/jax_rs/spring_boot
>
> Added Javadoc to method sayHello
>
>/**
> * sayHello doc
> * @param a the a param
>
Hi!
Playing with
https://github.com/apache/cxf/tree/master/distribution/src/main/release/samples/jax_rs/spring_boot
Added Javadoc to method sayHello
/**
* sayHello doc
* @param a the a param
* @return
*/
public String sayHello(String a) {
return "Hello2 " + a
11 matches
Mail list logo
