subject:"\[Dev\] Chunk\-02 build failure"

Hi,

I am getting this.

[INFO] WSO2 Carbon - Patch releases - features - Aggregator Module  SKIPPED
[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 1:00.836s
[INFO] Finished at: Sat Sep 28 13:31:38 IST 2013
[INFO] Final Memory: 96M/596M
[INFO]

[ERROR] Failed to execute goal on project
org.wso2.carbon.databridge.datapublisher.feature: Could not resolve
dependencies for project
org.wso2.carbon:org.wso2.carbon.databridge.datapublisher.feature:pom:4.2.1:
Could not find artifact
org.wso2.carbon:org.wso2.carbon.databridge.commons.server.feature:zip:4.2.1
in wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/) -
[Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR]   mvn goals -rf :org.wso2.carbon.databridge.datapublisher.feature


-- 
*Isuru Udana*
*
*
Senior *
Software Engineer
*
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
twitter: http://twitter.com/isudana
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Chunk 02 - Build Failure

I am checking this


On Sat, Sep 28, 2013 at 1:43 PM, Isuru Udana isu...@wso2.com wrote:

 Hi,

 I am getting this.

 [INFO] WSO2 Carbon - Patch releases - features - Aggregator Module  SKIPPED
 [INFO]
 
 [INFO] BUILD FAILURE
 [INFO]
 
 [INFO] Total time: 1:00.836s
 [INFO] Finished at: Sat Sep 28 13:31:38 IST 2013
 [INFO] Final Memory: 96M/596M
 [INFO]
 
 [ERROR] Failed to execute goal on project
 org.wso2.carbon.databridge.datapublisher.feature: Could not resolve
 dependencies for project
 org.wso2.carbon:org.wso2.carbon.databridge.datapublisher.feature:pom:4.2.1:
 Could not find artifact
 org.wso2.carbon:org.wso2.carbon.databridge.commons.server.feature:zip:4.2.1
 in wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/)
 - [Help 1]
 [ERROR]
 [ERROR] To see the full stack trace of the errors, re-run Maven with the
 -e switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR]
 [ERROR] For more information about the errors and possible solutions,
 please read the following articles:
 [ERROR] [Help 1]
 http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
 [ERROR]
 [ERROR] After correcting the problems, you can resume the build with the
 command
 [ERROR]   mvn goals -rf :org.wso2.carbon.databridge.datapublisher.feature


 --
 *Isuru Udana*
 *
 *
 Senior *
 Software Engineer
 *
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/
 twitter: http://twitter.com/isudana

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




-- 
Regards,

Inosh Goonewardena
Associate Technical Lead- WSO2 Inc.
Mobile: +94779966317
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Chunk 02 - Build Failure

Added databridge.commons.server.feature 4.2.1 to chunk 02. Please get an
update and check.


On Sat, Sep 28, 2013 at 1:56 PM, Inosh Goonewardena in...@wso2.com wrote:

 I am checking this


 On Sat, Sep 28, 2013 at 1:43 PM, Isuru Udana isu...@wso2.com wrote:

 Hi,

 I am getting this.

 [INFO] WSO2 Carbon - Patch releases - features - Aggregator Module
  SKIPPED
 [INFO]
 
 [INFO] BUILD FAILURE
 [INFO]
 
 [INFO] Total time: 1:00.836s
 [INFO] Finished at: Sat Sep 28 13:31:38 IST 2013
 [INFO] Final Memory: 96M/596M
 [INFO]
 
 [ERROR] Failed to execute goal on project
 org.wso2.carbon.databridge.datapublisher.feature: Could not resolve
 dependencies for project
 org.wso2.carbon:org.wso2.carbon.databridge.datapublisher.feature:pom:4.2.1:
 Could not find artifact
 org.wso2.carbon:org.wso2.carbon.databridge.commons.server.feature:zip:4.2.1
 in wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/)
 - [Help 1]
 [ERROR]
 [ERROR] To see the full stack trace of the errors, re-run Maven with the
 -e switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR]
 [ERROR] For more information about the errors and possible solutions,
 please read the following articles:
 [ERROR] [Help 1]
 http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
 [ERROR]
 [ERROR] After correcting the problems, you can resume the build with the
 command
 [ERROR]   mvn goals -rf
 :org.wso2.carbon.databridge.datapublisher.feature


 --
 *Isuru Udana*
 *
 *
 Senior *
 Software Engineer
 *
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/
 twitter: http://twitter.com/isudana

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Regards,

 Inosh Goonewardena
 Associate Technical Lead- WSO2 Inc.
 Mobile: +94779966317




-- 
Regards,

Inosh Goonewardena
Associate Technical Lead- WSO2 Inc.
Mobile: +94779966317
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

[Dev] Chunk 02 - Build failure at components

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 6:47.976s
[INFO] Finished at: Sat Sep 28 14:22:40 IST 2013
[INFO] Final Memory: 680M/956M
[INFO]

[ERROR] Failed to execute goal on project org.wso2.carbon.analytics.hive:
Could not resolve dependencies for project
org.wso2.carbon:org.wso2.carbon.analytics.hive:bundle:4.2.0: The following
artifacts could not be resolved:
org.apache.hive.wso2:hive:jar:0.11.0.wso2v1,
org.wso2.carbon:org.wso2.carbon.rssmanager.core:jar:4.2.0: Failure to find
org.apache.hive.wso2:hive:jar:0.11.0.wso2v1 in
http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in the
local repository, resolution will not be reattempted until the update
interval of wso2-nexus has elapsed or updates are forced - [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR]   mvn goals -rf :org.wso2.carbon.analytics.hive


-- 
*Isuru Udana*
*
*
Senior *
Software Engineer
*
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
twitter: http://twitter.com/isudana
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Chunk 02 - Build failure at components

Hi Isuru,

For the moment could you please build 4.2.0/dependencies/hive/0.11.0-wso2v1
first and then build analytics.hive


On Sat, Sep 28, 2013 at 2:29 PM, Isuru Udana isu...@wso2.com wrote:

 [INFO] BUILD FAILURE
 [INFO]
 
 [INFO] Total time: 6:47.976s
 [INFO] Finished at: Sat Sep 28 14:22:40 IST 2013
 [INFO] Final Memory: 680M/956M
 [INFO]
 
 [ERROR] Failed to execute goal on project org.wso2.carbon.analytics.hive:
 Could not resolve dependencies for project
 org.wso2.carbon:org.wso2.carbon.analytics.hive:bundle:4.2.0: The following
 artifacts could not be resolved:
 org.apache.hive.wso2:hive:jar:0.11.0.wso2v1,
 org.wso2.carbon:org.wso2.carbon.rssmanager.core:jar:4.2.0: Failure to find
 org.apache.hive.wso2:hive:jar:0.11.0.wso2v1 in
 http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in the
 local repository, resolution will not be reattempted until the update
 interval of wso2-nexus has elapsed or updates are forced - [Help 1]
 [ERROR]
 [ERROR] To see the full stack trace of the errors, re-run Maven with the
 -e switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR]
 [ERROR] For more information about the errors and possible solutions,
 please read the following articles:
 [ERROR] [Help 1]
 http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
 [ERROR]
 [ERROR] After correcting the problems, you can resume the build with the
 command
 [ERROR]   mvn goals -rf :org.wso2.carbon.analytics.hive


 --
 *Isuru Udana*
 *
 *
 Senior *
 Software Engineer
 *
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/
 twitter: http://twitter.com/isudana

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




-- 
Regards,

Inosh Goonewardena
Associate Technical Lead- WSO2 Inc.
Mobile: +94779966317
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Chunk 02 - Build failure at components

Hi BAM Team,

Chunk-02 build it failing everywhere (components, features) with yesterday
commits done by BAM team.
Please revert those changes done for the chunk02 poms temporary and add
back only when you verify the build in a clean repo.

Thanks.



