jira.codehaus.org

  • Log In Access more options
    • Online Help
    • Keyboard Shortcuts
    • About JIRA
    • JIRA Credits
    • What?s New
  • Dashboards Access more options (Alt+d)
  • Projects Access more options (Alt+p)
  • Issues Access more options (Alt+i)
  • Continuum
  • CONTINUUM-1130

can't delete default project group

  • Log In
  • Views
    • XML
    • Word
    • Printable

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 1.1
  • Fix Version/s: 1.3.3 (Beta)
  • Component/s: Core system, Database
  • Labels:
    None
  • Complexity:
    Intermediate

Description

I don't really want/need this - but after deleting it, it keeps coming back

  • Options
    • Sort By Name
    • Sort By Date
    • Ascending
    • Descending
    • Download All

Attachments

  1. Text File
    CONTINUUM-1130.patch
    10/Feb/09 7:42 PM
    6 kB
    Jose Morales Martinez

Activity

Ascending order - Click to sort in descending order
  • All
  • Comments
  • Work Log
  • History
  • Activity
Hide
Permalink
George Gastaldi added a comment - 04/Oct/07 9:50 PM

It is still a problem in version 1.1-beta-3.

Show
George Gastaldi added a comment - 04/Oct/07 9:50 PM It is still a problem in version 1.1-beta-3.
Hide
Permalink
Wendy Smoak added a comment - 23/Nov/07 9:14 AM

In 1.1 Final, attempting to delete the Default project group results in:

Error Occurred
javax.jdo.JDOUserException: One or more instances could not be deleted NestedThrowables: javax.jdo.JDODataStoreException: Delete request failed: DELETE FROM BUILDDEFINITION WHERE ID = ? NestedThrowables: SQL Exception: DELETE on table 'BUILDDEFINITION' caused a violation of foreign key constraint 'BUILDDEFINITCE_FK2' for key (3). The statement has been rolled back.

Show/hide Stack Trace

        javax.jdo.JDOUserException: One or more instances could not be deleted
	at org.jpox.AbstractPersistenceManager.deletePersistentAll(AbstractPersistenceManager.java:1525)
	at org.jpox.store.rdbms.scostore.ElementContainerStore.clear(ElementContainerStore.java:662)
...
NestedThrowablesStackTrace:
javax.jdo.JDODataStoreException: Delete request failed: DELETE FROM BUILDDEFINITION WHERE ID = ?
	at org.jpox.store.rdbms.request.DeleteRequest.execute(DeleteRequest.java:288)
	at org.jpox.store.rdbms.table.ClassTable.delete(ClassTable.java:2611)
	at org.jpox.store.StoreManager.delete(StoreManager.java:981)
...
NestedThrowablesStackTrace:
ERROR 23503: DELETE on table 'BUILDDEFINITION' caused a violation of foreign key constraint 'BUILDDEFINITCE_FK2' for key (3).  The statement has been rolled back.
	at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
	at org.apache.derby.impl.sql.execute.ReferencedKeyRIChecker.doCheck(Unknown Source)
	at org.apache.derby.impl.sql.execute.RISetChecker.doPKCheck(Unknown Source)
...
Show
Wendy Smoak added a comment - 23/Nov/07 9:14 AM In 1.1 Final, attempting to delete the Default project group results in: Error Occurred javax.jdo.JDOUserException: One or more instances could not be deleted NestedThrowables: javax.jdo.JDODataStoreException: Delete request failed: DELETE FROM BUILDDEFINITION WHERE ID = ? NestedThrowables: SQL Exception: DELETE on table 'BUILDDEFINITION' caused a violation of foreign key constraint 'BUILDDEFINITCE_FK2' for key (3). The statement has been rolled back. Show/hide Stack Trace
        javax.jdo.JDOUserException: One or more instances could not be deleted
	at org.jpox.AbstractPersistenceManager.deletePersistentAll(AbstractPersistenceManager.java:1525)
	at org.jpox.store.rdbms.scostore.ElementContainerStore.clear(ElementContainerStore.java:662)
...
NestedThrowablesStackTrace:
javax.jdo.JDODataStoreException: Delete request failed: DELETE FROM BUILDDEFINITION WHERE ID = ?
	at org.jpox.store.rdbms.request.DeleteRequest.execute(DeleteRequest.java:288)
	at org.jpox.store.rdbms.table.ClassTable.delete(ClassTable.java:2611)
	at org.jpox.store.StoreManager.delete(StoreManager.java:981)
