Petals Studio

SA projects should also be built when a SU project is removed / refreshed / created

Details

  • Type: Bug Bug
  • Status: Closed Closed
  • Priority: Minor Minor
  • Resolution: Fixed
  • Affects Version/s: 1.0, 1.1.0
  • Fix Version/s: 1.1.1
  • Component/s: Petals Tools
  • Security Level: Public
  • Description:
    Hide

    Currently, the SA builder tests the existence of the referenced SU on the disk.
    Thus, if you delete a SU project from the workspace, but not from the disk, the builder indicates no error.
    While it should.

    It should first test the existence in the workspace, and then, and only then, for the existence on the disk.

    Show
    Currently, the SA builder tests the existence of the referenced SU on the disk. Thus, if you delete a SU project from the workspace, but not from the disk, the builder indicates no error. While it should. It should first test the existence in the workspace, and then, and only then, for the existence on the disk.
  • Environment:
    All.

Activity

Ascending order - Click to sort in descending order
Hide
Permalink
Vincent Zurczak added a comment - Fri, 20 Aug 2010 - 15:38:28 +0200

In fact, a SA project is validated in two cases:
+ If a file from the project has changed.
+ If a file from one of the SU projects has changed.

It does not handle deletion, refresh and closure actions that could be performed on a SU project.
The SA builder should in fact register a resource listener and listen to all the resource changes.
It would start a full build of the SA project if any change occurs on one of its SU projects.

This mechanism should replace the current one, where it is the SU builder that triggers a full SA validation for the second case.

Show
Vincent Zurczak added a comment - Fri, 20 Aug 2010 - 15:38:28 +0200 In fact, a SA project is validated in two cases: + If a file from the project has changed. + If a file from one of the SU projects has changed. It does not handle deletion, refresh and closure actions that could be performed on a SU project. The SA builder should in fact register a resource listener and listen to all the resource changes. It would start a full build of the SA project if any change occurs on one of its SU projects. This mechanism should replace the current one, where it is the SU builder that triggers a full SA validation for the second case.
Hide
Permalink
Vincent Zurczak added a comment - Fri, 20 Aug 2010 - 19:30:23 +0200

The title was changed.
The symptoms were true, but the diagnostic was wrong (see the last comment).

Show
Vincent Zurczak added a comment - Fri, 20 Aug 2010 - 19:30:23 +0200 The title was changed. The symptoms were true, but the diagnostic was wrong (see the last comment).
Hide
Permalink
Vincent Zurczak added a comment - Fri, 20 Aug 2010 - 19:35:29 +0200

Commits 1807 and 1808

Show
Vincent Zurczak added a comment - Fri, 20 Aug 2010 - 19:35:29 +0200 Commits 1807 and 1808

People

Dates

  • Created:
    Thu, 19 Aug 2010 - 19:46:11 +0200
    Updated:
    Fri, 20 Aug 2010 - 19:37:47 +0200
    Resolved:
    Fri, 20 Aug 2010 - 19:35:29 +0200
Atlassian JIRA (v4.1.2#531) | Report a problem | Request a feature | Contact administrators
Powered by a free Atlassian JIRA open source license for Petals ESB. Try JIRA - bug tracking software for your team.