RE: [dsdp-mtj-dev] Separate resources foldersformulti-target buildanddis

["Hildum Eric-XFQ473" <XFQ473@xxxxxxxxxxxx>]

Thank you for the pointer to the tutorial; facets look very interesting as a solution to multiple resources. 


Eric Hildum
Senior Product Manager, Mobile Developer Tools & SDK
Software Platforms and Delivery
Ecosystem and Market Development
Motorola
Direct: +1-408-541-6809
Mobile: +1-510-305-0801
 
809 11th Avenue
Sunnyvale, CA 94089
USA

-----Original Message-----
From: dsdp-mtj-dev-bounces@xxxxxxxxxxx [mailto:dsdp-mtj-dev-bounces@xxxxxxxxxxx] On Behalf Of Gorkem Ercan
Sent: Monday, December 15, 2008 6:39
To: Mobile Tools for The Java Platform mailing list
Subject: Re: [dsdp-mtj-dev] Separate resources foldersformulti-target buildanddistribution

There is a tutorial about facets here.
http://www.eclipse.org/articles/Article-BuildingProjectFacets/tutorial.html
. I think it is a good document to skim through to understand all the possibilities. The document is dated 2006 however I do not think it has changed much since then.

I was thinking that configurations would be facets. So when a facet is added by the developer to the project, it would be possible to change the src folders, and the anttena configuration files etc. Facets also provide the possibility to have wizards for getting custom vales. For instance developers can use own locations for src and resource files etc. Also facets can be grouped, I guess this can also be helpful in organizing different manufacturer properties together.
--
Gorkem

