C# annoyed me today, so I took revenge.
-
I currently have two instances of VS open, each using less than 200MB of RAM
Ah, but do they have solutions loaded? she posts from a laptop running two instances of VS, both with solutions loaded, one running debugging, with a total memory usage of around 800MB, so she know's it's not all that heavy on memory
-
-
Blakeyimitation fail. I would have accepted:
Liar!
or
OK? this has nnoting to do with what I'm talking about... so... you're a moron
-
I was hoping you'd finish making whatever point you were trying to make. But now I can see that you didn't have one.
MUTE
-
My point was probably about you not doing your job or somethinrg
-
Why would I do my job when that just helps people like you who aren't paying me?
-
Why would I do my job when that just helps people like you who aren't paying me?
Do you accept 'cuteness of avatar' as a currency?
-
Do you accept 'cuteness of avatar' as a currency?
Yes, but I'm not sure my definition of cute matches yours.
-
I dunno, Gradle seems to be doing a pretty good job... but I haven't had a chance to use it in a real project yet, only in some test projects.
Likewise, but I have a partially-completed task on my list to convert our Maven projects to Gradle. Looking forward to seeing that completed.
in a sense it stole one of Maven's best features (automatic dependency downloading)
Everybody got on that bandwagon, and a good thing too. Even Ant can use Ivy to do the same thing.
It kept some of the other best Maven features too, such as a mainly declarative project description instead of Ant or make's procedural build instructions.
while getting rid of its worst (pom.xml files)
I'm not infected by the irrational XML hate, I think it's an appropriate tool sometimes, but I really do like the conciseness of a Gradle build file compared to the POM. Being Groovy makes it quite flexible too, which is something Maven never quite worked out.
This is opposed to Maven, which does have plugins like this. For that matter, Eclipse has shipped with m2e since 2012 which means you can both directly create Maven projects or pull Maven projects from a SCM out of the box (assuming for the latter that you installed the appropriate SCM plugin).
I never had much success with Eclipse integration with our Maven builds. I haven't tried it in a couple of years, but last time really didn't work very well. Maybe our build is too complicated, we have a bunch of submodules and we use AspectJ compile-time weaving for example, but I would have though that both of those things would be common enough that it would work.
So I use
mvn eclipse:eclipse
to keep dependencies updated in Eclipse which means I won't be losing anything if we move to Gradle.
-
Well, apparently there is some tooling for Gradle as well. However, the plugin that lets you run gradle tasks from within Eclipse will use whichever java install you used to start Eclipse.
Unfortunately, I use a JRE to start Eclipse since JREs have an auto-updater and JDKs don't... plus you can set the JDK from within Eclipse...
-
I'm not infected by the irrational XML hate, I think it's an appropriate tool sometimes, but I really do like the conciseness of a Gradle build file compared to the POM. Being Groovy makes it quite flexible too, which is something Maven never quite worked out.
We're using Maven because we've got a custom plugin that assembles OSGi bundles into an application, which is a bit nasty otherwise. My general take is that though Maven's long-winded when you're doing something complicated, it at least manages to do it instead of needing horrible chunks of manually curated text files (what we did previously).
The XML isn't a problem. After a while, you don't see the angle brackets any more. Just blonde and brunette…
-
The XML isn't a problem. After a while, you don't see the angle brackets any more. Just blonde and brunette…
No redheads?
-
-
-