On Sat, Sep 28, 2013 at 2:40 PM, Inosh Goonewardena in...@wso2.com wrote:

 Hi Isuru,

 For the moment could you please build
 4.2.0/dependencies/hive/0.11.0-wso2v1 first and then build analytics.hive


 On Sat, Sep 28, 2013 at 2:29 PM, Isuru Udana isu...@wso2.com wrote:

  [INFO] BUILD FAILURE
 [INFO]
 
 [INFO] Total time: 6:47.976s
 [INFO] Finished at: Sat Sep 28 14:22:40 IST 2013
 [INFO] Final Memory: 680M/956M
 [INFO]
 
 [ERROR] Failed to execute goal on project org.wso2.carbon.analytics.hive:
 Could not resolve dependencies for project
 org.wso2.carbon:org.wso2.carbon.analytics.hive:bundle:4.2.0: The following
 artifacts could not be resolved:
 org.apache.hive.wso2:hive:jar:0.11.0.wso2v1,
 org.wso2.carbon:org.wso2.carbon.rssmanager.core:jar:4.2.0: Failure to find
 org.apache.hive.wso2:hive:jar:0.11.0.wso2v1 in
 http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in
 the local repository, resolution will not be reattempted until the update
 interval of wso2-nexus has elapsed or updates are forced - [Help 1]
 [ERROR]
 [ERROR] To see the full stack trace of the errors, re-run Maven with the
 -e switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR]
 [ERROR] For more information about the errors and possible solutions,
 please read the following articles:
 [ERROR] [Help 1]
 http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
 [ERROR]
 [ERROR] After correcting the problems, you can resume the build with the
 command
 [ERROR]   mvn goals -rf :org.wso2.carbon.analytics.hive


 --
 *Isuru Udana*
 *
 *
 Senior *
 Software Engineer
 *
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/
 twitter: http://twitter.com/isudana

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Regards,

 Inosh Goonewardena
 Associate Technical Lead- WSO2 Inc.
 Mobile: +94779966317




-- 
*Isuru Udana*
*
 *
Senior *
Software Engineer
*
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
twitter: http://twitter.com/isudana
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Chunk 02 - Build failure at components

Hi Isuru,

I have added changes to data-bridge, cassandra-explorer and
cassandra-search component and features yesterday. Apart from the one
reported in '[Dev] Chunk 02 - Build Failure' which I have fixed, are there
any other issues regarding data-bridge  cassandra components?



On Sat, Sep 28, 2013 at 2:45 PM, Isuru Udana isu...@wso2.com wrote:

 Hi BAM Team,

 Chunk-02 build it failing everywhere (components, features) with yesterday
 commits done by BAM team.
 Please revert those changes done for the chunk02 poms temporary and add
 back only when you verify the build in a clean repo.

 Thanks.



 On Sat, Sep 28, 2013 at 2:40 PM, Inosh Goonewardena in...@wso2.comwrote:

 Hi Isuru,

 For the moment could you please build
 4.2.0/dependencies/hive/0.11.0-wso2v1 first and then build analytics.hive


 On Sat, Sep 28, 2013 at 2:29 PM, Isuru Udana isu...@wso2.com wrote:

  [INFO] BUILD FAILURE
 [INFO]
 
 [INFO] Total time: 6:47.976s
 [INFO] Finished at: Sat Sep 28 14:22:40 IST 2013
 [INFO] Final Memory: 680M/956M
 [INFO]
 
 [ERROR] Failed to execute goal on project
 org.wso2.carbon.analytics.hive: Could not resolve dependencies for project
 org.wso2.carbon:org.wso2.carbon.analytics.hive:bundle:4.2.0: The following
 artifacts could not be resolved:
 org.apache.hive.wso2:hive:jar:0.11.0.wso2v1,
 org.wso2.carbon:org.wso2.carbon.rssmanager.core:jar:4.2.0: Failure to find
 org.apache.hive.wso2:hive:jar:0.11.0.wso2v1 in
 http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in
 the local repository, resolution will not be reattempted until the update
 interval of wso2-nexus has elapsed or updates are forced - [Help 1]
 [ERROR]
 [ERROR] To see the full stack trace of the errors, re-run Maven with the
 -e switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR]
 [ERROR] For more information about the errors and possible solutions,
 please read the following articles:
 [ERROR] [Help 1]
 http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
 [ERROR]
 [ERROR] After correcting the problems, you can resume the build with the
 command
 [ERROR]   mvn goals -rf :org.wso2.carbon.analytics.hive


 --
 *Isuru Udana*
 *
 *
 Senior *
 Software Engineer
 *
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/
 twitter: http://twitter.com/isudana

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Regards,

 Inosh Goonewardena
 Associate Technical Lead- WSO2 Inc.
 Mobile: +94779966317




 --
 *Isuru Udana*
 *
  *
 Senior *
 Software Engineer
 *
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/
 twitter: http://twitter.com/isudana




-- 
Regards,

Inosh Goonewardena
Associate Technical Lead- WSO2 Inc.
Mobile: +94779966317
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Chunk 02 - Build failure at components

Hi Isuru,

I have removed rss-manager dependency from
org.wso2.carbon.analytics.hive component and made the following changes to
chunk 02. Now the chunk 02 should build without a problem.

dashboards components were added
cassandra 1.1.3-wso2v5 dependencies were added
data-bridge datasink feature was added
analytic hive stubs were added




On Sat, Sep 28, 2013 at 8:27 PM, Isuru Udana isu...@wso2.com wrote:

 Hi BAM Team,

 Looks like some of the dependent components (ex. rss-manager) are still
 not added to chunk-02. When I added them locally and continue the build it
 fails from somewhere else. This will never ends :)

 I am suggesting again to revert all changes done to chunk-02 and build in
 a clean repo and commit all at once.

 I will locally revert BAM Team changes and continue my work.

 Thanks.


 On Sat, Sep 28, 2013 at 5:14 PM, Anjana Fernando anj...@wso2.com wrote:

 Hi Isuru,

 Fixed. Earlier I forgot to remove those dependencies when I removed some
 modules from the Hive dependency.

 Cheers,
 Anjana.


 On Sat, Sep 28, 2013 at 4:15 PM, Isuru Udana isu...@wso2.com wrote:

 Now I am getting this while building hive orbit.

 [INFO]

 [INFO]
 
 [INFO] Building hive.wso2 0.11.0.wso2v1
 [INFO]
 
 [WARNING] The POM for org.apache.hive:hive-cassandra:jar:0.11.0-wso2v1
 is missing, no dependency information available
 [WARNING] The POM for
 org.wso2.carbon:hive-jdbc-handler:jar:0.11.0-wso2v1 is missing, no
 dependency information available
 [INFO]
 
  [INFO] BUILD FAILURE
 [INFO]
 
 [INFO] Total time: 0.854s
 [INFO] Finished at: Sat Sep 28 16:12:57 IST 2013
  [INFO] Final Memory: 6M/490M
 [INFO]
 
 [ERROR] Failed to execute goal on project hive: Could not resolve
 dependencies for project org.apache.hive.wso2:hive:bundle:0.11.0.wso2v1:
 The following artifacts could not be resolved:
 org.apache.hive:hive-cassandra:jar:0.11.0-wso2v1,
 org.wso2.carbon:hive-jdbc-handler:jar:0.11.0-wso2v1: Failure to find
 org.apache.hive:hive-cassandra:jar:0.11.0-wso2v1 in
 http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in
 the local repository, resolution will not be reattempted until the update
 interval of wso2-nexus has elapsed or updates are forced - [Help 1]
 [ERROR]



 On Sat, Sep 28, 2013 at 3:45 PM, Isuru Udana isu...@wso2.com wrote:

 Thanks Anjana.
 The best approach is to first build chunk-02 without BAM changes in a
 clean repo and then merge BAM components.
 I followed that approach while merging ESB related components.
 I will report or fix straightforward build issues anyway.

 Thanks.




 On Sat, Sep 28, 2013 at 3:38 PM, Anjana Fernando anj...@wso2.comwrote:

 Hi Isuru,

 There was the case of new Hive version not added to chunk2, I just
 fixed it, where the full changes from chunk3 to chunk2 hasn't been done.
 Bear with us for a bit to get the build right, where there can be problems
 and complications in migrating the stuff from chunk3. If there are any
 build issues, please report it, or better yet, fix it then and there. 
 Inosh
 will soon be doing a full build with a clean repo to verify the changes.

 Cheers,
 Anjana.


 On Sat, Sep 28, 2013 at 2:45 PM, Isuru Udana isu...@wso2.com wrote:

 Hi BAM Team,

 Chunk-02 build it failing everywhere (components, features) with
 yesterday commits done by BAM team.
 Please revert those changes done for the chunk02 poms temporary and
 add back only when you verify the build in a clean repo.

 Thanks.



 On Sat, Sep 28, 2013 at 2:40 PM, Inosh Goonewardena 
 in...@wso2.comwrote:

 Hi Isuru,

 For the moment could you please build
 4.2.0/dependencies/hive/0.11.0-wso2v1 first and then build 
 analytics.hive


 On Sat, Sep 28, 2013 at 2:29 PM, Isuru Udana isu...@wso2.comwrote:

  [INFO] BUILD FAILURE
 [INFO]
 
 [INFO] Total time: 6:47.976s
 [INFO] Finished at: Sat Sep 28 14:22:40 IST 2013
 [INFO] Final Memory: 680M/956M
 [INFO]
 
 [ERROR] Failed to execute goal on project
 org.wso2.carbon.analytics.hive: Could not resolve dependencies for 
 project
 org.wso2.carbon:org.wso2.carbon.analytics.hive:bundle:4.2.0: The 
 following
 artifacts could not be resolved:
 org.apache.hive.wso2:hive:jar:0.11.0.wso2v1,
 org.wso2.carbon:org.wso2.carbon.rssmanager.core:jar:4.2.0: Failure to 
 find
 org.apache.hive.wso2:hive:jar:0.11.0.wso2v1 in
 http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached
 in the local repository, resolution will not be reattempted until the
 update interval of wso2-nexus has elapsed or updates are forced - 
 [Help 1]

