You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by Lahiru Sandaruwan <la...@wso2.com> on 2013/07/11 22:04:23 UTC
Jclouds dependancies
Hi,
Shall we bring dependency directory to the code base. We need a place to
have followings,
org.jclouds.api:openstack-nova:jar:1.5.0-beta.5.wso2v1,
org.jclouds.api:openstack-keystone:jar:1.5.0-beta.5.wso2v1,
org.jclouds.api:openstack-nova:jar:1.5.0-beta.5.wso2v1
Thanks.
--
--
Lahiru Sandaruwan
Software Engineer,
Platform Technologies,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
email: lahirus@wso2.com cell: (+94) 773 325 954
blog: http://lahiruwrites.blogspot.com/
twitter: http://twitter.com/lahirus
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
Re: Jclouds dependancies
Posted by Supun Kamburugamuva <su...@gmail.com>.
I think the mentioned jars are OSGI bundles. If I'm correct only a pom will
be added for each jar and this pom will re-package the jclouds jar in to an
OSGI bundle.
Thanks,
Supun..
On Thu, Jul 11, 2013 at 4:11 PM, Chip Childers <ch...@sungard.com>wrote:
> On Fri, Jul 12, 2013 at 01:34:23AM +0530, Lahiru Sandaruwan wrote:
> > Hi,
> >
> > Shall we bring dependency directory to the code base. We need a place to
> > have followings,
> >
> > org.jclouds.api:openstack-nova:jar:1.5.0-beta.5.wso2v1,
> > org.jclouds.api:openstack-keystone:jar:1.5.0-beta.5.wso2v1,
> > org.jclouds.api:openstack-nova:jar:1.5.0-beta.5.wso2v1
> >
>
> Are you suggesting adding the jar files into the git repo?
>
> If so, I don't recommend it. Apache releases are "source only", so if
> those are in the repo it will require removing them from the source
> tarball. Is there any reason that you can't depend on them in the
> project POMs?
>
> Keep in mind the jclouds is another podling within the incubator, so if
> you need anything from them I'd bet they could help.
>
> -chip
>
--
Supun Kamburugamuva
Member, Apache Software Foundation; http://www.apache.org
E-mail: supun06@gmail.com; Mobile: +1 812 369 6762
Blog: http://supunk.blogspot.com
Re: Jclouds dependancies
Posted by Lahiru Sandaruwan <la...@wso2.com>.
In fact, it is not only what i mentioned, there are several such components
from Jclouds.
Thanks.
On Fri, Jul 12, 2013 at 1:52 AM, Lahiru Sandaruwan <la...@wso2.com> wrote:
> Hi all,
>
> What we have is complete source which is customized.
>
> Thanks.
>
>
> On Fri, Jul 12, 2013 at 1:45 AM, Chip Childers <ch...@sungard.com>wrote:
>
>> On Thu, Jul 11, 2013 at 04:11:29PM -0400, Chip Childers wrote:
>> > On Fri, Jul 12, 2013 at 01:34:23AM +0530, Lahiru Sandaruwan wrote:
>> > > Hi,
>> > >
>> > > Shall we bring dependency directory to the code base. We need a place
>> to
>> > > have followings,
>> > >
>> > > org.jclouds.api:openstack-nova:jar:1.5.0-beta.5.wso2v1,
>> > > org.jclouds.api:openstack-keystone:jar:1.5.0-beta.5.wso2v1,
>> > > org.jclouds.api:openstack-nova:jar:1.5.0-beta.5.wso2v1
>> > >
>> >
>> > Are you suggesting adding the jar files into the git repo?
>> >
>> > If so, I don't recommend it. Apache releases are "source only", so if
>> > those are in the repo it will require removing them from the source
>> > tarball. Is there any reason that you can't depend on them in the
>> > project POMs?
>> >
>> > Keep in mind the jclouds is another podling within the incubator, so if
>> > you need anything from them I'd bet they could help.
>> >
>> > -chip
>>
>> And just to provide a link to explain what I meant by "source only", see
>> the following paragraph that's at [1].
>>
>> """
>> The Apache Software Foundation produces open source software. All
>> releases are in the form of the source materials needed to make changes
>> to the software being released. In some cases, binary/bytecode packages
>> are also produced as a convenience to users that might not have the
>> appropriate tools to build a compiled version of the source. In all such
>> cases, the binary/bytecode package must have the same version number as
>> the source release and may only add binary/bytecode files that are the
>> result of compiling that version of the source code release.
>> """
>>
>> [1] http://www.apache.org/dev/release.html#what
>>
>
>
>
> --
> --
> Lahiru Sandaruwan
> Software Engineer,
> Platform Technologies,
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> email: lahirus@wso2.com cell: (+94) 773 325 954
> blog: http://lahiruwrites.blogspot.com/
> twitter: http://twitter.com/lahirus
> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>
>
--
--
Lahiru Sandaruwan
Software Engineer,
Platform Technologies,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
email: lahirus@wso2.com cell: (+94) 773 325 954
blog: http://lahiruwrites.blogspot.com/
twitter: http://twitter.com/lahirus
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
Re: Jclouds dependancies
Posted by Suresh Marru <sm...@apache.org>.
On Jul 12, 2013, at 1:28 AM, Lahiru Sandaruwan <la...@wso2.com> wrote:
> Don't we have these jars deployed to the nexus repo ?!
>
> Not yet. I also think this would be good enough until we move to Apache Jclouds. We have to do that fast to get the build stable.
> I'll look into it.
> Also our patches are not given to Jclouds yet. We need to figure that out before we move to Apache Jclouds.
Its fine to get the build stable by adding a 3rd-party repo, but its highly recommended to rely entirely on maven central for all dependencies. As you all might know any open source jars can be published to maven central through the sonatype OSS repo - https://docs.sonatype.org/display/Repository/Sonatype+OSS+Maven+Repository+Usage+Guide
Suresh
Re: Jclouds dependancies
Posted by Lahiru Sandaruwan <la...@wso2.com>.
On Fri, Jul 12, 2013 at 10:24 AM, Shariq Muhammed <sh...@wso2.com> wrote:
> On Fri, Jul 12, 2013 at 9:29 AM, Lahiru Sandaruwan <la...@wso2.com>wrote:
>
>>
>>
>>
>> On Fri, Jul 12, 2013 at 7:22 AM, Lakmal Warusawithana <la...@wso2.com>wrote:
>>
>>> AFAIK those changes already fixed in newest version of jcloud. Anyway
>>> we need to go to jcloud apache version after our build stable.
>>>
>>
>> But we still maintain the code and depend on that. So until refactoring
>> is done, we should find a way to keep them.
>>
>
> Don't we have these jars deployed to the nexus repo ?!
>
Not yet. I also think this would be good enough until we move to Apache
Jclouds. We have to do that fast to get the build stable.
I'll look into it.
Also our patches are not given to Jclouds yet. We need to figure that out
before we move to Apache Jclouds.
Thanks.
>
>>>
>>> On Fri, Jul 12, 2013 at 2:08 AM, Lahiru Sandaruwan <la...@wso2.com>wrote:
>>>
>>>>
>>>>
>>>>
>>>> On Fri, Jul 12, 2013 at 2:05 AM, Suresh Marru <sm...@apache.org>wrote:
>>>>
>>>>> On Jul 11, 2013, at 4:22 PM, Lahiru Sandaruwan <la...@wso2.com>
>>>>> wrote:
>>>>>
>>>>> > Hi all,
>>>>> >
>>>>> > What we have is complete source which is customized.
>>>>>
>>>>> Orthogonal to this discussion, can you guys engage with jcloudscommunity and contribute back to JClouds next release?
>>>>>
>>>> +1...
>>>>
>>>>>
>>>>> Suresh
>>>>>
>>>>> >
>>>>> > Thanks.
>>>>> >
>>>>> >
>>>>> > On Fri, Jul 12, 2013 at 1:45 AM, Chip Childers <
>>>>> chip.childers@sungard.com> wrote:
>>>>> > On Thu, Jul 11, 2013 at 04:11:29PM -0400, Chip Childers wrote:
>>>>> > > On Fri, Jul 12, 2013 at 01:34:23AM +0530, Lahiru Sandaruwan wrote:
>>>>> > > > Hi,
>>>>> > > >
>>>>> > > > Shall we bring dependency directory to the code base. We need a
>>>>> place to
>>>>> > > > have followings,
>>>>> > > >
>>>>> > > > org.jclouds.api:openstack-nova:jar:1.5.0-beta.5.wso2v1,
>>>>> > > > org.jclouds.api:openstack-keystone:jar:1.5.0-beta.5.wso2v1,
>>>>> > > > org.jclouds.api:openstack-nova:jar:1.5.0-beta.5.wso2v1
>>>>> > > >
>>>>> > >
>>>>> > > Are you suggesting adding the jar files into the git repo?
>>>>> > >
>>>>> > > If so, I don't recommend it. Apache releases are "source only",
>>>>> so if
>>>>> > > those are in the repo it will require removing them from the
>>>>> source
>>>>> > > tarball. Is there any reason that you can't depend on them in the
>>>>> > > project POMs?
>>>>> > >
>>>>> > > Keep in mind the jclouds is another podling within the incubator,
>>>>> so if
>>>>> > > you need anything from them I'd bet they could help.
>>>>> > >
>>>>> > > -chip
>>>>> >
>>>>> > And just to provide a link to explain what I meant by "source only",
>>>>> see
>>>>> > the following paragraph that's at [1].
>>>>> >
>>>>> > """
>>>>> > The Apache Software Foundation produces open source software. All
>>>>> > releases are in the form of the source materials needed to make
>>>>> changes
>>>>> > to the software being released. In some cases, binary/bytecodepackages
>>>>> > are also produced as a convenience to users that might not have the
>>>>> > appropriate tools to build a compiled version of the source. In all
>>>>> such
>>>>> > cases, the binary/bytecode package must have the same version
>>>>> number as
>>>>> > the source release and may only add binary/bytecode files that are
>>>>> the
>>>>> > result of compiling that version of the source code release.
>>>>> > """
>>>>> >
>>>>> > [1] http://www.apache.org/dev/release.html#what
>>>>> >
>>>>> >
>>>>> >
>>>>> > --
>>>>> > --
>>>>> > Lahiru Sandaruwan
>>>>> > Software Engineer,
>>>>> > Platform Technologies,
>>>>> > WSO2 Inc., http://wso2.com
>>>>> > lean.enterprise.middleware
>>>>> >
>>>>> > email: lahirus@wso2.com cell: (+94) 773 325 954
>>>>> > blog: http://lahiruwrites.blogspot.com/
>>>>> > twitter: http://twitter.com/lahirus
>>>>> > linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>> >
>>>>>
>>>>>
>>>>
>>>>
>>>> --
>>>> --
>>>> Lahiru Sandaruwan
>>>> Software Engineer,
>>>> Platform Technologies,
>>>> WSO2 Inc., http://wso2.com
>>>> lean.enterprise.middleware
>>>>
>>>> email: lahirus@wso2.com cell: (+94) 773 325 954
>>>> blog: http://lahiruwrites.blogspot.com/
>>>> twitter: http://twitter.com/lahirus
>>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>>
>>>>
>>>
>>>
>>> --
>>> Lakmal Warusawithana
>>> Software Architect; WSO2 Inc.
>>> Mobile : +94714289692
>>> Blog : http://lakmalsview.blogspot.com/
>>>
>>>
>>
>>
>> --
>> --
>> Lahiru Sandaruwan
>> Software Engineer,
>> Platform Technologies,
>> WSO2 Inc., http://wso2.com
>> lean.enterprise.middleware
>>
>> email: lahirus@wso2.com cell: (+94) 773 325 954
>> blog: http://lahiruwrites.blogspot.com/
>> twitter: http://twitter.com/lahirus
>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>
>>
>
>
> --
> Thanks,
> Shariq.
> Phone: +94 777 202 225
>
--
--
Lahiru Sandaruwan
Software Engineer,
Platform Technologies,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
email: lahirus@wso2.com cell: (+94) 773 325 954
blog: http://lahiruwrites.blogspot.com/
twitter: http://twitter.com/lahirus
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
Re: Jclouds dependancies
Posted by Shariq Muhammed <sh...@wso2.com>.
On Fri, Jul 12, 2013 at 9:29 AM, Lahiru Sandaruwan <la...@wso2.com> wrote:
>
>
>
> On Fri, Jul 12, 2013 at 7:22 AM, Lakmal Warusawithana <la...@wso2.com>wrote:
>
>> AFAIK those changes already fixed in newest version of jcloud. Anyway we
>> need to go to jcloud apache version after our build stable.
>>
>
> But we still maintain the code and depend on that. So until refactoring
> is done, we should find a way to keep them.
>
Don't we have these jars deployed to the nexus repo ?!
>
>>
>> On Fri, Jul 12, 2013 at 2:08 AM, Lahiru Sandaruwan <la...@wso2.com>wrote:
>>
>>>
>>>
>>>
>>> On Fri, Jul 12, 2013 at 2:05 AM, Suresh Marru <sm...@apache.org> wrote:
>>>
>>>> On Jul 11, 2013, at 4:22 PM, Lahiru Sandaruwan <la...@wso2.com>
>>>> wrote:
>>>>
>>>> > Hi all,
>>>> >
>>>> > What we have is complete source which is customized.
>>>>
>>>> Orthogonal to this discussion, can you guys engage with jcloudscommunity and contribute back to JClouds next release?
>>>>
>>> +1...
>>>
>>>>
>>>> Suresh
>>>>
>>>> >
>>>> > Thanks.
>>>> >
>>>> >
>>>> > On Fri, Jul 12, 2013 at 1:45 AM, Chip Childers <
>>>> chip.childers@sungard.com> wrote:
>>>> > On Thu, Jul 11, 2013 at 04:11:29PM -0400, Chip Childers wrote:
>>>> > > On Fri, Jul 12, 2013 at 01:34:23AM +0530, Lahiru Sandaruwan wrote:
>>>> > > > Hi,
>>>> > > >
>>>> > > > Shall we bring dependency directory to the code base. We need a
>>>> place to
>>>> > > > have followings,
>>>> > > >
>>>> > > > org.jclouds.api:openstack-nova:jar:1.5.0-beta.5.wso2v1,
>>>> > > > org.jclouds.api:openstack-keystone:jar:1.5.0-beta.5.wso2v1,
>>>> > > > org.jclouds.api:openstack-nova:jar:1.5.0-beta.5.wso2v1
>>>> > > >
>>>> > >
>>>> > > Are you suggesting adding the jar files into the git repo?
>>>> > >
>>>> > > If so, I don't recommend it. Apache releases are "source only", so
>>>> if
>>>> > > those are in the repo it will require removing them from the source
>>>> > > tarball. Is there any reason that you can't depend on them in the
>>>> > > project POMs?
>>>> > >
>>>> > > Keep in mind the jclouds is another podling within the incubator,
>>>> so if
>>>> > > you need anything from them I'd bet they could help.
>>>> > >
>>>> > > -chip
>>>> >
>>>> > And just to provide a link to explain what I meant by "source only",
>>>> see
>>>> > the following paragraph that's at [1].
>>>> >
>>>> > """
>>>> > The Apache Software Foundation produces open source software. All
>>>> > releases are in the form of the source materials needed to make
>>>> changes
>>>> > to the software being released. In some cases, binary/bytecodepackages
>>>> > are also produced as a convenience to users that might not have the
>>>> > appropriate tools to build a compiled version of the source. In all
>>>> such
>>>> > cases, the binary/bytecode package must have the same version number
>>>> as
>>>> > the source release and may only add binary/bytecode files that are
>>>> the
>>>> > result of compiling that version of the source code release.
>>>> > """
>>>> >
>>>> > [1] http://www.apache.org/dev/release.html#what
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> > --
>>>> > Lahiru Sandaruwan
>>>> > Software Engineer,
>>>> > Platform Technologies,
>>>> > WSO2 Inc., http://wso2.com
>>>> > lean.enterprise.middleware
>>>> >
>>>> > email: lahirus@wso2.com cell: (+94) 773 325 954
>>>> > blog: http://lahiruwrites.blogspot.com/
>>>> > twitter: http://twitter.com/lahirus
>>>> > linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>> >
>>>>
>>>>
>>>
>>>
>>> --
>>> --
>>> Lahiru Sandaruwan
>>> Software Engineer,
>>> Platform Technologies,
>>> WSO2 Inc., http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> email: lahirus@wso2.com cell: (+94) 773 325 954
>>> blog: http://lahiruwrites.blogspot.com/
>>> twitter: http://twitter.com/lahirus
>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>
>>>
>>
>>
>> --
>> Lakmal Warusawithana
>> Software Architect; WSO2 Inc.
>> Mobile : +94714289692
>> Blog : http://lakmalsview.blogspot.com/
>>
>>
>
>
> --
> --
> Lahiru Sandaruwan
> Software Engineer,
> Platform Technologies,
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> email: lahirus@wso2.com cell: (+94) 773 325 954
> blog: http://lahiruwrites.blogspot.com/
> twitter: http://twitter.com/lahirus
> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>
>
--
Thanks,
Shariq.
Phone: +94 777 202 225
Re: Jclouds dependancies
Posted by Lahiru Sandaruwan <la...@wso2.com>.
On Fri, Jul 12, 2013 at 7:22 AM, Lakmal Warusawithana <la...@wso2.com>wrote:
> AFAIK those changes already fixed in newest version of jcloud. Anyway we
> need to go to jcloud apache version after our build stable.
>
But we still maintain the code and depend on that. So until refactoring is
done, we should find a way to keep them.
>
>
> On Fri, Jul 12, 2013 at 2:08 AM, Lahiru Sandaruwan <la...@wso2.com>wrote:
>
>>
>>
>>
>> On Fri, Jul 12, 2013 at 2:05 AM, Suresh Marru <sm...@apache.org> wrote:
>>
>>> On Jul 11, 2013, at 4:22 PM, Lahiru Sandaruwan <la...@wso2.com> wrote:
>>>
>>> > Hi all,
>>> >
>>> > What we have is complete source which is customized.
>>>
>>> Orthogonal to this discussion, can you guys engage with jclouds
>>> community and contribute back to JClouds next release?
>>>
>> +1...
>>
>>>
>>> Suresh
>>>
>>> >
>>> > Thanks.
>>> >
>>> >
>>> > On Fri, Jul 12, 2013 at 1:45 AM, Chip Childers <
>>> chip.childers@sungard.com> wrote:
>>> > On Thu, Jul 11, 2013 at 04:11:29PM -0400, Chip Childers wrote:
>>> > > On Fri, Jul 12, 2013 at 01:34:23AM +0530, Lahiru Sandaruwan wrote:
>>> > > > Hi,
>>> > > >
>>> > > > Shall we bring dependency directory to the code base. We need a
>>> place to
>>> > > > have followings,
>>> > > >
>>> > > > org.jclouds.api:openstack-nova:jar:1.5.0-beta.5.wso2v1,
>>> > > > org.jclouds.api:openstack-keystone:jar:1.5.0-beta.5.wso2v1,
>>> > > > org.jclouds.api:openstack-nova:jar:1.5.0-beta.5.wso2v1
>>> > > >
>>> > >
>>> > > Are you suggesting adding the jar files into the git repo?
>>> > >
>>> > > If so, I don't recommend it. Apache releases are "source only", so
>>> if
>>> > > those are in the repo it will require removing them from the source
>>> > > tarball. Is there any reason that you can't depend on them in the
>>> > > project POMs?
>>> > >
>>> > > Keep in mind the jclouds is another podling within the incubator, so
>>> if
>>> > > you need anything from them I'd bet they could help.
>>> > >
>>> > > -chip
>>> >
>>> > And just to provide a link to explain what I meant by "source only",
>>> see
>>> > the following paragraph that's at [1].
>>> >
>>> > """
>>> > The Apache Software Foundation produces open source software. All
>>> > releases are in the form of the source materials needed to make changes
>>> > to the software being released. In some cases, binary/bytecode packages
>>> > are also produced as a convenience to users that might not have the
>>> > appropriate tools to build a compiled version of the source. In all
>>> such
>>> > cases, the binary/bytecode package must have the same version number as
>>> > the source release and may only add binary/bytecode files that are the
>>> > result of compiling that version of the source code release.
>>> > """
>>> >
>>> > [1] http://www.apache.org/dev/release.html#what
>>> >
>>> >
>>> >
>>> > --
>>> > --
>>> > Lahiru Sandaruwan
>>> > Software Engineer,
>>> > Platform Technologies,
>>> > WSO2 Inc., http://wso2.com
>>> > lean.enterprise.middleware
>>> >
>>> > email: lahirus@wso2.com cell: (+94) 773 325 954
>>> > blog: http://lahiruwrites.blogspot.com/
>>> > twitter: http://twitter.com/lahirus
>>> > linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>> >
>>>
>>>
>>
>>
>> --
>> --
>> Lahiru Sandaruwan
>> Software Engineer,
>> Platform Technologies,
>> WSO2 Inc., http://wso2.com
>> lean.enterprise.middleware
>>
>> email: lahirus@wso2.com cell: (+94) 773 325 954
>> blog: http://lahiruwrites.blogspot.com/
>> twitter: http://twitter.com/lahirus
>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>
>>
>
>
> --
> Lakmal Warusawithana
> Software Architect; WSO2 Inc.
> Mobile : +94714289692
> Blog : http://lakmalsview.blogspot.com/
>
>
--
--
Lahiru Sandaruwan
Software Engineer,
Platform Technologies,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
email: lahirus@wso2.com cell: (+94) 773 325 954
blog: http://lahiruwrites.blogspot.com/
twitter: http://twitter.com/lahirus
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
Re: Jclouds dependancies
Posted by Suresh Marru <sm...@apache.org>.
On Jul 12, 2013, at 1:49 AM, Nirmal Fernando <ni...@gmail.com> wrote:
> On Fri, Jul 12, 2013 at 8:40 AM, Pradeep Fernando <pr...@gmail.com> wrote:
>
> Hi,
>
> On Fri, Jul 12, 2013 at 7:22 AM, Lakmal Warusawithana <la...@wso2.com> wrote:
> AFAIK those changes already fixed in newest version of jcloud. Anyway we need to go to jcloud apache version after our build stable.
> +1. We shouldn't maintain any source, which doesn't belong to apache stratos. If we have an OSGi requirement,(if we need bundles) we better ask it from the jclouds community as well...
>
> jclouds stuff are already OSGi bundles, we did few code modifications to tackle some issues, hence we created our own dependency. As we were in a hurry, we couldn't contribute to the jclouds, but now the time has come to contribute the fixes back to jclouds.
>
> All the fixes we did, are not there in the latest jclouds (eg: vCloud Director 1.5 support etc.).
@Nirmal, I have seen you hang around in jclouds lists, so it will be good to get these additions to the trunk so they can be considered before for the 1.7 release.
Suresh
>
> On Fri, Jul 12, 2013 at 2:08 AM, Lahiru Sandaruwan <la...@wso2.com> wrote:
>
>
>
> On Fri, Jul 12, 2013 at 2:05 AM, Suresh Marru <sm...@apache.org> wrote:
> On Jul 11, 2013, at 4:22 PM, Lahiru Sandaruwan <la...@wso2.com> wrote:
>
> > Hi all,
> >
> > What we have is complete source which is customized.
>
> Orthogonal to this discussion, can you guys engage with jclouds community and contribute back to JClouds next release?
> +1...
>
> Suresh
>
> >
> > Thanks.
> >
> >
> > On Fri, Jul 12, 2013 at 1:45 AM, Chip Childers <ch...@sungard.com> wrote:
> > On Thu, Jul 11, 2013 at 04:11:29PM -0400, Chip Childers wrote:
> > > On Fri, Jul 12, 2013 at 01:34:23AM +0530, Lahiru Sandaruwan wrote:
> > > > Hi,
> > > >
> > > > Shall we bring dependency directory to the code base. We need a place to
> > > > have followings,
> > > >
> > > > org.jclouds.api:openstack-nova:jar:1.5.0-beta.5.wso2v1,
> > > > org.jclouds.api:openstack-keystone:jar:1.5.0-beta.5.wso2v1,
> > > > org.jclouds.api:openstack-nova:jar:1.5.0-beta.5.wso2v1
> > > >
> > >
> > > Are you suggesting adding the jar files into the git repo?
> > >
> > > If so, I don't recommend it. Apache releases are "source only", so if
> > > those are in the repo it will require removing them from the source
> > > tarball. Is there any reason that you can't depend on them in the
> > > project POMs?
> > >
> > > Keep in mind the jclouds is another podling within the incubator, so if
> > > you need anything from them I'd bet they could help.
> > >
> > > -chip
> >
> > And just to provide a link to explain what I meant by "source only", see
> > the following paragraph that's at [1].
> >
> > """
> > The Apache Software Foundation produces open source software. All
> > releases are in the form of the source materials needed to make changes
> > to the software being released. In some cases, binary/bytecode packages
> > are also produced as a convenience to users that might not have the
> > appropriate tools to build a compiled version of the source. In all such
> > cases, the binary/bytecode package must have the same version number as
> > the source release and may only add binary/bytecode files that are the
> > result of compiling that version of the source code release.
> > """
> >
> > [1] http://www.apache.org/dev/release.html#what
> >
> >
> >
> > --
> > --
> > Lahiru Sandaruwan
> > Software Engineer,
> > Platform Technologies,
> > WSO2 Inc., http://wso2.com
> > lean.enterprise.middleware
> >
> > email: lahirus@wso2.com cell: (+94) 773 325 954
> > blog: http://lahiruwrites.blogspot.com/
> > twitter: http://twitter.com/lahirus
> > linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
> >
>
>
>
>
> --
> --
> Lahiru Sandaruwan
> Software Engineer,
> Platform Technologies,
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> email: lahirus@wso2.com cell: (+94) 773 325 954
> blog: http://lahiruwrites.blogspot.com/
> twitter: http://twitter.com/lahirus
> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>
>
>
>
> --
> Lakmal Warusawithana
> Software Architect; WSO2 Inc.
> Mobile : +94714289692
> Blog : http://lakmalsview.blogspot.com/
>
>
>
>
> --
> Pradeep Fernando.
> http://pradeepfernando.blogspot.com/
>
>
>
> --
> Best Regards,
> Nirmal
>
> C.S.Nirmal J. Fernando
> Senior Software Engineer,
> WSO2 Inc.
>
> Blog: http://nirmalfdo.blogspot.com/
Re: Jclouds dependancies
Posted by Nirmal Fernando <ni...@gmail.com>.
On Fri, Jul 12, 2013 at 8:40 AM, Pradeep Fernando <pr...@gmail.com>wrote:
>
> Hi,
>
> On Fri, Jul 12, 2013 at 7:22 AM, Lakmal Warusawithana <la...@wso2.com>wrote:
>
>> AFAIK those changes already fixed in newest version of jcloud. Anyway we
>> need to go to jcloud apache version after our build stable.
>>
> +1. We shouldn't maintain any source, which doesn't belong to apache
> stratos. If we have an OSGi requirement,(if we need bundles) we better ask
> it from the jclouds community as well...
>
jclouds stuff are already OSGi bundles, we did few code modifications to
tackle some issues, hence we created our own dependency. As we were in a
hurry, we couldn't contribute to the jclouds, but now the time has come to
contribute the fixes back to jclouds.
All the fixes we did, are not there in the latest jclouds (eg: vCloud
Director 1.5 support etc.).
>
>
>>
>>
>> On Fri, Jul 12, 2013 at 2:08 AM, Lahiru Sandaruwan <la...@wso2.com>wrote:
>>
>>>
>>>
>>>
>>> On Fri, Jul 12, 2013 at 2:05 AM, Suresh Marru <sm...@apache.org> wrote:
>>>
>>>> On Jul 11, 2013, at 4:22 PM, Lahiru Sandaruwan <la...@wso2.com>
>>>> wrote:
>>>>
>>>> > Hi all,
>>>> >
>>>> > What we have is complete source which is customized.
>>>>
>>>> Orthogonal to this discussion, can you guys engage with jclouds
>>>> community and contribute back to JClouds next release?
>>>>
>>> +1...
>>>
>>>>
>>>> Suresh
>>>>
>>>> >
>>>> > Thanks.
>>>> >
>>>> >
>>>> > On Fri, Jul 12, 2013 at 1:45 AM, Chip Childers <
>>>> chip.childers@sungard.com> wrote:
>>>> > On Thu, Jul 11, 2013 at 04:11:29PM -0400, Chip Childers wrote:
>>>> > > On Fri, Jul 12, 2013 at 01:34:23AM +0530, Lahiru Sandaruwan wrote:
>>>> > > > Hi,
>>>> > > >
>>>> > > > Shall we bring dependency directory to the code base. We need a
>>>> place to
>>>> > > > have followings,
>>>> > > >
>>>> > > > org.jclouds.api:openstack-nova:jar:1.5.0-beta.5.wso2v1,
>>>> > > > org.jclouds.api:openstack-keystone:jar:1.5.0-beta.5.wso2v1,
>>>> > > > org.jclouds.api:openstack-nova:jar:1.5.0-beta.5.wso2v1
>>>> > > >
>>>> > >
>>>> > > Are you suggesting adding the jar files into the git repo?
>>>> > >
>>>> > > If so, I don't recommend it. Apache releases are "source only", so
>>>> if
>>>> > > those are in the repo it will require removing them from the source
>>>> > > tarball. Is there any reason that you can't depend on them in the
>>>> > > project POMs?
>>>> > >
>>>> > > Keep in mind the jclouds is another podling within the incubator,
>>>> so if
>>>> > > you need anything from them I'd bet they could help.
>>>> > >
>>>> > > -chip
>>>> >
>>>> > And just to provide a link to explain what I meant by "source only",
>>>> see
>>>> > the following paragraph that's at [1].
>>>> >
>>>> > """
>>>> > The Apache Software Foundation produces open source software. All
>>>> > releases are in the form of the source materials needed to make
>>>> changes
>>>> > to the software being released. In some cases, binary/bytecode
>>>> packages
>>>> > are also produced as a convenience to users that might not have the
>>>> > appropriate tools to build a compiled version of the source. In all
>>>> such
>>>> > cases, the binary/bytecode package must have the same version number
>>>> as
>>>> > the source release and may only add binary/bytecode files that are the
>>>> > result of compiling that version of the source code release.
>>>> > """
>>>> >
>>>> > [1] http://www.apache.org/dev/release.html#what
>>>> >
>>>> >
>>>> >
>>>> > --
>>>> > --
>>>> > Lahiru Sandaruwan
>>>> > Software Engineer,
>>>> > Platform Technologies,
>>>> > WSO2 Inc., http://wso2.com
>>>> > lean.enterprise.middleware
>>>> >
>>>> > email: lahirus@wso2.com cell: (+94) 773 325 954
>>>> > blog: http://lahiruwrites.blogspot.com/
>>>> > twitter: http://twitter.com/lahirus
>>>> > linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>> >
>>>>
>>>>
>>>
>>>
>>> --
>>> --
>>> Lahiru Sandaruwan
>>> Software Engineer,
>>> Platform Technologies,
>>> WSO2 Inc., http://wso2.com
>>> lean.enterprise.middleware
>>>
>>> email: lahirus@wso2.com cell: (+94) 773 325 954
>>> blog: http://lahiruwrites.blogspot.com/
>>> twitter: http://twitter.com/lahirus
>>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>>
>>>
>>
>>
>> --
>> Lakmal Warusawithana
>> Software Architect; WSO2 Inc.
>> Mobile : +94714289692
>> Blog : http://lakmalsview.blogspot.com/
>>
>>
>
>
> --
> Pradeep Fernando.
> http://pradeepfernando.blogspot.com/
>
--
Best Regards,
Nirmal
C.S.Nirmal J. Fernando
Senior Software Engineer,
WSO2 Inc.
Blog: http://nirmalfdo.blogspot.com/
Re: Jclouds dependancies
Posted by Pradeep Fernando <pr...@gmail.com>.
Hi,
On Fri, Jul 12, 2013 at 7:22 AM, Lakmal Warusawithana <la...@wso2.com>wrote:
> AFAIK those changes already fixed in newest version of jcloud. Anyway we
> need to go to jcloud apache version after our build stable.
>
+1. We shouldn't maintain any source, which doesn't belong to apache
stratos. If we have an OSGi requirement,(if we need bundles) we better ask
it from the jclouds community as well...
>
>
> On Fri, Jul 12, 2013 at 2:08 AM, Lahiru Sandaruwan <la...@wso2.com>wrote:
>
>>
>>
>>
>> On Fri, Jul 12, 2013 at 2:05 AM, Suresh Marru <sm...@apache.org> wrote:
>>
>>> On Jul 11, 2013, at 4:22 PM, Lahiru Sandaruwan <la...@wso2.com> wrote:
>>>
>>> > Hi all,
>>> >
>>> > What we have is complete source which is customized.
>>>
>>> Orthogonal to this discussion, can you guys engage with jclouds
>>> community and contribute back to JClouds next release?
>>>
>> +1...
>>
>>>
>>> Suresh
>>>
>>> >
>>> > Thanks.
>>> >
>>> >
>>> > On Fri, Jul 12, 2013 at 1:45 AM, Chip Childers <
>>> chip.childers@sungard.com> wrote:
>>> > On Thu, Jul 11, 2013 at 04:11:29PM -0400, Chip Childers wrote:
>>> > > On Fri, Jul 12, 2013 at 01:34:23AM +0530, Lahiru Sandaruwan wrote:
>>> > > > Hi,
>>> > > >
>>> > > > Shall we bring dependency directory to the code base. We need a
>>> place to
>>> > > > have followings,
>>> > > >
>>> > > > org.jclouds.api:openstack-nova:jar:1.5.0-beta.5.wso2v1,
>>> > > > org.jclouds.api:openstack-keystone:jar:1.5.0-beta.5.wso2v1,
>>> > > > org.jclouds.api:openstack-nova:jar:1.5.0-beta.5.wso2v1
>>> > > >
>>> > >
>>> > > Are you suggesting adding the jar files into the git repo?
>>> > >
>>> > > If so, I don't recommend it. Apache releases are "source only", so
>>> if
>>> > > those are in the repo it will require removing them from the source
>>> > > tarball. Is there any reason that you can't depend on them in the
>>> > > project POMs?
>>> > >
>>> > > Keep in mind the jclouds is another podling within the incubator, so
>>> if
>>> > > you need anything from them I'd bet they could help.
>>> > >
>>> > > -chip
>>> >
>>> > And just to provide a link to explain what I meant by "source only",
>>> see
>>> > the following paragraph that's at [1].
>>> >
>>> > """
>>> > The Apache Software Foundation produces open source software. All
>>> > releases are in the form of the source materials needed to make changes
>>> > to the software being released. In some cases, binary/bytecode packages
>>> > are also produced as a convenience to users that might not have the
>>> > appropriate tools to build a compiled version of the source. In all
>>> such
>>> > cases, the binary/bytecode package must have the same version number as
>>> > the source release and may only add binary/bytecode files that are the
>>> > result of compiling that version of the source code release.
>>> > """
>>> >
>>> > [1] http://www.apache.org/dev/release.html#what
>>> >
>>> >
>>> >
>>> > --
>>> > --
>>> > Lahiru Sandaruwan
>>> > Software Engineer,
>>> > Platform Technologies,
>>> > WSO2 Inc., http://wso2.com
>>> > lean.enterprise.middleware
>>> >
>>> > email: lahirus@wso2.com cell: (+94) 773 325 954
>>> > blog: http://lahiruwrites.blogspot.com/
>>> > twitter: http://twitter.com/lahirus
>>> > linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>> >
>>>
>>>
>>
>>
>> --
>> --
>> Lahiru Sandaruwan
>> Software Engineer,
>> Platform Technologies,
>> WSO2 Inc., http://wso2.com
>> lean.enterprise.middleware
>>
>> email: lahirus@wso2.com cell: (+94) 773 325 954
>> blog: http://lahiruwrites.blogspot.com/
>> twitter: http://twitter.com/lahirus
>> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>>
>>
>
>
> --
> Lakmal Warusawithana
> Software Architect; WSO2 Inc.
> Mobile : +94714289692
> Blog : http://lakmalsview.blogspot.com/
>
>
--
Pradeep Fernando.
http://pradeepfernando.blogspot.com/
Re: Jclouds dependancies
Posted by Lakmal Warusawithana <la...@wso2.com>.
AFAIK those changes already fixed in newest version of jcloud. Anyway we
need to go to jcloud apache version after our build stable.
On Fri, Jul 12, 2013 at 2:08 AM, Lahiru Sandaruwan <la...@wso2.com> wrote:
>
>
>
> On Fri, Jul 12, 2013 at 2:05 AM, Suresh Marru <sm...@apache.org> wrote:
>
>> On Jul 11, 2013, at 4:22 PM, Lahiru Sandaruwan <la...@wso2.com> wrote:
>>
>> > Hi all,
>> >
>> > What we have is complete source which is customized.
>>
>> Orthogonal to this discussion, can you guys engage with jclouds community
>> and contribute back to JClouds next release?
>>
> +1...
>
>>
>> Suresh
>>
>> >
>> > Thanks.
>> >
>> >
>> > On Fri, Jul 12, 2013 at 1:45 AM, Chip Childers <
>> chip.childers@sungard.com> wrote:
>> > On Thu, Jul 11, 2013 at 04:11:29PM -0400, Chip Childers wrote:
>> > > On Fri, Jul 12, 2013 at 01:34:23AM +0530, Lahiru Sandaruwan wrote:
>> > > > Hi,
>> > > >
>> > > > Shall we bring dependency directory to the code base. We need a
>> place to
>> > > > have followings,
>> > > >
>> > > > org.jclouds.api:openstack-nova:jar:1.5.0-beta.5.wso2v1,
>> > > > org.jclouds.api:openstack-keystone:jar:1.5.0-beta.5.wso2v1,
>> > > > org.jclouds.api:openstack-nova:jar:1.5.0-beta.5.wso2v1
>> > > >
>> > >
>> > > Are you suggesting adding the jar files into the git repo?
>> > >
>> > > If so, I don't recommend it. Apache releases are "source only", so if
>> > > those are in the repo it will require removing them from the source
>> > > tarball. Is there any reason that you can't depend on them in the
>> > > project POMs?
>> > >
>> > > Keep in mind the jclouds is another podling within the incubator, so
>> if
>> > > you need anything from them I'd bet they could help.
>> > >
>> > > -chip
>> >
>> > And just to provide a link to explain what I meant by "source only", see
>> > the following paragraph that's at [1].
>> >
>> > """
>> > The Apache Software Foundation produces open source software. All
>> > releases are in the form of the source materials needed to make changes
>> > to the software being released. In some cases, binary/bytecode packages
>> > are also produced as a convenience to users that might not have the
>> > appropriate tools to build a compiled version of the source. In all such
>> > cases, the binary/bytecode package must have the same version number as
>> > the source release and may only add binary/bytecode files that are the
>> > result of compiling that version of the source code release.
>> > """
>> >
>> > [1] http://www.apache.org/dev/release.html#what
>> >
>> >
>> >
>> > --
>> > --
>> > Lahiru Sandaruwan
>> > Software Engineer,
>> > Platform Technologies,
>> > WSO2 Inc., http://wso2.com
>> > lean.enterprise.middleware
>> >
>> > email: lahirus@wso2.com cell: (+94) 773 325 954
>> > blog: http://lahiruwrites.blogspot.com/
>> > twitter: http://twitter.com/lahirus
>> > linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>> >
>>
>>
>
>
> --
> --
> Lahiru Sandaruwan
> Software Engineer,
> Platform Technologies,
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> email: lahirus@wso2.com cell: (+94) 773 325 954
> blog: http://lahiruwrites.blogspot.com/
> twitter: http://twitter.com/lahirus
> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>
>
--
Lakmal Warusawithana
Software Architect; WSO2 Inc.
Mobile : +94714289692
Blog : http://lakmalsview.blogspot.com/
Re: Jclouds dependancies
Posted by Lahiru Sandaruwan <la...@wso2.com>.
On Fri, Jul 12, 2013 at 2:05 AM, Suresh Marru <sm...@apache.org> wrote:
> On Jul 11, 2013, at 4:22 PM, Lahiru Sandaruwan <la...@wso2.com> wrote:
>
> > Hi all,
> >
> > What we have is complete source which is customized.
>
> Orthogonal to this discussion, can you guys engage with jclouds community
> and contribute back to JClouds next release?
>
+1...
>
> Suresh
>
> >
> > Thanks.
> >
> >
> > On Fri, Jul 12, 2013 at 1:45 AM, Chip Childers <
> chip.childers@sungard.com> wrote:
> > On Thu, Jul 11, 2013 at 04:11:29PM -0400, Chip Childers wrote:
> > > On Fri, Jul 12, 2013 at 01:34:23AM +0530, Lahiru Sandaruwan wrote:
> > > > Hi,
> > > >
> > > > Shall we bring dependency directory to the code base. We need a
> place to
> > > > have followings,
> > > >
> > > > org.jclouds.api:openstack-nova:jar:1.5.0-beta.5.wso2v1,
> > > > org.jclouds.api:openstack-keystone:jar:1.5.0-beta.5.wso2v1,
> > > > org.jclouds.api:openstack-nova:jar:1.5.0-beta.5.wso2v1
> > > >
> > >
> > > Are you suggesting adding the jar files into the git repo?
> > >
> > > If so, I don't recommend it. Apache releases are "source only", so if
> > > those are in the repo it will require removing them from the source
> > > tarball. Is there any reason that you can't depend on them in the
> > > project POMs?
> > >
> > > Keep in mind the jclouds is another podling within the incubator, so if
> > > you need anything from them I'd bet they could help.
> > >
> > > -chip
> >
> > And just to provide a link to explain what I meant by "source only", see
> > the following paragraph that's at [1].
> >
> > """
> > The Apache Software Foundation produces open source software. All
> > releases are in the form of the source materials needed to make changes
> > to the software being released. In some cases, binary/bytecode packages
> > are also produced as a convenience to users that might not have the
> > appropriate tools to build a compiled version of the source. In all such
> > cases, the binary/bytecode package must have the same version number as
> > the source release and may only add binary/bytecode files that are the
> > result of compiling that version of the source code release.
> > """
> >
> > [1] http://www.apache.org/dev/release.html#what
> >
> >
> >
> > --
> > --
> > Lahiru Sandaruwan
> > Software Engineer,
> > Platform Technologies,
> > WSO2 Inc., http://wso2.com
> > lean.enterprise.middleware
> >
> > email: lahirus@wso2.com cell: (+94) 773 325 954
> > blog: http://lahiruwrites.blogspot.com/
> > twitter: http://twitter.com/lahirus
> > linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
> >
>
>
--
--
Lahiru Sandaruwan
Software Engineer,
Platform Technologies,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
email: lahirus@wso2.com cell: (+94) 773 325 954
blog: http://lahiruwrites.blogspot.com/
twitter: http://twitter.com/lahirus
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
Re: Jclouds dependancies
Posted by David Nalley <da...@gnsa.us>.
On Thu, Jul 11, 2013 at 4:35 PM, Suresh Marru <sm...@apache.org> wrote:
> On Jul 11, 2013, at 4:22 PM, Lahiru Sandaruwan <la...@wso2.com> wrote:
>
>> Hi all,
>>
>> What we have is complete source which is customized.
>
> Orthogonal to this discussion, can you guys engage with jclouds community and contribute back to JClouds next release?
>
Yes - I am sure they would be happy to get patches from you.
--David
Re: Jclouds dependancies
Posted by Suresh Marru <sm...@apache.org>.
On Jul 11, 2013, at 4:22 PM, Lahiru Sandaruwan <la...@wso2.com> wrote:
> Hi all,
>
> What we have is complete source which is customized.
Orthogonal to this discussion, can you guys engage with jclouds community and contribute back to JClouds next release?
Suresh
>
> Thanks.
>
>
> On Fri, Jul 12, 2013 at 1:45 AM, Chip Childers <ch...@sungard.com> wrote:
> On Thu, Jul 11, 2013 at 04:11:29PM -0400, Chip Childers wrote:
> > On Fri, Jul 12, 2013 at 01:34:23AM +0530, Lahiru Sandaruwan wrote:
> > > Hi,
> > >
> > > Shall we bring dependency directory to the code base. We need a place to
> > > have followings,
> > >
> > > org.jclouds.api:openstack-nova:jar:1.5.0-beta.5.wso2v1,
> > > org.jclouds.api:openstack-keystone:jar:1.5.0-beta.5.wso2v1,
> > > org.jclouds.api:openstack-nova:jar:1.5.0-beta.5.wso2v1
> > >
> >
> > Are you suggesting adding the jar files into the git repo?
> >
> > If so, I don't recommend it. Apache releases are "source only", so if
> > those are in the repo it will require removing them from the source
> > tarball. Is there any reason that you can't depend on them in the
> > project POMs?
> >
> > Keep in mind the jclouds is another podling within the incubator, so if
> > you need anything from them I'd bet they could help.
> >
> > -chip
>
> And just to provide a link to explain what I meant by "source only", see
> the following paragraph that's at [1].
>
> """
> The Apache Software Foundation produces open source software. All
> releases are in the form of the source materials needed to make changes
> to the software being released. In some cases, binary/bytecode packages
> are also produced as a convenience to users that might not have the
> appropriate tools to build a compiled version of the source. In all such
> cases, the binary/bytecode package must have the same version number as
> the source release and may only add binary/bytecode files that are the
> result of compiling that version of the source code release.
> """
>
> [1] http://www.apache.org/dev/release.html#what
>
>
>
> --
> --
> Lahiru Sandaruwan
> Software Engineer,
> Platform Technologies,
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> email: lahirus@wso2.com cell: (+94) 773 325 954
> blog: http://lahiruwrites.blogspot.com/
> twitter: http://twitter.com/lahirus
> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>
Re: Jclouds dependancies
Posted by Lahiru Sandaruwan <la...@wso2.com>.
Hi all,
What we have is complete source which is customized.
Thanks.
On Fri, Jul 12, 2013 at 1:45 AM, Chip Childers <ch...@sungard.com>wrote:
> On Thu, Jul 11, 2013 at 04:11:29PM -0400, Chip Childers wrote:
> > On Fri, Jul 12, 2013 at 01:34:23AM +0530, Lahiru Sandaruwan wrote:
> > > Hi,
> > >
> > > Shall we bring dependency directory to the code base. We need a place
> to
> > > have followings,
> > >
> > > org.jclouds.api:openstack-nova:jar:1.5.0-beta.5.wso2v1,
> > > org.jclouds.api:openstack-keystone:jar:1.5.0-beta.5.wso2v1,
> > > org.jclouds.api:openstack-nova:jar:1.5.0-beta.5.wso2v1
> > >
> >
> > Are you suggesting adding the jar files into the git repo?
> >
> > If so, I don't recommend it. Apache releases are "source only", so if
> > those are in the repo it will require removing them from the source
> > tarball. Is there any reason that you can't depend on them in the
> > project POMs?
> >
> > Keep in mind the jclouds is another podling within the incubator, so if
> > you need anything from them I'd bet they could help.
> >
> > -chip
>
> And just to provide a link to explain what I meant by "source only", see
> the following paragraph that's at [1].
>
> """
> The Apache Software Foundation produces open source software. All
> releases are in the form of the source materials needed to make changes
> to the software being released. In some cases, binary/bytecode packages
> are also produced as a convenience to users that might not have the
> appropriate tools to build a compiled version of the source. In all such
> cases, the binary/bytecode package must have the same version number as
> the source release and may only add binary/bytecode files that are the
> result of compiling that version of the source code release.
> """
>
> [1] http://www.apache.org/dev/release.html#what
>
--
--
Lahiru Sandaruwan
Software Engineer,
Platform Technologies,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
email: lahirus@wso2.com cell: (+94) 773 325 954
blog: http://lahiruwrites.blogspot.com/
twitter: http://twitter.com/lahirus
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
Re: Jclouds dependancies
Posted by Chip Childers <ch...@sungard.com>.
On Thu, Jul 11, 2013 at 04:11:29PM -0400, Chip Childers wrote:
> On Fri, Jul 12, 2013 at 01:34:23AM +0530, Lahiru Sandaruwan wrote:
> > Hi,
> >
> > Shall we bring dependency directory to the code base. We need a place to
> > have followings,
> >
> > org.jclouds.api:openstack-nova:jar:1.5.0-beta.5.wso2v1,
> > org.jclouds.api:openstack-keystone:jar:1.5.0-beta.5.wso2v1,
> > org.jclouds.api:openstack-nova:jar:1.5.0-beta.5.wso2v1
> >
>
> Are you suggesting adding the jar files into the git repo?
>
> If so, I don't recommend it. Apache releases are "source only", so if
> those are in the repo it will require removing them from the source
> tarball. Is there any reason that you can't depend on them in the
> project POMs?
>
> Keep in mind the jclouds is another podling within the incubator, so if
> you need anything from them I'd bet they could help.
>
> -chip
And just to provide a link to explain what I meant by "source only", see
the following paragraph that's at [1].
"""
The Apache Software Foundation produces open source software. All
releases are in the form of the source materials needed to make changes
to the software being released. In some cases, binary/bytecode packages
are also produced as a convenience to users that might not have the
appropriate tools to build a compiled version of the source. In all such
cases, the binary/bytecode package must have the same version number as
the source release and may only add binary/bytecode files that are the
result of compiling that version of the source code release.
"""
[1] http://www.apache.org/dev/release.html#what
Re: Jclouds dependancies
Posted by Chip Childers <ch...@sungard.com>.
On Fri, Jul 12, 2013 at 01:34:23AM +0530, Lahiru Sandaruwan wrote:
> Hi,
>
> Shall we bring dependency directory to the code base. We need a place to
> have followings,
>
> org.jclouds.api:openstack-nova:jar:1.5.0-beta.5.wso2v1,
> org.jclouds.api:openstack-keystone:jar:1.5.0-beta.5.wso2v1,
> org.jclouds.api:openstack-nova:jar:1.5.0-beta.5.wso2v1
>
Are you suggesting adding the jar files into the git repo?
If so, I don't recommend it. Apache releases are "source only", so if
those are in the repo it will require removing them from the source
tarball. Is there any reason that you can't depend on them in the
project POMs?
Keep in mind the jclouds is another podling within the incubator, so if
you need anything from them I'd bet they could help.
-chip
Re: Jclouds dependancies
Posted by Lahiru Sandaruwan <la...@wso2.com>.
On Fri, Jul 12, 2013 at 1:40 AM, Suresh Marru <sm...@apache.org> wrote:
> Are these any customizations to the standard jclouds dependencies? Can
> these be switched over to the recent release of jclouds? -
> http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache.jclouds%22
I think yes. Nirmal did some?
Currently we use Jclouds state which it before moving to Apache. We can
update it to the Apache version. But until we get the code base building we
should go with current versions(whatever we have).
We will definitely have to go to Apache version after that.
Thanks.
>
>
> Suresh
>
> On Jul 11, 2013, at 4:04 PM, Lahiru Sandaruwan <la...@wso2.com> wrote:
>
> > Hi,
> >
> > Shall we bring dependency directory to the code base. We need a place to
> have followings,
> >
> > org.jclouds.api:openstack-nova:jar:1.5.0-beta.5.wso2v1,
> > org.jclouds.api:openstack-keystone:jar:1.5.0-beta.5.wso2v1,
> > org.jclouds.api:openstack-nova:jar:1.5.0-beta.5.wso2v1
> >
> > Thanks.
> >
> > --
> > --
> > Lahiru Sandaruwan
> > Software Engineer,
> > Platform Technologies,
> > WSO2 Inc., http://wso2.com
> > lean.enterprise.middleware
> >
> > email: lahirus@wso2.com cell: (+94) 773 325 954
> > blog: http://lahiruwrites.blogspot.com/
> > twitter: http://twitter.com/lahirus
> > linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
> >
>
>
--
--
Lahiru Sandaruwan
Software Engineer,
Platform Technologies,
WSO2 Inc., http://wso2.com
lean.enterprise.middleware
email: lahirus@wso2.com cell: (+94) 773 325 954
blog: http://lahiruwrites.blogspot.com/
twitter: http://twitter.com/lahirus
linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
Re: Jclouds dependancies
Posted by Suresh Marru <sm...@apache.org>.
Are these any customizations to the standard jclouds dependencies? Can these be switched over to the recent release of jclouds? - http://search.maven.org/#search%7Cga%7C1%7Cg%3A%22org.apache.jclouds%22
Suresh
On Jul 11, 2013, at 4:04 PM, Lahiru Sandaruwan <la...@wso2.com> wrote:
> Hi,
>
> Shall we bring dependency directory to the code base. We need a place to have followings,
>
> org.jclouds.api:openstack-nova:jar:1.5.0-beta.5.wso2v1,
> org.jclouds.api:openstack-keystone:jar:1.5.0-beta.5.wso2v1,
> org.jclouds.api:openstack-nova:jar:1.5.0-beta.5.wso2v1
>
> Thanks.
>
> --
> --
> Lahiru Sandaruwan
> Software Engineer,
> Platform Technologies,
> WSO2 Inc., http://wso2.com
> lean.enterprise.middleware
>
> email: lahirus@wso2.com cell: (+94) 773 325 954
> blog: http://lahiruwrites.blogspot.com/
> twitter: http://twitter.com/lahirus
> linked-in: http://lk.linkedin.com/pub/lahiru-sandaruwan/16/153/146
>