Project

General

Profile

Bug #5272

kepler 2.1 suite can not be started using 'ant run'

Added by jianwu jianwu over 8 years ago. Updated over 8 years ago.

Status:
Resolved
Priority:
Normal
Assignee:
Category:
build system
Target version:
Start date:
01/12/2011
Due date:
% Done:

0%

Estimated time:
Bugzilla-Id:
5272

Description

Today, one partner tried to start Kepler 2.1 through build-area and failed.

We first tried the build-area at https://code.kepler-project.org/code/kepler/releases/release-branches/build-area-2.0/. The error message is:
<huynh@enea142 ~/SANDIEGOIII/kepler_2.1/build-area-2.0>ant run
Buildfile: build.xml

BUILD FAILED
/afs/efda-itm.eu/isip/user/huynh/SANDIEGOIII/kepler_2.1/build-area-2.0/build.xml:4: The following error occurred while executing this line:
/afs/efda-itm.eu/isip/user/huynh/SANDIEGOIII/kepler_2.1/build-area-2.0/settings/taskdefs.xml:114: typedef class org.kepler.build.RegisterModule cannot be found

Total time: 0 seconds

We switched to the build-area in kepler trunk, it can compile Kepler 2.1 but it get other exceptions:

JVM Memory = 5m 512m
[run] /afs/efda-itm.eu/isip/user/huynh/SANDIEGOIII/kepler_2.1
[run] java.io.FileNotFoundException: /afs/efda-itm.eu/isip/user/huynh/SANDIEGOIII/kepler_2.1/build-area/registry.txt (No such file or directory)
[run] at java.io.FileInputStream.open(Native Method)
[run] at java.io.FileInputStream.<init>(FileInputStream.java:106)
[run] at java.io.FileReader.<init>(FileReader.java:55)
[run] at org.kepler.build.project.RepositoryLocations.readModuleRegistryHelper(RepositoryLocations.java:75)
[run] at org.kepler.build.project.RepositoryLocations.readModuleRegistry(RepositoryLocations.java:62)
[run] at org.kepler.build.project.RepositoryLocations.getLocation(RepositoryLocations.java:96)
[run] at org.kepler.build.modules.Module.<init>(Module.java:152)
[run] at org.kepler.build.modules.Module.<init>(Module.java:204)
[run] at org.kepler.build.modules.ModulesTxt.readHelper(ModulesTxt.java:165)
[run] at org.kepler.build.modules.ModulesTxt.read(ModulesTxt.java:137)
[run] at org.kepler.build.modules.ModulesTxt.init(ModulesTxt.java:58)
[run] at org.kepler.build.modules.ModuleTree.init(ModuleTree.java:96)
[run] at org.kepler.build.modules.ModuleTree.instance(ModuleTree.java:86)
[run] at org.kepler.configuration.ConfigurationManager.loadConfiguration(ConfigurationManager.java:414)
[run] at org.kepler.configuration.ConfigurationManager.<init>(ConfigurationManager.java:87)
[run] at org.kepler.configuration.ConfigurationManager.getInstance(ConfigurationManager.java:116)
[run] at org.kepler.configuration.ConfigurationManager.getInstance(ConfigurationManager.java:105)
[run] at org.kepler.modulemanager.RepositoryLocations.initReleaseLocation(RepositoryLocations.java:24)
[run] at org.kepler.modulemanager.RepositoryLocations.getReleaseLocation(RepositoryLocations.java:18)
[run] at org.kepler.Kepler.main(Kepler.java:89)
[run] java.lang.NullPointerException
[run] at org.kepler.build.project.RepositoryLocations.getLocation(RepositoryLocations.java:98)
[run] at org.kepler.build.modules.Module.<init>(Module.java:152)
[run] at org.kepler.build.modules.Module.<init>(Module.java:204)
[run] at org.kepler.build.modules.ModulesTxt.readHelper(ModulesTxt.java:165)
[run] at org.kepler.build.modules.ModulesTxt.read(ModulesTxt.java:137)
[run] at org.kepler.build.modules.ModulesTxt.init(ModulesTxt.java:58)
[run] at org.kepler.build.modules.ModuleTree.init(ModuleTree.java:96)
[run] at org.kepler.build.modules.ModuleTree.instance(ModuleTree.java:86)
[run] at org.kepler.configuration.ConfigurationManager.loadConfiguration(ConfigurationManager.java:414)
[run] at org.kepler.configuration.ConfigurationManager.<init>(ConfigurationManager.java:87)
[run] at org.kepler.configuration.ConfigurationManager.getInstance(ConfigurationManager.java:116)
[run] at org.kepler.configuration.ConfigurationManager.getInstance(ConfigurationManager.java:105)
[run] at org.kepler.modulemanager.RepositoryLocations.initReleaseLocation(RepositoryLocations.java:24)
[run] at org.kepler.modulemanager.RepositoryLocations.getReleaseLocation(RepositoryLocations.java:18)
[run] at org.kepler.Kepler.main(Kepler.java:89)
[run] Exception in thread "main" java.lang.RuntimeException: Could not load configuration: null
[run] at org.kepler.configuration.ConfigurationManager.<init>(ConfigurationManager.java:93)
[run] at org.kepler.configuration.ConfigurationManager.getInstance(ConfigurationManager.java:116)
[run] at org.kepler.configuration.ConfigurationManager.getInstance(ConfigurationManager.java:105)
[run] at org.kepler.modulemanager.RepositoryLocations.initReleaseLocation(RepositoryLocations.java:24)
[run] at org.kepler.modulemanager.RepositoryLocations.getReleaseLocation(RepositoryLocations.java:18)
[run] at org.kepler.Kepler.main(Kepler.java:89)

BUILD FAILED
/afs/efda-itm.eu/isip/user/huynh/SANDIEGOIII/kepler_2.1/build-area/build.xml:36: Java returned: 1

History

#1 Updated by David Welker over 8 years ago

I will look into this bug soon. However, it certainly is not a release blocker for 2.2. Reclassifying.

#2 Updated by jianwu jianwu over 8 years ago

It might not be a block for kepler 2.2 installation package release. But many users download kepler based on release-branches so that they can build their modules on it. Currently, users can not start Kepler 2.1 after checking out from 2.1 release-branch. If we release kepler 2.2 with this bug, users still can not start Kepler 2.1 using 'ant run'. It will make bad back compatibility of Kepler.

#3 Updated by Jing Tao over 8 years ago

Another user tried to build kepler execution eninge base on kepler-2.1
but he get the same error.

#4 Updated by Derik Barseghian over 8 years ago

Increasing importance, this has been getting in my way, and is likely to come up again soon for the two users who have been recently been emailing the list.

#5 Updated by David Welker over 8 years ago

Fixed.

The trunk build can now run the kepler-2.1 branch.

I also branched the build (to build-area-2.1) so that we always have a build that can run Kepler 2.1 around. In the future, I expect that the trunk build will not be able to build Kepler 2.1, but for now, it is more convenient to keep the two compatible even though this requires some otherwise unnecessary files to remain in the build.

#6 Updated by Redmine Admin about 6 years ago

Original Bugzilla ID was 5272

Also available in: Atom PDF