Issue (View Online)

Key: NXP-1423
Issue Type: Bug Bug
Status: Open Open
Priority: Critical Critical
Assignee: Bogdan Stefanescu
Reporter: Olivier Grisel
Original Estimate: 4 hours
Remaining Estimate: 4 hours

Operations

View all
View comments
View history
NXRuntime should log configuration errors and stop its deployment instead of hiding problems 
Updated: 06/08/07 14:02   Created: 06/08/07 14:01  

The following comment has been added to this issue: [ Permlink ]

Author: Olivier Grisel
Date: 06/08/07 14:02
Comment:
Please note that this problem was already raised by NXP-568 but is different from NXP-172 .

Project: Nuxeo Enterprise Platform 5
Components: Runtime
Affects Versions: 5.1.RC
Fix Versions: 5.2 M1

 Description   
If a syntax error is found in a MANIFEST.MF file, a extension point definition or contribution file, or a MANIFEST.MF pointing to a non existing configuration file, NXRuntime should log a meaningful message at ERROR level and stop trying to deploy a buggy nuxeo app.

Otherwise the developer has to wait a long deployment time only to get an inconsistently deployed application losing time hunting for applicative bugs that are in fact invisible and undirect consequences of typos in configuration files.

This has a major negative impact on productivity for nuxeo developer / integrators.

This message was automatically generated by Atlassian JIRA Enterprise Edition, Version: 3.10-260 - Bug/feature request.
If you think it was sent incorrectly, contact one of this server's administrators.

_______________________________________________
ECM-tickets mailing list
[email protected]
http://lists.nuxeo.com/mailman/listinfo/ecm-tickets

Reply via email to