Version 1.1.0

[Fabio Da Soghe]

Hello everybody.

Yesterday I still did some other commits, to correct some minor
defects (the last one was moving an hard-coded string from the
AaptTask to the Convention object).

Now I'm using the 1.1.0-SNAPSHOT version with much satisfaction on my
real-world Android project, and others have tested it on theirs
projects with success.

I'm sorry I'm not able to execute the unit testing (as I said I have
some classpath problem but I was unable to investigate further). Could
someone (Ladislav? Matthias? Ealden?) execute them and confirm they're
passing?

Besides this, I'm ok for doing a 1.1.0 release. Now, the release
issue. If I remember well, every release requires Jason's work, for
how is configured the actual "official" repository.

Maybe we can think a more ultimate and community-oriented
configuration? I don't know how/if there is a official plugins
repository for Gradle (like Maven has), if nobody knows here I can
volunteer to ask on their mailing list for help.

What do you think?

Cheers to all,

Fabio

[Marcin Erdmann]

On Wed, Nov 30, 2011 at 11:30 AM, Fabio Da Soghe <fabiod...@gmail.com> wrote:

> Maybe we can think a more ultimate and community-oriented
> configuration? I don't know how/if there is a official plugins
> repository for Gradle (like Maven has), if nobody knows here I can
> volunteer to ask on their mailing list for help.

