You are viewing a plain text version of this content. The canonical link for it is here.
Posted to issues@maven.apache.org by "Carlos Sanchez (JIRA)" <ji...@codehaus.org> on 2006/10/17 23:00:53 UTC
[jira] Created: (CONTINUUM-960) Build definitions relationship with
projects is not one to one
Build definitions relationship with projects is not one to one
--------------------------------------------------------------
Key: CONTINUUM-960
URL: http://jira.codehaus.org/browse/CONTINUUM-960
Project: Continuum
Issue Type: Bug
Components: Core system, Web interface
Affects Versions: 1.1
Reporter: Carlos Sanchez
The assumption of build definition relationship one to one to project is wrong now that we have project groups.
It makes more sense to have a N to M
The problem can be seen in input() method
http://svn.apache.org/viewvc/maven/continuum/trunk/continuum-webapp/src/main/java/org/apache/maven/continuum/web/action/BuildDefinitionAction.java?view=markup
Where for a project group build definition it just assumes that the executor id is the one of the first project, wrong assumption.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-960) Build definitions relationship with
projects is not one to one
Posted by "Jesse McConnell (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Jesse McConnell updated CONTINUUM-960:
--------------------------------------
Fix Version/s: (was: 1.1-alpha-1)
1.1-alpha-#
> Build definitions relationship with projects is not one to one
> --------------------------------------------------------------
>
> Key: CONTINUUM-960
> URL: http://jira.codehaus.org/browse/CONTINUUM-960
> Project: Continuum
> Issue Type: Bug
> Components: Core system, Web interface
> Affects Versions: 1.1-alpha-1
> Reporter: Carlos Sanchez
> Fix For: 1.1-alpha-#
>
>
> The assumption of build definition relationship one to one to project is wrong now that we have project groups.
> It makes more sense to have a N to M
> The problem can be seen in input() method
> http://svn.apache.org/viewvc/maven/continuum/trunk/continuum-webapp/src/main/java/org/apache/maven/continuum/web/action/BuildDefinitionAction.java?view=markup
> Where for a project group build definition it just assumes that the executor id is the one of the first project, wrong assumption.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Updated: (CONTINUUM-960) Build definitions relationship with
projects is not one to one
Posted by "Carlos Sanchez (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-960?page=all ]
Carlos Sanchez updated CONTINUUM-960:
-------------------------------------
Fix Version/s: 1.1
> Build definitions relationship with projects is not one to one
> --------------------------------------------------------------
>
> Key: CONTINUUM-960
> URL: http://jira.codehaus.org/browse/CONTINUUM-960
> Project: Continuum
> Issue Type: Bug
> Components: Core system, Web interface
> Affects Versions: 1.1
> Reporter: Carlos Sanchez
> Fix For: 1.1
>
>
> The assumption of build definition relationship one to one to project is wrong now that we have project groups.
> It makes more sense to have a N to M
> The problem can be seen in input() method
> http://svn.apache.org/viewvc/maven/continuum/trunk/continuum-webapp/src/main/java/org/apache/maven/continuum/web/action/BuildDefinitionAction.java?view=markup
> Where for a project group build definition it just assumes that the executor id is the one of the first project, wrong assumption.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (CONTINUUM-960) Build definitions relationship with
projects is not one to one
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Venisse closed CONTINUUM-960.
--------------------------------------
Assignee: Emmanuel Venisse
Resolution: Won't Fix
this issue is out of date
> Build definitions relationship with projects is not one to one
> --------------------------------------------------------------
>
> Key: CONTINUUM-960
> URL: http://jira.codehaus.org/browse/CONTINUUM-960
> Project: Continuum
> Issue Type: Bug
> Components: Core system, Web interface
> Affects Versions: 1.1-alpha-1
> Reporter: Carlos Sanchez
> Assignee: Emmanuel Venisse
> Fix For: Future
>
>
> The assumption of build definition relationship one to one to project is wrong now that we have project groups.
> It makes more sense to have a N to M
> The problem can be seen in input() method
> http://svn.apache.org/viewvc/maven/continuum/trunk/continuum-webapp/src/main/java/org/apache/maven/continuum/web/action/BuildDefinitionAction.java?view=markup
> Where for a project group build definition it just assumes that the executor id is the one of the first project, wrong assumption.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Closed: (CONTINUUM-960) Build definitions relationship with
projects is not one to one
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Venisse closed CONTINUUM-960.
--------------------------------------
Resolution: Fixed
Fix Version/s: (was: Future)
> Build definitions relationship with projects is not one to one
> --------------------------------------------------------------
>
> Key: CONTINUUM-960
> URL: http://jira.codehaus.org/browse/CONTINUUM-960
> Project: Continuum
> Issue Type: Bug
> Components: Core system, Web interface
> Affects Versions: 1.1-alpha-1
> Reporter: Carlos Sanchez
> Assignee: Emmanuel Venisse
>
> The assumption of build definition relationship one to one to project is wrong now that we have project groups.
> It makes more sense to have a N to M
> The problem can be seen in input() method
> http://svn.apache.org/viewvc/maven/continuum/trunk/continuum-webapp/src/main/java/org/apache/maven/continuum/web/action/BuildDefinitionAction.java?view=markup
> Where for a project group build definition it just assumes that the executor id is the one of the first project, wrong assumption.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira
[jira] Reopened: (CONTINUUM-960) Build definitions relationship
with projects is not one to one
Posted by "Emmanuel Venisse (JIRA)" <ji...@codehaus.org>.
[ http://jira.codehaus.org/browse/CONTINUUM-960?page=com.atlassian.jira.plugin.system.issuetabpanels:all-tabpanel ]
Emmanuel Venisse reopened CONTINUUM-960:
----------------------------------------
> Build definitions relationship with projects is not one to one
> --------------------------------------------------------------
>
> Key: CONTINUUM-960
> URL: http://jira.codehaus.org/browse/CONTINUUM-960
> Project: Continuum
> Issue Type: Bug
> Components: Core system, Web interface
> Affects Versions: 1.1-alpha-1
> Reporter: Carlos Sanchez
> Assignee: Emmanuel Venisse
>
> The assumption of build definition relationship one to one to project is wrong now that we have project groups.
> It makes more sense to have a N to M
> The problem can be seen in input() method
> http://svn.apache.org/viewvc/maven/continuum/trunk/continuum-webapp/src/main/java/org/apache/maven/continuum/web/action/BuildDefinitionAction.java?view=markup
> Where for a project group build definition it just assumes that the executor id is the one of the first project, wrong assumption.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators: http://jira.codehaus.org/secure/Administrators.jspa
-
For more information on JIRA, see: http://www.atlassian.com/software/jira