Ok.. Thanks!
FYI all questions I ask are not posed to doubt your answers and
observations. Merely so I'd understand it better.
stephenconnolly wrote:
>
>
> But did you ever ask why it was OK to rebuild the artifact in those
> environments?
>
Actually, yes. The answer to that usually has something to do with building
on the target platform. I've worked on one project where we had a
professional 'build manager'. Yet he worked with unit tests and integration
tests using Teamcity with build-test-fail/succes principles.
stephenconnolly wrote:
>
>
> How do you know that other SCM changes have not crept in? The contents
> of that EAR have different checksums too, so now we have to do a diff
> on the wars and jars in the ear... oh and the jars in the wars are
> also different... so now we have to do a diff of all the .class files
> to show that they are the same.... and you have code that references
> File.separator and you have optimization turned on in your compiler
> and this build was on windows while that build was on linux oooops!
> these artifacts behave differently... the one on windows won't work on
> linux but the one on linux works on windows except when it launches
> the bat file that it writes... eeek!!! if only we had a repeatable
> consistant build that we just passed through all the environments, we
> would have caught this earlier and either turned off the optimization
> in javac, or used System.getProperty("file.separator").
>
I thought that was the whole point of pulling a tag and rebuilding that tag
using profiles on a machine with a contineous build tool such as Hudson or
Teamcity. At any rate, that way we are absolutely sure that other SCM
changes have not crept in, if the dependencies in the local/remote repo are
ok.
Though I do have to admit that I've seen charset problems rather often.
That might have something to do with this kind of building strategy, right?
stephenconnolly wrote:
>
> Correction, you have yet to work on a project where you were aware of
> the work that went into showing why rebuilding was OK, or where a
> quality team understood the risk
>
Fair enough, although I do doubt the amount of work that's being put in on
that account.
--
View this message in context:
http://maven.40175.n5.nabble.com/Reasonable-use-of-profiles-tp3300650p3304419.html
Sent from the Maven - Users mailing list archive at Nabble.com.
---------------------------------------------------------------------
To unsubscribe, e-mail: [email protected]
For additional commands, e-mail: [email protected]
