On Wed, Oct 26, 2011 at 3:04 PM, Afkham Azeez <az...@wso2.com> wrote:
> How do we disable doc generation for registry? Building core is taking a > very long time. Hack is to comment out the reporting sections. Fix is to introduce a proper release profile. We desperately need such, going forward with Maven3. The registry kernel and other public APIs have good Javadocs, and if we start commenting this out, people will stop maintaining those over time. Similarly, we have other APIs in Carbon, we should be publishing these as API docs. Its a very bad practice and a huge limitation to not do that. Thanks, Senaka. > > > On Wed, Oct 26, 2011 at 4:35 AM, Senaka Fernando <sen...@wso2.com> wrote: > >> Hi Pradeep >> >> On Tue, Oct 25, 2011 at 10:10 PM, Pradeep Fernando <prad...@wso2.com>wrote: >> >>> hi, >>> >>> we had this issue before carbon 3.2.0. The javadoc info plugin used by >>> registry to populate javadocs go through all the available dependency graph >>> and try to get all the dependency info. we havent put that above repo as one >>> of our repos in carbon. Some pom of a jar dependency has it. >>> >>> In the earlier case senaka did some modifications to the pom and fixed >>> it. With the plugin version upgrades it has introduced again in to build. >>> Senaka can you remember what was the fix ? >>> >> >> I excluded the generation of the dependency reports in the javadoc plugin >> for Maven2. As I discussed with you earlier, we need to do the same for >> Maven3. But, it seems that the same mechanism of doing it won't work in >> Maven3, and it must be defined in a different way. >> >> Thanks, >> Senaka. >> >>> >>> The error here is that the build hangs. but after 20 mins or so it starts >>> again. no build failure, yet we have to fix this somehow. >>> >>> thanks, >>> --Pradeep >>> >>> _______________________________________________ >>> Carbon-dev mailing list >>> Carbon-dev@wso2.org >>> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >>> >>> >> >> >> -- >> *Senaka Fernando* >> Product Manager - WSO2 Governance Registry; >> Associate Technical Lead; WSO2 Inc.; http://wso2.com* >> Member; Apache Software Foundation; http://apache.org >> >> E-mail: senaka AT wso2.com >> **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 >> Linked-In: http://linkedin.com/in/senakafernando >> >> * >> Lean . Enterprise . Middleware >> >> >> _______________________________________________ >> Carbon-dev mailing list >> Carbon-dev@wso2.org >> http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev >> >> > > > -- > *Afkham Azeez* > Director of Architecture; WSO2, Inc.; http://wso2.com > Member; Apache Software Foundation; http://www.apache.org/ > * <http://www.apache.org/>** > email: **az...@wso2.com* <az...@wso2.com>* cell: +94 77 3320919 > blog: **http://blog.afkham.org* <http://blog.afkham.org>* > twitter: **http://twitter.com/afkham_azeez*<http://twitter.com/afkham_azeez> > * > linked-in: **http://lk.linkedin.com/in/afkhamazeez* > * > * > *Lean . Enterprise . Middleware* > > > _______________________________________________ > Carbon-dev mailing list > Carbon-dev@wso2.org > http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev > > -- *Senaka Fernando* Product Manager - WSO2 Governance Registry; Associate Technical Lead; WSO2 Inc.; http://wso2.com* Member; Apache Software Foundation; http://apache.org E-mail: senaka AT wso2.com **P: +1 408 754 7388; ext: 51736*; *M: +94 77 322 1818 Linked-In: http://linkedin.com/in/senakafernando *Lean . Enterprise . Middleware
_______________________________________________ Carbon-dev mailing list Carbon-dev@wso2.org http://mail.wso2.org/cgi-bin/mailman/listinfo/carbon-dev
