Customization of generated files #52

Closed
rhajdacki opened this Issue Nov 3, 2011 · 4 comments

Projects

None yet

2 participants

@rhajdacki

There are situations when due to strange requirements in project generated Eclipse files need some non stanadard customization.
It would be nice to have simple extension points that would allow customization of generated Eclipse project files.

@hseeberger hseeberger closed this Nov 11, 2011
@hseeberger hseeberger reopened this Nov 24, 2011
@hseeberger

Could you please elaborate?

@rhajdacki

We had to setup Android project and sbteclipse does not support this out of the box.
But there are lots of Eclipse plugins that in order to work require some setup in Eclipse project files.
It would be handy if sbteclipse supported some kind of extension point or post processing functionality that would allow customization of generated project files.

@hseeberger

Could you please give some concrete examples how such additional contents in .classpath or .project would look like?

@hseeberger hseeberger reopened this Dec 20, 2011
@rhajdacki

Examples of such modifications:

  • Customization of natures in .project file. In case of Android this is:

    <nature>com.android.ide.eclipse.adt.AndroidNature</nature>
    
  • Modification of buildSpec in .project file. For example adding such elements:

    <buildCommand>
        <name>com.android.ide.eclipse.adt.ResourceManagerBuilder</name>
        <arguments>
        </arguments>
    </buildCommand>
    
  • Adding classpath entry in .claspath file:

    <classpathentry kind="con" path="com.android.ide.eclipse.adt.ANDROID_FRAMEWORK"/>
    

In general it would be best to have one power feature to customize/post process any generated project file in any way one wants.

@hseeberger hseeberger pushed a commit that closed this issue Apr 11, 2012
Heiko Seeberger closes #52: Customization of generated files 004329e
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment