Issue Details (XML | Word | Printable)

Key: SFOS-1043
Type: Bug Bug
Status: Resolved Resolved
Resolution: Fixed
Priority: Major Major
Assignee: Steve Loughran
Reporter: Steve Loughran
Votes: 0
Watchers: 0
Operations

If you were logged in you would be able to see more operations.
SmartFrog

CI tools are picking up the wrong version of the main distribution .zip file

Created: 04/Dec/08 04:09 PM (GMT)   Updated: 05/Jan/09 03:23 PM (GMT)
Component/s: build process
Affects Version/s: 3.17.004
Fix Version/s: 3.17.010

Time Tracking:
Not Specified

Compatibility: backwards compatible


 Description  « Hide
both hudson and CC are failing to pick up the latest version of the sf-core-install-artifacts. They are picking up the 3.15.001 version and not 3.17.002; a check in the release process intercepts this and fails the build

/home/bob/CC/SmartFrogSVN/core/build.xml:109: The following error occurred while executing this line: /home/bob/CC/SmartFrogSVN/core/release/build.xml:261: Unable to locate /home/bob/CC/SmartFrogSVN/core/release/build/ivy/lib/package-core-install/sf-core-install-3.17.002.zip; There is probably a mismatch between the version of SmartFrog that Ivy retrieved and the version that the build file is expecting, which is 3.17.002, and which is calculated by getting the SmartFrog version off the classpath. sf-core-install-artifacts=sf-core-install-3.15.001dev.zip smartfrog.classpath=/home/bob/CC/SmartFrogSVN/core/smartfrog/dist/lib/eclipse-clp-5.10.jar:/home/bob/CC/SmartFrogSVN/core/smartfrog/dist/lib/sfExamples-3.17.002.jar:/home/bob/CC/SmartFrogSVN/core/smartfrog/dist/lib/sfServices-3.17.002.jar:/home/bob/CC/SmartFrogSVN/core/smartfrog/dist/lib/smartfrog-3.17.002.jar

 All   Comments   Work Log   Change History      Sort Order: Ascending order - Click to sort in descending order
Steve Loughran added a comment - 04/Dec/08 04:11 PM (GMT)
It could be that smartfrog is no longer publishing all its artifacts correctly

[bob@brunel2 smartfrog]$ pwd
/home/bob/.ivy2/local/org.smartfrog/smartfrog
[bob@brunel2 smartfrog]$ ls -l
total 48
drwxrwxr-x 5 bob bob 4096 Apr 21 2008 3.12.031dev
drwxrwxr-x 5 bob bob 4096 Apr 22 2008 3.12.032
drwxrwxr-x 5 bob bob 4096 Apr 22 2008 3.12.033dev
drwxrwxr-x 5 bob bob 4096 May 1 2008 3.12.035dev
drwxrwxr-x 5 bob bob 4096 May 2 2008 3.12.036
drwxrwxr-x 5 bob bob 4096 May 2 2008 3.12.037dev
drwxrwxr-x 5 bob bob 4096 Jun 19 16:56 3.12.041dev
drwxrwxr-x 5 bob bob 4096 Oct 2 15:53 3.12.044
drwxrwxr-x 5 bob bob 4096 Oct 6 17:13 3.12.045dev
drwxrwxr-x 5 bob bob 4096 Oct 23 17:25 3.12.047dev
drwxrwxr-x 5 bob bob 4096 Oct 27 12:21 3.13.001dev
drwxrwxr-x 5 bob bob 4096 Nov 3 17:27 3.15.001dev


Steve Loughran added a comment - 04/Dec/08 04:13 PM (GMT)
this problem exists on the desktop too

Steve Loughran added a comment - 04/Dec/08 04:16 PM (GMT)

kernel.ivy-warn-no-ivy:
     [echo]
     [echo] No Ivy file found:
     [echo] /home/slo/Projects/SmartFrog/Forge/core/antbuild/ivy/lib/ivy-2.0.0-beta1.jar
     [echo] Artifacts created in this build will not be published.
     [echo]

Steve Loughran added a comment - 04/Dec/08 04:20 PM (GMT)
the cause of this problem was deleting the old version of ivy in SVN; core/smartfrog/build.xml had this ivy version encoded in as a property, and is configured to skip publishing artifacts if not present