Next Soot Release

[ericbodden]

This is a new "meta entry" discussing which bugs and enhancement should be addressed before the next Soot release, which we plan for mid-September 2014.

[ericbodden]

We should tag all items to be included in 2.6.0 with the appropriate milestone tag Soot-2.6.0, as seen on the right.

[StevenArzt]

Bugs that need to be fixed:

1. Dexpler fails on the official CNN app

Things that at least need to be investigated:

1. Original variable names are not always properly assigned in ASM. Not a functional issue, but may confuse people.

[ericbodden]

Steven can you please open issues for both and assign them the appropriate milestone? Thanks!

[raulcf]

Do you have a place with the release candidate features?
In particular, is there any change concerning Java 8?
Thanks!

[ericbodden]

@raulcf We should add basic Java 8 support before the release. I have added the appropriate milestone tag to this issue:
#225

We will not be able to implement this advanced support before the release, I am afraid:
#226
Finishing it before would require external man power.

[raulcf]

That sounds great
Thanks!

Raul
PhD student, office 346
Large-Scale Distributed Systems Group
Department of Computing
Imperial College London

---

From: Eric Bodden [notifications@github.com]
Sent: Friday, August 08, 2014 11:00 AM
To: Sable/soot
Cc: Raul
Subject: Re: [soot] Next Soot Release (#231)

@raulcfhttps://github.com/raulcf We should add basic Java 8 support before the release. I have added the appropriate milestone tag to this issue:
#225#225

We will not be able to implement this advanced support before the release, I am afraid:
#226#226
Finishing it before would require external man power.

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/231#issuecomment-51583550.

[ericbodden]

I have added a page to the wiki which describes the release process:
https://github.com/Sable/soot/wiki/Preparing-a-new-Soot-release

This is a live document. It's still outdated (copied from the old Wiki), but I am working on updating it.

[sertel]

Hi,

I'm currently trying to use Soot in one of my projects and would be very happy about a new release coming soon. It would be really great if you could deploy the release to Maven Central or Clojars to remove the hassle with the dependencies to Jasmin etc. and allow for a smooth integration. Maybe it is a good idea to think about switching the build system to Leiningen to make the release process much easier.

When do you think that you have the new release ready?

Cheers,
Sebastian

[raulcf]

Actually having the library published to Maven would be great!

Raul
PhD student, office 346
Large-Scale Distributed Systems Group
Department of Computing
Imperial College London

---

From: sertel [notifications@github.com]
Sent: Tuesday, January 13, 2015 4:20 PM
To: Sable/soot
Cc: Raul
Subject: Re: [soot] Next Soot Release (#231)

Hi,

I'm currently trying to use Soot in one of my projects and would be very happy about a new release coming soon. It would be really great if you could deploy the release to Maven Central or Clojars to remove the hassle with the dependencies to Jasmin etc. and allow for a smooth integration. Maybe it is a good idea to think about switching the build system to Leiningen to make the release process much easier.

When do you think that you have the new release ready?

Cheers,
Sebastian

—
Reply to this email directly or view it on GitHubhttps://github.com//issues/231#issuecomment-69770972.

[StevenArzt]

There is an ongoing discussion about dependency management and maven in #44, so please keep this thread strictly related to the Soot 2.6 release.

@sertel I would just download the latest nightly build from our web site and integrate that into your build process. We have a fully-built JAR file (soot-trunk.jar) that contains all required dependencies, so you don't need to care about Jasmin, JastAdd, etc.

[sertel]

Hi Steven,

thanks for the pointer to the nightly jar!
However, in order to ship this with my software it would really be great to have a release in a public repo. Often this is required by companies to verify the software.

Cheers,
Sebastian.

[sertel]

I just saw that there is already an open issue on that matter. See issue #42.

[pnest]

Are there any movements toward release?

[StevenArzt]

It seems to me as if we have already had new versions from the Maven builds, but they have not been published here on Github as a release (https://github.com/Sable/soot/releases).

@mbenz89 Could you shed some light here?

[mbenz89]

The 3.0.1 release which corresponds to the master branch can be acquired here.

I'll add it to GitHub in case of interest.

[pnest]

Great! It would be nice to have releases at github as well.
Have you had any tags since soot-2.5.0? As it is the last one on github