Bug 751009 - Eclipse Guvnor plugin doesn't allow files with same name to be added
Summary: Eclipse Guvnor plugin doesn't allow files with same name to be added
Keywords:
Status: CLOSED WONTFIX
Alias: None
Product: JBoss Enterprise BRMS Platform 5
Classification: JBoss
Component: Tooling (JBDS)
Version: BRMS 5.3.0.GA
Hardware: Unspecified
OS: Unspecified
unspecified
high
Target Milestone: ---
: ---
Assignee: manstis
QA Contact: Tomas Schlosser
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2011-11-03 08:20 UTC by Tomas Schlosser
Modified: 2018-12-05 15:25 UTC (History)
6 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2012-11-07 15:47:44 UTC
Type: Enhancement


Attachments (Terms of Use)

Description Tomas Schlosser 2011-11-03 08:20:45 UTC
Description of problem:
When files have the same name they can't be added to Guvnor although they have different extension.

Version-Release number of selected component (if applicable):
BRMS-5.3.0.dev4, plugin version 5.2.1.Final

How reproducible:
Every time

Steps to Reproduce:
1. Upload to Guvnor file "samle.dsl"
2. Try to upload "sample.dslr"
  
Actual results:
sample.dslr already exists in http://localhost:8080/jboss-brms/org.drools.guvnor.Guvnor/webdav/packages/org.jboss.qa.brms.bre.functional/ 

Expected results:
file imported into Guvnor

Additional info:

Comment 1 Tihomir Surdilovic 2012-01-27 19:49:21 UTC
This is a limitation in Guvnor - asset name inside a package has to be unique.

Comment 2 manstis 2012-04-11 15:01:57 UTC
This is not a bug, but a major enhancement request. If you want to have the ability to have assets with the same name but different extensions added to Guvnor - created in Guvnor or imported via WebDav or REST etc, it will have to be done after BRMS 5.3. Set to MODIFIED for other comments.

Comment 5 Kris Verlaenen 2012-11-07 15:47:44 UTC
This won't be fixed in the current implementation as it is a limitation of the underlying Guvnor JCR repository.  Guvnor is working on a new backend (using GIT) that will resolve this.  Closing this issue as won't fix as it will not be fixed in the current codebase.


Note You need to log in before you can comment on or make changes to this bug.