question about build

classic Classic list List threaded Threaded
3 messages Options
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

question about build

Scott Lewis-2
Hi Mat,

I have a question about the new tycho build.   I see there is a goal for
creating the javadoc via the new tycho build, and these javadocs get
uploaded to here [1].  This is all great.

One thing we have/had been doing, however, is to configure the javadoc
generation so that it doesn't publish the docs from *all* packages, but
rather only the API packages.   We did this by using a javadoc.xml file
in the org.eclipse.ecf project/javadoc.xml. How do we set those same
parameters in the tycho build so that the generated javadocs are
simpler/more complete?

BTW, I was able to add an example plugin
(com.mycorp.examples.timeservice.consumer.ds.async) to the examples
feature, add a pom.xml to this plugin, and update the list of included
modules in the top-level pom.xml and get everything to build properly.  
Is this the appropriate process? (i.e. is there any more/other to do
when adding a new plugin to an existing feature?)

Thanksinadvance,

Scott

[1] http://download.eclipse.org/rt/ecf/snapshot/javadoc/

_______________________________________________
ecf-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ecf-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: question about build

Mat Booth
On 27 November 2016 at 01:15, Scott Lewis <[hidden email]> wrote:
Hi Mat,

I have a question about the new tycho build.   I see there is a goal for creating the javadoc via the new tycho build, and these javadocs get uploaded to here [1].  This is all great.

One thing we have/had been doing, however, is to configure the javadoc generation so that it doesn't publish the docs from *all* packages, but rather only the API packages.   We did this by using a javadoc.xml file in the org.eclipse.ecf project/javadoc.xml. How do we set those same parameters in the tycho build so that the generated javadocs are simpler/more complete?


These parameters are set in the main parent pom.xml (in the configuration section for the maven-javadoc-plugin) -- I will submit a patch shortly to fix this and another javadoc problem.
 
BTW, I was able to add an example plugin (com.mycorp.examples.timeservice.consumer.ds.async) to the examples feature, add a pom.xml to this plugin, and update the list of included modules in the top-level pom.xml and get everything to build properly.   Is this the appropriate process? (i.e. is there any more/other to do when adding a new plugin to an existing feature?)


Yes, this the appropriate process, and no, you did all the necessary things :-)
 
Thanksinadvance,

Scott

[1] http://download.eclipse.org/rt/ecf/snapshot/javadoc/

_______________________________________________
ecf-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ecf-dev


_______________________________________________
ecf-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ecf-dev
Reply | Threaded
Open this post in threaded view
|  
Report Content as Inappropriate

Re: question about build

Scott Lewis-2
Hi Mat,

I would like to do a final build for 3.13.3 on Saturday if at all possible, so would you be able to submit this patch tomorrow/Friday?   I'll approve it as soon as possible.

Also if you have any thoughts on the removal of ECF Core Features and ECF Core Features Source from the top-level feature group as per the 'snapshot install test for 3.13.3'.

Thanksinadvance,

Scott

On 11/29/2016 1:24 AM, Mat Booth wrote:
On 27 November 2016 at 01:15, Scott Lewis <[hidden email]> wrote:
Hi Mat,

I have a question about the new tycho build.   I see there is a goal for creating the javadoc via the new tycho build, and these javadocs get uploaded to here [1].  This is all great.

One thing we have/had been doing, however, is to configure the javadoc generation so that it doesn't publish the docs from *all* packages, but rather only the API packages.   We did this by using a javadoc.xml file in the org.eclipse.ecf project/javadoc.xml. How do we set those same parameters in the tycho build so that the generated javadocs are simpler/more complete?


These parameters are set in the main parent pom.xml (in the configuration section for the maven-javadoc-plugin) -- I will submit a patch shortly to fix this and another javadoc problem.
 
BTW, I was able to add an example plugin (com.mycorp.examples.timeservice.consumer.ds.async) to the examples feature, add a pom.xml to this plugin, and update the list of included modules in the top-level pom.xml and get everything to build properly.   Is this the appropriate process? (i.e. is there any more/other to do when adding a new plugin to an existing feature?)


Yes, this the appropriate process, and no, you did all the necessary things :-)
 
Thanksinadvance,

Scott

[1] http://download.eclipse.org/rt/ecf/snapshot/javadoc/

_______________________________________________
ecf-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ecf-dev



_______________________________________________
ecf-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ecf-dev



_______________________________________________
ecf-dev mailing list
[hidden email]
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/ecf-dev
Loading...