Re: [Dev] Chunk 02 - Build failure at components

On Sun, Sep 29, 2013 at 3:19 AM, Inosh Goonewardena in...@wso2.com wrote:

 Hi Isuru,

 I have removed rss-manager dependency from
 org.wso2.carbon.analytics.hive component and made the following changes to
 chunk 02. Now the chunk 02 should build without a problem.

No it is not.

[INFO]

[INFO] BUILD FAILURE
[INFO]

[INFO] Total time: 1:53.696s
[INFO] Finished at: Sun Sep 29 08:21:53 IST 2013
[INFO] Final Memory: 113M/636M
[INFO]

[ERROR] Failed to execute goal on project
org.wso2.carbon.cassandra.explorer.server.feature: Could not resolve
dependencies for project
org.wso2.carbon:org.wso2.carbon.cassandra.explorer.server.feature:pom:4.2.0:
Could not find artifact
org.wso2.carbon:org.wso2.carbon.cassandra.explorer.mgt:jar:4.2.0 in
wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/) -
[Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR]   mvn goals -rf :org.wso2.carbon.cassandra.explorer.server.feature




 dashboards components were added
 cassandra 1.1.3-wso2v5 dependencies were added
 data-bridge datasink feature was added
 analytic hive stubs were added




 On Sat, Sep 28, 2013 at 8:27 PM, Isuru Udana isu...@wso2.com wrote:

 Hi BAM Team,

 Looks like some of the dependent components (ex. rss-manager) are still
 not added to chunk-02. When I added them locally and continue the build it
 fails from somewhere else. This will never ends :)

 I am suggesting again to revert all changes done to chunk-02 and build in
 a clean repo and commit all at once.

 I will locally revert BAM Team changes and continue my work.

 Thanks.


 On Sat, Sep 28, 2013 at 5:14 PM, Anjana Fernando anj...@wso2.com wrote:

 Hi Isuru,

 Fixed. Earlier I forgot to remove those dependencies when I removed some
 modules from the Hive dependency.

 Cheers,
 Anjana.


 On Sat, Sep 28, 2013 at 4:15 PM, Isuru Udana isu...@wso2.com wrote:

 Now I am getting this while building hive orbit.

 [INFO]

 [INFO]
 
 [INFO] Building hive.wso2 0.11.0.wso2v1
 [INFO]
 
 [WARNING] The POM for org.apache.hive:hive-cassandra:jar:0.11.0-wso2v1
 is missing, no dependency information available
 [WARNING] The POM for
 org.wso2.carbon:hive-jdbc-handler:jar:0.11.0-wso2v1 is missing, no
 dependency information available
 [INFO]
 
  [INFO] BUILD FAILURE
 [INFO]
 
 [INFO] Total time: 0.854s
 [INFO] Finished at: Sat Sep 28 16:12:57 IST 2013
  [INFO] Final Memory: 6M/490M
 [INFO]
 
 [ERROR] Failed to execute goal on project hive: Could not resolve
 dependencies for project org.apache.hive.wso2:hive:bundle:0.11.0.wso2v1:
 The following artifacts could not be resolved:
 org.apache.hive:hive-cassandra:jar:0.11.0-wso2v1,
 org.wso2.carbon:hive-jdbc-handler:jar:0.11.0-wso2v1: Failure to find
 org.apache.hive:hive-cassandra:jar:0.11.0-wso2v1 in
 http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in
 the local repository, resolution will not be reattempted until the update
 interval of wso2-nexus has elapsed or updates are forced - [Help 1]
 [ERROR]



 On Sat, Sep 28, 2013 at 3:45 PM, Isuru Udana isu...@wso2.com wrote:

 Thanks Anjana.
 The best approach is to first build chunk-02 without BAM changes in a
 clean repo and then merge BAM components.
 I followed that approach while merging ESB related components.
 I will report or fix straightforward build issues anyway.

 Thanks.




 On Sat, Sep 28, 2013 at 3:38 PM, Anjana Fernando anj...@wso2.comwrote:

 Hi Isuru,

 There was the case of new Hive version not added to chunk2, I just
 fixed it, where the full changes from chunk3 to chunk2 hasn't been done.
 Bear with us for a bit to get the build right, where there can be 
 problems
 and complications in migrating the stuff from chunk3. If there are any
 build issues, please report it, or better yet, fix it then and there. 
 Inosh
 will soon be doing a full build with a clean repo to verify the changes.

 Cheers,
 Anjana.


 On Sat, Sep 28, 2013 at 2:45 PM, Isuru Udana isu...@wso2.com wrote:

 Hi BAM Team,

 Chunk-02 build it failing everywhere

Re: [Dev] Chunk 02 - Build failure at components

Fixed. Somehow cassanda-explorer components were missing. I have added them
now