...
NestedThrowablesStackTrace:
ERROR 23503: DELETE on table 'BUILDDEFINITION' caused a violation of foreign key constraint 'BUILDDEFINITCE_FK2' for key (3).  The statement has been rolled back.
	at org.apache.derby.iapi.error.StandardException.newException(Unknown Source)
	at org.apache.derby.impl.sql.execute.ReferencedKeyRIChecker.doCheck(Unknown Source)
	at org.apache.derby.impl.sql.execute.RISetChecker.doPKCheck(Unknown Source)
...
Hide
Permalink
Rahul Thakur added a comment - 02/Apr/08 5:22 PM

Ok, I could be wrong but IIRC the idea of having a default Project Group was that no Projects would live outside a ProjectGroup.

Should we allow renaming the default ProjectGroup instead of deleting it?

Show
Rahul Thakur added a comment - 02/Apr/08 5:22 PM Ok, I could be wrong but IIRC the idea of having a default Project Group was that no Projects would live outside a ProjectGroup. Should we allow renaming the default ProjectGroup instead of deleting it?
Hide
Permalink
Brett Porter added a comment - 02/Apr/08 5:25 PM

I would say only allow deleting it if it is empty, and there are no other groups. That way adding a project can always require addiion to an existing project group

Show
Brett Porter added a comment - 02/Apr/08 5:25 PM I would say only allow deleting it if it is empty, and there are no other groups. That way adding a project can always require addiion to an existing project group
Hide
Permalink
Jose Morales Martinez added a comment - 03/Feb/09 11:49 AM

The problem is not because it is the default project group, It's due to the fact project group contains a template definition. I obtain the same error by creating new project group and assign a template definition.

I got that Continuum can eliminate this type of projectgroup, but when they have problems with the generation of projects and Ant Console. Only need create a not null restriction about group project.

You believe that it would be working on this improvement, or just perform a single validation, so as not to allow the removal of the default project group?

Show
Jose Morales Martinez added a comment - 03/Feb/09 11:49 AM The problem is not because it is the default project group, It's due to the fact project group contains a template definition. I obtain the same error by creating new project group and assign a template definition. I got that Continuum can eliminate this type of projectgroup, but when they have problems with the generation of projects and Ant Console. Only need create a not null restriction about group project. You believe that it would be working on this improvement, or just perform a single validation, so as not to allow the removal of the default project group?
Hide
Permalink
Jose Morales Martinez added a comment - 10/Feb/09 7:42 PM

This patch allow delete default project group and project groups which have associated build templates. It also validates that when we add an Ant or Shell project, it must be in a project group .

Note: When we restart Continuum application, it creates the default project, I am working for to do that only the first time it create default project. Anyway, someone has a suggestion?

Show
Jose Morales Martinez added a comment - 10/Feb/09 7:42 PM This patch allow delete default project group and project groups which have associated build templates. It also validates that when we add an Ant or Shell project, it must be in a project group . Note: When we restart Continuum application, it creates the default project, I am working for to do that only the first time it create default project. Anyway, someone has a suggestion?
Hide
Permalink
Emmanuel Venisse added a comment - 26/Mar/09 1:00 AM

This patch delete the Default Project Group but we have an exception in logs.

Show
Emmanuel Venisse added a comment - 26/Mar/09 1:00 AM This patch delete the Default Project Group but we have an exception in logs.
Hide
Permalink
Emmanuel Venisse added a comment - 30/Mar/09 11:57 PM

Fixed in rev.760328
Now it is possible to remove the default project group without exception in logs. When a group is created the build definition template is cloned so th exception won't appear in the future.

Show
Emmanuel Venisse added a comment - 30/Mar/09 11:57 PM Fixed in rev.760328 Now it is possible to remove the default project group without exception in logs. When a group is created the build definition template is cloned so th exception won't appear in the future.

People

  • Assignee:
    Emmanuel Venisse
    Reporter:
    Brett Porter
Vote (5)
Watch (0)

Dates

  • Created:
    09/Jan/07 9:53 AM
    Updated:
    30/Mar/09 11:57 PM
    Resolved:
    30/Mar/09 11:57 PM
  • Atlassian JIRA (v5.0.4#731-sha1:3aa7374)
  • Report a problem
  • Powered by a free Atlassian JIRA open source license for Codehaus. Try JIRA - bug tracking software for your team.