All my 1.10.2 Mods on the same workspace - Is it possible?

[American2050]

Well, the title pretty much already explains it.

Is there any way to have one workspace set up to work with for example MC 1.10.2 and have all my mods there, and be able to work on them and launch them individually? How would it be done?

 

Thanks a lot.

[Ugdhar]

If you're using eclipse, just import each project into the same workspace, and each project will have it's own run configurations.

[American2050]

  On 6/7/2017 at 10:17 PM, Ugdhar said:

If you're using eclipse, just import each project into the same workspace, and each project will have it's own run configurations.

Expand  

Thanks, I will try it, yes I'm using Eclipse

[Draco18s]

When I was developing several related mods (one of which was a library shared by the other four) I used one workspace, but different gradle commands to build them as separate jar files. 

 

For unrelated mods, I'd suggest Ugdhar's method. 

[BenignBanana]

Since I'm using a multi module project (in IntelliJ, but this should apply equally to Eclipse), I thought I'd chime in. I'd recommend putting them into subdirectories as subprojects in one main gradle root. So you have your root with a common build.gradle, and a settings.gradle with just

include 'Mod1', 'Mod2'

and then have a separate build.gradle in each mod folder. This allows you to trigger a full build/setupDecompWorkspace for all mods at once, along with making dependencies much easier. You can put all common dependencies and repositories in the root's build.gradle. And of course you can still trigger builds etc for each individual mod.

[Alexiy]

  On 6/22/2017 at 7:44 AM, BenignBanana said:

Since I'm using a multi module project (in IntelliJ, but this should apply equally to Eclipse), I thought I'd chime in. I'd recommend putting them into subdirectories as subprojects in one main gradle root. So you have your root with a common build.gradle, and a settings.gradle with just

include 'Mod1', 'Mod2'

and then have a separate build.gradle in each mod folder. This allows you to trigger a full build/setupDecompWorkspace for all mods at once, along with making dependencies much easier. You can put all common dependencies and repositories in the root's build.gradle. And of course you can still trigger builds etc for each individual mod.

Expand  

I have this layout too, although there is a slight problem. Whenever I build inner mod, it messes up something in root project, so it becomes unusable in the game (getting abstract method errors and such), so I must build it from terminal (./gradlew :build) to make it usable again. I haven't investigated the issue much, ain't nobody got time for that.

[BenignBanana]

  On 6/22/2017 at 5:00 PM, Alexiy said:

I have this layout too, although there is a slight problem. Whenever I build inner mod, it messes up something in root project, so it becomes unusable in the game (getting abstract method errors and such), so I must build it from terminal (./gradlew :build) to make it usable again. I haven't investigated the issue much, ain't nobody got time for that.

Expand  

That's odd, it's working just fine for me. Are you using Eclipse or IntelliJ? I know in IntelliJ sometimes gradle gets a bit desynced so you have to manually refresh it from the Gradle tool window. I've never worked with gradle in eclipse so if you're using that I doubt I could help you much

[Alexiy]

  On 6/23/2017 at 12:40 AM, BenignBanana said:

That's odd, it's working just fine for me. Are you using Eclipse or IntelliJ? I know in IntelliJ sometimes gradle gets a bit desynced so you have to manually refresh it from the Gradle tool window. I've never worked with gradle in eclipse so if you're using that I doubt I could help you much

Expand  

I'm using Intellij and I hate eclipse.