On Sun, Sep 29, 2013 at 8:41 AM, Isuru Udana isu...@wso2.com wrote:




 On Sun, Sep 29, 2013 at 3:19 AM, Inosh Goonewardena in...@wso2.comwrote:

 Hi Isuru,

 I have removed rss-manager dependency from
 org.wso2.carbon.analytics.hive component and made the following changes to
 chunk 02. Now the chunk 02 should build without a problem.

 No it is not.

 [INFO]
 
 [INFO] BUILD FAILURE
 [INFO]
 
 [INFO] Total time: 1:53.696s
 [INFO] Finished at: Sun Sep 29 08:21:53 IST 2013
 [INFO] Final Memory: 113M/636M
 [INFO]
 
 [ERROR] Failed to execute goal on project
 org.wso2.carbon.cassandra.explorer.server.feature: Could not resolve
 dependencies for project
 org.wso2.carbon:org.wso2.carbon.cassandra.explorer.server.feature:pom:4.2.0:
 Could not find artifact
 org.wso2.carbon:org.wso2.carbon.cassandra.explorer.mgt:jar:4.2.0 in
 wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/) -
 [Help 1]
  [ERROR]
 [ERROR] To see the full stack trace of the errors, re-run Maven with the
 -e switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR]
 [ERROR] For more information about the errors and possible solutions,
 please read the following articles:
 [ERROR] [Help 1]
 http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
 [ERROR]
 [ERROR] After correcting the problems, you can resume the build with the
 command
 [ERROR]   mvn goals -rf
 :org.wso2.carbon.cassandra.explorer.server.feature




 dashboards components were added
 cassandra 1.1.3-wso2v5 dependencies were added
 data-bridge datasink feature was added
 analytic hive stubs were added




 On Sat, Sep 28, 2013 at 8:27 PM, Isuru Udana isu...@wso2.com wrote:

 Hi BAM Team,

 Looks like some of the dependent components (ex. rss-manager) are still
 not added to chunk-02. When I added them locally and continue the build it
 fails from somewhere else. This will never ends :)

 I am suggesting again to revert all changes done to chunk-02 and build
 in a clean repo and commit all at once.

 I will locally revert BAM Team changes and continue my work.

 Thanks.


 On Sat, Sep 28, 2013 at 5:14 PM, Anjana Fernando anj...@wso2.comwrote:

 Hi Isuru,

 Fixed. Earlier I forgot to remove those dependencies when I removed
 some modules from the Hive dependency.

 Cheers,
 Anjana.


 On Sat, Sep 28, 2013 at 4:15 PM, Isuru Udana isu...@wso2.com wrote:

 Now I am getting this while building hive orbit.

 [INFO]

 [INFO]
 
 [INFO] Building hive.wso2 0.11.0.wso2v1
 [INFO]
 
 [WARNING] The POM for org.apache.hive:hive-cassandra:jar:0.11.0-wso2v1
 is missing, no dependency information available
 [WARNING] The POM for
 org.wso2.carbon:hive-jdbc-handler:jar:0.11.0-wso2v1 is missing, no
 dependency information available
 [INFO]
 
  [INFO] BUILD FAILURE
 [INFO]
 
 [INFO] Total time: 0.854s
 [INFO] Finished at: Sat Sep 28 16:12:57 IST 2013
  [INFO] Final Memory: 6M/490M
 [INFO]
 
 [ERROR] Failed to execute goal on project hive: Could not resolve
 dependencies for project org.apache.hive.wso2:hive:bundle:0.11.0.wso2v1:
 The following artifacts could not be resolved:
 org.apache.hive:hive-cassandra:jar:0.11.0-wso2v1,
 org.wso2.carbon:hive-jdbc-handler:jar:0.11.0-wso2v1: Failure to find
 org.apache.hive:hive-cassandra:jar:0.11.0-wso2v1 in
 http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached in
 the local repository, resolution will not be reattempted until the update
 interval of wso2-nexus has elapsed or updates are forced - [Help 1]
 [ERROR]



 On Sat, Sep 28, 2013 at 3:45 PM, Isuru Udana isu...@wso2.com wrote:

 Thanks Anjana.
 The best approach is to first build chunk-02 without BAM changes in a
 clean repo and then merge BAM components.
 I followed that approach while merging ESB related components.
 I will report or fix straightforward build issues anyway.

 Thanks.




 On Sat, Sep 28, 2013 at 3:38 PM, Anjana Fernando anj...@wso2.comwrote:

 Hi Isuru,

 There was the case of new Hive version not added to chunk2, I just
 fixed it, where the full changes from chunk3 to chunk2 hasn't been done.
 Bear with us for a bit to get the build right, where there can be 
 problems
 and complications in migrating the stuff from chunk3. If there are any
 build issues, please report it, or better yet, fix it then and there. 
 Inosh
 will soon be doing a full build with a

Re: [Dev] Chunk 02 - Build failure at components

Thanks Inosh. Now it is building without failures.


On Sun, Sep 29, 2013 at 8:51 AM, Inosh Goonewardena in...@wso2.com wrote:

 Fixed. Somehow cassanda-explorer components were missing. I have added
 them now


 On Sun, Sep 29, 2013 at 8:41 AM, Isuru Udana isu...@wso2.com wrote:




 On Sun, Sep 29, 2013 at 3:19 AM, Inosh Goonewardena in...@wso2.comwrote:

 Hi Isuru,

 I have removed rss-manager dependency from
 org.wso2.carbon.analytics.hive component and made the following changes to
 chunk 02. Now the chunk 02 should build without a problem.

 No it is not.

 [INFO]
 
 [INFO] BUILD FAILURE
 [INFO]
 
 [INFO] Total time: 1:53.696s
 [INFO] Finished at: Sun Sep 29 08:21:53 IST 2013
 [INFO] Final Memory: 113M/636M
 [INFO]
 
 [ERROR] Failed to execute goal on project
 org.wso2.carbon.cassandra.explorer.server.feature: Could not resolve
 dependencies for project
 org.wso2.carbon:org.wso2.carbon.cassandra.explorer.server.feature:pom:4.2.0:
 Could not find artifact
 org.wso2.carbon:org.wso2.carbon.cassandra.explorer.mgt:jar:4.2.0 in
 wso2-nexus (http://maven.wso2.org/nexus/content/groups/wso2-public/) -
 [Help 1]
  [ERROR]
 [ERROR] To see the full stack trace of the errors, re-run Maven with the
 -e switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR]
 [ERROR] For more information about the errors and possible solutions,
 please read the following articles:
 [ERROR] [Help 1]
 http://cwiki.apache.org/confluence/display/MAVEN/DependencyResolutionException
 [ERROR]
 [ERROR] After correcting the problems, you can resume the build with the
 command
 [ERROR]   mvn goals -rf
 :org.wso2.carbon.cassandra.explorer.server.feature




 dashboards components were added
 cassandra 1.1.3-wso2v5 dependencies were added
 data-bridge datasink feature was added
 analytic hive stubs were added




 On Sat, Sep 28, 2013 at 8:27 PM, Isuru Udana isu...@wso2.com wrote:

 Hi BAM Team,

 Looks like some of the dependent components (ex. rss-manager) are still
 not added to chunk-02. When I added them locally and continue the build it
 fails from somewhere else. This will never ends :)

 I am suggesting again to revert all changes done to chunk-02 and build
 in a clean repo and commit all at once.

 I will locally revert BAM Team changes and continue my work.

 Thanks.


 On Sat, Sep 28, 2013 at 5:14 PM, Anjana Fernando anj...@wso2.comwrote:

 Hi Isuru,

 Fixed. Earlier I forgot to remove those dependencies when I removed
 some modules from the Hive dependency.

 Cheers,
 Anjana.


 On Sat, Sep 28, 2013 at 4:15 PM, Isuru Udana isu...@wso2.com wrote:

 Now I am getting this while building hive orbit.

 [INFO]

 [INFO]
 
 [INFO] Building hive.wso2 0.11.0.wso2v1
 [INFO]
 
 [WARNING] The POM for
 org.apache.hive:hive-cassandra:jar:0.11.0-wso2v1 is missing, no 
 dependency
 information available
 [WARNING] The POM for
 org.wso2.carbon:hive-jdbc-handler:jar:0.11.0-wso2v1 is missing, no
 dependency information available
 [INFO]
 
  [INFO] BUILD FAILURE
 [INFO]
 
 [INFO] Total time: 0.854s
 [INFO] Finished at: Sat Sep 28 16:12:57 IST 2013
  [INFO] Final Memory: 6M/490M
 [INFO]
 
 [ERROR] Failed to execute goal on project hive: Could not resolve
 dependencies for project org.apache.hive.wso2:hive:bundle:0.11.0.wso2v1:
 The following artifacts could not be resolved:
 org.apache.hive:hive-cassandra:jar:0.11.0-wso2v1,
 org.wso2.carbon:hive-jdbc-handler:jar:0.11.0-wso2v1: Failure to find
 org.apache.hive:hive-cassandra:jar:0.11.0-wso2v1 in
 http://maven.wso2.org/nexus/content/groups/wso2-public/ was cached
 in the local repository, resolution will not be reattempted until the
 update interval of wso2-nexus has elapsed or updates are forced - [Help 
 1]
 [ERROR]



 On Sat, Sep 28, 2013 at 3:45 PM, Isuru Udana isu...@wso2.com wrote:

 Thanks Anjana.
 The best approach is to first build chunk-02 without BAM changes in
 a clean repo and then merge BAM components.
 I followed that approach while merging ESB related components.
 I will report or fix straightforward build issues anyway.

 Thanks.




 On Sat, Sep 28, 2013 at 3:38 PM, Anjana Fernando anj...@wso2.comwrote:

 Hi Isuru,

 There was the case of new Hive version not added to chunk2, I just
 fixed it, where the full changes from chunk3 to chunk2 hasn't been 
 done.
 Bear with us for a bit to get the build right, where there can be 
 problems
 and complications in migrating the stuff from chunk3.

[Dev] Chunk 02 Build Failure

