Skip to main content
[Date Prev][Date Next][Thread Prev][Thread Next][Date Index][Thread Index] [List Home]
Re: [andmore-dev] m2e-android integration
Whatever is going to be easiest for you to support.  I might recommend splitting into two plugins.  One that is Andmore specific, and one that is ADT specific.   And maybe refactoring to a common core plugin that has the base functionality between the two.

This way the separate feature route could be used and only the functionality and plugins required for a specific feature are included.

The thing we need to be careful of is making sure that m2e-android doesn't install ADT plugins in with Andmore, as you will have both possible plugins fighting to control things.  We've renamed the natures and builders for Andmore to try and help elminate the conflict.

Also, how is m2e when it is doing discovery of the plugins to use, going to know which set of plugins to bring in?  Will it present two options to the user?   m2e-android-adt and m2e-android-andmore?

As soon as we have a public repo of p2 plugins available I can let you know.  In the mean time if you want to try supporting the plugins now, I think the main plugins and package ids are pretty stable, some class names might be renamed though.

Dave

On 1/7/15 10:26 AM, Ricardo Gladwell wrote:
Opening discussion here following on from the discussion on this PR:


So far we have two possibly solutions:

1. Use the adaptor design pattern within the plugin to support ADT and Andmore.

2. Separate features for Andmore and ADT support with some kind of extension point.

Regards…

— 
@rgladwell





_______________________________________________
andmore-dev mailing list
andmore-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe from this list, visit
https://dev.eclipse.org/mailman/listinfo/andmore-dev

Back to the top