Re: [aspectj-dev] 1.1.0 release

["George Harley1" <GHARLEY@xxxxxxxxxx>]

Hi Wes,

The fault is all mine. Here is what happened....

I started off trying to use the build/release/build.xml script yesterday (following the instructions in build/release/readme.txt) and immediately encountered a problem with the "install" target. Namely, when I ran the following...

c:\ > ant install -Dskip.cvs=true -Daspectj.modules.dir=../.. -Djava13.home=c:\sun-jdk-131-08 -Djava14.home=C:\sun-jdk-141-02

...then after a minute or so I got a fail message as pasted in the fragment below ...

- - - - - - - - - - - - - - - - - - - - - - - - 

do-write-javahome-file:
[propertyfile] Updating property file: C:\Eclipse-21\eclipse\workspace\build\release\javahome.props.tmp

init-variables:

do-run-ant:
     [echo]
     [echo]   do-run-ant dir C:\Eclipse-21\eclipse\workspace\build
     [echo]      file/target -f build.xml build-testing-jars
     [echo]          options  -Dtrim.testing.default=false
     [echo]           output C:\Eclipse-21\eclipse\workspace\aj-build\logs\build-build-testing-jars-13.txt

BUILD FAILED
file:C:/Eclipse-21/eclipse/workspace/build/release/build.xml:550: Java returned: 1

- - - - - - - - - - - - - - - - - - - - - - - - 

The bottom of the build-build-testing-jars-13.txt output file contained the following....

- - - - - - - - - - - - - - - - - - - - - - - -

init-version:

build-module:
  [ajbuild] unable to build <bad BuildSpec -  baseDir=C:\Eclipse-21\eclipse\workspace jarDir=C:\Eclipse-21\eclipse\workspace\aj-build\jars buildConfig=verbose> using script: C:\Eclipse-21\eclipse\workspace\build\build.xml

BUILD FAILED
file:C:/Eclipse-21/eclipse/workspace/build/build.xml:175: error building module build

Total time: 1 second

- - - - - - - - - - - - - - - - - - - - - - - -

I retried this several times but always got the same outcome. Using the default target did not change matters. I had seen behaviour like this earlier this week when I tried using the script but did not have the time to follow it up with you. This was all happening early-afternoon (UK time) yesterday and I was faced with the choice of either trying to start drilling down into the mechanics of build/release/build.xml (estimated duration : unknown) or else biting the bullet and doing a manual 1.1.0 build and test (estimated duration : 1 hour tops). I opted for the latter since I had specifically set aside the time for cutting the release yesterday afternoon and, because of other work commitments, could not be sure that the opportunity would come my way again this week. 

Maybe you could spare some time today to help me iron out the difficulties that I'm seeing running the new release script ? Please let me know your availability and I could call you. 

Best regards,
George
________________________________________
George C. Harley

Wes Isberg <wes@xxxxxxxxxxxxxx> Sent by: aspectj-dev-admin@xxxxxxxxxxx 03/06/2003 23:50 Please respond to aspectj-dev

To:        aspectj-dev@xxxxxxxxxxx         cc:                 Subject:        Re: [aspectj-dev] 1.1.0 release

Thanks for doing this, George.  I'm confused, though, because it looks 
like you ran through the process manually.  To release, we have to use 
the release/build.xml script.  In retrospect, I see that I didn't make 
sure we closed the loop on this earlier, but I've said enough that this 
shouldn't be a surprise.  If necessary we can all discuss further how 
this confusion happened and whether the script is wise or necessary, but 
I suspect we'd agree, and it's easier just to run it.

I also wanted to make sure no one assumed that the person doing the 
release is doing the manual testing.  We should all look at the 
completed checklist and either do undone tests in our areas or assume 
the risk, with notice to the others (preferably in the checklist itself).

A script is helpful in part as a way to add test requirements to a 
release, particularly after seeing a release get out untested in some 
respect.  Feel free to add to the script even/esp. in a release cycle 
(except that if you break it you might have to do the release).  In any 
case, additional testing should not invalidate prior testing, so no 
release should be delayed for or by an upgrade.  On that note, one thing 
I wanted to add was a link checker.  I didn't find one last night, but 
I'll try to write one today because I found a broken link.  I also plan 
to add per-example ant runs and enable the JDK 1.1 testing.

Thanks -
Wes