I am getting the following build failure.

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
(default-compile) on project org.wso2.carbon.registry.indexing: Compilation
failure
[ERROR]
/media/isuru/WSO2/svn/public/4.2.0/platform/4.2.0/components/registry/org.wso2.carbon.registry.indexing/4.2.1/src/main/java/org/wso2/carbon/registry/indexing/service/ContentBasedSearchService.java:[140,33]
cannot find symbol
[ERROR] symbol  : method setLength(int)
[ERROR] location: class
org.wso2.carbon.registry.core.pagination.PaginationContext
[ERROR] - [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven with the -e
switch.
[ERROR] Re-run Maven using the -X switch to enable full debug logging.
[ERROR]
[ERROR] For more information about the errors and possible solutions,
please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build with the
command
[ERROR]   mvn goals -rf :org.wso2.carbon.registry.indexing

This got resolved after building kernel patch0001.
Are we allow API changes in kernel patches now ?


-- 
*Isuru Udana*
*
*
Senior *
Software Engineer
*
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
twitter: http://twitter.com/isudana
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Chunk 02 Build Failure

2013-09-26 Thread Lalaji Sureshika

Hi Isuru,

This fix was added by Ajith as part of the fix an issue on registry
pagination with APIM integration.AFAIK,by this change a new getter/setter
has added to PaginationContext class. Refer the jira [1]

[1] https://wso2.org/jira/browse/REGISTRY-2003


Thanks;


On Thu, Sep 26, 2013 at 11:03 PM, Isuru Udana isu...@wso2.com wrote:

 I am getting the following build failure.

 [ERROR] Failed to execute goal
 org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
 (default-compile) on project org.wso2.carbon.registry.indexing: Compilation
 failure
 [ERROR]
 /media/isuru/WSO2/svn/public/4.2.0/platform/4.2.0/components/registry/org.wso2.carbon.registry.indexing/4.2.1/src/main/java/org/wso2/carbon/registry/indexing/service/ContentBasedSearchService.java:[140,33]
 cannot find symbol
 [ERROR] symbol  : method setLength(int)
 [ERROR] location: class
 org.wso2.carbon.registry.core.pagination.PaginationContext
 [ERROR] - [Help 1]
 [ERROR]
 [ERROR] To see the full stack trace of the errors, re-run Maven with the
 -e switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR]
 [ERROR] For more information about the errors and possible solutions,
 please read the following articles:
 [ERROR] [Help 1]
 http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
 [ERROR]
 [ERROR] After correcting the problems, you can resume the build with the
 command
 [ERROR]   mvn goals -rf :org.wso2.carbon.registry.indexing

 This got resolved after building kernel patch0001.
 Are we allow API changes in kernel patches now ?


 --
 *Isuru Udana*
 *
 *
 Senior *
 Software Engineer
 *
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/
 twitter: http://twitter.com/isudana

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




-- 
Lalaji Sureshika
WSO2, Inc.;  http://wso2.com/
email: lal...@wso2.com; cell: +94 71 608 6811
blog: http://lalajisureshika.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Chunk 02 Build Failure

Hi Lalaji,

AFAIK api changes are not allowed for Kernel patches. We had a similar case
for 4.1.3 and had to revert that at the last moment.


On Thu, Sep 26, 2013 at 11:14 PM, Lalaji Sureshika lal...@wso2.com wrote:

 Hi Isuru,

 This fix was added by Ajith as part of the fix an issue on registry
 pagination with APIM integration.AFAIK,by this change a new getter/setter
 has added to PaginationContext class. Refer the jira [1]


 [1] https://wso2.org/jira/browse/REGISTRY-2003


 Thanks;


 On Thu, Sep 26, 2013 at 11:03 PM, Isuru Udana isu...@wso2.com wrote:

  I am getting the following build failure.

 [ERROR] Failed to execute goal
 org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
 (default-compile) on project org.wso2.carbon.registry.indexing: Compilation
 failure
 [ERROR]
 /media/isuru/WSO2/svn/public/4.2.0/platform/4.2.0/components/registry/org.wso2.carbon.registry.indexing/4.2.1/src/main/java/org/wso2/carbon/registry/indexing/service/ContentBasedSearchService.java:[140,33]
 cannot find symbol
 [ERROR] symbol  : method setLength(int)
 [ERROR] location: class
 org.wso2.carbon.registry.core.pagination.PaginationContext
 [ERROR] - [Help 1]
 [ERROR]
 [ERROR] To see the full stack trace of the errors, re-run Maven with the
 -e switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR]
 [ERROR] For more information about the errors and possible solutions,
 please read the following articles:
 [ERROR] [Help 1]
 http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
 [ERROR]
 [ERROR] After correcting the problems, you can resume the build with the
 command
 [ERROR]   mvn goals -rf :org.wso2.carbon.registry.indexing

 This got resolved after building kernel patch0001.
 Are we allow API changes in kernel patches now ?


 --
 *Isuru Udana*
 *
 *
 Senior *
 Software Engineer
 *
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/
 twitter: http://twitter.com/isudana

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Lalaji Sureshika
  WSO2, Inc.;  http://wso2.com/
 email: lal...@wso2.com; cell: +94 71 608 6811
 blog: http://lalajisureshika.blogspot.com





-- 
*Isuru Udana*
*
 *
Senior *
Software Engineer
*
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
twitter: http://twitter.com/isudana
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Chunk 02 Build Failure

2013-09-26 Thread Lalaji Sureshika

Hi,

From this fix, only a new method has added and no existing API method
changes happened .Thus will this be cause any problem..?
From APIM side,we need this fix,to integrate registry pagination in APIM
[which has increased the performance of APIs loading in APIStore ] and this
is a bug fix,which hasn't identified before chunk1 release out..

Thanks;



On Thu, Sep 26, 2013 at 11:19 PM, Isuru Udana isu...@wso2.com wrote:

 Hi Lalaji,

 AFAIK api changes are not allowed for Kernel patches. We had a similar
 case for 4.1.3 and had to revert that at the last moment.



 On Thu, Sep 26, 2013 at 11:14 PM, Lalaji Sureshika lal...@wso2.comwrote:

 Hi Isuru,

 This fix was added by Ajith as part of the fix an issue on registry
 pagination with APIM integration.AFAIK,by this change a new getter/setter
 has added to PaginationContext class. Refer the jira [1]


 [1] https://wso2.org/jira/browse/REGISTRY-2003


 Thanks;


 On Thu, Sep 26, 2013 at 11:03 PM, Isuru Udana isu...@wso2.com wrote:

  I am getting the following build failure.

 [ERROR] Failed to execute goal
 org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
 (default-compile) on project org.wso2.carbon.registry.indexing: Compilation
 failure
 [ERROR]
 /media/isuru/WSO2/svn/public/4.2.0/platform/4.2.0/components/registry/org.wso2.carbon.registry.indexing/4.2.1/src/main/java/org/wso2/carbon/registry/indexing/service/ContentBasedSearchService.java:[140,33]
 cannot find symbol
 [ERROR] symbol  : method setLength(int)
 [ERROR] location: class
 org.wso2.carbon.registry.core.pagination.PaginationContext
 [ERROR] - [Help 1]
 [ERROR]
 [ERROR] To see the full stack trace of the errors, re-run Maven with the
 -e switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR]
 [ERROR] For more information about the errors and possible solutions,
 please read the following articles:
 [ERROR] [Help 1]
 http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
 [ERROR]
 [ERROR] After correcting the problems, you can resume the build with the
 command
 [ERROR]   mvn goals -rf :org.wso2.carbon.registry.indexing

 This got resolved after building kernel patch0001.
 Are we allow API changes in kernel patches now ?


 --
 *Isuru Udana*
 *
 *
 Senior *
 Software Engineer
 *
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/
 twitter: http://twitter.com/isudana

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Lalaji Sureshika
  WSO2, Inc.;  http://wso2.com/
 email: lal...@wso2.com; cell: +94 71 608 6811
 blog: http://lalajisureshika.blogspot.com





 --
 *Isuru Udana*
 *
  *
 Senior *
 Software Engineer
 *
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/
 twitter: http://twitter.com/isudana




-- 
Lalaji Sureshika
WSO2, Inc.;  http://wso2.com/
email: lal...@wso2.com; cell: +94 71 608 6811
blog: http://lalajisureshika.blogspot.com
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Chunk 02 Build Failure