On Mon, Dec 15, 2008 at 2:27 PM, Craig Setera <craigjunk@xxxxxxxxxx> wrote:
> Gorkem,
>
> I've heard much talk of facets in the past.  Do you have any good 
> pointers to high level information on what facets can do and how they 
> might work in this case?
>
> Thanks,
> Craig
>
> On Dec 10, 2008, at 4:55 PM, Gorkem Ercan wrote:
>
>> Eclipse Webtools project has a concept called facets. They are 
>> typically used as a way of adding functionality to a project. When a 
>> facet is added/removed to the project it can perform any set of 
>> actions such as  installing builders, creating, copying artifacts etc.
>> Facets also has UI parts so that they can be easily changed by users.
>> Facets have recently become a project by itself so that they can be 
>> used by other projects. The build time differentiation need on MTJ 
>> resembles the need in WTP to enable different enterprise java 
>> standards and vendor specific solutions. I think facets is an option 
>> worth to explore for MTJ as well.
>> --
>> Gorkem
>>
>>
>> On Wed, Dec 10, 2008 at 6:26 PM, Hildum Eric-XFQ473 
>> <XFQ473@xxxxxxxxxxxx>
>> wrote:
>>>
>>> Should we also consider requesting/making changes to JDT to support this?
>>> Would there be a value to desktop and enterprise Java developers to 
>>> have this sort of feature?
>>>
>>> Eric Hildum
>>> Senior Product Manager, Mobile Developer Tools & SDK Software 
>>> Platforms and Delivery Ecosystem and Market Development Motorola
>>> Direct: +1-408-541-6809
>>> Mobile: +1-510-305-0801
>>>
>>> 809 11th Avenue
>>> Sunnyvale, CA 94089
>>> USA
>>>
>>> ________________________________
>>> From: dsdp-mtj-dev-bounces@xxxxxxxxxxx 
>>> [mailto:dsdp-mtj-dev-bounces@xxxxxxxxxxx] On Behalf Of Paula 
>>> Gustavo-WGP010
>>> Sent: Wednesday, December 10, 2008 6:20
>>> To: Mobile Tools for The Java Platform mailing list
>>> Cc: dsdp-mtj-dev-bounces@xxxxxxxxxxx
>>> Subject: RES: [dsdp-mtj-dev] Separate resources 
>>> foldersformulti-target buildand distribution
>>>
>>> Other options that i was thinking about how to do this is to have 
>>> like a build.properties file on each mtj project similar to PDE.
>>>
>>>
>>>
>>> Everytime that we add a configuration, we could add an entry on that 
>>> file that list all content that is included on the final jar file. 
>>> That would give more freedom to the developer to use to organize 
>>> this folder and also to have like common resource folders.
>>>
>>>
>>>
>>> A possible example of file is:
>>>
>>>
>>>
>>> config_1.bin.includes = .,res_common,res_config1
>>>
>>> config_2.bin.includes = .,res_common,res_config2
>>>
>>>
>>>
>>> this approach might be easier to implement.
>>>
>>>
>>>
>>> J
>>>
>>> gep
>>>
>>>
>>>
>>> ________________________________
>>>
>>> De: dsdp-mtj-dev-bounces@xxxxxxxxxxx 
>>> [mailto:dsdp-mtj-dev-bounces@xxxxxxxxxxx] Em nome de Craig Setera 
>>> Enviada em: terça-feira, 9 de dezembro de 2008 09:15
>>> Para: Mobile Tools for The Java Platform mailing list
>>> Cc: dsdp-mtj-dev-bounces@xxxxxxxxxxx
>>> Assunto: Re: [dsdp-mtj-dev] Separate resources folders 
>>> formulti-target buildand distribution
>>>
>>>
>>>
>>> I agree with your assessment on this.   it is very similar to the way
>>> that
>>> we change out the JavaME libraries when the target device is altered.
>>>  This
>>> is a non-trivial feature to add to the system and definitely needs 
>>> to be part of a major release.
>>>
>>>
>>>
>>> On Dec 8, 2008, at 8:28 PM, Feng.Wang@xxxxxxxxxx wrote:
>>>
>>>
>>> I am thinking how to define source folders for each configuration. I 
>>> am afraid JDT don't support this feature. So we can 1. Set source 
>>> folders information in configuration meta data.
>>> 2. Only current active configuration's source folders are JDT Java 
>>> source folder. Other source folders are set to normal folder.
>>> 3. When active configuration switch, source folders switch too.
>>> 4. Modify Antenna build files exporting feature.
>>> 5. When packaging, go through every configurations, switch source 
>>> folders, build source code, and copy JAD and JAR files.
>>>
>>> I guess only if configurations share some source folders, put them 
>>> in one project make sense; otherwise, user can create separate projects.
>>> I think it's better to add this feature in feature release, if it is 
>>> important.
>>>
>>> Best Regards,
>>> Feng(Marvin) Wang(王峰)
>>>
>>> Sybase Software (China) Co., Ltd
>>> Room 1202-1203, Building One,
>>> Zhangjiang Semiconductor Industry Park 3000 Longdong Avenue Pudong, 
>>> Shanghai 201203
>>> Tel: +8621-38657441 or 258-7441
>>> email: feng.wang@xxxxxxxxxx
>>>
>>> "Hildum Eric-XFQ473" <XFQ473@xxxxxxxxxxxx> Sent by: 
>>> dsdp-mtj-dev-bounces@xxxxxxxxxxx
>>>
>>> 2008-12-09 00:30
>>>
>>> Please respond to
>>> Mobile Tools for The Java Platform mailing list 
>>> <dsdp-mtj-dev@xxxxxxxxxxx>
>>>
>>> To
>>>
>>> "Mobile Tools for The Java Platform mailing list"
>>> <dsdp-mtj-dev@xxxxxxxxxxx>
>>>
>>> cc
>>>
>>>
>>>
>>> Subject
>>>
>>> RE: [dsdp-mtj-dev] Separate resources folders for multi-target 
>>> buildand distribution
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>>
>>> If it is important, and not currently in the roadmap, then it seems 
>>> that we should put it there. Would this be a good 1.1 feature?
>>>
>>> Eric Hildum
>>> Senior Product Manager, Mobile Developer Tools & SDK Software 
>>> Platforms and Delivery Ecosystem and Market Development Motorola
>>> Direct: +1-408-541-6809
>>> Mobile: +1-510-305-0801
>>>
>>> 809 11th Avenue
>>> Sunnyvale, CA 94089
>>> USA
>>>
>>>
>>> ________________________________
>>>
>>> From: dsdp-mtj-dev-bounces@xxxxxxxxxxx 
>>> [mailto:dsdp-mtj-dev-bounces@xxxxxxxxxxx] On Behalf Of Craig Setera
>>> Sent: Monday, December 08, 2008 4:18
>>> To: Mobile Tools for The Java Platform mailing list
>>> Subject: Re: [dsdp-mtj-dev] Separate resources folders for 
>>> multi-target buildand distribution
>>>
>>> This has been in the conceptual design for quite some time (back in 
>>> EclipseME days).  I agree that it is an important piece of functionality.
>>>
>>> On Dec 8, 2008, at 6:12 AM, Ales Milan (Inlogic Software s.r.o.) wrote:
>>>
>>> One more issue what I need in MTJ.
>>> Developer of limited devices many times require to use different 
>>> resource folders for each configuration.
>>> My suggestion is
>>> 1) define default resource folders for project (this choice is 
>>> currently
>>> available)
>>> 2) possibility to define resource folders for each device configuration.
>>>
>>> what you think ?
>>>
>>> similar problem was:
>>> [multdevice]: Separate deploy folders for multi-target build and 
>>> distribution
>>> https://bugs.eclipse.org/bugs/show_bug.cgi?id=249834
>>>
>>> Ales
>>> _______________________________________________
>>> dsdp-mtj-dev mailing list
>>> dsdp-mtj-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/dsdp-mtj-dev
>>> _______________________________________________
>>> dsdp-mtj-dev mailing list
>>> dsdp-mtj-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/dsdp-mtj-dev
>>>
>>> _______________________________________________
>>> dsdp-mtj-dev mailing list
>>> dsdp-mtj-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/dsdp-mtj-dev
>>>
>>>
>>>
>>> _______________________________________________
>>> dsdp-mtj-dev mailing list
>>> dsdp-mtj-dev@xxxxxxxxxxx
>>> https://dev.eclipse.org/mailman/listinfo/dsdp-mtj-dev
>>>
>>>
>> _______________________________________________
>> dsdp-mtj-dev mailing list
>> dsdp-mtj-dev@xxxxxxxxxxx
>> https://dev.eclipse.org/mailman/listinfo/dsdp-mtj-dev
>
> _______________________________________________
> dsdp-mtj-dev mailing list
> dsdp-mtj-dev@xxxxxxxxxxx
> https://dev.eclipse.org/mailman/listinfo/dsdp-mtj-dev
>