| Re: [ide-dev] News about Android Studio |
> Does not help much BuildShip gets opened up if JDT continues to want to have one class path per project.
JDT neither "insists" nor "want" this, you know that, we discussed it when you visited us. It's just a lot of work which no one was willing to invest so far. The good news is, that we probably have to do something in that area for the Java 9 module support.
Dani
From:
"Max Rydahl Andersen"
<manderse@xxxxxxxxxx>
To:
"Discussions about
the IDE" <ide-dev@xxxxxxxxxxx>
Cc:
Etienne Studer <etienne@xxxxxxxxxx>
Date:
08.12.2015 13:52
Subject:
Re: [ide-dev]
News about Android Studio
Sent by:
ide-dev-bounces@xxxxxxxxxxx
On Wed, Dec 2, 2015 at 4:01 PM, Doug Schaefer dschaefer@xxxxxxxwrote:
I haven¹t really looked at Buildship other than the EclipseCon
presentations so I¹ll have to assume you¹re right. But to get started and
remove this dependency as an issue until it¹s ready, we may have to come
up with alternatives to make sure we have something by Neon.
AFAIK Redhat have already a patch that would allow that
projects
configure Gradle accordingly. You can check with Max. If that is true,
we ONLY ;-) need to motivate Gradleware to accept patches. Currently
most PR on Github remain untouched.
We had to pause that development since Gradleware currently
don't seem to
want to open that part up and thus everything currently have to be done
as patches into buildship/gradle. Thus we can't currently justify doing
that work for Neon since most we need for now is Maven based.
cc'ed Etienne so he can see the interest from Android is
there too and not
limited to our WTP ideas.
For Android (and Gradle) I think the issue about JDT insisting
on having one
class path per project is the next-biggest inhibitor on having good progress.
Does not help much BuildShip gets opened up if JDT continues
to want to
have one class path per project.
/max
Best regards, Lars
On 2015-12-01, 11:38 AM, "ide-dev-bounces@xxxxxxxxxxxon behalf of Lars
Vogel" <ide-dev-bounces@xxxxxxxxxxx on behalf of lars.vogel@xxxxxxxxxxx>
wrote:
Hi Mickael,
I use Android Studio on a regular basis and it seems to
me that they
moving more and more functionality to Gradle. AFAIK the target is
still to stay as much independent as possible from the IDE and
delegate as much as possible to the build system.
Once the Gradle tooling has been extended to support Android,
we
(Eclipse) should be a good alternative again for Android development.
Android Studio feel to us and our customers relatively buggy and slow.
Unfortunately the Eclipse Gradle project seems currently
slow
(https://github.com/eclipse/buildship/commits/master),
not sure if
they planning to work on Android support in the near future.
Best regards, Lars
On Mon, Nov 30, 2015 at 3:29 PM, Mickael Istria mistria@xxxxxxxxxx
wrote:
Android Studio recently released a new version. This good
video covers
some
nice features https://www.youtube.com/watch?v=Y2GC6P5hPeA#t=770.
Nothing
very new, no big uber-powerful feature changing the game. This video
is
also
a good opportunity to see the completion, quick-fixes and templates of
IDEA
in action. The features I find the most interesting are all already
logged
in Bugzilla and were already discussed there, so I won't get into
details.
There performance tools seem very good. It's IMO something we're
missing in
Eclipse IDE since TPTP was abandonned. As far as I remember, none of
the
main Eclipse IDE packages provide a way to profile or monitor
applications
under development easily. That's a major missing feature compared to
Android
Studio. However, it simply seems like it's not one our community
wishes
to
invest into, probably because it's still not a top-priority in most
end-users projects.
However, my lack of general experience with Gradle nor C++ make me
unable to
evaluate what's good/bad in Android Studio compared to Eclipse
BuildShip or
CDT.
For Android, it's interesting how they answer to the 1st
question, ie
most
of the tools about Android development will move only to the IDE. It
seems
to mean that the SDK and IDE are going to be merged at some point, and
that
the IDE will be the single entry-point for development. That means
that
it's
a lot of thing to duplicate in Eclipse IDE if most other tools are
going to
be dropped.
Another interesting one is about sharing project settings, for the
project
specific configuration such as the "structural replace". It's
actually
an
important question when you add into the IDE some checks that are not
possible to "externalize" in the build or in independent tools.
They
do
encourage to share the project specific files, like we usually do for
Eclipse IDE:
http://www.slideshare.net/AurelienPupier/committing-ide-meta-files-misc
on
ceptions-misunderstandings-and-solutions
Mickael Istria
Eclipse developer at JBoss, by Red Hat
My blog - My Tweets
ide-dev mailing list
ide-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or
unsubscribe
from
this list, visit
https://dev.eclipse.org/mailman/listinfo/ide-dev
--
Eclipse Platform UI and e4 project co-lead
CEO vogella GmbH
Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (032) 221739404, Email: lars.vogel@xxxxxxxxxxx,
Web:
http://www.vogella.com
ide-dev mailing list
ide-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/ide-dev
ide-dev mailing list
ide-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/ide-dev
--
Eclipse Platform UI and e4 project co-lead
CEO vogella GmbH
Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (032) 221739404, Email: lars.vogel@xxxxxxxxxxx,
Web:
http://www.vogella.com
ide-dev mailing list
ide-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/ide-dev
ide-dev mailing list
ide-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/ide-dev
--
Eclipse Platform UI and e4 project co-lead
CEO vogella GmbH
Haindaalwisch 17a, 22395 Hamburg
Amtsgericht Hamburg: HRB 127058
Geschäftsführer: Lars Vogel, Jennifer Nerlich de Vogel
USt-IdNr.: DE284122352
Fax (032) 221739404, Email: lars.vogel@xxxxxxxxxxx,
Web: http://www.vogella.com
ide-dev mailing list
ide-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/ide-dev
/max
http://about.me/maxandersen_______________________________________________
ide-dev mailing list
ide-dev@xxxxxxxxxxx
To change your delivery options, retrieve your password, or unsubscribe
from this list, visit
https://dev.eclipse.org/mailman/listinfo/ide-dev