2013-09-26 Thread Ajith Vitharana

On Thu, Sep 26, 2013 at 11:19 PM, Isuru Udana isu...@wso2.com wrote:

 Hi Lalaji,

 AFAIK api changes are not allowed for Kernel patches. We had a similar
 case for 4.1.3 and had to revert that at the last moment.


AM pagination integration happened after chunk01 release. We had to do so
to fix some limitations.
This fix should be there to achieve the pagination requirement in AM , UES.

Thanks
Ajith.




 On Thu, Sep 26, 2013 at 11:14 PM, Lalaji Sureshika lal...@wso2.comwrote:

 Hi Isuru,

 This fix was added by Ajith as part of the fix an issue on registry
 pagination with APIM integration.AFAIK,by this change a new getter/setter
 has added to PaginationContext class. Refer the jira [1]


 [1] https://wso2.org/jira/browse/REGISTRY-2003


 Thanks;


 On Thu, Sep 26, 2013 at 11:03 PM, Isuru Udana isu...@wso2.com wrote:

  I am getting the following build failure.

 [ERROR] Failed to execute goal
 org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
 (default-compile) on project org.wso2.carbon.registry.indexing: Compilation
 failure
 [ERROR]
 /media/isuru/WSO2/svn/public/4.2.0/platform/4.2.0/components/registry/org.wso2.carbon.registry.indexing/4.2.1/src/main/java/org/wso2/carbon/registry/indexing/service/ContentBasedSearchService.java:[140,33]
 cannot find symbol
 [ERROR] symbol  : method setLength(int)
 [ERROR] location: class
 org.wso2.carbon.registry.core.pagination.PaginationContext
 [ERROR] - [Help 1]
 [ERROR]
 [ERROR] To see the full stack trace of the errors, re-run Maven with the
 -e switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR]
 [ERROR] For more information about the errors and possible solutions,
 please read the following articles:
 [ERROR] [Help 1]
 http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
 [ERROR]
 [ERROR] After correcting the problems, you can resume the build with the
 command
 [ERROR]   mvn goals -rf :org.wso2.carbon.registry.indexing

 This got resolved after building kernel patch0001.
 Are we allow API changes in kernel patches now ?


 --
 *Isuru Udana*
 *
 *
 Senior *
 Software Engineer
 *
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/
 twitter: http://twitter.com/isudana

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Lalaji Sureshika
  WSO2, Inc.;  http://wso2.com/
 email: lal...@wso2.com; cell: +94 71 608 6811
 blog: http://lalajisureshika.blogspot.com





 --
 *Isuru Udana*
 *
  *
 Senior *
 Software Engineer
 *
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/
 twitter: http://twitter.com/isudana




-- 
Ajith Vitharana.
WSO2 Inc. - http://wso2.org
Email  :  aji...@wso2.com
Mobile : +94772217350
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Chunk 02 Build Failure

2013-09-26 Thread Sumedha Rubasinghe

On Thu, Sep 26, 2013 at 11:57 PM, Ajith Vitharana aji...@wso2.com wrote:




 On Thu, Sep 26, 2013 at 11:35 PM, Lalaji Sureshika lal...@wso2.comwrote:

 Hi,

 From this fix, only a new method has added and no existing API method
 changes happened .Thus will this be cause any problem..?
 From APIM side,we need this fix,to integrate registry pagination in APIM
 [which has increased the performance of APIs loading in APIStore ] and this
 is a bug fix,which hasn't identified before chunk1 release out..


 Feature development and integrations can't avoid after chunk01 release, we
 have to face limitations or bugs.
 If the feature/bug is critical for the given release, we need some
 alternative  than preventing API changes.


But this violates chunk release  strategy. Your features will not be
compatible within platform.
Please get Sameera's input on this.



 Thanks
 Ajith



 Thanks;



 On Thu, Sep 26, 2013 at 11:19 PM, Isuru Udana isu...@wso2.com wrote:

 Hi Lalaji,

 AFAIK api changes are not allowed for Kernel patches. We had a similar
 case for 4.1.3 and had to revert that at the last moment.



 On Thu, Sep 26, 2013 at 11:14 PM, Lalaji Sureshika lal...@wso2.comwrote:

 Hi Isuru,

 This fix was added by Ajith as part of the fix an issue on registry
 pagination with APIM integration.AFAIK,by this change a new getter/setter
 has added to PaginationContext class. Refer the jira [1]


 [1] https://wso2.org/jira/browse/REGISTRY-2003


 Thanks;


 On Thu, Sep 26, 2013 at 11:03 PM, Isuru Udana isu...@wso2.com wrote:

  I am getting the following build failure.

 [ERROR] Failed to execute goal
 org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
 (default-compile) on project org.wso2.carbon.registry.indexing: 
 Compilation
 failure
 [ERROR]
 /media/isuru/WSO2/svn/public/4.2.0/platform/4.2.0/components/registry/org.wso2.carbon.registry.indexing/4.2.1/src/main/java/org/wso2/carbon/registry/indexing/service/ContentBasedSearchService.java:[140,33]
 cannot find symbol
 [ERROR] symbol  : method setLength(int)
 [ERROR] location: class
 org.wso2.carbon.registry.core.pagination.PaginationContext
 [ERROR] - [Help 1]
 [ERROR]
 [ERROR] To see the full stack trace of the errors, re-run Maven with
 the -e switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR]
 [ERROR] For more information about the errors and possible solutions,
 please read the following articles:
 [ERROR] [Help 1]
 http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
 [ERROR]
 [ERROR] After correcting the problems, you can resume the build with
 the command
 [ERROR]   mvn goals -rf :org.wso2.carbon.registry.indexing

 This got resolved after building kernel patch0001.
 Are we allow API changes in kernel patches now ?


 --
 *Isuru Udana*
 *
 *
 Senior *
 Software Engineer
 *
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/
 twitter: http://twitter.com/isudana

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Lalaji Sureshika
  WSO2, Inc.;  http://wso2.com/
 email: lal...@wso2.com; cell: +94 71 608 6811
 blog: http://lalajisureshika.blogspot.com





 --
 *Isuru Udana*
 *
  *
 Senior *
 Software Engineer
 *
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/
 twitter: http://twitter.com/isudana




 --
 Lalaji Sureshika
 WSO2, Inc.;  http://wso2.com/
 email: lal...@wso2.com; cell: +94 71 608 6811
 blog: http://lalajisureshika.blogspot.com





 --
 Ajith Vitharana.
 WSO2 Inc. - http://wso2.org
 Email  :  aji...@wso2.com
 Mobile : +94772217350


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




-- 
/sumedha
m: +94 773017743
b :  bit.ly/sumedha
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Chunk 02 Build Failure

2013-09-26 Thread Ajith Vitharana

On Fri, Sep 27, 2013 at 12:22 AM, Sumedha Rubasinghe sume...@wso2.comwrote:




 On Thu, Sep 26, 2013 at 11:57 PM, Ajith Vitharana aji...@wso2.com wrote:




 On Thu, Sep 26, 2013 at 11:35 PM, Lalaji Sureshika lal...@wso2.comwrote:

 Hi,

 From this fix, only a new method has added and no existing API method
 changes happened .Thus will this be cause any problem..?
 From APIM side,we need this fix,to integrate registry pagination in APIM
 [which has increased the performance of APIs loading in APIStore ] and this
 is a bug fix,which hasn't identified before chunk1 release out..


 Feature development and integrations can't avoid after chunk01 release,
 we have to face limitations or bugs.
 If the feature/bug is critical for the given release, we need some
 alternative  than preventing API changes.


 But this violates chunk release  strategy. Your features will not be
 compatible within platform.
 Please get Sameera's input on this.


It is not practical to develop/integrate feature at  *chunk01* to
compatible in all over the platform.

Eg: How to test/integrate AM with pagination at the *chunk01* without
proper AM build (or distributed setup) ???.
At the chunk01 we did AS, IS but pagination didn't involved with those
products.

My suggestion is we should restrict the API changes once we finished at
least  one release of the all the products from a given kernel release.
Because kernel 4.2.0 based product releases are major releases that
involves many new features and integrations, therefore nothing to wonder
with API changes.

