You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "David Jencks (JIRA)" <de...@geronimo.apache.org> on 2004/10/28 23:32:32 UTC
[jira] Created: (GERONIMO-406) Move assembly out of modules
Move assembly out of modules
----------------------------
Key: GERONIMO-406
URL: http://issues.apache.org/jira/browse/GERONIMO-406
Project: Apache Geronimo
Type: Bug
Components: buildsystem
Reporter: David Jencks
The main reason for the uber-build is really the circular dependency between the modules in geronimo "modules" and openejb. Openejb requires many of the geronimo modules, and geronimo assembly requires openejb.
This could be fixed by moving geronimo assembly out of modules. I suggest making a bunch of assemblies, starting with assembly/default which will include current modules/assembly.
The result is that projects can be built in this order:
howl
geronimo/spec
tranql
tranql-connector
geronimo/modules
activemq
openejb
geronimo/assembly
This can be done by a normal continuous integration tool rather than the uber-build.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
If you want more information on JIRA, or have a bug to report see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-406) Move assembly out of modules
Posted by "Aaron Mulder (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-406?page=all ]
Aaron Mulder updated GERONIMO-406:
----------------------------------
type: Improvement (was: Bug)
Fix Version: 1.0-M5
Description:
The main reason for the uber-build is really the circular dependency between the modules in geronimo "modules" and openejb. Openejb requires many of the geronimo modules, and geronimo assembly requires openejb.
This could be fixed by moving geronimo assembly out of modules. I suggest making a bunch of assemblies, starting with assembly/default which will include current modules/assembly.
The result is that projects can be built in this order:
howl
geronimo/spec
tranql
tranql-connector
geronimo/modules
activemq
openejb
geronimo/assembly
This can be done by a normal continuous integration tool rather than the uber-build.
was:
The main reason for the uber-build is really the circular dependency between the modules in geronimo "modules" and openejb. Openejb requires many of the geronimo modules, and geronimo assembly requires openejb.
This could be fixed by moving geronimo assembly out of modules. I suggest making a bunch of assemblies, starting with assembly/default which will include current modules/assembly.
The result is that projects can be built in this order:
howl
geronimo/spec
tranql
tranql-connector
geronimo/modules
activemq
openejb
geronimo/assembly
This can be done by a normal continuous integration tool rather than the uber-build.
Version: 1.0-M4
Environment:
Assign To: Jeremy Boynes
> Move assembly out of modules
> ----------------------------
>
> Key: GERONIMO-406
> URL: http://issues.apache.org/jira/browse/GERONIMO-406
> Project: Geronimo
> Type: Improvement
> Components: buildsystem
> Versions: 1.0-M4
> Reporter: David Jencks
> Assignee: Jeremy Boynes
> Fix For: 1.0-M5
>
> The main reason for the uber-build is really the circular dependency between the modules in geronimo "modules" and openejb. Openejb requires many of the geronimo modules, and geronimo assembly requires openejb.
> This could be fixed by moving geronimo assembly out of modules. I suggest making a bunch of assemblies, starting with assembly/default which will include current modules/assembly.
> The result is that projects can be built in this order:
> howl
> geronimo/spec
> tranql
> tranql-connector
> geronimo/modules
> activemq
> openejb
> geronimo/assembly
> This can be done by a normal continuous integration tool rather than the uber-build.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Closed: (GERONIMO-406) Move assembly out of modules
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-406?page=all ]
David Jencks closed GERONIMO-406:
---------------------------------
Resolution: Duplicate
Forgot about this copy, I just reopened as GERONIMO-1306
> Move assembly out of modules
> ----------------------------
>
> Key: GERONIMO-406
> URL: http://issues.apache.org/jira/browse/GERONIMO-406
> Project: Geronimo
> Type: Improvement
> Components: buildsystem
> Versions: 1.0-M4
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 1.0
>
> The main reason for the uber-build is really the circular dependency between the modules in geronimo "modules" and openejb. Openejb requires many of the geronimo modules, and geronimo assembly requires openejb.
> This could be fixed by moving geronimo assembly out of modules. I suggest making a bunch of assemblies, starting with assembly/default which will include current modules/assembly.
> The result is that projects can be built in this order:
> howl
> geronimo/spec
> tranql
> tranql-connector
> geronimo/modules
> activemq
> openejb
> geronimo/assembly
> This can be done by a normal continuous integration tool rather than the uber-build.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-406) Move assembly out of modules
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-406?page=all ]
David Jencks updated GERONIMO-406:
----------------------------------
Fix Version: 1.0
(was: 1.x)
Assign To: David Jencks (was: Jeremy Boynes)
This is the main thing I am working on for 1.0
> Move assembly out of modules
> ----------------------------
>
> Key: GERONIMO-406
> URL: http://issues.apache.org/jira/browse/GERONIMO-406
> Project: Geronimo
> Type: Improvement
> Components: buildsystem
> Versions: 1.0-M4
> Reporter: David Jencks
> Assignee: David Jencks
> Fix For: 1.0
>
> The main reason for the uber-build is really the circular dependency between the modules in geronimo "modules" and openejb. Openejb requires many of the geronimo modules, and geronimo assembly requires openejb.
> This could be fixed by moving geronimo assembly out of modules. I suggest making a bunch of assemblies, starting with assembly/default which will include current modules/assembly.
> The result is that projects can be built in this order:
> howl
> geronimo/spec
> tranql
> tranql-connector
> geronimo/modules
> activemq
> openejb
> geronimo/assembly
> This can be done by a normal continuous integration tool rather than the uber-build.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-406) Move assembly out of modules
Posted by "David Blevins (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-406?page=all ]
David Blevins updated GERONIMO-406:
-----------------------------------
Fix Version: 1.0
(was: 1.0-M5)
> Move assembly out of modules
> ----------------------------
>
> Key: GERONIMO-406
> URL: http://issues.apache.org/jira/browse/GERONIMO-406
> Project: Geronimo
> Type: Improvement
> Components: buildsystem
> Versions: 1.0-M4
> Reporter: David Jencks
> Assignee: Jeremy Boynes
> Fix For: 1.0
>
> The main reason for the uber-build is really the circular dependency between the modules in geronimo "modules" and openejb. Openejb requires many of the geronimo modules, and geronimo assembly requires openejb.
> This could be fixed by moving geronimo assembly out of modules. I suggest making a bunch of assemblies, starting with assembly/default which will include current modules/assembly.
> The result is that projects can be built in this order:
> howl
> geronimo/spec
> tranql
> tranql-connector
> geronimo/modules
> activemq
> openejb
> geronimo/assembly
> This can be done by a normal continuous integration tool rather than the uber-build.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira
[jira] Updated: (GERONIMO-406) Move assembly out of modules
Posted by "Matt Hogstrom (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-406?page=all ]
Matt Hogstrom updated GERONIMO-406:
-----------------------------------
Fix Version: 1.x
(was: 1.0)
Is this still an issue? Moving to 1.x
> Move assembly out of modules
> ----------------------------
>
> Key: GERONIMO-406
> URL: http://issues.apache.org/jira/browse/GERONIMO-406
> Project: Geronimo
> Type: Improvement
> Components: buildsystem
> Versions: 1.0-M4
> Reporter: David Jencks
> Assignee: Jeremy Boynes
> Fix For: 1.x
>
> The main reason for the uber-build is really the circular dependency between the modules in geronimo "modules" and openejb. Openejb requires many of the geronimo modules, and geronimo assembly requires openejb.
> This could be fixed by moving geronimo assembly out of modules. I suggest making a bunch of assemblies, starting with assembly/default which will include current modules/assembly.
> The result is that projects can be built in this order:
> howl
> geronimo/spec
> tranql
> tranql-connector
> geronimo/modules
> activemq
> openejb
> geronimo/assembly
> This can be done by a normal continuous integration tool rather than the uber-build.
--
This message is automatically generated by JIRA.
-
If you think it was sent incorrectly contact one of the administrators:
http://issues.apache.org/jira/secure/Administrators.jspa
-
For more information on JIRA, see:
http://www.atlassian.com/software/jira