You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@stratos.apache.org by Thanuja Uruththirakodeeswaran <th...@wso2.com> on 2015/10/12 10:35:53 UTC
DAS extension folder structure
Hi All,
I have restructured das extension folder to have similar structure as other
extensions. The review this P/R [1] and suggest any improvements.
Currntly das extension *modules* folder has following structure:
├── artifacts
│ └── metering-dashboard
│ ├── capps
│ ├── jaggery-files
│ ├── mysqlscript.sql
│ ├── README.md
│ └── ues-patch
├── distribution
│ ├── pom.xml
│ ├── README.md
│ ├── src
│ │ ├── assembly
│ │ └── main
│ └── target
│ ├── archive-tmp
│ ├── maven-shared-archive-resources
│ ├── org.apache.stratos.das.artifacts-4.1.4-SNAPSHOT.zip
│ └── timestamp
└── stratos-das-extension
└── spark-udfs
├── pom.xml
├── README.md
├── spark-time-udf
└── target
- artifacts folder includes metering-dashboard folder which consists all
artifacts needed to populate metering dashboard in externally running das.
- stratos-das-extension has spark-udfs which will include all the User
Defined Functions needed to run spark queries in DAS. Currently I have only
spark-time-udf within it.
[1]. https://github.com/apache/stratos/pull/474
Thanks.
--
Thanuja Uruththirakodeeswaran
Software Engineer
WSO2 Inc.;http://wso2.com
lean.enterprise.middleware
mobile: +94 774363167
Re: DAS extension folder structure
Posted by Thanuja Uruththirakodeeswaran <th...@wso2.com>.
Hi All,
If we remove this CApp folder structure and follow the same folder
structure as in cep extension artifacts, it's very hard to create the car
file. If we don't have this car file, It's difficult to populate dashboard
by manually copying all the artifacts to DAS. So for the time-being we will
go with structure.
I have removed the version(1.0.0) from CApps folders.
Thanks.
On Tue, Oct 13, 2015 at 4:58 PM, Imesh Gunaratne <im...@apache.org> wrote:
> Hi Thanuja,
>
> Few things I noticed:
>
>
> As a standard we do not check in CApp folder structure to version control
> system. Please see how CEP artifacts have been added. IMO we can directly
> copy DAS artifacts into the DAS runtime without having a CApp.
>
> The second point is, why we are invoking a build.xml from pom.xml? Shall
> we move the logic in build.xml to pom.xml?
>
> Thanks
>
>
> On Mon, Oct 12, 2015 at 2:05 PM, Thanuja Uruththirakodeeswaran <
> thanujau@wso2.com> wrote:
>
>> Hi All,
>>
>> I have restructured das extension folder to have similar structure as
>> other extensions. The review this P/R [1] and suggest any improvements.
>>
>> Currntly das extension *modules* folder has following structure:
>>
>> ├── artifacts
>> │ └── metering-dashboard
>> │ ├── capps
>> │ ├── jaggery-files
>> │ ├── mysqlscript.sql
>> │ ├── README.md
>> │ └── ues-patch
>> ├── distribution
>> │ ├── pom.xml
>> │ ├── README.md
>> │ ├── src
>> │ │ ├── assembly
>> │ │ └── main
>> │ └── target
>> │ ├── archive-tmp
>> │ ├── maven-shared-archive-resources
>> │ ├── org.apache.stratos.das.artifacts-4.1.4-SNAPSHOT.zip
>> │ └── timestamp
>> └── stratos-das-extension
>> └── spark-udfs
>> ├── pom.xml
>> ├── README.md
>> ├── spark-time-udf
>> └── target
>>
>> - artifacts folder includes metering-dashboard folder which consists
>> all artifacts needed to populate metering dashboard in externally running
>> das.
>> - stratos-das-extension has spark-udfs which will include all the
>> User Defined Functions needed to run spark queries in DAS. Currently I have
>> only spark-time-udf within it.
>>
>> [1]. https://github.com/apache/stratos/pull/474
>>
>> Thanks.
>>
>> --
>> Thanuja Uruththirakodeeswaran
>> Software Engineer
>> WSO2 Inc.;http://wso2.com
>> lean.enterprise.middleware
>>
>> mobile: +94 774363167
>>
>
>
>
> --
> Imesh Gunaratne
>
> Senior Technical Lead, WSO2
> Committer & PMC Member, Apache Stratos
>
--
Thanuja Uruththirakodeeswaran
Software Engineer
WSO2 Inc.;http://wso2.com
lean.enterprise.middleware
mobile: +94 774363167
Re: DAS extension folder structure
Posted by Imesh Gunaratne <im...@apache.org>.
Hi Thanuja,
Few things I noticed:
As a standard we do not check in CApp folder structure to version control
system. Please see how CEP artifacts have been added. IMO we can directly
copy DAS artifacts into the DAS runtime without having a CApp.
The second point is, why we are invoking a build.xml from pom.xml? Shall we
move the logic in build.xml to pom.xml?
Thanks
On Mon, Oct 12, 2015 at 2:05 PM, Thanuja Uruththirakodeeswaran <
thanujau@wso2.com> wrote:
> Hi All,
>
> I have restructured das extension folder to have similar structure as
> other extensions. The review this P/R [1] and suggest any improvements.
>
> Currntly das extension *modules* folder has following structure:
>
> ├── artifacts
> │ └── metering-dashboard
> │ ├── capps
> │ ├── jaggery-files
> │ ├── mysqlscript.sql
> │ ├── README.md
> │ └── ues-patch
> ├── distribution
> │ ├── pom.xml
> │ ├── README.md
> │ ├── src
> │ │ ├── assembly
> │ │ └── main
> │ └── target
> │ ├── archive-tmp
> │ ├── maven-shared-archive-resources
> │ ├── org.apache.stratos.das.artifacts-4.1.4-SNAPSHOT.zip
> │ └── timestamp
> └── stratos-das-extension
> └── spark-udfs
> ├── pom.xml
> ├── README.md
> ├── spark-time-udf
> └── target
>
> - artifacts folder includes metering-dashboard folder which consists
> all artifacts needed to populate metering dashboard in externally running
> das.
> - stratos-das-extension has spark-udfs which will include all the User
> Defined Functions needed to run spark queries in DAS. Currently I have only
> spark-time-udf within it.
>
> [1]. https://github.com/apache/stratos/pull/474
>
> Thanks.
>
> --
> Thanuja Uruththirakodeeswaran
> Software Engineer
> WSO2 Inc.;http://wso2.com
> lean.enterprise.middleware
>
> mobile: +94 774363167
>
--
Imesh Gunaratne
Senior Technical Lead, WSO2
Committer & PMC Member, Apache Stratos