Thanks
Ajith.





 Thanks
 Ajith



 Thanks;



 On Thu, Sep 26, 2013 at 11:19 PM, Isuru Udana isu...@wso2.com wrote:

 Hi Lalaji,

 AFAIK api changes are not allowed for Kernel patches. We had a similar
 case for 4.1.3 and had to revert that at the last moment.



 On Thu, Sep 26, 2013 at 11:14 PM, Lalaji Sureshika lal...@wso2.comwrote:

 Hi Isuru,

 This fix was added by Ajith as part of the fix an issue on registry
 pagination with APIM integration.AFAIK,by this change a new getter/setter
 has added to PaginationContext class. Refer the jira [1]


 [1] https://wso2.org/jira/browse/REGISTRY-2003


 Thanks;


 On Thu, Sep 26, 2013 at 11:03 PM, Isuru Udana isu...@wso2.com wrote:

  I am getting the following build failure.

 [ERROR] Failed to execute goal
 org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
 (default-compile) on project org.wso2.carbon.registry.indexing: 
 Compilation
 failure
 [ERROR]
 /media/isuru/WSO2/svn/public/4.2.0/platform/4.2.0/components/registry/org.wso2.carbon.registry.indexing/4.2.1/src/main/java/org/wso2/carbon/registry/indexing/service/ContentBasedSearchService.java:[140,33]
 cannot find symbol
 [ERROR] symbol  : method setLength(int)
 [ERROR] location: class
 org.wso2.carbon.registry.core.pagination.PaginationContext
 [ERROR] - [Help 1]
 [ERROR]
 [ERROR] To see the full stack trace of the errors, re-run Maven with
 the -e switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug logging.
 [ERROR]
 [ERROR] For more information about the errors and possible solutions,
 please read the following articles:
 [ERROR] [Help 1]
 http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
 [ERROR]
 [ERROR] After correcting the problems, you can resume the build with
 the command
 [ERROR]   mvn goals -rf :org.wso2.carbon.registry.indexing

 This got resolved after building kernel patch0001.
 Are we allow API changes in kernel patches now ?


 --
 *Isuru Udana*
 *
 *
 Senior *
 Software Engineer
 *
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/
 twitter: http://twitter.com/isudana

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Lalaji Sureshika
  WSO2, Inc.;  http://wso2.com/
 email: lal...@wso2.com; cell: +94 71 608 6811
 blog: http://lalajisureshika.blogspot.com





 --
 *Isuru Udana*
 *
  *
 Senior *
 Software Engineer
 *
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/
 twitter: http://twitter.com/isudana




 --
 Lalaji Sureshika
 WSO2, Inc.;  http://wso2.com/
 email: lal...@wso2.com; cell: +94 71 608 6811
 blog: http://lalajisureshika.blogspot.com





 --
 Ajith Vitharana.
 WSO2 Inc. - http://wso2.org
 Email  :  aji...@wso2.com
 Mobile : +94772217350


 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 /sumedha
 m: +94 773017743
 b :  bit.ly/sumedha




-- 
Ajith Vitharana.
WSO2 Inc. - http://wso2.org
Email  :  aji...@wso2.com
Mobile : +94772217350
___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

Re: [Dev] Chunk 02 Build Failure

2013-09-26 Thread Nuwan Dias

Since this is an addition of 2 new methods, I don't think it'll have an
impact unless someone tries to install new features to a product released
on an older chunk. Ex: If someone tries to install APIM (chunk2) features
on top of AS 5.2.0 (chunk1), then there'll be a problem. But in this kind
of situation we anyway have to ask people to install all kernel patches
since there are bug fixes anyway.

Thanks,
NuwanD.


On Fri, Sep 27, 2013 at 12:51 AM, Ajith Vitharana aji...@wso2.com wrote:




 On Fri, Sep 27, 2013 at 12:22 AM, Sumedha Rubasinghe sume...@wso2.comwrote:




 On Thu, Sep 26, 2013 at 11:57 PM, Ajith Vitharana aji...@wso2.comwrote:




 On Thu, Sep 26, 2013 at 11:35 PM, Lalaji Sureshika lal...@wso2.comwrote:

 Hi,

 From this fix, only a new method has added and no existing API method
 changes happened .Thus will this be cause any problem..?
 From APIM side,we need this fix,to integrate registry pagination in
 APIM [which has increased the performance of APIs loading in APIStore ] and
 this is a bug fix,which hasn't identified before chunk1 release out..


 Feature development and integrations can't avoid after chunk01 release,
 we have to face limitations or bugs.
 If the feature/bug is critical for the given release, we need some
 alternative  than preventing API changes.


 But this violates chunk release  strategy. Your features will not be
 compatible within platform.
 Please get Sameera's input on this.


 It is not practical to develop/integrate feature at  *chunk01* to
 compatible in all over the platform.

 Eg: How to test/integrate AM with pagination at the *chunk01* without
 proper AM build (or distributed setup) ???.
 At the chunk01 we did AS, IS but pagination didn't involved with those
 products.

 My suggestion is we should restrict the API changes once we finished at
 least  one release of the all the products from a given kernel release.
 Because kernel 4.2.0 based product releases are major releases that
 involves many new features and integrations, therefore nothing to wonder
 with API changes.

 Thanks
 Ajith.





 Thanks
 Ajith



 Thanks;



 On Thu, Sep 26, 2013 at 11:19 PM, Isuru Udana isu...@wso2.com wrote:

 Hi Lalaji,

 AFAIK api changes are not allowed for Kernel patches. We had a similar
 case for 4.1.3 and had to revert that at the last moment.



 On Thu, Sep 26, 2013 at 11:14 PM, Lalaji Sureshika lal...@wso2.comwrote:

 Hi Isuru,

 This fix was added by Ajith as part of the fix an issue on registry
 pagination with APIM integration.AFAIK,by this change a new getter/setter
 has added to PaginationContext class. Refer the jira [1]


 [1] https://wso2.org/jira/browse/REGISTRY-2003


 Thanks;


 On Thu, Sep 26, 2013 at 11:03 PM, Isuru Udana isu...@wso2.comwrote:

  I am getting the following build failure.

 [ERROR] Failed to execute goal
 org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
 (default-compile) on project org.wso2.carbon.registry.indexing: 
 Compilation
 failure
 [ERROR]
 /media/isuru/WSO2/svn/public/4.2.0/platform/4.2.0/components/registry/org.wso2.carbon.registry.indexing/4.2.1/src/main/java/org/wso2/carbon/registry/indexing/service/ContentBasedSearchService.java:[140,33]
 cannot find symbol
 [ERROR] symbol  : method setLength(int)
 [ERROR] location: class
 org.wso2.carbon.registry.core.pagination.PaginationContext
 [ERROR] - [Help 1]
 [ERROR]
 [ERROR] To see the full stack trace of the errors, re-run Maven with
 the -e switch.
 [ERROR] Re-run Maven using the -X switch to enable full debug
 logging.
 [ERROR]
 [ERROR] For more information about the errors and possible
 solutions, please read the following articles:
 [ERROR] [Help 1]
 http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
 [ERROR]
 [ERROR] After correcting the problems, you can resume the build with
 the command
 [ERROR]   mvn goals -rf :org.wso2.carbon.registry.indexing

 This got resolved after building kernel patch0001.
 Are we allow API changes in kernel patches now ?


 --
 *Isuru Udana*
 *
 *
 Senior *
 Software Engineer
 *
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/
 twitter: http://twitter.com/isudana

 ___
 Dev mailing list
 Dev@wso2.org
 http://wso2.org/cgi-bin/mailman/listinfo/dev




 --
 Lalaji Sureshika
  WSO2, Inc.;  http://wso2.com/
 email: lal...@wso2.com; cell: +94 71 608 6811
 blog: http://lalajisureshika.blogspot.com





 --
 *Isuru Udana*
 *
  *
 Senior *
 Software Engineer
 *
 WSO2 Inc.; http://wso2.com
 email: isu...@wso2.com cell: +94 77 3791887
 blog: http://mytecheye.blogspot.com/
 twitter: http://twitter.com/isudana




 --
 Lalaji Sureshika
 WSO2, Inc.;  http://wso2.com/
 email: lal...@wso2.com; cell: +94 71 608 6811
 blog: http://lalajisureshika.blogspot.com





 --
 Ajith Vitharana.
 WSO2 Inc. - http://wso2.org
 Email  :  aji...@wso2.com
 Mobile : +94772217350


 ___
 Dev

