Re: [wtp-releng] Build Breaker 5

[David M Williams <david_williams@xxxxxxxxxx>]

Er, thanks for the warning ... I've
been spending the last 6 hours trying to figure out what's going on ...
I eventually had to go "way" back to the "last good build",
proved that still built, then, via compare, etc., take out what I could
that mentioned JSF ... this was urgent because he had to "get up on"
all the right RC versions for our RC declaration tomorrow! 

So ... in future, let's make a pact
that we not put thngs in 'head' until they are ready to go. Perhaps use
a little side branch ... you could still build with that to get the kinks
worked out, but then if one of the other of us has another (much smaller)
build update to make we easily could. 

Along these same lines ... I still think
there is not the correct seperation between the "build" code,
and some of the other tasks we have to do .. api checking, performance
tests, etc. 
The problem is, that I think its risky
to have "near build" code changing at the same time we are trying
to produce a criticial build. 
In other words, it makes my life much
harder. 
So, those of you that do other near-build
tasks ... can you please document what you are doing and why its completely
safe? 
Or, better yet ... but it else where
... there is no reason for it to be in releng.builder as far as I can tell
... and that is the critical ones for our builds .... because that one
is unversioned. 

Naci, Jeffrey, would you prefer I move
the "build machine" scripts out of releng.builder?

Naci Dai <naci.dai@xxxxxxxxxxxxx>
Sent by: wtp-releng-bounces@xxxxxxxxxxx

05/05/2006 01:09 AM

Please respond to
Webtools releng discussion list <wtp-releng@xxxxxxxxxxx>

To	Webtools releng discussion list <wtp-releng@xxxxxxxxxxx>
cc	Raghu Srinivasan <raghunathan.srinivasan@xxxxxxxxxx>
Subject	Re: [wtp-releng] Build Breaker 4

Raghu and I am trying integrate jsf into the wtp build
stream, so you may see some problems today and tomorrow on the I-Builds

John, I was SO excited to see you actually reducing our plugins!  :)
But .. looks like maybe you forgot to fix and release the isv doc custom
build scripts? 
(I only post this here, to help us all remember in the future .. not _only_
to embarrass John :) 

[build-wtp-wst-sdk] /shared/webtools/build-wtp-S/workdir/plugins/org.eclipse.wst.doc.isv/build.xml:31:
The following error occurred while executing this line:
[build-wtp-wst-sdk] /shared/webtools/build-wtp-S/workdir/plugins/org.eclipse.wst.doc.isv/javadoc.xml:49:
/shared/webtools/build-wtp-S/workdir/plugins/org.eclipse.wst.common.navigator.views/src-navigator
not found.

---

_______________________________________________
wtp-releng mailing list
wtp-releng@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-releng
  
_______________________________________________
wtp-releng mailing list
wtp-releng@xxxxxxxxxxx
https://dev.eclipse.org/mailman/listinfo/wtp-releng