Maybe new archetype

[peter-budo]

Not sure if this is in general interest and if you willing to add this to the project, but maybe someone may find it useful.

I used my previous experiences with this project to create a specific archetype that we started to use in our company Novoda (https://github.com/novoda/android-archetypes).
Project is split into four modules:

• app - android application (depends on core module)
• core - "plain" Java, stuff that can be easier tested with JUnit and mocked with various frameworks (we try this section to be as much independent from Android, but sometimes some stuff sneak inside)
• instrumentation - tests for Android stuff in app module
• team - plain folder with team related stuff if one has to share some documents that may not necessary part of the project, coding standards etc

Few things to mention:

• 4.0.1.2 been made default Android version down to number of 4.0 devices and client requirements to build agains this version rather then 2.3 and/or lower
• By default Android support library, action bar sherlock, robolectric, powermock been added
• This setup also includes working setup for Emma reports with reports being build also on none rooted devices (Android Maven Plugin wiki info is rather difficult to follow get this setup going http://code.google.com/p/maven-android-plugin/wiki/EmmaMaven)
• .gitignore for IntelliJ and Eclipse

[cescoffier]

Except the team folder which may be a bit too tight to your organization, the rest could be a new archetype... We just need a name for it.

[peter-budo]

Sorry for delayed replay I was on holidays.

I can remove team folder.
However for name I was hopping to keep it as it is, given that project structure it is done in the "fashion" we use in Novoda plus they allowed me to work on this.

[peter-budo]

Hmmm, since no comment was given I think outcome is clear.
Is it OK with you if I spin novoda archetype as new project based on your project?

[cescoffier]

Hi,

The problem is that I'm no more in charge of the archetypes (I don't work for akquinet anymore). However,, I'm not against a fork on codehaus or apache.

Clement

On 2 sept. 2012, at 13:34, Peter Mikloško notifications@github.com wrote:

Hmmm, since no comment was given I think outcome is clear.
Is it OK with you if I spin novoda archetype as new project based on your project?

—
Reply to this email directly or view it on GitHub.

[peter-budo]

Hmm so who is in charge and can approve pull requests that I made for Jelly Bean addition?

[philippkumar]

Hi there,

I am.
The archetype without the team folder looks like a nice addition to the present archetypes. Alternatively, feel free to fork the project.

Best regards
Philipp

[peter-budo]

Will be forking project (only releasing novoda part) due to slow respond time on last pull request