Groups | Search | Server Info | Keyboard shortcuts | Login | Register [http] [https] [nntp] [nntps]

Groups > linux.debian.maint.java > #8921

Re: building android-studio

Show all headers | View raw

[Multipart message — attachments visible in raw view] - view raw

Hi,

no need to CC me. I'm subcribed to debian-java.

On Fri, 04. Mar 08:23 toogley@mailbox.org wrote:
> Hey,
>
> > Probably you don't have to package the whole IntelliJ IDE. Most recently
> > I have packaged intellij-annotations because I needed it as a
> > build-dependency for android-platform-tools-base. Especially for large
> > and complex projects like IntelliJ (last time I checked I noticed that
> > the source release bundles ~500 jars), it is often simpler to package
> > certain parts from maven central instead of trying to build everything.
>
> Yeah, this sound reasonable. But how do i find out in what packages i should
> split intellij? E.g. just by folders like RegExpSupport
> (https://github.com/JetBrains/intellij-community/tree/master/RegExpSupport),
> Debugger(https://github.com/JetBrains/intellij-community/tree/master/java/debugger)
> and write my own gant/ant build scripts for that? How would i import new
> versions then? I mean, should i just continue with the normal debian/ upstream/
> branch split and pull all changes in that particular folder (e.g. with
> http://stackoverflow.com/a/13738951)?
>

Your first step should be to determine what build-dependencies are
required for android studio. Then you can use for instance
mvnrepository.com and search for jar files, group ids or artifacts.

http://mvnrepository.com/artifact/com.intellij/annotations

Not all IntelliJ parts are packaged as Maven artifacts though. Also I
would recommend to package releases from

https://github.com/JetBrains/intellij-community/releases

A tarball release is a well defined snapshot and it is usually much simpler
to track those releases. I don't know if they provide separate
repositories / release tarballs for their subprojects but I wouldn't go
for writing my own build scripts unless there is really no alternative.
The maintenance burden will increase over time and at some time people
will stop rewriting the scripts whenever upstream changes something. Try
to avoid that.

Regards,

Markus

Back to linux.debian.maint.java | Previous | Next — Previous in thread | Find similar

Thread

building android-studio toogley <toogley@mailbox.org> - 2016-03-01 19:10 +0100
  Re: building android-studio 殷啟聰 <seamlikok@gmail.com> - 2016-03-02 10:40 +0100
    Re: building android-studio toogley@mailbox.org - 2016-03-04 08:30 +0100
      Re: building android-studio toogley@mailbox.org - 2016-03-04 08:50 +0100
        Re: building android-studio Hans-Christoph Steiner <hans@at.or.at> - 2016-03-04 19:00 +0100
          Re: building android-studio toogley@mailbox.org - 2016-05-27 22:40 +0200
  Re: building android-studio Markus Koschany <apo@debian.org> - 2016-03-02 13:40 +0100
    Re: building android-studio toogley@mailbox.org - 2016-03-04 08:30 +0100
      Re: building android-studio Markus Koschany <apo@debian.org> - 2016-03-04 09:20 +0100

csiph-web