You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@myfaces.apache.org by "Gerhard Petracek (JIRA)" <de...@myfaces.apache.org> on 2009/11/14 00:25:39 UTC

[jira] Resolved: (EXTVAL-53) adjust the package structure in view of the new storage mechanism

     [ https://issues.apache.org/jira/browse/EXTVAL-53?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]

Gerhard Petracek resolved EXTVAL-53.
------------------------------------

       Resolution: Fixed
    Fix Version/s: 1.1.3-SNAPSHOT
                   2.0.3-SNAPSHOT
                   1.2.3-SNAPSHOT

there was no community-veto

> adjust the package structure in view of the new storage mechanism
> -----------------------------------------------------------------
>
>                 Key: EXTVAL-53
>                 URL: https://issues.apache.org/jira/browse/EXTVAL-53
>             Project: MyFaces Extensions Validator
>          Issue Type: Wish
>          Components: Property Validation
>    Affects Versions: 1.2.1, 1.2.2, 1.1.1, 1.1.2
>            Reporter: Gerhard Petracek
>            Assignee: Gerhard Petracek
>             Fix For: 1.2.3-SNAPSHOT, 2.0.3-SNAPSHOT, 1.1.3-SNAPSHOT
>
>
> first of all: this change is not final until the next official release.
> everybody is allowed to express a veto!
> the classes of the new storage mechanism (see EXTVAL-49) are in the *.storage package
> some internal classes were moved to this new package.
> org.apache.myfaces.extensions.validator.crossval.CrossValidationStorage
> org.apache.myfaces.extensions.validator.crossval.CrossValidationStorageEntry
> are part of a frequently used api.
> to be consistent with the new *.storage package they should be moved to:
> org.apache.myfaces.extensions.validator.crossval.storage.CrossValidationStorage
> org.apache.myfaces.extensions.validator.crossval.storage.CrossValidationStorageEntry
> if you already implemented custom cross-validation-strategies, you just have to fix the package names in your import statements.
> please inform the community, if you have any problems with that.
> this change will be part of milestone 2. please inform us as soon as possible.
> basically you have time until the last milestone (it will be announced explicitly).
> since it's a simple refactoring step it isn't a problem to revert this change at any point very easily

-- 
This message is automatically generated by JIRA.
-
You can reply to this email to add a comment to the issue online.