Visual Studio non-solution



  • @tar said:

    knock up

    :giggity:



  • @dkf said:

    Workspace configurations tend to contain paths and stuff like that.

    You can get around that by mandating that all developers put their workspaces and tools in the same location. That can be possible in a controlled corporate environment, but as you say, Bad Idea.

    @dkf said:

    Maven is a very scary ecosystem to work with at first.

    Yes, Maven is all or nothing. Maven's way or the highway. We've been using it for seven or eight years but we have very recently moved to Gradle for our in-house projects. Maven was far better than the alternatives at the time we started using it, which was pretty much just Ant, but the Maven shackles have started to chafe.


  • Discourse touched me in a no-no place

    @another_sam said:

    the Maven shackles have started to chafe

    I'm curious, how are they proving to be a problem? I've yet to have problems with working that way (well, as far as I'm aware) but it might be useful to have some idea of what to watch out for.


Log in to reply