[Dev] How are we going to move unified-endpoint and old datasource features to GitHub?

2014-02-13 Thread Thilini Ishaka
Hi, BPS depends on *unified-endpoint* and *old datasource* features. Are there any product teams who use these? If no other product team needs above two features, we can maintain those under *'carbon-business-process*' or '*bps*' project category according to the new structuring. I think 'carbon-

Re: [Dev] How are we going to move unified-endpoint and old datasource features to GitHub?

2014-02-13 Thread Anjana Fernando
Hi, Actually no one should be actually using the old data source component, we should move everything to the new data sources component. Cheers, Anjana. On Thu, Feb 13, 2014 at 3:05 PM, Thilini Ishaka wrote: > ESB team, do you need old datasource component? As I see there's a > dependency for

Re: [Dev] How are we going to move unified-endpoint and old datasource features to GitHub?

2014-02-13 Thread Thilini Ishaka
Hi Anjana, BPS still depends on the old datasource component. Due to few issues we encountered, we are unable to migrate to new datasource component. This has already been communicated in different mail threads. Until we move to ndatasource component, we need to keep the old datasource component.

Re: [Dev] How are we going to move unified-endpoint and old datasource features to GitHub?

2014-02-13 Thread Anjana Fernando
Hi, OK, but we would need to do it soon, by figuring out what the issues are, it doesn't make sense to have two of these components to be in the same server. Cheers, Anjana. On Thu, Feb 13, 2014 at 4:13 PM, Thilini Ishaka wrote: > Hi Anjana, > > BPS still depends on the old datasource compone

Re: [Dev] How are we going to move unified-endpoint and old datasource features to GitHub?

2014-02-13 Thread Thilini Ishaka
Yes, we are planning that for the next release which is due in May. Thanks Thilini On Thu, Feb 13, 2014 at 4:46 PM, Anjana Fernando wrote: > Hi, > > OK, but we would need to do it soon, by figuring out what the issues are, > it doesn't make sense to have two of these components to be in the sa

Re: [Dev] How are we going to move unified-endpoint and old datasource features to GitHub?

2014-02-13 Thread Sagara Gunathunga
On Thu, Feb 13, 2014 at 5:05 PM, Thilini Ishaka wrote: > Yes, we are planning that for the next release which is due in May. > Then for the time being can you depended on already released version ? if it's possible we don't need to bring this component into GitHub. Thanks ! > > Thanks > Thili

Re: [Dev] How are we going to move unified-endpoint and old datasource features to GitHub?

2014-02-13 Thread Thilini Ishaka
On Thu, Feb 13, 2014 at 5:08 PM, Sagara Gunathunga wrote: > > > > On Thu, Feb 13, 2014 at 5:05 PM, Thilini Ishaka wrote: > >> Yes, we are planning that for the next release which is due in May. >> > > Then for the time being can you depended on already released version ? if > it's possible we d

Re: [Dev] How are we going to move unified-endpoint and old datasource features to GitHub?

2014-02-13 Thread Thilini Ishaka
ESB team, do you need old datasource component? As I see there's a dependency for that. please confirm. Thanks Thilini On Thu, Feb 13, 2014 at 2:52 PM, Thilini Ishaka wrote: > Hi, > > BPS depends on *unified-endpoint* and *old datasource* features. > Are there any product teams who use these?