Re: [Dev] Chunk 02 Build Failure

On Fri, Sep 27, 2013 at 8:27 AM, Nuwan Dias nuw...@wso2.com wrote:

Since this is an addition of 2 new methods, I don't think it'll have an
impact unless someone tries to install new features to a product released
on an older chunk. Ex: If someone tries to install APIM (chunk2) features
on top of AS 5.2.0 (chunk1), then there'll be a problem. But in this kind
of situation we anyway have to ask people to install all kernel patches
since there are bug fixes anyway.

No. This has an impact for the next chunk releases.
If we are going to create a org.wso2.carbon.registry.indexing 4.2.2 or some
component use this api change in chunk-03 or later chunks. we always have
to build patch0001 even it is released.

Thanks,
NuwanD.

On Fri, Sep 27, 2013 at 12:51 AM, Ajith Vitharana aji...@wso2.com wrote:

On Fri, Sep 27, 2013 at 12:22 AM, Sumedha Rubasinghe sume...@wso2.comwrote:

On Thu, Sep 26, 2013 at 11:57 PM, Ajith Vitharana aji...@wso2.comwrote:

On Thu, Sep 26, 2013 at 11:35 PM, Lalaji Sureshika lal...@wso2.comwrote:

Hi,

From this fix, only a new method has added and no existing API method
changes happened .Thus will this be cause any problem..?
From APIM side,we need this fix,to integrate registry pagination in
APIM [which has increased the performance of APIs loading in APIStore ]
and
this is a bug fix,which hasn't identified before chunk1 release out..

Feature development and integrations can't avoid after chunk01 release,
we have to face limitations or bugs.
If the feature/bug is critical for the given release, we need some
alternative than preventing API changes.

But this violates chunk release strategy. Your features will not be
compatible within platform.
Please get Sameera's input on this.

It is not practical to develop/integrate feature at *chunk01* to
compatible in all over the platform.

Eg: How to test/integrate AM with pagination at the *chunk01* without
proper AM build (or distributed setup) ???.
At the chunk01 we did AS, IS but pagination didn't involved with those
products.

My suggestion is we should restrict the API changes once we finished at
least one release of the all the products from a given kernel release.
Because kernel 4.2.0 based product releases are major releases that
involves many new features and integrations, therefore nothing to wonder
with API changes.

Thanks
Ajith.

Thanks
Ajith

Thanks;

On Thu, Sep 26, 2013 at 11:19 PM, Isuru Udana isu...@wso2.com wrote:

Hi Lalaji,

AFAIK api changes are not allowed for Kernel patches. We had a
similar case for 4.1.3 and had to revert that at the last moment.

On Thu, Sep 26, 2013 at 11:14 PM, Lalaji Sureshika
lal...@wso2.comwrote:

Hi Isuru,

This fix was added by Ajith as part of the fix an issue on registry
pagination with APIM integration.AFAIK,by this change a new
getter/setter
has added to PaginationContext class. Refer the jira [1]

[1] https://wso2.org/jira/browse/REGISTRY-2003

Thanks;

On Thu, Sep 26, 2013 at 11:03 PM, Isuru Udana isu...@wso2.comwrote:

I am getting the following build failure.

[ERROR] Failed to execute goal
org.apache.maven.plugins:maven-compiler-plugin:2.3.2:compile
(default-compile) on project org.wso2.carbon.registry.indexing:
Compilation
failure
[ERROR]
/media/isuru/WSO2/svn/public/4.2.0/platform/4.2.0/components/registry/org.wso2.carbon.registry.indexing/4.2.1/src/main/java/org/wso2/carbon/registry/indexing/service/ContentBasedSearchService.java:[140,33]
cannot find symbol
[ERROR] symbol : method setLength(int)
[ERROR] location: class
org.wso2.carbon.registry.core.pagination.PaginationContext
[ERROR] - [Help 1]
[ERROR]
[ERROR] To see the full stack trace of the errors, re-run Maven
with the -e switch.
[ERROR] Re-run Maven using the -X switch to enable full debug
logging.
[ERROR]
[ERROR] For more information about the errors and possible
solutions, please read the following articles:
[ERROR] [Help 1]
http://cwiki.apache.org/confluence/display/MAVEN/MojoFailureException
[ERROR]
[ERROR] After correcting the problems, you can resume the build
with the command
[ERROR] mvn goals -rf :org.wso2.carbon.registry.indexing

This got resolved after building kernel patch0001.
Are we allow API changes in kernel patches now ?

--
*Isuru Udana*
*
*
Senior *
Software Engineer
*
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
twitter: http://twitter.com/isudana

___
Dev mailing list
Dev@wso2.org
http://wso2.org/cgi-bin/mailman/listinfo/dev

--
Lalaji Sureshika
WSO2, Inc.; http://wso2.com/
email: lal...@wso2.com; cell: +94 71 608 6811
blog: http://lalajisureshika.blogspot.com

--
*Isuru Udana*
*
*
Senior *
Software Engineer
*
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
twitter:

Re: [Dev] Chunk 02 Build Failure

2013-09-26 Thread Isuru Wimalasundera

Hi IsuruU

On Fri, Sep 27, 2013 at 8:49 AM, Isuru Udana isu...@wso2.com wrote:

On Fri, Sep 27, 2013 at 8:27 AM, Nuwan Dias nuw...@wso2.com wrote:

No. This has an impact for the next chunk releases.
If we are going to create a org.wso2.carbon.registry.indexing 4.2.2 or
some component use this api change in chunk-03 or later chunks. we always
have to build patch0001 even it is released.

I am not sure why that is necessary, its true you have to build patch0001
till its being released with the chunk02 in case if any component have a
dependency to the so called API change. but after the release AFAIK all the
Kernel fixes done in patch0001 should be reflected in the Nexus repo ,
right? or am I missing something here.

Thanks,
NuwanD.

On Fri, Sep 27, 2013 at 12:51 AM, Ajith Vitharana aji...@wso2.comwrote:

On Fri, Sep 27, 2013 at 12:22 AM, Sumedha Rubasinghe
sume...@wso2.comwrote:

On Thu, Sep 26, 2013 at 11:57 PM, Ajith Vitharana aji...@wso2.comwrote:

On Thu, Sep 26, 2013 at 11:35 PM, Lalaji Sureshika lal...@wso2.comwrote:

Hi,

Feature development and integrations can't avoid after chunk01
release, we have to face limitations or bugs.
If the feature/bug is critical for the given release, we need some
alternative than preventing API changes.

But this violates chunk release strategy. Your features will not be
compatible within platform.
Please get Sameera's input on this.

It is not practical to develop/integrate feature at *chunk01* to
compatible in all over the platform.

Eg: How to test/integrate AM with pagination at the *chunk01* without
proper AM build (or distributed setup) ???.
At the chunk01 we did AS, IS but pagination didn't involved with those
products.

Thanks
Ajith.

Thanks
Ajith

Thanks;

On Thu, Sep 26, 2013 at 11:19 PM, Isuru Udana isu...@wso2.comwrote:

Hi Lalaji,

AFAIK api changes are not allowed for Kernel patches. We had a
similar case for 4.1.3 and had to revert that at the last moment.

On Thu, Sep 26, 2013 at 11:14 PM, Lalaji Sureshika
lal...@wso2.comwrote:

Hi Isuru,

This fix was added by Ajith as part of the fix an issue on registry
pagination with APIM integration.AFAIK,by this change a new
getter/setter
has added to PaginationContext class. Refer the jira [1]

[1] https://wso2.org/jira/browse/REGISTRY-2003

Thanks;

On Thu, Sep 26, 2013 at 11:03 PM, Isuru Udana isu...@wso2.comwrote:

I am getting the following build failure.

This got resolved after building kernel patch0001.
Are we allow API changes in kernel patches now ?

--
*Isuru Udana*
*
*
Senior *
Software Engineer
*
WSO2 Inc.; http://wso2.com
email: isu...@wso2.com cell: +94 77 3791887
blog: http://mytecheye.blogspot.com/
twitter: http://twitter.com/isudana

___

Re: [Dev] Chunk 02 Build Failure