|
Quick Lists
|
|
Bug ID:
|
6559161
|
|
Votes
|
0
|
|
Synopsis
|
(modinit) Handle invalid VersionConstraint during module initialization
|
|
Category
|
java:module
|
|
Reported Against
|
|
|
Release Fixed
|
7(beta)
|
|
State
|
10-Fix Delivered,
bug
|
|
Priority:
|
5-Very Low
|
|
Related Bugs
|
|
|
Submit Date
|
18-MAY-2007
|
|
Description
|
> what happens if an invalid version constraint is declared in the source, e.g.
>
> @VersionConstraint("X")
> import foo;
>
> ?
>
> How/when should we handle this at runtime? Ignore the version constraint?
See Section 5.7. Having an invalid version constraint would mean the module definition is invalid. Ideally, the jam file should be rejected by the repository at deployment time. If this is not possible, we should simply make the module initialization to fail at runtime.
Posted Date : 2007-05-18 01:07:28.0
|
|
Work Around
|
N/A
|
|
Evaluation
|
Invalid version constraint shouldcause module initialization to fail.
Posted Date : 2008-03-04 22:21:14.0
This is already handled in the existing implementation. Added test case.
Posted Date : 2008-03-06 06:39:35.0
|
|
Comments
|
PLEASE NOTE: JDK6 is formerly known as Project Mustang
|
|
|
|
