Moving away from wso2 maven repo

[Suresh Marru <sm...@apache.org>]

Changing subject and my 2 cents on this topic:

I agree it is fully acceptable and legally ok to rely on Apache V2 licensed (and other compatible license) software. But what will be useful for these kind of cases is to push the carbon and other dependencies to maven central. In a nutshell, the sooner the reliance on WSO2 maven repo [1] dependency is removed the better. I am lazyto search for right references, but I was previous told by incubation mentors to do this task before graduation. Not a blocker for graduation, but highly recommended. 

Since all the WSO2 dependencies are open source anyway, it is better to take advantage of the Sonatype OSS repository [2] , which publishes artifacts into maven central.

Its also encouraging to see the willingness to contribute back jclouds, axis2 like customizations to the parent projects.  A big + 1 for getting on to these also sooner than later.  My experience is unless we do these during these high momentum time, they linger for ever. 

Suresh
[1] - http://maven.wso2.org/nexus/content/groups/wso2-public/
[2] - https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide

On Jul 15, 2013, at 4:40 AM, Paul Fremantle <pa...@wso2.com> wrote:

> Completely agree! 
> 
> I didn't mean to imply that what was happening was a legal problem! 
> 
> Paul
> 
> 
> On 15 July 2013 09:33, Sanjiva Weerawarana <sa...@wso2.com> wrote:
> Just to be pedantic tho .. if the 3rd party stuff is Apache licensed and available in a public repo there's no problem with dependencies on them.
> 
> I do agree that there should be no need to have a modified version of an ASF project that we pick up from outside .. but Stratos depends on the Carbon kernel and Carbon kernel is an ASF licensed project run by WSO2. So those deps are legit - and yes eventually we should clean those up too as much as possible but (presumably) Carbon has good reason for those mods. I don't know the details at this level to explain .. I'll let someone else do it. If the mods can go into Axis2 great - but again that's a general improvement not a pre-req to getting this going.
> 
> Sanjiva.
> 
> 
> On Mon, Jul 15, 2013 at 1:25 PM, Paul Fremantle <pa...@wso2.com> wrote:
> I don't think we can rely on patches from a third-party project (speaking as Apache here not WSO2!). 
> 
> The simplest solution to this would be for WSO2 to contribute those patches back to Axis2 and for the Axis2 team to create an Axis2 release that we can use.
> In the meantime, perhaps WSO2 could push a working version into a maven repo so that the Stratos build works?
> 
> Paul
> 
> 
> On 15 July 2013 08:20, Isuru Perera <is...@wso2.com> wrote:
> Hi Alex,
> 
> Thanks for looking into build issues.
> 
> The Axis2 used in the Stratos comes from WSO2 Carbon Kernel. AFAIK, there are some modifications to Axis2 clustering. You can find details about  resetGroupManagementAgent from [1] and [2].
> 
> [1] https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.1.0/patches/patch0002/dependencies/axis2/modules/kernel/src/org/apache/axis2/clustering/ClusteringAgent.java
> [2] https://svn.wso2.org/repos/wso2/carbon/kernel/branches/4.1.0/patches/patch0002/dependencies/axis2/modules/clustering/src/org/apache/axis2/clustering/tribes/TribesClusteringAgent.java
> 
> 
> On Mon, Jul 15, 2013 at 12:17 PM, Alex Heneveld <al...@cloudsoftcorp.com> wrote:
> hi folks-
> 
> i've been trying to get the latest apache git [1] to build.  i know some of you have been working to make this happen so i thought i'd share my efforts.  i've fixed about a dozen problems [2] and gave up when i hit what looks like a dependency on an anonymous fork of axis2 referencing "clusteringAgent.resetGroupManagementAgent" (this doesn't exist in axis2).
> 
> i hope this helps.  for this to get any acceptance it really does need to get to the point where it builds PDQ !
> 
> best
> alex
> 
> 
> [1]  https://git-wip-us.apache.org/repos/asf/incubator-stratos.git
> [2]  https://github.com/ahgittin/stratos
> 
> 
> 
> -- 
> Isuru Perera
> Senior Software Engineer | WSO2, Inc. | http://wso2.com/
> Lean . Enterprise . Middleware
> 
> Twitter: http://twitter.com/chrishantha | LinkedIn: http://lk.linkedin.com/in/chrishantha/
> 
> 
> 
> -- 
> Paul Fremantle
> CTO and Co-Founder, WSO2
> OASIS WS-RX TC Co-chair, Apache Member
> 
> UK: +44 207 096 0336
> US: +1 646 595 7614
> 
> blog: http://pzf.fremantle.org
> twitter.com/pzfreo
> paul@wso2.com
> 
> wso2.com Lean Enterprise Middleware
> 
> Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions.
> 
> 
> 
> -- 
> Sanjiva Weerawarana, Ph.D.
> Founder, Chairman & CEO; WSO2, Inc.;  http://wso2.com/
> email: sanjiva@wso2.com; phone: +94 11 763 9614; cell: +94 77 787 6880 | +1 650 265 8311
> blog: http://sanjiva.weerawarana.org/
> 
> 
> Lean . Enterprise . Middleware
> 
> 
> 
> -- 
> Paul Fremantle
> CTO and Co-Founder, WSO2
> OASIS WS-RX TC Co-chair, Apache Member
> 
> UK: +44 207 096 0336
> US: +1 646 595 7614
> 
> blog: http://pzf.fremantle.org
> twitter.com/pzfreo
> paul@wso2.com
> 
> wso2.com Lean Enterprise Middleware
> 
> Disclaimer: This communication may contain privileged or other confidential information and is intended exclusively for the addressee/s. If you are not the intended recipient/s, or believe that you may have received this communication in error, please reply to the sender indicating that fact and delete the copy you received and in addition, you should not print, copy, retransmit, disseminate, or otherwise use the information contained in this communication. Internet communications cannot be guaranteed to be timely, secure, error or virus-free. The sender does not accept liability for any errors or omissions.