Project:
| View Issue Details[ Jump to Notes ] | [ Issue History ] [ Print ] | |||||||
| ID | ||||||||
| 0009125 | ||||||||
| Type | Category | Severity | Reproducibility | Date Submitted | Last Update | |||
| defect | [Openbravo ERP] 00. Application dictionary | minor | always | 2009-05-21 04:38 | 2010-01-06 00:00 | |||
| Reporter | elopio | View Status | public | |||||
| Assigned To | iperdomo | |||||||
| Priority | high | Resolution | no change required | Fixed in Version | ||||
| Status | closed | Fix in branch | Fixed in SCM revision | |||||
| Projection | none | ETA | none | Target Version | ||||
| OS | Any | Database | Any | Java version | ||||
| OS Version | Database version | Ant version | ||||||
| Product Version | 2.50MP1 | SCM revision | ||||||
| Review Assigned To | ||||||||
| Web browser | ||||||||
| Modules | Core | |||||||
| Regression level | ||||||||
| Regression date | ||||||||
| Regression introduced in release | ||||||||
| Regression introduced by commit | ||||||||
| Triggers an Emergency Pack | No | |||||||
| Summary | 0009125: Modules should have a unique name | |||||||
| Description | Currently, from Application dictionary->Module you can create multiple modules with the same name. It's not possible to identify them from the application. | |||||||
| Steps To Reproduce | # Login as Openbravo/openbravo with role system administrator # Go to Application dictionary->Module # Click new and fill the mandatory fields: # Name: Sample Module # Version: 1.0.0 # Java Package: Sample # Description: Sample Module # Save # Click new and fill the mandatory fields: # Name: Sample Module # Version: 1.0.0 # Java Package: Sample # Description: Sample Module # Save | |||||||
| Proposed Solution | Add a constraint on modules to force the name to be unique. | |||||||
| Tags | Modularity | |||||||
| Attached Files | ||||||||
 Relationships [ Relation Graph ]
[ Dependency Graph ]
|
|
 Relationships |
|
Notes |
|
|
(0023236) iciordia (manager) 2010-01-05 13:51 |
Elopio, this is not a bug but intended behaviour. There is no reason to force uniqueness in module names. From other info (description, author, logo, etc.) it is possible to differentiate them. There is no reason to block a name just because someone else used it before. Of course Openbravo admin will take care of people copying (and in general cheating) other modules. Ismael |
|
Notes |
|
Issue History |
|||
| Date Modified | Username | Field | Change |
| 2009-05-21 04:38 | elopio | New Issue | |
| 2009-05-21 04:38 | elopio | Assigned To | => rafaroda |
| 2009-05-21 04:38 | elopio | Regression testing | => No |
| 2009-05-21 10:53 | psarobe | Tag Attached: Modularity | |
| 2009-05-21 10:54 | psarobe | Assigned To | rafaroda => iperdomo |
| 2009-05-21 10:54 | psarobe | Priority | low => high |
| 2009-05-21 10:54 | psarobe | Status | new => scheduled |
| 2010-01-05 13:51 | iciordia | Note Added: 0023236 | |
| 2010-01-05 13:51 | iciordia | Status | scheduled => closed |
| 2010-01-05 13:51 | iciordia | Resolution | open => no change required |
| 2010-01-06 00:00 | anonymous | sf_bug_id | 0 => 2926541 |
|
Issue History |
| Copyright © 2000 - 2009 MantisBT Group |
 |