One of the possibilities is trying to get a codehaus project created
for the plugin - then it is possible to even get the artifact into
Maven Central. Another thing is trying to achieve the same with
Sonatype OSS repositories. And probably the worst but still possible
is to go with own github based maven repo
(http://www.sven-ehrke.de/wp_blog/?p=64). Plugin is stored in a svn
based repo at the moment so it wouldn't be much of a difference...

Marcin

[Fabio Da Soghe]

On 30 Nov, 11:43, Marcin Erdmann <erd...@gmail.com> wrote:

Those are all good option, in my opinion. Being on maven central would
mean to not be requested to add explicitly the repository from where
to fetch the plugin, right? That is, it would be unnecessary the
lines:

buildscript {
repositories {
mavenRepo(urls: 'http://jvoegele.com/maven2/')
}

Do you know how to accomplish that? Asking in mailing list of...
Gradle? Codehaus?

Anyway, thank you for the useful infos!

[Marcin Erdmann]

From what I know if you apply for a project in Codehaus and get it granted you will be in Maven central. Never did it though.

Sorry for brievity, sent from mobile.

Marcin

On 30 Nov 2011 12:04, "Fabio Da Soghe" <fabiod...@gmail.com> wrote:
On 30 Nov, 11:43, Marcin Erdmann <erd...@gmail.com> wrote:

> On Wed, Nov 30, 2011 at 11:30 AM, Fabio Da Soghe <fabiodaso...@gmail.com> wrote:
>

> > Maybe we ca...

[Matthias Käppler]

+1 for that. We're currently setting up a public Nexus repository here
at Qype that we'd like to use for our open source projects, but a repo
over at Codehaus would be fantastic.

and thanks for all the great work guys, didn't have time for testing
yet. We were busy revamping our build env to work with Maven (again),
since that was a show stopper for us. I'd like to get back to work on
the plugin at some point, but of course there is now much less drive
for me since we don't use it anymore in our production setup. Too
brittle.

2011/11/30 Marcin Erdmann <erd...@gmail.com>:

--
-Matthias

[Ealden Escañan]

Hi,

On Wed, Nov 30, 2011 at 6:30 PM, Fabio Da Soghe <fabiod...@gmail.com> wrote:

I'm sorry I'm not able to execute the unit testing (as I said I have
some classpath problem but I was unable to investigate further). Could
someone (Ladislav? Matthias? Ealden?) execute them and confirm they're
passing?

Tests are passing on my end.  Hopefully we can get 1.1.0 out soon :-)

--
Ealden Escañan
http://ealden.net

[Ealden Escañan]

Hi

On Wed, Nov 30, 2011 at 6:43 PM, Marcin Erdmann <erd...@gmail.com> wrote:

On Wed, Nov 30, 2011 at 11:30 AM, Fabio Da Soghe <fabiod...@gmail.com> wrote:

And probably the worst but still possible

is to go with own github based maven repo
(http://www.sven-ehrke.de/wp_blog/?p=64). 

One more possibility is to upload a release to GitHub as a file and refer to it, similar to the gradle-license-plugin:

https://github.com/hierynomus/gradle-plugins/blob/master/license-gradle-plugin/README.md

But I agree the best is still to get it to Maven Central.

Best regards,

[Ealden Escañan]

Hi,

On Wed, Nov 30, 2011 at 7:04 PM, Fabio Da Soghe <fabiod...@gmail.com> wrote:

Being on maven central would
mean to not be requested to add explicitly the repository from where
to fetch the plugin, right? That is, it would be unnecessary the
lines:

buildscript {
 repositories {
   mavenRepo(urls: 'http://jvoegele.com/maven2/')
 }

Yes that looks to be the case.  I just tried it with gradle-liquibase-plugin (as it is in Maven Central) and no need to add that snippet (though you do need to have mavenCentral() in there).

 

Do you know how to accomplish that? Asking in mailing list of...
Gradle? Codehaus?

I found the link below.  I can't seem to access Codehaus at the moment (just ends up being downloaded by my browser for some reason).  I haven't uploaded anything to Maven Central yet, but I can work on this for gradle-android-plugin if that's okay with everyone.

http://maven.apache.org/guides/mini/guide-central-repository-upload.html

[Fabio Da Soghe]

2011/11/30 Ealden Escañan <eal...@gmail.com>

Great to know! Excuse me but... could you describe briefly how you configured your project? When I execute 'gradle eclipse' the project gets configured but I have classpath problems (it lacks some Android library). I have the env var ANDROID_HOME set... maybe I have to set it into Eclipse and not (only) on system environment?

[Fabio Da Soghe]

2011/11/30 Ealden Escañan <eal...@gmail.com>

I found the link below.  I can't seem to access Codehaus at the moment (just ends up being downloaded by my browser for some reason).  I haven't uploaded anything to Maven Central yet, but I can work on this for gradle-android-plugin if that's okay with everyone.

http://maven.apache.org/guides/mini/guide-central-repository-upload.html

Great resource!

+1 for me, absolutely.

[Ealden Escañan]

Hi,

On Wed, Nov 30, 2011 at 11:26 PM, Fabio Da Soghe <fabiod...@gmail.com> wrote:

Great to know! Excuse me but... could you describe briefly how you configured your project? When I execute 'gradle eclipse' the project gets configured but I have classpath problems (it lacks some Android library). I have the env var ANDROID_HOME set... maybe I have to set it into Eclipse and not (only) on system environment?

I.. actually just ran `gradle developerBuild`.

I use IDEA and never really tried to run the tests from there.  Well, until now at least.  And I could run them because R.java in the test projects couldn't be generated at least by default.  I also tried with an Eclipse+ADT install and same situation with the R.java file.

To answer your question with ANDROID_HOME I didn't have to set it in a classpath definition inside Eclipse or IDEA.  For Eclipse I simply got ADT and then pointed it to to my Android SDK, and ANDROID_HOME isn't in my classpath entries.  FWIW I'm on OSX Lion and used launchctl as well which I think sets env variables in a way that Mac apps can identify them.

launchctl setenv ANDROID_HOME $ANDROID_HOME

Hope this helps,

[Ealden Escañan]

Hi,

On Wed, Nov 30, 2011 at 11:29 PM, Fabio Da Soghe <fabiod...@gmail.com> wrote:

+1 for me, absolutely.

I'll start tomorrow, as it's midnight here already :-).

[Ealden Escañan]

Hi,

On Thursday, December 1, 2011, Ealden Escañan <eal...@gmail.com> wrote:
> Hi,
>
> On Wed, Nov 30, 2011 at 11:29 PM, Fabio Da Soghe <fabiod...@gmail.com> wrote:
>>
>> +1 for me, absolutely.
>
> I'll start tomorrow, as it's midnight here already :-).
>

Is it just me, or is http://codehaus.org not accessible?

[Matthias Käppler]

yeah it's broken

2011/12/1 Ealden Escañan <eal...@gmail.com>:

--
-Matthias

[Fabio Da Soghe]

2011/11/30 Ealden Escañan <eal...@gmail.com>

Hi,

On Wed, Nov 30, 2011 at 11:26 PM, Fabio Da Soghe <fabiod...@gmail.com> wrote:

Great to know! Excuse me but... could you describe briefly how you configured your project? When I execute 'gradle eclipse' the project gets configured but I have classpath problems (it lacks some Android library). I have the env var ANDROID_HOME set... maybe I have to set it into Eclipse and not (only) on system environment?

I.. actually just ran `gradle developerBuild`.

Duh! Ok, I was misunderstanding. It works for me, too (just tried). I thought there was some way to get rid of the classpath error in Eclipse after executing 'gradle eclipse': it complains about some missing classes, all in com.jvoegele.gradle.android.hello.HelloActivity class.

Thanks for your assistance!

Cheers,

Fabio