On Jun 2, 2014, at 9:16 PM, Will Stevens wrote:
> I started playing with the 'javasphinx' project to see if it would work for
> generating the API docs.
>
> So here is the basic idea of what it produces.
>
> I created docs for the following cloudstack directory:
> 'api/src/org/apache/cloudst
I started playing with the 'javasphinx' project to see if it would work for
generating the API docs.
So here is the basic idea of what it produces.
I created docs for the following cloudstack directory:
'api/src/org/apache/cloudstack/api/'
I then took the RST files and generated the html docs fr
Hi Will,
I don't know why it was not updated, one reason, I'm anticipating, could be
that we moved to Spring for many things which uses bunch of xmls for some
configuration, any not this properties file anymore?
Probably Alex or Kelven could comment if this is the case. I think you can
add the cl
I have completely started from scratch with a new clone of the CloudStack
repo.
Master is now pointing to 4.5, so I checked out the 4.4 branch.
I put all the deps in place as well as the vhd-util file.
I completely removed my ~/.m2 directory so I am starting from completely
clean.
I checked the
On 05/30/2014 10:40 PM, Will Stevens wrote:
Thanks Rohit, I will do all those steps.
I know the git branch is correct, but I will do a clean anyway.
Removing the maven repositories is a good idea.
NB; for this issue, e.g., fear of old cloudstack stuff being used rather
then newly built bits,
Thanks Rohit, I will do all those steps.
I know the git branch is correct, but I will do a clean anyway.
Removing the maven repositories is a good idea.
Thx,
Will
On Fri, May 30, 2014 at 4:35 PM, Rohit Yadav wrote:
> Check if git branch or source code in question is correct, git clean -df
>
Check if git branch or source code in question is correct, git clean -df
(note: this will remove files not tracked by git), check that
the commands.properties has the API you were searching in apidocs, remove
~/.m2 and do mvn clean install, if that does not work check if the
API/plugin in question
On May 30, 2014, at 4:25 PM, Will Stevens wrote:
> By clean install you mean starting from scratch, not 'mvn clean install'
> right? I have been doing mvn clean installs…
>
Will, quickly stated I think that piece of code is a nightmare + folks have
complained about our apidocs.
Since you ar
By clean install you mean starting from scratch, not 'mvn clean install'
right? I have been doing mvn clean installs...
Will
On Fri, May 30, 2014 at 4:22 PM, Rohit Yadav wrote:
> Hi Will,
>
> Based on my last memories of the apidocs tool and maven poms, I think it
> used to scan built jar art
Hi Will,
Based on my last memories of the apidocs tool and maven poms, I think it
used to scan built jar artifacts and reference them against something like
a properties file (commands.properties?) and internally scans bunch of
annotations in available class files to find apis and create apidocs.
Hey All,
Paul Angus and I have both tested this and this is what we are seeing.
When we compile the the 'master' branch, the docs in
'tools/apidoc/target/xmldoc/html', but they appear to be the wrong docs.
Yes, we know that the versions that appear in the output is hardcoded in
the XSL files, but
11 matches
Mail list logo