You are viewing a plain text version of this content. The canonical link for it is here.
Posted to dev@geronimo.apache.org by "Prasad Kashyap (JIRA)" <de...@geronimo.apache.org> on 2006/05/31 17:31:34 UTC
[jira] Created: (GERONIMO-2071) Move Geronimo build to M2 (new 1.2
trunk)
Move Geronimo build to M2 (new 1.2 trunk)
-----------------------------------------
Key: GERONIMO-2071
URL: http://issues.apache.org/jira/browse/GERONIMO-2071
Project: Geronimo
Type: New Feature
Security: public (Regular issues)
Components: buildsystem
Versions: 1.2
Reporter: Prasad Kashyap
Assigned to: Jacek Laskowski
Fix For: 1.2
A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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] Commented: (GERONIMO-2071) Move Geronimo build to M2 (new
1.2 trunk)
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=comments#action_12414879 ]
David Jencks commented on GERONIMO-2071:
----------------------------------------
prasad, the deployment-plugin patch seems to have about 5 copies of each file in it. Can you try again to produce a patch with only one copy of each file?
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: applications.patch, applications.patch.zip, configs.log, deploy-tool.patch, deploy-tool.patch, deployment-plugin.patch, geronimo.patch, geronimo.patch, geronimo.patch, m2-plugins.patch, modules.patch, mvn.log, openejb.log, openejb.patch, openejb.patch, openejb.patch, openejb.patch, pom.xml, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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-2071) Move Geronimo build to M2 (new 1.2
trunk)
Posted by "Jason Dillon (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=all ]
Jason Dillon closed GERONIMO-2071.
----------------------------------
Resolution: Fixed
m2 migration work is for the most part finished. If anything is left, please open a new issue to track.
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: buildsystem
> Affects Versions: 1.2
> Reporter: Prasad Kashyap
> Assigned To: Jason Dillon
> Fix For: 1.2
>
> Attachments: applications.patch, applications.patch.zip, configs.log, configs.log, configs.patch, configs.patch, deploy-tool.patch, deploy-tool.patch, deployment-plugin.patch, deployment-plugin.patch, geronimo-deployment-plugin-RTC-VOTE.2.patch, geronimo-deployment-plugin-RTC-VOTE.patch, geronimo.patch, geronimo.patch, geronimo.patch, m2-plugins.patch, modules.patch, modules.patch, mvn.log, openejb.log, openejb.patch, openejb.patch, openejb.patch, openejb.patch, openejb.patch, openejb.patch, pom.xml, pom.xml
>
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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-2071) Move Geronimo build to M2 (new 1.2
trunk)
Posted by "Anita Kulshreshtha (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=all ]
Anita Kulshreshtha updated GERONIMO-2071:
-----------------------------------------
Attachment: geronimo.patch
To test the build use this patch, it uses older version of activemq. The M1 build uses
activemq_version=3.2.4-SNAPSHOT, this is not available on M2 repo. Hence I have used 3.2.
To build openejb -
checkout openejb
cd openejb/modules
mvn
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: deploy-tool.patch, geronimo.patch, geronimo.patch, openejb.patch, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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] Commented: (GERONIMO-2071) Move Geronimo build to M2 (new
1.2 trunk)
Posted by "Anita Kulshreshtha (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=comments#action_12414567 ]
Anita Kulshreshtha commented on GERONIMO-2071:
----------------------------------------------
please delete PackageBuilderShellMojo.jav <---------- It was in the big patch.
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: applications.patch.zip, deploy-tool.patch, deploy-tool.patch, geronimo.patch, geronimo.patch, geronimo.patch, m2-plugins.patch, mvn.log, openejb.patch, openejb.patch, pom.xml, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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] Commented: (GERONIMO-2071) Move Geronimo build to M2 (new
1.2 trunk)
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=comments#action_12414870 ]
David Jencks commented on GERONIMO-2071:
----------------------------------------
Moved console parts into a new applications/console directory for better m2 build: fixed m1 build so it works with the new locations. This was also done in dead-1.2, although I suspect by a different method since there appear to be 2 copies of the console parts there. rev 411927.
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: applications.patch, applications.patch.zip, configs.log, deploy-tool.patch, deploy-tool.patch, deployment-plugin.patch, geronimo.patch, geronimo.patch, geronimo.patch, m2-plugins.patch, modules.patch, mvn.log, openejb.log, openejb.patch, openejb.patch, openejb.patch, openejb.patch, pom.xml, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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-2071) Move Geronimo build to M2 (new 1.2
trunk)
Posted by "Prasad Kashyap (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=all ]
Prasad Kashyap updated GERONIMO-2071:
-------------------------------------
Attachment: pom.xml
Latest pom.xml with codehaus reppo for tranql and dwrVersion set to 1.1.1
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: applications.patch.zip, deploy-tool.patch, geronimo.patch, geronimo.patch, geronimo.patch, openejb.patch, pom.xml, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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-2071) Move Geronimo build to M2 (new 1.2
trunk)
Posted by "Prasad Kashyap (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=all ]
Prasad Kashyap updated GERONIMO-2071:
-------------------------------------
Attachment: applications.patch
applications.patch does not include the console and magicGball reorg.
It also configures surefire in the geronimo/pom.xml to skip tests (for now).
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: applications.patch, applications.patch.zip, configs.log, deploy-tool.patch, deploy-tool.patch, deployment-plugin.patch, geronimo.patch, geronimo.patch, geronimo.patch, m2-plugins.patch, modules.patch, mvn.log, openejb.log, openejb.patch, openejb.patch, openejb.patch, openejb.patch, pom.xml, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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] Commented: (GERONIMO-2071) Move Geronimo build to M2 (new
1.2 trunk)
Posted by "Jacek Laskowski (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=comments#action_12414127 ]
Jacek Laskowski commented on GERONIMO-2071:
-------------------------------------------
If there's no proper version of activemq on M2 repos, why can't we use M1 repo (legacy)?
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: deploy-tool.patch, geronimo.patch, geronimo.patch, openejb.patch, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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-2071) Move Geronimo build to M2 (new 1.2
trunk)
Posted by "Anita Kulshreshtha (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=all ]
Anita Kulshreshtha updated GERONIMO-2071:
-----------------------------------------
Attachment: openejb.patch
openejb.patch is to build openejb locally. This is needed if the repository does not contain the latest
modifications.
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: deploy-tool.patch, geronimo.patch, openejb.patch, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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] Commented: (GERONIMO-2071) Move Geronimo build to M2 (new
1.2 trunk)
Posted by "Prasad Kashyap (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=comments#action_12414984 ]
Prasad Kashyap commented on GERONIMO-2071:
------------------------------------------
I cut my teeth on M2 migrating this plugin. It was also the first one to be migrated. So I "migrated" the classes as is. But I don't believe we will have a need for that class. M2 provides some form of resource filtering. So please prune this plugin and out it for vote.
The site and test were stubs for future work. But let's remove that too for now. We should revisit the sites for all plugins that we create usage info and stuff.
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: applications.patch, applications.patch.zip, configs.log, configs.log, configs.patch, configs.patch, deploy-tool.patch, deploy-tool.patch, deployment-plugin.patch, deployment-plugin.patch, geronimo.patch, geronimo.patch, geronimo.patch, m2-plugins.patch, modules.patch, modules.patch, mvn.log, openejb.log, openejb.patch, openejb.patch, openejb.patch, openejb.patch, openejb.patch, openejb.patch, pom.xml, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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] Commented: (GERONIMO-2071) Move Geronimo build to M2 (new
1.2 trunk)
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=comments#action_12415290 ]
David Jencks commented on GERONIMO-2071:
----------------------------------------
rev 412684 added more configs poms and modified dependencies so modules and configs build. In particular list all configs in the dependency-management section of the root pom. configs builds for me although I don't think it includes all the modules.
rev 412688 add 2 missing src geronimo-dependency.xml files as pointed out by anita. This leaves only the openejb ones to add.
rev 412690 go back to released xmlbeans plugin. Change was accidentally committed, I am maintaining the build against the fixed plugin.
I think this completes the existing work in patches except for openejb. I plan to apply that when it is clear which branch to apply to.
This jira and in particular its patch list has gotten very long, I suggest we start a new one for further patches and comments.
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: applications.patch, applications.patch.zip, configs.log, configs.log, configs.patch, configs.patch, deploy-tool.patch, deploy-tool.patch, deployment-plugin.patch, deployment-plugin.patch, geronimo-deployment-plugin-RTC-VOTE.2.patch, geronimo-deployment-plugin-RTC-VOTE.patch, geronimo.patch, geronimo.patch, geronimo.patch, m2-plugins.patch, modules.patch, modules.patch, mvn.log, openejb.log, openejb.patch, openejb.patch, openejb.patch, openejb.patch, openejb.patch, openejb.patch, pom.xml, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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] Commented: (GERONIMO-2071) Move Geronimo build to M2 (new
1.2 trunk)
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=comments#action_12415194 ]
David Jencks commented on GERONIMO-2071:
----------------------------------------
We have a conflict with the m1 build and geronimo-dependency.xml files. Since the geronimo groupId is different in m2 than m1, we need different contents. There is currently no way to generate the content in m2, and this is likely to stay the same for the forseeable future. If you add the m2 version to the appropriate m2 location src/resources/META-INF/geronimo-dependency.xml, the m1 build uses it instead of the generated m1 version.
I guess we need to change the m1 build to exclude this specific file?
I added the fixed g-d.xml files in rev r412485, discovered this problem, and rolled back in rev 412487.
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: applications.patch, applications.patch.zip, configs.log, configs.log, configs.patch, configs.patch, deploy-tool.patch, deploy-tool.patch, deployment-plugin.patch, deployment-plugin.patch, geronimo-deployment-plugin-RTC-VOTE.2.patch, geronimo-deployment-plugin-RTC-VOTE.patch, geronimo.patch, geronimo.patch, geronimo.patch, m2-plugins.patch, modules.patch, modules.patch, mvn.log, openejb.log, openejb.patch, openejb.patch, openejb.patch, openejb.patch, openejb.patch, openejb.patch, pom.xml, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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-2071) Move Geronimo build to M2 (new 1.2
trunk)
Posted by "Anita Kulshreshtha (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=all ]
Anita Kulshreshtha updated GERONIMO-2071:
-----------------------------------------
Attachment: modules.patch
openejb.patch
openejb.log
- This modules.patch contains axis and jetty geronimo-dependency.xml. Due to yet
unknown reason these did not get included in the patch. These files contains tomcat,
axis, wadi, and other dependencies which have same groupId in M1 and M2. There are
no geronimo dependency in g-dependency.xml.
- I could not build openejb as is after a fresh checkout. Please see attached openejb.log. The stax dependency is needed to exclude xmlbeans:xmlbeans-jsr173-api. I have attached openejb.patch which includes stax. It removes things from openejb/modules/pom.xml. These are now part of openejb/pom.xml.
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: applications.patch.zip, deploy-tool.patch, deploy-tool.patch, geronimo.patch, geronimo.patch, geronimo.patch, m2-plugins.patch, modules.patch, mvn.log, openejb.log, openejb.patch, openejb.patch, openejb.patch, openejb.patch, pom.xml, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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] Commented: (GERONIMO-2071) Move Geronimo build to M2 (new
1.2 trunk)
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=comments#action_12415217 ]
David Jencks commented on GERONIMO-2071:
----------------------------------------
Following a suggestion from anita I moved the location of the source m2 files to not conflict with m1. Committed in rev 412575. Files are in src/resources2
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: applications.patch, applications.patch.zip, configs.log, configs.log, configs.patch, configs.patch, deploy-tool.patch, deploy-tool.patch, deployment-plugin.patch, deployment-plugin.patch, geronimo-deployment-plugin-RTC-VOTE.2.patch, geronimo-deployment-plugin-RTC-VOTE.patch, geronimo.patch, geronimo.patch, geronimo.patch, m2-plugins.patch, modules.patch, modules.patch, mvn.log, openejb.log, openejb.patch, openejb.patch, openejb.patch, openejb.patch, openejb.patch, openejb.patch, pom.xml, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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] Assigned: (GERONIMO-2071) Move Geronimo build to M2 (new 1.2
trunk)
Posted by "Jason Dillon (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=all ]
Jason Dillon reassigned GERONIMO-2071:
--------------------------------------
Assignee: Jason Dillon (was: Jacek Laskowski)
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Issue Type: New Feature
> Security Level: public(Regular issues)
> Components: buildsystem
> Affects Versions: 1.2
> Reporter: Prasad Kashyap
> Assigned To: Jason Dillon
> Fix For: 1.2
>
> Attachments: applications.patch, applications.patch.zip, configs.log, configs.log, configs.patch, configs.patch, deploy-tool.patch, deploy-tool.patch, deployment-plugin.patch, deployment-plugin.patch, geronimo-deployment-plugin-RTC-VOTE.2.patch, geronimo-deployment-plugin-RTC-VOTE.patch, geronimo.patch, geronimo.patch, geronimo.patch, m2-plugins.patch, modules.patch, modules.patch, mvn.log, openejb.log, openejb.patch, openejb.patch, openejb.patch, openejb.patch, openejb.patch, openejb.patch, pom.xml, pom.xml
>
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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-2071) Move Geronimo build to M2 (new 1.2
trunk)
Posted by "Anita Kulshreshtha (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=all ]
Anita Kulshreshtha updated GERONIMO-2071:
-----------------------------------------
Attachment: configs.log
My xmlbeans pom is also autogenerated. I think(?) because the local tranql pom has been flagged as invalid, maven looks for a valid pom in the repo, and may be that is where stax is coming from -
(this is from the attached openejb.log)
[WARNING] POM for 'tranql:tranql:pom:1.3-SNAPSHOT:compile' is invalid. It will be ignored for artifa
ct resolution. Reason: Not a v4.0.0 POM.
All the *-builders have to explicitly exclude xmlbeans:xmlbeans-jsr173-api. It will be good to have it excluded at source.
The configs have always been working for me :) -
http://issues.apache.org/jira/browse/GERONIMO-2071#action_12414073
I am attaching configs.log generated for fresh checkout of rev. 411482 using -
mvn -o -Dall=configs clean install >configs.log
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: applications.patch.zip, configs.log, deploy-tool.patch, deploy-tool.patch, geronimo.patch, geronimo.patch, geronimo.patch, m2-plugins.patch, modules.patch, mvn.log, openejb.log, openejb.patch, openejb.patch, openejb.patch, openejb.patch, pom.xml, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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-2071) Move Geronimo build to M2 (new 1.2
trunk)
Posted by "Prasad Kashyap (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=all ]
Prasad Kashyap updated GERONIMO-2071:
-------------------------------------
Attachment: deployment-plugin.patch
The deployment-plugin.patch (later used by magicGball tests)
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: applications.patch.zip, configs.log, deploy-tool.patch, deploy-tool.patch, deployment-plugin.patch, geronimo.patch, geronimo.patch, geronimo.patch, m2-plugins.patch, modules.patch, mvn.log, openejb.log, openejb.patch, openejb.patch, openejb.patch, openejb.patch, pom.xml, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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] Commented: (GERONIMO-2071) Move Geronimo build to M2 (new
1.2 trunk)
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=comments#action_12414914 ]
David Jencks commented on GERONIMO-2071:
----------------------------------------
I've looked at the deployment-plugin.patch and most of it looks good. However I'm confused by the VelocityFilter class since it uses JellyContext which I would expect is unavailable in m2. Have you actually used velocity filtering in this plugin? I would actually expect this to move to the assembly plugin, IIRC in m1 it was used during unpacking to replace e.g config.xml with a filtered version.
Also I don't see any content in the site or test. Is there some?
i've updated some comments, copyright dates, and such, so if you can advise on whether these parts should remain I'll prune the patch and put it up for a vote.
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: applications.patch, applications.patch.zip, configs.log, configs.patch, deploy-tool.patch, deploy-tool.patch, deployment-plugin.patch, deployment-plugin.patch, geronimo.patch, geronimo.patch, geronimo.patch, m2-plugins.patch, modules.patch, modules.patch, mvn.log, openejb.log, openejb.patch, openejb.patch, openejb.patch, openejb.patch, openejb.patch, pom.xml, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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] Commented: (GERONIMO-2071) Move Geronimo build to M2 (new
1.2 trunk)
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=comments#action_12414882 ]
David Jencks commented on GERONIMO-2071:
----------------------------------------
Extracted the poms and classpath.properties for console from big applications.patch.zip. This should bring complete application patching per the patches as of today. (this assertion could use some checking :-) rev 411954.
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: applications.patch, applications.patch.zip, configs.log, deploy-tool.patch, deploy-tool.patch, deployment-plugin.patch, geronimo.patch, geronimo.patch, geronimo.patch, m2-plugins.patch, modules.patch, mvn.log, openejb.log, openejb.patch, openejb.patch, openejb.patch, openejb.patch, pom.xml, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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-2071) Move Geronimo build to M2 (new 1.2
trunk)
Posted by "Anita Kulshreshtha (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=all ]
Anita Kulshreshtha updated GERONIMO-2071:
-----------------------------------------
Attachment: modules.patch
configs.patch
openejb.patch
These patches are built against rev 411948. These patches adds jetty and jetty-deployer configurations.
1. modules.patch
2. configs.patch
-- The dependency on wadi and spring has been removed from g-dependency.xml
-- I had to add servlet-spec to g-dependency.xml to avoid javax.servlet.UnavailableException. This was not
needed in M1!
3. openejb.patch - It is for building openejb from the top most directory and removes stax-api dependency
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: applications.patch, applications.patch.zip, configs.log, configs.patch, deploy-tool.patch, deploy-tool.patch, deployment-plugin.patch, deployment-plugin.patch, geronimo.patch, geronimo.patch, geronimo.patch, m2-plugins.patch, modules.patch, modules.patch, mvn.log, openejb.log, openejb.patch, openejb.patch, openejb.patch, openejb.patch, openejb.patch, pom.xml, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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-2071) Move Geronimo build to M2 (new 1.2
trunk)
Posted by "Prasad Kashyap (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=all ]
Prasad Kashyap updated GERONIMO-2071:
-------------------------------------
Attachment: deployment-plugin.patch
David, can you please try this deployment-plugin.patch.
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: applications.patch, applications.patch.zip, configs.log, deploy-tool.patch, deploy-tool.patch, deployment-plugin.patch, deployment-plugin.patch, geronimo.patch, geronimo.patch, geronimo.patch, m2-plugins.patch, modules.patch, mvn.log, openejb.log, openejb.patch, openejb.patch, openejb.patch, openejb.patch, pom.xml, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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-2071) Move Geronimo build to M2 (new 1.2
trunk)
Posted by "Anita Kulshreshtha (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=all ]
Anita Kulshreshtha updated GERONIMO-2071:
-----------------------------------------
Attachment: m2-plugins.patch
deploy-tool.patch
mvn.log
Thanks! DavidJ, The m2-plugins.patch updates m2-plugin to accommodate changes in o.a.g.kernel after
rev. 409296. The PackageBuilder, MavenAttributeStore, and MavenConfigStore were affected. The deploy-tool.patch
contains o.a.g.d.PluginBootstrap2.
-- openejb tests are being skipped. will create a jira for that...
-- tomcat tests are not failing for me, see attached mvn.log.
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: applications.patch.zip, deploy-tool.patch, deploy-tool.patch, geronimo.patch, geronimo.patch, geronimo.patch, m2-plugins.patch, mvn.log, openejb.patch, openejb.patch, pom.xml, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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] Commented: (GERONIMO-2071) Move Geronimo build to M2 (new
1.2 trunk)
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=comments#action_12414854 ]
David Jencks commented on GERONIMO-2071:
----------------------------------------
Applied 5 june 2006 applications.patch in rev 411916. However, I had to merge the pom.xml by hand, and:
- did not skip tests
- left the m2-plugins building after modules
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: applications.patch, applications.patch.zip, configs.log, deploy-tool.patch, deploy-tool.patch, deployment-plugin.patch, geronimo.patch, geronimo.patch, geronimo.patch, m2-plugins.patch, modules.patch, mvn.log, openejb.log, openejb.patch, openejb.patch, openejb.patch, openejb.patch, pom.xml, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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] Commented: (GERONIMO-2071) Move Geronimo build to M2 (new
1.2 trunk)
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=comments#action_12414624 ]
David Jencks commented on GERONIMO-2071:
----------------------------------------
I think the reason that my openejb builds and yours doesn't is that for some reason my copy of the xmlbeans-maven-plugin.pom is missing the unnecessary stax dependency. However, even in the ibiblio copy it is already excluding xmlbeans-jsr173-api, so I'm not sure why it's a problem. I will investigate a bit more tomorrow, maybe we can get another release of the xmlbeans plugin out without the dependency. It would be good to fix the xmlbeans pom as well to depend on stax-api, so we don't need to include it every time we want to use xmlbeans.
Do configs build for you with the geronimo-dependency.xml files you have supplied? (I haven't tried yet)
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: applications.patch.zip, deploy-tool.patch, deploy-tool.patch, geronimo.patch, geronimo.patch, geronimo.patch, m2-plugins.patch, modules.patch, mvn.log, openejb.log, openejb.patch, openejb.patch, openejb.patch, openejb.patch, pom.xml, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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-2071) Move Geronimo build to M2 (new 1.2
trunk)
Posted by "Anita Kulshreshtha (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=all ]
Anita Kulshreshtha updated GERONIMO-2071:
-----------------------------------------
Attachment: configs.patch
openejb.patch
configs.log
adding j2ee-corba, client-corba and openejb configurations -
1. configs.patch
2. openejb.patch - checking in g-dependency.xml in openejb-core, please see :
http://issues.apache.org/jira/browse/GERONIMO-2067#action_12414961
3. configs.log - results
4. modules.patch from yesterday (June 6th)
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: applications.patch, applications.patch.zip, configs.log, configs.log, configs.patch, configs.patch, deploy-tool.patch, deploy-tool.patch, deployment-plugin.patch, deployment-plugin.patch, geronimo.patch, geronimo.patch, geronimo.patch, m2-plugins.patch, modules.patch, modules.patch, mvn.log, openejb.log, openejb.patch, openejb.patch, openejb.patch, openejb.patch, openejb.patch, openejb.patch, pom.xml, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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] Commented: (GERONIMO-2071) Move Geronimo build to M2 (new
1.2 trunk)
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=comments#action_12414880 ]
David Jencks commented on GERONIMO-2071:
----------------------------------------
Copied the magic gball files to their locations in the big applications.patch and add the poms. Commented out the reference to deployment plugin, it doesn't exist yet. Left m1 version in place, I don't want to write an m1 build for this :-)
rev 411947
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: applications.patch, applications.patch.zip, configs.log, deploy-tool.patch, deploy-tool.patch, deployment-plugin.patch, geronimo.patch, geronimo.patch, geronimo.patch, m2-plugins.patch, modules.patch, mvn.log, openejb.log, openejb.patch, openejb.patch, openejb.patch, openejb.patch, pom.xml, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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-2071) Move Geronimo build to M2 (new 1.2
trunk)
Posted by "Anita Kulshreshtha (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=all ]
Anita Kulshreshtha updated GERONIMO-2071:
-----------------------------------------
Attachment: geronimo.patch
deploy-tool.patch
pom.xml
These patches build modules, plugins, openejb, and the configs (see output for details) -
1. geronimo.patch
2. deploy-tool.patch -******** this affects m1 build*********. To build with m1 again revert this patch.
3. pom.xml is provided for the top level directory, in case there are merge conflicts.
For all the details please refer to -
http://issues.apache.org/jira/browse/GERONIMO-1740
The following configurations can be built -
[INFO]
[INFO] ----------------------------------------------------------------------------
[INFO] Reactor Summary:
[INFO] ----------------------------------------------------------------------------
[INFO] Geronimo Configs ....................................... SUCCESS [3.250s]
[INFO] Geronimo Configuration for performing service deployments SUCCESS [9.625s]
[INFO] System Configuration for the J2EE Server ............... SUCCESS [2.766s]
[INFO] RMI Naming configuration ............................... SUCCESS [1.328s]
[INFO] Server Configuration for the J2EE Server ............... SUCCESS [1.859s]
[INFO] Axis Configuration for the J2EE Server ................. SUCCESS [1.703s]
[INFO] Configuration for performing J2EE deployments .......... SUCCESS [2.438s]
[INFO] Axis Configuration for performing J2EE deployments ..... SUCCESS [2.719s]
[INFO] System Configuration for the J2EE Client ............... SUCCESS [0.937s]
[INFO] Configuration for the J2EE Client ...................... SUCCESS [1.672s]
[INFO] Configuration for Application Client Deployments ....... SUCCESS [2.547s]
[INFO] Security Configuration for the J2EE Client ............. SUCCESS [2.891s]
[INFO] Directory Configuration ................................ SUCCESS [2.359s]
[INFO] Hot Deployer ........................................... SUCCESS [1.875s]
[INFO] Security Configuration for the J2EE server ............. SUCCESS [1.531s]
[INFO] LDAP Security Realm .................................... SUCCESS [1.047s]
[INFO] Online Deployer Configuration .......................... SUCCESS [0.735s]
[INFO] openejb Configuration for performing J2EE deployments .. SUCCESS [2.750s]
[INFO] Shared Library GBean ................................... SUCCESS [0.812s]
[INFO] Shutdown Configuration ................................. SUCCESS [0.813s]
[INFO] System Database Configuration for the J2EE Server ...... SUCCESS [3.703s]
[INFO] Tomcat Configuration for the J2EE Server ............... SUCCESS [2.750s]
[INFO] Tomcat Deployer Configuration for performing J2EE deployments SUCCESS [1.453s]
[INFO] Configuration for no j2ee app clients .................. SUCCESS [1.610s]
[INFO] Configuration for no EJBs .............................. SUCCESS [1.000s]
[INFO] Unavailable Web Services deployer ...................... SUCCESS [1.109s]
[INFO] Geronimo Configuration for upgrading plans ............. SUCCESS [1.156s]
[INFO] System Configuration for the command line upgrade ...... SUCCESS [1.109s]
[INFO] ----------------------------------------------------------------------------
[INFO] ----------------------------------------------------------------------------
[INFO] BUILD SUCCESSFUL
[INFO] ----------------------------------------------------------------------------
[INFO] Total time: 1 minute 5 seconds
[INFO] Finished at: Wed May 31 10:17:18 EDT 2006
[INFO] Final Memory: 24M/49M
[INFO] ----------------------------------------------------------------------------
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: deploy-tool.patch, geronimo.patch, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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] Commented: (GERONIMO-2071) Move Geronimo build to M2 (new
1.2 trunk)
Posted by "Anita Kulshreshtha (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=comments#action_12414138 ]
Anita Kulshreshtha commented on GERONIMO-2071:
----------------------------------------------
We use 2 legacy repository -
- http://www.ibiblio.org/maven - nothing found
- http://people.apache.org/repository/incubator-activemq/jars/
The second one contains 4.0-SNAPSHOT under a different gropuId (incubator-activemq)
The version on M2 repo (repo1.maven.org) is - 4.0M1 dt Nov 2005
http://repo.mergere.com/maven2/activemq/activemq-core/4.0-M1/
We could use the incubator-activemq groupId, this is where the latest jar is.
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: deploy-tool.patch, geronimo.patch, geronimo.patch, openejb.patch, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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] Commented: (GERONIMO-2071) Move Geronimo build to M2 (new
1.2 trunk)
Posted by "Anita Kulshreshtha (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=comments#action_12415254 ]
Anita Kulshreshtha commented on GERONIMO-2071:
----------------------------------------------
Thanks! David. I did not see g-dependency.xml for axis, tomcat in rev 412630 and openejb/modules/core.
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: applications.patch, applications.patch.zip, configs.log, configs.log, configs.patch, configs.patch, deploy-tool.patch, deploy-tool.patch, deployment-plugin.patch, deployment-plugin.patch, geronimo-deployment-plugin-RTC-VOTE.2.patch, geronimo-deployment-plugin-RTC-VOTE.patch, geronimo.patch, geronimo.patch, geronimo.patch, m2-plugins.patch, modules.patch, modules.patch, mvn.log, openejb.log, openejb.patch, openejb.patch, openejb.patch, openejb.patch, openejb.patch, openejb.patch, pom.xml, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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] Commented: (GERONIMO-2071) Move Geronimo build to M2 (new
1.2 trunk)
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=comments#action_12415654 ]
David Jencks commented on GERONIMO-2071:
----------------------------------------
Openejb rev 2671 adds the 2 geronimo-dependency.xml files in src for the m2 build. I believe all work in this issue except for the deployment plugin which is being voted on is now committed.
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: applications.patch, applications.patch.zip, configs.log, configs.log, configs.patch, configs.patch, deploy-tool.patch, deploy-tool.patch, deployment-plugin.patch, deployment-plugin.patch, geronimo-deployment-plugin-RTC-VOTE.2.patch, geronimo-deployment-plugin-RTC-VOTE.patch, geronimo.patch, geronimo.patch, geronimo.patch, m2-plugins.patch, modules.patch, modules.patch, mvn.log, openejb.log, openejb.patch, openejb.patch, openejb.patch, openejb.patch, openejb.patch, openejb.patch, pom.xml, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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] Commented: (GERONIMO-2071) Move Geronimo build to M2 (new
1.2 trunk)
Posted by "Anita Kulshreshtha (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=comments#action_12414248 ]
Anita Kulshreshtha commented on GERONIMO-2071:
----------------------------------------------
In response to Matt's comments on the list :
http://www.nabble.com/Change+to+commit+model+for+Apache+Geronimo-t1660384.html
The following were part of the old trunk, and have had minor modifications to accommodate 1.1
-- pom.patch and
-- modules/**/pom.xml
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: deploy-tool.patch, geronimo.patch, geronimo.patch, openejb.patch, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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-2071) Move Geronimo build to M2 (new 1.2
trunk)
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=all ]
David Jencks updated GERONIMO-2071:
-----------------------------------
Attachment: geronimo-deployment-plugin-RTC-VOTE.2.patch
2nd version of deployment plugin patch incorporating Jacek's comments.
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: applications.patch, applications.patch.zip, configs.log, configs.log, configs.patch, configs.patch, deploy-tool.patch, deploy-tool.patch, deployment-plugin.patch, deployment-plugin.patch, geronimo-deployment-plugin-RTC-VOTE.2.patch, geronimo-deployment-plugin-RTC-VOTE.patch, geronimo.patch, geronimo.patch, geronimo.patch, m2-plugins.patch, modules.patch, modules.patch, mvn.log, openejb.log, openejb.patch, openejb.patch, openejb.patch, openejb.patch, openejb.patch, openejb.patch, pom.xml, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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-2071) Move Geronimo build to M2 (new 1.2
trunk)
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=all ]
David Jencks updated GERONIMO-2071:
-----------------------------------
Attachment: geronimo-deployment-plugin-RTC-VOTE.patch
I've cleaned up prasad's deployment plugin patch a little bit and removed some unused stuff and think it's ready to apply.
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: applications.patch, applications.patch.zip, configs.log, configs.log, configs.patch, configs.patch, deploy-tool.patch, deploy-tool.patch, deployment-plugin.patch, deployment-plugin.patch, geronimo-deployment-plugin-RTC-VOTE.patch, geronimo.patch, geronimo.patch, geronimo.patch, m2-plugins.patch, modules.patch, modules.patch, mvn.log, openejb.log, openejb.patch, openejb.patch, openejb.patch, openejb.patch, openejb.patch, openejb.patch, pom.xml, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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] Commented: (GERONIMO-2071) Move Geronimo build to M2 (new
1.2 trunk)
Posted by "Prasad Kashyap (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=comments#action_12414343 ]
Prasad Kashyap commented on GERONIMO-2071:
------------------------------------------
Just FYI -
http://www.mail-archive.com/dev@geronimo.apache.org/msg23018.html
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: applications.patch.zip, deploy-tool.patch, geronimo.patch, geronimo.patch, geronimo.patch, openejb.patch, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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-2071) Move Geronimo build to M2 (new 1.2
trunk)
Posted by "Anita Kulshreshtha (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=all ]
Anita Kulshreshtha updated GERONIMO-2071:
-----------------------------------------
Attachment: openejb.patch
This patch has the openejb-builder
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: applications.patch.zip, deploy-tool.patch, geronimo.patch, geronimo.patch, geronimo.patch, openejb.patch, openejb.patch, pom.xml, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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-2071) Move Geronimo build to M2 (new 1.2
trunk)
Posted by "Prasad Kashyap (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=all ]
Prasad Kashyap updated GERONIMO-2071:
-------------------------------------
Attachment: applications.patch.zip
The applications.patch does the following
1. in the geronimo/pom.xml, change dwrVersion to 1.1.1
2. consolidate all the individual application patches in the subtasks of http://issues.apache.org/jira/browse/GERONIMO-851.
3. consolidate and re-org console and magicGball apps.
The applications.patch does NOT do the following yet:
1. jsp precompile (http://jira.codehaus.org/browse/MJSPC-2)
2. jar classes dir to web-inf/lib/classes.jar (http://jira.codehaus.org/browse/MWAR-45)
3. migration of remote-deploy app. remote-deploy-lib app to be merged in 1.2
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: applications.patch.zip, deploy-tool.patch, geronimo.patch, geronimo.patch, geronimo.patch, openejb.patch, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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] Commented: (GERONIMO-2071) Move Geronimo build to M2 (new
1.2 trunk)
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=comments#action_12414605 ]
David Jencks commented on GERONIMO-2071:
----------------------------------------
Stax removed from openejb in rev 2664.
applied deploy-tool.patch, m2-plugins.patch, and the configs part of geronimo.patch, and removed stax dependency in rev 411465.
There are some problems:
- there are a lot of missing source geronimo-dependency.xml files. The ones generated by the m1 build don't work since they have the wrong groupId for geronimo artifacts.
- As a result, the configs builds don't work after a couple of configs.
- there are zillions of unneeded dependencies that should be taken care of by transitive dependency. I suspect this will be an ongoing battle.
- The june 3 2006 patches were created without updating to get the changes committed on june 2. This is too hard to deal with: in the future make certain your local copy is up to date with svn before creating a patch.
Either I downloaded the wrong openejb patch or the june 3 patch has no changes from the already applied june 2 patch. Please update your openejb copy and submit a patch with only the differences.
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: applications.patch.zip, deploy-tool.patch, deploy-tool.patch, geronimo.patch, geronimo.patch, geronimo.patch, m2-plugins.patch, mvn.log, openejb.patch, openejb.patch, openejb.patch, pom.xml, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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-2071) Move Geronimo build to M2 (new 1.2
trunk)
Posted by "Anita Kulshreshtha (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=all ]
Anita Kulshreshtha updated GERONIMO-2071:
-----------------------------------------
Attachment: geronimo.patch
This patch replaces the old geronimo.patch
added http://dist.codehaus.org as a 'legacy' repository to fetch the latest tranql jars
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: deploy-tool.patch, geronimo.patch, geronimo.patch, geronimo.patch, openejb.patch, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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-2071) Move Geronimo build to M2 (new 1.2
trunk)
Posted by "Anita Kulshreshtha (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=all ]
Anita Kulshreshtha updated GERONIMO-2071:
-----------------------------------------
Attachment: openejb.patch
This openejb patch moves exisiting modules/pom.xml to openejb/pom.xml
and adds a new modules/pom.xml
This is for better usability. Now all units can be built from the top directory using -
mvn -Dall=modules | m2-plugins | openejb | configs | applications (need a better name for 'all')
-- configurations must always be built using clean followed by an install.
-- As before after the modules and the plugins have been built once, the build can be run from the top directory using
mvn -o or mvn
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: applications.patch.zip, deploy-tool.patch, deploy-tool.patch, geronimo.patch, geronimo.patch, geronimo.patch, m2-plugins.patch, mvn.log, openejb.patch, openejb.patch, openejb.patch, pom.xml, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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] Commented: (GERONIMO-2071) Move Geronimo build to M2 (new
1.2 trunk)
Posted by "David Jencks (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=comments#action_12414538 ]
David Jencks commented on GERONIMO-2071:
----------------------------------------
I've applied parts of some of these patches:
openejb.patch dated 02/june/06 applied in openejb rev 2663
geronimo.patch dated 01/june/06 applied the parts for modules and m2-plugins. Have not committed the configs parts, waiting for a PluginBootstrap2 class that does not conflict with the one for m1. geronimo rev 411333.
For me all the tomcat tests fail, I had to run with mvn -Dmaven.test.skip=true. It did not look to me like the openejb tests were running at all, even with plain mvn install.
Also I updated 2 versions in /pom.xml, commons-modeler and axis, to the versions currently in the m1 build.
I think that the applications reorganization should proceed by a committer executing the svn mv operations so we preserve svn history. I doubt that patch can do this. Exactly how to proceed with this part needs a little more discussion.
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: applications.patch.zip, deploy-tool.patch, geronimo.patch, geronimo.patch, geronimo.patch, openejb.patch, openejb.patch, pom.xml, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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] Commented: (GERONIMO-2071) Move Geronimo build to M2 (new
1.2 trunk)
Posted by "Guillaume Nodet (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=comments#action_12414131 ]
Guillaume Nodet commented on GERONIMO-2071:
-------------------------------------------
ActiveMQ should be upgrade to 4.0 (which is currently voted) and m2 poms are available for this version.
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: deploy-tool.patch, geronimo.patch, geronimo.patch, openejb.patch, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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] Commented: (GERONIMO-2071) Move Geronimo build to M2 (new
1.2 trunk)
Posted by "Anita Kulshreshtha (JIRA)" <de...@geronimo.apache.org>.
[ http://issues.apache.org/jira/browse/GERONIMO-2071?page=comments#action_12414080 ]
Anita Kulshreshtha commented on GERONIMO-2071:
----------------------------------------------
Build instructions - (I have used maven 2.0.4)
from top directory -
1. mvn -N install
2. cd modules, mvn
3. cd m2-plugins, mvn install
After the plugin is built, the build can be run from the top level directory using
mvn clean install or
mvn -o clean install
configs should always be built with mvn clean install, clean is necessary for configs. this restriction will be removed soon.
> Move Geronimo build to M2 (new 1.2 trunk)
> -----------------------------------------
>
> Key: GERONIMO-2071
> URL: http://issues.apache.org/jira/browse/GERONIMO-2071
> Project: Geronimo
> Type: New Feature
> Security: public(Regular issues)
> Components: buildsystem
> Versions: 1.2
> Reporter: Prasad Kashyap
> Assignee: Jacek Laskowski
> Fix For: 1.2
> Attachments: deploy-tool.patch, geronimo.patch, pom.xml
>
> A lot of work for moving Geronimo build to M2 was done under G-851. (http://issues.apache.org/jira/browse/GERONIMO-851)
> The old trunk was renamed as dead-1.2. The new trunk was created from 1.1 and hence the migration work needs to be done here again. This JIRA will seek to consolidate the work that was done under G-851 and all it's subtasks.
> The patch(es) here will be submitted under the RTC guidelines. Future patches for migration will have to be applied on top of this one. This patch will contain the parent pom, modules, openejb, configs, m2-plugins
> Any issues/concerns about migrating some pieces are well documented in G-851 with links to dev list archives.
--
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