cordova-dev mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From Joe Bowser <>
Subject Re: .classpath in Android platform in 3.5.0
Date Fri, 23 May 2014 15:27:26 GMT
I believe this was regarding the .classpath that's in the framework
that is bundled with your generated project, not YOUR .classpath.  I
personally think we should ignore all .classpath files, since we
already have, and this stupid file changes on
everyone's machine.   Every time I have to pull down the repo, I have
to do go a git reset --HARD to purge the classpath changes on my
version of Cordova.

Also, does anyone know of a way to be build-tool agnostic? I'm very
uninterested in the impending Gradle vs Ant war.

On Fri, May 23, 2014 at 8:22 AM, sebb <> wrote:
> On 23 May 2014 16:03, Victor Sosa <> wrote:
>> Hi all.
>> I thought one features going in in Cordova 3.5 is that Android now has a
>> .classpath file for Eclipse projects so when importing, it will have the
>> Java classpath automatically configured [1].
>> I'm using Cordova 3.5.0-0.2.4 and I can only see .project in
>> platforms/android.
>> Is my assumption correct? or am I missing something here?
>> Thanks in advance
> Note that the Eclipse files .project and .classpath are unfortunately
> not portable in general, as they contain references that may depend on
> the local host. Also some developers may wish to add additional items
> (e.g. links to Javadoc/source).
> If the Cordova project wants to provide sample files for Eclipse
> users, then may I suggest that these are given different paths?
> For example, the Tomcat project stores Eclipse classpath and project files here:
> Each developer can then merge the contents with their local versions.
>> [1]
>> --
>> Victor Sosa
>> Guadalajara, Jalisco

View raw message